
From amanda.baber@icann.org  Thu Aug  1 01:10:37 2013
Return-Path: <amanda.baber@icann.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF9E21F9DB2 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 01:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DeyoCj3bbByc for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 01:10:23 -0700 (PDT)
Received: from EXPFE100-2.exc.icann.org (expfe100-2.exc.icann.org [64.78.22.237]) by ietfa.amsl.com (Postfix) with ESMTP id 9079121F9BB6 for <ietf@ietf.org>; Thu,  1 Aug 2013 01:10:09 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-2.exc.icann.org ([64.78.22.237]) with mapi; Thu, 1 Aug 2013 01:10:08 -0700
From: Amanda Baber <amanda.baber@icann.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 1 Aug 2013 01:10:06 -0700
Subject: Re: stability of iana.org URLs
Thread-Topic: stability of iana.org URLs
Thread-Index: Ac6Ojom+WzwkjGx6QoabpSsHOcTczQ==
Message-ID: <CE1FE47E.B59E%amanda.baber@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CE1FE47EB59Eamandababericannorg_"
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, 01 Aug 2013 08:10:37 -0000

--_000_CE1FE47EB59Eamandababericannorg_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNClRoZSBsaW5rIGluIFJGQzMzMTUgaXMgYWN0dWFsbHkgaW5jb3JyZWN0IC0tIGl0IHNo
b3VsZCBoYXZlIGJlZW4gaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9lbnRlcnByaXNl
LW51bWJlcnMsIHdpdGhvdXQgdGhlIGZpbGUgZXh0ZW5zaW9uLCBhbmQgdGhlcmUncyBhbiBlcnJh
dHVtIGFib3V0IHRoaXMuIEhUTUwgd2FzIGdlbmVyYWxseSAoaWYgbm90IGV4Y2x1c2l2ZWx5KSBy
ZXNlcnZlZCBmb3IgZmlsZXMgdGhhdCBuZWVkZWQgdG8gaW5jbHVkZSBsaW5rcyB0byByZWdpc3Ry
YXRpb24gZm9ybXMgLg0KDQpBcyBCYXJyeSBzYWlkLCB3ZSBkbyBpbnRlbmQgdG8ga2VlcCB0aGF0
IHNhbWUgc2hvcnQgaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9leGFtcGxlIGZvcm1h
dCB3b3JraW5nIGZvciBldmVyeSBjdXJyZW50IHBhZ2UsIGV2ZW4gdGhlIG5ld2x5LWNyZWF0ZWQg
b25lcy4gV2UgYWxzbyBwcmVmZXIgdG8gc2VlIHRoYXQgZm9ybWF0IHVzZWQgaW4gZG9jdW1lbnRz
LCBzaW5jZSB3ZSBjYW4ndCBndWFyYW50ZWUgdGhhdCB0aGUgZmlsZSBleHRlbnNpb24gdXNlZCBm
b3IgdGhlIGxvbmcgdmVyc2lvbiB3b24ndCBjaGFuZ2UuIChUaGlzIGluZm9ybWF0aW9uIHdpbGwg
YmUgYXBwZWFyaW5nIG9uIHRoZSB3ZWJzaXRlIGluIHNvbWUgZm9ybS4pDQoNCg0KQWxzbywgaWYg
eW91IGZpbmQgdGhhdCBhIGZvcm1lcmx5LXZhbGlkIFVSTCAobGlrZSBvbmUgdGhhdCB1c2VkIHRv
IGhhdmUgYW4gLmh0bWwgZXhjZXB0aW9uKSBpc24ndCByZWRpcmVjdGluZyB0byB0aGUgY3VycmVu
dCBwYWdlLCBwbGVhc2UgcmVwb3J0IGl0IHRvIGlhbmFAaWFuYS5vcmc8bWFpbHRvOmlhbmFAaWFu
YS5vcmc+LiBBIHJlZGlyZWN0IHNob3VsZCBoYXZlIGJlZW4gc2V0IHVwLg0KDQp0aGFua3MsDQoN
CkFtYW5kYSBCYWJlcg0KSUFOQSBSZXF1ZXN0IFNwZWNpYWxpc3QNCklDQU5ODQoNCk9uIFdlZCBK
dWwgMzEgMTQ6MDY6MjggMjAxMywgYmFycnlsZWliYUBjb21wdXRlci5vcmcgd3JvdGU6DQo+ID4g
SSBqdXN0IGZvbGxvd2VkIGh0dHA6Ly93d3cuaWFuYS5vcmcvYXNzaWdubWVudHMvZW50ZXJwcmlz
ZS1udW1iZXJzLmh0bWwNCj4gPiBGcm9tIFJGQzMzMTUgKERIQ1B2NikncyByZWZlcmVuY2Ugc2Vj
dGlvbi4gIFRlbiB5ZWFycyBsYXRlciwgdGhlIFVSTA0KPiA+IGRvZXNuJ3Qgd29yay4NCj4gPg0K
PiA+IEkga25vdyB0aGF0IHRoaW5ncyB3ZXJlIHJld29ya2VkIHdoZW4gd2Ugd2VudCB0byBYTUwg
YmFzZWQgc3RvcmFnZSwgYnV0DQo+ID4gSSB0aG91Z2h0IHRoYXQgdGhlIG9sZCBVUkxzIHdvdWxk
IGF0IGxlYXN0IGhhdmUgYSAzMDEgZXJyb3Igb24gdGhlbS4NCj4gPg0KPiA+IEkgZGlzY292ZXJl
ZCB0aGF0IGRyb3BwaW5nIHRoZSAuaHRtbCBnZXRzIG1lIHRoZSByaWdodCBkYXRhIGF0Og0KPiA+
ICAgaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9lbnRlcnByaXNlLW51bWJlcnMNCj4N
Cj4gWWVzOiB0aGF0J3MgdGhlIGZvcm0gdGhhdCBJQU5BIHdvdWxkIGxpa2UgeW91IHRvIHVzZS4g
IFRoZXkgY2hhbmdlZA0KPiB0aGVpciByZWdpc3RyaWVzIGZyb20gSFRNTCB0byBYTUwsIGFuZCB0
aGUgVVJMcyBjaGFuZ2VkLiAgU3VwcG9zZWQNCj4gdGhleSBzaG91bGQgZGVjaWRlIHRvIHR1cm4g
dGhlbSBhbGwgaW50byBKU09OIChhaWVlZWVlZWVlZSEpLi4uIHRoZQ0KPiBVUkxzIHdvdWxkIGNo
YW5nZSBhZ2Fpbi4gIEJ1dCB0aGUgc3VmZml4LWxlc3MgdmVyc2lvbiB3aWxsIGFsd2F5cw0KPiB3
b3JrLg0KPg0KPiBXaGVuIEkndmUgZG9uZSBBRCByZXZpZXdzIG9mIGRvY3VtZW50cyB0aGF0IGNp
dGUgSUFOQSBVUkxzLCBJJ3ZlIGdpdmVuDQo+IHRoZSBhdXRob3JzIHRoYXQgZmVlZGJhY2ssIGFu
ZCBzdWdnZXN0ZWQgdGhlIGNoYW5nZSB0byB0aGUgc3VmZml4LWxlc3MNCj4gVVJMcy4gIEkgYWxz
byBpbnRlbmQgdG8gc3VnZ2VzdCB0byBJQU5BICh0aGFua3MgdG8gYSBkb2N1bWVudCBhdXRob3Is
DQo+IGFuZCBJJ3ZlIHNpbmNlIGZvcmdvdHRlbiB3aG8gaXQgd2FzOyBzb3JyeSkgdGhhdCB0aGV5
IHBvc3QgcGVybWFsaW5rcw0KPiBpbiBhbGwgdGhlIHJlZ2lzdHJpZXMsIHNvIHBlb3BsZSB3aWxs
IGtub3cgd2hpY2ggVVJMIHRoZXkgb3VnaHQgdG8NCj4gdXNlLCBhbmQgbm90IGhhdmUgdG8gZ3Vl
c3MuDQo+DQo+IEJhcnJ5LCBBcHBsaWNhdGlvbnMgQUQNCj4NCg0KDQoNCg==

--_000_CE1FE47EB59Eamandababericannorg_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPjwvaGVhZD48Ym9keSBzdHlsZT0id29yZC13cmFwOiBicmVh
ay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtc2l6ZTogMTRweDsgIj48
ZGl2PjxwcmU+PGZvbnQgZmFjZT0iQ2FsaWJyaSI+SGksDQoNClRoZSBsaW5rIGluIFJGQzMzMTUg
aXMgYWN0dWFsbHkgaW5jb3JyZWN0IC0tIGl0IHNob3VsZCBoYXZlIGJlZW4gaHR0cDovL3d3dy5p
YW5hLm9yZy9hc3NpZ25tZW50cy9lbnRlcnByaXNlLW51bWJlcnMsIHdpdGhvdXQgdGhlIGZpbGUg
ZXh0ZW5zaW9uLCBhbmQgdGhlcmUncyBhbiBlcnJhdHVtIGFib3V0IHRoaXMuIEhUTUwgd2FzIGdl
bmVyYWxseSAoaWYgbm90IGV4Y2x1c2l2ZWx5KSByZXNlcnZlZCBmb3IgZmlsZXMgdGhhdCBuZWVk
ZWQgdG8gaW5jbHVkZSBsaW5rcyB0byByZWdpc3RyYXRpb24gZm9ybXMgLg0KDQpBcyBCYXJyeSBz
YWlkLCB3ZSBkbyBpbnRlbmQgdG8ga2VlcCB0aGF0IHNhbWUgc2hvcnQgaHR0cDovL3d3dy5pYW5h
Lm9yZy9hc3NpZ25tZW50cy9leGFtcGxlIGZvcm1hdCB3b3JraW5nIGZvciBldmVyeSBjdXJyZW50
IHBhZ2UsIGV2ZW4gdGhlIG5ld2x5LWNyZWF0ZWQgb25lcy4gV2UgYWxzbyBwcmVmZXIgdG8gc2Vl
IHRoYXQgZm9ybWF0IHVzZWQgaW4gZG9jdW1lbnRzLCBzaW5jZSB3ZSBjYW4ndCBndWFyYW50ZWUg
dGhhdCB0aGUgZmlsZSBleHRlbnNpb24gdXNlZCBmb3IgdGhlIGxvbmcgdmVyc2lvbiB3b24ndCBj
aGFuZ2UuIChUaGlzIGluZm9ybWF0aW9uIHdpbGwgYmUgYXBwZWFyaW5nIG9uIHRoZSB3ZWJzaXRl
IGluIHNvbWUgZm9ybS4pDQo8L2ZvbnQ+PC9wcmU+PHByZT48Zm9udCBmYWNlPSJDYWxpYnJpIj5B
bHNvLCBpZiB5b3UgZmluZCB0aGF0IGEgZm9ybWVybHktdmFsaWQgVVJMIChsaWtlIG9uZSB0aGF0
IHVzZWQgdG8gaGF2ZSBhbiAuaHRtbCBleGNlcHRpb24pIGlzbid0IHJlZGlyZWN0aW5nIHRvIHRo
ZSBjdXJyZW50IHBhZ2UsIHBsZWFzZSByZXBvcnQgaXQgdG8gPGEgaHJlZj0ibWFpbHRvOmlhbmFA
aWFuYS5vcmciPmlhbmFAaWFuYS5vcmc8L2E+LiBBIHJlZGlyZWN0IHNob3VsZCBoYXZlIGJlZW4g
c2V0IHVwLiA8L2ZvbnQ+PC9wcmU+PHByZT48Zm9udCBmYWNlPSJDYWxpYnJpIj50aGFua3MsPC9m
b250PjwvcHJlPjxwcmU+PGZvbnQgZmFjZT0iQ2FsaWJyaSI+QW1hbmRhIEJhYmVyDQpJQU5BIFJl
cXVlc3QgU3BlY2lhbGlzdA0KSUNBTk4gPC9mb250Pjxmb250IGZhY2U9IkNhbGlicmksc2Fucy1z
ZXJpZiI+DQoNCk9uIFdlZCBKdWwgMzEgMTQ6MDY6MjggMjAxMywgYmFycnlsZWliYUBjb21wdXRl
ci5vcmcgd3JvdGU6DQomZ3Q7ICZndDsgSSBqdXN0IGZvbGxvd2VkIGh0dHA6Ly93d3cuaWFuYS5v
cmcvYXNzaWdubWVudHMvZW50ZXJwcmlzZS1udW1iZXJzLmh0bWwNCiZndDsgJmd0OyBGcm9tIFJG
QzMzMTUgKERIQ1B2NikncyByZWZlcmVuY2Ugc2VjdGlvbi4gIFRlbiB5ZWFycyBsYXRlciwgdGhl
IFVSTA0KJmd0OyAmZ3Q7IGRvZXNuJ3Qgd29yay4NCiZndDsgJmd0Ow0KJmd0OyAmZ3Q7IEkga25v
dyB0aGF0IHRoaW5ncyB3ZXJlIHJld29ya2VkIHdoZW4gd2Ugd2VudCB0byBYTUwgYmFzZWQgc3Rv
cmFnZSwgYnV0DQomZ3Q7ICZndDsgSSB0aG91Z2h0IHRoYXQgdGhlIG9sZCBVUkxzIHdvdWxkIGF0
IGxlYXN0IGhhdmUgYSAzMDEgZXJyb3Igb24gdGhlbS4NCiZndDsgJmd0Ow0KJmd0OyAmZ3Q7IEkg
ZGlzY292ZXJlZCB0aGF0IGRyb3BwaW5nIHRoZSAuaHRtbCBnZXRzIG1lIHRoZSByaWdodCBkYXRh
IGF0Og0KJmd0OyAmZ3Q7ICAgaHR0cDovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9lbnRlcnBy
aXNlLW51bWJlcnMNCiZndDsgDQomZ3Q7IFllczogdGhhdCdzIHRoZSBmb3JtIHRoYXQgSUFOQSB3
b3VsZCBsaWtlIHlvdSB0byB1c2UuICBUaGV5IGNoYW5nZWQNCiZndDsgdGhlaXIgcmVnaXN0cmll
cyBmcm9tIEhUTUwgdG8gWE1MLCBhbmQgdGhlIFVSTHMgY2hhbmdlZC4gIFN1cHBvc2VkDQomZ3Q7
IHRoZXkgc2hvdWxkIGRlY2lkZSB0byB0dXJuIHRoZW0gYWxsIGludG8gSlNPTiAoYWllZWVlZWVl
ZWUhKS4uLiB0aGUNCiZndDsgVVJMcyB3b3VsZCBjaGFuZ2UgYWdhaW4uICBCdXQgdGhlIHN1ZmZp
eC1sZXNzIHZlcnNpb24gd2lsbCBhbHdheXMNCiZndDsgd29yay4NCiZndDsgDQomZ3Q7IFdoZW4g
SSd2ZSBkb25lIEFEIHJldmlld3Mgb2YgZG9jdW1lbnRzIHRoYXQgY2l0ZSBJQU5BIFVSTHMsIEkn
dmUgZ2l2ZW4NCiZndDsgdGhlIGF1dGhvcnMgdGhhdCBmZWVkYmFjaywgYW5kIHN1Z2dlc3RlZCB0
aGUgY2hhbmdlIHRvIHRoZSBzdWZmaXgtbGVzcw0KJmd0OyBVUkxzLiAgSSBhbHNvIGludGVuZCB0
byBzdWdnZXN0IHRvIElBTkEgKHRoYW5rcyB0byBhIGRvY3VtZW50IGF1dGhvciwNCiZndDsgYW5k
IEkndmUgc2luY2UgZm9yZ290dGVuIHdobyBpdCB3YXM7IHNvcnJ5KSB0aGF0IHRoZXkgcG9zdCBw
ZXJtYWxpbmtzDQomZ3Q7IGluIGFsbCB0aGUgcmVnaXN0cmllcywgc28gcGVvcGxlIHdpbGwga25v
dyB3aGljaCBVUkwgdGhleSBvdWdodCB0bw0KJmd0OyB1c2UsIGFuZCBub3QgaGF2ZSB0byBndWVz
cy4NCiZndDsgDQomZ3Q7IEJhcnJ5LCBBcHBsaWNhdGlvbnMgQUQNCiZndDsgDQoNCg0KPC9mb250
PjwvcHJlPjwvZGl2PjwvYm9keT48L2h0bWw+DQo=

--_000_CE1FE47EB59Eamandababericannorg_--

From rdroms.ietf@gmail.com  Thu Aug  1 01:50:59 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF5AE21F9E9A for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 01:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level: 
X-Spam-Status: No, score=-102.435 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 xc5nbj7atWtW for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 01:50:59 -0700 (PDT)
Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2F64E21F9E8B for <ietf@ietf.org>; Thu,  1 Aug 2013 01:50:59 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id f11so958673qae.3 for <ietf@ietf.org>; Thu, 01 Aug 2013 01:50:58 -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:message-id:date :to:mime-version:x-mailer; bh=yjftL3wo3GTj0xG9fAXYYAYdQR5DrZHtKAHXRSpStng=; b=U14O5/gK+wRmNcPxSxCTRGLxbAA4wkOFSYS1GSyiWsq+0msSuSYgyZFzKpHotTBXXS 688mGzz8E+0S5OaUWIzc50dA1EEDpQIE3BU19JyzomHsttvxQFUly1+QJoNWzLlZzAPh rCADr/SLNM2hKnRf/YC0XL19hiovYHWzzRoDaqrazCKjnUUhG9aOX7H6ejX3HlWjFRON /P4W/oj7TuaISUME73suIS8K7o+/ZbzoP+8PDR/Cp8H9suKL/uKwmKDqHG4JDSkqI5AT jVWWaxs90rLBL4QJHtxPevKkgakI5UyxmnrTKVtUo1J0LcOaQ4EiJIr3jNJTDZzH9S92 3Gyw==
X-Received: by 10.49.47.84 with SMTP id b20mr465339qen.83.1375347058344; Thu, 01 Aug 2013 01:50:58 -0700 (PDT)
Received: from [10.86.252.177] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id t5sm3686352qae.9.2013.08.01.01.50.56 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 01:50:57 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6tsch BoF
Message-Id: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>
Date: Thu, 1 Aug 2013 10:50:54 +0200
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 08:50:59 -0000

I found the process in the 6tsch BoF (Tue 1520) for asking about taking =
on the work discussed in the BoF to be thought-provoking.

Toward the end of the BoF, the chairs asked the question "1. Is this a =
topic that the IETF should address?"  First, the chairs asked for a hum. =
 =46rom my vantage point (middle of the room), the hum was pretty close =
to equal, for/against.  I reviewed the audio =
(http://www.ietf.org/audio/ietf87/ietf87-bellevue-20130730-1520-pm2.mp3, =
starting about 1:22), and heard a slightly louder hum "for".  The BoF =
chairs decided they needed more information than they could extract from =
the hum, so they asked for a show of hands.  =46rom the audio record, =
there were "a lot" for (which matches my recollection) and "a handful" =
against (my memory is that no hands showed against).  There was a =
request to ask for a show of hands for "how many don't know".  The =
question was asked, and the record shows "a dozen".

So, there was apparently a complete change in the answer to the question =
based on humming versus voting.  There may also have been some effect =
from asking, after the fact, for a show of hands for "don't know".

I'm really curious about the results, which indicate that, at least in =
this case, the response to the question is heavily dependent on the on =
the mode used to obtain the answers to the question (which we all know =
is possible).  In particular, the effect of humming versus show of hands =
was pretty obvious.  draft-resnick-on-consensus gives several reasons =
why humming is preferred over a show of hands.  =46rom this example, it =
seems to me to be worth considering whether a more honest and accurate =
result is obtained through humming rather than a show of hands.

The other question raised in my mind is why the initial result from the =
hum, which did not have a consensus either way, was not sufficient.  =
"Roughly the same response" for/against the question would seem to me to =
be as valid a result as explicit consensus one way or the other, and the =
act of taking a show of hands to survey the appeared to treat the hum as =
irrelevant, rather than highly significant.=20

- Ralph


From ietf@meetecho.com  Thu Aug  1 02:07:09 2013
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 2419E21F9F5F for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.206
X-Spam-Level: 
X-Spam-Status: No, score=-0.206 tagged_above=-999 required=5 tests=[AWL=0.513,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I+ljUs-HYqvJ for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:07:04 -0700 (PDT)
Received: from smtpdg5.aruba.it (smtpdg223.aruba.it [62.149.158.223]) by ietfa.amsl.com (Postfix) with ESMTP id C697D21F9A90 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:06:33 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.65.11]) by smtpcmd02.ad.aruba.it with bizsmtp id 7M6Y1m01J0EaGCq01M6ZvA; Thu, 01 Aug 2013 11:06:33 +0200
Date: Thu, 1 Aug 2013 11:06:30 +0200 (CEST)
From: Meetecho Team <ietf@meetecho.com>
To: ietf@ietf.org
Message-ID: <1612687302.15.1375347990945.JavaMail.tcastaldi@dell-tcastaldi>
Subject: TECH PLENARY session recording available
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_14_1984541037.1375347990944"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:07:09 -0000

------=_Part_14_1984541037.1375347990944
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

the full recording (synchronized video, audio, slides and jabber room) of the 
TECH PLENARY WG session at IETF 87 is available at the following URL:
http://ietf87.conf.meetecho.com/index.php/Recorded_Sessions#TECH_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.

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_14_1984541037.1375347990944--

From ietf@meetecho.com  Thu Aug  1 02:08:01 2013
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 094D621E8056 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.283
X-Spam-Level: 
X-Spam-Status: No, score=-0.283 tagged_above=-999 required=5 tests=[AWL=0.436,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4hfy3y7ACZB for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:07:56 -0700 (PDT)
Received: from smtpdg6.aruba.it (smtpdg224.aruba.it [62.149.158.224]) by ietfa.amsl.com (Postfix) with ESMTP id 87AA121F9D28 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:07:07 -0700 (PDT)
Received: from dell-tcastaldi ([130.129.65.11]) by smtpcmd02.ad.aruba.it with bizsmtp id 7M761m00M0EaGCq01M76sb; Thu, 01 Aug 2013 11:07:06 +0200
Date: Thu, 1 Aug 2013 11:07:04 +0200 (CEST)
From: Meetecho Team <ietf@meetecho.com>
To: ietf@ietf.org
Message-ID: <130523741.49.1375348024509.JavaMail.tcastaldi@dell-tcastaldi>
Subject: ADMIN PLENARY session recording available
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_48_1148688553.1375348024508"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:08:01 -0000

------=_Part_48_1148688553.1375348024508
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear all,

the full recording (synchronized video, audio, slides and jabber room) of the 
ADMIN PLENARY WG session at IETF 87 is available at the following URL:
http://ietf87.conf.meetecho.com/index.php/Recorded_Sessions#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.

Cheers,
the Meetecho Team


This email has been automatically generated by The Meetecho Conferencing System


------=_Part_48_1148688553.1375348024508--

From andy@yumaworks.com  Thu Aug  1 02:14:49 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A56721F8468 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level: 
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[AWL=-2.222, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_SUMOF=5,  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 3tztXdT09vXk for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:14:45 -0700 (PDT)
Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7A221E80A5 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:14:34 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so1862156pbb.33 for <ietf@ietf.org>; Thu, 01 Aug 2013 02:14:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=2F3U9NaMhyxCfu0XcCIXOrK/XIgc7iFduktD8itSdgU=; b=B6UANCVDVMWWcOQW5JGeuXzbSUHWxFYna9Vxmp1KRrwIV1Wj2oNhwROfmXQLxbI0Ww 7JWRxnwadjrsBdYDjfNaLC/FBaO8BvHU9Ar9eczxuv/401jI84Q6hCGxGtNu9teydTd4 GpZqPdnl/mzdfnAKI4fWd9EnP5HLlywalKwTSj9J9Gr3XzG6Zc0JECSkTZXPYOxn5qC5 zuklxmvxEKBGq7EKHfqASZmyJ8mDPErH06iIRCnAGIrWPu3UJtDVWS5xiBK20G/Nx8or JECu0qYxQ6/gdxTGqmelIdOwg3aBKQSfffyJMNcV7GnxbylawdlzIiGDgLjtVgpyNEgJ +STA==
MIME-Version: 1.0
X-Received: by 10.66.253.40 with SMTP id zx8mr2843797pac.71.1375348473842; Thu, 01 Aug 2013 02:14:33 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Thu, 1 Aug 2013 02:14:33 -0700 (PDT)
In-Reply-To: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>
Date: Thu, 1 Aug 2013 02:14:33 -0700
Message-ID: <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Andy Bierman <andy@yumaworks.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmdZ4obOjmZ/1+P4oaBZ4PyfqHFAqQBrQlE548bu2Dn+IYN62h1kH1+jfagdJVxBBzDVl1R
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:14:49 -0000

Hi,

Isn't it obvious why humming is flawed and raising hands works?
(Analog vs. digital).  A hand is either raised or it isn't.
The sum of all hands raised is comparable across tests.
The sum of the amplitude of all hums is not.


Andy

On Thu, Aug 1, 2013 at 1:50 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>
> I found the process in the 6tsch BoF (Tue 1520) for asking about taking o=
n the work discussed in the BoF to be thought-provoking.
>
> Toward the end of the BoF, the chairs asked the question "1. Is this a to=
pic that the IETF should address?"  First, the chairs asked for a hum.  Fro=
m my vantage point (middle of the room), the hum was pretty close to equal,=
 for/against.  I reviewed the audio (http://www.ietf.org/audio/ietf87/ietf8=
7-bellevue-20130730-1520-pm2.mp3, starting about 1:22), and heard a slightl=
y louder hum "for".  The BoF chairs decided they needed more information th=
an they could extract from the hum, so they asked for a show of hands.  Fro=
m the audio record, there were "a lot" for (which matches my recollection) =
and "a handful" against (my memory is that no hands showed against).  There=
 was a request to ask for a show of hands for "how many don't know".  The q=
uestion was asked, and the record shows "a dozen".
>
> So, there was apparently a complete change in the answer to the question =
based on humming versus voting.  There may also have been some effect from =
asking, after the fact, for a show of hands for "don't know".
>
> I'm really curious about the results, which indicate that, at least in th=
is case, the response to the question is heavily dependent on the on the mo=
de used to obtain the answers to the question (which we all know is possibl=
e).  In particular, the effect of humming versus show of hands was pretty o=
bvious.  draft-resnick-on-consensus gives several reasons why humming is pr=
eferred over a show of hands.  From this example, it seems to me to be wort=
h considering whether a more honest and accurate result is obtained through=
 humming rather than a show of hands.
>
> The other question raised in my mind is why the initial result from the h=
um, which did not have a consensus either way, was not sufficient.  "Roughl=
y the same response" for/against the question would seem to me to be as val=
id a result as explicit consensus one way or the other, and the act of taki=
ng a show of hands to survey the appeared to treat the hum as irrelevant, r=
ather than highly significant.
>
> - Ralph
>

From simon.leinen@switch.ch  Thu Aug  1 02:16:24 2013
Return-Path: <simon.leinen@switch.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6059121F85B3 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:16:24 -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 Xj987n8pcFmk for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:16:23 -0700 (PDT)
Received: from presunto.switch.ch (presunto.switch.ch [IPv6:2001:620:0:1b::9b]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD2221E8089 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:16:18 -0700 (PDT)
Received: from surlej.switch.ch (surlej.switch.ch [IPv6:2001:620:0:e::69]) by presunto.switch.ch (8.14.3/8.14.3/Debian-9.4) with ESMTP id r719GFco001837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Aug 2013 11:16:16 +0200
Received: from [2001:620:0:26:209f:4573:cc16:1878] (helo=Simons-MacBook-Air-34726.local) by surlej.switch.ch with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <simon.leinen@switch.ch>) id 1V4ozX-0007cn-IT; Thu, 01 Aug 2013 11:16:15 +0200
From: Simon Leinen <simon.leinen@switch.ch>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: Re: Bringing back Internet transparency
In-Reply-To: <20130730235306.B798918C0FA@mercury.lcs.mit.edu> (Noel Chiappa's message of "Tue, 30 Jul 2013 19:53:06 -0400 (EDT)")
References: <20130730235306.B798918C0FA@mercury.lcs.mit.edu>
User-Agent: Gnus/5.130008 (Ma Gnus v0.8) Emacs/24.3 (darwin)
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7, F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z, @ttmwYVO7l`6OXXYR`
Date: Thu, 01 Aug 2013 11:16:30 +0200
Message-ID: <aak3k57oup.fsf@switch.ch>
MIME-Version: 1.0
Content-Type: text/plain
X-SWITCHham-Score: 
X-CanIt-Geo: ip=2001:620:0:e::69; country=CH
X-CanItPRO-Stream: switch-ch:outbound (inherits from switch-ch:default, base:default)
X-Canit-Stats-ID: Bayes signature not available
X-Scanned-By: CanIt (www . roaringpenguin . 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, 01 Aug 2013 09:16:24 -0000

Noel Chiappa writes:
>> From: Joe Touch <touch@isi.edu>
>> "what people want" (ISP operators, or at least some of them), was an
>> artificial way to differentiate home customers from commercial
>> providers.
>> I.e., they wanted to create a differentiation that wasn't part of the
>> Internet architecture, so they put one in.
>> NATs did other things ... but IMO mostly as a by-product of this
>> primary motivation.

> I'm not so sure about that.

> For the first couple of years that I had an ISP connection (which soon
> had an early NAT box on it), whenever I called up the ISP (then, and
> still, one of the largest in the US) with a service call, the first
> thing I had to do was unplug the NAT box and plug in a host directly!

I don't think your anecdote contradicts Joe's claim.

In the eyes of your ISP, you were misbehaving, because you were
violating their assumption that you would use ONE (1) computer with that
connection.  If you had been what they consider an honest citizen, you
would have gotten a "commercial" connection to connect more than one.

(Your service calls were just an opportunity for them to remind you
about that. :-)

Another early assumption about the consumer Internet connection was that
you wouldn't use it all the time, but only when you needed it.  This
"session" concept was natural for modems or ISDN connections, but was,
somewhat artificially, included in xDSL, presumably to conserve the
valuable customer experience of "connecting" and "disconnecting".

> It was only after everyone's house had multiple PC's (which was really
> only after wireless became common - I don't think too many people were
> willing to wire their houses for Ethernet :-) that they kind of
> expected there to be a NAT box there.

Yes, eventually the ISPs had to adapt their assumptions.

> But in any event, it's doesn't void my point: if people want
> something, we have two choices: i) blow people off, and they'll adopt
> some point solution that interacts poorly with everything else, or ii)
> give people the _capabilities_ they need/want (and thereby have some
> chance at minimizing the brain damage - since generally people don't
> care _how_ it works, as long as it _does_ what they want).

> I guess this is just a long-winded, engineering take on 'the customer
> is always right'.

Yes, but it's harder than that.  In the NAT case, were our (we being the
IETF) customers the ISPs, the users (in this case "end users" who
insisted on connecting multiple devices without going incurring the
costs of becoming "commercial" customers), the vendors of then-current
equipment, the vendors of potential circumvention solutions (NATs)?

These groups of customers probably didn't agree on what they wanted.

Were all of them right?
-- 
Simon.

From joelja@bogus.com  Thu Aug  1 02:31:05 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C83221F8F24 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.03
X-Spam-Level: 
X-Spam-Status: No, score=-100.03 tagged_above=-999 required=5 tests=[AWL=-2.431, BAYES_00=-2.599, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fi2ouJkN-5Tf for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:31:02 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 649D621F9D22 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:29:32 -0700 (PDT)
Received: from dhcp-6518.meeting.ietf.org (dhcp-6518.meeting.ietf.org [130.129.101.24]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r719TLu7099543 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 1 Aug 2013 09:29:23 GMT (envelope-from joelja@bogus.com)
Message-ID: <51FA2A70.10208@bogus.com>
Date: Thu, 01 Aug 2013 11:29:20 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
In-Reply-To: <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 01 Aug 2013 09:29:24 +0000 (UTC)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:31:05 -0000

On 8/1/13 11:14 AM, Andy Bierman wrote:
> Hi,
>
> Isn't it obvious why humming is flawed and raising hands works?
> (Analog vs. digital).  A hand is either raised or it isn't.
> The sum of all hands raised is comparable across tests.
> The sum of the amplitude of all hums is not.
Consensus for any particular outcome is in the end a judgment call.
> Andy
>
> On Thu, Aug 1, 2013 at 1:50 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>> I found the process in the 6tsch BoF (Tue 1520) for asking about taking on the work discussed in the BoF to be thought-provoking.
>>
>> Toward the end of the BoF, the chairs asked the question "1. Is this a topic that the IETF should address?"  First, the chairs asked for a hum.  From my vantage point (middle of the room), the hum was pretty close to equal, for/against.  I reviewed the audio (http://www.ietf.org/audio/ietf87/ietf87-bellevue-20130730-1520-pm2.mp3, starting about 1:22), and heard a slightly louder hum "for".  The BoF chairs decided they needed more information than they could extract from the hum, so they asked for a show of hands.  From the audio record, there were "a lot" for (which matches my recollection) and "a handful" against (my memory is that no hands showed against).  There was a request to ask for a show of hands for "how many don't know".  The question was asked, and the record shows "a dozen".
>>
>> So, there was apparently a complete change in the answer to the question based on humming versus voting.  There may also have been some effect from asking, after the fact, for a show of hands for "don't know".
>>
>> I'm really curious about the results, which indicate that, at least in this case, the response to the question is heavily dependent on the on the mode used to obtain the answers to the question (which we all know is possible).  In particular, the effect of humming versus show of hands was pretty obvious.  draft-resnick-on-consensus gives several reasons why humming is preferred over a show of hands.  From this example, it seems to me to be worth considering whether a more honest and accurate result is obtained through humming rather than a show of hands.
>>
>> The other question raised in my mind is why the initial result from the hum, which did not have a consensus either way, was not sufficient.  "Roughly the same response" for/against the question would seem to me to be as valid a result as explicit consensus one way or the other, and the act of taking a show of hands to survey the appeared to treat the hum as irrelevant, rather than highly significant.
>>
>> - Ralph
>>


From rdroms.ietf@gmail.com  Thu Aug  1 02:35:00 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C059521F9FD8 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.955
X-Spam-Level: 
X-Spam-Status: No, score=-99.955 tagged_above=-999 required=5 tests=[AWL=-2.356, BAYES_00=-2.599, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bWRL3UFeaHA for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:35:00 -0700 (PDT)
Received: from mail-qe0-x22b.google.com (mail-qe0-x22b.google.com [IPv6:2607:f8b0:400d:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED5921F8F24 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:34:58 -0700 (PDT)
Received: by mail-qe0-f43.google.com with SMTP id k5so973287qej.16 for <ietf@ietf.org>; Thu, 01 Aug 2013 02:34:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=RilYNyrywG6yYOcBIDB5uIY/YkdZYJeSLPCbd2AW7uE=; b=Jhiogub0s/I0WSIt5nBgJynKa4QVzDbsl/fbYxrm4R/5FdoyAvphyglqQxx6i5Uu2v be7/Z1ncgS86hjyMNCXhlTA2wLpywRMrgrcCS3oUluR6pGXyLRbDzJOYgaNyRGQMSf45 1ibbA5zC7CN5rasVDRANlVIqE7zdnv22UBZxK4bybvdlSlP9mJkOHeOKsozl6B66K5f9 DecqsrEhJ/DimTe7urhGc8wMIf092X5LFeXy8/Zi04DdCFMM45olmozZbF9mg3WF2lah 5MIXZYdp0OkrKwIfCzwPl8TP+cw4nBCmcr3MR4lqY2X9nTnUgUdOqBP01ddNzHmUVmJw 8dsA==
X-Received: by 10.224.2.194 with SMTP id 2mr3407076qak.40.1375349696493; Thu, 01 Aug 2013 02:34:56 -0700 (PDT)
Received: from [10.86.252.177] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id b6sm179015qar.13.2013.08.01.02.34.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 02:34:55 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: 6tsch BoF
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
Date: Thu, 1 Aug 2013 11:34:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2262F8D-552E-44D7-B5F4-0FDC512BBC6A@gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:35:00 -0000

On Aug 1, 2013, at 11:14 AM 8/1/13, Andy Bierman <andy@yumaworks.com> =
wrote:

> Hi,
>=20
> Isn't it obvious why humming is flawed and raising hands works?
> (Analog vs. digital).  A hand is either raised or it isn't.
> The sum of all hands raised is comparable across tests.

The repeatable test gives *an* answer, but is not necessarily the answer =
that best reflects the sentiment of those answering the question.

A relatively imprecise thermometer that gives a reading close to the =
measured temperature is more useful than a digital thermometer that =
gives a precise but highly inaccurate reading.

- Ralph

> The sum of the amplitude of all hums is not.
>=20
>=20
> Andy
>=20
> On Thu, Aug 1, 2013 at 1:50 AM, Ralph Droms <rdroms.ietf@gmail.com> =
wrote:
>>=20
>> I found the process in the 6tsch BoF (Tue 1520) for asking about =
taking on the work discussed in the BoF to be thought-provoking.
>>=20
>> Toward the end of the BoF, the chairs asked the question "1. Is this =
a topic that the IETF should address?"  First, the chairs asked for a =
hum.  =46rom my vantage point (middle of the room), the hum was pretty =
close to equal, for/against.  I reviewed the audio =
(http://www.ietf.org/audio/ietf87/ietf87-bellevue-20130730-1520-pm2.mp3, =
starting about 1:22), and heard a slightly louder hum "for".  The BoF =
chairs decided they needed more information than they could extract from =
the hum, so they asked for a show of hands.  =46rom the audio record, =
there were "a lot" for (which matches my recollection) and "a handful" =
against (my memory is that no hands showed against).  There was a =
request to ask for a show of hands for "how many don't know".  The =
question was asked, and the record shows "a dozen".
>>=20
>> So, there was apparently a complete change in the answer to the =
question based on humming versus voting.  There may also have been some =
effect from asking, after the fact, for a show of hands for "don't =
know".
>>=20
>> I'm really curious about the results, which indicate that, at least =
in this case, the response to the question is heavily dependent on the =
on the mode used to obtain the answers to the question (which we all =
know is possible).  In particular, the effect of humming versus show of =
hands was pretty obvious.  draft-resnick-on-consensus gives several =
reasons why humming is preferred over a show of hands.  =46rom this =
example, it seems to me to be worth considering whether a more honest =
and accurate result is obtained through humming rather than a show of =
hands.
>>=20
>> The other question raised in my mind is why the initial result from =
the hum, which did not have a consensus either way, was not sufficient.  =
"Roughly the same response" for/against the question would seem to me to =
be as valid a result as explicit consensus one way or the other, and the =
act of taking a show of hands to survey the appeared to treat the hum as =
irrelevant, rather than highly significant.
>>=20
>> - Ralph
>>=20


From andy@yumaworks.com  Thu Aug  1 02:51:03 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C2121F99E9 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.023
X-Spam-Level: 
X-Spam-Status: No, score=0.023 tagged_above=-999 required=5 tests=[AWL=-2.000,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_SUMOF=5, 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 9v+ZI4rZY5hT for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 02:50:59 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3A09D21F9AD1 for <ietf@ietf.org>; Thu,  1 Aug 2013 02:50:59 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so1948517pab.13 for <ietf@ietf.org>; Thu, 01 Aug 2013 02:50:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=MkUc5IHuwid//yZjjJv5j89YTB1MjzBfERXXr3kGerw=; b=biawMzrpvZxTdFSbv6s7t+Ze+nz8AiJXH50KKDITFiDJ4k6fstlRYwphAMinQKToxX Zu0B1IgSif5uaORkfWzHsq5b7n00UAAtAFqzFlVUQnsso5ptYGFCUEY5hwzfVavAwWX1 G1tZNh3haEygiLQ5MfCL7dDrk4TPIK+mnFLNmxlNBivBX4o+Uk+RBk2vI8nKKwvQh9Aa Uhftt4uPbbAglB8JEhsdXB3pbFk4Hqt0hWOqfKlzDP3vewRWRl47KTQ1S/KdsdPF2OgN lk2dgMNAhHgRebTgNrisJPDREmY4+/FBGsu+xmpoXSzSPrg0sXbLENXyQu7Mz7jSnZDO JvUg==
MIME-Version: 1.0
X-Received: by 10.68.170.133 with SMTP id am5mr838860pbc.104.1375350658286; Thu, 01 Aug 2013 02:50:58 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Thu, 1 Aug 2013 02:50:58 -0700 (PDT)
In-Reply-To: <E2262F8D-552E-44D7-B5F4-0FDC512BBC6A@gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <E2262F8D-552E-44D7-B5F4-0FDC512BBC6A@gmail.com>
Date: Thu, 1 Aug 2013 02:50:58 -0700
Message-ID: <CABCOCHSPsybvb1YwN+RDMJcXNy2XPnHUJtvCA5+cf0CjF_mfDg@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Andy Bierman <andy@yumaworks.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlq3T74Y0szNXsXhQzLLlxzD5kVjwWAE4mPj+j55RH9XGvrml3oiIeO/SJgLlXXda23Wqs6
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 09:51:03 -0000

On Thu, Aug 1, 2013 at 2:34 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>
> On Aug 1, 2013, at 11:14 AM 8/1/13, Andy Bierman <andy@yumaworks.com> wro=
te:
>
>> Hi,
>>
>> Isn't it obvious why humming is flawed and raising hands works?
>> (Analog vs. digital).  A hand is either raised or it isn't.
>> The sum of all hands raised is comparable across tests.
>
> The repeatable test gives *an* answer, but is not necessarily the answer =
that best reflects the sentiment of those answering the question.
>
> A relatively imprecise thermometer that gives a reading close to the meas=
ured temperature is more useful than a digital thermometer that gives a pre=
cise but highly inaccurate reading.
>

I disagree.  Whether I raise my hand to ear level, 2 inches above my head,
or as high as I can reach, the chair will still count my raised hand as "1"=
.
If I hum really load (and if everybody hums at a different volume) the
chair cannot possibly know how to quantify that result.

Quantifying the number of raised hands is not a judgement call,


> - Ralph

Andy


>
>> The sum of the amplitude of all hums is not.
>>
>>
>> Andy
>>
>> On Thu, Aug 1, 2013 at 1:50 AM, Ralph Droms <rdroms.ietf@gmail.com> wrot=
e:
>>>
>>> I found the process in the 6tsch BoF (Tue 1520) for asking about taking=
 on the work discussed in the BoF to be thought-provoking.
>>>
>>> Toward the end of the BoF, the chairs asked the question "1. Is this a =
topic that the IETF should address?"  First, the chairs asked for a hum.  F=
rom my vantage point (middle of the room), the hum was pretty close to equa=
l, for/against.  I reviewed the audio (http://www.ietf.org/audio/ietf87/iet=
f87-bellevue-20130730-1520-pm2.mp3, starting about 1:22), and heard a sligh=
tly louder hum "for".  The BoF chairs decided they needed more information =
than they could extract from the hum, so they asked for a show of hands.  F=
rom the audio record, there were "a lot" for (which matches my recollection=
) and "a handful" against (my memory is that no hands showed against).  The=
re was a request to ask for a show of hands for "how many don't know".  The=
 question was asked, and the record shows "a dozen".
>>>
>>> So, there was apparently a complete change in the answer to the questio=
n based on humming versus voting.  There may also have been some effect fro=
m asking, after the fact, for a show of hands for "don't know".
>>>
>>> I'm really curious about the results, which indicate that, at least in =
this case, the response to the question is heavily dependent on the on the =
mode used to obtain the answers to the question (which we all know is possi=
ble).  In particular, the effect of humming versus show of hands was pretty=
 obvious.  draft-resnick-on-consensus gives several reasons why humming is =
preferred over a show of hands.  From this example, it seems to me to be wo=
rth considering whether a more honest and accurate result is obtained throu=
gh humming rather than a show of hands.
>>>
>>> The other question raised in my mind is why the initial result from the=
 hum, which did not have a consensus either way, was not sufficient.  "Roug=
hly the same response" for/against the question would seem to me to be as v=
alid a result as explicit consensus one way or the other, and the act of ta=
king a show of hands to survey the appeared to treat the hum as irrelevant,=
 rather than highly significant.
>>>
>>> - Ralph
>>>
>

From bmanning@isi.edu  Thu Aug  1 03:05:06 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BACDB21F9F70 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 03:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.599
X-Spam-Level: 
X-Spam-Status: No, score=-101.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_SUMOF=5, 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 ljoKKHAycxhj for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 03:05:01 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 31C7A21F9815 for <ietf@ietf.org>; Thu,  1 Aug 2013 03:05:01 -0700 (PDT)
Received: from [192.168.0.4] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r71A49KR018405 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 Aug 2013 03:04:18 -0700 (PDT)
Subject: Re: 6tsch BoF
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: manning bill <bmanning@isi.edu>
In-Reply-To: <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
Date: Thu, 1 Aug 2013 03:04:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9EDD707-14AE-4F6D-B010-D4E60AC52BDF@isi.edu>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 10:05:06 -0000

we have never voted at IETFs.
"we believe in rough consensus and running code"

/bill


On 1August2013Thursday, at 2:14, A ndy Bierman wrote:

> Hi,
>=20
> Isn't it obvious why humming is flawed and raising hands works?
> (Analog vs. digital).  A hand is either raised or it isn't.
> The sum of all hands raised is comparable across tests.
> The sum of the amplitude of all hums is not.
>=20
>=20
> Andy
>=20
> On Thu, Aug 1, 2013 at 1:50 AM, Ralph Droms <rdroms.ietf@gmail.com> =
wrote:
>>=20
>> I found the process in the 6tsch BoF (Tue 1520) for asking about =
taking on the work discussed in the BoF to be thought-provoking.
>>=20
>> Toward the end of the BoF, the chairs asked the question "1. Is this =
a topic that the IETF should address?"  First, the chairs asked for a =
hum.  =46rom my vantage point (middle of the room), the hum was pretty =
close to equal, for/against.  I reviewed the audio =
(http://www.ietf.org/audio/ietf87/ietf87-bellevue-20130730-1520-pm2.mp3, =
starting about 1:22), and heard a slightly louder hum "for".  The BoF =
chairs decided they needed more information than they could extract from =
the hum, so they asked for a show of hands.  =46rom the audio record, =
there were "a lot" for (which matches my recollection) and "a handful" =
against (my memory is that no hands showed against).  There was a =
request to ask for a show of hands for "how many don't know".  The =
question was asked, and the record shows "a dozen".
>>=20
>> So, there was apparently a complete change in the answer to the =
question based on humming versus voting.  There may also have been some =
effect from asking, after the fact, for a show of hands for "don't =
know".
>>=20
>> I'm really curious about the results, which indicate that, at least =
in this case, the response to the question is heavily dependent on the =
on the mode used to obtain the answers to the question (which we all =
know is possible).  In particular, the effect of humming versus show of =
hands was pretty obvious.  draft-resnick-on-consensus gives several =
reasons why humming is preferred over a show of hands.  =46rom this =
example, it seems to me to be worth considering whether a more honest =
and accurate result is obtained through humming rather than a show of =
hands.
>>=20
>> The other question raised in my mind is why the initial result from =
the hum, which did not have a consensus either way, was not sufficient.  =
"Roughly the same response" for/against the question would seem to me to =
be as valid a result as explicit consensus one way or the other, and the =
act of taking a show of hands to survey the appeared to treat the hum as =
irrelevant, rather than highly significant.
>>=20
>> - Ralph
>>=20


From jabley@hopcount.ca  Thu Aug  1 03:19:26 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17D8E21F8546 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 03:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BLkOHTAyM4VV for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 03:19:21 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1B51C21F84D1 for <ietf@ietf.org>; Thu,  1 Aug 2013 03:19:20 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 5so1856741pdd.34 for <ietf@ietf.org>; Thu, 01 Aug 2013 03:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=/KYZiREyoh1roMmPu2yHzzmwEmR61otlhGtSDWpeOl4=; b=e5I1bl6hQz4Aw7vkEW0rRUdLbK/kbax9Xx9ue30xadzRrDVXiWGGPjeWnlA6+YeKED hPoxIsF0jD/K6C+rafRzWP5wGiu5aDDnQzLZAioWPneuQo5FAUSq/Xt9KTTg7la6C4oo VxNY7sxo6SkPNSPxjE/LrOI7303PtHrLbVfB8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=/KYZiREyoh1roMmPu2yHzzmwEmR61otlhGtSDWpeOl4=; b=WA3ge/Op7DseP3K91iwSi+UwGK/wrQH7yfui0OUBOTH0eHDnPnTLK87i4uu1qDQ9WN SNCwqDkkonxl/4H4KVUYsK7q8nGPu68UlNa8jmdt5zghho408klhLeCV1MUb92xh8PBJ dSnXYV/jAMBurvim4Z3HDGO2+WOkdfQfsOY+T/1742ShZidvo3eh63b1GEWPiVqAwP+3 Kmlf/55IX0MLGlVAM2XdE2BztLgZ7JOnBjwuS/9pD3EWODFP4tw/v4D7VitTS4cLy93n +LrLDiSuwEbI9UQqbiZ4kVcmN9/eUk6Z2gjotT0hRRzxrlDoZ11jOx5M2DoykKqXnX1P 6/VQ==
X-Received: by 10.68.217.137 with SMTP id oy9mr936115pbc.130.1375352359836; Thu, 01 Aug 2013 03:19:19 -0700 (PDT)
Received: from ?IPv6:2001:df8::64:797e:bb2b:260b:b4f6? ([2001:df8:0:64:797e:bb2b:260b:b4f6]) by mx.google.com with ESMTPSA id ss8sm3375833pab.6.2013.08.01.03.19.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 03:19:19 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: 6tsch BoF
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <C9EDD707-14AE-4F6D-B010-D4E60AC52BDF@isi.edu>
Date: Thu, 1 Aug 2013 12:19:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <47B17831-BE30-4338-8DB7-78B401F27665@hopcount.ca>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <C9EDD707-14AE-4F6D-B010-D4E60AC52BDF@isi.edu>
To: manning bill <bmanning@isi.edu>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmpWJnsbd0Zos66zx9rE5KCB2fKRATggncs9nr8zKVqezstTIM2Zi6OwNjAtG7GgYOMPN03
Cc: Andy Bierman <andy@yumaworks.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: Thu, 01 Aug 2013 10:19:26 -0000

On 2013-08-01, at 12:04, manning bill <bmanning@isi.edu> wrote:

> we have never voted at IETFs.
> "we believe in rough consensus and running code"

The enduring tautology in this is the use of the word "we".

"some of us believe in rough consensus and running code, probably enough =
that the mantra is worth repeating, although we have not measured =
support for this quantitatively, your mileage may vary"

:-)


Joe=

From sm@resistor.net  Thu Aug  1 03:30:23 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B5921F9B28 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 03:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gb+aWDvVOR4M for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 03:30: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 449A321F99C1 for <ietf@ietf.org>; Thu,  1 Aug 2013 03:30:18 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r71AU0nf001878; Thu, 1 Aug 2013 03:30:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375353005; bh=8D9lwP1nkcQEBRiZczKdrEYXMlq1dOFvarA6zkPQajE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SAmjoz+j4j8f+rjcpFS4s2nYUv0W3MFob9ZiSUBxAM5lKf6HG5Mv+p7tlFCMGHC9O S6ONwcO6M7bPDCZSxjwvzG6AjKla0LYk4i5sW0cHj9TMfQHpMS8tQGFrNwd1L8vy5W xHfglTuxx73QvGubQtrtubinIC4evDt3t5H6/F9E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375353005; i=@resistor.net; bh=8D9lwP1nkcQEBRiZczKdrEYXMlq1dOFvarA6zkPQajE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4YtwlpfMUL/11qKgiFYDcWeG/WACkRUqV2PRhUuoOsuWtktuaWfK+03R22jaD/UAA ZRpT6uXZQ6ycsISAuSnspirnszRI9h9GR3jGOvwrHQBacOGm6GbJvZVqDZV4pY1fbf MHpmS3i/sSK8l7kOE8+j5saCk8OxKrIUT1ackr28=
Message-Id: <6.2.5.6.2.20130801022915.0cf5aa00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Aug 2013 03:29:03 -0700
To: Ralph Droms <rdroms.ietf@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: 6tsch BoF
In-Reply-To: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@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, 01 Aug 2013 10:30:24 -0000

Hi Ralph,
At 01:50 01-08-2013, Ralph Droms wrote:
>Toward the end of the BoF, the chairs asked the question "1. Is this 
>a topic that the IETF should address?"  First, the chairs asked for 
>a hum.  From my vantage point (middle of the room), the hum was 
>pretty close to equal, for/against.  I reviewed the audio 
>(http://www.ietf.org/audio/ietf87/ietf87-bellevue-20130730-1520-pm2.mp3, 
>starting about 1:22), and heard a slightly louder hum "for".  The 
>BoF chairs decided they needed more information than they could 
>extract from the hum, so they asked for a show of hands.  From the 
>audio record, there were "a lot" for (which matches my recollection) 
>and "a handful" against (my memory is that no hands showed 
>against).  There was a request to ask for a show of hands for "how 
>many don't know".  The question was asked, and the record shows "a dozen".

Switching from hums to votes is not a good idea.  The above could be because:

   (a) The question asked was incorrect.

   (b) The choices provided were incorrect.

>So, there was apparently a complete change in the answer to the 
>question based on humming versus voting.  There may also have been 
>some effect from asking, after the fact, for a show of hands for "don't know".
>
>I'm really curious about the results, which indicate that, at least 
>in this case, the response to the question is heavily dependent on 
>the on the mode used to obtain the answers to the question (which we 
>all know is possible).  In particular, the effect of humming versus 
>show of hands was pretty obvious.  draft-resnick-on-consensus gives 
>several reasons why humming is preferred over a show of hands.  From 
>this example, it seems to me to be worth considering whether a more 
>honest and accurate result is obtained through humming rather than a 
>show of hands.

Your message does not provide enough context.  The simple explanation 
is that the vote was used to change the answer.  Consensus is a 
process, i.e. there are steps which are carefully followed until 
everyone is okay with the choices which they are provided with.  In 
case of doubt, hum.

>The other question raised in my mind is why the initial result from 
>the hum, which did not have a consensus either way, was not 
>sufficient.  "Roughly the same response" for/against the question 
>would seem to me to be as valid a result as explicit consensus one 
>way or the other, and the act of taking a show of hands to survey 
>the appeared to treat the hum as irrelevant, rather than highly significant.

The first result was sufficient.  A second try, whether it is a hum 
or a vote, creates an appearance that the decision-maker did not like 
the result and is trying to change it.  A decision can be undermined 
by people conforming to what other people in the group think.

Regards,
-sm 


From andy@yumaworks.com  Thu Aug  1 04:16:47 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A60521F9BD8 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 04:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.205
X-Spam-Level: 
X-Spam-Status: No, score=0.205 tagged_above=-999 required=5 tests=[AWL=-1.818,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_SUMOF=5, 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 OvxtESYi-C1M for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 04:16:43 -0700 (PDT)
Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) by ietfa.amsl.com (Postfix) with ESMTP id 375B621F87B7 for <ietf@ietf.org>; Thu,  1 Aug 2013 04:16:43 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so727534pbb.34 for <ietf@ietf.org>; Thu, 01 Aug 2013 04:16:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=r91bvscrPHBkhDUDcUzY2EhxQ5kb4/NFlk5b4nEOoOk=; b=RDu/BRV9Uv7A3HO7r5K801RtrQ7j/xPJUReLxbRENdccn/cT8mC3uCdLuoeh5Ci8E+ djN7blB/GN5Jppm5zEE39ijWBLNmMpqWlODAcFmCgU7RHDPoDmF4RmV45OulLxlspU2h XXLBxqp8lFArDaWJ6h8EupH/hQsJci4GpUJY/DPwJdmAc8YpxqawLtA1zeXAFGq7QM+w 5wvui1HXtJmgzQEgUVRD2e4m1XmfkgPzxb7aU0zb0Jn0ibulOR5WN+qAoh87IFDkIUaN Vl03D3RpegLd0mKaDeVnz/VTQSb8OpMZkWLIuboI65w3TiyiAG+05Pr/rpj8Nwhib1RQ PUrg==
MIME-Version: 1.0
X-Received: by 10.68.131.133 with SMTP id om5mr1197435pbb.148.1375355802754; Thu, 01 Aug 2013 04:16:42 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Thu, 1 Aug 2013 04:16:42 -0700 (PDT)
In-Reply-To: <C9EDD707-14AE-4F6D-B010-D4E60AC52BDF@isi.edu>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <C9EDD707-14AE-4F6D-B010-D4E60AC52BDF@isi.edu>
Date: Thu, 1 Aug 2013 04:16:42 -0700
Message-ID: <CABCOCHQrgieR-JSFwFjkZXkeOyEPG+bqxeyYt+vHHxd_w6sv5Q@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Andy Bierman <andy@yumaworks.com>
To: manning bill <bmanning@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQk8eWO6yB/sLhBDwVSnf/mEgPHIvh65GXYAjDrZ48PhGH/EdJZP7be5d+12wCJON940+Mpr
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:16:47 -0000

On Thu, Aug 1, 2013 at 3:04 AM, manning bill <bmanning@isi.edu> wrote:
> we have never voted at IETFs.
> "we believe in rough consensus and running code"
>

We are not voting.
We are expressing agreement with a specific assertion.
That is true whether the agreement is expressed via vocalization
or motion of limbs.

Humming allows the chairs to be totally biased and interpret the hum volume
in a way that aligns with their preference for the outcome.

However, I have seen many times where the chairs clearly miscounted
the number of raised hands in order to make the outcome align
with their preference.  However this is much harder to pull off than compar=
ing
2 similar hum volumes.

The chairs can pick however they want to measure agreement.
Many chairs ask for a show of hands.  I prefer that method.
There is still a judgement call when the numbers for and against
are not significantly different.

> /bill

Andy

>
> On 1August2013Thursday, at 2:14, A ndy Bierman wrote:
>
>> Hi,
>>
>> Isn't it obvious why humming is flawed and raising hands works?
>> (Analog vs. digital).  A hand is either raised or it isn't.
>> The sum of all hands raised is comparable across tests.
>> The sum of the amplitude of all hums is not.
>>
>>
>> Andy
>>
>> On Thu, Aug 1, 2013 at 1:50 AM, Ralph Droms <rdroms.ietf@gmail.com> wrot=
e:
>>>
>>> I found the process in the 6tsch BoF (Tue 1520) for asking about taking=
 on the work discussed in the BoF to be thought-provoking.
>>>
>>> Toward the end of the BoF, the chairs asked the question "1. Is this a =
topic that the IETF should address?"  First, the chairs asked for a hum.  F=
rom my vantage point (middle of the room), the hum was pretty close to equa=
l, for/against.  I reviewed the audio (http://www.ietf.org/audio/ietf87/iet=
f87-bellevue-20130730-1520-pm2.mp3, starting about 1:22), and heard a sligh=
tly louder hum "for".  The BoF chairs decided they needed more information =
than they could extract from the hum, so they asked for a show of hands.  F=
rom the audio record, there were "a lot" for (which matches my recollection=
) and "a handful" against (my memory is that no hands showed against).  The=
re was a request to ask for a show of hands for "how many don't know".  The=
 question was asked, and the record shows "a dozen".
>>>
>>> So, there was apparently a complete change in the answer to the questio=
n based on humming versus voting.  There may also have been some effect fro=
m asking, after the fact, for a show of hands for "don't know".
>>>
>>> I'm really curious about the results, which indicate that, at least in =
this case, the response to the question is heavily dependent on the on the =
mode used to obtain the answers to the question (which we all know is possi=
ble).  In particular, the effect of humming versus show of hands was pretty=
 obvious.  draft-resnick-on-consensus gives several reasons why humming is =
preferred over a show of hands.  From this example, it seems to me to be wo=
rth considering whether a more honest and accurate result is obtained throu=
gh humming rather than a show of hands.
>>>
>>> The other question raised in my mind is why the initial result from the=
 hum, which did not have a consensus either way, was not sufficient.  "Roug=
hly the same response" for/against the question would seem to me to be as v=
alid a result as explicit consensus one way or the other, and the act of ta=
king a show of hands to survey the appeared to treat the hum as irrelevant,=
 rather than highly significant.
>>>
>>> - Ralph
>>>
>

From ynir@checkpoint.com  Thu Aug  1 04:24:36 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17DFA21F964C for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 04:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.041
X-Spam-Level: 
X-Spam-Status: No, score=-8.041 tagged_above=-999 required=5 tests=[AWL=-2.442, BAYES_00=-2.599, GB_SUMOF=5, 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 ENzKBniDtra8 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 04:24:30 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 33C8A21E805F for <ietf@ietf.org>; Thu,  1 Aug 2013 04:24:27 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r71BOLV2032594; Thu, 1 Aug 2013 14:24:21 +0300
X-CheckPoint: {51FA4564-5-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Thu, 1 Aug 2013 14:24:20 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: 6tsch BoF
Thread-Topic: 6tsch BoF
Thread-Index: AQHOjpRRvA0DsGkI/0mTWZRWP8a6NJl/356AgAAkPgA=
Date: Thu, 1 Aug 2013 11:24:20 +0000
Message-ID: <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
In-Reply-To: <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.100]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1185dcd7b35b092494c3b7b975d5e65496b2edf6a2
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <A73E9753F245BE41A6FB672240589656@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:24:36 -0000

On Aug 1, 2013, at 11:14 AM, Andy Bierman <andy@yumaworks.com> wrote:

> Hi,
>=20
> Isn't it obvious why humming is flawed and raising hands works?
> (Analog vs. digital).  A hand is either raised or it isn't.
> The sum of all hands raised is comparable across tests.
> The sum of the amplitude of all hums is not.

Hums are better as they give greater weight to people who are more vocally =
in support (or in opposition) to the assertion.

Research shows([1]), that the one humming loudly for acceptance, will also =
volunteer to review and contribute code. The one humming loudly against is =
going to jump up to the mike in all future meetings and tell the group that=
 they're doing the wrong thing. Those who hum softly will go back to readin=
g their email.

Yoav

[1] citation needed


From scott.brim@gmail.com  Thu Aug  1 04:38:30 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A69E121F9BD3 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 04:38: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, 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 UmeDqVbRpDYY for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 04:38:30 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3359621E80C7 for <ietf@ietf.org>; Thu,  1 Aug 2013 04:38:30 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k18so3096532oag.40 for <ietf@ietf.org>; Thu, 01 Aug 2013 04:38: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 :content-type; bh=BD9RrD2/Ys1MLTVPAXQu4BG9BFHr4W8ngRCswRM9cqI=; b=zvKyfo5tWx8ykqDIN5E2cW6JsLw7UqZA/AAo4wYG57+wKp3evMadHL/wE/cJuoLY36 CtzrXFoMl3C6wbisk+U0jK0UnVMA6FimP3UWfE7+qAv8AwMBmJ9IrGecGsHyqYGvPOUn G3sZfXwmHo3E04iwsa6USRuDsdfnEJWIFLceEiNJVsDdP+EHOrmpJJ8aAaBGU0sBbne/ zGJ4RbcFytdCO7nhC3ADTljLHGZJF1CcMiHEXSq5Jtm0flwRTJl8Sz2NyJvTlHPiLC9G RhKIyz+vZpUItuT7aLxN/FqCQ03IAth/5j5DUjR1TlBzD6s9VcnVf0+D9K/iTNtN5R29 tLcA==
MIME-Version: 1.0
X-Received: by 10.182.220.199 with SMTP id py7mr775686obc.92.1375357108966; Thu, 01 Aug 2013 04:38:28 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Thu, 1 Aug 2013 04:38:28 -0700 (PDT)
In-Reply-To: <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com>
Date: Thu, 1 Aug 2013 13:38:28 +0200
Message-ID: <CAPv4CP_jFg8+hbdFYa_vm2rt3GC3ZpyrPoXQqKJu6hD2MtHjgQ@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Scott Brim <scott.brim@gmail.com>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c334aaeb5e6104e2e147e5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 11:38:30 -0000

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

See draft-resnick-on-consensus for the art of running a group using hums
and other tools.  With those nuances, I like hums.

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

See draft-resnick-on-consensus for the art of running a group using hums an=
d other tools. =A0With those nuances, I like hums.

--001a11c334aaeb5e6104e2e147e5--

From jcurran@istaff.org  Thu Aug  1 05:02:17 2013
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 553EF11E8136 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 05:02: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 QpVLJYbwb0Ch for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 05:02:12 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id 292FA21F9971 for <ietf@ietf.org>; Thu,  1 Aug 2013 05:01:30 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1V4rZN-000CMx-Hy; Thu, 01 Aug 2013 12:01:25 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19qocmp+XB+4ILQRUo4w+jq
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: stability of iana.org URLs
From: John Curran <jcurran@istaff.org>
In-Reply-To: <51F91B02.2040000@stpeter.im>
Date: Thu, 1 Aug 2013 08:01:07 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <4343AF25-8499-46A5-AFF1-20EED321994D@istaff.org>
References: <24093.1375278470@sandelman.ca> <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com> <51F91B02.2040000@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1508)
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, 01 Aug 2013 12:02:17 -0000

On Jul 31, 2013, at 10:11 AM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> 
> That's true, but cool URIs don't change:
> 
> http://www.w3.org/Provider/Style/URI.html

Even cooler would have been URN's (e.g. urn:ietf:enterprise-numbers), 
which was designed specifically as a persistent handle to information
(ref: http://en.wikipedia.org/wiki/Uniform_resource_name) but alas, it 
was not to be.

/John


From stpeter@stpeter.im  Thu Aug  1 06:29:55 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7252D21F9DCB for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 06:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.415
X-Spam-Level: 
X-Spam-Status: No, score=-102.415 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCzWRnWM82Cd for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 06:29:46 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0E42B21F9D98 for <ietf@ietf.org>; Thu,  1 Aug 2013 06:29:07 -0700 (PDT)
Received: from che-vpn-cluster-1-111.cisco.com (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 6FAD440344; Thu,  1 Aug 2013 07:31:25 -0600 (MDT)
Message-ID: <51FA62A0.3030804@stpeter.im>
Date: Thu, 01 Aug 2013 15:29:04 +0200
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>
Subject: Re: stability of iana.org URLs
References: <24093.1375278470@sandelman.ca> <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com> <51F91B02.2040000@stpeter.im> <4343AF25-8499-46A5-AFF1-20EED321994D@istaff.org>
In-Reply-To: <4343AF25-8499-46A5-AFF1-20EED321994D@istaff.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=us-ascii
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, 01 Aug 2013 13:29:55 -0000

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

On 8/1/13 2:01 PM, John Curran wrote:
> On Jul 31, 2013, at 10:11 AM, Peter Saint-Andre
> <stpeter@stpeter.im> wrote:
>> 
>> That's true, but cool URIs don't change:
>> 
>> http://www.w3.org/Provider/Style/URI.html
> 
> Even cooler would have been URN's (e.g.
> urn:ietf:enterprise-numbers), which was designed specifically as a
> persistent handle to information (ref:
> http://en.wikipedia.org/wiki/Uniform_resource_name) but alas, it 
> was not to be.

You're preaching to the choir:

https://datatracker.ietf.org/doc/draft-saintandre-iana-urn/

Peter

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


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

iQIcBAEBAgAGBQJR+mKgAAoJEOoGpJErxa2pqxgP/3/G2YgYnSzblkgnxtx8zB8H
ff81vkCnhRF/HnfZ5AwSjoXNvoGLNo+5e86ma6RUf6cOmKid11CaLqx6fZuBIKIt
dDmeyPloU4cL90qr7DDa6+msecLUEJpywtc9rTqHCVreaxplVW01aAhIpHtx+ElH
azvvYkg+C2uA2AYi2d9UCXheBKVFWZ25GxUUoUKF8VIy6htwslAZ+kbbaAuiStdo
zc0+XKjnpTB2Ng2jrUfBScuguos8ISH4WbJ0bDMmcF0pl20tX7oiQ2OkdGkaNYuL
UQIAZKyL+GZfhvFid+OSVWzNPUTP+ai3PXE4CdU5r1FdhyfYacQFXSvAzK5uSB5T
Iuo7mBouv87MFYvRcAZOkRv1ALcYeut5ZrzB/1zCWDtTVo7dMuICLms7FdZ/IiMw
j2Zd4xp+ATcPDiLAxACBoDU8l8A6Sw2XDr99o/G7qGu6Ligu5+qqjO1mrmEhNt9o
ZcJKhdof8DLknMGUcOsU0vPyxNaJoutZbk2xMoiDCa8USlhCanwZO1Ok98tL6/dx
sDGe750VH18YCCLZ0mpPHImtQK4OZ6dZSXIbxBeGCMiCQxiaKGbrKDeQAjf7ITa3
e86A9RN3LoJFpzL/uV+cHQisilrZaTZM4td7DHvGphmVdJu9vx0LAwPQU8+nTdWT
iNF30/g+vGz1gHk0D6Ad
=UYu0
-----END PGP SIGNATURE-----

From andy@yumaworks.com  Thu Aug  1 06:30:46 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA8621E8156 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 06:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.856
X-Spam-Level: 
X-Spam-Status: No, score=0.856 tagged_above=-999 required=5 tests=[AWL=-2.167,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_SUMOF=5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ng3y6w2cGtRY for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 06:30:41 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id 73BC121E80FE for <ietf@ietf.org>; Thu,  1 Aug 2013 06:30:19 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z11so1275752pdj.31 for <ietf@ietf.org>; Thu, 01 Aug 2013 06:30:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=1igF4+Ft6DY72HbbYJRMEWNxkTnnZm6/KCxMoTUFb5I=; b=nCAIge/jiG7qLbpw+tNTMGJdG0aOEMl2X+B2SgposQeRpbnOhkzsg/x1nHZ07p7QvY 0rfgT+GVoydHAXlbsROYrDUrO1gDQryN2YUKdgoUb76lG4jtN+SaInF7EOsdhJTOZvLh 8gICN0gnbAtX8xuk8Gx+Roh1aIuQyuVMIW19PkKtBJMBhnsOD2GUmzfPohcnm+L+CyDA tsXPNmhCrWfSsbzxWcmnmla5Tip43ekYQPnLsXk/wytNRlPCzl+/ScR1+8TIaDnvf342 65Ig4znOgqVgeJLTd5VBA/hp605BLrsSukfhj5x1L1JjHvNWAU6Qn68jgCP3JGO9+Paj gttA==
MIME-Version: 1.0
X-Received: by 10.68.170.133 with SMTP id am5mr2019080pbc.104.1375363819096; Thu, 01 Aug 2013 06:30:19 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Thu, 1 Aug 2013 06:30:19 -0700 (PDT)
In-Reply-To: <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com>
Date: Thu, 1 Aug 2013 06:30:19 -0700
Message-ID: <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Andy Bierman <andy@yumaworks.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkiXuUCPlG0GC31LLj6Gqk6fzly3XXlM6+17+y9Eiofws+pU6dh1T5lq4aLWbhjsVvs0BOA
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 13:30:46 -0000

On Thu, Aug 1, 2013 at 4:24 AM, Yoav Nir <ynir@checkpoint.com> wrote:
>
> On Aug 1, 2013, at 11:14 AM, Andy Bierman <andy@yumaworks.com> wrote:
>
>> Hi,
>>
>> Isn't it obvious why humming is flawed and raising hands works?
>> (Analog vs. digital).  A hand is either raised or it isn't.
>> The sum of all hands raised is comparable across tests.
>> The sum of the amplitude of all hums is not.
>
> Hums are better as they give greater weight to people who are more vocall=
y in support (or in opposition) to the assertion.
>

Please provide some evidence that a loud hum means the person is more
committed to work on an item.

Favoring loud humming is subject to cultural bias.
Some cultures are more inclined to raise their voice than others.
Some people have naturally louder voices than others.
Measuring volume may introduce bias in favor of loud men and against
soft-spoken women, for example.

This cultural bias is not compatible with increased inclusiveness.


Andy

> Research shows([1]), that the one humming loudly for acceptance, will als=
o volunteer to review and contribute code. The one humming loudly against i=
s going to jump up to the mike in all future meetings and tell the group th=
at they're doing the wrong thing. Those who hum softly will go back to read=
ing their email.
>
> Yoav
>
> [1] citation needed
>

From rdroms.ietf@gmail.com  Thu Aug  1 07:39:59 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1708421E8233 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 07:39:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.203
X-Spam-Level: 
X-Spam-Status: No, score=-96.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_SUMOF=5, 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 1+guGpQmEwcf for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 07:39:58 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8744321E8253 for <ietf@ietf.org>; Thu,  1 Aug 2013 07:39:52 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so917260pbb.20 for <ietf@ietf.org>; Thu, 01 Aug 2013 07:39:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:content-transfer-encoding:subject:references:from :mime-version:in-reply-to:message-id:date:cc:to:x-mailer; bh=hkBDy+j6eSuAvu9CPOQ+xrC5ev9rnUMRbUkaEGpMSlA=; b=IpkB1yR9tlHYZCJsghebubEF6kYfFHlCYjKCo/cBH3kcYAV608zbODmvUG9Ot4R+3+ +ecpLzGSh26ee7zMuPQJZcgzKHuJK7Jt6UAFVo4G1VD3GuJTiAru59Mb/ukVlLJU0TIJ QwXJ3lxKwZfdiqs79WML02h5j6hv060pyjWKOF5FqarIukxFSqcWJ4mqRNEpVWbThFHb 38rfNU3lRm521aFfn+wmuI7loqLs82JvS7qWqOjV/qcjepmZdeYQ62T1o4Z5HKnTlmFx +/NJSB+xE7p3WUqDuUzSHV8B7RmFJ/hPyBTxx8/ilqIfhWwGTKsvG8xcApLlfb/ur9aL XaGg==
X-Received: by 10.68.59.98 with SMTP id y2mr2388089pbq.135.1375367992213; Thu, 01 Aug 2013 07:39:52 -0700 (PDT)
Received: from [130.129.67.89] (dhcp-4359.meeting.ietf.org. [130.129.67.89]) by mx.google.com with ESMTPSA id sp4sm4414509pbc.45.2013.08.01.07.39.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 07:39:51 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
From: Ralph Droms <rdroms.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
Message-Id: <6087CC54-542E-4013-91F0-80F2D930B7D1@gmail.com>
Date: Thu, 1 Aug 2013 16:15:07 +0200
To: Andy Bierman <andy@yumaworks.com>
X-Mailer: iPhone Mail (10B350)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 14:39:59 -0000

On Aug 1, 2013, at 3:30 PM, Andy Bierman <andy@yumaworks.com> wrote:

> On Thu, Aug 1, 2013 at 4:24 AM, Yoav Nir <ynir@checkpoint.com> wrote:
>>=20
>> On Aug 1, 2013, at 11:14 AM, Andy Bierman <andy@yumaworks.com> wrote:
>>=20
>>> Hi,
>>>=20
>>> Isn't it obvious why humming is flawed and raising hands works?
>>> (Analog vs. digital).  A hand is either raised or it isn't.
>>> The sum of all hands raised is comparable across tests.
>>> The sum of the amplitude of all hums is not.
>>=20
>> Hums are better as they give greater weight to people who are more vocall=
y in support (or in opposition) to the assertion.
>=20
> Please provide some evidence that a loud hum means the person is more
> committed to work on an item.
>=20
> Favoring loud humming is subject to cultural bias.

As is identifying oneself with a position by raising one's hand.  I can imag=
ine as much - my uninformed opinion would be more - cultural bias effect on a=
 show of hands as on a hum.

> Some cultures are more inclined to raise their voice than others.
> Some people have naturally louder voices than others.
> Measuring volume may introduce bias in favor of loud men and against
> soft-spoken women, for example.

And a show of hands may introduce bias against women preferring anonymity.

- Ralph

>=20
> This cultural bias is not compatible with increased inclusiveness.
>=20
>=20
> Andy
>=20
>> Research shows([1]), that the one humming loudly for acceptance, will als=
o volunteer to review and contribute code. The one humming loudly against is=
 going to jump up to the mike in all future meetings and tell the group that=
 they're doing the wrong thing. Those who hum softly will go back to reading=
 their email.
>>=20
>> Yoav
>>=20
>> [1] citation needed
>>=20

From Ted.Lemon@nominum.com  Thu Aug  1 08:01:14 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66A7821E81A8 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 08:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.234
X-Spam-Level: 
X-Spam-Status: No, score=-106.234 tagged_above=-999 required=5 tests=[AWL=-0.235, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, 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 lTPKT+go4IVl for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 08:01:07 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBB921E8150 for <ietf@ietf.org>; Thu,  1 Aug 2013 08:01:00 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUfp4LBWFd7/kvUcOb33BcqR6MbH7W1eq@postini.com; Thu, 01 Aug 2013 08:01:00 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D46C41B803D for <ietf@ietf.org>; Thu,  1 Aug 2013 08:00:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CCE1E190065; Thu,  1 Aug 2013 08:00:59 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 1 Aug 2013 08:00:59 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: 6tsch BoF
Thread-Topic: 6tsch BoF
Thread-Index: AQHOjpRUXHUCY2plmUOb4HszrvBChJmAh0KAgAAkQgCAACMzgIAAGVkA
Date: Thu, 1 Aug 2013 15:00:59 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
In-Reply-To: <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2CA028A1F7ADEE46AD101EFE983C5184@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 15:01:14 -0000

We actually had a talk about this amongst several IESG and former IESG memb=
ers.   I am not going to report the results, because I might remember them =
wrong, but my thoughts on this are as follows:

- The hum is not a means of determining consensus; it is a means of determi=
ning the sense of the room.   If the hum is clearly many in favor, nobody a=
gainst,then you have consensus, but that's unusual.   If the hum shows many=
 in favor and some against, you need to go to the next step, because you do=
 not yet know whether you have consensus.

- So since the hum was quite inconclusive, the next question is, "can someb=
ody who objects please say why."   One way to approach that is to ask for a=
 show of hands.   Here, the chairs could have asked for a show of hands aga=
inst=97the show of hands for was unnecessary.   But this is forgivable, I t=
hink, unless you think people were intimidated by the show of hands for.   =
I think that would be hard to argue, given that they had already heard the =
result of the hum.

- So the show of hands against elicited no hands.   I was there, that's wha=
t I remember seeing too.

So at this point, what do you do?   Nobody is willing to stand up and say "=
I think we shouldn't go forward with this because of X."   Many people have=
 said "we think we should go forward with this, support doing this, and wan=
t to participate."

To me, that's consensus.

That wasn't the full outcome of the BoF; there was a lot of good feedback a=
nd the charter needs work.   But it's pretty clear to me that in principle =
at least, there was consensus to do this work.

If you disagree, now would be a fine time to say so, although if in fact we=
 get a charter that the IESG decides is worth floating, you will get anothe=
r chance during the last call on the charter.


From hallam@gmail.com  Thu Aug  1 08:25:33 2013
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 1EABC21E81EB for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 08:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093,  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 3KHBYqnPDSZu for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 08:25:32 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 838C121E8195 for <ietf@ietf.org>; Thu,  1 Aug 2013 08:25:29 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id j17so6330304wiw.13 for <ietf@ietf.org>; Thu, 01 Aug 2013 08:25:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y2EtBgicL9i36tHBC3gPXoOieUjYSetsRPaWiiMPKI8=; b=Ed2OxATtT5QDF5iQejMvoO/LviUrTGbm7K95JIIKD5BAGoVE8jYkDgEzoTcotWW3zt 21LHzA+ikBKr/fCAshDzLD9X7BsJnIFwc2fNRiA/U0ytwUifm5YEQvlbb2AwxFvC7aqO TjkkzcBjN2Oi3qE//C2Yxlm19NPJm0vA+dy3o56CoacEnQSk0BwtwQUFXBubVsqmB3ff 3sbtLC3MEKcx4iqe9j/SiCtRoifMwqoH7xbnziaXDzf950LHaev5Axu2JTHcfVSn+O29 2hYa57FdBsBUHFbVNbIII0y2oPnhOASVVt2otKJG3V8+Rg4js/Ii1yeT+uidKcYHPQU2 WwYQ==
MIME-Version: 1.0
X-Received: by 10.180.183.40 with SMTP id ej8mr1612271wic.37.1375370727964; Thu, 01 Aug 2013 08:25:27 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 1 Aug 2013 08:25:27 -0700 (PDT)
In-Reply-To: <aak3k57oup.fsf@switch.ch>
References: <20130730235306.B798918C0FA@mercury.lcs.mit.edu> <aak3k57oup.fsf@switch.ch>
Date: Thu, 1 Aug 2013 11:25:27 -0400
Message-ID: <CAMm+LwiSKFTiO_mDskVFONGLaHb2MgCTio8BJQ5qO=tsBXRb0w@mail.gmail.com>
Subject: Re: Bringing back Internet transparency
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Simon Leinen <simon.leinen@switch.ch>
Content-Type: multipart/alternative; boundary=001a11c2297aacc70304e2e47360
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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, 01 Aug 2013 15:25:33 -0000

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

On Thu, Aug 1, 2013 at 5:16 AM, Simon Leinen <simon.leinen@switch.ch> wrote:

> Noel Chiappa writes:
> > But in any event, it's doesn't void my point: if people want
> > something, we have two choices: i) blow people off, and they'll adopt
> > some point solution that interacts poorly with everything else, or ii)
> > give people the _capabilities_ they need/want (and thereby have some
> > chance at minimizing the brain damage - since generally people don't
> > care _how_ it works, as long as it _does_ what they want).
>
> > I guess this is just a long-winded, engineering take on 'the customer
> > is always right'.
>
> Yes, but it's harder than that.  In the NAT case, were our (we being the
> IETF) customers the ISPs, the users (in this case "end users" who
> insisted on connecting multiple devices without going incurring the
> costs of becoming "commercial" customers), the vendors of then-current
> equipment, the vendors of potential circumvention solutions (NATs)?
>
> These groups of customers probably didn't agree on what they wanted
>

I think it was a little uglier than that.

ISPs and backbone providers were well represented in the IETF, home users,
rather less so. The ISPs had a clear interest in killing of NAT which
threatened the ISP business model.

People internalize their employers interests very easily and without
knowing that they have done so. I have an acquaintance from Oxford who
spends his time 'researching' climate change for the Koch brothers. He has
no qualifications in the field. His 'research method' is essentially the
method of Winston Smith in 1984.  But he is completely convinced that he is
a legitimate researcher and that he is right and the nobel prize winners
whose work he is misrepresenting are engaged in an international conspiracy.

So when people were trying to mau-mau me into rejecting NAT as
ideologically unsound, I had a different perspective.

It is never going to be in the customers interest to let their internetwork
provider know what their internal network looks like. Never-ever-ever. I
don't want my ISP to know because then they might sell that information to
other people and I would be getting all sorts of demands for payment.

The business logic means that it will be NAT today, NAT tomorrow and NAT
forever. Whether I am a commercial or a residential user, I am going to use
that NAT box to protect my economic interests versus my supplier. And that
will be the case regardless of how many IP addresses are available.


The IETF was originally the product of a group of people who looked at the
telephone system and could see how to do the job differently. I don't see
many people who look at the Internet in that way. The IETF has become more
like what it has replaced.

The issue is not just welcoming newcomers, it is welcoming newcomers who
can look at problems with a fresh perspective and reject ideological
approaches. And that is why I am going to continue to point out the the
governance model of the IETF is expressly designed to exclude dissident
thinkers.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Aug 1, 2013 at 5:16 AM, Simon Leinen <span dir=3D"ltr">&lt;=
<a href=3D"mailto:simon.leinen@switch.ch" target=3D"_blank">simon.leinen@sw=
itch.ch</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">Noel Chiappa writes:<br></=
div><div class=3D"im">
&gt; But in any event, it&#39;s doesn&#39;t void my point: if people want<b=
r>
&gt; something, we have two choices: i) blow people off, and they&#39;ll ad=
opt<br>
&gt; some point solution that interacts poorly with everything else, or ii)=
<br>
&gt; give people the _capabilities_ they need/want (and thereby have some<b=
r>
&gt; chance at minimizing the brain damage - since generally people don&#39=
;t<br>
&gt; care _how_ it works, as long as it _does_ what they want).<br>
<br>
&gt; I guess this is just a long-winded, engineering take on &#39;the custo=
mer<br>
&gt; is always right&#39;.<br>
<br>
</div>Yes, but it&#39;s harder than that. =A0In the NAT case, were our (we =
being the<br>
IETF) customers the ISPs, the users (in this case &quot;end users&quot; who=
<br>
insisted on connecting multiple devices without going incurring the<br>
costs of becoming &quot;commercial&quot; customers), the vendors of then-cu=
rrent<br>
equipment, the vendors of potential circumvention solutions (NATs)?<br>
<br>
These groups of customers probably didn&#39;t agree on what they wanted<br>=
</blockquote><div><br></div><div>I think it was a little uglier than that.<=
/div><div><br></div><div>ISPs and backbone providers were well represented =
in the IETF, home users, rather less so. The ISPs had a clear interest in k=
illing of NAT which threatened the ISP business model.</div>
<div><br></div><div>People internalize their employers interests very easil=
y and without knowing that they have done so. I have an acquaintance from O=
xford who spends his time &#39;researching&#39; climate change for the Koch=
 brothers. He has no qualifications in the field. His &#39;research method&=
#39; is essentially the method of Winston Smith in 1984. =A0But he is compl=
etely convinced that he is a legitimate researcher and that he is right and=
 the nobel prize winners whose work he is misrepresenting are engaged in an=
 international conspiracy.</div>
</div><br clear=3D"all"><div>So when people were trying to mau-mau me into =
rejecting NAT as ideologically unsound, I had a different perspective.</div=
><div><br></div><div>It is never going to be in the customers interest to l=
et their internetwork provider know what their internal network looks like.=
 Never-ever-ever. I don&#39;t want my ISP to know because then they might s=
ell that information to other people and I would be getting all sorts of de=
mands for payment.</div>
<div><br></div><div>The business logic means that it will be NAT today, NAT=
 tomorrow and NAT forever. Whether I am a commercial or a residential user,=
 I am going to use that NAT box to protect my economic interests versus my =
supplier. And that will be the case regardless of how many IP addresses are=
 available.</div>
<div><br></div><div><br></div><div>The IETF was originally the product of a=
 group of people who looked at the telephone system and could see how to do=
 the job differently. I don&#39;t see many people who look at the Internet =
in that way. The IETF has become more like what it has replaced.</div>
<div><br></div><div>The issue is not just welcoming newcomers, it is welcom=
ing newcomers who can look at problems with a fresh perspective and reject =
ideological approaches. And that is why I am going to continue to point out=
 the the governance model of the IETF is expressly designed to exclude diss=
ident thinkers.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2297aacc70304e2e47360--

From dhc@dcrocker.net  Thu Aug  1 08:32:48 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6319C21E81EB for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 08:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YZhbBle8-CWe for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 08:32:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CFD5921E81E0 for <ietf@ietf.org>; Thu,  1 Aug 2013 08:32:42 -0700 (PDT)
Received: from [130.129.18.235] (dhcp-12eb.meeting.ietf.org [130.129.18.235]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r71FWY5G016544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Aug 2013 08:32:39 -0700
Message-ID: <51FA7F8D.9080308@dcrocker.net>
Date: Thu, 01 Aug 2013 17:32:29 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>
In-Reply-To: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 01 Aug 2013 08:32:40 -0700 (PDT)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 15:32:48 -0000

Ralph, et al,

Perhaps I have missed relevant responses, but it appears that folk are 
missing what is significant here:


On 8/1/2013 10:50 AM, Ralph Droms wrote:
>  In particular, the effect of humming versus
> show of hands was pretty obvious.

The fact that the results were so profoundly different should get our 
attention, enough to get us to consider specifying how to measure 
consensus.  From the data you cited, it appears that raising hands 
carries some sort of social onus, at least for some people some times, 
that raising hands does not.

Perhaps that doesn't bother other folk very much but the differential 
result was so extreme -- as a single-event experiment -- it strongly 
suggests we should not call for hand-raising.  (The likely explanations 
for the difference are pretty straightforward.  Whether our community of 
engineers wants to believe the explanations or not doesn't matter  The 
data should be sufficiently compelling.)


> The other question raised in my mind is why the initial result from
> the hum, which did not have a consensus either way, was not
> sufficient.

Exactly.  This is a point of working group management that should prompt 
some concern.

It's not appropriate to throw out results that were validly obtained but 
yield unpleasant results, and then repeat the same query.  (In fact a 
repetition of a survey on the same sample population is a rank violation 
of reasonable experimental methodology.)

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From barryleiba.mailing.lists@gmail.com  Thu Aug  1 09:10:30 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9B2921E81FD for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 09:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.97
X-Spam-Level: 
X-Spam-Status: No, score=-101.97 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06N5P+sKoRjK for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 09:10:30 -0700 (PDT)
Received: from mail-vb0-x22f.google.com (mail-vb0-x22f.google.com [IPv6:2607:f8b0:400c:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E4D2921E81AB for <ietf@ietf.org>; Thu,  1 Aug 2013 09:10:01 -0700 (PDT)
Received: by mail-vb0-f47.google.com with SMTP id h10so2311965vbh.34 for <ietf@ietf.org>; Thu, 01 Aug 2013 09:09: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=RiO5LLFiiMZF1L+ixbJAtJm6oR3CDTGzUvRfQjKKE4k=; b=OnqzED7zJKTcvrIMySiAf3wVNotdwTz+EOTLS0cYSrdzmW5wVxzyYr48ld4nJpfPZW EqXP7EDOUIP/RnRTIsMNb2BNbGfFblQbo7DwdvhAvp1nGkOADy7JfLRuBMZ0Yaccz0CP R59HNhZsqd/Lk6ldqd+KbN6BIFH62RCt0qnj1Bz8AiLwrHAcWYBzJ7v4e14xUwgTeOAK Rdd1e3PJ5RT8wmt4QF7a4irJ5UKYQ/9TMiprSGx7cOFGheNtoT58QxQL+0ouPtE5O4nO rEBPLexmw696CJszNIW2uat8uJSWTCtg+5GW2MulehI1VIN5syk8pfLJBwT4mvBOGn34 d5wA==
MIME-Version: 1.0
X-Received: by 10.220.20.3 with SMTP id d3mr701556vcb.55.1375373398852; Thu, 01 Aug 2013 09:09:58 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Thu, 1 Aug 2013 09:09:58 -0700 (PDT)
In-Reply-To: <CABCOCHQrgieR-JSFwFjkZXkeOyEPG+bqxeyYt+vHHxd_w6sv5Q@mail.gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <C9EDD707-14AE-4F6D-B010-D4E60AC52BDF@isi.edu> <CABCOCHQrgieR-JSFwFjkZXkeOyEPG+bqxeyYt+vHHxd_w6sv5Q@mail.gmail.com>
Date: Thu, 1 Aug 2013 12:09:58 -0400
X-Google-Sender-Auth: 6aOI84CI5b_39tnJSIvCs4IxRA8
Message-ID: <CAC4RtVA2vEY3b9tu6x00QqD+7bLsndbi9GuBx3PvJq7SQ94LHQ@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Barry Leiba <barryleiba@computer.org>
To: Andy Bierman <andy@yumaworks.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>, manning bill <bmanning@isi.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 16:10:31 -0000

> We are not voting.
> We are expressing agreement with a specific assertion.
> That is true whether the agreement is expressed via vocalization
> or motion of limbs.

Absolutely so.

> The chairs can pick however they want to measure agreement.
> Many chairs ask for a show of hands.  I prefer that method.
> There is still a judgement call when the numbers for and against
> are not significantly different.

Just some somewhat arbitrary notes here:

There are times when I want to count hands, but it's not for a "vote".
 If I ask who will commit to working on something, I'm looking for a
critical mass that doesn't require counting... but I'm often *also*
looking for commitments, which requires both counting and
identification.

There are also times when I just want to see the relative balance.  As
Andy says, listening to hums can be dicey, even if we don't try to
second guess whether people who hum loudly have stronger opinions
and/or more enthusiasm, or are just demonstrating a cultural
difference.  But if I get a show of hands and do *not* count, I see
that relative balance better.

On the other hand, in perhaps the same situation, if it turns out that
I see only a few hands on one side of the question, I can see whom to
ask to stand up and tell us *why*, and that's often the real value of
the hums: we have a few people who object to X, and we need them to
tell us what their issues are so they can be discussed and addressed.

It drives me nuts [1] when chairs ask for a hum, hear a loud hum for A
and a weak hum for B, and then say, "OK, we have rough consensus,"
without pursuing the issue: What are the objections to A?  Do the B
people just *prefer* B, but they can live with A?  Or is A
fundamentally flawed, but only a few people understand that?

Barry

[1] Admittedly, a short drive.

From melinda.shore@gmail.com  Thu Aug  1 09:25:18 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CAF111E810D for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 09:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 E58nWkdM0cuW for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 09:25:17 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 7063E21F9DF3 for <ietf@ietf.org>; Thu,  1 Aug 2013 09:25:10 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id lb1so2305139pab.40 for <ietf@ietf.org>; Thu, 01 Aug 2013 09:25: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=FGX9oKffejwEme02N+DV/4fLopee45clstyeZKeDCiI=; b=Em+MG/QPrkwOY33xQF06UPZkLYqPI0jqfpGuFNFl78ZOYgCH4NEE3I7pO6fSODpvYu 4I2iCUb4d4/71byHoxAqr5Y2hMjr4sgs1BNha2B+c7wvtOzJ6z91ptdGwpJkaXSzd6vP ooSPondHTFPRm/ZkF9Uwf9agEB0ZvZvlP0WSTYvZ/q13+9JMOPEUi9COfxvdNRDapXCG OWX800Qu9z2BorVtumqy8Y8mbBMYLc3AHXY1pcKAA1dN+cUMlCgABrWl7BtgcYM25rhm kCLpRm3+iG//YCrM9azUft6+dJBzYXJEbLwztUWVDNxHJMQxfHtAMH3S+DZSCHVipl+A axIw==
X-Received: by 10.68.99.98 with SMTP id ep2mr3147984pbb.6.1375374310008; Thu, 01 Aug 2013 09:25:10 -0700 (PDT)
Received: from spandex.local (66-230-112-156-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.156]) by mx.google.com with ESMTPSA id sp4sm4900154pbc.45.2013.08.01.09.25.07 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 09:25:08 -0700 (PDT)
Message-ID: <51FA8BE2.90406@gmail.com>
Date: Thu, 01 Aug 2013 08:25:06 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <51FA2A70.10208@bogus.com>
In-Reply-To: <51FA2A70.10208@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 16:25:18 -0000

On 8/1/13 1:29 AM, joel jaeggli wrote:
> Consensus for any particular outcome is in the end a judgment call.

Well, yes and no, but this situation strikes me as odd, and probably
a mistake on the part of the chairs.  If you can't tell whether or
not you've got consensus, you don't have consensus.  It sounds like
they were treating the hum as a vote in the first place (which we
do entirely too often).

Melinda


From touch@isi.edu  Thu Aug  1 10:02:43 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C34121E8202 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 10:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.026
X-Spam-Level: 
X-Spam-Status: No, score=-106.026 tagged_above=-999 required=5 tests=[AWL=0.573, 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 64yjMYYNn-pO for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 10:02:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id BB39B21E8195 for <ietf@ietf.org>; Thu,  1 Aug 2013 10:02:38 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r71H1Of5009979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Aug 2013 10:01:30 -0700 (PDT)
Message-ID: <51FA9461.8090509@isi.edu>
Date: Thu, 01 Aug 2013 10:01:21 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Simon Leinen <simon.leinen@switch.ch>
Subject: Re: Bringing back Internet transparency
References: <20130730235306.B798918C0FA@mercury.lcs.mit.edu> <aak3k57oup.fsf@switch.ch>
In-Reply-To: <aak3k57oup.fsf@switch.ch>
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: 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, 01 Aug 2013 17:02:43 -0000

On 8/1/2013 2:16 AM, Simon Leinen wrote:
>> >For the first couple of years that I had an ISP connection (which soon
>> >had an early NAT box on it), whenever I called up the ISP (then, and
>> >still, one of the largest in the US) with a service call, the first
>> >thing I had to do was unplug the NAT box and plug in a host directly!
 >
> I don't think your anecdote contradicts Joe's claim.
>
> In the eyes of your ISP, you were misbehaving, because you were
> violating their assumption that you would use ONE (1) computer with that
> connection.  If you had been what they consider an honest citizen, you
> would have gotten a "commercial" connection to connect more than one.

Another data point is Google's recent reversal on network transparency 
focused on artificially differentiating between perceived "commercial" 
and "individual" customers:

http://www.listbox.com/member/archive/247/2013/07/sort/time_rev/page/1/entry/4:390/20130731102314:B16998B8-F9EC-11E2-AF78-DB9DE151F03B/

My experience has been that there are four ways ISPs try to break the 
Internet's assumption that "all nodes are equivalent" (any port, any 
time, any where, IMO), with:

	1. asymmetric BW provisioning and throttling

	2. NATs

	3. short-lease DHCP (i.e., spinning IP addrs every day or
	faster, to interfere with registering an assigned IP in the DNS)

	4. legal means

ISPs use a combination of these, but the cheapest one is NATs.

Joe

From ned+ietf@mauve.mrochek.com  Thu Aug  1 10:32:47 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCDF011E80F9 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 10:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tm3OF4KQkWer for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 10:32:43 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 4287D21E8204 for <ietf@ietf.org>; Thu,  1 Aug 2013 10:32:32 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OWP6ISRZ8G0012FD@mauve.mrochek.com> for ietf@ietf.org; Thu, 1 Aug 2013 10:27:58 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OWGOYH1YHC00004R@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 1 Aug 2013 10:26:57 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OWP6IR7LKQ00004R@mauve.mrochek.com>
Date: Thu, 01 Aug 2013 10:26:24 -0700 (PDT)
Subject: Re: stability of iana.org URLs
In-reply-to: "Your message dated Thu, 01 Aug 2013 01:10:06 -0700" <CE1FE47E.B59E%amanda.baber@icann.org>
References: <CE1FE47E.B59E%amanda.baber@icann.org>
To: Amanda Baber <amanda.baber@icann.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 17:32:47 -0000

> Hi,

> The link in RFC3315 is actually incorrect -- it should have been http://www.iana.org/assignments/enterprise-numbers, without the file extension, and there's an erratum about this. HTML was generally (if not exclusively) reserved for files that needed to include links to registration forms .

> As Barry said, we do intend to keep that same short http://www.iana.org/assignments/example format working for every current page, even the newly-created ones. We also prefer to see that format used in documents, since we can't guarantee that the file extension used for the long version won't change. (This information will be appearing on the website in some form.)


> Also, if you find that a formerly-valid URL (like one that used to have an .html exception) isn't redirecting to the current page, please report it to iana@iana.org<mailto:iana@iana.org>. A redirect should have been set up.

Excellent, thanks.

				Ned

From jnc@mercury.lcs.mit.edu  Thu Aug  1 10:39:49 2013
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 F278211E8136 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 10:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.484
X-Spam-Level: 
X-Spam-Status: No, score=-6.484 tagged_above=-999 required=5 tests=[AWL=0.115,  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 EegsM6XyYXGl for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 10:39:43 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1946D11E8131 for <ietf@ietf.org>; Thu,  1 Aug 2013 10:39:41 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id ECAE318C128; Thu,  1 Aug 2013 13:39:38 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Bringing back Internet transparency
Message-Id: <20130801173938.ECAE318C128@mercury.lcs.mit.edu>
Date: Thu,  1 Aug 2013 13:39:38 -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, 01 Aug 2013 17:39:49 -0000

    > From: Simon Leinen <simon.leinen@switch.ch>

    > In the eyes of your ISP, you were misbehaving, because you were
    > violating their assumption that you would use ONE (1) computer with that
    > connection.  If you had been what they consider an honest citizen, you
    > would have gotten a "commercial" connection to connect more than one.

I suspect it had a lot more to do with their customer service setup; they were
not, after all, hiring computer scientists. They worked off scripts, and the
script needed a known quantity connected to the port (I would guess the only
handled Windows boxes and Apple machines). With 7 different kinds of Brand-X
NAT boxes (some of which had limited maintainence capabilities), their scripts
would not have worked.

Besides, they had other ways to sort out the commercial from residential
customers; for one, they filtered out incoming SMTP connections (although this
might have been as much to prevent clueless home users from being spam vectors
by running open relays, etc as anything else). I would assume they filtered
out incoming HTTP connections too.

Don't forget, in some ways a NAT box probably works _against_ an ISP's
interests, because they'd probably _like_ to be able to charge for each
machine connected up. (Many cable TV suppliers try to charge for multiple TVs,
don't forget). But I suspect the difficulty of connecting multiple machines
_without_ a NAT box (you've got to have a real router, and configure it, etc),
and its attendant increase in customer service costs (not to mention the
increased demand for address space), led them to throw up their hands.

Anway, this is all just speculation on our part. IMO, further discussion
without some real data on how the ISPs saw this is just a waste of time.


    >> I guess this is just a long-winded, engineering take on 'the customer
    >> is always right'.

    > were our (we being the IETF) customers the ISPs, the users .., the
    > vendors of then-current equipment, the vendors of potential
    > circumvention solutions (NATs)?
    > These groups of customers probably didn't agree on what they wanted.
    > Were all of them right?

Excellent point. Have to go away and ponder that one for a while.

	  Noel

From sm@resistor.net  Thu Aug  1 11:27:58 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A44611E80D7 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 11:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MsqGzhXqaQx2 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 11:27:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 714C511E80D5 for <ietf@ietf.org>; Thu,  1 Aug 2013 11:27: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 r71IReFC012600; Thu, 1 Aug 2013 11:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375381665; bh=Jsm8l9r37A4BySAlQE6WsvzljQk0JipDUdGVC8sbHts=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CsrX/papaDHwLiQbzn8v6mO0kq8QTgUDdqYiFor8K0tuIaAtStsLcM0lLFuPFkDTH 8ICz8afCIV4/sLY1r6OZStFQaD3sXBveAmOc/bBYkICkDPUNt1KFCHIkvnCsibKvU5 IuvLMHDxoNi8JgB0PSt/x8liQ1907wgWH4CaFluM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375381665; i=@resistor.net; bh=Jsm8l9r37A4BySAlQE6WsvzljQk0JipDUdGVC8sbHts=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=t/kW4E6tPE/PqqVIBdAPSY8sE8BFRyohqxsfv+n3j3tleYqyWlo/U1NFVsYWu4xRX xt/7b8exb+ghW5ztuM/JlUl60kwsRv4cfc2aHF2R+4KVn8DPuq7KA4JZFPpFoacDOE QRK+XdGbVgk+TeCxGMMhcqU2fp6T/zCMhfA3DF0Y=
Message-Id: <6.2.5.6.2.20130801100640.0ccf1a80@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Aug 2013 11:26:57 -0700
To: Andy Bierman <andy@yumaworks.com>
From: SM <sm@resistor.net>
Subject: Protecting the disclosure of the identity (was: Loud humming is subject to cultural bias)
In-Reply-To: <CABCOCHRC_wS55fnd-ypXMOb+vaJKN6SfzrrRsVcJBSHykgoJiQ@mail.g mail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <6.2.5.6.2.20130801075701.0d1d3398@resistor.net> <CABCOCHSadV_=Z9crk1paXeZXQm_ROKSQr-irAbSbwKyRZ3W5zg@mail.gmail.com> <6.2.5.6.2.20130801085913.0d161b80@resistor.net> <CABCOCHRC_wS55fnd-ypXMOb+vaJKN6SfzrrRsVcJBSHykgoJiQ@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, 01 Aug 2013 18:27:58 -0000

Hi Andy,
At 09:26 01-08-2013, Andy Bierman wrote:
>I meant that it is difficult to remain anonymous when the
>email to the WG has your email address in it.

Agreed.

>Perhaps you can point me to the RFC 2026 text (or other RFC)
>that says something about protecting the disclosure of the identity
>of the person expressing agreement or disagreement with
>some question asked in a WG meeting.

I read RFC 2026 quickly.  I did not find any text about protecting 
the disclosure of the identity of a person.  I read another RFC which 
was about a WG meeting.  It states that there are requirements for 
disclosure of conflicts of interest.  I did not find any text about 
protecting the disclosure of the identity of the person.

Regards,
-sm 


From jhutz@cmu.edu  Thu Aug  1 11:50:30 2013
Return-Path: <jhutz@cmu.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 A15CB11E80F9 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 11:50:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8O4hTIoSu0KX for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 11:50:25 -0700 (PDT)
Received: from smtp02.srv.cs.cmu.edu (SMTP02.SRV.CS.CMU.EDU [128.2.217.197]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE0211E80A2 for <ietf@ietf.org>; Thu,  1 Aug 2013 11:50:21 -0700 (PDT)
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp02.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id r71ImEfb027076 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 1 Aug 2013 14:48:14 -0400 (EDT)
Message-ID: <1375382894.23365.553.camel@minbar.fac.cs.cmu.edu>
Subject: Re: stability of iana.org URLs
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Amanda Baber <amanda.baber@icann.org>
Date: Thu, 01 Aug 2013 14:48:14 -0400
In-Reply-To: <21265_1375344641_r718AdfO023164_CE1FE47E.B59E%amanda.baber@icann.org>
References: <21265_1375344641_r718AdfO023164_CE1FE47E.B59E%amanda.baber@icann.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3-0ubuntu6 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Scanned-By: mimedefang-cmuscs on 128.2.217.197
Cc: "ietf@ietf.org" <ietf@ietf.org>, jhutz@cmu.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, 01 Aug 2013 18:50:30 -0000

On Thu, 2013-08-01 at 01:10 -0700, Amanda Baber wrote:
> Hi,
> 
> The link in RFC3315 is actually incorrect -- it should have been
> http://www.iana.org/assignments/enterprise-numbers, without the file
> extension, and there's an erratum about this. HTML was generally (if
> not exclusively) reserved for files that needed to include links to
> registration forms .

Nonetheless, it's an existing URL in an immutable published RFC.  Once
such a thing has been published, right or wrong, best practice is to
make sure it remains valid.


From jnc@mercury.lcs.mit.edu  Thu Aug  1 12:14:47 2013
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 319C911E8137 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 12:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.106,  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 WsQZX3e5QmD8 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 12:14: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 0280D11E8131 for <ietf@ietf.org>; Thu,  1 Aug 2013 12:14:41 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C027718C183; Thu,  1 Aug 2013 15:14:38 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Bringing back Internet transparency
Message-Id: <20130801191438.C027718C183@mercury.lcs.mit.edu>
Date: Thu,  1 Aug 2013 15:14:38 -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, 01 Aug 2013 19:14:47 -0000

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

    > The ISPs had a clear interest in killing of NAT which threatened the
    > ISP business model.

So this is rather amusing: you're trying to tell me that ISPs wanted to kill
NAT, and I have other people telling me NAT was an intergral part of ISPs'
master plan to take over the universe.

Clearly you all both can't be right.

	Noel

From brian.e.carpenter@gmail.com  Thu Aug  1 13:54:36 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D6E11E8164 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 13:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.069
X-Spam-Level: 
X-Spam-Status: No, score=-100.069 tagged_above=-999 required=5 tests=[AWL=-2.470, BAYES_00=-2.599, GB_SUMOF=5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JRdt+fxq3NjG for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 13:54:36 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 745B911E815C for <ietf@ietf.org>; Thu,  1 Aug 2013 13:54:24 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kq13so2559362pab.25 for <ietf@ietf.org>; Thu, 01 Aug 2013 13:54:23 -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=SflEub4feVJtdENzb+sEW8L0MP7BSMb+Jt2SfAHmXzo=; b=b/6gSAsHIGJrDlhhLGNLmLMejvbSYAhlpxlzBfWU8QAl+vqg90qEyX64e817Qcn6aF JXAfeRCTaivB1Wc5t281O5ymrMOFF+liJ1DZo88ek0qxzuiYIJDto5wcD3uhvPeKJ0j5 IdzCmr9qVxe01hNKzFiVmXgwHlWu1TWX+W2OHBj8Myz3Pk+PVbYsdHi0BbRI3GwRu3i9 otcL24gva2tceo6/SbBnyK5Zgbwd/5LFDNakXgVt7zC957ig5I9Yf40IK1Zs2RhDYt5I JqGrTKewCQpPEvFXKELY43JzKQhKd5hnfAycS/Qy6L6EaxZAAOj5jh1WHsCcUX6k944F SxHg==
X-Received: by 10.66.5.195 with SMTP id u3mr6441056pau.79.1375390463120; Thu, 01 Aug 2013 13:54:23 -0700 (PDT)
Received: from [192.168.178.23] (107.199.69.111.dynamic.snap.net.nz. [111.69.199.107]) by mx.google.com with ESMTPSA id dg3sm5909862pbc.24.2013.08.01.13.54.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 13:54:22 -0700 (PDT)
Message-ID: <51FACB07.7060806@gmail.com>
Date: Fri, 02 Aug 2013 08:54:31 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>	<CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>	<B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
In-Reply-To: <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 20:54:37 -0000

On 02/08/2013 01:30, Andy Bierman wrote:
> On Thu, Aug 1, 2013 at 4:24 AM, Yoav Nir <ynir@checkpoint.com> wrote:
>> On Aug 1, 2013, at 11:14 AM, Andy Bierman <andy@yumaworks.com> wrote:
>>
>>> Hi,
>>>
>>> Isn't it obvious why humming is flawed and raising hands works?
>>> (Analog vs. digital).  A hand is either raised or it isn't.
>>> The sum of all hands raised is comparable across tests.
>>> The sum of the amplitude of all hums is not.
>> Hums are better as they give greater weight to people who are more vocally in support (or in opposition) to the assertion.
>>
> 
> Please provide some evidence that a loud hum means the person is more
> committed to work on an item.

I spotted a number of virtual :-)s in Yoav's message.

The fact is that both methods are broken. A loud hum may indeed
represent strength of feeling, which in judging consensus is
valuable input. Or it may represent chance (some people naturally
hum louder) or a cultural split in opinion. So it's fairly
meaningless. A lot of hands up may indicate that a couple of
employers have loaded the room.

One can make a case that we shouldn't use either method: just
go by the arguments made in the room and on the list.

In the case of a WG-forming BOF, it seems to me that a nucleus
of people willing and competent to do the work, and a good set of
arguments why the work needs to be done and how it will make the
Internet better, are more important than any kind of numbers game.

  Brian


From brian.e.carpenter@gmail.com  Thu Aug  1 14:09:27 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1725121E822C for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 14:09:27 -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 LxDMP9P9jfqL for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 14:09:12 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 173A221F8A67 for <ietf@ietf.org>; Thu,  1 Aug 2013 14:08:06 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so2062039pbb.28 for <multiple recipients>; Thu, 01 Aug 2013 14:07: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 :subject:content-type:content-transfer-encoding; bh=O2Etm9eu0jaHDI90DMMCqjSHXazLJtRaCbbQOelCI8Y=; b=aCAMlXgblNpmGNegDdn1jEHkDTnCvc6LUWXMszomvQESBD0x48rAsTMxmI0LKv7kOV R5/AN6SqXZ0Ed/FOgVDP0tD2iIzygU2NN0Bm/GHEMq2RNvLJtBqgYdPVO9oVvFqvRn7J 9AeCrKrUOIZh/L4lxVSblS++GlbU7vHqSI6r6IK6PrL31+WI3QDMprtgWU2IAs3elN34 TDRy3R5IPgyMfmuSFWZwIx5dyJWfoPr5WxhhIj/GISfKAvnjLdQKderPK/7nwew2bfDL pw6Rhu2+w9PM1ROHc4PsTGJldEbyTmp+piAy15qZrMzJN4ishyAfl/k0EzmruipKCtxN X/YQ==
X-Received: by 10.66.160.3 with SMTP id xg3mr6732893pab.28.1375390786506; Thu, 01 Aug 2013 13:59:46 -0700 (PDT)
Received: from [192.168.178.23] (107.199.69.111.dynamic.snap.net.nz. [111.69.199.107]) by mx.google.com with ESMTPSA id qh10sm5916977pbb.33.2013.08.01.13.59.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 13:59:45 -0700 (PDT)
Message-ID: <51FACC4A.4020307@gmail.com>
Date: Fri, 02 Aug 2013 08:59:54 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Trustees <trustees@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: The Trust Agreement
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, 01 Aug 2013 21:09:27 -0000

Hi,

Re the Trust's plenary slides (I was not in Berlin):

I have an allergy to modifying the Trust Agreement unless there's an
overwhelming reason to do so. It was a very hard-won piece of text.

> Issue #1
> We have recently been asked permission to
> republish the TAO with a creative commons
> license, but unfortunately the current trust
> agreement does not give the trustees the
> rights to do this

It doesn't? You have the right to license "existing and future
intellectual property" according to clause 2.1 of the Trust Agreement.
Is there some particular property of the CC license that causes a
problem?

> Issue #2
> We cannot currently accept physical assets
> like hardware donations into the trust
> Once accepted into the trust, we would be unable
> to dispose of these items in the future if they are
> identified as no longer being needed

It was definitely intended that the Trust would only handle
intellectual property, and that ISOC on behalf of IASA would handle
money and material property. Why change this?

(I'm not quite sure why the Trust Agreement included the words
"and other property" in the first place. It was there from a very
early draft and was never discussed, as far as I can tell from my
2005 email archive.)

> Issue #3
> Once a domain name or trademark is
> registered by the trust, it cannot be
> abandoned even if it is no longer needed
> We must maintain these in perpetuity

IANAL, but it isn't clear to me that clause 9.4 forces you to do this.
It requires you to "take reasonable steps" and to file applications "as
the Trustees deem necessary in order to maintain and protect the Trust
Assets." If you decide (and minute) that it isn't reasonable or necessary
to maintain veryolddomainname.org, where's the crime?

    Brian










From marka@isc.org  Thu Aug  1 18:24:16 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF6811E82EC for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78-zdz3z2MsT for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:23:59 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id DB66111E83FE for <ietf@ietf.org>; Thu,  1 Aug 2013 17:21:52 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id A8026C9484; Fri,  2 Aug 2013 00:21:39 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1375402912; bh=Qg8r+P9esy0hFn4Kudf1rI0SuYftnpyhzZftUdg4mGM=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=Fr9Z6k2O+bqspPjRvkmxerraUwDvPEIuOFnHLPLrpbQNdPKzstB0QFr81UZChE8zm HT2x/6RVtJTlUZ5tYOb859F0mXvFmy+TlfjeL8YE+16dsBQsO11ZvxmBLL6kJqlt2h VlteyCOWIk/pwNPcfnzutdA1n1P2Fg/jspJ8Jyp0=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Fri,  2 Aug 2013 00:21:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 5D142160303; Fri,  2 Aug 2013 00:25:31 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id xMEV_h3cnw-8; Fri,  2 Aug 2013 00:25:31 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id F0185160306; Fri,  2 Aug 2013 00:25:30 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id B7339160305; Fri,  2 Aug 2013 00:25:30 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 0439237EE6EF; Fri,  2 Aug 2013 10:21:32 +1000 (EST)
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
From: Mark Andrews <marka@isc.org>
References: <20130801191438.C027718C183@mercury.lcs.mit.edu>
Subject: Re: Bringing back Internet transparency
In-reply-to: Your message of "Thu, 01 Aug 2013 15:14:38 -0400." <20130801191438.C027718C183@mercury.lcs.mit.edu>
Date: Fri, 02 Aug 2013 10:21:32 +1000
Message-Id: <20130802002133.0439237EE6EF@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 01:24:17 -0000

In message <20130801191438.C027718C183@mercury.lcs.mit.edu>, Noel Chiappa write
s:
>     > From: Phillip Hallam-Baker <hallam@gmail.com>
> 
>     > The ISPs had a clear interest in killing of NAT which threatened the
>     > ISP business model.
> 
> So this is rather amusing: you're trying to tell me that ISPs wanted to kill
> NAT, and I have other people telling me NAT was an intergral part of ISPs'
> master plan to take over the universe.
> 
> Clearly you all both can't be right.

They want the extra dollars for extra address but the don't want
the support costs that would bring.  They sit at different points
for different sets of customers.

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

From melinda.shore@gmail.com  Thu Aug  1 18:34:01 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6406121E82D7 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ho+4y5eUOoA4 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:33:54 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id D4F4C11E843B for <ietf@ietf.org>; Thu,  1 Aug 2013 17:38:33 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id lb1so46582pab.26 for <ietf@ietf.org>; Thu, 01 Aug 2013 17:38:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=HnS42NMNA4HZJR4JtCzUIrjl2cMNJvA4NDtUvI9+ygA=; b=qGtf3HJXnZzFk7aQMZuGXqNsB/leBVh0xJBzqYW6FUrZivlLgTyECasg+IFJtEDe7C GOe4wDmQCHgi1Ko0r9zyipkuvY1TugCyOQeoXVw9KB5ELYJAEW5BX3QN2s//9qHgvqEP bZnBgBtEP1Pz3tk03W44aabyH658YqBR5eeOhZH8JUAbYSUi7iwH2MSbwglTj+aPysih B8XEJo1eUUlWuNauXEEJYWzeUb5afjU6zrvgQAHZ6oPIMylzdEVEsQtygTIWdiv4nPx1 DcqwpCn0P2Sclg7gHCQmG8Gw+nxfB9iBD25X8TR2rcLy7eU7ef05DeoP78AqoXZzzaJU EzGg==
X-Received: by 10.66.241.99 with SMTP id wh3mr7251768pac.141.1375403913516; Thu, 01 Aug 2013 17:38:33 -0700 (PDT)
Received: from spandex.local (66-230-112-156-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.156]) by mx.google.com with ESMTPSA id ht5sm6657413pbb.29.2013.08.01.17.38.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 Aug 2013 17:38:32 -0700 (PDT)
Message-ID: <51FAFF86.4010205@gmail.com>
Date: Thu, 01 Aug 2013 16:38:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>	<CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>	<B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <51FACB07.7060806@gmail.com>
In-Reply-To: <51FACB07.7060806@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: Fri, 02 Aug 2013 01:34:01 -0000

On 8/1/13 12:54 PM, Brian E Carpenter wrote:
> In the case of a WG-forming BOF, it seems to me that a nucleus
> of people willing and competent to do the work, and a good set of
> arguments why the work needs to be done and how it will make the
> Internet better, are more important than any kind of numbers game.

Yes, and "Who here is planning on contributing to
this effort if we're chartered?" is an entirely different
question from "Who here thinks we should charter a
working group?"

Finding consensus is not simply a matter of asking
a particular question at a given point in time.  It's
a process.  I cannot recommend strongly enough that
people spend time with Pete's document:
http://datatracker.ietf.org/doc/draft-resnick-on-consensus/

Melinda


From hallam@gmail.com  Thu Aug  1 18:36:52 2013
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 EBDCC21E82F9 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:36:51 -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, 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 Rk+IpOEdmBaC for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 18:36:39 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id CE80211E8281 for <ietf@ietf.org>; Thu,  1 Aug 2013 17:44:12 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id j17so29355wiw.11 for <ietf@ietf.org>; Thu, 01 Aug 2013 17:44: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=4dicrt5XXc5vbYCE8C1MTbDo3NIcKu5v5K3Ds95KWY0=; b=ifP81VM6C/RKF6KE0JpWEqGIHa8ajSyAmLRw9NvkLTgSlZ8d4iVVIzTlczkoJvXJVs 7LjmJYIr72Q02PWyA/bNND8MuuHVNjuK+Z/L47C/ZGy6zuf95Z6rBjoUIDYf2lIC9HWT sCPPAY7EdxiRPqwv4aM4np9ah+3B/CSMf8QrXF/zUAV/JCKrqbQbh3T/nes4ROdVTkWS IGu+YtBlbgalvyJ5as9hV5VupGeSXKxThssRHEHBy0UE7Nf67wJ3oii4WEuPee2DSgGm Lw7EpM9VYkh5w4mAM1p2yb5BdziPQvruzs/eY3JV1TBbm8y+Jn8+JhOQpAqcxXP2Zrgy TPmQ==
MIME-Version: 1.0
X-Received: by 10.180.182.229 with SMTP id eh5mr103413wic.63.1375404251956; Thu, 01 Aug 2013 17:44:11 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 1 Aug 2013 17:44:11 -0700 (PDT)
In-Reply-To: <20130801191438.C027718C183@mercury.lcs.mit.edu>
References: <20130801191438.C027718C183@mercury.lcs.mit.edu>
Date: Thu, 1 Aug 2013 20:44:11 -0400
Message-ID: <CAMm+LwjAY7OLF19-7=fJNYmH0q=MMKhrPJ7oOtMtTHaabWAL0Q@mail.gmail.com>
Subject: Re: Bringing back Internet transparency
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=089e0163491edc4cb404e2ec4129
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, 02 Aug 2013 01:36:52 -0000

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

On Thu, Aug 1, 2013 at 3:14 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

>     > From: Phillip Hallam-Baker <hallam@gmail.com>
>
>     > The ISPs had a clear interest in killing of NAT which threatened the
>     > ISP business model.
>
> So this is rather amusing: you're trying to tell me that ISPs wanted to
> kill
> NAT, and I have other people telling me NAT was an intergral part of ISPs'
> master plan to take over the universe.
>
> Clearly you all both can't be right.
>

Not at all. It is entirely possible for them to be telling everyone else
not to use NAT because it is 'evul' while planning to deploy and use it
themselves.

In practice the two positions were separated in time by many years as my
ISP allowed me to use NAT ten years back and my current ISP actually
requires me to use a NAT box as the NAT capability is built into my cable
modem.


On the network neutrality thing, I think the arguments on both sides as
specious. The fundamental issue is whether ISPs will be permitted to
leverage local monopolies on the provision of broadband services to
establish monopolies in network services that depend on those monopoly
services.

Some people have ideological blinkers that tell them that the free market
solves all problems and since the markets in the US are free (they must be
because it says so in the constitution) there can be no monopoly issue.
Markets are not perfect, people need to get over that.

It seems reasonable to me that any party that has a local monopoly in
providing broadband services has to be regulated up the pattottie and the
same is true if the number of providers is effectively constrained. Network
neutrality is just a fix for a market failure situation.

If an ISP wants to have a pricing model where I get my 1x Internet
connection for $X but Sony can stream an HD movie to me at 10x by paying to
temporarily up my connection, that seems perfectly fine to me. If on the
other hand I am paying $Y for that 10x connection then the ISP has no
business demanding a double dip from Sony or whoever.

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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Aug 1, 2013 at 3:14 PM, Noel Chiappa <span dir=3D"ltr">&lt;=
<a href=3D"mailto:jnc@mercury.lcs.mit.edu" target=3D"_blank">jnc@mercury.lc=
s.mit.edu</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">=A0 =A0 &gt; From: Phillip Hallam-Baker &lt;=
<a href=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt;<br>
<div class=3D"im"><br>
=A0 =A0 &gt; The ISPs had a clear interest in killing of NAT which threaten=
ed the<br>
=A0 =A0 &gt; ISP business model.<br>
<br>
</div>So this is rather amusing: you&#39;re trying to tell me that ISPs wan=
ted to kill<br>
NAT, and I have other people telling me NAT was an intergral part of ISPs&#=
39;<br>
master plan to take over the universe.<br>
<br>
Clearly you all both can&#39;t be right.<br></blockquote><div><br></div><di=
v>Not at all. It is entirely possible for them to be telling everyone else =
not to use NAT because it is &#39;evul&#39; while planning to deploy and us=
e it themselves.</div>
<div><br></div><div>In practice the two positions were separated in time by=
 many years as my ISP allowed me to use NAT ten years back and my current I=
SP actually requires me to use a NAT box as the NAT capability is built int=
o my cable modem.</div>
<div><br></div><div><br></div><div>On the network neutrality thing, I think=
 the arguments on both sides as specious. The fundamental issue is whether =
ISPs will be permitted to leverage local monopolies on the provision of bro=
adband services to establish monopolies in network services that depend on =
those monopoly services. =A0</div>
</div><div><br></div><div>Some people have ideological blinkers that tell t=
hem that the free market solves all problems and since the markets in the U=
S are free (they must be because it says so in the constitution) there can =
be no monopoly issue. Markets are not perfect, people need to get over that=
.</div>
<div><br></div><div>It seems reasonable to me that any party that has a loc=
al monopoly in providing broadband services has to be regulated up the patt=
ottie and the same is true if the number of providers is effectively constr=
ained. Network neutrality is just a fix for a market failure situation.</di=
v>
<div><br></div><div>If an ISP wants to have a pricing model where I get my =
1x Internet connection for $X but Sony can stream an HD movie to me at 10x =
by paying to temporarily up my connection, that seems perfectly fine to me.=
 If on the other hand I am paying $Y for that 10x connection then the ISP h=
as no business demanding a double dip from Sony or whoever.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--089e0163491edc4cb404e2ec4129--

From john-ietf@jck.com  Thu Aug  1 19:38:17 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BFBB21E82E8; Thu,  1 Aug 2013 19:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ovQKRPj60nPp; Thu,  1 Aug 2013 19:38:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8E421E8349; Thu,  1 Aug 2013 19:23:33 -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 1V551d-000NW9-Nh; Thu, 01 Aug 2013 22:23:29 -0400
Date: Thu, 01 Aug 2013 22:23:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Trustees <trustees@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: The Trust Agreement
Message-ID: <2E71568ACE1E80FB6F7BB1DD@JcK-HP8200.jck.com>
In-Reply-To: <51FACC4A.4020307@gmail.com>
References: <51FACC4A.4020307@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: Fri, 02 Aug 2013 02:38:17 -0000

FWIW, I share Brian's concern and reasoning about these
questions (and his allergy).   I might have a lower threshold of
necessity as a requirement for changing the agreement, but I'm
not convinced -- from either the slide or what I could hear of
the audio-- that it is necessary.

   john


--On Friday, August 02, 2013 08:59 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Hi,
> 
> Re the Trust's plenary slides (I was not in Berlin):
> 
> I have an allergy to modifying the Trust Agreement unless
> there's an overwhelming reason to do so. It was a very
> hard-won piece of text.
>...


From James.H.Manger@team.telstra.com  Thu Aug  1 21:49:10 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD3A11E81BE for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 21:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.419
X-Spam-Level: 
X-Spam-Status: No, score=-0.419 tagged_above=-999 required=5 tests=[AWL=0.482,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vpmi5vDKzXd for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 21:48:54 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 883A611E81CF for <ietf@ietf.org>; Thu,  1 Aug 2013 21:48:54 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,798,1367935200"; d="scan'208";a="150380820"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 02 Aug 2013 14:48:53 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7154"; a="153833343"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipcbni.tcif.telstra.com.au with ESMTP; 02 Aug 2013 14:48:49 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Fri, 2 Aug 2013 14:48:49 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: IETF Discussion <ietf@ietf.org>
Date: Fri, 2 Aug 2013 14:48:47 +1000
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Index: Ac6O0XZOfE87L5d8QPuKdyzMxfiPsAAaVrzQ
Message-ID: <255B9BB34FB7D647A506DC292726F6E115281CEEC1@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 04:49:10 -0000

ZHJhZnQtYm9ybWFubi1jYm9yLTA0IGFkZHMgdGV4dCBhYm91dCBoYW5kbGluZyBtYXBzIHdpdGgg
bXVsdGlwbGUgaWRlbnRpY2FsIGtleXMuLCBidXQgaXQgaXMgY29udHJhZGljdG9yeS4gU2VjdGlv
biAzLjQuICJTcGVjaWZ5aW5nIEtleXMgZm9yIE1hcHMiIHNheXM6DQoNCiAgIEEgQ0JPUi1iYXNl
ZCBwcm90b2NvbCBzaG91bGQgbWFrZSBhbiBpbnRlbnRpb25hbCBkZWNpc2lvbiBhYm91dCB3aGF0
DQogICB0byBkbyB3aGVuIGEgcmVjZWl2aW5nIGFwcGxpY2F0aW9uIHNlZXMgbXVsdGlwbGUgaWRl
bnRpY2FsIGtleXMgaW4gYQ0KICAgbWFwLiAgQSBwcm90b2NvbCBtaWdodCBoYXZlIGEgcnVsZSB0
aGF0IGl0IGlzIG5vdCBhbiBlcnJvciB0byBoYXZlDQogICBpZGVudGljYWwga2V5cyBpbiBhIG1h
cCwgYW5kIHRoYXQgdGhlIHJlY2VpdmluZyBhcHBsaWNhdGlvbiB3aWxsDQogICBkaXNjYXJkIGFs
bCBidXQgdGhlIGxhc3Qga2V5L3ZhbHVlIHBhaXIgZm9yIGEgZ2l2ZW4ga2V5IGluIGEgbWFwLg0K
DQogICAuLi4NCg0KICAgVGhlIENCT1IgZGF0YSBtb2RlbCBmb3IgbWFwcyBkb2VzIG5vdCBhbGxv
dyBhc2NyaWJpbmcgc2VtYW50aWNzIHRvDQogICB0aGUgb3JkZXIgb2YgdGhlIGtleS92YWx1ZSBw
YWlycyBpbiB0aGUgbWFwIHJlcHJlc2VudGF0aW9uLiAgQSBDQk9SLQ0KICAgYmFzZWQgcHJvdG9j
b2wgTVVTVCBOT1QgYmUgZGVmaW5lZCBpbiBzdWNoIGEgd2F5IHRoYXQgY2hhbmdpbmcgdGhlDQog
ICBrZXkvdmFsdWUgcGFpciBvcmRlciBpbiBhIG1hcCB3b3VsZCBjaGFuZ2UgdGhlIHNlbWFudGlj
cywgYXBhcnQgZnJvbQ0KICAgdHJpdmlhbCBhc3BlY3RzIChjYWNoZSB1c2FnZSBldGMuKS4NCg0K
DQpBIHByb3RvY29sIHRoYXQgc2F5cyAiZGlzY2FyZCBhbGwgYnV0IHRoZSBsYXN0IGtleS92YWx1
ZSBwYWlyIGZvciBhIGdpdmVuIGtleSIgZG9lcyBjaGFuZ2Ugc2VtYW50aWNzIGlmIHRoZSBrZXkv
dmFsdWUgcGFpciBvcmRlciBpcyBjaGFuZ2VkIHNvIGl0IHZpb2xhdGVzIHRoZSB0ZXh0IHNheWlu
ZyB0aGlzICJNVVNUIE5PVCIgaGFwcGVuLg0KDQpHaXZlbiB0aGVyZSBpcyBubyBsZWdhY3kgQ0JP
UiBkYXRhIHRvIG1haW50YWluIGJhY2t3YXJkIGNvbXBhdGliaWxpdHkgd2l0aCwgdGhlIHNwZWMg
c2hvdWxkIGJlIGNsZWFyZXIgdGhhdCBhIG1hcCB3aXRoIG11bHRpcGxlIGlkZW50aWNhbCBrZXlz
IGlzIGFsd2F5cyBhbiBlcnJvci4gRGlzY2FyZGluZyBhbGwgYnV0IHRoZSBsYXN0IHBhaXIgZm9y
IGEgZ2l2ZW4ga2V5IGlzIE5PVCBhY2NlcHRhYmxlIGJlaGF2aW91ciBmb3IgYSBwYXJzZXIuIEEg
bm90ZSB0aGF0IGEgc3RyZWFtaW5nIHBhcnNlciBtaWdodCBub3QgYmUgYWJsZSB0byBkZXRlY3Qg
ZHVwbGljYXRlcyBpcyBvaywgYWNjb21wYW5pZWQgYnkgYSB3YXJuaW5nIHRoYXQgYW4gYXBwbGlj
YXRpb24gdXNpbmcgc3VjaCBhIHBhcnNlciB3aWxsIG5lZWQgaXRzIG93biBjaGVja3MgZm9yIG11
bHRpcGxlIGlkZW50aWNhbCBrZXlzIHRvIGF2b2lkIHVuYW1iaWd1b3VzIG1lc3NhZ2VzLg0KDQpT
dWdnZXN0aW9uOg0KDQpEZWxldGUgdGhlIHdob2xlIHBhcmFncmFwaCBzdGFydGluZyAiQSBDQk9S
LWJhc2VkIHByb3RvY29sIHNob3VsZCBtYWtlIGFuIGludGVudGlvbmFsIGRlY2lzaW9uIi4NCg0K
QWZ0ZXIgdGhlIHNlbnRlbmNlICJUaGUgQ0JPUiBkYXRhIG1vZGVsIGZvciBtYXBzIGFsbG93cyB6
ZXJvIG9yIG9uZSBlbnRyaWVzIGluIHRoZSBtYXAgZm9yIGVhY2ggc3BlY2lmaWMga2V5IiwgYWRk
IHRoZSBmb2xsb3dpbmcgc2VudGVuY2VzOg0KDQogICBDb25zZXF1ZW50bHksIGEgbWFwIGluIHdo
aWNoIGEgc3BlY2lmaWMga2V5IGFwcGVhcnMgbXVsdGlwbGUgdGltZXMgaXMgbm90DQogICBhIHZh
bGlkIENCT1IgdmFsdWUuIEEgcGFyc2VyIE1VU1QgTk9UIGFjY2VwdCBzdWNoIGEgbWFwIGJ5IGtl
ZXBpbmcganVzdA0KICAgb25lIGVudHJ5IGZvciBhbiBvZmZlbmRpbmcga2V5Lg0KDQoNClR5cG86
IHMvZm9yIGVhY2ggYSBzcGVjaWZpYyBrZXkvZm9yIGVhY2ggc3BlY2lmaWMga2V5Lw0KDQotLQ0K
SmFtZXMgTWFuZ2VyDQoNCg==

From narten@us.ibm.com  Thu Aug  1 21:53:19 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B58F11E81F3 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 21:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pyt1rdLNTUDg for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 21:53:11 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 97CD011E8104 for <ietf@ietf.org>; Thu,  1 Aug 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 2 Aug 2013 00:53:06 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 2 Aug 2013 00:53:05 -0400
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 8023E6E803A for <ietf@ietf.org>; Fri,  2 Aug 2013 00:52:59 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r724r4ev38273234 for <ietf@ietf.org>; Fri, 2 Aug 2013 00:53:04 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r724r4n5002400 for <ietf@ietf.org>; Fri, 2 Aug 2013 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r724r39X002379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 2 Aug 2013 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r724r3JG006512 for <ietf@ietf.org>; Fri, 2 Aug 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r724r3O8006473 for ietf@ietf.org; Fri, 2 Aug 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201308020453.r724r3O8006473@rotala.raleigh.ibm.com>
Date: Fri, 02 Aug 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13080204-7182-0000-0000-000007F21106
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 04:53:19 -0000

Total of 222 messages in the last 7 days.
 
script run at: Fri Aug  2 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.95% |   11 |  7.45% |   129461 | abdussalambaryun@gmail.com
  5.41% |   12 |  6.26% |   108812 | moore@network-heretics.com
  4.95% |   11 |  4.51% |    78362 | sm@resistor.net
  4.50% |   10 |  4.72% |    82029 | brian.e.carpenter@gmail.com
  3.60% |    8 |  5.15% |    89569 | hallam@gmail.com
  4.05% |    9 |  3.58% |    62145 | john-ietf@jck.com
  4.05% |    9 |  3.54% |    61529 | arturo.servin@gmail.com
  4.05% |    9 |  3.39% |    58959 | melinda.shore@gmail.com
  3.60% |    8 |  2.83% |    49207 | jari.arkko@piuha.net
  1.80% |    4 |  3.79% |    65923 | leaf.yeh.sdo@gmail.com
  3.15% |    7 |  2.10% |    36449 | jnc@mercury.lcs.mit.edu
  2.70% |    6 |  2.50% |    43444 | ynir@checkpoint.com
  2.70% |    6 |  2.05% |    35661 | stpeter@stpeter.im
  2.25% |    5 |  2.01% |    34917 | dhc@dcrocker.net
  2.25% |    5 |  1.87% |    32418 | barryleiba@computer.org
  1.80% |    4 |  2.25% |    39049 | tjc@ecs.soton.ac.uk
  1.35% |    3 |  2.36% |    41081 | spromano@unina.it
  1.80% |    4 |  1.87% |    32564 | andy@yumaworks.com
  1.80% |    4 |  1.65% |    28732 | ted.lemon@nominum.com
  1.80% |    4 |  1.50% |    26028 | mcr+ietf@sandelman.ca
  1.80% |    4 |  1.45% |    25184 | aaron.ding@cl.cam.ac.uk
  1.35% |    3 |  1.38% |    24049 | chair@ietf.org
  1.35% |    3 |  1.34% |    23348 | rdroms.ietf@gmail.com
  1.35% |    3 |  1.16% |    20126 | roland.bless@kit.edu
  1.35% |    3 |  1.15% |    19939 | kathleen.moriarty@emc.com
  1.35% |    3 |  1.12% |    19406 | joelja@bogus.com
  1.35% |    3 |  1.09% |    19009 | hartmans-ietf@mit.edu
  1.35% |    3 |  0.96% |    16709 | touch@isi.edu
  0.90% |    2 |  0.99% |    17194 | d3e3e3@gmail.com
  0.90% |    2 |  0.93% |    16233 | petithug@acm.org
  0.90% |    2 |  0.85% |    14812 | amorris@amsl.com
  0.90% |    2 |  0.82% |    14280 | jcurran@istaff.org
  0.90% |    2 |  0.80% |    13957 | yding@cs.helsinki.fi
  0.90% |    2 |  0.77% |    13418 | danny@tcb.net
  0.90% |    2 |  0.71% |    12262 | josh.howlett@ja.net
  0.90% |    2 |  0.66% |    11396 | scott.brim@gmail.com
  0.90% |    2 |  0.64% |    11075 | ned+ietf@mauve.mrochek.com
  0.90% |    2 |  0.59% |    10336 | randy@psg.com
  0.90% |    2 |  0.56% |     9647 | ietf@meetecho.com
  0.45% |    1 |  0.93% |    16123 | nkukich@verilan.com
  0.45% |    1 |  0.85% |    14714 | jsalowey@cisco.com
  0.45% |    1 |  0.81% |    14144 | andrewmcgr@google.com
  0.45% |    1 |  0.66% |    11498 | amanda.baber@icann.org
  0.45% |    1 |  0.62% |    10744 | mary.h.barnes@gmail.com
  0.45% |    1 |  0.59% |    10318 | daedulus@btconnect.com
  0.45% |    1 |  0.55% |     9616 | dave@cridland.net
  0.45% |    1 |  0.54% |     9392 | david.black@emc.com
  0.45% |    1 |  0.50% |     8729 | ajs@anvilwalrusden.com
  0.45% |    1 |  0.50% |     8686 | narten@us.ibm.com
  0.45% |    1 |  0.47% |     8238 | ted.ietf@gmail.com
  0.45% |    1 |  0.46% |     7965 | brian@innovationslab.net
  0.45% |    1 |  0.46% |     7918 | kvivek@broadcom.com
  0.45% |    1 |  0.45% |     7905 | simon.leinen@switch.ch
  0.45% |    1 |  0.45% |     7825 | fluffy@cisco.com
  0.45% |    1 |  0.45% |     7808 | mir@ripe.net
  0.45% |    1 |  0.43% |     7535 | bclaise@cisco.com
  0.45% |    1 |  0.43% |     7507 | bmanning@isi.edu
  0.45% |    1 |  0.43% |     7493 | hannes.tschofenig@gmx.net
  0.45% |    1 |  0.42% |     7376 | alejandroacostaalamo@gmail.com
  0.45% |    1 |  0.42% |     7233 | doug.mtview@gmail.com
  0.45% |    1 |  0.40% |     7035 | gsalguei@cisco.com
  0.45% |    1 |  0.40% |     7005 | zach@sensinode.com
  0.45% |    1 |  0.39% |     6692 | jabley@hopcount.ca
  0.45% |    1 |  0.37% |     6450 | marka@isc.org
  0.45% |    1 |  0.37% |     6370 | johnl@taugh.com
  0.45% |    1 |  0.36% |     6308 | peter@akayla.com
  0.45% |    1 |  0.34% |     5940 | lorenzo@meetecho.com
  0.45% |    1 |  0.34% |     5865 | ietf2dave@davearonson.com
  0.45% |    1 |  0.34% |     5864 | l.wood@surrey.ac.uk
  0.45% |    1 |  0.33% |     5797 | steve@shinkuro.com
  0.45% |    1 |  0.33% |     5733 | tterribe@xiph.org
  0.45% |    1 |  0.32% |     5593 | housley@vigilsec.com
  0.45% |    1 |  0.30% |     5262 | braden@isi.edu
  0.45% |    1 |  0.30% |     5180 | jhutz@cmu.edu
  0.45% |    1 |  0.29% |     5035 | adrian@olddog.co.uk
--------+------+--------+----------+------------------------
100.00% |  222 |100.00% |  1737615 | Total


From moore@network-heretics.com  Thu Aug  1 23:29:20 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA2A711E821E for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 23:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.617
X-Spam-Level: 
X-Spam-Status: No, score=-3.617 tagged_above=-999 required=5 tests=[AWL=-0.018, 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 Hwr4HooYsFEV for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 23:29:15 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE7011E8253 for <ietf@ietf.org>; Thu,  1 Aug 2013 23:28:13 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 31B7320F30; Fri,  2 Aug 2013 02:28:11 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 02 Aug 2013 02:28:12 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=sng7vRjFNN0ZUlpRGbbHmzmkZK0=; b=MM dtwsrEQdemf8ZZ+d46HqhJ/ttVywuXufSb96n81PYnTGYcH3ERve+O9J0z+Wqx0A YykmbhXfb5omonrcAje50IV3Wno+pt5RtLcZOaGOk0jtlvsQjAwPEksjNd9bxDo7 zqb8cQrw8Bn7zNz5brJ45DMequHkfNovin6JHGzV8=
X-Sasl-enc: 0Tbu9HaIp0602d9NRbyitd9CRtw5pDlkRCW1AiPcd5BT 1375424891
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 1F5F26800A0; Fri,  2 Aug 2013 02:28:10 -0400 (EDT)
Subject: Re: Bringing back Internet transparency
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <20130801191438.C027718C183@mercury.lcs.mit.edu>
Date: Fri, 2 Aug 2013 08:28:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3C285AE-7B5C-4BAA-8FAC-F4BC209CE275@network-heretics.com>
References: <20130801191438.C027718C183@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 06:29:21 -0000

On Aug 1, 2013, at 9:14 PM, Noel Chiappa wrote:

>> From: Phillip Hallam-Baker <hallam@gmail.com>
>=20
>> The ISPs had a clear interest in killing of NAT which threatened the
>> ISP business model.
>=20
> So this is rather amusing: you're trying to tell me that ISPs wanted =
to kill
> NAT, and I have other people telling me NAT was an intergral part of =
ISPs'
> master plan to take over the universe.
>=20
> Clearly you all both can't be right.

ISPs were against NATs at first.   It was only later that they embraced =
them.

Keith


From petithug@acm.org  Thu Aug  1 23:50:33 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBA811E825A for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 23:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.013,  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 TRYp9s5W-BIa for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 23:50:32 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 62D6D11E8249 for <ietf@ietf.org>; Thu,  1 Aug 2013 23:50:32 -0700 (PDT)
Received: from [IPv6:2001:df8:0:64:ca0a:a9ff:fe2e:a4f6] (unknown [IPv6:2001:df8:0:64:ca0a:a9ff:fe2e:a4f6]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 1B7732088A; Fri,  2 Aug 2013 08:50:29 +0200 (CEST)
Message-ID: <51FB56C1.9080200@acm.org>
Date: Fri, 02 Aug 2013 08:50:41 +0200
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Bringing back Internet transparency
References: <20130801191438.C027718C183@mercury.lcs.mit.edu> <A3C285AE-7B5C-4BAA-8FAC-F4BC209CE275@network-heretics.com>
In-Reply-To: <A3C285AE-7B5C-4BAA-8FAC-F4BC209CE275@network-heretics.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 02 Aug 2013 06:50:33 -0000

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

On 08/02/2013 08:28 AM, Keith Moore wrote:
> 
> On Aug 1, 2013, at 9:14 PM, Noel Chiappa wrote:
> 
>>> From: Phillip Hallam-Baker <hallam@gmail.com>
>> 
>>> The ISPs had a clear interest in killing of NAT which threatened the 
>>> ISP business model.
>> 
>> So this is rather amusing: you're trying to tell me that ISPs wanted to
>> kill NAT, and I have other people telling me NAT was an intergral part of
>> ISPs' master plan to take over the universe.
>> 
>> Clearly you all both can't be right.
> 
> ISPs were against NATs at first.   It was only later that they embraced
> them.
> 

This mess is still the ISP fault.  If they gave users what they wanted, which
is multiple IP addresses, then they wouldn't have to install NAT (I am still
paying $9.95 per month for the privilege of having 4 additional IPv4 addresses
on my Comcast connection).  And that would have accelerated IPv6 deployment.

The firewall issue is orthogonal (which I put the blame on Microsoft sloppy
coding practices).

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBCAAGBQJR+1a7AAoJECnERZXWan7EK7MQAOTwF/oZp5nPSbygmgivYCCD
W+TYtQhtikwMJHn1VriikxQlsKaDM/GtJuG9/Zwe7zj7rdu4Z7QkHQolD3CMhOPM
d74rRnqTrFOxedyLoknly/xCkb/4cpb0q7zX06nRsrm6ufy84i6UWVX+HONcEkh1
/9rF1/6gNWlKIiEHjT9fmiOrdVU0D4I/sQaeGHrI4wCdIdr8PXVADPQ1mAQJlxVT
FW4P5KfXRz7pBQ+vcmuHEn+3spf64ClP5fBD6DsEuujjU6P5mxaaTgKZqy9YXhHb
9buSk7xJINLN9oG2GAYKPw/WGLlVo/AzaOmQoRIP63+bFmFZ4JAIS/ikWvdWdI5A
NJuxGML0Pp4sNAwtAOY5kAQsBwEdrJMDtUHNtSHCOarog/IpbPP9BKjgzF1owA+N
AzEh08YqiE+f67hXE4cYrnXcF87BzcBeP3NXsuRF3jh2uAY4DGuTVLvLgG4Z1tfI
aKXBQVekn3gdEFN4sMEjfEMih0gpS1mDqPm3ccVBQvD6WcWyZcFNwIiJGJfysBV3
EmAQC8W4hpSKQ7uzVhbpBb7M+puFJg7iIt6BprX60KoLXGx7HklsecdQXk6gYQA5
Pdr42nNiLZPwd3ehI8PR+K2qirXJUkKKBIn78rVt7UeuxEj+oN+GOQQSst3h2j4e
qYDN6/Qx+xUcAy1Y7D8m
=s1v7
-----END PGP SIGNATURE-----

From joelja@bogus.com  Thu Aug  1 23:55:58 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E4711E8253 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 23:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level: 
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qd42-4oqsnQ9 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 23:55:58 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1A24011E8249 for <ietf@ietf.org>; Thu,  1 Aug 2013 23:55:58 -0700 (PDT)
Received: from dhcp-6518.meeting.ietf.org (dhcp-6518.meeting.ietf.org [130.129.101.24]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r726trTL014518 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 06:55:55 GMT (envelope-from joelja@bogus.com)
Message-ID: <51FB57F9.4050201@bogus.com>
Date: Fri, 02 Aug 2013 08:55:53 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: 6tsch BoF
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com>	<CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com>	<51FA2A70.10208@bogus.com> <51FA8BE2.90406@gmail.com>
In-Reply-To: <51FA8BE2.90406@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 02 Aug 2013 06:55:56 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 06:55:59 -0000

On 8/1/13 6:25 PM, Melinda Shore wrote:
> On 8/1/13 1:29 AM, joel jaeggli wrote:
>> Consensus for any particular outcome is in the end a judgment call.
> Well, yes and no, but this situation strikes me as odd, and probably
> a mistake on the part of the chairs.  If you can't tell whether or
> not you've got consensus, you don't have consensus.
Yes agree The distinction of none or any variant of something else is a
judgement call.
>   It sounds like
> they were treating the hum as a vote in the first place (which we
> do entirely too often).
I see nothing wrong with taking the temperature of the room.  further
exposition on the mailing list might be a discriminator that would be
easier to identify the positions and what action should therefore occur.
>
> Melinda
>


From iana-shared@icann.org  Wed Jul 31 07:40:48 2013
Return-Path: <iana-shared@icann.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B324C11E8109 for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glswxTsvz06y for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 07:40:44 -0700 (PDT)
Received: from smtp1.lax.icann.org (smtp01.icann.org [192.0.33.81]) by ietfa.amsl.com (Postfix) with ESMTP id DBE5011E8198 for <ietf@ietf.org>; Wed, 31 Jul 2013 07:40:42 -0700 (PDT)
Received: from request1.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp1.lax.icann.org (8.13.8/8.13.8) with ESMTP id r6VEefhP022235 for <ietf@ietf.org>; Wed, 31 Jul 2013 14:40:41 GMT
Received: by request1.lax.icann.org (Postfix, from userid 48) id 8E0D656049C; Wed, 31 Jul 2013 14:40:41 +0000 (UTC)
RT-Owner: Nobody
Subject: [IANA #700324] stability of iana.org URLs
From: "Amanda Baber via RT" <iana-questions@iana.org>
In-Reply-To: <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com>
References: <RT-Ticket-700324@icann.org> <24093.1375278470@sandelman.ca> <CAC4RtVA_BQ=mMjSJCZEW3tpzadgJuk+KmaR8zR0Bjo_EqDoihg@mail.gmail.com>
Message-ID: <rt-4.0.8-10003-1375281641-1570.700324-7-0@icann.org>
Precedence: bulk
X-RT-Loop-Prevention: IANA
RT-Ticket: IANA #700324
Managed-BY: RT 4.0.8 (http://www.bestpractical.com/rt/)
RT-Originator: amanda.baber@icann.org
CC: ietf@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Date: Wed, 31 Jul 2013 14:40:41 +0000
X-Mailman-Approved-At: Fri, 02 Aug 2013 00:07:19 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: iana-questions@iana.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2013 14:40:48 -0000

Hi,

The link in RFC3315 is actually incorrect -- it should have been http://www.iana.org/assignments/enterprise-numbers, without the file extension, and there's an erratum about this. HTML was generally (I say "generally" because there may be exceptions Michelle would know about) reserved for files that needed to include links to registration forms, like MIME/Media Types (which will be converted to XML shortly) and URI Schemes.

As Barry said, we do intend to keep that same short http://www.iana.org/assignments/example format working for every current page, even the newly-created ones. We also prefer to see that format used in documents, since we can't guarantee that the file extension used for the long version won't change. (This information will be appearing on the website in some form.)

(BTW: I've never tried writing to ietf@ietf.org from our ticketing system, so Barry, would you mind pushing this along if it never shows up there?)

Amanda Baber
IANA Request Specialist
ICANN 

On Wed Jul 31 14:06:28 2013, barryleiba@computer.org wrote:
> > I just followed http://www.iana.org/assignments/enterprise-numbers.html
> > From RFC3315 (DHCPv6)'s reference section.  Ten years later, the URL
> > doesn't work.
> >
> > I know that things were reworked when we went to XML based storage, but
> > I thought that the old URLs would at least have a 301 error on them.
> >
> > I discovered that dropping the .html gets me the right data at:
> >   http://www.iana.org/assignments/enterprise-numbers
> 
> Yes: that's the form that IANA would like you to use.  They changed
> their registries from HTML to XML, and the URLs changed.  Supposed
> they should decide to turn them all into JSON (aieeeeeeeee!)... the
> URLs would change again.  But the suffix-less version will always
> work.
> 
> When I've done AD reviews of documents that cite IANA URLs, I've given
> the authors that feedback, and suggested the change to the suffix-less
> URLs.  I also intend to suggest to IANA (thanks to a document author,
> and I've since forgotten who it was; sorry) that they post permalinks
> in all the registries, so people will know which URL they ought to
> use, and not have to guess.
> 
> Barry, Applications AD
> 




From James.H.Manger@team.telstra.com  Thu Aug  1 09:09:32 2013
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3602321E8153 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 09:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level: 
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCQ2VEX2Hdp2 for <ietf@ietfa.amsl.com>; Thu,  1 Aug 2013 09:09:26 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 5910D11E8105 for <ietf@ietf.org>; Thu,  1 Aug 2013 09:09:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,795,1367935200"; d="scan'208";a="150285491"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipoani.tcif.telstra.com.au with ESMTP; 02 Aug 2013 02:09:14 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,7153"; a="159210390"
Received: from wsmsg3757.srv.dir.telstra.com ([172.49.40.85]) by ipccni.tcif.telstra.com.au with ESMTP; 02 Aug 2013 02:09:14 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3757.srv.dir.telstra.com ([172.49.40.85]) with mapi; Fri, 2 Aug 2013 02:09:14 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: IETF Discussion <ietf@ietf.org>
Date: Fri, 2 Aug 2013 02:09:12 +1000
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Topic: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Index: Ac6O0XZOfE87L5d8QPuKdyzMxfiPsA==
Message-ID: <255B9BB34FB7D647A506DC292726F6E115281CE3C1@WSMSG3153V.srv.dir.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 02 Aug 2013 00:07:40 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2013 16:09:32 -0000

ZHJhZnQtYm9ybWFubi1jYm9yLTA0IGFkZHMgdGV4dCBhYm91dCBoYW5kbGluZyBtYXBzIHdpdGgg
bXVsdGlwbGUgaWRlbnRpY2FsIGtleXMuLCBidXQgaXQgaXMgY29udHJhZGljdG9yeS4gU2VjdGlv
biAzLjQuICJTcGVjaWZ5aW5nIEtleXMgZm9yIE1hcHMiIHNheXM6DQoNCiAgIEEgQ0JPUi1iYXNl
ZCBwcm90b2NvbCBzaG91bGQgbWFrZSBhbiBpbnRlbnRpb25hbCBkZWNpc2lvbiBhYm91dCB3aGF0
DQogICB0byBkbyB3aGVuIGEgcmVjZWl2aW5nIGFwcGxpY2F0aW9uIHNlZXMgbXVsdGlwbGUgaWRl
bnRpY2FsIGtleXMgaW4gYQ0KICAgbWFwLiAgQSBwcm90b2NvbCBtaWdodCBoYXZlIGEgcnVsZSB0
aGF0IGl0IGlzIG5vdCBhbiBlcnJvciB0byBoYXZlDQogICBpZGVudGljYWwga2V5cyBpbiBhIG1h
cCwgYW5kIHRoYXQgdGhlIHJlY2VpdmluZyBhcHBsaWNhdGlvbiB3aWxsDQogICBkaXNjYXJkIGFs
bCBidXQgdGhlIGxhc3Qga2V5L3ZhbHVlIHBhaXIgZm9yIGEgZ2l2ZW4ga2V5IGluIGEgbWFwLg0K
DQogICAuLi4NCg0KICAgVGhlIENCT1IgZGF0YSBtb2RlbCBmb3IgbWFwcyBkb2VzIG5vdCBhbGxv
dyBhc2NyaWJpbmcgc2VtYW50aWNzIHRvDQogICB0aGUgb3JkZXIgb2YgdGhlIGtleS92YWx1ZSBw
YWlycyBpbiB0aGUgbWFwIHJlcHJlc2VudGF0aW9uLiAgQSBDQk9SLQ0KICAgYmFzZWQgcHJvdG9j
b2wgTVVTVCBOT1QgYmUgZGVmaW5lZCBpbiBzdWNoIGEgd2F5IHRoYXQgY2hhbmdpbmcgdGhlDQog
ICBrZXkvdmFsdWUgcGFpciBvcmRlciBpbiBhIG1hcCB3b3VsZCBjaGFuZ2UgdGhlIHNlbWFudGlj
cywgYXBhcnQgZnJvbQ0KICAgdHJpdmlhbCBhc3BlY3RzIChjYWNoZSB1c2FnZSBldGMuKS4NCg0K
DQpBIHByb3RvY29sIHRoYXQgc2F5cyAiZGlzY2FyZCBhbGwgYnV0IHRoZSBsYXN0IGtleS92YWx1
ZSBwYWlyIGZvciBhIGdpdmVuIGtleSIgZG9lcyBjaGFuZ2Ugc2VtYW50aWNzIGlmIHRoZSBrZXkv
dmFsdWUgcGFpciBvcmRlciBpcyBjaGFuZ2VkIHNvIGl0IHZpb2xhdGVzIHRoZSB0ZXh0IHNheWlu
ZyB0aGlzICJNVVNUIE5PVCIgaGFwcGVuLg0KDQpHaXZlbiB0aGVyZSBpcyBubyBsZWdhY3kgQ0JP
UiBkYXRhIHRvIG1haW50YWluIGJhY2t3YXJkIGNvbXBhdGliaWxpdHkgd2l0aCwgdGhlIHNwZWMg
c2hvdWxkIGJlIGNsZWFyZXIgdGhhdCBhIG1hcCB3aXRoIG11bHRpcGxlIGlkZW50aWNhbCBrZXlz
IGlzIGFsd2F5cyBhbiBlcnJvci4gRGlzY2FyZGluZyBhbGwgYnV0IHRoZSBsYXN0IHBhaXIgZm9y
IGEgZ2l2ZW4ga2V5IGlzIE5PVCBhY2NlcHRhYmxlIGJlaGF2aW91ciBmb3IgYSBwYXJzZXIuIEEg
bm90ZSB0aGF0IGEgc3RyZWFtaW5nIHBhcnNlciBtaWdodCBub3QgYmUgYWJsZSB0byBkZXRlY3Qg
ZHVwbGljYXRlcyBpcyBvaywgYWNjb21wYW5pZWQgYnkgYSB3YXJuaW5nIHRoYXQgYW4gYXBwbGlj
YXRpb24gdXNpbmcgc3VjaCBhIHBhcnNlciB3aWxsIG5lZWQgaXRzIG93biBjaGVja3MgZm9yIG11
bHRpcGxlIGlkZW50aWNhbCBrZXlzIHRvIGF2b2lkIHVuYW1iaWd1b3VzIG1lc3NhZ2VzLg0KDQpT
dWdnZXN0aW9uOg0KDQpEZWxldGUgdGhlIHdob2xlIHBhcmFncmFwaCBzdGFydGluZyAiQSBDQk9S
LWJhc2VkIHByb3RvY29sIHNob3VsZCBtYWtlIGFuIGludGVudGlvbmFsIGRlY2lzaW9uIi4NCg0K
QWZ0ZXIgdGhlIHNlbnRlbmNlICJUaGUgQ0JPUiBkYXRhIG1vZGVsIGZvciBtYXBzIGFsbG93cyB6
ZXJvIG9yIG9uZSBlbnRyaWVzIGluIHRoZSBtYXAgZm9yIGVhY2ggc3BlY2lmaWMga2V5IiwgYWRk
IHRoZSBmb2xsb3dpbmcgc2VudGVuY2VzOg0KDQogICBDb25zZXF1ZW50bHksIGEgbWFwIGluIHdo
aWNoIGEgc3BlY2lmaWMga2V5IGFwcGVhcnMgbXVsdGlwbGUgdGltZXMgaXMgbm90DQogICBhIHZh
bGlkIENCT1IgdmFsdWUuIEEgcGFyc2VyIE1VU1QgTk9UIGFjY2VwdCBzdWNoIGEgbWFwIGJ5IGtl
ZXBpbmcganVzdA0KICAgb25lIGVudHJ5IGZvciBhbiBvZmZlbmRpbmcga2V5Lg0KDQoNClR5cG86
IHMvZm9yIGVhY2ggYSBzcGVjaWZpYyBrZXkvZm9yIGVhY2ggc3BlY2lmaWMga2V5Lw0KDQotLQ0K
SmFtZXMgTWFuZ2VyDQoNCg==

From zhaoqin@bupt.edu.cn  Wed Jul 31 13:15:25 2013
Return-Path: <zhaoqin@bupt.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDE221F9D3A for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 13:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, 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 I34b9S6AGRjI for <ietf@ietfa.amsl.com>; Wed, 31 Jul 2013 13:15:19 -0700 (PDT)
Received: from mail.bupt.edu.cn (mail.bupt.edu.cn [211.68.71.7]) by ietfa.amsl.com (Postfix) with ESMTP id 2EADD21F9D02 for <ietf@ietf.org>; Wed, 31 Jul 2013 13:15:19 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx5.bupt.edu.cn (Postfix) with SMTP id 832F73403CA for <ietf@ietf.org>; Thu,  1 Aug 2013 04:15:17 +0800 (CST)
X-AnySpam-Host: mx5.bupt.edu.cn
X-AnySpam-Flag: No
X-AnySpam-Hits: 3.00/5.00
X-AnySpam-Rules: LocalUSER_Send
Received: from zhao-qinmatoMacBook-Pro.local (unknown [213.23.104.157]) by mx5.bupt.edu.cn (Postfix) with ESMTP id 981683403BC for <ietf@ietf.org>; Thu,  1 Aug 2013 04:15:16 +0800 (CST)
X-SenderID: Sendmail Sender-ID Filter v0.2.14 mx5.bupt.edu.cn 981683403BC
Authentication-Results: mx5.bupt.edu.cn from=zhaoqin@bupt.edu.cn; sender-id=softfail; spf=softfail
Message-ID: <51F97051.5030201@bupt.edu.cn>
Date: Thu, 01 Aug 2013 04:15:13 +0800
From: =?UTF-8?B?6LW16ZKm?= <zhaoqin@bupt.edu.cn>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: About Final Receipt
References: <20130729111753.24528.44252.idtracker@ietfa.amsl.com>
In-Reply-To: <20130729111753.24528.44252.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Fri, 02 Aug 2013 00:09:23 -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, 31 Jul 2013 20:15:25 -0000

Hiï¼Œ
I have received the Preliminary Payment Receipt, but don't receive the 
final receipt until now.
Is it correct?

-- 
èµµé’¦
åŒ—äº¬é‚®ç”µå¤§å­¦
ä¿¡æ�¯ç½‘ç»œä¸­å¿ƒ

zhaoqin
62283011
zhaoqin@bupt.edu.cn


From sm@resistor.net  Fri Aug  2 00:15:10 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25D8E11E827B for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 00:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, J_CHICKENPOX_74=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XIGLb9QF5BFw for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 00:15:09 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB0B11E8276 for <ietf@ietf.org>; Fri,  2 Aug 2013 00:15:09 -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 r727F25d016857; Fri, 2 Aug 2013 00:15:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375427708; bh=dKdQFI7Tbqe3CLn5+3+EhtHO+xI4nvnY+uWc71/k8FQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eX0QJ9WS3+P/Hm3zHZUump31XfzcKysCea+X8gH/wzcaFLbVCbWveZqhwobgxIxwo ww8VcQfM3t94lTdhtResU3GHtLRXRRWpTU4RMLZlbuqdJhx6cH8j4qQd1XfiAJmC7F IjpYaRt9H7Ctm8YjtuuiANsQwqx3iJfwEnK3DWK8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375427708; i=@resistor.net; bh=dKdQFI7Tbqe3CLn5+3+EhtHO+xI4nvnY+uWc71/k8FQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uRXBKFcYKdq+au+W30fwwM/vLeYWo/0jCoQUbGYT0h+cww34w7Z1tTL6/Fym0KWWj VM+IFxibz6d5E82aNAibIZehJOh6xyhkQrbBS+1vvmZLhdwaJAf6OIUQv2txulDyrh 1n1S3+ZFPTm4Dscs4buahkYtE65IyXjEeBfOK5Rs=
Message-Id: <6.2.5.6.2.20130801225725.0d388d50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 02 Aug 2013 00:13:50 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>
From: SM <sm@resistor.net>
Subject: Re: 6tsch BoF
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominu m.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, Andy Bierman <andy@yumaworks.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:15:10 -0000

Hi Ted,
At 08:00 01-08-2013, Ted Lemon wrote:
>We actually had a talk about this amongst=20
>several IESG and former IESG members.   I am not going to

Bernard Aboba once mentioned:

   To paraphrase Tilda Swinton's Oscar Acceptance Speech:

   "To the IESG, you know, the seriousness and the
    dedication to your art... you rock, man!"

>  report the results, because I might remember=20
> them wrong, but my thoughts on this are as follows:
>
>- The hum is not a means of determining=20
>consensus; it is a means of determining the=20
>sense of the room.   If the hum is clearly many=20
>in favor, nobody against,then you have=20
>consensus, but that's unusual.   If the hum=20
>shows many in favor and some against, you need=20
>to go to the next step, because you do not yet know whether you have=
 consensus.
>
>- So since the hum was quite inconclusive, the=20
>next question is, "can somebody who objects=20
>please say why."   One way to approach that is=20
>to ask for a show of hands.   Here, the chairs=20
>could have asked for a show of hands against=97the=20
>show of hands for was unnecessary.   But this is=20
>forgivable, I think, unless you think people=20
>were intimidated by the show of hands for.   I=20
>think that would be hard to argue, given that=20
>they had already heard the result of the hum.
>
>- So the show of hands against elicited no=20
>hands.   I was there, that's what I remember seeing too.
>
>So at this point, what do you do?   Nobody is=20
>willing to stand up and say "I think we=20
>shouldn't go forward with this because of=20
>X."   Many people have said "we think we should=20
>go forward with this, support doing this, and want to participate."
>
>To me, that's consensus.

The above comment about consensus is an opinion. :-)

In my opinion part of the answer has been=20
provided by Brian Carpenter.  The other part of=20
the answer is the minutes.  The rest of the=20
answer is in something mentioned in the Note Well.

Regards,
-sm =20


From amorris@amsl.com  Fri Aug  2 00:18:13 2013
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 2E5DF11E8274 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 00:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, 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 gz9cjvCHnQXH for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 00:18:12 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id D23FE11E826B for <ietf@ietf.org>; Fri,  2 Aug 2013 00:18:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id E4AE5A60A6; Fri,  2 Aug 2013 00:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6UJYkuaH4e8; Fri,  2 Aug 2013 00:17:54 -0700 (PDT)
Received: from dhcp-4090.meeting.ietf.org (dhcp-4090.meeting.ietf.org [130.129.64.144]) by c9a.amsl.com (Postfix) with ESMTPSA id 4DDA0A60A1; Fri,  2 Aug 2013 00:17:54 -0700 (PDT)
Subject: Re: About Final Receipt
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=utf-8
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <51F97051.5030201@bupt.edu.cn>
Date: Fri, 2 Aug 2013 00:18:09 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F8129F9-D529-4E8F-A1F6-491BB4EABE08@amsl.com>
References: <20130729111753.24528.44252.idtracker@ietfa.amsl.com> <51F97051.5030201@bupt.edu.cn>
To: =?utf-8?B?6LW16ZKm?= <zhaoqin@bupt.edu.cn>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 07:18:13 -0000

Any attendee who paid for their meeting registration fee by midnight of =
22 July has received their final VAT receipt. However, if you paid your =
meeting fee after 22 July you have not yet received your final receipt. =
We will be generating those final receipts shortly after the conclusion =
of the meeting. I apologize for any inconvenience.

Regards,
Alexa

On Jul 31, 2013, at 1:15 PM, =E8=B5=B5=E9=92=A6 wrote:

> Hi=EF=BC=8C
> I have received the Preliminary Payment Receipt, but don't receive the =
final receipt until now.
> Is it correct?
>=20
> --=20
> =E8=B5=B5=E9=92=A6
> =E5=8C=97=E4=BA=AC=E9=82=AE=E7=94=B5=E5=A4=A7=E5=AD=A6
> =E4=BF=A1=E6=81=AF=E7=BD=91=E7=BB=9C=E4=B8=AD=E5=BF=83
>=20
> zhaoqin
> 62283011
> zhaoqin@bupt.edu.cn
>=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/>


From joelja@bogus.com  Fri Aug  2 00:24:39 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50FD911E8253 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 00:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HAPrPaYrwPQp for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 00:24:37 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 47DC511E8293 for <ietf@ietf.org>; Fri,  2 Aug 2013 00:24:37 -0700 (PDT)
Received: from dhcp-6518.meeting.ietf.org (dhcp-6518.meeting.ietf.org [130.129.101.24]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r727OWiU014968 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 07:24:34 GMT (envelope-from joelja@bogus.com)
Message-ID: <51FB5EB0.5030102@bogus.com>
Date: Fri, 02 Aug 2013 09:24:32 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>, Keith Moore <moore@network-heretics.com>
Subject: Re: Bringing back Internet transparency
References: <20130801191438.C027718C183@mercury.lcs.mit.edu>	<A3C285AE-7B5C-4BAA-8FAC-F4BC209CE275@network-heretics.com> <51FB56C1.9080200@acm.org>
In-Reply-To: <51FB56C1.9080200@acm.org>
Content-Type: text/plain; charset=UTF-8
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, 02 Aug 2013 07:24:35 +0000 (UTC)
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, 02 Aug 2013 07:24:39 -0000

On 8/2/13 8:50 AM, Marc Petit-Huguenin wrote:
> On 08/02/2013 08:28 AM, Keith Moore wrote:
>
> > On Aug 1, 2013, at 9:14 PM, Noel Chiappa wrote:
>
> >>> From: Phillip Hallam-Baker <hallam@gmail.com>
> >>
> >>> The ISPs had a clear interest in killing of NAT which threatened the
> >>> ISP business model.
> >>
> >> So this is rather amusing: you're trying to tell me that ISPs wanted to
> >> kill NAT, and I have other people telling me NAT was an intergral
> part of
> >> ISPs' master plan to take over the universe.
> >>
> >> Clearly you all both can't be right.
>
> > ISPs were against NATs at first.   It was only later that they embraced
> > them.
>
>
> This mess is still the ISP fault.  If they gave users what they
> wanted, which
> is multiple IP addresses, then they wouldn't have to install NAT (I am
> still
> paying $9.95 per month for the privilege of having 4 additional IPv4
> addresses
> on my Comcast connection).  And that would have accelerated IPv6
> deployment.
>
Wierdly, I don't actually want to bridge my home network to my ISP nor
are they frankly likely to accommodate my need for a /27 without some
consideration, while there are plenty of ways that can be achieved with
IPv4 they have more friction and therefore cost for the isp and the
consumer then simply receiving one ip via dhcp and getting on with my 
life. it's also somewhat convenient when that primary provider is down
that the network can be hung off an LTE connection (renumbering isn't a
problem, dhcp can address that, getting one IP is).

My current CPE does DHCPv6 PD and comcast accommodates me accordingly. I
hope verizon LTE will eventually.
> The firewall issue is orthogonal (which I put the blame on Microsoft
> sloppy
> coding practices).
>
Windows machines are not principally the devices on my homenet whose
code I don't trust. consumer electronics don't get a lot of software
updates.

>



From ulrich@herberg.name  Fri Aug  2 01:30:00 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 842E311E82B9 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 01:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.955
X-Spam-Level: 
X-Spam-Status: No, score=-1.955 tagged_above=-999 required=5 tests=[AWL=0.023,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 WHcSvAZo-OY8 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 01:29:55 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id B1D3721F9B8F for <ietf@ietf.org>; Fri,  2 Aug 2013 01:28:28 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id b10so350166vea.7 for <ietf@ietf.org>; Fri, 02 Aug 2013 01:28:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:date:message-id:subject:from:to:content-type; bh=6HMVExdhs0oj+Zm4qY1p/bVV075C7St4CXoXvM/fpnM=; b=Rhao51mhY3ful/vpl4ScBOrQzFAaLrnj3D4DRpEW+SLQQGMbW39+cRG+3tfqYqd3vF KBT/TD5fU6NxVjZkl4ALlFxMcZvzrOp3LQx7K1xhSS1DhRMY1g4l7hiLrQeSKATXG1eu K4uP+OquMqSBTNtpygttQcmjrmlhlqH/lO2jE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=6HMVExdhs0oj+Zm4qY1p/bVV075C7St4CXoXvM/fpnM=; b=n/iB8pd+Oo3SGjWwI4jGxg3HloNJQ+X0RH0in60Kp2noCVUMS2M27XbG5KGtC5laaC NBZHI68xZfa3Qe1QMdlMw4OzGsJ/GaH0RsSI+5Wgts3dzlqydIwimlALIdHyd7Haglpp ZD5yqjL/rj4RUJ1IzEizAOHuhBZCSHtzVCLR9Tw7DfsJT3eMWH8AsXjNcatY8d/6oUBc C8957ErgSuidhEbmMLAn0BEVivGQOzGiuwBYnPFEfeMqObTxlDEh9bynksiYOVkINCWg qMhteXUrsS7uGBKX2klYMKWBX4hN5fhhhXs8hKnlfYo0BgkFmWYDhWUL8D0vm7BfIRBt jMTQ==
MIME-Version: 1.0
X-Received: by 10.58.80.38 with SMTP id o6mr1697456vex.69.1375432103640; Fri, 02 Aug 2013 01:28:23 -0700 (PDT)
Received: by 10.221.55.70 with HTTP; Fri, 2 Aug 2013 01:28:23 -0700 (PDT)
Date: Fri, 2 Aug 2013 10:28:23 +0200
Message-ID: <CAK=bVC_HsyuR0FLgHcevfhWierpnANQNT7G=PPSFvL7rdrcEzQ@mail.gmail.com>
Subject: Time between meetings
From: Ulrich Herberg <ulrich@herberg.name>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmJbZTF0/dEHbO+j/e4AvKPIm+ZZ2X2UrzRdG42IQW9d18TQrj7E3IhjJVh5+lE36PdXRY2
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 08:30:03 -0000

Hi,

I chaired two afternoon sessions on Thursday, and I think that the 10
minutes break between the sessions were not enough. Not only had I to
rush to the other room to set up my laptop etc., but also the scribes
and minutes takers that have volunteered for the second session were
not yet there (they arrived about 5 minutes after meeting start), so
that I had to find new volunteers at the beginning of the meeting. I
know that the available meeting time is very sparse, but having 20
minutes between meetings could avoid that.

Ulrich

From arturo.servin@gmail.com  Fri Aug  2 03:25:15 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE12E11E8251 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 03:25:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f7wT3DE3yIyD for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 03:25:15 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id F148E21E80A8 for <ietf@ietf.org>; Fri,  2 Aug 2013 03:24:10 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id r10so512597pdi.41 for <ietf@ietf.org>; Fri, 02 Aug 2013 03:24: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=2tbziqUGksGiHmcDxfPM7+rsAUMp1E0MTDPsar1C/Ks=; b=ZHkxCtkw3wmIszoIG0lG+lyeDP+zuqyw7NULNohcqkhmZ6XZe9iM9XBGsEXf+shKLR zpQ3DkbeMmCnBYrYQ+KcYg6KExBS1KoiQFbWggak1PhURjTbcXwaQBzJqNildIgWZOSm r5zdj1Qm5niPMS7nFcsih1m17EYOtLE/glE/qHXi4UmhtwHvqdYbLRrg/NW0DnQuYUvQ G/bHYiJfyl3IWRYpGr1nPO4oy0762pHQCO+ai3hWUgsRX5fWabcEa1i6rSee6cAk41ku PcwiwE9dUjn5suPoSt+vjtQqtdKJitjomGO8NVheqV7yDn2zIGyNYnmvKyGajTuKQzfI 8D9w==
X-Received: by 10.68.164.97 with SMTP id yp1mr6781303pbb.77.1375439050002; Fri, 02 Aug 2013 03:24:10 -0700 (PDT)
Received: from dhcp-156a.meeting.ietf.org ([2001:df8:0:16:9184:8ddf:9492:7d91]) by mx.google.com with ESMTPSA id ib9sm9437681pbc.43.2013.08.02.03.24.07 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 03:24:09 -0700 (PDT)
Message-ID: <51FB88C9.8000304@gmail.com>
Date: Fri, 02 Aug 2013 12:24:09 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Time between meetings
References: <CAK=bVC_HsyuR0FLgHcevfhWierpnANQNT7G=PPSFvL7rdrcEzQ@mail.gmail.com>
In-Reply-To: <CAK=bVC_HsyuR0FLgHcevfhWierpnANQNT7G=PPSFvL7rdrcEzQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 10:25:16 -0000

	Or eat less cookies.  :)

	Now, seriously. I think in your case, it was just bad luck to chair to
meetings one after the other.

	For the rest, taking punctuality more seriously would help.

	As you said, time is scarce and I prefer to use it in meetings than in
breaks.

my 20 cents,
as

On 8/2/13 10:28 AM, Ulrich Herberg wrote:
> Hi,
> 
> I chaired two afternoon sessions on Thursday, and I think that the 10
> minutes break between the sessions were not enough. Not only had I to
> rush to the other room to set up my laptop etc., but also the scribes
> and minutes takers that have volunteered for the second session were
> not yet there (they arrived about 5 minutes after meeting start), so
> that I had to find new volunteers at the beginning of the meeting. I
> know that the available meeting time is very sparse, but having 20
> minutes between meetings could avoid that.
> 
> Ulrich
> 

From olaf@NLnetLabs.nl  Fri Aug  2 03:37:25 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BAC111E810B for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 03:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCT5PAzfbE2n for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 03:37:24 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D39FF11E828C for <ietf@ietf.org>; Fri,  2 Aug 2013 03:37:18 -0700 (PDT)
Received: from dhcp-6532.meeting.ietf.org (dhcp-6532.meeting.ietf.org [130.129.101.50]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r72AbDgl071689 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 2 Aug 2013 12:37:15 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r72AbDgl071689
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1375439837; bh=/se7cSqSGnOXK1mb0OfaS8B2NlOsVw2uGwiRRQ4GC9w=; h=From:Subject:Date:To; b=GKmQ8v4cHN6VSBVyRwSxPW3l5pXiG7SmPsH4JfwPs9wyBClYlhiZop2YXZOboB+wF JExP5q1+tKN13/nBWgeXGNJ4SvPvlcKgGm1i0B+NFUgKHaQDERQgw0KBD0SSo2EYi9 Uy4vd62lRFrJ1j0P8ncJguJp8QGbB2fLL0iw5hns=
From: Olaf Kolkman <olaf@NLnetLabs.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: PS Characterization Clarified
Message-Id: <B8F661D1-1C45-4A4B-9EFE-C7E32A7654E7@NLnetLabs.nl>
Date: Fri, 2 Aug 2013 12:37:13 +0200
To: IETF list <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Fri, 02 Aug 2013 12:37:15 +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: Fri, 02 Aug 2013 10:37:25 -0000

Colleagues,

I have posted draft-kolkman-proposed-standards-clarified-00.txt

We have evolved the quality criteria for our entry-level maturity level =
and todays documentation doesn't reflect that.  With this document we =
intend to align our characterization of PS with what is the current day =
reality.=20

Having 'Immaturity' terminology in RFC2024 and having a large number of =
specifications that remain on proposed standard is something that is =
hard to explain by anybody talking about the quality of IETF =
standards[*]. But that is not the only, or even primary, motivation for =
submitting this. It is good for the people participating in the IETF to =
be aligned on our quality norms.

The I-D does not speak to, or alter the process by which we progress on =
the maturity track.=20

--Olaf

[*] e.g. in regulatory and industry context such as =
http://ec.europa.eu/transparency/regexpert/index.cfm?do=3DgroupDetail.grou=
pDetail&groupID=3D2758


PS. As an aside, with reference to the discussion about progressing =
standards during the Administrative plenary. I would like to stress that =
the quality control (cross area review, progressing along the standards =
track, and retiring specification) that our maintenance mechanisms =
provide are an important part in the conversation about RFCs with =
external business and policy parties.













URL: =
http://www.ietf.org/id/draft-kolkman-proposed-standards-clarified-00.txt=

From lars@netapp.com  Fri Aug  2 03:58:18 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685EA11E825F; Fri,  2 Aug 2013 03:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.937
X-Spam-Level: 
X-Spam-Status: No, score=-8.937 tagged_above=-999 required=5 tests=[AWL=1.662,  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 ml0MO9I0+lI3; Fri,  2 Aug 2013 03:58:11 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE7021E82DB; Fri,  2 Aug 2013 03:58:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,800,1367996400";  d="asc'?scan'208";a="77939671"
Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx12-out.netapp.com with ESMTP; 02 Aug 2013 03:58:04 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.240]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Fri, 2 Aug 2013 03:58:03 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaQ==
Date: Fri, 2 Aug 2013 10:58:03 +0000
Message-ID: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: multipart/signed; boundary="Apple-Mail=_07A54766-CAEF-489D-8B76-B7CAB2613D5C"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IAOC List <IAOC@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 10:58:19 -0000

--Apple-Mail=_07A54766-CAEF-489D-8B76-B7CAB2613D5C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Venue was great, food options here and in the city were great, =
all-around great experience. Let's come again!

(I do kinda wonder how there wasn't a single local company willing to =
step up to be the host. That's embarrassing to me as a German, esp. if =
the IETF meets in the self-declared IT hub of Germany. Better luck next =
time, I hope.)

Lars

--Apple-Mail=_07A54766-CAEF-489D-8B76-B7CAB2613D5C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQCVAwUBUfuQuNZcnpRveo1xAQLuEQP/WJv0u7vZ+8L0GoL6M2yc7D6P7/k1wCyW
syWzepMDNcw3UxmTQFzwN2KoMhb1oVO/sVDfwQog3kwULC1gNyITNHy1IdJZ+hQq
6PsbExRLHuL5L1BsGHWOxiCN0ExY4EiEFQ6POaxsgj2Tt06NVDrCYGW0Jg1mnrSV
r+fwFF7l45E=
=ICTm
-----END PGP SIGNATURE-----

--Apple-Mail=_07A54766-CAEF-489D-8B76-B7CAB2613D5C--

From tony@att.com  Fri Aug  2 04:01:33 2013
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 8B55721E82E6 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-WjG1jPmC6Q for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:01:27 -0700 (PDT)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) by ietfa.amsl.com (Postfix) with ESMTP id 9906811E828A for <ietf@ietf.org>; Fri,  2 Aug 2013 04:00:53 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo07.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 5619bf15.0.6128342.00-446.16937270.nbfkord-smmo07.seg.att.com (envelope-from <tony@att.com>);  Fri, 02 Aug 2013 11:00:53 +0000 (UTC)
X-MXL-Hash: 51fb916517ff4941-918983f399eed1eb57ce910675a4f72dd5dbe933
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 r72B0qUf005811 for <ietf@ietf.org>; Fri, 2 Aug 2013 07:00:52 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r72B0hbW005638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 2 Aug 2013 07:00:47 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor) for <ietf@ietf.org>; Fri, 2 Aug 2013 11:00:25 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r72B0P8W030690 for <ietf@ietf.org>; Fri, 2 Aug 2013 07:00:25 -0400
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r72B0Mu0030406 for <ietf@ietf.org>; Fri, 2 Aug 2013 07:00:22 -0400
Received: from [135.70.11.218] (vpn-135-70-11-218.vpn.west.att.com[135.70.11.218]) by maillennium.att.com (mailgw1) with ESMTP id <20130802110021gw100bhhtke> (Authid: tony); Fri, 2 Aug 2013 11:00:21 +0000
X-Originating-IP: [135.70.11.218]
Message-ID: <51FB9143.5040103@att.com>
Date: Fri, 02 Aug 2013 07:00:19 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: stability of iana.org URLs
References: <21265_1375344641_r718AdfO023164_CE1FE47E.B59E%amanda.baber@icann.org> <1375382894.23365.553.camel@minbar.fac.cs.cmu.edu>
In-Reply-To: <1375382894.23365.553.camel@minbar.fac.cs.cmu.edu>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
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=2.0 cv=YP8oP26x c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=SQo6OefQvGoA:10 a=3ukmKKXcZEAA:10 a=p6_0SVrTFw0A:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=I0CVDw5]
X-AnalysisOut: [ZAAAA:8 a=zQP7CpKOAAAA:8 a=F0QAhBvKCA4A:10 a=-UbDmqGGzsexC]
X-AnalysisOut: [mflf8cA:9 a=QEXdDO2ut3YA:10 a=huntNF1cNFcA:10 a=DFLxlu1nqL]
X-AnalysisOut: [kA:10 a=qiIBw2E1WsIA:10]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:01:33 -0000

I sent IANA a list of 45 iana.org URLs found in the RFCs that generate
404 NOT FOUND (along with the number of the RFC(s) where that URL was
found). Amanda said she'd pass the list on to "the redirector".

    Tony

On 8/1/2013 2:48 PM, Jeffrey Hutzelman wrote:
> Nonetheless, it's an existing URL in an immutable published RFC. Once
> such a thing has been published, right or wrong, best practice is to
> make sure it remains valid. 


From cabo@tzi.org  Fri Aug  2 04:04:42 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D730C21F85C3; Fri,  2 Aug 2013 04:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.119
X-Spam-Level: 
X-Spam-Status: No, score=-106.119 tagged_above=-999 required=5 tests=[AWL=0.130, 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 BBBHW6moRAIS; Fri,  2 Aug 2013 04:04:36 -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 0A76C21F8495; Fri,  2 Aug 2013 04:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r72B2tTB011005; Fri, 2 Aug 2013 13:02:55 +0200 (CEST)
Received: from dhcp-90f8.meeting.ietf.org (dhcp-90f8.meeting.ietf.org [130.129.8.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id C4212324; Fri,  2 Aug 2013 13:02:55 +0200 (CEST)
Subject: Re: Berlin was awesome, let's come again
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Date: Fri, 2 Aug 2013 13:02:55 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1508)
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:04:42 -0000

On Aug 2, 2013, at 12:58, "Eggert, Lars" <lars@netapp.com> wrote:

> Venue was great, food options here and in the city were great, =
all-around great experience. Let's come again!

I'm a big fan of Prague, but I agree that that has now got a rival.
The venue for this meeting was very productive, with few things getting =
in the way.
It also simply was pleasant.

Indeed, let's come again!

Gr=FC=DFe, Carsten


From ynir@checkpoint.com  Fri Aug  2 04:07:47 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45B011E82B0; Fri,  2 Aug 2013 04:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.484
X-Spam-Level: 
X-Spam-Status: No, score=-10.484 tagged_above=-999 required=5 tests=[AWL=0.115, 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 kEehzU2hNMSr; Fri,  2 Aug 2013 04:07:41 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id CCC5311E82B3; Fri,  2 Aug 2013 04:04:52 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r72B4pvW026215; Fri, 2 Aug 2013 14:04:51 +0300
X-CheckPoint: {51FB9253-14-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Fri, 2 Aug 2013 14:04:51 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmBjwyA
Date: Fri, 2 Aug 2013 11:04:50 +0000
Message-ID: <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.96]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11b3c5729073b28e32e8e0429fd16ad8a6dcbf760b
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0A7B1E3E1516A44DB3076547CA2658C1@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:07:47 -0000

There's the slight matter of $123.50 in VAT.=20

To me personally that is minor compared with the much lower price of a flig=
ht to Germany as compared with a flight to the US. But for people working i=
n the US, there's the more expensive flight, and the more expensive meeting=
.

Yoav

On Aug 2, 2013, at 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:

> Venue was great, food options here and in the city were great, all-around=
 great experience. Let's come again!
>=20
> (I do kinda wonder how there wasn't a single local company willing to ste=
p up to be the host. That's embarrassing to me as a German, esp. if the IET=
F meets in the self-declared IT hub of Germany. Better luck next time, I ho=
pe.)
>=20
> Lars


From housley@vigilsec.com  Fri Aug  2 04:07:55 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6361A11E82B3; Fri,  2 Aug 2013 04:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4ZS7qtK5qDS; Fri,  2 Aug 2013 04:07:45 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAF211E82B5; Fri,  2 Aug 2013 04:05:01 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 57B1AF24082; Fri,  2 Aug 2013 07:05:26 -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 jJkoDKCqMzeA; Fri,  2 Aug 2013 07:04:53 -0400 (EDT)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 02D1FF24038; Fri,  2 Aug 2013 07:05:23 -0400 (EDT)
Subject: Re: Berlin was awesome, let's come again
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Date: Fri, 2 Aug 2013 07:04:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A8BA2880-0215-458C-98D7-A8D3F47D62CB@vigilsec.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:07:56 -0000

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

I have also enjoyed my time in Berlin.  However, we need to complete the =
analysis on the impact of VAT.  I hope there is a way to avoid a cost to =
each participant of an 19%.  We heard in plenary that VAT clearly =
applies to conferences, but it may not apply to standards meeting.

Russ


On Aug 2, 2013, at 6:58 AM, Eggert, Lars wrote:

> Venue was great, food options here and in the city were great, =
all-around great experience. Let's come again!
>=20
> (I do kinda wonder how there wasn't a single local company willing to =
step up to be the host. That's embarrassing to me as a German, esp. if =
the IETF meets in the self-declared IT hub of Germany. Better luck next =
time, I hope.)
>=20
> Lars

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlH7klgACgkQiuTu0PWcEcu0QQCdG27kU3gnthbQ35aq9esnpQ0k
SxMAoPvdKtJ8zKbUpcsxPNxKCOAGeiv0
=3DHRQG
-----END PGP SIGNATURE-----

From lars@netapp.com  Fri Aug  2 04:11:07 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 278D311E810B; Fri,  2 Aug 2013 04:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.965
X-Spam-Level: 
X-Spam-Status: No, score=-8.965 tagged_above=-999 required=5 tests=[AWL=1.634,  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 4EhBiW0BpRr5; Fri,  2 Aug 2013 04:11:01 -0700 (PDT)
Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by ietfa.amsl.com (Postfix) with ESMTP id 60B6111E8323; Fri,  2 Aug 2013 04:09:46 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,800,1367996400";  d="asc'?scan'208";a="271363786"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx1-out.netapp.com with ESMTP; 02 Aug 2013 04:09:31 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.240]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Fri, 2 Aug 2013 04:09:30 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNreAgAABQwA=
Date: Fri, 2 Aug 2013 11:09:30 +0000
Message-ID: <7922AF29-364C-4113-AEB5-B18915C128DA@netapp.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <A8BA2880-0215-458C-98D7-A8D3F47D62CB@vigilsec.com>
In-Reply-To: <A8BA2880-0215-458C-98D7-A8D3F47D62CB@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: multipart/signed; boundary="Apple-Mail=_DB1B99FA-D3CB-46B9-9725-8B4503F38399"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:11:07 -0000

--Apple-Mail=_DB1B99FA-D3CB-46B9-9725-8B4503F38399
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On Aug 2, 2013, at 13:04, Russ Housley <housley@vigilsec.com>
 wrote:
> I have also enjoyed my time in Berlin.  However, we need to complete =
the analysis on the impact of VAT.  I hope there is a way to avoid a =
cost to each participant of an 19%.  We heard in plenary that VAT =
clearly applies to conferences, but it may not apply to standards =
meeting.

agreed.

Snarky side comment: We should also analyze the impact of over-the-top =
tipping customs in some countries :-)

Lars

--Apple-Mail=_DB1B99FA-D3CB-46B9-9725-8B4503F38399
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQCVAwUBUfuTZtZcnpRveo1xAQKkSwP+IRtsVcBWD02cs8dPUiXaimHkg8hWycsH
Xa5zSTUazLablM0jJDHlmuahtz5R5GutJeYkqNGvzGsYGylsLWcLgsVz8zrXRrJi
XvEPlz3tAGBP7wF/oDHWgDxkrjowkJasQM6uh7TZbNUoiNenbemAYcyoDsVIBsJC
wSqwOf8L0UA=
=JPtp
-----END PGP SIGNATURE-----

--Apple-Mail=_DB1B99FA-D3CB-46B9-9725-8B4503F38399--

From cpignata@cisco.com  Fri Aug  2 04:12:33 2013
Return-Path: <cpignata@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 BBA8521E8309 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.668
X-Spam-Level: 
X-Spam-Status: No, score=-110.668 tagged_above=-999 required=5 tests=[AWL=-0.070, 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 upXhzyu8PK3l for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:12:29 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id E8A3C11E827F for <ietf@ietf.org>; Fri,  2 Aug 2013 04:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11534; q=dns/txt; s=iport; t=1375441944; x=1376651544; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UjJfmr7p/W9UBUl/BEM+DM6U1naA/b0u880YGj5+3tA=; b=OAh4jhdJ3pisrAT0jRatX4Tj4f7RN70Vws3GEmySn0ORE3yPhBYUOyHn gKtn0Z+/Z/KQF25G3TrB/cJeV8ggdFWOefeIdJnzu1HFhGtGCIWtVAelE qnGCP62rcEKl342JJNiqwn0Kg7s2tRr+5oFvcbXTY+YLWZtzqezJAFRb+ s=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj4FANWT+1GtJV2Z/2dsb2JhbABQCoJCRDVQthqIOIEcFnSCJAEBAQMBeQULAgEIGAokMiUBAQQOBQgBBYd8Bgy5B40YgT4QgQExBwmDEHQDjECDUoEtggiFQoVsijiDF4FpQQ
X-IronPort-AV: E=Sophos;i="4.89,800,1367971200";  d="asc'?scan'208,217";a="242783332"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 02 Aug 2013 11:12:23 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r72BCNej028403 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 2 Aug 2013 11:12:23 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.29]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 06:12:22 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Amanda Baber <amanda.baber@icann.org>
Subject: Re: stability of iana.org URLs
Thread-Topic: stability of iana.org URLs
Thread-Index: Ac6Ojom+B0PKoYA49kGjc0hA9nzSEwBDIbEA
Date: Fri, 2 Aug 2013 11:12:22 +0000
Message-ID: <95067C434CE250468B77282634C96ED322D717DB@xmb-aln-x02.cisco.com>
References: <CE1FE47E.B59E%amanda.baber@icann.org>
In-Reply-To: <CE1FE47E.B59E%amanda.baber@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.106.13]
Content-Type: multipart/signed; boundary="Apple-Mail=_2E6D26E8-BCCD-42F0-A0BC-4E9345C65A0E"; protocol="application/pgp-signature"; micalg=pgp-sha1
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, 02 Aug 2013 11:12:33 -0000

--Apple-Mail=_2E6D26E8-BCCD-42F0-A0BC-4E9345C65A0E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_98D9A809-618E-4943-8EF2-668415AF15AB"


--Apple-Mail=_98D9A809-618E-4943-8EF2-668415AF15AB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi, Amanda,

In my experience, at some point, IANA was instructing authors to replace =
registry URLs (i.e., URLs to specific registries) with a generic pointer =
to http://www.iana.org instead. This had been based on text from RFC =
5226, namely [1] and [2].

Before that there were URLs identifying the registry; and more recently =
as well, the guidance has been to include the suffex-less specific URL =
pointing to a registry, which is great.

If IANA guarantees that stability, URLs pointing to the specific =
registry are very useful IMHO.

Thanks,

-- Carlos.

[1] http://tools.ietf.org/html/rfc5226#section-4.2
4.2.  What to Put in Documents That Create a Registry
...
         that it is a part of should be clearly identified.  When
         referring to an already existing registry, providing a URL to
         precisely identify the registry is helpful.  All such URLs,
         however, will be removed from the RFC prior to final
         publication.  For example, documents could contain: [TO BE
         REMOVED: This registration should take place at the following
         location:  http://www.iana.org/assignments/foobar-registry]

[2] http://tools.ietf.org/html/rfc5226#section-5.1
5.1.  What to Put in Documents When Registering Values
        Note 2: When referring to an existing registry, providing a URL
        to precisely identify the registry is helpful.  Such URLs,
        however, should usually be removed from the RFC prior to final
        publication, since IANA URLs are not guaranteed to be stable in
        the future.  In cases where it is important to include a URL in
        the document, IANA should concur on its inclusion.




On Aug 1, 2013, at 10:10 AM, Amanda Baber <amanda.baber@icann.org> =
wrote:

> Hi,
>=20
> The link in RFC3315 is actually incorrect -- it should have been =
http://www.iana.org/assignments/enterprise-numbers, without the file =
extension, and there's an erratum about this. HTML was generally (if not =
exclusively) reserved for files that needed to include links to =
registration forms .
>=20
> As Barry said, we do intend to keep that same short =
http://www.iana.org/assignments/example format working for every current =
page, even the newly-created ones. We also prefer to see that format =
used in documents, since we can't guarantee that the file extension used =
for the long version won't change. (This information will be appearing =
on the website in some form.)
> Also, if you find that a formerly-valid URL (like one that used to =
have an .html exception) isn't redirecting to the current page, please =
report it to iana@iana.org. A redirect should have been set up.=20
> thanks,
> Amanda Baber
> IANA Request Specialist
> ICANN=20
>=20
> On Wed Jul 31 14:06:28 2013, barryleiba@computer.org wrote:
> > > I just followed =
http://www.iana.org/assignments/enterprise-numbers.html
> > > =46rom RFC3315 (DHCPv6)'s reference section.  Ten years later, the =
URL
> > > doesn't work.
> > >
> > > I know that things were reworked when we went to XML based =
storage, but
> > > I thought that the old URLs would at least have a 301 error on =
them.
> > >
> > > I discovered that dropping the .html gets me the right data at:
> > >   http://www.iana.org/assignments/enterprise-numbers
> >=20
> > Yes: that's the form that IANA would like you to use.  They changed
> > their registries from HTML to XML, and the URLs changed.  Supposed
> > they should decide to turn them all into JSON (aieeeeeeeee!)... the
> > URLs would change again.  But the suffix-less version will always
> > work.
> >=20
> > When I've done AD reviews of documents that cite IANA URLs, I've =
given
> > the authors that feedback, and suggested the change to the =
suffix-less
> > URLs.  I also intend to suggest to IANA (thanks to a document =
author,
> > and I've since forgotten who it was; sorry) that they post =
permalinks
> > in all the registries, so people will know which URL they ought to
> > use, and not have to guess.
> >=20
> > Barry, Applications AD
> >=20
>=20
>=20


--Apple-Mail=_98D9A809-618E-4943-8EF2-668415AF15AB
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; ">Hi, =
Amanda,<div><br></div><div>In my experience, at some point, IANA was =
instructing authors to replace registry URLs (i.e., URLs to specific =
registries) with a generic pointer to <a =
href=3D"http://www.iana.org">http://www.iana.org</a> instead. This had =
been based on text from RFC&nbsp;5226, namely [1] and =
[2].</div><div><br></div><div>Before that there were URLs identifying =
the registry; and more recently as well, the guidance has been to =
include the suffex-less specific URL pointing to a registry, which is =
great.</div><div><br></div><div>If IANA guarantees that stability, URLs =
pointing to the specific registry are very useful =
IMHO.</div><div><br></div><div>Thanks,</div><div><br></div><div>-- =
Carlos.</div><div><br></div><div>[1]&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc5226#section-4.2">http://tools.ietf.=
org/html/rfc5226#section-4.2</a></div><div>4.2. &nbsp;What to Put in =
Documents That Create a Registry</div><div>...</div><div><div>&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;that it is a part of should be clearly =
identified. &nbsp;When</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;referring to an already existing registry, providing a URL =
to</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;precisely identify the =
registry is helpful. &nbsp;All such URLs,</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;however, will be removed from the RFC prior to =
final</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;publication. &nbsp;For =
example, documents could contain: [TO BE</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;REMOVED: This registration should take place at the =
following</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;location: &nbsp;<a =
href=3D"http://www.iana">http://www.iana</a>.org/assignments/foobar-regist=
ry]</div></div><div><br></div><div>[2]&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc5226#section-5.1">http://tools.ietf.=
org/html/rfc5226#section-5.1</a></div><div>5.1. &nbsp;What to Put in =
Documents When Registering Values</div><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; Note 2: When referring to an existing registry, providing a =
URL</div><div>&nbsp; &nbsp; &nbsp; &nbsp; to precisely identify the =
registry is helpful. &nbsp;Such URLs,</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; however, should usually be removed from the RFC prior to =
final</div><div>&nbsp; &nbsp; &nbsp; &nbsp; publication, since IANA URLs =
are not guaranteed to be stable in</div><div>&nbsp; &nbsp; &nbsp; &nbsp; =
the future. &nbsp;In cases where it is important to include a URL =
in</div><div>&nbsp; &nbsp; &nbsp; &nbsp; the document, IANA should =
concur on its =
inclusion.</div></div><div><br></div><div><br></div><div><br></div><div><b=
r><div><div>On Aug 1, 2013, at 10:10 AM, Amanda Baber &lt;<a =
href=3D"mailto:amanda.baber@icann.org">amanda.baber@icann.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; font-size: 14px; =
"><pre><font face=3D"Calibri">Hi,

The link in RFC3315 is actually incorrect -- it should have been <a =
href=3D"http://www.iana.org/assignments/enterprise-numbers">http://www.ian=
a.org/assignments/enterprise-numbers</a>, without the file extension, =
and there's an erratum about this. HTML was generally (if not =
exclusively) reserved for files that needed to include links to =
registration forms .

As Barry said, we do intend to keep that same short <a =
href=3D"http://www.iana.org/assignments/example">http://www.iana.org/assig=
nments/example</a> format working for every current page, even the =
newly-created ones. We also prefer to see that format used in documents, =
since we can't guarantee that the file extension used for the long =
version won't change. (This information will be appearing on the website =
in some form.)
</font></pre><pre><font face=3D"Calibri">Also, if you find that a =
formerly-valid URL (like one that used to have an .html exception) isn't =
redirecting to the current page, please report it to <a =
href=3D"mailto:iana@iana.org">iana@iana.org</a>. A redirect should have =
been set up. </font></pre><pre><font =
face=3D"Calibri">thanks,</font></pre><pre><font face=3D"Calibri">Amanda =
Baber
IANA Request Specialist
ICANN </font><font face=3D"Calibri,sans-serif">

On Wed Jul 31 14:06:28 2013, <a =
href=3D"mailto:barryleiba@computer.org">barryleiba@computer.org</a> =
wrote:
&gt; &gt; I just followed <a =
href=3D"http://www.iana.org/assignments/enterprise-numbers.html">http://ww=
w.iana.org/assignments/enterprise-numbers.html</a>
&gt; &gt; =46rom RFC3315 (DHCPv6)'s reference section.  Ten years later, =
the URL
&gt; &gt; doesn't work.
&gt; &gt;
&gt; &gt; I know that things were reworked when we went to XML based =
storage, but
&gt; &gt; I thought that the old URLs would at least have a 301 error on =
them.
&gt; &gt;
&gt; &gt; I discovered that dropping the .html gets me the right data =
at:
&gt; &gt;   <a =
href=3D"http://www.iana.org/assignments/enterprise-numbers">http://www.ian=
a.org/assignments/enterprise-numbers</a>
&gt;=20
&gt; Yes: that's the form that IANA would like you to use.  They changed
&gt; their registries from HTML to XML, and the URLs changed.  Supposed
&gt; they should decide to turn them all into JSON (aieeeeeeeee!)... the
&gt; URLs would change again.  But the suffix-less version will always
&gt; work.
&gt;=20
&gt; When I've done AD reviews of documents that cite IANA URLs, I've =
given
&gt; the authors that feedback, and suggested the change to the =
suffix-less
&gt; URLs.  I also intend to suggest to IANA (thanks to a document =
author,
&gt; and I've since forgotten who it was; sorry) that they post =
permalinks
&gt; in all the registries, so people will know which URL they ought to
&gt; use, and not have to guess.
&gt;=20
&gt; Barry, Applications AD
&gt;=20


</font></pre></div>
</blockquote></div><br></div></body></html>=

--Apple-Mail=_98D9A809-618E-4943-8EF2-668415AF15AB--

--Apple-Mail=_2E6D26E8-BCCD-42F0-A0BC-4E9345C65A0E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlH7lBQACgkQtfDPGTp3USwvlgCfSdFBOkCwdELhnDuAhmKntIir
54cAn1XSfGmEyx6Xjtz7p0c3cXwVg4Dn
=Xk3m
-----END PGP SIGNATURE-----

--Apple-Mail=_2E6D26E8-BCCD-42F0-A0BC-4E9345C65A0E--

From hgs@cs.columbia.edu  Fri Aug  2 04:12:45 2013
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C26F211E8273; Fri,  2 Aug 2013 04:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFCOHkKSFWFh; Fri,  2 Aug 2013 04:12:39 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC1621E82D3; Fri,  2 Aug 2013 04:12:29 -0700 (PDT)
Received: from dhcp-559a.meeting.ietf.org (dhcp-559a.meeting.ietf.org [130.129.85.154]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r72BC9Uu018490 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 2 Aug 2013 07:12:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Berlin was awesome, let's come again
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com>
Date: Fri, 2 Aug 2013 07:12:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <82759CF4-3793-47F2-9303-CDADF8C591B2@cs.columbia.edu>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1508)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:12:46 -0000

It seems likely that the VAT problem will affect all European (or at =
least EU) meetings.

On Aug 2, 2013, at 7:04 AM, Yoav Nir <ynir@checkpoint.com> wrote:

> There's the slight matter of $123.50 in VAT.=20
>=20
> To me personally that is minor compared with the much lower price of a =
flight to Germany as compared with a flight to the US. But for people =
working in the US, there's the more expensive flight, and the more =
expensive meeting.
>=20
> Yoav
>=20
> On Aug 2, 2013, at 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:
>=20
>> Venue was great, food options here and in the city were great, =
all-around great experience. Let's come again!
>>=20
>> (I do kinda wonder how there wasn't a single local company willing to =
step up to be the host. That's embarrassing to me as a German, esp. if =
the IETF meets in the self-declared IT hub of Germany. Better luck next =
time, I hope.)
>>=20
>> Lars
>=20
>=20


From rsk@gsp.org  Fri Aug  2 04:17:52 2013
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5177211E82C7 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCDrUl-uYfq6 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:17:45 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFD611E81F6 for <ietf@ietf.org>; Fri,  2 Aug 2013 04:17:44 -0700 (PDT)
Received: from gsp.org (localhost.firemountain.net [127.0.0.1]) by taos.firemountain.net (8.14.7/8.14.7) with SMTP id r72BHfqr008071 for <ietf@ietf.org>; Fri, 2 Aug 2013 07:17:43 -0400 (EDT)
Date: Fri, 2 Aug 2013 07:17:41 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
Message-ID: <20130802111741.GC15609@gsp.org>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com> <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net> <51F7D06A.9080707@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51F7D06A.9080707@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: Fri, 02 Aug 2013 11:17:52 -0000

On Tue, Jul 30, 2013 at 04:40:42PM +0200, Arturo Servin wrote:
>     Captchas? Recaptchas?

Captchas et.al. are completely worthless.  They're defeated at will by
the first adversary who comes along that's willing to expend the minimal
resources required to overcome them.

The best methods for blog comment abuse control seem to be combinations
of network/domain blocks and moderation.  Both have their downsides,
though; the former needs to be custom-crafted for each particular
application and the latter can be time-intensive.   The "trick", if
there is one, is to use layers of these so that each is conservative
about what it blocks (thus keeping the FP rate down) but that each
leaves less work for successive layers to handle (thus keeping the
FN rate down).

---rsk

From joelja@bogus.com  Fri Aug  2 04:18:03 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A721A11E827F; Fri,  2 Aug 2013 04:18:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lMbLw1sBzbei; Fri,  2 Aug 2013 04:18:03 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 221EF11E8303; Fri,  2 Aug 2013 04:18:01 -0700 (PDT)
Received: from dhcp-6518.meeting.ietf.org (dhcp-6518.meeting.ietf.org [130.129.101.24]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r72BHwCp018344 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 2 Aug 2013 11:18:00 GMT (envelope-from joelja@bogus.com)
Message-ID: <51FB9566.7020307@bogus.com>
Date: Fri, 02 Aug 2013 13:17:58 +0200
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:23.0) Gecko/20100101 Thunderbird/23.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: Berlin was awesome, let's come again
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 02 Aug 2013 11:18:00 +0000 (UTC)
Cc: IAOC List <IAOC@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:18:03 -0000

On 8/2/13 12:58 PM, Eggert, Lars wrote:
> Venue was great, food options here and in the city were great, all-around great experience. Let's come again!
>
> (I do kinda wonder how there wasn't a single local company willing to step up to be the host. That's embarrassing to me as a German, esp. if the IETF meets in the self-declared IT hub of Germany. Better luck next time, I hope.)
There were many great sponsors stepped up they should be appreciated for
their generosity. Sometimes it's hard to hard to find a host, that's not
a reflection those who have invested time/energy/capital in making the
meeting a success.
> Lars


From martin.thomson@gmail.com  Fri Aug  2 04:19:29 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2FEB11E80FC; Fri,  2 Aug 2013 04:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.468
X-Spam-Level: 
X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[AWL=0.132,  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 BCX1gGi6Ntd9; Fri,  2 Aug 2013 04:19:29 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C050911E81F6; Fri,  2 Aug 2013 04:19:28 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id x12so409603wgg.24 for <multiple recipients>; Fri, 02 Aug 2013 04:19: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=O8xsRWWD2B9LhbHiKtdWvek0vIzBAhT5mMEl0Rg1Qd8=; b=lVuHFq1+b63PEhJMpG1LeFOGGuivIbwf2Os6UTxYMOkbKlOzqHec/nv0+fObtugif0 FXHJd5AsAI7ANjwkiJ8gOllc4yC0Al502KWfp4D0HMLVaYiDQHNkjpRI+UrEQptPNmgX 3Hr5jzdzsjPoEmmdKkY0iviPhmNb1CBDOqoE/VZMqzxGr4Zv0G5ll+jrPeE2iqFteN8E +G6xchv3Gu5q7UM/mN7X6mfykJYeTs853hED4gxMLyqIvrFgTMcUeotiC6ycwIa5+pST QJ/xxOiZdItiJmnvLby8SgoJKRW1nGHmG/yjI4CMpdE+agM7zLxswglZTbz6iYp9boxH wZFg==
MIME-Version: 1.0
X-Received: by 10.194.78.110 with SMTP id a14mr4503132wjx.84.1375442367929; Fri, 02 Aug 2013 04:19:27 -0700 (PDT)
Received: by 10.194.60.46 with HTTP; Fri, 2 Aug 2013 04:19:27 -0700 (PDT)
In-Reply-To: <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com>
Date: Fri, 2 Aug 2013 13:19:27 +0200
Message-ID: <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Martin Thomson <martin.thomson@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: text/plain; charset=UTF-8
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:19:29 -0000

On 2 August 2013 13:04, Yoav Nir <ynir@checkpoint.com> wrote:
> There's the slight matter of $123.50 in VAT.

This was such a good meeting, I think that I could justify paying
extra to cover VAT.

That is, assuming that the implicit thesis in the above is correct.
Namely, that attendee fee income exceed the meeting costs that also
include VAT such that they can be later recovered.  I'm not sure we
can know the answer to that question just yet, so I'm not certain that
the VAT thing is something that should influence any decision to
return.

From Ted.Lemon@nominum.com  Fri Aug  2 04:21:13 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F21F311E81A6; Fri,  2 Aug 2013 04:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.545
X-Spam-Level: 
X-Spam-Status: No, score=-106.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 xRos8GnVOf9a; Fri,  2 Aug 2013 04:21:05 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 3652021E80AC; Fri,  2 Aug 2013 04:20:59 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUfuWGjIBQOYHz80ff9aLEq3oStGF3m+e@postini.com; Fri, 02 Aug 2013 04:20:59 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B51BB1B8290; Fri,  2 Aug 2013 04:20:58 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id AD7CB190065; Fri,  2 Aug 2013 04:20:58 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 04:20:52 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCOzAA
Date: Fri, 2 Aug 2013 11:20:51 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077523F9B2@mbx-01.win.nominum.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <867D9173613E7345B62179FACC4D06D6@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:21:13 -0000

On Aug 2, 2013, at 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:
> Venue was great, food options here and in the city were great, all-around=
 great experience. Let's come again!

+1

As venues go, this was a good one.


From pthaler@broadcom.com  Fri Aug  2 04:26:36 2013
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FD211E8210; Fri,  2 Aug 2013 04:26:28 -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 0nixYCdAGvby; Fri,  2 Aug 2013 04:26:24 -0700 (PDT)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 080F921E82F9; Fri,  2 Aug 2013 04:26:11 -0700 (PDT)
Received: from [10.9.208.57] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Fri, 02 Aug 2013 04:22:09 -0700
X-Server-Uuid: 06151B78-6688-425E-9DE2-57CB27892261
Received: from SJEXCHCAS06.corp.ad.broadcom.com (10.16.203.14) by IRVEXCHCAS08.corp.ad.broadcom.com (10.9.208.57) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 2 Aug 2013 04:25:59 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS06.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Fri, 2 Aug 2013 04:25:58 -0700
From: "Pat Thaler" <pthaler@broadcom.com>
To: "Russ Housley" <housley@vigilsec.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNreA//+QiUg=
Date: Fri, 2 Aug 2013 11:25:58 +0000
Message-ID: <66B534B0-73FC-4449-8DD3-5DB3A7B50046@broadcom.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>, <A8BA2880-0215-458C-98D7-A8D3F47D62CB@vigilsec.com>
In-Reply-To: <A8BA2880-0215-458C-98D7-A8D3F47D62CB@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
MIME-Version: 1.0
X-WSS-ID: 7DE549EB31W79883971-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:26:36 -0000

Sent from my iPhone

On Aug 2, 2013, at 1:11 PM, "Russ Housley" <housley@vigilsec.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> I have also enjoyed my time in Berlin.  However, we need to complete the =
analysis on the impact of VAT.  I hope there is a way to avoid a cost to ea=
ch participant of an 19%.


> We heard in plenary that VAT clearly applies to conferences, but it may n=
ot apply to standards meeting.
>=20
To clarify, that was an opinion from before any recent rule changes. Whethe=
r the situation has changed is under review ATM.

> Russ
>=20
>=20
> On Aug 2, 2013, at 6:58 AM, Eggert, Lars wrote:
>=20
>> Venue was great, food options here and in the city were great, all-aroun=
d great experience. Let's come again!
>>=20
>> (I do kinda wonder how there wasn't a single local company willing to st=
ep up to be the host. That's embarrassing to me as a German, esp. if the IE=
TF meets in the self-declared IT hub of Germany. Better luck next time, I h=
ope.)
>>=20
>> Lars
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>=20
> iEYEARECAAYFAlH7klgACgkQiuTu0PWcEcu0QQCdG27kU3gnthbQ35aq9esnpQ0k
> SxMAoPvdKtJ8zKbUpcsxPNxKCOAGeiv0
> =3DHRQG
> -----END PGP SIGNATURE-----
>=20


From ynir@checkpoint.com  Fri Aug  2 04:28:28 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5AE921E834B; Fri,  2 Aug 2013 04:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.487
X-Spam-Level: 
X-Spam-Status: No, score=-10.487 tagged_above=-999 required=5 tests=[AWL=0.112, 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 gAWrgcbv2YXz; Fri,  2 Aug 2013 04:28:22 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 2214221E8315; Fri,  2 Aug 2013 04:28:03 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r72BS1vd031369; Fri, 2 Aug 2013 14:28:01 +0300
X-CheckPoint: {51FB97C1-9-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Fri, 2 Aug 2013 14:28:01 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Martin Thomson <martin.thomson@gmail.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmBjwyAgAAEF4CAAAJhAA==
Date: Fri, 2 Aug 2013 11:27:59 +0000
Message-ID: <D099C9C6-83A5-49EC-BB75-16B873FC71C3@checkpoint.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com> <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com>
In-Reply-To: <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.96]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11c9e8f77774a9964406d7a517be324269b0e2f50d
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B364A7E15844814FA62287F2B8B079DF@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:28:28 -0000

On Aug 2, 2013, at 1:19 PM, Martin Thomson <martin.thomson@gmail.com> wrote=
:

> On 2 August 2013 13:04, Yoav Nir <ynir@checkpoint.com> wrote:
>> There's the slight matter of $123.50 in VAT.
>=20
> This was such a good meeting, I think that I could justify paying
> extra to cover VAT.

I agree, but it's easy for me to agree, as all the expense goes to my emplo=
yer.

> That is, assuming that the implicit thesis in the above is correct.
> Namely, that attendee fee income exceed the meeting costs that also
> include VAT such that they can be later recovered.  I'm not sure we
> can know the answer to that question just yet, so I'm not certain that
> the VAT thing is something that should influence any decision to
> return.

In the grand scheme of things, it's less than the room price for one night =
(unless you're staying at some particularly cheap motel, and those are more=
 available in the US).=

From adam@nostrum.com  Fri Aug  2 04:34:53 2013
Return-Path: <adam@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 B39EA11E8241 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RiT7LOXa3fqv for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:34:53 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id ACCEB11E82BE for <ietf@ietf.org>; Fri,  2 Aug 2013 04:34:48 -0700 (PDT)
Received: from dhcp-55a4.meeting.ietf.org (dhcp-55a4.meeting.ietf.org [130.129.85.164]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r72BYdQr012389 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 2 Aug 2013 06:34:41 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <51FB9951.7090700@nostrum.com>
Date: Fri, 02 Aug 2013 13:34:41 +0200
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "Olle E. Johansson" <oej@edvina.net>
Subject: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net>
In-Reply-To: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 130.129.85.164 is authenticated by a trusted mechanism)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:34:53 -0000

Moving to ietf@ietf.org, since I think this is not in any way specific 
to Berlin.


On 8/2/13 12:24, Olle E. Johansson wrote:
> In rtcweb we have remote participants that prefer anonymity for a number of reasons.

I'm going to make a broad assumption that the "number of reasons" all 
relate to privacy. If that is incorrect, please weigh in.

> The question is how this is handled in regards to note well, when they want jabber scribes to relay opinions or proposals to the meeting.
>
> Just a note for the future. I think we should allow anonymous listeners, but should they really be allowed to participate?
>

We had a previous conversation around pseudonyms, which I think 
concluded that pseudonyms are pretty much okay (and impossible to 
reliably detect anyway).

Given this fact, someone can protect their identity through use of a 
consistent pseudonym. This has the property of developing a persona 
behind that pseudonym that the working group members can reasonably 
interact with.

By contrast, attempting to participate in a truly anonymous fashion 
rather than participating with a pseudonym seems to have very little 
justification, with significant potential drawback for the working 
group. The privacy implications are pretty much identical, but it 
provides the illusion that one can act in a way that has no impact on a 
persona's reputation. IMHO, this is ripe for bad behavior, bad faith 
participation, and other abuses.

Given the availability of pseudonymous participation, I don't think we 
need to tolerate anonymous participation.

/a


From jason_livingood@cable.comcast.com  Fri Aug  2 04:49:42 2013
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 9FEFA21E838F; Fri,  2 Aug 2013 04:49:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.064
X-Spam-Level: 
X-Spam-Status: No, score=-103.064 tagged_above=-999 required=5 tests=[AWL=-2.167, 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 mQbOIik0pKLE; Fri,  2 Aug 2013 04:49:36 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 4580521E838D; Fri,  2 Aug 2013 04:49:36 -0700 (PDT)
Received: from ([24.40.56.115]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.60523169; Fri, 02 Aug 2013 07:48:32 -0400
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.158]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Fri, 2 Aug 2013 07:49:28 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCMmMA
Date: Fri, 2 Aug 2013 11:49:27 +0000
Message-ID: <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com>
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [68.87.16.248]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <248669555175A041AF63AC44A7A2051A@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
To: "ietf@ietf.org list" <ietf@ietf.org>
Cc: IAOC List <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:49:42 -0000

+1=20


Very productive venue, easy to access city, several hotels near the venue
for alternatives, walkable area around the venue, lots of options for
restaurants, good public transit system, etc. And I enjoyed the social &
social venue as well (thanks DENIC)!

I really do hope we return in the future - this location really has many
of the things we as participants like.

Thank you very much to all of the sponsors and volunteers!!

Jason

On 8/2/13 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:

>Venue was great, food options here and in the city were great, all-around
>great experience. Let's come again!
>
>(I do kinda wonder how there wasn't a single local company willing to
>step up to be the host. That's embarrassing to me as a German, esp. if
>the IETF meets in the self-declared IT hub of Germany. Better luck next
>time, I hope.)
>
>Lars


From scott.brim@gmail.com  Fri Aug  2 04:49:54 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A58021E83A6; Fri,  2 Aug 2013 04:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 TT7K-fJQfcPF; Fri,  2 Aug 2013 04:49:52 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A3AD021E838D; Fri,  2 Aug 2013 04:49:48 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so578130pdj.29 for <multiple recipients>; Fri, 02 Aug 2013 04:49:48 -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:x-enigmail-version:content-type :content-transfer-encoding; bh=9P5rdI9v9NQbs+WzfPpHj/XfzPsgYHPcmFwQ7T4lYqA=; b=CJQkJWLVRaqk4h0LvU09pm+P+at/nwM41FvxpESasuh2RI2LtciRVRvyHabPDfvLJ8 B/jYXKELzTOzcPdYUccDWB1p5+7UJ+14XeOa89fQqkK8dUl5aW0IvTO/EoeJQhQsaOTA LU6q8xMA5wl1IYb+TDXOUzdrqbcgZ/8+3+k5fZ4IUwf4uhPY4ve5D9+8d0bhmGFe72et FI1RJwzU2KqdVPyeHOf6f3/ZJlDaobQ1B9N8hvtGtB/SfsDyZhRbrbreRC2JgXhScCEe 44jcKadHMOTy+eh1K9v5VIpuVpqbzjRAKoE629yDG5Dt21fHYGPBL1OK4RIb9SrY408g bdBw==
X-Received: by 10.66.235.39 with SMTP id uj7mr9992312pac.122.1375444188385; Fri, 02 Aug 2013 04:49:48 -0700 (PDT)
Received: from dhcp-1668.meeting.ietf.org (dhcp-1668.meeting.ietf.org. [130.129.22.104]) by mx.google.com with ESMTPSA id oj6sm9427245pab.9.2013.08.02.04.49.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 04:49:47 -0700 (PDT)
Message-ID: <51FB9CD8.7040109@gmail.com>
Date: Fri, 02 Aug 2013 13:49:44 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Berlin was awesome, let's come again
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>
In-Reply-To: <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:49:54 -0000

On 08/02/13 13:02, Carsten Bormann allegedly wrote:
> The venue for this meeting was very productive, with few things getting in the way.
> It also simply was pleasant.
> 
> Indeed, let's come again!
> 
> Grüße, Carsten

+1

It would work even in winter.


From glenn.deen@nbcuni.com  Fri Aug  2 04:57:01 2013
Return-Path: <glenn.deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8B3211E81B0 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2g1RAhP3juoO for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:56:54 -0700 (PDT)
Received: from exprod5og115.obsmtp.com (exprod5og115.obsmtp.com [64.18.0.246]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF6B11E82B9 for <ietf@ietf.org>; Fri,  2 Aug 2013 04:56:54 -0700 (PDT)
Received: from alpmlip11.e2k.ad.ge.com ([12.43.191.1]) (using TLSv1) by exprod5ob115.postini.com ([64.18.4.12]) with SMTP ID DSNKUfuehOQTUPY71owqfDuywbtYht4s41fF@postini.com; Fri, 02 Aug 2013 04:56:54 PDT
Received: from unknown (HELO USUSHECWP005.mail.tfayd.com) ([3.156.41.23]) by alpmlip11.e2k.ad.ge.com with ESMTP/TLS/AES128-SHA; 02 Aug 2013 07:56:51 -0400
Received: from USUSHEMWP011.mail.tfayd.com ([169.254.5.153]) by usushecwp005.mail.tfayd.com ([3.156.41.23]) with mapi id 14.03.0146.002; Fri, 2 Aug 2013 04:56:50 -0700
From: "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNiiAgAANFAD//4yk7g==
Date: Fri, 2 Aug 2013 11:56:50 +0000
Message-ID: <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>, <51FB9CD8.7040109@gmail.com>
In-Reply-To: <51FB9CD8.7040109@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
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 list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:57:01 -0000

+1 on visiting Berlin again

-1 on doing it during the winter speaking as a Californian who doesn't even=
 own a winter coat


Sent from my iPad, please forgive any tpyos or auto connections=20

On Aug 2, 2013, at 1:51 PM, "Scott Brim" <scott.brim@gmail.com> wrote:

> On 08/02/13 13:02, Carsten Bormann allegedly wrote:
>> The venue for this meeting was very productive, with few things getting =
in the way.
>> It also simply was pleasant.
>>=20
>> Indeed, let's come again!
>>=20
>> Gr=FC=DFe, Carsten
>=20
> +1
>=20
> It would work even in winter.
>=20

From lars@netapp.com  Fri Aug  2 04:59:05 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4599521E8064 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.953
X-Spam-Level: 
X-Spam-Status: No, score=-4.953 tagged_above=-999 required=5 tests=[AWL=-2.354, 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 JPioFcLl-MCj for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:59:00 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id A02F811E831C for <ietf@ietf.org>; Fri,  2 Aug 2013 04:58:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,800,1367996400";  d="asc'?scan'208";a="38433078"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx11-out.netapp.com with ESMTP; 02 Aug 2013 04:58:34 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.240]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Fri, 2 Aug 2013 04:58:34 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNiiAgAANFAD//4yk7oAAddOA
Date: Fri, 2 Aug 2013 11:58:34 +0000
Message-ID: <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>, <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>
In-Reply-To: <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.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=_80249E53-35B3-4306-AAEC-C7F22203AD99"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:59:05 -0000

--Apple-Mail=_80249E53-35B3-4306-AAEC-C7F22203AD99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Aug 2, 2013, at 13:56, "Deen, Glenn (NBCUniversal)" =
<glenn.deen@nbcuni.com>
 wrote:
> -1 on doing it during the winter speaking as a Californian who doesn't =
even own a winter coat

You are not going to like going to Vancouver for IETF-88...

Lars

--Apple-Mail=_80249E53-35B3-4306-AAEC-C7F22203AD99
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQCVAwUBUfue6tZcnpRveo1xAQIsEwQAhUreHtjLfuu49BBB+ranGZzIhwfRTVWG
R/Rm1tikEFnZj9cUKvwhDT75Doyj25b8TOU9PuU+XEyLpiECZsjX6rYTcTI0goT+
aCfN+GSBGa3ViHE0Hnb3Z1ngXvd87tAcIpWygpCpBc7qQC8TETGFqyNGsO331bN7
aImE+aVzAe8=
=gL4g
-----END PGP SIGNATURE-----

--Apple-Mail=_80249E53-35B3-4306-AAEC-C7F22203AD99--

From listsebby@me.com  Fri Aug  2 04:59:48 2013
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DA4421E837B for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhjdYgHxlEHw for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 04:59:43 -0700 (PDT)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtp001.mac.com [17.158.236.236]) by ietfa.amsl.com (Postfix) with ESMTP id A188221E8379 for <ietf@ietf.org>; Fri,  2 Aug 2013 04:59:26 -0700 (PDT)
Received: from [192.168.1.9] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTPSA id <0MQW004JUJYX0680@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Fri, 02 Aug 2013 11:59:23 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-08-02_04:2013-08-02, 2013-08-02, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1305010000 definitions=main-1308020071
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF-Blog comments (Was Re: setting a goal for an inclusive IETF)
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <20130802111741.GC15609@gsp.org>
Date: Fri, 02 Aug 2013 12:59:19 +0100
Content-transfer-encoding: quoted-printable
Message-id: <9416E99A-6595-46C6-88D5-978B88B9777B@me.com>
References: <EDC539D2-48CE-44D7-A06C-19EEAE42D31C@piuha.net> <51F7CCD5.5080202@gmail.com> <E248EA0A-33AC-4653-9432-89D07B83F9DD@piuha.net> <51F7D06A.9080707@gmail.com> <20130802111741.GC15609@gsp.org>
To: Rich Kulawiec <rsk@gsp.org>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 11:59:48 -0000

On 2 Aug 2013, at 12:17, Rich Kulawiec <rsk@gsp.org> wrote:
> On Tue, Jul 30, 2013 at 04:40:42PM +0200, Arturo Servin wrote:
>>    Captchas? Recaptchas?
>=20
> Captchas et.al. are completely worthless.  They're defeated at will by
> the first adversary who comes along that's willing to expend the =
minimal
> resources required to overcome them.

Yes, indeed, and in the meantime it excludes many people with limited or =
no vision, including me.  There's a rant here, but you don't want to =
hear it right now. :)

FYI I use the service from http://www.skipinput.com/ for my =
CAPTCHA-solving needs.  Works very well, though you need to be aware =
that it uses a browser extension.

> The best methods for blog comment abuse control seem to be =
combinations
> of network/domain blocks and moderation.  Both have their downsides,
> though; the former needs to be custom-crafted for each particular
> application and the latter can be time-intensive.   The "trick", if
> there is one, is to use layers of these so that each is conservative
> about what it blocks (thus keeping the FP rate down) but that each
> leaves less work for successive layers to handle (thus keeping the
> FN rate down).

Without wishing to kill morale, it's not clear to me how important the =
IETF is to our friendly cockroach neighbourhood.  I'll bet that a simple =
question and answer (whose answer is trivial to find on Google) is all =
that we really need to kill comment spam.  There is the authentication =
database at Tools too, of course, and the IETF is quite versed in =
sending challenge emails, so at worst the combination of a Q&A and a =
valid email address should scare off the worst, while leaving guests the =
honour of commenting and leaving familiars almost no work to do at all.

Cheers,
Sabahattin


From henrik@levkowetz.com  Fri Aug  2 05:00:35 2013
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 10B2E21E808F for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ysa5mp3X+mP3 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:00:34 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 3820511E8321 for <ietf@ietf.org>; Fri,  2 Aug 2013 05:00:12 -0700 (PDT)
Received: from localhost ([127.0.0.1]:46106 helo=vigonier.tools.ietf.org ident=henrik) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1V5E1j-0005cs-5w for ietf@ietf.org; Fri, 02 Aug 2013 14:00:11 +0200
Message-ID: <51FB9F4A.2050209@levkowetz.com>
Date: Fri, 02 Aug 2013 14:00:10 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Thanks, and tools work clarification
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: ietf@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:00:35 -0000

Hi,

I'd like to say *thank you* to all of you for the incredible applause you
gave me when I went up to receive the plaque for my contributions as a
datatracker program manager during Wednesday's plenary.  It was incredibly
warming and appreciated.

Afterwards, a number of people have come up to me and wondered if I'm
getting out of the IETF tools business altogether; so I want to clarify
that the reason I asked to be released from the role of program manager
was that I would like to spend more time on coding and design, rather than
managing projects.  I'm hoping that will give me time to contribute more
tools and datatracker enhancement over the coming years, rather than less!


Thank you all again,

	Henrik

From glenn.deen@nbcuni.com  Fri Aug  2 05:05:38 2013
Return-Path: <glenn.deen@nbcuni.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F410811E8319 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:05:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DkHGkKPD+YXx for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:05:28 -0700 (PDT)
Received: from exprod5og106.obsmtp.com (exprod5og106.obsmtp.com [64.18.0.182]) by ietfa.amsl.com (Postfix) with ESMTP id D58F011E8342 for <ietf@ietf.org>; Fri,  2 Aug 2013 05:05:25 -0700 (PDT)
Received: from cinmlip13.e2k.ad.ge.com ([12.71.149.1]) (using TLSv1) by exprod5ob106.postini.com ([64.18.4.12]) with SMTP ID DSNKUfughQwLmJWs3eoqT1sqyd7sWZ1+3Yx2@postini.com; Fri, 02 Aug 2013 05:05:25 PDT
Received: from unknown (HELO USUSHECWP004.mail.tfayd.com) ([3.156.41.22]) by cinmlip13.e2k.ad.ge.com with ESMTP/TLS/AES128-SHA; 02 Aug 2013 08:05:24 -0400
Received: from USUSHEMWP011.mail.tfayd.com ([169.254.5.153]) by usushecwp004.mail.tfayd.com ([3.156.41.22]) with mapi id 14.03.0146.002; Fri, 2 Aug 2013 05:05:23 -0700
From: "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNiiAgAANFAD//4yk7oAAddOA//+Mjyw=
Date: Fri, 2 Aug 2013 12:05:22 +0000
Message-ID: <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>, <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>, <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com>
In-Reply-To: <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-exclaimer-md-config: 47edc00f-f2d6-45ef-be83-8a353bd47e45
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:05:38 -0000

Vancouver will be great. I'm looking forward to it. The pacific helps keep =
it moderate during winter unless you go up in elevation such as the local m=
ountains.=20

Glenn
--------
Sent from my cell, please forgive the typos

On Aug 2, 2013, at 1:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:

> On Aug 2, 2013, at 13:56, "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni=
.com>
> wrote:
>> -1 on doing it during the winter speaking as a Californian who doesn't e=
ven own a winter coat
>=20
> You are not going to like going to Vancouver for IETF-88...
>=20
> Lars

From prvs=9926cf947e=aallen@blackberry.com  Fri Aug  2 05:09:59 2013
Return-Path: <prvs=9926cf947e=aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07D8A11E8346 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.518
X-Spam-Level: 
X-Spam-Status: No, score=-5.518 tagged_above=-999 required=5 tests=[AWL=-0.315, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 FxFKMEcc2kEH for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:09:53 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 778C211E8313 for <ietf@ietf.org>; Fri,  2 Aug 2013 05:09:53 -0700 (PDT)
X-AuditID: 0a41282f-b7f9b6d000002847-dc-51fba18bac6b
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) by mhs060cnc.rim.net (SBG) with SMTP id 66.A1.10311.B81ABF15; Fri,  2 Aug 2013 07:09:47 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.03.0123.003; Fri, 2 Aug 2013 07:09:46 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "glenn.deen@nbcuni.com" <glenn.deen@nbcuni.com>, "lars@netapp.com" <lars@netapp.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCFKGAgAANFACAAAH8AIAAAHwAgAAB5gD//61p6Q==
Date: Fri, 2 Aug 2013 12:09:45 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338DF0D60@XMB104ADS.rim.net>
In-Reply-To: <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.251]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKKsWRmVeSWpSXmKPExsXC5Zyvrdu98HegwZ8JQhZHptxltbjS8J7J 4tnG+SwWL173sDiweCxZ8pPJo3HbdhaPGZ++sHlMW5QZwBLVwGiTlFhSFpyZnqdvZ5OYl5df kliSqpCSWpxsq+STmp6YoxBQlFmWmFyp4JJZnJyTmJmbWqSkkJliq2SipFCQk5icmpuaV2Kr lFhQkJqXomTHpYABbIDKMvMUUvOS81My89JtlTyD/XUtLEwtdQ2V7HQTOnkydjY8ZS2YwVFx 9cFN5gbGM2xdjJwcEgImEk+3X2GCsMUkLtxbDxYXEljJKPHuSwWEvYlR4k2jKIjNJqAlsf/w dKB6Dg4RgSiJb+vdQMLMAk4S7au+MoPYwgKGEpve97BDlBhJnOyvAwmLCIRJzF51jx3EZhFQ kXj6oROsnFfAQ6L37ipGEJtTwE7i6c2FLCA2o4CsxO6z15kgxotL3HoyH+pKAYkle84zQ9ii Ei8f/2OFsBUlZuyZzwpRrydxY+oUNghbW2LZwtdQuwQlTs58wjKBUXQWkrGzkLTMQtIyC0nL AkaWVYyCuRnFBmYGyXnJekWZuXp5qSWbGEHpwlFDfwfj2/cWhxgFOBiVeHjPNf8OFGJNLCuu zD3EKMHBrCTC+2f2r0Ah3pTEyqrUovz4otKc1OJDjK7AkJjILMWdnA9MZXkl8cYGBrg5SuK8 riofAoUE0oFpJzs1tSC1CGYOEwcnyB4uKZFiYPJILUosLcmIB6W4+GJgkpNqYHT4E1vLbv1o w9FJB5cxLp06+4nC0fXWu656R84My5NM5TFNmJP+y6qnLXuX7oPT3hN8y/qOZG3/+IBfX+zZ 0lsS9d92MF8T852X9/fLdqZf4dOUPkgGqATJX5mY6PndxHJH1wW++x9W7Xjk+Kyfla1Xtj4k 5x6TlALTboFDXlYxMreqi+YczlBiKc5INNRiLipOBADKfmUqWAMAAA==
Cc: "cabo@tzi.org" <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: Fri, 02 Aug 2013 12:09:59 -0000

Temperature Moderate - and wet and foggy.

If you like to see the sun then you are unlikely to be happy in Vancouver in=
 November.


----- Original Message -----
From: Deen, Glenn (NBCUniversal) [mailto:glenn.deen@nbcuni.com]
Sent: Friday, August 02, 2013 07:05 AM Central Standard Time=0A=
To: Eggert, Lars <lars@netapp.com>
Cc: Carsten Bormann <cabo@tzi.org>; ietf@ietf.org list <ietf@ietf.org>
Subject: Re: Berlin was awesome, let's come again

Vancouver will be great. I'm looking forward to it. The pacific helps keep i=
t moderate during winter unless you go up in elevation such as the local mou=
ntains. 

Glenn
--------
Sent from my cell, please forgive the typos

On Aug 2, 2013, at 1:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:

> On Aug 2, 2013, at 13:56, "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.=
com>
> wrote:
>> -1 on doing it during the winter speaking as a Californian who doesn't ev=
en own a winter coat
> 
> You are not going to like going to Vancouver for IETF-88...
> 
> Lars

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From scott.brim@gmail.com  Fri Aug  2 05:13:19 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5B911E8313 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:13: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=[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 ctUJGv98c0FC for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:13:17 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5E14911E834B for <ietf@ietf.org>; Fri,  2 Aug 2013 05:13:17 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kl13so608110pab.34 for <ietf@ietf.org>; Fri, 02 Aug 2013 05:13:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=85wPGiCY71iiGfBKC90Uisr3JYBP2YlVPE2c+sgTvsA=; b=JRz2dWb+BAcZzdhiqprtjlHRi9k5IXAgUG9pWv3zDta2Fzt6riqZCA3DTHGP7wtHIw TZYinmhLtS+rN2LvSMBk4keiOLI80AjArxq/gZkrShkJduhjkAYBfrqjiFJ6uqKyRYyo c6zo/pcbqW5IYe5AYRFNar7t3P+OYejGseCR6Ot7FOjCy8yY6qMQ/3UyLoI3g1icdq23 HrMIRjQNMBXnyNv6q8QqS3LUt59HulBytHRizQnHqQNEt8Ui4ADgIfoCHo7nhHm3ZcL+ fbkMZgmC3arvzRL1xx/FEn61KrTIt8sqB7Wv1X1Y4iA553jGg75TzIhuqrJaXWe70f9b hqVA==
X-Received: by 10.66.246.225 with SMTP id xz1mr9943398pac.110.1375445595539; Fri, 02 Aug 2013 05:13:15 -0700 (PDT)
Received: from dhcp-1668.meeting.ietf.org (dhcp-1668.meeting.ietf.org. [130.129.22.104]) by mx.google.com with ESMTPSA id yg1sm7664740pbb.1.2013.08.02.05.13.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 05:13:08 -0700 (PDT)
Message-ID: <51FBA251.9040804@gmail.com>
Date: Fri, 02 Aug 2013 14:13:05 +0200
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Adam Roach <adam@nostrum.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com>
In-Reply-To: <51FB9951.7090700@nostrum.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Olle E. Johansson" <oej@edvina.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:13:19 -0000

I'm completely against participating anonymously because of IPR issues.
 I'm mostly against pseudonymous participation for the same reason.  I
need to be able to know who I'm dealing with, in order to know if there
are IPR issues that should be brought up.

From mary.h.barnes@gmail.com  Fri Aug  2 05:32:02 2013
Return-Path: <mary.h.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 34BD211E8313 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.448
X-Spam-Level: 
X-Spam-Status: No, score=-102.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, 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 xfHgL7kI4FSr for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:31:37 -0700 (PDT)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 30FF211E82B8 for <ietf@ietf.org>; Fri,  2 Aug 2013 05:31:26 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id b10so561958vea.7 for <ietf@ietf.org>; Fri, 02 Aug 2013 05:31: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=RncUaRcX3W9S+SSycUpbo9iSBXcUxDq2THhNIhBn5YY=; b=iO92JNNAl7LKpwKKj7s2IXrTtZCPGlfBry7OGslmiuvjL/IezuZYZbapsby1w3P/8J kh958t1lZtBkhhlQejE3OGCyOq3LtrUacA2yZsx/62GGikd5u8hjMucXxMC4VxbWy7Yq YTyOs8LpQc0IkpEFxnOXMZaV93zGgZC4WNp/uDA2lN0OuET2s7I3fEPlYbivXRyQU+Dq m0VybxxKsTfDekmkwvzY5zGgO5hBtRnfuIKrBBSf2KP6MruHfyIdckHW2OnxMvbVI6sD 4BPzEo8eyHb9lc0UQ1mX6vlf0T2yhuSH/zyVdrXmvBXRJiowAt6T8DHLJP4Zlrt02Lo+ dPiA==
MIME-Version: 1.0
X-Received: by 10.58.171.4 with SMTP id aq4mr1938877vec.26.1375446685572; Fri, 02 Aug 2013 05:31:25 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Fri, 2 Aug 2013 05:31:25 -0700 (PDT)
In-Reply-To: <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org> <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com> <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com> <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com>
Date: Fri, 2 Aug 2013 07:31:25 -0500
Message-ID: <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Mary Barnes <mary.h.barnes@gmail.com>
To: "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.com>
Content-Type: multipart/alternative; boundary=047d7b6743b419e4fa04e2f62390
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:32:02 -0000

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

It was snowing the last time we were in Vancouver.  While the snow melted
quickly, the temp was quite brisk.  There are many restaurants within
walking distance so you would be wise to bring some layers of outerwear
along with gloves, a hat and scarf.

Mary

On Friday, August 2, 2013, Deen, Glenn (NBCUniversal) wrote:

> Vancouver will be great. I'm looking forward to it. The pacific helps keep
> it moderate during winter unless you go up in elevation such as the local
> mountains.
>
> Glenn
> --------
> Sent from my cell, please forgive the typos
>
> On Aug 2, 2013, at 1:58 PM, "Eggert, Lars" <lars@netapp.com <javascript:;>>
> wrote:
>
> > On Aug 2, 2013, at 13:56, "Deen, Glenn (NBCUniversal)" <
> glenn.deen@nbcuni.com <javascript:;>>
> > wrote:
> >> -1 on doing it during the winter speaking as a Californian who doesn't
> even own a winter coat
> >
> > You are not going to like going to Vancouver for IETF-88...
> >
> > Lars
>

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

It was snowing the last time we were in Vancouver. =A0While the snow melted=
 quickly, the temp was quite brisk. =A0There are many restaurants within wa=
lking distance so you would be wise to bring some layers of outerwear along=
 with gloves, a hat and scarf.<div>
<br></div><div>Mary<span></span><br><br>On Friday, August 2, 2013, Deen, Gl=
enn (NBCUniversal)  wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Vancouver will=
 be great. I&#39;m looking forward to it. The pacific helps keep it moderat=
e during winter unless you go up in elevation such as the local mountains.<=
br>

<br>
Glenn<br>
--------<br>
Sent from my cell, please forgive the typos<br>
<br>
On Aug 2, 2013, at 1:58 PM, &quot;Eggert, Lars&quot; &lt;<a href=3D"javascr=
ipt:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;lars@netapp.com&#39;)">lar=
s@netapp.com</a>&gt; wrote:<br>
<br>
&gt; On Aug 2, 2013, at 13:56, &quot;Deen, Glenn (NBCUniversal)&quot; &lt;<=
a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;glenn.dee=
n@nbcuni.com&#39;)">glenn.deen@nbcuni.com</a>&gt;<br>
&gt; wrote:<br>
&gt;&gt; -1 on doing it during the winter speaking as a Californian who doe=
sn&#39;t even own a winter coat<br>
&gt;<br>
&gt; You are not going to like going to Vancouver for IETF-88...<br>
&gt;<br>
&gt; Lars<br>
</blockquote></div>

--047d7b6743b419e4fa04e2f62390--

From jari.arkko@piuha.net  Fri Aug  2 05:36:14 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3B111E8319; Fri,  2 Aug 2013 05:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id caNgX7gfQF2r; Fri,  2 Aug 2013 05:35:41 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 54FBA11E81A5; Fri,  2 Aug 2013 05:34:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 121E82CC5D; Fri,  2 Aug 2013 15:34:24 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bdyn2uYc-mc; Fri,  2 Aug 2013 15:34:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 759762CC48; Fri,  2 Aug 2013 15:34:23 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Berlin was awesome, let's come again
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com>
Date: Fri, 2 Aug 2013 14:34:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <34C821B7-3B25-42F3-A396-31A6806D94EC@piuha.net>
References: <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
X-Mailer: Apple Mail (2.1508)
Cc: IAOC List <iaoc@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:36:18 -0000

> Very productive venue, easy to access city, several hotels near the =
venue
> for alternatives, walkable area around the venue, lots of options for
> restaurants, good public transit system, etc. And I enjoyed the social =
&
> social venue as well (thanks DENIC)!
>=20
> I really do hope we return in the future - this location really has =
many
> of the things we as participants like.
>=20
> Thank you very much to all of the sponsors and volunteers!!

Jason said it better than I can. Absolutely agree.

The other thing that I wanted to say was that I'd caution people for =
jumping into simplistic conclusions about the VAT. Companies generally =
can recover VAT, for instance, of the expenses their employees have. But =
I'm not a VAT lawyer, so YMMV.=20

Jari


From ole@cisco.com  Fri Aug  2 05:39:42 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA4B311E831C for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.297
X-Spam-Level: 
X-Spam-Status: No, score=-110.297 tagged_above=-999 required=5 tests=[AWL=0.302, 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 bNmA+QDAd29N for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:39:37 -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 3EB6111E8321 for <ietf@ietf.org>; Fri,  2 Aug 2013 05:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=538; q=dns/txt; s=iport; t=1375447177; x=1376656777; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=IhQk0234HC5R+RaEdFEuupH7OSGx9r+2cT5/WJzq90E=; b=eABFsSYc6dJpQDxljvPj2Uc3/i4t72F78fO9ZTlYVjsIK1MT76s7nTHr HmVZsQT1YinyOuynxZvjINVsQnxzoPGP2jDlT0/mZnVWQ8zW1c+o37/w9 cU3Jco7S3Gz/bNpnQJ6YydcWo9mnemlaiT7OeGfxmzRvQKseJpqKoQG+u 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjAFAL6n+1GrRDoH/2dsb2JhbABagwY2vyGBHBZ0giQBAQEDATo/BQsLRlcGiB0FuS+QGAeEDQOJKpRZiyqDNxw
X-IronPort-AV: E=Sophos;i="4.89,801,1367971200"; d="scan'208";a="88265521"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-2.cisco.com with ESMTP; 02 Aug 2013 12:39:36 +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 r72CdZSD027950 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Aug 2013 12:39:35 GMT
Date: Fri, 2 Aug 2013 05:39:35 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Mary Barnes <mary.h.barnes@gmail.com>
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com>
Message-ID: <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org> <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com> <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com> <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com> <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@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: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org 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, 02 Aug 2013 12:39:42 -0000

On Fri, 2 Aug 2013, Mary Barnes wrote:

> It was snowing the last time we were in Vancouver.  While the snow melted
> quickly, the temp was quite brisk.  There are many restaurants within
> walking distance so you would be wise to bring some layers of outerwear
> along with gloves, a hat and scarf.
> 
> Mary
> 

No, last time we were in Vancouver was August last year. It was 
actually quite hot on some days and it most certainly DID not snow.

If you mean "last time we were in Vancouver in NOVEMBER, then yes.

Ole

From adrian@olddog.co.uk  Fri Aug  2 05:50:56 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 887D921E810A for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  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 Qojhn4NRVwgq for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:50:47 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 7752A21E824D for <ietf@ietf.org>; Fri,  2 Aug 2013 05:48:56 -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 r72CmqSv002636;  Fri, 2 Aug 2013 13:48:52 +0100
Received: from 950129200 (dhcp-13f0.meeting.ietf.org [130.129.19.240]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r72CmjOe002622 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Aug 2013 13:48:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ole Jacobsen'" <ole@cisco.com>, "'Mary Barnes'" <mary.h.barnes@gmail.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>	<74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>	<51FB9CD8.7040109@gmail.com>	<EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>	<4924C546-2C2A-4282-A126-096AAEE24173@netapp.com>	<F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com>	<CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com> <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
Subject: RE: Berlin was awesome, let's come again
Date: Fri, 2 Aug 2013 13:48:44 +0100
Message-ID: <00bd01ce8f7e$a3ad2dd0$eb078970$@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: AQJs3yGVraLECT2C5emyr5pMWHC4jAHVO8CXAt4iPvoB3mOE9gJdJmThAluJhGICMAZ64gGBGr0nl81g3+A=
Content-Language: en-gb
Cc: 'Carsten Bormann' <cabo@tzi.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: Fri, 02 Aug 2013 12:50:57 -0000

Mutter.

IETF 87
It was warm in Berlin

IETF 84 
Hot sun. Got sunburn on Saturday before IETF

IETF 70
Snowed a little in Vancouver. Reasonable skiing the week after.

IETF 64
Rain, rain, more rain. Got very wet feet walking from non-IETF hotel. Bought
boots.

Adrian


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Ole
> Jacobsen
> Sent: 02 August 2013 13:40
> To: Mary Barnes
> Cc: Carsten Bormann; ietf@ietf.org list
> Subject: Re: Berlin was awesome, let's come again
> 
> 
> On Fri, 2 Aug 2013, Mary Barnes wrote:
> 
> > It was snowing the last time we were in Vancouver.  While the snow melted
> > quickly, the temp was quite brisk.  There are many restaurants within
> > walking distance so you would be wise to bring some layers of outerwear
> > along with gloves, a hat and scarf.
> >
> > Mary
> >
> 
> No, last time we were in Vancouver was August last year. It was
> actually quite hot on some days and it most certainly DID not snow.
> 
> If you mean "last time we were in Vancouver in NOVEMBER, then yes.
> 
> Ole


From mary.h.barnes@gmail.com  Fri Aug  2 05:53:45 2013
Return-Path: <mary.h.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 261A821E80B4; Fri,  2 Aug 2013 05:53:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, 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 e6LlaGpLOADN; Fri,  2 Aug 2013 05:53:42 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2FC11E8317; Fri,  2 Aug 2013 05:53:22 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id cz11so586920veb.36 for <multiple recipients>; Fri, 02 Aug 2013 05:53:22 -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=sOPaFCogacuV0rNPDoFiVC18C05kTDpznRZuc3Psf0c=; b=XrrDj+rSIhu/WHFkS3xsKAPcKNjozcfRw2iovpEjWDaY6eAj18lY3vAISCN5RANhKy fzM720AtlNE5NDBTitfcN4gFQKeI8y7a4b+dTVQIsZeiDfiz6CbqifZpRgOMBtPCQ7/b 6cJHHCDvLuOtIUNou9xJ6h8PLhUr8UXdaNr8C2soeUTKRhMP4q2SGbGfi4GeUYGTFIkb KXrmE4cQb4ZjHCMbYe0VEkRSvaqpLkRgTYR2EbvldCS+3vTDJ8lUlR9xg1Zj0j74GNEj 5X+6dHeHkcENyEuOUsgID4M7uj4QeGpYTV2FBTG4sXGIFEY2vbWXWGMvWIyDcsxvwkbA O5iA==
MIME-Version: 1.0
X-Received: by 10.58.248.40 with SMTP id yj8mr1986372vec.40.1375448001917; Fri, 02 Aug 2013 05:53:21 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Fri, 2 Aug 2013 05:53:21 -0700 (PDT)
In-Reply-To: <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com>
Date: Fri, 2 Aug 2013 07:53:21 -0500
Message-ID: <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Mary Barnes <mary.h.barnes@gmail.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Content-Type: multipart/alternative; boundary=047d7bf0ddf48fbb7204e2f671dc
Cc: IAOC List <iaoc@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:53:45 -0000

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

Overall, I agree that it was a good venue for getting work done overall.
>From my perspective, I would have preferred all the rooms be around the
temperature that we had in the Charlottenbergs.  Also, food was very hit or
miss for me.  The hotel breakfast was fine.   I had two dinners that I am
confident were GF - one I had Lars to translate and the other was a
restaurant that specializes in GF.  The catering at the receptions was also
fairly decent in that respect.  The food served at snacks wasn't acceptable
other than Monday, when they  plenty of nice veggies.  The only other day
they had veggies, they ran out well before the cookies.  The snacks with
sandwiches didn't work at all. Yesterday when they had cheese and crackers
- there was a huge issue with cross contamination.   However, since there
were nearby markets that wasn't that big of a deal.

I did have some annoyances with the housekeeping, in particular the
 rewashing of glasses/mugs in the bathroom sink and someone else's soap bar
ending up in my bathroom.

The social was great overall.

Mary.



On Fri, Aug 2, 2013 at 6:49 AM, Livingood, Jason <
Jason_Livingood@cable.comcast.com> wrote:

> +1
>
>
> Very productive venue, easy to access city, several hotels near the venue
> for alternatives, walkable area around the venue, lots of options for
> restaurants, good public transit system, etc. And I enjoyed the social &
> social venue as well (thanks DENIC)!
>
> I really do hope we return in the future - this location really has many
> of the things we as participants like.
>
> Thank you very much to all of the sponsors and volunteers!!
>
> Jason
>
> On 8/2/13 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:
>
> >Venue was great, food options here and in the city were great, all-around
> >great experience. Let's come again!
> >
> >(I do kinda wonder how there wasn't a single local company willing to
> >step up to be the host. That's embarrassing to me as a German, esp. if
> >the IETF meets in the self-declared IT hub of Germany. Better luck next
> >time, I hope.)
> >
> >Lars
>
>

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

<div dir=3D"ltr">Overall, I agree that it was a good venue for getting work=
 done overall. From my perspective, I would have preferred all the rooms be=
 around the temperature that we had in the Charlottenbergs. =A0Also, food w=
as very hit or miss for me. =A0The hotel breakfast was fine. =A0 I had two =
dinners that I am confident were GF - one I had Lars to translate and the o=
ther was a restaurant that specializes in GF. =A0The catering at the recept=
ions was also fairly decent in that respect. =A0The food served at snacks w=
asn&#39;t acceptable other than Monday, when they =A0plenty of nice veggies=
. =A0The only other day they had veggies, they ran out well before the cook=
ies. =A0The snacks with sandwiches didn&#39;t work at all. Yesterday when t=
hey had cheese and crackers - there was a huge issue with cross contaminati=
on. =A0 However, since there were nearby markets that wasn&#39;t that big o=
f a deal.=A0<div>
<br></div><div>I did have some annoyances with the housekeeping, in particu=
lar the =A0rewashing of glasses/mugs in the bathroom sink and someone else&=
#39;s soap bar ending up in my bathroom.=A0<br><div><br></div><div>The soci=
al was great overall.</div>
<div><br></div><div>Mary.=A0</div><div><br></div><div><br><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Fri, Aug 2, 2013 at 6:49 AM, Li=
vingood, Jason <span dir=3D"ltr">&lt;<a href=3D"mailto:Jason_Livingood@cabl=
e.comcast.com" target=3D"_blank">Jason_Livingood@cable.comcast.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">+1<br>
<br>
<br>
Very productive venue, easy to access city, several hotels near the venue<b=
r>
for alternatives, walkable area around the venue, lots of options for<br>
restaurants, good public transit system, etc. And I enjoyed the social &amp=
;<br>
social venue as well (thanks DENIC)!<br>
<br>
I really do hope we return in the future - this location really has many<br=
>
of the things we as participants like.<br>
<br>
Thank you very much to all of the sponsors and volunteers!!<br>
<br>
Jason<br>
<br>
On 8/2/13 12:58 PM, &quot;Eggert, Lars&quot; &lt;<a href=3D"mailto:lars@net=
app.com" target=3D"_blank">lars@netapp.com</a>&gt; wrote:<br>
<br>
&gt;Venue was great, food options here and in the city were great, all-arou=
nd<br>
&gt;great experience. Let&#39;s come again!<br>
&gt;<br>
&gt;(I do kinda wonder how there wasn&#39;t a single local company willing =
to<br>
&gt;step up to be the host. That&#39;s embarrassing to me as a German, esp.=
 if<br>
&gt;the IETF meets in the self-declared IT hub of Germany. Better luck next=
<br>
&gt;time, I hope.)<br>
&gt;<br>
&gt;Lars<br>
<br>
</blockquote></div><br></div></div></div></div>

--047d7bf0ddf48fbb7204e2f671dc--

From grmocg@gmail.com  Fri Aug  2 05:55:04 2013
Return-Path: <grmocg@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B891821F9EA9 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:55:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 hOSXkt758YSy for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:55:00 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2ADA021F9F7F for <ietf@ietf.org>; Fri,  2 Aug 2013 05:54:23 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id ef5so1097383obb.9 for <ietf@ietf.org>; Fri, 02 Aug 2013 05:54: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=2NX19SHkvk3mM+jpT9es9cdwNkZ0yDk98sbN3eGa5oA=; b=a7iQsGvcRJaOCxrYtVYOLl9EM0i+u8opXI4uqGRpl8Asw6ESKHmYycuW7dJx5K37tX 24aHmJQpxS+rnrYb9TCFrjoSh3Cxkouxxl71Ar5yD4+UbdNcjl2H9ul/ovTUd+7Srvbi 9CS4BIqrBTS1wkBPPMDFMTr7H0AmUJKbD+QGSI7U2uTlWQVQpcsxS0rfzhS0mwebTZKr COf6tX9CLOv2uLrMwDZMn2FqV79KXSNmfZ2APjYrpWQGi2EZWBAdjFRVV2T9X5BEVuSY O6ltBp8wP1FvD12X1MgAKx4Qjz21vatmDA8O7LO8A0yJfuF7TZIdn2m1Y1RXEiPvDpua bG3w==
MIME-Version: 1.0
X-Received: by 10.60.149.202 with SMTP id uc10mr5168717oeb.12.1375448057697; Fri, 02 Aug 2013 05:54:17 -0700 (PDT)
Received: by 10.76.91.229 with HTTP; Fri, 2 Aug 2013 05:54:17 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org> <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com> <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com> <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com> <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com> <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Fri, 2 Aug 2013 14:54:17 +0200
Message-ID: <CAP+FsNdo28izmm89Z5L9-2-uefpCfnEA08LhbJ96AeZS+3eyWA@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Roberto Peon <grmocg@gmail.com>
To: Ole Jacobsen <ole@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b41c580e2e4da04e2f67411
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:55:04 -0000

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

I'd just prefer a venue where we had temps in the various
conference/meeting rooms and facilities which were reliably below 80
degrees Fahrenheit.

I looked around a number of times while in various meetings, and a large
number of people were sweating (including myself).

-=R


On Fri, Aug 2, 2013 at 2:39 PM, Ole Jacobsen <ole@cisco.com> wrote:

>
> On Fri, 2 Aug 2013, Mary Barnes wrote:
>
> > It was snowing the last time we were in Vancouver.  While the snow melted
> > quickly, the temp was quite brisk.  There are many restaurants within
> > walking distance so you would be wise to bring some layers of outerwear
> > along with gloves, a hat and scarf.
> >
> > Mary
> >
>
> No, last time we were in Vancouver was August last year. It was
> actually quite hot on some days and it most certainly DID not snow.
>
> If you mean "last time we were in Vancouver in NOVEMBER, then yes.
>
> Ole
>

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

<div dir=3D"ltr">I&#39;d just prefer a venue where we had temps in the vari=
ous conference/meeting rooms and facilities which were reliably below 80 de=
grees Fahrenheit.<div><br></div><div>I looked around a number of times whil=
e in various meetings, and a large number of people were sweating (includin=
g myself).</div>
<div><br></div><div>-=3DR</div></div><div class=3D"gmail_extra"><br><br><di=
v class=3D"gmail_quote">On Fri, Aug 2, 2013 at 2:39 PM, Ole Jacobsen <span =
dir=3D"ltr">&lt;<a href=3D"mailto:ole@cisco.com" target=3D"_blank">ole@cisc=
o.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
On Fri, 2 Aug 2013, Mary Barnes wrote:<br>
<br>
&gt; It was snowing the last time we were in Vancouver. =A0While the snow m=
elted<br>
&gt; quickly, the temp was quite brisk. =A0There are many restaurants withi=
n<br>
&gt; walking distance so you would be wise to bring some layers of outerwea=
r<br>
&gt; along with gloves, a hat and scarf.<br>
&gt;<br>
&gt; Mary<br>
&gt;<br>
<br>
</div>No, last time we were in Vancouver was August last year. It was<br>
actually quite hot on some days and it most certainly DID not snow.<br>
<br>
If you mean &quot;last time we were in Vancouver in NOVEMBER, then yes.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Ole<br>
</font></span></blockquote></div><br></div>

--047d7b41c580e2e4da04e2f67411--

From mary.h.barnes@gmail.com  Fri Aug  2 05:55:07 2013
Return-Path: <mary.h.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 301FF21F9EA9 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, 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 erY4cKjP6fxP for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 05:55:04 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4814B11E8335 for <ietf@ietf.org>; Fri,  2 Aug 2013 05:54:23 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id d10so580704vea.5 for <ietf@ietf.org>; Fri, 02 Aug 2013 05:54:15 -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=g/ycyvXD3JYI/5xT0jrOdY6LZwUWyA7z6lWSJoPE0qQ=; b=x8pGLvhWwr9zuuUQO/RtxkQLmOKRhQueRI4ooZlqMzaDYfbcZ/LUiEmPvtuavQHO8M 8IlCEHtaKyWQOLj7Ox8YFYmsxVqR0pK3GCA1oTqNEb9zXzIcOY13sYhzEj1SxYyfIYT3 KYLVmZ68m+9qTDyUJoqbP1FBUZjLh9HuQ8WvHFYiPpuZumpA3H9lyk1ps9e1m2Bwd9gg 4x55d2a+xAPafyV+JS+hc9lkb4seKVL1xb+aZ/K57Kbe4XMH2fSaMxxW2Nmj68XJnnqE 4z2b61wRyKolfY9c4NXQLNdigbJqWZZI5wZyrn9pW5ny7/eKrXiqAguZeVHqMc/tm0yy g0oQ==
MIME-Version: 1.0
X-Received: by 10.58.80.38 with SMTP id o6mr1994847vex.69.1375448055121; Fri, 02 Aug 2013 05:54:15 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Fri, 2 Aug 2013 05:54:14 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org> <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com> <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com> <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com> <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com> <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Fri, 2 Aug 2013 07:54:14 -0500
Message-ID: <CABmDk8mxOaspCJFtbCadyvqC8genZ4D_hfQ1ishjffS1DaQHjA@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Ole Jacobsen <ole@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b5d48a6bb8c4e04e2f674e6
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 12:55:07 -0000

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

Yes, I meant to say the last time we were there in November (since that was
what we were talking about).


On Fri, Aug 2, 2013 at 7:39 AM, Ole Jacobsen <ole@cisco.com> wrote:

>
> On Fri, 2 Aug 2013, Mary Barnes wrote:
>
> > It was snowing the last time we were in Vancouver.  While the snow melted
> > quickly, the temp was quite brisk.  There are many restaurants within
> > walking distance so you would be wise to bring some layers of outerwear
> > along with gloves, a hat and scarf.
> >
> > Mary
> >
>
> No, last time we were in Vancouver was August last year. It was
> actually quite hot on some days and it most certainly DID not snow.
>
> If you mean "last time we were in Vancouver in NOVEMBER, then yes.
>
> Ole
>

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

<div dir=3D"ltr">Yes, I meant to say the last time we were there in Novembe=
r (since that was what we were talking about).</div><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote">On Fri, Aug 2, 2013 at 7:39 AM, Ole =
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"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
On Fri, 2 Aug 2013, Mary Barnes wrote:<br>
<br>
&gt; It was snowing the last time we were in Vancouver. =A0While the snow m=
elted<br>
&gt; quickly, the temp was quite brisk. =A0There are many restaurants withi=
n<br>
&gt; walking distance so you would be wise to bring some layers of outerwea=
r<br>
&gt; along with gloves, a hat and scarf.<br>
&gt;<br>
&gt; Mary<br>
&gt;<br>
<br>
</div>No, last time we were in Vancouver was August last year. It was<br>
actually quite hot on some days and it most certainly DID not snow.<br>
<br>
If you mean &quot;last time we were in Vancouver in NOVEMBER, then yes.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Ole<br>
</font></span></blockquote></div><br></div>

--047d7b5d48a6bb8c4e04e2f674e6--

From Ted.Lemon@nominum.com  Fri Aug  2 06:00:25 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF5B21F91B7 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 06:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.55
X-Spam-Level: 
X-Spam-Status: No, score=-106.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 D17sbLs8sXx3 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 06:00:17 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 51A3211E8342 for <ietf@ietf.org>; Fri,  2 Aug 2013 06:00:12 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUfutV9mFODdmUO/XPtY5TOEn0L4ZIP7C@postini.com; Fri, 02 Aug 2013 06:00:12 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3B6F71B8291 for <ietf@ietf.org>; Fri,  2 Aug 2013 06:00:07 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 30E4D190065; Fri,  2 Aug 2013 06:00:07 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 2 Aug 2013 06:00:07 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Roberto Peon <grmocg@gmail.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNiiAgAANFAD//4yk7oAAddOA//+MjyyAAHyggIAAAkiAgAAEG4CAAAGmgA==
Date: Fri, 2 Aug 2013 13:00:06 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077523FF8E@mbx-01.win.nominum.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org> <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com> <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com> <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com> <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com> <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net> <CAP+FsNdo28izmm89Z5L9-2-uefpCfnEA08LhbJ96AeZS+3eyWA@mail.gmail.com>
In-Reply-To: <CAP+FsNdo28izmm89Z5L9-2-uefpCfnEA08LhbJ96AeZS+3eyWA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <15BF7228FE1B484294211ABDB63F3B4C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.org>, Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:00:25 -0000

On Aug 2, 2013, at 2:54 PM, Roberto Peon <grmocg@gmail.com> wrote:
> I'd just prefer a venue where we had temps in the various conference/meet=
ing rooms and facilities which were reliably below 80 degrees Fahrenheit.

So, Autumn IETF in Berlin?

:)


From grmocg@gmail.com  Fri Aug  2 06:04:29 2013
Return-Path: <grmocg@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2628311E8342 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 06:04:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 0p6bWYkvD8Ju for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 06:04:28 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id A605D11E8339 for <ietf@ietf.org>; Fri,  2 Aug 2013 06:04:28 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k18so1281873oag.12 for <ietf@ietf.org>; Fri, 02 Aug 2013 06:04:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+K2swTVrowprH5JD+Y/6KL4+nAgtKOh5ZEIZwtC0Q4o=; b=Aa9JKTHLQzLHbdU0zzplU7kdX0lAn+GzSdbcvLjXCfrbLwBKI/+5Tzo7pN5ep3z6KS 6EoEHIATLK5bjgL69ctP8WcDBS+6VVAsbAiFGXxtgoiw1bJJA/Ql62ociEQ8i1pVzNWB 419FIfO4/M1WVZ1gz5XJWtizeQIEjWWlh2kXcOve9k02lCmbgQfL2/af2GvHYrc3Q7mR 5Xx4Ngmnp4WkZ5PmZgOcqbF82CsOXcHs0BnUUV+vIgfQ6kifNuXXbgf9dIQZvtWiWkgk +ehZu+UC/q8S44OutIgHnstMHJg0Q1SAUx2LFXt0rIFx9C62OD261VJpbXak4AjhE1op vE2A==
MIME-Version: 1.0
X-Received: by 10.182.71.38 with SMTP id r6mr5100296obu.64.1375448668115; Fri, 02 Aug 2013 06:04:28 -0700 (PDT)
Received: by 10.76.91.229 with HTTP; Fri, 2 Aug 2013 06:04:28 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077523FF8E@mbx-01.win.nominum.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org> <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com> <4924C546-2C2A-4282-A126-096AAEE24173@netapp.com> <F8D50767-7FAE-46D7-B150-A19575C53511@nbcuni.com> <CABmDk8=cS8YxxvetX9hX=GyUE57d=NXaQ5xn9u2XSkL-eERyhQ@mail.gmail.com> <alpine.OSX.2.01.1308020538010.66901@173-11-110-132-sfba.hfc.comcastbusiness.net> <CAP+FsNdo28izmm89Z5L9-2-uefpCfnEA08LhbJ96AeZS+3eyWA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523FF8E@mbx-01.win.nominum.com>
Date: Fri, 2 Aug 2013 15:04:28 +0200
Message-ID: <CAP+FsNdXrL_09p3oe=NU5YaYVTDo7Ma3pu7kPJTkV3Uw7BBrig@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Roberto Peon <grmocg@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=e89a8fb1f56c451d7004e2f699c3
Cc: Carsten Bormann <cabo@tzi.org>, Ole Jacobsen <ole@cisco.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:04:29 -0000

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

I'd even settle for winter. I can wear a coat, if necessary.
Carrying an effective AC is far less practical, to say nothing of the
extension cord...

-=R


On Fri, Aug 2, 2013 at 3:00 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 2, 2013, at 2:54 PM, Roberto Peon <grmocg@gmail.com> wrote:
> > I'd just prefer a venue where we had temps in the various
> conference/meeting rooms and facilities which were reliably below 80
> degrees Fahrenheit.
>
> So, Autumn IETF in Berlin?
>
> :)
>
>

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

<div dir=3D"ltr">I&#39;d even settle for winter. I can wear a coat, if nece=
ssary.<div>Carrying an effective AC is far less practical, to say nothing o=
f the extension cord...<div><br></div><div>-=3DR</div></div></div><div clas=
s=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Fri, Aug 2, 2013 at 3:00 PM, Ted Lemo=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"=
_blank">Ted.Lemon@nominum.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">On Aug 2, 2013, at 2:54 PM, Roberto Peon &lt;<a href=3D"m=
ailto:grmocg@gmail.com">grmocg@gmail.com</a>&gt; wrote:<br>
&gt; I&#39;d just prefer a venue where we had temps in the various conferen=
ce/meeting rooms and facilities which were reliably below 80 degrees Fahren=
heit.<br>
<br>
</div>So, Autumn IETF in Berlin?<br>
<br>
:)<br>
<br>
</blockquote></div><br></div>

--e89a8fb1f56c451d7004e2f699c3--

From scott.brim@gmail.com  Fri Aug  2 06:14:02 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17F3C21E8128; Fri,  2 Aug 2013 06:14:02 -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 0BpyeKq3Wqql; Fri,  2 Aug 2013 06:14:01 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 8574321E80D8; Fri,  2 Aug 2013 06:14:01 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id er7so1111234obc.17 for <multiple recipients>; Fri, 02 Aug 2013 06:14: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:from:date:message-id:subject:to :cc:content-type; bh=Ocvb7Hr92wTF/Pm/bRwM92QbRr8lT4Zj0QRFb5NhQ4A=; b=KAt3JrqFGnPBWRcDaQ/wUv2EJEcQng5HSqNVi4C8t+8clgmtaWmAtb52vo/9HHuQGD GorpOVqSyFjgOb7GIiMvpTrT3mHDP0SnHzDdDeB6ZtFGCsfPl2/BZftRHktiHDxfkKux pX5PGWsrD/YXPh3V/cDyOr69Kopw8VnCIyMfmx23SIkWcBvWqOqo1x+2il8sLILfX1yg 4ElNKuuen1qsex1bJZZfJyf4pvkkcyUynhiy2CfNzMFUjxD9uSR4G1VPuWW+qFDJ4qtA 7v+axXEp6rhNXB0fFD48Qer+j/8nnBIh+eoLJJWWwtBhjeb9YzLArqRhGkSRMmeKnu2o /M/w==
X-Received: by 10.60.60.228 with SMTP id k4mr4975521oer.84.1375449240961; Fri, 02 Aug 2013 06:14:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Fri, 2 Aug 2013 06:13:39 -0700 (PDT)
In-Reply-To: <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 2 Aug 2013 15:13:39 +0200
Message-ID: <CAPv4CP87d2W8T5XjjK99_1-2G9fSOJsn+K+7oOXseYao-=4uKA@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
To: Mary Barnes <mary.h.barnes@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IAOC List <iaoc@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:14:02 -0000

On Fri, Aug 2, 2013 at 2:53 PM, Mary Barnes <mary.h.barnes@gmail.com> wrote:
> I did have some annoyances with the housekeeping, in particular the
> rewashing of glasses/mugs in the bathroom sink and someone else's soap bar
> ending up in my bathroom.

I never ever use hotel glassware.

From mcr@sandelman.ca  Fri Aug  2 06:31:26 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9B211E812C; Fri,  2 Aug 2013 06:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 zhODrgN+1JS1; Fri,  2 Aug 2013 06:31:21 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id D038521F9EAD; Fri,  2 Aug 2013 06:30:31 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id CE3D820178; Fri,  2 Aug 2013 10:36:34 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 870AA63A7C; Fri,  2 Aug 2013 09:28:57 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7AA25636AD; Fri,  2 Aug 2013 09:28:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IAOC List <IAOC@ietf.org>, "ietf\@ietf.org list" <ietf@ietf.org>
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com> <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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, 02 Aug 2013 09:28:57 -0400
Message-ID: <6462.1375450137@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:31:26 -0000

--=-=-=


Many countries let you claim VAT paid as you leave.
If we organized ourselves, then the whole issue of VAT could be neutral to
non-EC attendees.  EC-attendees, likely can claim the VAT paid anyway.

I just wish travel in the summer to Europe wasn't so expensive, and that the
week didn't so often run right into the August long weekend, which for me, is
a family weekend of the summer.   It was the combination of the cost and the
family impact that kept me from travelling.
(Toronto next summer is a week earlier, and Prague in 2015 almost two weeks earlier)

I'm glad to hear that the venue worked so well.

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



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

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

iQCVAwUBUfu0F4qHRg3pndX9AQJmSAP/UFzIuY6e1NnwWtAQHtcLPXr1QwnpIiYZ
u4bbLtso6zoniDEDkKv+olFWiaRSj5UsF2KKzMI38sC0F3Jn67zTrtG2KtSB2CWa
yNuw4VTdufu4AhtExhrCJMxI7DwBMK93N+ZO9EeaOL5sM9tchL5A+klPJuamHAnl
TOPbI0Z6lO8=
=zD7i
-----END PGP SIGNATURE-----
--=-=-=--

From jgunn6@csc.com  Fri Aug  2 06:40:06 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3CBE11E80EC; Fri,  2 Aug 2013 06:40: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.009,  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 Jzn8qRDRLSFI; Fri,  2 Aug 2013 06:40:00 -0700 (PDT)
Received: from mail85.messagelabs.com (mail85.messagelabs.com [216.82.241.211]) by ietfa.amsl.com (Postfix) with ESMTP id 07B1811E80D3; Fri,  2 Aug 2013 06:39:59 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-2.tower-85.messagelabs.com!1375450795!20052452!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2840 invoked from network); 2 Aug 2013 13:39:55 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-2.tower-85.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 2 Aug 2013 13:39:55 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r72DaRWB016019; Fri, 2 Aug 2013 09:36:27 -0400
In-Reply-To: <6462.1375450137@sandelman.ca>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>	<E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com> <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com> <6462.1375450137@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
MIME-Version: 1.0
Subject: Re: Berlin was awesome, let's come again
X-KeepSent: 70AE9A70:AC0E3B6C-85257BBB:004AF56A; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF70AE9A70.AC0E3B6C-ON85257BBB.004AF56A-85257BBB.004B2014@csc.com>
Date: Fri, 2 Aug 2013 09:39:50 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/02/2013 09:33:21 AM, Serialize complete at 08/02/2013 09:33:21 AM
Content-Type: multipart/alternative; boundary="=_alternative 004B1F9685257BBB_="
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, ietf-bounces@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:40:06 -0000

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

AFAIK, you can only get a VAT refund for GOODS you take with you, not for 
the VAT on goods or services "consumed" in country.

Janet


ietf-bounces@ietf.org wrote on 08/02/2013 09:28:57 AM:

> From: Michael Richardson <mcr+ietf@sandelman.ca>
> To: IAOC List <IAOC@ietf.org>, "ietf\@ietf.org list" <ietf@ietf.org>
> Date: 08/02/2013 09:31 AM
> Subject: Re: Berlin was awesome, let's come again
> Sent by: ietf-bounces@ietf.org
> 
> 
> Many countries let you claim VAT paid as you leave.
> If we organized ourselves, then the whole issue of VAT could be neutral 
to
> non-EC attendees.  EC-attendees, likely can claim the VAT paid anyway.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> 
> 
> [attachment "attpcwe7.dat" deleted by Janet P Gunn/USA/CSC] 
--=_alternative 004B1F9685257BBB_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">AFAIK, you can only get a VAT refund for
GOODS you take with you, not for the VAT on goods or services &quot;consumed&quot;
in country.</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 08/02/2013 09:28:57
AM:<br>
<br>
&gt; From: Michael Richardson &lt;mcr+ietf@sandelman.ca&gt;</font></tt>
<br><tt><font size=2>&gt; To: IAOC List &lt;IAOC@ietf.org&gt;, &quot;ietf\@ietf.org
list&quot; &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 08/02/2013 09:31 AM</font></tt>
<br><tt><font size=2>&gt; Subject: Re: Berlin was awesome, let's come again</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; Many countries let you claim VAT paid as you leave.<br>
&gt; If we organized ourselves, then the whole issue of VAT could be neutral
to<br>
&gt; non-EC attendees. &nbsp;EC-attendees, likely can claim the VAT paid
anyway.<br>
&gt; <br>
&gt; --<br>
&gt; Michael Richardson &lt;mcr+IETF@sandelman.ca&gt;, Sandelman Software
Works<br>
&gt; <br>
&gt; <br>
&gt; [attachment &quot;attpcwe7.dat&quot; deleted by Janet P Gunn/USA/CSC]
</font></tt>
--=_alternative 004B1F9685257BBB_=--

From mcr@sandelman.ca  Fri Aug  2 06:44:49 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6E821E80AA for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 06:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 CW7TesXGn9tI for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 06:44:45 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 9C62121E80B0 for <ietf@ietf.org>; Fri,  2 Aug 2013 06:44:34 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id A11A220178; Fri,  2 Aug 2013 10:50:46 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 512D363A7C; Fri,  2 Aug 2013 09:43:09 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 42515636AD; Fri,  2 Aug 2013 09:43:09 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Amanda Baber <amanda.baber@icann.org>, "ietf\@ietf.org" <ietf@ietf.org>
Subject: Re: stability of iana.org URLs
In-Reply-To: <1375382894.23365.553.camel@minbar.fac.cs.cmu.edu>
References: <21265_1375344641_r718AdfO023164_CE1FE47E.B59E%amanda.baber@icann.org> <1375382894.23365.553.camel@minbar.fac.cs.cmu.edu>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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, 02 Aug 2013 09:43:09 -0400
Message-ID: <8662.1375450989@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:44:49 -0000

--=-=-=


Jeffrey Hutzelman <jhutz@cmu.edu> wrote:
    > On Thu, 2013-08-01 at 01:10 -0700, Amanda Baber wrote:
    >> Hi,
    >>
    >> The link in RFC3315 is actually incorrect -- it should have been
    >> http://www.iana.org/assignments/enterprise-numbers, without the file
    >> extension, and there's an erratum about this. HTML was generally (if
    >> not exclusively) reserved for files that needed to include links to
    >> registration forms .

    > Nonetheless, it's an existing URL in an immutable published RFC.  Once
    > such a thing has been published, right or wrong, best practice is to
    > make sure it remains valid.

that was my point...
I did not think to look at Errata for a URL "mistake"

The Apache mod_spelling module would even have fixed the reference, I think.

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



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

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

iQCVAwUBUfu3aoqHRg3pndX9AQII0QQA8KzL2enuhzrMSXXbqLjhb8ccQYo7HjbJ
fUvSM1K6V8l7RNO8r884QG+sfGGqmyl1QVX5mDzmEHUb+l6JVc/6gdS+5uWIrhHr
PuEAhbM+LpbyBRKAqImkjp+vEWPn1k1MpwkMsjb8UoxpDj7cCYxqnKoVgKkraQvC
qbtrFa+98Zk=
=mYzk
-----END PGP SIGNATURE-----
--=-=-=--

From moore@network-heretics.com  Fri Aug  2 08:24:57 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85B5711E80E7; Fri,  2 Aug 2013 08:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.615
X-Spam-Level: 
X-Spam-Status: No, score=-3.615 tagged_above=-999 required=5 tests=[AWL=-0.016, 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 wUsSji6Ic-Hb; Fri,  2 Aug 2013 08:24:52 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5FA11E811A; Fri,  2 Aug 2013 08:24:52 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0C1F3215D7; Fri,  2 Aug 2013 11:24:50 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 02 Aug 2013 11:24:51 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=OPRrJR6TDe1On4GETrkyogIPs+w=; b=I1 GeXaGh03/d9SCOjqPFZ+wj6dC7xUPOy8JC2bltJ1zqv1m4pwZFPK/vp/PGqcMCvZ FvWkJmtzV4MA8plicaDIhFtWMTN0V+XITPivapp92Vq/PawFcp+ISvn8izJ8GUtf quVRMgrRdfn45EALUxFdHGPR9OCuBD9zzQ3KtYmA0=
X-Sasl-enc: mhHp2ztWDAdVblzMFQpMWrOw2j67ZojuTCIB8ohCihiY 1375457089
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 3A86A6801A8; Fri,  2 Aug 2013 11:24:49 -0400 (EDT)
Subject: Re: Berlin was awesome, let's come again
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <7922AF29-364C-4113-AEB5-B18915C128DA@netapp.com>
Date: Fri, 2 Aug 2013 17:24:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D25A8F2-CA98-418C-B510-373020AC76DC@network-heretics.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <A8BA2880-0215-458C-98D7-A8D3F47D62CB@vigilsec.com> <7922AF29-364C-4113-AEB5-B18915C128DA@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1085)
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 15:24:57 -0000

On Aug 2, 2013, at 1:09 PM, Eggert, Lars wrote:

> Hi,
>=20
> On Aug 2, 2013, at 13:04, Russ Housley <housley@vigilsec.com>
> wrote:
>> I have also enjoyed my time in Berlin.  However, we need to complete =
the analysis on the impact of VAT.  I hope there is a way to avoid a =
cost to each participant of an 19%.  We heard in plenary that VAT =
clearly applies to conferences, but it may not apply to standards =
meeting.
>=20
> agreed.

It's not just the 19% VAT.  I found fares to Berlin several hundred USD =
more expensive than fares to other European cities.

But I agree that the city and the hotel were a splendid location for an =
IETF conference.

>=20
> Snarky side comment: We should also analyze the impact of over-the-top =
tipping customs in some countries :-)

seems fair.

Keith


From moore@network-heretics.com  Fri Aug  2 08:27:38 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B355511E8135; Fri,  2 Aug 2013 08:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.614
X-Spam-Level: 
X-Spam-Status: No, score=-3.614 tagged_above=-999 required=5 tests=[AWL=-0.015, 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 92RACS8VIem1; Fri,  2 Aug 2013 08:27:33 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9C37511E813D; Fri,  2 Aug 2013 08:27:33 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 5066521359; Fri,  2 Aug 2013 11:27:33 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 02 Aug 2013 11:27:33 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id :references:to; s=smtpout; bh=zCvq6e9iWMtXSkOwuf0xD9HdPxM=; b=P3 E9anL0EnE+ElWIY0ua2xb+Cv1GmJaubDUccWZD5DFikjgpAXv8WaqxjEf+6nvxak jp+9ck3diMB7xmh6Zn8JcHZr2XAipv/WzMUg9HnCfib/Lz4dz0QjWWnzrWxXGOw4 9eAboD0CGmzRyPkpNRoJe+/PtgkQgSuV+22JjXu0s=
X-Sasl-enc: ce41IRuUxmhJYo2FvtCyQh8jToc2Mfp8L2zfP50h1Wv0 1375457252
Received: from surfer-172-29-8-65-hotspot.internet-for-guests.com (unknown [87.193.195.90]) by mail.messagingengine.com (Postfix) with ESMTPA id EEE546800B6; Fri,  2 Aug 2013 11:27:31 -0400 (EDT)
Subject: Re: Berlin was awesome, let's come again
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <D099C9C6-83A5-49EC-BB75-16B873FC71C3@checkpoint.com>
Date: Fri, 2 Aug 2013 17:27:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <31E48667-E4B3-4208-9723-62D942A8C6DE@network-heretics.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com> <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com> <D099C9C6-83A5-49EC-BB75-16B873FC71C3@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.com>
X-Mailer: Apple Mail (2.1085)
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 15:27:38 -0000

On Aug 2, 2013, at 1:27 PM, Yoav Nir wrote:

> In the grand scheme of things, it's less than the room price for one =
night (unless you're staying at some particularly cheap motel, and those =
are more available in the US).

The availability of less expensive nearby hotels was also a plus for the =
Berlin location, and is something that should be considered for any =
location.  =20

My hotel room (perfectly adequate and quite close to the IC) was far =
less per night than the amount of VAT imposed on the conference.

Keith


From ulrich@herberg.name  Fri Aug  2 08:28:27 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAB5B21E80C7 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 08:28:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.569
X-Spam-Level: 
X-Spam-Status: No, score=-1.569 tagged_above=-999 required=5 tests=[AWL=-0.366, 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 77TwQQCL4jdL for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 08:28:24 -0700 (PDT)
Received: from mail-bk0-x22b.google.com (mail-bk0-x22b.google.com [IPv6:2a00:1450:4008:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBD821E80C5 for <ietf@ietf.org>; Fri,  2 Aug 2013 08:28:24 -0700 (PDT)
Received: by mail-bk0-f43.google.com with SMTP id jm2so251554bkc.16 for <ietf@ietf.org>; Fri, 02 Aug 2013 08:28:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=PO/IENi5T8+JpsvEJdWTw006Vl/HYxoI/pgt9bLZm0A=; b=XCHu0HbnwCpaI04pAC7GKqTZkgaP+Hn6uqatxsPNfMY3Qu3dJKBZD1h3FqlFlr+T7t e33SJSxRrLm07vHqR7yfoYaHWhotMjZJulUlLOi3SwvMx6NxcKxvvI2bWHIzo9buQtNs wAVQMqAD2dc6bHyQvm+TNeQFvWzZJEjvyMhyw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=PO/IENi5T8+JpsvEJdWTw006Vl/HYxoI/pgt9bLZm0A=; b=ay83hjX2R08AKOrd8v57cIIlYZjW7o+WvMru8u6q21lj4jmrc3fBQ6T7N8oOSAcKty g/sESeZ81TsGgaf3CdvmJmSg52aRdTVZB/245DWtwfXRhIQ+PKyhaoGd6uAxfLmSzzk+ J6dscH7FslBSyGLGxmtcgEhPfIDh549zff6cULU8TsgfH2aw/9NwLwAmp9fv0i3CryyM MIc61LVsayWsfSwdZuGf5qtcH+JCch7+uDfmXwn/jWGlGamEaqT+MW4BT/1KC3BNPZR8 6e0XeRjeQUW7XJ5It/K+rz375nastuC9P3fPsD5ff//rYd3XhhqvzImEamoFNdGb1Zqc fCzQ==
X-Received: by 10.204.173.196 with SMTP id q4mr1378549bkz.9.1375457303494; Fri, 02 Aug 2013 08:28:23 -0700 (PDT)
Received: from [192.168.178.51] (p5499AA1B.dip0.t-ipconnect.de. [84.153.170.27]) by mx.google.com with ESMTPSA id ct12sm2092876bkb.12.2013.08.02.08.28.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 08:28:22 -0700 (PDT)
References: <CAK=bVC_HsyuR0FLgHcevfhWierpnANQNT7G=PPSFvL7rdrcEzQ@mail.gmail.com> <51FB88C9.8000304@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51FB88C9.8000304@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <EAAE7F13-2E90-45EC-9DCF-DA960EDAC31E@herberg.name>
X-Mailer: iPad Mail (10B146)
From: Ulrich Herberg <ulrich@herberg.name>
Subject: Re: Time between meetings
Date: Fri, 2 Aug 2013 17:28:22 +0200
To: Arturo Servin <arturo.servin@gmail.com>
X-Gm-Message-State: ALoCoQn736U5DL1TPcUV6i/Um7y4LzN3dcv6ntpaLv89sts9v4QrRCw+fSI24Nf4YA7lJJWAYlMb
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, 02 Aug 2013 15:28:28 -0000

Fair enough. By the way, this was in no way meant as a critizism of the scri=
be or minutes takers, they did a great job.

On Aug 2, 2013, at 12:24, Arturo Servin <arturo.servin@gmail.com> wrote:

>=20
>    Or eat less cookies.  :)
>=20
>    Now, seriously. I think in your case, it was just bad luck to chair to
> meetings one after the other.
>=20
>    For the rest, taking punctuality more seriously would help.
>=20
>    As you said, time is scarce and I prefer to use it in meetings than in
> breaks.
>=20
> my 20 cents,
> as
>=20
> On 8/2/13 10:28 AM, Ulrich Herberg wrote:
>> Hi,
>>=20
>> I chaired two afternoon sessions on Thursday, and I think that the 10
>> minutes break between the sessions were not enough. Not only had I to
>> rush to the other room to set up my laptop etc., but also the scribes
>> and minutes takers that have volunteered for the second session were
>> not yet there (they arrived about 5 minutes after meeting start), so
>> that I had to find new volunteers at the beginning of the meeting. I
>> know that the available meeting time is very sparse, but having 20
>> minutes between meetings could avoid that.
>>=20
>> Ulrich
>>=20

From arturo.servin@gmail.com  Fri Aug  2 09:40:34 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D0121E80EF for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 09:40:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 VxkfjibW-HKH for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 09:40:32 -0700 (PDT)
Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id B6F8921E80EC for <ietf@ietf.org>; Fri,  2 Aug 2013 09:40:31 -0700 (PDT)
Received: by mail-bk0-f51.google.com with SMTP id ji2so278810bkc.10 for <ietf@ietf.org>; Fri, 02 Aug 2013 09:40:29 -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=btAAzWMYizHF7+trX4CHYDPVJrIte7qN5IKJaG2uHMU=; b=BFl4DO8L1yiWGIqb8vAbCslB/CtFhp78rWcQYo0JdOGBy3cBTQJb4hK5OinEAYBSRR AkK5coJfKOx/mtI7iDPefzWhmViZO8VRaQHHkzr2LL037DTCFxpEfZNbpowLROY4GSQ3 zt1esajfysh8fYAJb7DpQHyHmdasbOkf4OewOfMrYnGYWaTWNgG3UOTFkYpS0AVMZFho Wc9v+Cg9gKr959jZVdW73f9Zvwp6fQzhpez74ZsrNvRKZ8E3PdOcZtlhdc/BLCv/1pCt PsGiI/BWl7/iHHvJ8mq8W5iXGv6fdbmqzKPkqIJq/HFpnn4R16ySQNYrfCmcC7nG15HD DqQQ==
X-Received: by 10.205.26.67 with SMTP id rl3mr1401539bkb.41.1375461629590; Fri, 02 Aug 2013 09:40:29 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([62.220.28.124]) by mx.google.com with ESMTPSA id oe7sm2166331bkb.5.2013.08.02.09.40.28 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 09:40:29 -0700 (PDT)
Message-ID: <51FBE100.6050604@gmail.com>
Date: Fri, 02 Aug 2013 18:40:32 +0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>	<E361BAFC-CB52-4BBE-8775-41F47FD8DC3F@checkpoint.com> <CABkgnnV1WSBbML8SrvTKKeywTfjf=LKSyTEhHZTZkB==qNrLtg@mail.gmail.com> <6462.1375450137@sandelman.ca> <OF70AE9A70.AC0E3B6C-ON85257BBB.004AF56A-85257BBB.004B2014@csc.com>
In-Reply-To: <OF70AE9A70.AC0E3B6C-ON85257BBB.004AF56A-85257BBB.004B2014@csc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 16:40:34 -0000

On 8/2/13 3:39 PM, Janet P Gunn wrote:
> AFAIK, you can only get a VAT refund for GOODS you take with you, not
> for the VAT on goods or services "consumed" in country.
> 
> Janet
> 

	If I print the slides of the WG that I attend, does it do the trick?

:D

as

From sm@resistor.net  Fri Aug  2 13:01:15 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2299111E8126; Fri,  2 Aug 2013 13:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egYElKnrqcCA; Fri,  2 Aug 2013 13:01:14 -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 A50E511E8127; Fri,  2 Aug 2013 13:01:12 -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 r72K0vUE009847; Fri, 2 Aug 2013 13:01:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375473664; bh=wV0LoMX275KzoMQaw3bWzNXYTXP6GzJYYzKa87kK/Kw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RGBNUnaamAfOVeiIzI9HEfAkg9SEgXYjsBv1kLO8do112UsGZkjtVhDoIPLnQvlRH vI3ldvJ9SCcpJMX+UbjPo6qwnQGJi9nXebkypzdZpArVvMwaDXbxxwdkgRxyTRyJw6 u0Z/WVeG5fFhoPChH6fIQiORuvkA7wHrqV0H8SOk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375473664; i=@resistor.net; bh=wV0LoMX275KzoMQaw3bWzNXYTXP6GzJYYzKa87kK/Kw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IWXQ/J1gDACHEexbpfZVBRZ+fCtTADo/halvRa3v+gebq2VXWmCbTToF+o6JoLQe1 30QV+0ugqPnXK0ppvkMYOd7/e4PoYZAib8EvNNfQdniF607JuYkRfb5ThdLBDar3hw rsasivEfdX/A3ZJ6BCdoHPzNy6IzW8QrpOxFRr6I=
Message-Id: <6.2.5.6.2.20130802122410.0d3bc988@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 02 Aug 2013 12:58:55 -0700
To: Chris Griffiths <cgriffiths@dyn.com>
From: SM <sm@resistor.net>
Subject: Re: The Trust Agreement
In-Reply-To: <51FACC4A.4020307@gmail.com>
References: <51FACC4A.4020307@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: trustees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 20:01:15 -0000

Hi Chris,
At 13:59 01-08-2013, Brian E Carpenter wrote:
>Re the Trust's plenary slides (I was not in Berlin):
>
>I have an allergy to modifying the Trust Agreement unless there's an
>overwhelming reason to do so. It was a very hard-won piece of text.
>
> > Issue #1
> > We have recently been asked permission to
> > republish the TAO with a creative commons
> > license, but unfortunately the current trust
> > agreement does not give the trustees the
> > rights to do this
>
>It doesn't? You have the right to license "existing and future
>intellectual property" according to clause 2.1 of the Trust Agreement.
>Is there some particular property of the CC license that causes a
>problem?

I was told during the JSON chartering that relicensing of the 
specification was not a problem.  I would appreciate some feedback on 
the questions from Brian Carpenter.

> > Issue #3
> > Once a domain name or trademark is
> > registered by the trust, it cannot be
> > abandoned even if it is no longer needed
> > We must maintain these in perpetuity
>
>IANAL, but it isn't clear to me that clause 9.4 forces you to do this.
>It requires you to "take reasonable steps" and to file applications "as
>the Trustees deem necessary in order to maintain and protect the Trust
>Assets." If you decide (and minute) that it isn't reasonable or necessary
>to maintain veryolddomainname.org, where's the crime?

The IAOC decided to register a domain name.  It wasn't well-thought 
in my humble opinion.  Anyway, I don't see why there will ever be a 
need for a new domain.  As for trademarks, well, I don't see why the 
IETF needs more of them.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Fri Aug  2 13:54:26 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 644D211E80E7 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 13:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level: 
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBnh2mwryk7u for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 13:54:23 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A268911E80F9 for <ietf@ietf.org>; Fri,  2 Aug 2013 13:54:22 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 5so1062660pdd.6 for <ietf@ietf.org>; Fri, 02 Aug 2013 13:54:18 -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=KgcIvuos0dSR/aIJW5ic+d3a31PDaOlW6WfkUcC7+mc=; b=Eh2MB2cP6kWYQHUoSSvZuLM/tvEI6wm0Qd0W8d7LuleWrLayR+3e5a2aYtWkBWDWpU 9SI+YudV5LVWqI3vplE2/jIPkqqEvYdGR+gCKgMpaPTIIHLYVKbt9QqYQFddViFuBJfa SdXDfa6dg0LN4Yqd5r+qufB/Y7ehcFd3p2FBdGNOUjkG2tor49HybBTheCX0kYEAjZGS u1m1rARF90D1Q+F01H0DvXjl7M7QT+kHe6rG6uGvxF7EdAuzjFomCtVb3LjnRBPffS4c D/uJ88utIzJGjoCQ80UUqdufpquCCF6bAaaxM71DSKPYy5R40gv86TVeElb0V2/voJS8 RyFw==
X-Received: by 10.66.136.49 with SMTP id px17mr12517923pab.133.1375476858361;  Fri, 02 Aug 2013 13:54:18 -0700 (PDT)
Received: from [192.168.178.23] (225.199.69.111.dynamic.snap.net.nz. [111.69.199.225]) by mx.google.com with ESMTPSA id s5sm8760772pbo.38.2013.08.02.13.54.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 13:54:17 -0700 (PDT)
Message-ID: <51FC1C84.5070103@gmail.com>
Date: Sat, 03 Aug 2013 08:54:28 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net>	<51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com>
In-Reply-To: <51FBA251.9040804@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Olle E. Johansson" <oej@edvina.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 20:54:26 -0000

On 03/08/2013 00:13, Scott Brim wrote:
> I'm completely against participating anonymously because of IPR issues.
>  I'm mostly against pseudonymous participation for the same reason.  I
> need to be able to know who I'm dealing with, in order to know if there
> are IPR issues that should be brought up.

More generally, there are other kinds of conflict of interest, not just
intentional or accidental concealment of IPR, that can be hidden by
anonymity or pseudonymity. It seems to me to be directly against the
principles of open standards openly developed.

    Brian


From lberger@labn.net  Fri Aug  2 16:30:21 2013
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91A921E80DC for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 16:30:21 -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.083, 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 J52YcjyEUEIl for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 16:30:16 -0700 (PDT)
Received: from oproxy13-pub.unifiedlayer.com (oproxy13-pub.unifiedlayer.com [69.89.16.30]) by ietfa.amsl.com (Postfix) with SMTP id 3EEC821E80BF for <ietf@ietf.org>; Fri,  2 Aug 2013 16:30:16 -0700 (PDT)
Received: (qmail 15448 invoked by uid 0); 2 Aug 2013 23:29:46 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy13.unifiedlayer.com with SMTP; 2 Aug 2013 23:29:46 -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:MIME-Version:Subject:References:In-Reply-To:Message-ID:Date:CC:To:From; bh=whFAgdgbslGBONZZCVSdDiZwDA8g63QFoOruFCTTQ9w=;  b=hJh7pOghDcoyCuf2gNRIjfcb3qOq7/u7672kV2RXqpX/zP34sQf0slvEqr2RlQR4Y58sdHiza1IUwhfvd31MPcynlkOhVbwz62yqzir4PtyeAYqWOx57aF+8NWh/OIpX;
Received: from [70.208.153.123] (port=11744 helo=[10.165.77.15]) by box313.bluehost.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.80) (envelope-from <lberger@labn.net>) id 1V5On3-0003me-Nv; Fri, 02 Aug 2013 17:29:46 -0600
From: Lou Berger <lberger@labn.net>
To: Scott Brim <scott.brim@gmail.com>, Adam Roach <adam@nostrum.com>
Date: Fri, 02 Aug 2013 19:29:44 -0400
Message-ID: <14040865437.2764.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <51FBA251.9040804@gmail.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 AquaMail/1.2.4.0 (build: 2100294)
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 8bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 70.208.153.123 authed with lberger@labn.net}
Cc: "Olle E. Johansson" <oej@edvina.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 23:30:22 -0000

+1.



On August 2, 2013 1:13:05 PM Scott Brim <scott.brim@gmail.com> wrote:
> I'm completely against participating anonymously because of IPR issues.
>  I'm mostly against pseudonymous participation for the same reason.  I
> need to be able to know who I'm dealing with, in order to know if there
> are IPR issues that should be brought up.
>



From abdussalambaryun@gmail.com  Fri Aug  2 23:41:06 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BFAD21E809D for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, 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 gWrG1LQ5vIOW for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:41:05 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BBDB321E8097 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:41:05 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so1452242pbc.3 for <ietf@ietf.org>; Fri, 02 Aug 2013 23:41: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=kjSFNt/G1oHMqV4cyN10aQU/ru2hTXA0CkzdC9mJITI=; b=sXjmudRfKQnnt8Bw4SM00qjo4X3PVTdcZn+tVhjgKsNmgC0vIQYT/CgnxXoOCQdxIP fxEuJT5MrmwzHj2ory41Oov3Aj4lIScyBBaYyWRV5fr/GznnBoUeyDRn4dzadEWGHGzR ynVncxABSBr/WZQk8uRNS+B8hX3Yzz0bCZd5q852/zQGSKt8XEB/yKiN4TCE7S2Gucnd s/c9j2fJVUzBrv0VCf+ZqXHjZpt5M7OeKwAQQf4eEJVRU1iD3mY7QjRxWGzO+QLa38xP k3k0bkXturU5D1Cqiv+6iElckbEYSjaqZt9mDBYMwq5yEj308uRwj0cU/jIdyexQLQHS /Kzg==
MIME-Version: 1.0
X-Received: by 10.68.189.162 with SMTP id gj2mr3627152pbc.96.1375512065468; Fri, 02 Aug 2013 23:41:05 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Fri, 2 Aug 2013 23:41:05 -0700 (PDT)
In-Reply-To: <51FB9951.7090700@nostrum.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com>
Date: Sat, 3 Aug 2013 08:41:05 +0200
Message-ID: <CADnDZ8-vUWB=KT+uvgrOUyhFG-2EoR08cwisvcfFbqygdD9+jQ@mail.gmail.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Olle E. Johansson" <oej@edvina.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 06:41:06 -0000

Hi Adam,

I don't agree with you. I am a remote participant (2 years and never
attended meetings) in the IETF organisation, do you think that IETF is
fare in treating remote participants? I think the current IETF
direction is in favor of attended-meeting participants, so IMHO one
reason of some hidding their name is because the IETF still is not yet
able to control wrong behaviour of participants who think they are
well known. Thoes wrong behavior abuse peoples rights in IETF. If some
are well known, the reason is because they got better opportunity in
going to meetings, or that majority of participants are from two
regions (North America+Europe).

For me the IETF reputation is about 40% (evaluated by asking close
friends that did not participate and including the way I was treated
within 2 years), still needs more work to build its reputation (e.g. I
think some old participants need guidance to IETF visions). For me
participants' good reputation depend on their reactions: if I get a
nice reply from them, or if they don't only respond to known people,
or if they acknowledge efforts, or if they encourage other into IETF
visions, or if they provide good ideas/inputs, or if they manage
work/WG/IETF well, etc.

In IETF volunteers' reputations SHOULD always be high and respected,
but seems like the IETF give chance for abuse so its reputation makes
some people prefer to be anonymous so they try to save their self
reputation. We in IETF SHOULD not focus on people's reputation, we
SHOULD focus on ideas, reasons, work-quality, documents/RFCs
reputations and process-procedures reputations. We are here to
document IETF reputation but not to document a person reputation or
even his/her name. A person's name for me is only important when I
want to refer to his/her review, draft, idea, etc. Don't forget that
in procedure; any input into IETF is own also by IETF no matter what
was the name given, so bad behaviour makes IETF reputation bad and
then some people leave, or make anonymous names, or don't participate
just listen. IMO, the majority of subscribers (in WGs) are listeners
with zero participation.

AB

On 8/2/13, Adam Roach <adam@nostrum.com> wrote:
> Moving to ietf@ietf.org, since I think this is not in any way specific
> to Berlin.
>
>
> On 8/2/13 12:24, Olle E. Johansson wrote:
>> In rtcweb we have remote participants that prefer anonymity for a number
>> of reasons.
>
> I'm going to make a broad assumption that the "number of reasons" all
> relate to privacy. If that is incorrect, please weigh in.
>
>> The question is how this is handled in regards to note well, when they
>> want jabber scribes to relay opinions or proposals to the meeting.
>>
>> Just a note for the future. I think we should allow anonymous listeners,
>> but should they really be allowed to participate?
>>
>
> We had a previous conversation around pseudonyms, which I think
> concluded that pseudonyms are pretty much okay (and impossible to
> reliably detect anyway).
>
> Given this fact, someone can protect their identity through use of a
> consistent pseudonym. This has the property of developing a persona
> behind that pseudonym that the working group members can reasonably
> interact with.
>
> By contrast, attempting to participate in a truly anonymous fashion
> rather than participating with a pseudonym seems to have very little
> justification, with significant potential drawback for the working
> group. The privacy implications are pretty much identical, but it
> provides the illusion that one can act in a way that has no impact on a
> persona's reputation. IMHO, this is ripe for bad behavior, bad faith
> participation, and other abuses.
>
> Given the availability of pseudonymous participation, I don't think we
> need to tolerate anonymous participation.
>
> /a
>
>

From abdussalambaryun@gmail.com  Fri Aug  2 23:46:14 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82FB511E8103 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.036,  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 aTCqu0OxtUHU for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:46:13 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id B017911E80F7 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:46:13 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 15so1380535pdi.39 for <ietf@ietf.org>; Fri, 02 Aug 2013 23:46: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=YB/hpCtSOrU0Kfji4gTKlCElc/w+2oop/UT1gC/nvTo=; b=QZjFXfw7+Qk72hUBcBUo9zgoSdnEel2tT+x8ADFe2dPhQ79LxHELbu0WhZQGnA3/+w RFF1WuvSrDWciCtTARDdSMThfhfifqBhBAgwmoZW5htKkv7HDD4BCj5jJooqXhUqye0F s7r7xlhxnEq+UeXNt4E7ZAXvQNwh/ctzYrA7ez5wg8qMlrCXxrFW2IXm7sqEsrdjmcSY SmrtDScCkdga+6LmPocRpcdbH/tIim7IxU4qNiPcnRWzw48bMjhHHqUT/aJt+8i8PSYz Qk+eOphz+kNJ8E+HsKGCM0a/iWzVwJ7MC4N/9MezBzkUxHBdoW2LFiUpyMGFHiu9SH5v ARKw==
MIME-Version: 1.0
X-Received: by 10.68.228.201 with SMTP id sk9mr11676785pbc.4.1375512373342; Fri, 02 Aug 2013 23:46:13 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Fri, 2 Aug 2013 23:46:13 -0700 (PDT)
In-Reply-To: <201308020453.r724r3O8006473@rotala.raleigh.ibm.com>
References: <201308020453.r724r3O8006473@rotala.raleigh.ibm.com>
Date: Sat, 3 Aug 2013 08:46:13 +0200
Message-ID: <CADnDZ8-qND=HfU0osyVesn+u1wCEF2HuW5h=HFu_Q6P-jJK31Q@mail.gmail.com>
Subject: Re: Weekly posting summary for ietf@ietf.org
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Narten <narten@us.ibm.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: Sat, 03 Aug 2013 06:46:14 -0000

Hi Thomas,

Please note that the week did not end yet (IMO ends on Saturday night)
but your week is starting from Friday and end on Thursday night. If we
follow your week then I prefer if you post at end of Friday (as in the
end of working days of 5 in each week). However, in my comment below I
will follow the week as done in world calender, start from Sunday
(mornings) and ends on Saturday (nights).


In the last previous weeks IETF got 135, 140, and 109 messages, for
weeks 28, 29, and 30 respectively. The week 31 as below got 222
messages because it is the IETF meeting week in Berline. I expected to
get lower input from attendees and higher from remote, because
attendees are available at meetings. My input increased as you
reported (but percentage per total is still similar), because of the
meeting and I am remote, to communicate with attended participants.
However, I will try to check my input per month not per week so I can
adjust my particpation volume on the list, because on week 30 I had no
input.

Please note that this respond is related to you reporting my and
others participation activity, which I will do frequently to
comment/discuss on such report.

AB

+++++++++++++++++++++  2013 WEEK 28  +++++++++++++++++++++++
http://www.ietf.org/mail-archive/web/ietf/current/msg80637.html
+++++++++++++++++++++  2013 WEEK 29  +++++++++++++++++++++++
http://www.ietf.org/mail-archive/web/ietf/current/msg80774.html
+++++++++++++++++++++  2013 WEEK 30  +++++++++++++++++++++++
http://www.ietf.org/mail-archive/web/ietf/current/msg80883.html
+++++++++++++++++++++  2013 WEEK 31  +++++++++++++++++++++++
On 8/2/13, Thomas Narten <narten@us.ibm.com> wrote:
> Total of 222 messages in the last 7 days.
>
> script run at: Fri Aug  2 00:53:02 EDT 2013
>
>     Messages   |      Bytes        | Who
> --------+------+--------+----------+------------------------
>   4.95% |   11 |  7.45% |   129461 | abdussalambaryun@gmail.com
>   5.41% |   12 |  6.26% |   108812 | moore@network-heretics.com
>   4.95% |   11 |  4.51% |    78362 | sm@resistor.net
>   4.50% |   10 |  4.72% |    82029 | brian.e.carpenter@gmail.com
>   3.60% |    8 |  5.15% |    89569 | hallam@gmail.com
>   4.05% |    9 |  3.58% |    62145 | john-ietf@jck.com
>   4.05% |    9 |  3.54% |    61529 | arturo.servin@gmail.com
>   4.05% |    9 |  3.39% |    58959 | melinda.shore@gmail.com
>   3.60% |    8 |  2.83% |    49207 | jari.arkko@piuha.net
>   1.80% |    4 |  3.79% |    65923 | leaf.yeh.sdo@gmail.com
>   3.15% |    7 |  2.10% |    36449 | jnc@mercury.lcs.mit.edu
>   2.70% |    6 |  2.50% |    43444 | ynir@checkpoint.com
>   2.70% |    6 |  2.05% |    35661 | stpeter@stpeter.im
>   2.25% |    5 |  2.01% |    34917 | dhc@dcrocker.net
>   2.25% |    5 |  1.87% |    32418 | barryleiba@computer.org
>   1.80% |    4 |  2.25% |    39049 | tjc@ecs.soton.ac.uk
>   1.35% |    3 |  2.36% |    41081 | spromano@unina.it
>   1.80% |    4 |  1.87% |    32564 | andy@yumaworks.com
>   1.80% |    4 |  1.65% |    28732 | ted.lemon@nominum.com
>   1.80% |    4 |  1.50% |    26028 | mcr+ietf@sandelman.ca
>   1.80% |    4 |  1.45% |    25184 | aaron.ding@cl.cam.ac.uk
>   1.35% |    3 |  1.38% |    24049 | chair@ietf.org
>   1.35% |    3 |  1.34% |    23348 | rdroms.ietf@gmail.com
>   1.35% |    3 |  1.16% |    20126 | roland.bless@kit.edu
>   1.35% |    3 |  1.15% |    19939 | kathleen.moriarty@emc.com
>   1.35% |    3 |  1.12% |    19406 | joelja@bogus.com
>   1.35% |    3 |  1.09% |    19009 | hartmans-ietf@mit.edu
>   1.35% |    3 |  0.96% |    16709 | touch@isi.edu
>   0.90% |    2 |  0.99% |    17194 | d3e3e3@gmail.com
>   0.90% |    2 |  0.93% |    16233 | petithug@acm.org
>   0.90% |    2 |  0.85% |    14812 | amorris@amsl.com
>   0.90% |    2 |  0.82% |    14280 | jcurran@istaff.org
>   0.90% |    2 |  0.80% |    13957 | yding@cs.helsinki.fi
>   0.90% |    2 |  0.77% |    13418 | danny@tcb.net
>   0.90% |    2 |  0.71% |    12262 | josh.howlett@ja.net
>   0.90% |    2 |  0.66% |    11396 | scott.brim@gmail.com
>   0.90% |    2 |  0.64% |    11075 | ned+ietf@mauve.mrochek.com
>   0.90% |    2 |  0.59% |    10336 | randy@psg.com
>   0.90% |    2 |  0.56% |     9647 | ietf@meetecho.com
>   0.45% |    1 |  0.93% |    16123 | nkukich@verilan.com
>   0.45% |    1 |  0.85% |    14714 | jsalowey@cisco.com
>   0.45% |    1 |  0.81% |    14144 | andrewmcgr@google.com
>   0.45% |    1 |  0.66% |    11498 | amanda.baber@icann.org
>   0.45% |    1 |  0.62% |    10744 | mary.h.barnes@gmail.com
>   0.45% |    1 |  0.59% |    10318 | daedulus@btconnect.com
>   0.45% |    1 |  0.55% |     9616 | dave@cridland.net
>   0.45% |    1 |  0.54% |     9392 | david.black@emc.com
>   0.45% |    1 |  0.50% |     8729 | ajs@anvilwalrusden.com
>   0.45% |    1 |  0.50% |     8686 | narten@us.ibm.com
>   0.45% |    1 |  0.47% |     8238 | ted.ietf@gmail.com
>   0.45% |    1 |  0.46% |     7965 | brian@innovationslab.net
>   0.45% |    1 |  0.46% |     7918 | kvivek@broadcom.com
>   0.45% |    1 |  0.45% |     7905 | simon.leinen@switch.ch
>   0.45% |    1 |  0.45% |     7825 | fluffy@cisco.com
>   0.45% |    1 |  0.45% |     7808 | mir@ripe.net
>   0.45% |    1 |  0.43% |     7535 | bclaise@cisco.com
>   0.45% |    1 |  0.43% |     7507 | bmanning@isi.edu
>   0.45% |    1 |  0.43% |     7493 | hannes.tschofenig@gmx.net
>   0.45% |    1 |  0.42% |     7376 | alejandroacostaalamo@gmail.com
>   0.45% |    1 |  0.42% |     7233 | doug.mtview@gmail.com
>   0.45% |    1 |  0.40% |     7035 | gsalguei@cisco.com
>   0.45% |    1 |  0.40% |     7005 | zach@sensinode.com
>   0.45% |    1 |  0.39% |     6692 | jabley@hopcount.ca
>   0.45% |    1 |  0.37% |     6450 | marka@isc.org
>   0.45% |    1 |  0.37% |     6370 | johnl@taugh.com
>   0.45% |    1 |  0.36% |     6308 | peter@akayla.com
>   0.45% |    1 |  0.34% |     5940 | lorenzo@meetecho.com
>   0.45% |    1 |  0.34% |     5865 | ietf2dave@davearonson.com
>   0.45% |    1 |  0.34% |     5864 | l.wood@surrey.ac.uk
>   0.45% |    1 |  0.33% |     5797 | steve@shinkuro.com
>   0.45% |    1 |  0.33% |     5733 | tterribe@xiph.org
>   0.45% |    1 |  0.32% |     5593 | housley@vigilsec.com
>   0.45% |    1 |  0.30% |     5262 | braden@isi.edu
>   0.45% |    1 |  0.30% |     5180 | jhutz@cmu.edu
>   0.45% |    1 |  0.29% |     5035 | adrian@olddog.co.uk
> --------+------+--------+----------+------------------------
> 100.00% |  222 |100.00% |  1737615 | Total
>
>

From paf@frobbit.se  Fri Aug  2 23:52:04 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73CB921F9B07 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hi0EapFuZdfr for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:52:04 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 8D50011E80F7 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:51:58 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) by mail.frobbit.se (Postfix) with ESMTPSA id 56E9223FD3; Sat,  3 Aug 2013 08:51:52 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Weekly posting summary for ietf@ietf.org
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CADnDZ8-qND=HfU0osyVesn+u1wCEF2HuW5h=HFu_Q6P-jJK31Q@mail.gmail.com>
Date: Sat, 3 Aug 2013 08:51:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE3491B7-32C1-4C19-A0E4-32FF53244D97@frobbit.se>
References: <201308020453.r724r3O8006473@rotala.raleigh.ibm.com> <CADnDZ8-qND=HfU0osyVesn+u1wCEF2HuW5h=HFu_Q6P-jJK31Q@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 06:52:04 -0000

On 3 aug 2013, at 08:46, Abdussalam Baryun <abdussalambaryun@gmail.com> =
wrote:

> However, in my comment below I
> will follow the week as done in world calender, start from Sunday
> (mornings) and ends on Saturday (nights).

The day a week starts, and what days are working days in a week, differs =
between cultures. Many have Sunday-Thursday as working days. Many have =
Monday as the first day of the week.

There is not *one* definition of when a week start and end.

   Patrik


From cgriffiths@dyn.com  Fri Aug  2 23:57:05 2013
Return-Path: <cgriffiths@dyn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7C1711E80F7 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:57:05 -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 00boW5fNqhRR for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:57:00 -0700 (PDT)
Received: from mail-ee0-f49.google.com (mail-ee0-f49.google.com [74.125.83.49]) by ietfa.amsl.com (Postfix) with ESMTP id 28C4411E80F6 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:56:59 -0700 (PDT)
Received: by mail-ee0-f49.google.com with SMTP id d41so662505eek.8 for <ietf@ietf.org>; Fri, 02 Aug 2013 23:56:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer:x-gm-message-state; bh=ENeL6HTV4R589et+4H5+++aSXWuFTnV71vevJJ4jZog=; b=QWGWZluUQmYRvGtdJrRCqMrQVU7p2u1bCQK6z6GPmX4HjUY6XR0DbTKdEDo3bieDmc NVRreBTcyh2Iv4FVdCfokUR7EqY8rAZfxUPSu/28IzfFy0aY4MARZd96+UIF+PCv2KsE qQcnPvAudaCSNQg0ZVw4Ay4IEnB+DFKzqwU8ywz8zGp1j2YAArwKwEHeFm49QPnoP+aJ FAsgJ/wgppkdWYH8sfCtZMaivLmXOB8xQgh5qjEd5sN2vi0vcEmHhh9gu47KMz6rPR17 eE4YS5Z1DP/sHnfeWf/tSjKJHLw6q32lywv2mW1kehfGTi1T5HwWk2ggJ7c/NjbdBo/b l4Vg==
X-Received: by 10.15.49.72 with SMTP id i48mr8397963eew.37.1375513019174; Fri, 02 Aug 2013 23:56:59 -0700 (PDT)
Received: from 14109fe98af6.netpoint.com ([217.111.26.100]) by mx.google.com with ESMTPSA id c3sm17353039eev.3.2013.08.02.23.56.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 23:56:58 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_B29480BB-56EC-4C80-8441-8997F48998C4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Trustees] The Trust Agreement
From: Chris Griffiths <cgriffiths@dyn.com>
In-Reply-To: <6.2.5.6.2.20130802122410.0d3bc988@resistor.net>
Date: Sat, 3 Aug 2013 08:56:54 +0200
Message-Id: <0A35B0E6-908C-401E-85F4-3B7972751FDB@dyn.com>
References: <51FACC4A.4020307@gmail.com> <6.2.5.6.2.20130802122410.0d3bc988@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQmzfF1VyOj+lCx1Y0WuVBWwBXTqu2q8fNzOzOS3fzShqnNDWbBqNBpmsorsS2iU6mzlks85
Cc: trustees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Aug 2013 06:57:05 -0000

--Apple-Mail=_B29480BB-56EC-4C80-8441-8997F48998C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 2, 2013, at 9:58 PM, SM <sm@resistor.net> wrote:

Hello SM,

> Hi Chris,
> At 13:59 01-08-2013, Brian E Carpenter wrote:
>> Re the Trust's plenary slides (I was not in Berlin):
>>=20
>> I have an allergy to modifying the Trust Agreement unless there's an
>> overwhelming reason to do so. It was a very hard-won piece of text.
>>=20
>> > Issue #1
>> > We have recently been asked permission to
>> > republish the TAO with a creative commons
>> > license, but unfortunately the current trust
>> > agreement does not give the trustees the
>> > rights to do this
>>=20
>> It doesn't? You have the right to license "existing and future
>> intellectual property" according to clause 2.1 of the Trust =
Agreement.
>> Is there some particular property of the CC license that causes a
>> problem?
>=20
> I was told during the JSON chartering that relicensing of the =
specification was not a problem.  I would appreciate some feedback on =
the questions from Brian Carpenter.

I just replied to Brian's email, and also requested that Jorge Contreras =
(CC'd) weigh in with his legal review on this matter.  Please let me =
know if you need any further details.

>> > Issue #3
>> > Once a domain name or trademark is
>> > registered by the trust, it cannot be
>> > abandoned even if it is no longer needed
>> > We must maintain these in perpetuity
>>=20
>> IANAL, but it isn't clear to me that clause 9.4 forces you to do =
this.
>> It requires you to "take reasonable steps" and to file applications =
"as
>> the Trustees deem necessary in order to maintain and protect the =
Trust
>> Assets." If you decide (and minute) that it isn't reasonable or =
necessary
>> to maintain veryolddomainname.org, where's the crime?
>=20
> The IAOC decided to register a domain name.  It wasn't well-thought in =
my humble opinion.  Anyway, I don't see why there will ever be a need =
for a new domain.  As for trademarks, well, I don't see why the IETF =
needs more of them.

While I cannot speculate if we will need to register new domains or =
trademarks, there are some that have already been registered that the =
trust must continue to maintain indefinitely that we would prefer to see =
lapse.  The current state of having to hold onto them indefinitely seems =
impractical and requires the trust to go through efforts to maintain =
these every few years when they are most likely not needed.

Thanks

Chris




--Apple-Mail=_B29480BB-56EC-4C80-8441-8997F48998C4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJR/Km6AAoJEHFHVZ6m4kP0sigH/3W8L9U1EsswKLqASwxah33E
EiTiKKBOXxPSKtFpBAF4jkIXmuR0vnJMyCOcasaIQb5eS/ywY7mzLk6x2s/MfObJ
T77ghdlhnkQ//Dli7Dxkt2O/HyX+AFrMmgv09YQWg2/PUSFa7QSjcXNEpO/YV3+8
aQJ7q6vQ2Bez0JZGpNBvnVWcJ8vmvOKZYwKYpChFlW1oiS2Idq/HtP5q2LKQswBn
clSx7MDMNrCRQXUWyDpwIgirKDxmCWtQy4qXWdZCzd58Om2wReCutrLSfQAl4TXQ
+8vO26Uj56IP/5DxAUsVHSDwiqf5LyuRmwZe86sBvl9gIztmG1QylBuDUHbeZh0=
=+d3L
-----END PGP SIGNATURE-----

--Apple-Mail=_B29480BB-56EC-4C80-8441-8997F48998C4--

From abdussalambaryun@gmail.com  Sat Aug  3 00:05:09 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A2111E811A for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 00:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.416
X-Spam-Level: 
X-Spam-Status: No, score=-2.416 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZMNT9YyT0Rh for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 00:05:09 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9DF11E810C for <ietf@ietf.org>; Sat,  3 Aug 2013 00:05:09 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up15so1467825pbc.26 for <ietf@ietf.org>; Sat, 03 Aug 2013 00:05:09 -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 :content-transfer-encoding; bh=vmcFYjLbvC2UxqPxRz6OVrz3f8wiiayynlIqU+bdgm4=; b=PrmEenhukOwn4WXpO3ZDDJVHUubgDMkGvqImfRwSj0ejZ+nvZXih3YZrvJ5oBO/Nje TFHv5XvuTu9gdoLsdCgWz1U6TOr2Lcel8p+4EvRfeej5hJHeA7dQvBBBJ1xoiCkrSzxZ Nwqf+KLQzFfiMfYntk95fvsYmZWd2RmQvKQYIQ/B5b792dAenQeqa5nTLzeHHup4gnXZ 37ZE24lKovdDDQGGga4IMXaqLC/sccrRTlga485gapwzlDLQx4FtAPpWGScmgJREkqqF 5e2vglL4yrueH68nopKFvb/OwQa2ki75WA9ErynoESpmIYFotOTFXZFWhcD0l1PY2aFj LwOg==
MIME-Version: 1.0
X-Received: by 10.68.34.97 with SMTP id y1mr11521590pbi.198.1375513509159; Sat, 03 Aug 2013 00:05:09 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Sat, 3 Aug 2013 00:05:09 -0700 (PDT)
Date: Sat, 3 Aug 2013 09:05:09 +0200
Message-ID: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com>
Subject: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 07:05:10 -0000

On 8/3/13, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:
> On 3 aug 2013, at 08:46, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>
>>I prefer if you post at end of Friday (as in the end of working days of 5=
 in each week).

>> However, in my comment below I
>> will follow the week as done in world calender, start from Sunday
>> (mornings) and ends on Saturday (nights).
>
> The day a week starts, and what days are working days in a week, differs
> between cultures. Many have Sunday-Thursday as working days. Many have
> Monday as the first day of the week.

I suggested to Thomas to submit report in end of Friday (read what i
prefered done above) to include both Sun-Thur and Mon-Fri working
days, so all can see the result of working days in IETF.
>
> There is not *one* definition of when a week start and end.

I have worked both (Sun-Thur) and (Mon-Fri), my definition never
matters, it is the definition of the organisation we work for that
matters. So is there a definition in IETF or does Thomas have a
definition or it was selected randomly morning of Friday.

AB

>
>    Patrik
>
>

From heas@shrubbery.net  Sat Aug  3 00:12:32 2013
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFF821F8526 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 00:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 qX8dOd11mN-G for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 00:12:26 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45AEF21F8578 for <ietf@ietf.org>; Sat,  3 Aug 2013 00:12:26 -0700 (PDT)
Received: from [172.16.21.40] (135.158.241.83.in-addr.dgcsystems.net [83.241.158.135]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by guelah.shrubbery.net (Postfix) with ESMTPSA id 8295FA9D8; Sat,  3 Aug 2013 07:12:25 +0000 (UTC)
References: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net>
X-Mailer: iPhone Mail (10B329)
From: Heasley <heas@shrubbery.net>
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
Date: Sat, 3 Aug 2013 09:12:22 +0200
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: Thomas Narten <narten@us.ibm.com>, "ietf@ietf.org" <ietf@ietf.org>, =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 07:12:32 -0000

Am Aug 3, 2013 um 9:05 schrieb Abdussalam Baryun <abdussalambaryun@gmail.com=
>:

> On 8/3/13, Patrik F=C3=A4ltstr=C3=B6m <paf@frobbit.se> wrote:
>> On 3 aug 2013, at 08:46, Abdussalam Baryun <abdussalambaryun@gmail.com>
>> wrote:
>>=20
>>> I prefer if you post at end of Friday (as in the end of working days of 5=
 in each week).
>=20
>>> However, in my comment below I
>>> will follow the week as done in world calender, start from Sunday
>>> (mornings) and ends on Saturday (nights).
>>=20
>> The day a week starts, and what days are working days in a week, differs
>> between cultures. Many have Sunday-Thursday as working days. Many have
>> Monday as the first day of the week.
>=20
> I suggested to Thomas to submit report in end of Friday (read what i

I suggest eliminating the report. As it doesn't measure content quality, one=
's contribution can't be measured by the email they produce. So, it is only a=
 guage of  the distraction they produce. The report itself is a distraction.=
=20=

From andy@yumaworks.com  Sat Aug  3 01:05:13 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8CE11E8147 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level: 
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[AWL=0.289,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jX06gfqjMBBO for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 01:05:08 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3B46E11E810C for <ietf@ietf.org>; Sat,  3 Aug 2013 01:05:08 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 5so1439906pdd.6 for <ietf@ietf.org>; Sat, 03 Aug 2013 01:05:07 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=2kHAdQZiGkAkj7/RFg9txkXjEQN1P1MHnHcOngSBNlU=; b=laf1NiZcmfmd4ukswlluVdPU9zHJnXoSR9uXT/VVPvpyk+4qSz5H8mGMlKwn8chs2A 44I/L/RPyltgMM4rznkWskZg6ERyj/DRvc8mMznYdjuQ0pjSSlLs8EbbzGH/reeMc7OU ETN16ikD7ILsUZHRzoOzlobTQ7Mepa2vwARvTgniLrYKwXpP7IZUBBAL+kgyHnN3oY6C /yCtANt5+6snoCm0Dr5arbmxJ/kbGgqBKiPSr6BXvxa4lXPew6RzJtEfQcKwq0weRDu8 qPOjhXzlUIHxT5gb74Ctf4JIsGP96/zO7+3JEX9wyrxcpxXQkDmze/irWFfTSD26Ppfa bA1Q==
MIME-Version: 1.0
X-Received: by 10.66.159.72 with SMTP id xa8mr14702178pab.38.1375517107759; Sat, 03 Aug 2013 01:05:07 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Sat, 3 Aug 2013 01:05:07 -0700 (PDT)
In-Reply-To: <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net>
References: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com> <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net>
Date: Sat, 3 Aug 2013 01:05:07 -0700
Message-ID: <CABCOCHRhOaSzQ+2DDrZ+ALGTY=VHYLMh0LZ6x-wurSs8T23Uag@mail.gmail.com>
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Andy Bierman <andy@yumaworks.com>
To: Heasley <heas@shrubbery.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkpJTQTGbflXOioHf64E/xzebi+LcPyC0oCnpvUCzvh0KTwgIqnxUtK7hiB7ZEy3ip20+Fp
Cc: Thomas Narten <narten@us.ibm.com>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, "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, 03 Aug 2013 08:05:13 -0000

Hi,

I don't care if this report is published or not, but I will point
out that the 1 week sample period is not that useful if
the intent is to spot excessive posting.

Somebody could be following up on 1 thread, and not post again
for a year.  Somebody could be participating in an IETF Last Call
discussion, which should not even count as "extra" since that is
a critical part of our review process.


Andy


On Sat, Aug 3, 2013 at 12:12 AM, Heasley <heas@shrubbery.net> wrote:
> Am Aug 3, 2013 um 9:05 schrieb Abdussalam Baryun <abdussalambaryun@gmail.=
com>:
>
>> On 8/3/13, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:
>>> On 3 aug 2013, at 08:46, Abdussalam Baryun <abdussalambaryun@gmail.com>
>>> wrote:
>>>
>>>> I prefer if you post at end of Friday (as in the end of working days o=
f 5 in each week).
>>
>>>> However, in my comment below I
>>>> will follow the week as done in world calender, start from Sunday
>>>> (mornings) and ends on Saturday (nights).
>>>
>>> The day a week starts, and what days are working days in a week, differ=
s
>>> between cultures. Many have Sunday-Thursday as working days. Many have
>>> Monday as the first day of the week.
>>
>> I suggested to Thomas to submit report in end of Friday (read what i
>
> I suggest eliminating the report. As it doesn't measure content quality, =
one's contribution can't be measured by the email they produce. So, it is o=
nly a guage of  the distraction they produce. The report itself is a distra=
ction.

From ole@cisco.com  Sat Aug  3 02:13:35 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635DD11E8166 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:13:35 -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 TBN58fNCwRRR for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:13:29 -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 C6D4811E8164 for <ietf@ietf.org>; Sat,  3 Aug 2013 02:13:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1344; q=dns/txt; s=iport; t=1375521209; x=1376730809; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=W55T3uU9KOgl904mBvcMBLwxt3qrOnZMso+RqppgIkI=; b=MCoXalGGIlozL6ABfm5o5ad1Mac6y1NxYAb5m03hfv5J4+zcswS+Gc/U CEa8dgh1zpFYsL55kgHiZJlFOZH2XXHU/FiqHS0VClDLaAY/MLRDJNIhx xiMKifVPU6PHFRE4Yna1it+SpJkvYtrDn+seqhlPDkzeg6yc8adpPFbUx w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAD3J/FGtJXHA/2dsb2JhbABagwY1Sr8agRwWdIIkAQEBAQIBeQULAgEIGC4hESUCBA4FFYdpAwkGB68xDYhejSeBKoEVMweDGXQDiHKNBYFpgSqKfgOFJIMXgXE
X-IronPort-AV: E=Sophos;i="4.89,806,1367971200"; d="scan'208";a="242851109"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 03 Aug 2013 09:13:29 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r739DTxI024651 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 3 Aug 2013 09:13:29 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.218]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 04:13:28 -0500
From: "Ole Jacobsen (ole)" <ole@cisco.com>
To: Heasley <heas@shrubbery.net>
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
Thread-Topic: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
Thread-Index: AQHOkBjf+wM1hYhtCkagJpIx5KE0YJmDMzwv
Date: Sat, 3 Aug 2013 09:13:28 +0000
Message-ID: <586E502A-0083-4C3D-9515-C9B3245BC6E4@cisco.com>
References: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com>, <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net>
In-Reply-To: <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, "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, 03 Aug 2013 09:13:35 -0000

It was never a distraction until AB started complaining about it. Been serv=
ing a useful purpose for many, many years. Procmail is your friend.

Ole J. Jacobsen
Editor & Publisher
http://cisco.com/ipj

Sent from my iPhone

On Aug 3, 2013, at 9:12, "Heasley" <heas@shrubbery.net> wrote:

> Am Aug 3, 2013 um 9:05 schrieb Abdussalam Baryun <abdussalambaryun@gmail.=
com>:
>=20
>> On 8/3/13, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:
>>> On 3 aug 2013, at 08:46, Abdussalam Baryun <abdussalambaryun@gmail.com>
>>> wrote:
>>>=20
>>>> I prefer if you post at end of Friday (as in the end of working days o=
f 5 in each week).
>>=20
>>>> However, in my comment below I
>>>> will follow the week as done in world calender, start from Sunday
>>>> (mornings) and ends on Saturday (nights).
>>>=20
>>> The day a week starts, and what days are working days in a week, differ=
s
>>> between cultures. Many have Sunday-Thursday as working days. Many have
>>> Monday as the first day of the week.
>>=20
>> I suggested to Thomas to submit report in end of Friday (read what i
>=20
> I suggest eliminating the report. As it doesn't measure content quality, =
one's contribution can't be measured by the email they produce. So, it is o=
nly a guage of  the distraction they produce. The report itself is a distra=
ction.

From adrian@olddog.co.uk  Sat Aug  3 02:48:30 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0351211E815C for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISYWTTYbAjxW for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 02:48:24 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id EED1A21F935A for <ietf@ietf.org>; Sat,  3 Aug 2013 02:48:23 -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 r739mLgb030602;  Sat, 3 Aug 2013 10:48:21 +0100
Received: from 950129200 ([89.246.150.136]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r739mKCq030596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 3 Aug 2013 10:48:20 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Heasley'" <heas@shrubbery.net>, "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
Subject: RE: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
Date: Sat, 3 Aug 2013 10:48:15 +0100
Message-ID: <01b501ce902e$96092480$c21b6d80$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6QLo+ikmPqph37Sa25Jq4XZ1fulw==
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: Sat, 03 Aug 2013 09:48:30 -0000

> >>> I prefer if you post at end of Friday (as in the end of working =
days of 5 in each
> >>> week).

There are seven days in most weeks, in my experience.

> > I suggested to Thomas to submit report in end of Friday

I suggest that anyone who wants something different simply writes code =
for something different.

> I suggest eliminating the report. As it doesn't measure content =
quality, one's
> contribution can't be measured by the email they produce. So, it is =
only a guage
> of  the distraction they produce. The report itself is a distraction. =
=3D

Have you considered not reading it?

Adrian


From warren@kumari.net  Sat Aug  3 03:07:04 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1A7111E816B for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 03:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52kH09A8aRSL for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 03:06:58 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2B611E8163 for <ietf@ietf.org>; Sat,  3 Aug 2013 03:06:58 -0700 (PDT)
Received: from [10.140.221.106] (unknown [88.128.80.12]) by vimes.kumari.net (Postfix) with ESMTPSA id DA2751B412AC; Sat,  3 Aug 2013 06:06:56 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [IETF] RE: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <01b501ce902e$96092480$c21b6d80$@olddog.co.uk>
Date: Sat, 3 Aug 2013 12:06:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA3F6F49-0E1B-4721-BF0B-7F285A60BF52@kumari.net>
References: <01b501ce902e$96092480$c21b6d80$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1508)
Cc: 'Heasley' <heas@shrubbery.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 10:07:04 -0000

On Aug 3, 2013, at 11:48 AM, "Adrian Farrel" <adrian@olddog.co.uk> =
wrote:

>>>>> I prefer if you post at end of Friday (as in the end of working =
days of 5 in each
>>>>> week).
>=20
> There are seven days in most weeks, in my experience.
>=20
>>> I suggested to Thomas to submit report in end of Friday
>=20
> I suggest that anyone who wants something different simply writes code =
for something different.
>=20
>> I suggest eliminating the report. As it doesn't measure content =
quality, one's
>> contribution can't be measured by the email they produce. So, it is =
only a guage
>> of  the distraction they produce. The report itself is a distraction. =
=3D
>=20
> Have you considered not reading it?

Or, better yet, not appearing prominently on it?

W

>=20
> Adrian
>=20

--
Don't be impressed with unintelligible stuff said condescendingly.
    -- Radia Perlman.






From sm@resistor.net  Sat Aug  3 03:16:56 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2C6B11E8168; Sat,  3 Aug 2013 03:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B66CtFRh21Bc; Sat,  3 Aug 2013 03:16: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 334F711E8163; Sat,  3 Aug 2013 03:16:55 -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 r73AGdEJ021451; Sat, 3 Aug 2013 03:16:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375525007; bh=O4Raotc0KwPglEOUik0bdFagodqrP9fFg0omQCh2PdI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HvA3M21E92u6cr5PkOAxOEB+0qYIX7gpqpkpjZOffEBwyxQ0qNDcsSQYAh0GA4K0+ 826xJlX2WOwuuamztkbshJlJkcVvuOQaTyjGSJLh8E6LUaKLg00rchy8nZRclBWcOC /GYlsSJfnX8v7/+pZr860eVdPRUrJI/ViZ1udHR0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375525007; i=@resistor.net; bh=O4Raotc0KwPglEOUik0bdFagodqrP9fFg0omQCh2PdI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lfBt9v9EZJD72C/jKg/++IGDQ51YTMuSdxzqWGCEyDaOJ6MO7SY0Jdua+NiuYZI2A OiUxLmn8lUAAQqd3a/Sx4Uqnm6L1TvFPGNENkuL0GPxW7WcvEgvd4HilqqymzUvlnH qSHX5LXThF5WALYPXh0Q0QomRSQPjPbFEv9lKAPM=
Message-Id: <6.2.5.6.2.20130803014558.0bb0e678@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 03 Aug 2013 03:14:31 -0700
To: Chris Griffiths <cgriffiths@dyn.com>
From: SM <sm@resistor.net>
Subject: Re: [Trustees] The Trust Agreement
In-Reply-To: <0A35B0E6-908C-401E-85F4-3B7972751FDB@dyn.com>
References: <51FACC4A.4020307@gmail.com> <6.2.5.6.2.20130802122410.0d3bc988@resistor.net> <0A35B0E6-908C-401E-85F4-3B7972751FDB@dyn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: trustees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Aug 2013 10:16:56 -0000

Hi Chris,
At 23:56 02-08-2013, Chris Griffiths wrote:
>I just replied to Brian's email, and also requested that Jorge 
>Contreras (CC'd) weigh in with his legal review on this 
>matter.  Please let me know if you need any further details.

I'll wait for Jorge Contreras's comments.

>While I cannot speculate if we will need to register new domains or 
>trademarks, there are some that have already been registered that 
>the trust must continue to maintain indefinitely that we would 
>prefer to see lapse.  The current state of having to hold onto them 
>indefinitely seems impractical and requires the trust to go through 
>efforts to maintain these every few years when they are most likely not needed.

I guess that the problem is "must continue to maintain 
indefinitely".  My (uninformed) understanding is that the IETF Trust 
has to take reasonable steps to maintain the value of a thing.  It 
would be very difficult to claim that the IETF Trust has taken 
unreasonable steps in not maintaining a thing which does not have any value.

Regards,
-sm



From rg+ietf@qualcomm.com  Fri Aug  2 06:47:33 2013
Return-Path: <rg+ietf@qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A69211E8357; Fri,  2 Aug 2013 06:47:33 -0700 (PDT)
X-Quarantine-ID: <t3SqhOahWvtS>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -105.441
X-Spam-Level: 
X-Spam-Status: No, score=-105.441 tagged_above=-999 required=5 tests=[AWL=1.158, 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 t3SqhOahWvtS; Fri,  2 Aug 2013 06:47:16 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 4C73811E8293; Fri,  2 Aug 2013 06:47:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=@qualcomm.com; q=dns/txt; s=qcdkim; t=1375451236; x=1406987236; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:content-type; bh=ICXMGWpbCyK21GSmBr47REawy6b2kOaj5RE7F/kmueY=; b=Thz4K9HYgtBJjc33e5M53jAC/Ntxl77c7itbSZjlwqqQ3NyFsqT2UNk6 IozP1M3BrmbIQnaRJ7NHLOPt5p7JDjSTYAlrdchyJoU3/rNn2gIfjojXe 3xIAOFi4SzPyS0OqmiaZhe8cMlVCpAfDqSyzX0Jk3XmSboZFWAApf35wB A=;
X-IronPort-AV: E=Sophos;i="4.89,801,1367996400"; d="scan'208";a="66245660"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 02 Aug 2013 06:47:16 -0700
X-IronPort-AV: E=Sophos;i="4.89,801,1367996400"; d="scan'208";a="577995226"
Received: from warlock.qualcomm.com ([129.46.50.49]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Aug 2013 06:47:16 -0700
Received: from Ironmsg04-R.qualcomm.com (ironmsg04-R.qualcomm.com [172.30.46.18]) by warlock.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id r72DlEqm012906 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 2 Aug 2013 06:47:14 -0700
X-IronPort-AV: E=Sophos;i="4.89,801,1367996400"; d="scan'208";a="577995211"
Received: from unknown (HELO [10.35.200.44]) ([10.64.193.73]) by Ironmsg04-R.qualcomm.com with ESMTP; 02 Aug 2013 06:47:12 -0700
Mime-Version: 1.0
Message-Id: <p06240610ce216847354d@[10.35.200.44]>
In-Reply-To: <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.co m> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Fri, 2 Aug 2013 06:47:08 -0700
To: Mary Barnes <mary.h.barnes@gmail.com>, "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
From: Randall Gellens <rg+ietf@qualcomm.com>
Subject: Re: Berlin was awesome, let's come again
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:16:58 -0700
Cc: IAOC List <iaoc@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:47:33 -0000

At 7:53 AM -0500 8/2/13, Mary Barnes wrote:

>  I did have some annoyances with the housekeeping, in particular the 
>  rewashing of glasses/mugs in the bathroom sink and someone else's 
> soap bar ending up in my bathroom.

Obviously, someone else's soap should never end up in your room, but 
unfortunately, it's extremely common for in-room glassware and cups 
to be washed by the housekeeper.  If I don't see racks of clean 
glasses and cups on the housekeeping carts, then I assume those in my 
room aren't clean, and I use paper.  Less environmentally friendly, 
sadly.

I can rattle off a very small number of hotels around the world where 
they do wash in-room items in the restaurant dishwasher.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Make it idiot proof and someone will make a better idiot.

From cgriffiths@gmail.com  Fri Aug  2 23:48:13 2013
Return-Path: <cgriffiths@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B50C11E8103 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 hatW520uhX8T for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:48:13 -0700 (PDT)
Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8D56C11E8159 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:48:12 -0700 (PDT)
Received: by mail-ee0-f54.google.com with SMTP id e53so670921eek.27 for <ietf@ietf.org>; Fri, 02 Aug 2013 23:48:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version:x-mailer; bh=46HGd448RziZPbSbog//R2+giou6w97PoRPylkdqq8E=; b=y8YfTQt6B04jQwep77Hy3BfMBpUwmhODIKVa8BGbqAkjMYkFoaammYmWxoLWHqYL6m 1gC3OTdwQZekrSpIG8egGozztkpRAVGlE7mVXm1epYL2CwgP+gi9EQX+6Xp7/BZaTQke xYoKIrccHWB8A0ClPYEGPLNP8ZLE/Wyh2tj1ZaBeBHE9J1hD6O6r0sWWzrln+Mu1TveP u1Xrdvmfht/XbR3ss4prsfhoOPWiDDSL5mlu8SdmijrKmSOZNWb7LKLxCNBNVq0Ah7bC 1DnokUPrDiH7F0ib6RBpJNGDk5rEddAZahMQ7gfQbz/ihuqhF5rsNQ81f0Ja1X4XTqZR DY9w==
X-Received: by 10.14.179.4 with SMTP id g4mr6922517eem.93.1375512491694; Fri, 02 Aug 2013 23:48:11 -0700 (PDT)
Received: from 14109fe98af6.netpoint.com ([217.111.26.100]) by mx.google.com with ESMTPSA id c3sm17310956eev.3.2013.08.02.23.48.10 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 23:48:11 -0700 (PDT)
From: Chris Griffiths <cgriffiths@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_360312C5-D9B1-429C-992B-C531558A6582"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: Community Feedback:  IETF Trust Agreement Issues
Message-Id: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>
Date: Sat, 3 Aug 2013 08:48:08 +0200
To: ietf@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:16: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: Sat, 03 Aug 2013 06:48:13 -0000

--Apple-Mail=_360312C5-D9B1-429C-992B-C531558A6582
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_06F729F6-5D62-4EB7-9E24-8DB6459F6068"


--Apple-Mail=_06F729F6-5D62-4EB7-9E24-8DB6459F6068
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

IETF Community,

The IETF Trust Trustees would like feedback from the community on =
several issues:
	- We have received requests that we cannot accommodate and have =
consulted legal counsel to review our options
	- The trust agreement does not allow the trustees to effectively =
manage some trust assets=20

The Trust was created in December 2005 by the Internet Society and the =
Corporation for National Research Initiatives (CNRI) for the purpose of =
"the advancement of education and public interest by acquiring, holding, =
maintaining and licensing certain existing and future intellectual =
property and other property used in connection with the Internet =
standards process and its administration, for the advancement of the =
science and technology associated with the Internet and related =
technology."  =
<http://trustee.ietf.org/docs/IETF-Trust-Agreement-Executed-12-15-05.pdf> =
=20

Issue 1

We have recently been asked permission to republish the TAO with a =
creative commons license, but according to counsel, the current trust =
agreement does not give the trustees the rights to do this.

- Without specific language being added to the trust agreement, we =
cannot grant these types of requests. =20
- The current open request for a creative commons license from 6/18/2013 =
cannot be completed.

Issue 2

We cannot currently accept physical assets like hardware donations into =
the trust.  Once accepted into the trust, we would be unable to dispose =
of these items in the future if they are identified as no longer being =
needed.

- This removes flexibility in managing assets in the trust, and we =
currently use alternative methods of accepting donations outside of the =
trust.

Issue 3

Once a domain name or trademark is registered by the trust, it cannot be =
abandoned even if it is no longer needed. =20

- We must maintain these in perpetuity based on legal counsel review of =
the current language

You can also find the latest trust report that covers these items and =
was presented at the IETF 87 plenary here:  =
http://www.ietf.org/proceedings/87/slides/slides-87-iesg-opsplenary-4

Thank you and we look forward to getting your feedback. =20

Chris Griffiths
Chair, IETF Trust

--Apple-Mail=_06F729F6-5D62-4EB7-9E24-8DB6459F6068
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; ">IETF =
Community,<div><br></div><div>The IETF Trust Trustees would like =
feedback from the community on several issues:</div><div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- We have =
received requests that we cannot accommodate and have consulted legal =
counsel to review our options</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>-&nbsp;The trust agreement does =
not allow the trustees to effectively manage some trust =
assets&nbsp;<br><br>The Trust was created in December 2005 by the =
Internet Society and the Corporation for National Research Initiatives =
(CNRI) for the purpose of "the advancement of education and public =
interest by acquiring, holding, maintaining and licensing certain =
existing and future intellectual property and other property used in =
connection with the Internet standards process and its administration, =
for the advancement of the science and technology associated with the =
Internet and related technology." &nbsp;&lt;<a =
href=3D"http://trustee.ietf.org/docs/IETF-Trust-Agreement-Executed-12-15-0=
5.pdf">http://trustee.ietf.org/docs/IETF-Trust-Agreement-Executed-12-15-05=
.pdf</a>&gt; &nbsp;<br><br>Issue 1<br><br>We have recently been asked =
permission to republish the TAO with a creative commons license, but =
according to counsel, the current trust agreement does not give the =
trustees the rights to do this.<br><br>- Without specific language being =
added to the trust agreement, we cannot grant these types of requests. =
&nbsp;</div><div>- The current open request for a creative commons =
license from 6/18/2013 cannot be completed.<br><br>Issue 2<br><br>We =
cannot currently accept physical assets like hardware donations into the =
trust. &nbsp;Once accepted into the trust, we would be unable to dispose =
of these items in the future if they are identified as no longer being =
needed.<br><br>- This removes flexibility in managing assets in the =
trust, and we currently use alternative methods of accepting donations =
outside of the trust.<br><br>Issue 3<br><br>Once a domain name or =
trademark is registered by the trust, it cannot be&nbsp;abandoned even =
if it is no longer needed. &nbsp;</div><div><br></div><div>- We must =
maintain these in perpetuity based on legal counsel review of the =
current language<br><br>You can also find the latest trust report that =
covers these items and was presented at the IETF 87 plenary here: =
&nbsp;<a =
href=3D"http://www.ietf.org/proceedings/87/slides/slides-87-iesg-opsplenar=
y-4">http://www.ietf.org/proceedings/87/slides/slides-87-iesg-opsplenary-4=
</a></div><div><br>Thank you and we look forward to getting your =
feedback. &nbsp;</div><div><br>Chris Griffiths<br>Chair, IETF =
Trust</div></div></body></html>=

--Apple-Mail=_06F729F6-5D62-4EB7-9E24-8DB6459F6068--

--Apple-Mail=_360312C5-D9B1-429C-992B-C531558A6582
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJR/KerAAoJEE4wr5snmnsMa2AH/i9N1STBt5ujLM16jFyDDIDP
nKaiOAdOOXHQJIsL/INIJk0Fo0um5xO5Ywow9+fNw4BaR2iUMDjO/gTGJPNhFNk5
JtxqTBHCGHi0cWJcZZ14DNBO24IAUp8IkvCN5Ri8lWfCsk3qsc52j1h8YYEZTGID
1Ko674Fj8oc2oxAV+fA+2wMkT8fzRPki+Y3vLpGCpQjG1ZOUZ+FKIPG+T/zONuZH
P5GV+hzdLr05Ar3p8awI9IdFFbbIm0TIeMf0qi6ebXS16pBnkhs7utR0CQvJu1Ra
xCyPH4lwX7QI6nLNH4K1mLrYYaPGDwMWbQ0BxsaJMe88d529asBDDAhAhNnfzWM=
=RzFL
-----END PGP SIGNATURE-----

--Apple-Mail=_360312C5-D9B1-429C-992B-C531558A6582--

From oej@edvina.net  Fri Aug  2 23:49:21 2013
Return-Path: <oej@edvina.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7D121F9BC3 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122,  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 7FRitjn0CElt for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:49:19 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) by ietfa.amsl.com (Postfix) with ESMTP id D1B5121F9B07 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:49:18 -0700 (PDT)
Received: from [192.168.40.16] (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id AD23B93C1AF; Sat,  3 Aug 2013 06:49:16 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <51FBA251.9040804@gmail.com>
Date: Sat, 3 Aug 2013 08:49:19 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:16:58 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 06:49:21 -0000

2 aug 2013 kl. 14:13 skrev Scott Brim <scott.brim@gmail.com>:

> I'm completely against participating anonymously because of IPR issues.
> I'm mostly against pseudonymous participation for the same reason.  I
> need to be able to know who I'm dealing with, in order to know if there
> are IPR issues that should be brought up.

THat's exactly the problem. Unfortunately the world requires the IETF to
manage IPR. There's a reason why we need to be strict with the note well.
Anonymous remote *PARTICIPATION* breaks the requirements of the
note well acceptance in my view. 


/O

From cgriffiths@gmail.com  Fri Aug  2 23:49:48 2013
Return-Path: <cgriffiths@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBEB11E80F7; Fri,  2 Aug 2013 23:49: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 3D20kzzDbPuV; Fri,  2 Aug 2013 23:49:47 -0700 (PDT)
Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1532E11E80F6; Fri,  2 Aug 2013 23:49:46 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id r16so676595ead.31 for <multiple recipients>; Fri, 02 Aug 2013 23:49:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=nZoziGVok8nhS7UW2fdafD4/xXsPlxk+vXuM5SwzLBo=; b=u5B3q9y2tAmrvLExRewhmAa/UTRVlT8GAG6M58AYgL2SQRs5RM/FC/e3R5wT5IucRU 0ixGNUT7e5sljH/7c65bL7wR7kGCZ8PYuG/DzMKJgz15tGirfAwLOEw06L6KQfx5zvPC JxTFmzwJPH31M/L6xGetFan0OmsOt41NLTIxP6vrpcuIKrbTl80oYEh8IPubvKcLRAZA KRH+maVY4uAbcCYiUgj6qGlrprj6E6NCZVLkXcYsyVDFcHapHmKO7D2+O9oh14IvtBoB UjFyVcY5mL922itscNFWrj6X94n+P0VaBUXMnWdgEv4mAT/9LERhMWQnR6uiYmIPtaYS YOVg==
X-Received: by 10.15.110.10 with SMTP id cg10mr8504714eeb.57.1375512586207; Fri, 02 Aug 2013 23:49:46 -0700 (PDT)
Received: from 14109fe98af6.netpoint.com ([217.111.26.100]) by mx.google.com with ESMTPSA id bb14sm17286182eeb.17.2013.08.02.23.49.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 02 Aug 2013 23:49:45 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Trustees] The Trust Agreement
From: Chris Griffiths <cgriffiths@gmail.com>
In-Reply-To: <51FACC4A.4020307@gmail.com>
Date: Sat, 3 Aug 2013 08:49:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com>
References: <51FACC4A.4020307@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:16:58 -0700
Cc: Trustees <trustees@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, 03 Aug 2013 06:49:48 -0000

On Aug 1, 2013, at 10:59 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

Hi Brian,

> Re the Trust's plenary slides (I was not in Berlin):
>=20
> I have an allergy to modifying the Trust Agreement unless there's an
> overwhelming reason to do so. It was a very hard-won piece of text.

I recognize that this was a very hard-won piece of text and agree we =
should put a much higher threshold in order to update it.  Based on =
review of some recent items with legal counsel, we were advised that =
there were some sections that would need to be updated in order to deal =
with some recent requests and we felt we would ask the community for =
feedback if we had enough justification to make changes. =20

>> Issue #1
>> We have recently been asked permission to
>> republish the TAO with a creative commons
>> license, but unfortunately the current trust
>> agreement does not give the trustees the
>> rights to do this
>=20
> It doesn't? You have the right to license "existing and future
> intellectual property" according to clause 2.1 of the Trust Agreement.
> Is there some particular property of the CC license that causes a
> problem?

Unfortunately based on review by counsel the answer is no, we don't =
under the current language.  I will ask that Jorge Contreras (legal =
counsel) send over the specific issues if that would help.

>> Issue #2
>> We cannot currently accept physical assets
>> like hardware donations into the trust
>> Once accepted into the trust, we would be unable
>> to dispose of these items in the future if they are
>> identified as no longer being needed
>=20
> It was definitely intended that the Trust would only handle
> intellectual property, and that ISOC on behalf of IASA would handle
> money and material property. Why change this?
>=20
> (I'm not quite sure why the Trust Agreement included the words
> "and other property" in the first place. It was there from a very
> early draft and was never discussed, as far as I can tell from my
> 2005 email archive.)

Thank you for your background on this one.  Based on the review with the =
other trustees and legal counsel, we wanted to raise this one but it is =
not nearly as critical as Issue #1 or #3, and agree we have alternative =
methods that are used now which do include ISOC handling this for IASA.

>> Issue #3
>> Once a domain name or trademark is
>> registered by the trust, it cannot be
>> abandoned even if it is no longer needed
>> We must maintain these in perpetuity
>=20
> IANAL, but it isn't clear to me that clause 9.4 forces you to do this.
> It requires you to "take reasonable steps" and to file applications =
"as
> the Trustees deem necessary in order to maintain and protect the Trust
> Assets." If you decide (and minute) that it isn't reasonable or =
necessary
> to maintain veryolddomainname.org, where's the crime?

I am also not a lawyer, but based on review with legal counsel, they =
assessed that the language did not allow the trust to perform the action =
of not maintaining a domain or trademark, and we must hold onto them =
indefinitely.  This doesn't seem very practical, but again we want to =
make sure the community gets a chance to voice their thoughts on this.

Thanks=20

Chris


From oej@edvina.net  Fri Aug  2 23:55:03 2013
Return-Path: <oej@edvina.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76ECA21E8055 for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.113,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIVNqUQ7sIpA for <ietf@ietfa.amsl.com>; Fri,  2 Aug 2013 23:55:03 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) by ietfa.amsl.com (Postfix) with ESMTP id AF55D11E80F6 for <ietf@ietf.org>; Fri,  2 Aug 2013 23:55:02 -0700 (PDT)
Received: from [192.168.40.16] (h87-96-134-129.dynamic.se.alltele.net [87.96.134.129]) by smtp7.webway.se (Postfix) with ESMTPA id F3FB393C1AF; Sat,  3 Aug 2013 06:55:01 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [87attendees] procedural question with remote participation
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <CE218890.17010%york@isoc.org>
Date: Sat, 3 Aug 2013 08:55:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>
References: <CE218890.17010%york@isoc.org>
To: Dan York <york@isoc.org>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:16:58 -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: Sat, 03 Aug 2013 06:55:03 -0000

2 aug 2013 kl. 16:12 skrev Dan York <york@isoc.org>:

> Olle,
>=20
>=20
> On 8/2/13 12:24 PM, "Olle E. Johansson" <oej@edvina.net> wrote:
>=20
>> In rtcweb we have remote participants that prefer anonymity for a =
number
>> of reasons.
>>=20
>> The question is how this is handled in regards to note well, when =
they
>> want jabber scribes to relay opinions or proposals to the meeting.
>>=20
>> Just a note for the future. I think we should allow anonymous =
listeners,
>> but should they really be allowed to participate?
>=20
> We don't allow anonymous comments at the microphone in face-to-face
> meetings, requiring all people to clearly state their names and have =
those
> names recorded in the meeting minutes and in the Jabber log.    I =
don't
> see why we would change this for remote participants.
>=20
> In all the years I've been doing Jabber-scribing, I've actually never =
run
> into a case where a remote attendee requested anonymity.  I would have
> been puzzled like you.  Obviously, anyone can be "anonymous" when =
joining
> a Jabber chat room and can even make all the comments they want in the
> chat room, but I think the moment they request a relay to the mic and =
the
> comment goes into the audio record and thereby also the meeting =
minutes
> then the comment needs to have a name attached to it.
>=20
(moving to ietf mailing list)

Absolutely.

Now, should we add an automatic message when someone joins the chat =
rooms, or a message when meetings begin that all comments made in the =
chat room is also participation under the note well?

/O=

From cgriffiths@gmail.com  Sat Aug  3 00:09:20 2013
Return-Path: <cgriffiths@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A574F21F91B7; Sat,  3 Aug 2013 00:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 hBjfa0t84puf; Sat,  3 Aug 2013 00:09:20 -0700 (PDT)
Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A25E221E8055; Sat,  3 Aug 2013 00:09:17 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id r16so682235ead.31 for <multiple recipients>; Sat, 03 Aug 2013 00:09:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=hXR6S8PFC5q1QB7CBBYOY8gY97pqAgIyAWPJObAxRG0=; b=mAefQT50F+iR7YFRGrV1tjZC2xE+WeoMy70MIh2A47eig2wZO9gFxX1KzUYTU2lvMj Us4HyvFSSbFSxDx2g8gUI/4QLbHRVDKF4dgwqGfazdmHx1fe1ZGHylucoMQGyAysLFDK mKfjIXBWoJfNffdPFaVw/NCwqKlYqMDps71HeP5ECP6HKE4I8OYdhp85n9TlnG06jT19 bfjiiA/rlGEzqBdMxCw2QKAf8qL9IuFP+dfMYq66hSLx/M5JI/Wpz0LH/osfm2UAkFV+ dU3YpUeO6tIyL/tJCN8OoZWMXobom7qkaaN4CecccR2Fv1p4x/Lya6aH5zXVgR9/TuR1 wLgA==
X-Received: by 10.15.99.133 with SMTP id bl5mr8356596eeb.92.1375513751884; Sat, 03 Aug 2013 00:09:11 -0700 (PDT)
Received: from 14109fe98af6.netpoint.com ([217.111.26.100]) by mx.google.com with ESMTPSA id p49sm17419857eeu.2.2013.08.03.00.09.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 Aug 2013 00:09:10 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_3862AE39-7FC8-42D0-BB66-28BC3FE1D358"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Trustees] The Trust Agreement
From: Chris Griffiths <cgriffiths@gmail.com>
In-Reply-To: <2E71568ACE1E80FB6F7BB1DD@JcK-HP8200.jck.com>
Date: Sat, 3 Aug 2013 09:09:07 +0200
Message-Id: <15946EA1-BD1D-4EC5-9CC7-1945D45A7F27@gmail.com>
References: <51FACC4A.4020307@gmail.com> <2E71568ACE1E80FB6F7BB1DD@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:16:58 -0700
Cc: Trustees <trustees@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, 03 Aug 2013 07:09:20 -0000

--Apple-Mail=_3862AE39-7FC8-42D0-BB66-28BC3FE1D358
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 2, 2013, at 4:23 AM, John C Klensin <john-ietf@jck.com> wrote:

> FWIW, I share Brian's concern and reasoning about these
> questions (and his allergy).   I might have a lower threshold of
> necessity as a requirement for changing the agreement, but I'm
> not convinced -- from either the slide or what I could hear of
> the audio-- that it is necessary.
>=20
>   john

Thank you John for your feedback on this matter, it is appreciated.  The =
Trustees recognize that any changes to the trust agreement must have a =
very high threshold of review,  and that the community should provide =
guidance on if we should even undertake this work based on the issues =
presented.  I have asked that Jorge Contreras (legal counsel who =
reviewed these items) weigh in with his assessment.

Chris

--Apple-Mail=_3862AE39-7FC8-42D0-BB66-28BC3FE1D358
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJR/KyXAAoJEE4wr5snmnsMDiUIAIqXF5vJTJk2xV8kpM3u3xLK
yDZ6JGDskH+6obWCCATdGyxFzHsJvevbpjZKrqyQtKo4lJ1TqgpG5x5I0CtErNTt
WzURFGU/2AHyNv0ynZe9fBE0Fe7GC3tyY2nSOpCaqykuuxeRA00BDFhcHzhYdgop
22M+k6h5K+NUb0+NLU8i4m+VMfymoV0BOKJ9wo8CcLn46LH/fZr5ucR0i2oFlK3/
A/x7JPGp7VRbggSVZwYVjtLAWOo3UZUMrZywxSa+3FL2kmHTIMwIQIx362oAbqNv
2jaWOQBhyBKw1JgFOhEpEk5gBixzC5G4LpfNZQpYyHIQ+33LnLTogjuhatmsfo8=
=RyQ4
-----END PGP SIGNATURE-----

--Apple-Mail=_3862AE39-7FC8-42D0-BB66-28BC3FE1D358--

From paitken@cisco.com  Fri Aug  2 06:08:38 2013
Return-Path: <paitken@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 A2E8821E8125; Fri,  2 Aug 2013 06:08:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.512
X-Spam-Level: 
X-Spam-Status: No, score=-10.512 tagged_above=-999 required=5 tests=[AWL=0.087, 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 4SDh+le0Rerw; Fri,  2 Aug 2013 06:08:33 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id B7FF721E823D; Fri,  2 Aug 2013 06:08:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=742; q=dns/txt; s=iport; t=1375448894; x=1376658494; h=message-id:date:from:mime-version:to:cc:subject: content-transfer-encoding; bh=J+8XcEr0m94ykA6Jrm2J/7ekApQQGoH5RolGvfg/Fw0=; b=A0091dKFea8+Yanc032hIi4PxU3ccKo/zkaqDz+Sb9Y1rmIcDq7usE5p XdDy0CFxkE/5OxhIsBmh8i3BcViVacFG+72we2PoOrrKB3yqTf52+l1PJ kLxqy/N66wVJre8VPbwKTbP6Y0CWiguywe5Wk926bmPs7Rc4oH9RXgJeg Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIKAByu+1GQ/khL/2dsb2JhbABagwY1AYMYvAAEBAGBHBZ0gmM3CQE8FhgDAgECAVgBBwEBiAwMuSiQGB2DdwOXX4YkiyqDGA
X-IronPort-AV: E=Sophos;i="4.89,801,1367971200"; d="scan'208";a="85386425"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 02 Aug 2013 13:08:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r72D89Sa006029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Aug 2013 13:08:09 GMT
Received: from [10.61.98.64] (dhcp-10-61-98-64.cisco.com [10.61.98.64]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r72D88rx021341; Fri, 2 Aug 2013 14:08:08 +0100 (BST)
Message-ID: <51FBAF39.1090003@cisco.com>
Date: Fri, 02 Aug 2013 14:08:09 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: iaoc-rps@ietf.org
Subject: RPS Accessibility
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 03 Aug 2013 03:17:44 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2013 13:08:38 -0000

I've remotely participated in several IETFs.

I find that the biggest problem with remote attendance is the lack of 
visual cues. I've come to realise just how important these are in a meeting.
-are people paying attention, are they interested / confused / 
distracted / bored?

Also there's no way for local attendees (in the WG room) to know that 
remote attendees are "at the mic" and whose turn it is to speak.

There's been some discussion on the "87attendees" mailer about badge 
sensing at the mic - whether QR codes, NFC, or RFID. This could help 
remote attendees too.

eg, see what they did with NFC + mic here: 
http://www.5thbar.me/blog/2012/09/14/nfc-enabled-badges-at-the-5thbar-mobile-marketing-forum/ 


P.

From ulrich@herberg.name  Sat Aug  3 03:33:37 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8805711E8181 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 03:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 MIwGyoQGjsAg for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 03:33:36 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 9D29811E8172 for <ietf@ietf.org>; Sat,  3 Aug 2013 03:33:36 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id jz10so1658359veb.12 for <ietf@ietf.org>; Sat, 03 Aug 2013 03:33:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Zn6/MkiA3ECxCewuSC/BUeTHS1C44biGQi9tUPHIBoo=; b=aU63q3IZz4O0yVAIoRtc/HQrg4G1zxcUBZn6vt1i76yQigp2DxDosNAujDEm29w/xj cxq47OQqdkLlhTICtMc8PqbKkLY7A1XRH0nubCm7tiF9SAV2DBT6vkmZgz2dE4LgMlcn Cg+kiH4Ik8A1IzKCuKn+ea+/rP92ztIJYn+TY=
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=Zn6/MkiA3ECxCewuSC/BUeTHS1C44biGQi9tUPHIBoo=; b=nlea3h17gB93mKe15gECLIMNfgMVRuMlR+GkfU2/zNLOFWS8ZXOS/ounZezUlntSZd Ro4XTLy5XJhHqAcMYiOdM8f/eonAbkWda0jd+1ryfi0JiH3KqGtcVaoajrrk32O4dpSo 23dVFPozkdHvcJF2+V+2QZwUyBfW1ImbeReGaSaxBP89ZG304EybxYAtKXS4icClDkw1 eSV0swZvfszXH0wfCSALrfD6oIWGiBx2fwGVJm1wlyhBS4ZAML9M2E1rQZAnXGoGKHpG jIXOxoVijQ9GZKtKv3rrdJrDE5NANl/LEgucKzw8b2B7gTeS30P1DBdkRE5eLC4PnYvR 8OKw==
MIME-Version: 1.0
X-Received: by 10.58.54.70 with SMTP id h6mr3387218vep.36.1375526016050; Sat, 03 Aug 2013 03:33:36 -0700 (PDT)
Received: by 10.221.55.70 with HTTP; Sat, 3 Aug 2013 03:33:35 -0700 (PDT)
In-Reply-To: <p06240610ce216847354d@10.35.200.44>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com> <p06240610ce216847354d@10.35.200.44>
Date: Sat, 3 Aug 2013 12:33:35 +0200
Message-ID: <CAK=bVC90Fw4=V5Z8UVp392nomLeZUFPuDn34_-dauhxSUx5TbQ@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Ulrich Herberg <ulrich@herberg.name>
To: Randall Gellens <rg+ietf@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnqExvuAcpFDCNnpcBIAK7ZI1JYBSBack5eLkIRochP0YquzYAXv5JtaBO9Kj9UVCBidpRb
Cc: "ietf@ietf.org list" <ietf@ietf.org>, IAOC List <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 10:33:37 -0000

I agree that the venue was awesome! I hope that they will complete the
new airport still in this century, which would make it easier to reach
Berlin.

Ulrich

On Fri, Aug 2, 2013 at 3:47 PM, Randall Gellens <rg+ietf@qualcomm.com> wrote:
> At 7:53 AM -0500 8/2/13, Mary Barnes wrote:
>
>>  I did have some annoyances with the housekeeping, in particular the
>> rewashing of glasses/mugs in the bathroom sink and someone else's soap bar
>> ending up in my bathroom.
>
>
> Obviously, someone else's soap should never end up in your room, but
> unfortunately, it's extremely common for in-room glassware and cups to be
> washed by the housekeeper.  If I don't see racks of clean glasses and cups
> on the housekeeping carts, then I assume those in my room aren't clean, and
> I use paper.  Less environmentally friendly, sadly.
>
> I can rattle off a very small number of hotels around the world where they
> do wash in-room items in the restaurant dishwasher.
>
> --
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly selected tag: ---------------
> Make it idiot proof and someone will make a better idiot.

From gjshep@gmail.com  Sat Aug  3 03:39:30 2013
Return-Path: <gjshep@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 356E811E8172; Sat,  3 Aug 2013 03:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.995
X-Spam-Level: 
X-Spam-Status: No, score=-101.995 tagged_above=-999 required=5 tests=[AWL=0.604, 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 Hs9GGvIXOLwl; Sat,  3 Aug 2013 03:39:29 -0700 (PDT)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 1C90211E816B; Sat,  3 Aug 2013 03:39:28 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id q56so1201743wes.7 for <multiple recipients>; Sat, 03 Aug 2013 03:39:28 -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=3zcZkgp2TW6DjWCLtSd4hayJEgmN4xCSEclLWRvitKA=; b=HdHKtZXKd/Hh+upxRmRvzrHy+TdRTOHkGKv9UmEXC2PC7YAVA0ab6C9nOiDpJ3Craz HATaALVVoQ/TyWvWz0b187XbVx3on+VE3COAy1+vPaiUx5hEaNSyTHWI1EQzFm0R66am 8OpsH/qpLTzPKdAa1W4GP7ei2K1POtULQVgKHyzpq1gBvNQd+n/bsWP/nBSKyml0DP/W 4ltDNSeTOGtqpE+TibNBMorIkfHcWnHA+5qTQkD9lcqCZFqygA+fD1K+fLLdJ7VFbio2 fffx0ABowykysStg/5HmN6HvJ5YTWG2zCnKiWIHL5J9Tb9Ak5bOWwWHYFnUc71QbqfKW 4mew==
MIME-Version: 1.0
X-Received: by 10.194.109.164 with SMTP id ht4mr7597576wjb.35.1375526367952; Sat, 03 Aug 2013 03:39:27 -0700 (PDT)
Received: by 10.180.185.36 with HTTP; Sat, 3 Aug 2013 03:39:27 -0700 (PDT)
In-Reply-To: <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com>
Date: Sat, 3 Aug 2013 03:39:27 -0700
Message-ID: <CABFReBp9M+q7fGsojKT+YiYF09MBjDMZMo4rY_nq-b79TVbiFQ@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Greg Shepherd <gjshep@gmail.com>
To: Mary Barnes <mary.h.barnes@gmail.com>
Content-Type: multipart/alternative; boundary=089e0102f1628a83a504e308b054
Cc: IAOC List <iaoc@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: gjshep@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 10:39:30 -0000

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

On Fri, Aug 2, 2013 at 5:53 AM, Mary Barnes <mary.h.barnes@gmail.com> wrote:

> I did have some annoyances with the housekeeping, in particular the
>  rewashing of glasses/mugs in the bathroom sink and someone else's soap bar
> ending up in my bathroom.
>

Can I have my soap back?


> On Fri, Aug 2, 2013 at 6:49 AM, Livingood, Jason <
> Jason_Livingood@cable.comcast.com> wrote:
>
>> +1
>>
>>
>> Very productive venue, easy to access city, several hotels near the venue
>> for alternatives, walkable area around the venue, lots of options for
>> restaurants, good public transit system, etc. And I enjoyed the social &
>> social venue as well (thanks DENIC)!
>>
>> I really do hope we return in the future - this location really has many
>> of the things we as participants like.
>>
>> Thank you very much to all of the sponsors and volunteers!!
>>
>> Jason
>>
>> On 8/2/13 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:
>>
>> >Venue was great, food options here and in the city were great, all-around
>> >great experience. Let's come again!
>> >
>> >(I do kinda wonder how there wasn't a single local company willing to
>> >step up to be the host. That's embarrassing to me as a German, esp. if
>> >the IETF meets in the self-declared IT hub of Germany. Better luck next
>> >time, I hope.)
>> >
>> >Lars
>>
>>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Fri, Aug 2, 2013 at 5:53 AM,=
 Mary Barnes <span dir=3D"ltr">&lt;<a href=3D"mailto:mary.h.barnes@gmail.co=
m" target=3D"_blank">mary.h.barnes@gmail.com</a>&gt;</span> wrote:<br><div =
class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I did have some annoya=
nces with the housekeeping, in particular the =A0rewashing of glasses/mugs =
in the bathroom sink and someone else&#39;s soap bar ending up in my bathro=
om.=A0</div>
</div></blockquote><div><br></div><div style>Can I have my soap back?</div>=
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><di=
v class=3D"h5">
<div><div class=3D"gmail_extra"><div class=3D"gmail_quote">On Fri, Aug 2, 2=
013 at 6:49 AM, Livingood, Jason <span dir=3D"ltr">&lt;<a href=3D"mailto:Ja=
son_Livingood@cable.comcast.com" target=3D"_blank">Jason_Livingood@cable.co=
mcast.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">+1<br>
<br>
<br>
Very productive venue, easy to access city, several hotels near the venue<b=
r>
for alternatives, walkable area around the venue, lots of options for<br>
restaurants, good public transit system, etc. And I enjoyed the social &amp=
;<br>
social venue as well (thanks DENIC)!<br>
<br>
I really do hope we return in the future - this location really has many<br=
>
of the things we as participants like.<br>
<br>
Thank you very much to all of the sponsors and volunteers!!<br>
<br>
Jason<br>
<br>
On 8/2/13 12:58 PM, &quot;Eggert, Lars&quot; &lt;<a href=3D"mailto:lars@net=
app.com" target=3D"_blank">lars@netapp.com</a>&gt; wrote:<br>
<br>
&gt;Venue was great, food options here and in the city were great, all-arou=
nd<br>
&gt;great experience. Let&#39;s come again!<br>
&gt;<br>
&gt;(I do kinda wonder how there wasn&#39;t a single local company willing =
to<br>
&gt;step up to be the host. That&#39;s embarrassing to me as a German, esp.=
 if<br>
&gt;the IETF meets in the self-declared IT hub of Germany. Better luck next=
<br>
&gt;time, I hope.)<br>
&gt;<br>
&gt;Lars<br>
<br>
</blockquote></div><br></div></div></div></div></div></div>
</blockquote></div><br></div></div>

--089e0102f1628a83a504e308b054--

From spromano@unina.it  Sat Aug  3 03:41:21 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D723311E8163; Sat,  3 Aug 2013 03:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.305
X-Spam-Level: 
X-Spam-Status: No, score=-98.305 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, 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 mIBcE5hDZGUZ; Sat,  3 Aug 2013 03:41:16 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 5424B11E816B; Sat,  3 Aug 2013 03:41:16 -0700 (PDT)
Received: from localhost (inbox.unina.it [192.132.34.41]) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r73AfAdf021326; Sat, 3 Aug 2013 12:41:10 +0200
Received: from 31.189.208.97 ([31.189.208.97]) by inbox.unina.it (Horde Framework) with HTTP; Sat, 03 Aug 2013 12:41:10 +0200
Message-ID: <20130803124110.749523icrw5nv6me@inbox.unina.it>
Date: Sat, 03 Aug 2013 12:41:10 +0200
From: spromano@unina.it
To: Paul Aitken <paitken@cisco.com>
Subject: Re: RPS Accessibility
References: <51FBAF39.1090003@cisco.com>
In-Reply-To: <51FBAF39.1090003@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.8)
Cc: iaoc-rps@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Aug 2013 10:41:22 -0000

Hi Paul,

interesting pointer, thanks! You might all want to have  a look at the  
UMPIRE experiment proposed by Meetecho starting from IETF83:

http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project

The idea is definitely in-line with what you envisage. With the  
UMPIRE, you have an integrated means for moderating both local and  
remote participants in a seamless fashion. We would be glad to propose  
the experiment once more at the upcoming IETF in Vancouver.

Cheers,

Simon

Quoting Paul Aitken <paitken@cisco.com>:

> I've remotely participated in several IETFs.
>
> I find that the biggest problem with remote attendance is the lack  
> of visual cues. I've come to realise just how important these are in  
> a meeting.
> -are people paying attention, are they interested / confused /  
> distracted / bored?
>
> Also there's no way for local attendees (in the WG room) to know  
> that remote attendees are "at the mic" and whose turn it is to speak.
>
> There's been some discussion on the "87attendees" mailer about badge  
> sensing at the mic - whether QR codes, NFC, or RFID. This could help  
> remote attendees too.
>
> eg, see what they did with NFC + mic here:  
> http://www.5thbar.me/blog/2012/09/14/nfc-enabled-badges-at-the-5thbar-mobile-marketing-forum/  
> P.
>
>



-- 
                             _\\|//_
                             ( 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

     <<Molti mi dicono che lo scoraggiamento ? l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/


From cntreras@gmail.com  Sat Aug  3 04:50:27 2013
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE35811E80FC; Sat,  3 Aug 2013 04:50:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 PAsArFNA4VUp; Sat,  3 Aug 2013 04:50:25 -0700 (PDT)
Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com [IPv6:2a00:1450:4013:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3A16521F9E40; Sat,  3 Aug 2013 04:50:22 -0700 (PDT)
Received: by mail-ea0-f173.google.com with SMTP id g10so761360eak.32 for <multiple recipients>; Sat, 03 Aug 2013 04:50: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:date:message-id:subject:from:to :cc:content-type; bh=jGwv419ebwLOdH5LmF2p2QwSP37OJEeq/vJYndcVk4s=; b=HvLQAkngOHTCfWMqAtBcxTI6IYCEUEYLKLOBptmdqMrQfrzt5fUdeZKf+HM/a6a8Fb 3Lx7We139KMvG3dGm0NiCbLWz9vnEMc2lXaGcfnZ9By/RsjY2Q1pty3ZQnusbHTwwZs9 UnZ2IAKERtIUp/C2IDjL/9wsD2L1mE8NpanS62KfcBG7huRZhe8SJfzn16I4mrUzGkt2 uU8JyHIDTLUvDPcDPToxm/tFXlZ1u0CXzlTcclyy/9NmSXeYwtesaYSRNO/BGK7qSmTu ju+eP3NGO9ah0cBzUhTa2mFyyb33q761YbnuXCURZGzM9EOvFltHKj58YJ2TRykiemuM Darw==
MIME-Version: 1.0
X-Received: by 10.14.215.197 with SMTP id e45mr9230553eep.130.1375530621213; Sat, 03 Aug 2013 04:50:21 -0700 (PDT)
Received: by 10.14.174.66 with HTTP; Sat, 3 Aug 2013 04:50:21 -0700 (PDT)
In-Reply-To: <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com>
References: <51FACC4A.4020307@gmail.com> <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com>
Date: Sat, 3 Aug 2013 06:50:21 -0500
Message-ID: <CAP0PwYZ=T541VbjvFJnHcqPXXuhjUQVe33hsOrZ-Uer9OED9BQ@mail.gmail.com>
Subject: Re: [Trustees] The Trust Agreement
From: Jorge Contreras <cntreras@gmail.com>
To: Chris Griffiths <cgriffiths@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b603d180e432b04e309ae24
Cc: Trustees <trustees@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, 03 Aug 2013 11:50:28 -0000

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

Please see below for some specific responses to Brian's concerns.


On Sat, Aug 3, 2013 at 1:49 AM, Chris Griffiths <cgriffiths@gmail.com>wrote:

> On Aug 1, 2013, at 10:59 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
> Hi Brian,
>
> > Re the Trust's plenary slides (I was not in Berlin):
> >
> > I have an allergy to modifying the Trust Agreement unless there's an
> > overwhelming reason to do so. It was a very hard-won piece of text.
>
> I recognize that this was a very hard-won piece of text and agree we
> should put a much higher threshold in order to update it.  Based on review
> of some recent items with legal counsel, we were advised that there were
> some sections that would need to be updated in order to deal with some
> recent requests and we felt we would ask the community for feedback if we
> had enough justification to make changes.
>

Indeed, I was also part of that original negotiating team in 2005 and have
recently spent a great deal of time reviewing the records of that
negotiation.


>
> >> Issue #1
> >> We have recently been asked permission to
> >> republish the TAO with a creative commons
> >> license, but unfortunately the current trust
> >> agreement does not give the trustees the
> >> rights to do this
> >
> > It doesn't? You have the right to license "existing and future
> > intellectual property" according to clause 2.1 of the Trust Agreement.
> > Is there some particular property of the CC license that causes a
> > problem?
>

Brian - the restriction is contained in Section 9.5 which, as you may
recall, was added quite late in the negotiation.  It reads as follows:

9.5 Licenses. The Trust (acting through the Trustees) shall have the right
to grant licenses

for the use of the Trust Assets on such terms, subject to Section 7.1, as
the Trustees deem

appropriate; provided, however, that the Trust shall not grant any license
that would be

deemed a transfer of ownership or abandonment of any Trust Assets under
applicable law.

Specifically, any license granted by the Trust for the use of the Trust
Assets consisting ofiPR

other than rights in IETF standards-related documents (such as RFCs,
Internet Drafts and the

like) that have been acquired by the Trust through non-exclusive licenses
granted by their

contributors pursuant to the IETF community-approved procedures currently
set forth in RFC

3978, and any community-approved updates and revisions thereto, shall
include provisions

stating that (a) the licensee agrees to grant and assign to the Trust all
right, title, and interest it

may have or claim in any derivative works of licensee that are based on or
incorporate the

IPR, and (b) the licensee's use of the IPR and any goodwill associated
therewith shall inure to

the benefit of the Trust.

The last sentence of this clause makes the Trust is quite limited in its
ability to grant licenses to IPR other than standards-related documents.
 That is, it cannot grant licenses to non-standards IPR unless the
requirements of sub-clauses (a) and (b) are met.  If you recall, the
original negotiating position of CNRI was that the Trust have NO right
whatsoever to grant licenses to non-standards IPR.  We requested the
exceptions in clauses (a) and (b) to address planned tools development by
paid and volunteer contractors.  Those exceptions were negotiated and
allowed, and now the only way that the Trust can grant licenses to
non-standards IPR is if the licensee agrees to grant the Trust ownership of
any derivative works of the IPR.  Such a requirement is normal and
appropriate when dealing with contractor-developed tools and other
software.  However, it does NOT work in the case of something like the Tao,
which is non-standards track, but not a commissioned software tool.  In
particular, the requirement that derivative works be assigned to the Trust
is not consistent with the CC-BY license that the Tao team has requested.
 Thus, in order to allow this and similar requests, which the Trustees feel
is in the interest of the IETF community, a relaxation of the restrictions
in Section 9.5 has been suggested.


> >> Issue #2
> >> We cannot currently accept physical assets
> >> like hardware donations into the trust
> >> Once accepted into the trust, we would be unable
> >> to dispose of these items in the future if they are
> >> identified as no longer being needed
> >
> > It was definitely intended that the Trust would only handle
> > intellectual property, and that ISOC on behalf of IASA would handle
> > money and material property. Why change this?
> >
> > (I'm not quite sure why the Trust Agreement included the words
> > "and other property" in the first place. It was there from a very
> > early draft and was never discussed, as far as I can tell from my
> > 2005 email archive.)
>

As you point out, the Trust does have the ability to accept property other
than IPR.  This point is not being debated.  You may recall that CNRI
wanted the Trust to be able to raise funds to support itself, and to accept
monetary donations.  That is not a path that the Trust has gone down, but
in 2005 it was unclear what the eventual operating mode would be.


> >> Issue #3
> >> Once a domain name or trademark is
> >> registered by the trust, it cannot be
> >> abandoned even if it is no longer needed
> >> We must maintain these in perpetuity
> >
> > IANAL, but it isn't clear to me that clause 9.4 forces you to do this.
> > It requires you to "take reasonable steps" and to file applications "as
> > the Trustees deem necessary in order to maintain and protect the Trust
> > Assets." If you decide (and minute) that it isn't reasonable or necessary
> > to maintain veryolddomainname.org, where's the crime?
>

Brian - the relevant restriction in contained in Section 7.1(a):  "the
Trustees shall not, and shall not have the right or power to, (i)
exchange, distribute,
assign, sell, transfer, renounce, or convey the Trust Assets, (ii)
terminate the Trust Assets' registration,"

These restrictions, intended to prevent the Trustees from improperly
dissipating the Trust's assets, now prevent the Trust from engaging in
transactions that would help to conserve its funds (provided by ISOC) and
the community overall.   As noted before, there are trademark registrations
being maintained that are no longer necessary (i.e., the IETF SECRETARIAT
mark, which is duplicative of, and a subset of, the broader IETF mark).
 These marks cost money to maintain, both in terms of official maintenance
fees and attorney fees (not paid to me, by the way!)  However, because
under 7.1.a.ii the Trust can't terminate the registration of any Trust
Assets, we're stuck with these unnecessary registrations.

The same applies to physical assets:  historical documents that could be
donated to a museum, networking equipment that a company wants to donate
and have the Trust re-donate to worthy causes.  None of these are possible
because the Trust can't "sell, transfer, renounce or convey the Trust
Assets".

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

<div dir=3D"ltr">Please see below for some specific responses to Brian&#39;=
s concerns.<br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote=
">On Sat, Aug 3, 2013 at 1:49 AM, Chris Griffiths <span dir=3D"ltr">&lt;<a =
href=3D"mailto:cgriffiths@gmail.com" target=3D"_blank">cgriffiths@gmail.com=
</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">On Aug 1, 2013, at 10:59 PM, Brian E Carpenter &lt;<a href=
=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter=
@gmail.com</a>&gt; wrote:<br>


<br>
Hi Brian,<br>
<div><br>
&gt; Re the Trust&#39;s plenary slides (I was not in Berlin):<br>
&gt;<br>
&gt; I have an allergy to modifying the Trust Agreement unless there&#39;s =
an<br>
&gt; overwhelming reason to do so. It was a very hard-won piece of text.<br=
>
<br>
</div>I recognize that this was a very hard-won piece of text and agree we =
should put a much higher threshold in order to update it. =A0Based on revie=
w of some recent items with legal counsel, we were advised that there were =
some sections that would need to be updated in order to deal with some rece=
nt requests and we felt we would ask the community for feedback if we had e=
nough justification to make changes.<br>

</blockquote><div><br></div><div>Indeed, I was also part of that original n=
egotiating team in 2005 and have recently spent a great deal of time review=
ing the records of that negotiation.=A0<br></div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1=
px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:=
1ex">


<div><br>
&gt;&gt; Issue #1<br>
&gt;&gt; We have recently been asked permission to<br>
&gt;&gt; republish the TAO with a creative commons<br>
&gt;&gt; license, but unfortunately the current trust<br>
&gt;&gt; agreement does not give the trustees the<br>
&gt;&gt; rights to do this<br>
&gt;<br>
&gt; It doesn&#39;t? You have the right to license &quot;existing and futur=
e<br>
&gt; intellectual property&quot; according to clause 2.1 of the Trust Agree=
ment.<br>
&gt; Is there some particular property of the CC license that causes a<br>
&gt; problem?<br></div></blockquote>
<div><br></div><div>Brian - the restriction is contained in Section 9.5 whi=
ch, as you may recall, was added quite late in the negotiation. =A0It reads=
 as follows:</div><div><br></div><div><p style=3D"margin:0px;font-size:11.5=
px;font-family:Times">
9.5 Licenses. The Trust (acting through the Trustees) shall have the right =
to grant licenses</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">for the use of t=
he Trust Assets on such terms, subject to Section 7.1, as the Trustees deem=
</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">appropriate; pro=
vided, however, that the Trust shall not grant any license that would be</p=
>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">deemed a transfe=
r of ownership or abandonment of any Trust Assets under applicable law.</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">Specifically, an=
y license granted by the Trust for the use of the Trust Assets consisting o=
fiPR</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">other than right=
s in IETF standards-related documents (such as RFCs, Internet Drafts and th=
e</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">like) that have =
been acquired by the Trust through non-exclusive licenses granted by their<=
/p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">contributors pur=
suant to the IETF community-approved procedures currently set forth in RFC<=
/p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">3978, and any co=
mmunity-approved updates and revisions thereto, shall include provisions</p=
>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">stating that (a)=
 the licensee agrees to grant and assign to the Trust all right, title, and=
 interest it</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">may have or clai=
m in any derivative works of licensee that are based on or incorporate the<=
/p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">IPR, and (b) the=
 licensee&#39;s use of the IPR and any goodwill associated therewith shall =
inure to</p>
<p style=3D"margin:0px;font-size:11.5px;font-family:Times">the benefit of t=
he Trust.</p></div><div><br></div><div style>The last sentence of this clau=
se makes the Trust is quite limited in its ability to grant licenses to IPR=
 other than standards-related documents. =A0That is, it cannot grant licens=
es to non-standards IPR unless=A0the requirements of sub-clauses (a) and (b=
) are met. =A0If you recall, the original negotiating position of CNRI was =
that the Trust have NO right whatsoever to grant licenses to non-standards =
IPR. =A0We requested the exceptions in clauses (a) and (b) to address plann=
ed tools development by paid and volunteer contractors. =A0Those exceptions=
 were negotiated and allowed, and now the only way that the Trust can grant=
 licenses to non-standards IPR is if the=A0licensee agrees to grant the Tru=
st ownership of any derivative works of the IPR. =A0Such a requirement is n=
ormal and appropriate when dealing with contractor-developed tools and othe=
r software. =A0However, it does NOT work in the case of something like the =
Tao, which is non-standards track, but not a commissioned software tool. =
=A0In particular, the requirement that derivative works be assigned to the =
Trust is not consistent with the CC-BY license that the Tao team has reques=
ted. =A0Thus, in order to allow this and similar requests, which the Truste=
es feel is in the interest of the IETF community, a relaxation of the restr=
ictions in Section 9.5 has been suggested.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<div><br>
&gt;&gt; Issue #2<br>
&gt;&gt; We cannot currently accept physical assets<br>
&gt;&gt; like hardware donations into the trust<br>
&gt;&gt; Once accepted into the trust, we would be unable<br>
&gt;&gt; to dispose of these items in the future if they are<br>
&gt;&gt; identified as no longer being needed<br>
&gt;<br>
&gt; It was definitely intended that the Trust would only handle<br>
&gt; intellectual property, and that ISOC on behalf of IASA would handle<br=
>
&gt; money and material property. Why change this?<br>
&gt;<br>
&gt; (I&#39;m not quite sure why the Trust Agreement included the words<br>
&gt; &quot;and other property&quot; in the first place. It was there from a=
 very<br>
&gt; early draft and was never discussed, as far as I can tell from my<br>
&gt; 2005 email archive.)<br></div></blockquote><div><br></div><div style>A=
s you point out, the Trust does have the ability to accept property other t=
han IPR. =A0This point is not being debated. =A0You may recall that CNRI wa=
nted the Trust to be able to raise funds to support itself, and to accept m=
onetary donations. =A0That is not a path that the Trust has gone down, but =
in 2005 it was unclear what the eventual operating mode would be.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">

<div><br>
&gt;&gt; Issue #3<br>
&gt;&gt; Once a domain name or trademark is<br>
&gt;&gt; registered by the trust, it cannot be<br>
&gt;&gt; abandoned even if it is no longer needed<br>
&gt;&gt; We must maintain these in perpetuity<br>
&gt;<br>
&gt; IANAL, but it isn&#39;t clear to me that clause 9.4 forces you to do t=
his.<br>
&gt; It requires you to &quot;take reasonable steps&quot; and to file appli=
cations &quot;as<br>
&gt; the Trustees deem necessary in order to maintain and protect the Trust=
<br>
&gt; Assets.&quot; If you decide (and minute) that it isn&#39;t reasonable =
or necessary<br>
&gt; to maintain <a href=3D"http://veryolddomainname.org" target=3D"_blank"=
>veryolddomainname.org</a>, where&#39;s the crime?<br></div></blockquote><d=
iv><br></div><div style>Brian - the relevant restriction in contained in Se=
ction 7.1(a): =A0&quot;<span style=3D"font-family:Times;font-size:12px">the=
 Trustees shall not, and shall not have the right or power to, (i) exchange=
,=A0</span><span style=3D"font-family:Times;font-size:12px">distribute, ass=
ign, sell, transfer, renounce, or convey the Trust Assets, (ii) terminate t=
he Trust=A0</span><span style=3D"font-family:Times;font-size:12px">Assets&#=
39; registration,&quot;</span>=A0</div>
<div style><br></div><div style>These restrictions, intended to prevent the=
 Trustees from improperly dissipating the Trust&#39;s assets, now prevent t=
he Trust from engaging in transactions that would help to conserve its fund=
s (provided by ISOC) and the community overall. =A0 As noted before, there =
are trademark registrations being maintained that are no longer necessary (=
i.e., the IETF SECRETARIAT mark, which is duplicative of, and a subset of, =
the broader IETF mark). =A0These marks cost money to maintain, both in term=
s of official maintenance fees and attorney fees (not paid to me, by the wa=
y!) =A0However, because under 7.1.a.ii the Trust can&#39;t terminate the re=
gistration of any Trust Assets, we&#39;re stuck with these unnecessary regi=
strations. =A0</div>
<div style><br></div><div style>The same applies to physical assets: =A0his=
torical documents that could be donated to a museum, networking equipment t=
hat a company wants to donate and have the Trust re-donate to worthy causes=
. =A0None of these are possible because the Trust can&#39;t &quot;sell, tra=
nsfer, renounce or convey the Trust Assets&quot;. =A0</div>
</div></div></div>

--047d7b603d180e432b04e309ae24--

From adrian@olddog.co.uk  Sat Aug  3 04:58:22 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3719111E80FC; Sat,  3 Aug 2013 04:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96sRfoR+bcsZ; Sat,  3 Aug 2013 04:58:16 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3204621F9FF1; Sat,  3 Aug 2013 04:58:16 -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 r73Bw9Dw014822;  Sat, 3 Aug 2013 12:58:11 +0100
Received: from 950129200 ([89.246.150.136]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r73Bw6pc014812 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 3 Aug 2013 12:58:07 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Chris Griffiths'" <cgriffiths@gmail.com>
References: <51FACC4A.4020307@gmail.com> <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com>
In-Reply-To: <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com>
Subject: RE: [Trustees] The Trust Agreement
Date: Sat, 3 Aug 2013 12:58:04 +0100
Message-ID: <01e501ce9040$b7e814f0$27b83ed0$@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: AQIZ6Wch0HiYFI1v0uxp8FAXNVEzXwI9CQ7XmNrERvA=
Content-Language: en-gb
Cc: 'Trustees' <trustees@ietf.org>, 'IETF discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 11:58:22 -0000

Hi Chris,

> >> Issue #1
> >> We have recently been asked permission to
> >> republish the TAO with a creative commons
> >> license, but unfortunately the current trust
> >> agreement does not give the trustees the
> >> rights to do this
> >
> > It doesn't? You have the right to license "existing and future
> > intellectual property" according to clause 2.1 of the Trust Agreement.
> > Is there some particular property of the CC license that causes a
> > problem?
> 
> Unfortunately based on review by counsel the answer is no, we don't under the
> current language.  I will ask that Jorge Contreras (legal counsel) send over
the
> specific issues if that would help.

I recognise that the reason we pay an expert is to provide expert advice.

CC is *not* an alarming or scary thing. It is a license and is not a surrender
of assets.

If it would be helpful for the trust or Jorge to speak with CC direct, I am sure
they can use a web page and a telephone, but I would be happy to try to
facilitate if necessary.

I also wonder whether we have got caught by something in moving the Tao from an
I-D/RFC to a web page. The I-D/RFC republish requirements/license are easy and
allow someone to make and charge for a book containing RFCs etc. so long as they
comply with specific rules. It is (to me) much less clear whether the Tao can be
reproduced in full or part now that it is a Web page.
rust's mandate) and it would be very sad to let a set of trust issues block this
work.

Thanks,
Adrian


From barryleiba.mailing.lists@gmail.com  Sat Aug  3 05:17:32 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2B2111E80FF for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.971
X-Spam-Level: 
X-Spam-Status: No, score=-101.971 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRnbA8Kx-jAR for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:17:32 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id CA62E11E80FC for <ietf@ietf.org>; Sat,  3 Aug 2013 05:17:25 -0700 (PDT)
Received: by mail-lb0-f179.google.com with SMTP id v1so1050116lbd.24 for <ietf@ietf.org>; Sat, 03 Aug 2013 05:17: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=oeVVWmSTrqSzi8gfeJm99X0xrqtfO+KWdUh6AWAXMFs=; b=t20drOakj1t1qGJB/x84IdrmPQvvkB3eaoiNaBUfW2Klj2gEYhDjtJZGI7lpENezUa EMgqly8jyb1pcse14pB5QN+osCStRdCNVHxWH/z0EAPwR8CEpxHhWOlPSabWg8C1BJXJ UzOuqUsSkhz66onPhw9t7R+3OWnPRgaHm/NETcUJ0LomNTWj4pV+Q9bIxaVqP2zlfXW2 keUr13k31onc2naFPwVtN0ZpEHH3+CVwCJb399Q+UUUV/6DOkEAIZwnTOdyoaUWe/3vu Gj8uJw7iBBl+pRq0/AwlBq3y3TY6XXbfVg2KAny2FDYWeLeMuSnLRMusNFPfExUYabAH kBkg==
MIME-Version: 1.0
X-Received: by 10.112.18.198 with SMTP id y6mr5262322lbd.14.1375532244456; Sat, 03 Aug 2013 05:17:24 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.140.130 with HTTP; Sat, 3 Aug 2013 05:17:24 -0700 (PDT)
In-Reply-To: <p06240610ce216847354d@10.35.200.44>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com> <p06240610ce216847354d@10.35.200.44>
Date: Sat, 3 Aug 2013 14:17:24 +0200
X-Google-Sender-Auth: KXMPMCnHYX25YhpCjU5Dzw_xHL8
Message-ID: <CAC4RtVBr6keY0-WM8OGn6Ky088kzhMTkWdJypU-u-VKwCpgFAA@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Barry Leiba <barryleiba@computer.org>
To: Randall Gellens <rg+ietf@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 12:17:32 -0000

> it's extremely common for in-room glassware and cups to be
> washed by the housekeeper.  If I don't see racks of clean glasses and cups
> on the housekeeping carts, then I assume those in my room aren't clean, and
> I use paper.  Less environmentally friendly, sadly.

I just wash the glasses myself before using them.

I use the soap they left me from Mary's room.

Barry

From john-ietf@jck.com  Sat Aug  3 05:31:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A10EF21F9B9F; Sat,  3 Aug 2013 05:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.655
X-Spam-Level: 
X-Spam-Status: No, score=-102.655 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sp-hQoK+Kw6r; Sat,  3 Aug 2013 05:31:40 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6A44E21F9D70; Sat,  3 Aug 2013 05:31:38 -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 1V5aze-0000KC-HD; Sat, 03 Aug 2013 08:31:34 -0400
Date: Sat, 03 Aug 2013 08:31:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randall Gellens <rg+ietf@qualcomm.com>, Mary Barnes <mary.h.barnes@gmail.com>
Subject: Re: Berlin was awesome, let's come again
Message-ID: <EC5D626C97E912F6116E1395@JcK-HP8200.jck.com>
In-Reply-To: <p06240610ce216847354d@[10.35.200.44]>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.co	m> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com> <p06240610ce216847354d@[10.35.200.44]>
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 List <iaoc@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, 03 Aug 2013 12:31:46 -0000

--On Friday, August 02, 2013 06:47 -0700 Randall Gellens
<rg+ietf@qualcomm.com> wrote:

> I can rattle off a very small number of hotels around the
> world where they do wash in-room items in the restaurant
> dishwasher.

Or equivalent.  Most of those seal the washed cups in paper or
plastic to show that they have done so.  Sadly from an
environmental standpoint, there are fewer that do wash things
that way than there were a decade or two ago: especially for a
large hotel with many rooms it is simply cheaper to supply
disposable paper and/or plastic cups in the rooms that it is to
haul the glassware to the washing device, seal it, and haul it
back to the rooms.

It is a problem, but there is little point in blaming a single
hotel -- it is a chain-wide and industry-wide economic and
policy problem.

Bring your own and/or wash your own.  And, by the way, if you
are sensitive to such things washing cups or glassware from
which you intend to eat or drink with hand or bath soap is often
not really optimal because of moisturizing or fragrance
ingredients.  A 100 ml bottle of dish soap goes a long way.

   john




From Ted.Lemon@nominum.com  Sat Aug  3 05:47:35 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5993821F991F for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:47:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level: 
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 yuivsnRzycre for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:47:28 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3470711E8117 for <ietf@ietf.org>; Sat,  3 Aug 2013 05:47:25 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKUfz73FbJHTf3DBnBarXDojMxI7Go5n3o@postini.com; Sat, 03 Aug 2013 05:47:26 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 70B371B8298 for <ietf@ietf.org>; Sat,  3 Aug 2013 05:47:24 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 276D2190068; Sat,  3 Aug 2013 05:47:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 05:47:23 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmCNiiAgAANFAD//4yk7oAB06OA
Date: Sat, 3 Aug 2013 12:47:22 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775242039@mbx-01.win.nominum.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>, <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>
In-Reply-To: <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E1FD22A45ABCFF4F987781F7983F6B41@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.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, 03 Aug 2013 12:47:35 -0000

On Aug 2, 2013, at 1:56 PM, "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni=
.com> wrote:
> -1 on doing it during the winter speaking as a Californian who doesn't ev=
en own a winter coat

A winter coat used to be a prerequisite for attending winter IETF, and I do=
n't think that's a bad thing.   You can do quite well in a climate like Ber=
lin's with a stylish suit coat and jacket, plus a scarf and gloves, if you =
prefer not to go the winter coat route.   The styley route is much more exp=
ensive, but you can wear it on those days in LA when it's 50 degrees (f) ou=
t, rare though they may be.   It's also good in San Francisco weather.

Bottom line: IETF _probably_ shouldn't decide where to host its winter meet=
ings on the basis of the completeness of your wardrobe... ;)


From Ted.Lemon@nominum.com  Sat Aug  3 05:47:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 899B811E818D for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 geoosc481kYE for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:47:41 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7316611E8184 for <ietf@ietf.org>; Sat,  3 Aug 2013 05:47:29 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUfz74XPiHNvfsV6xEpQ69hSwX87yTTN8@postini.com; Sat, 03 Aug 2013 05:47:29 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1855D1B8294 for <ietf@ietf.org>; Sat,  3 Aug 2013 05:47:29 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1244C190060; Sat,  3 Aug 2013 05:47:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 05:47:29 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: 6tsch BoF
Thread-Topic: 6tsch BoF
Thread-Index: AQHOjpRUXHUCY2plmUOb4HszrvBChJmAh0KAgAAkQgCAACMzgIAAGVkAgACa0+qAAjk3AA==
Date: Sat, 3 Aug 2013 12:47:27 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net>
In-Reply-To: <6.2.5.6.2.20130801225725.0d388d50@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8F73A65299BF644DADF5882510168D43@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, Andy Bierman <andy@yumaworks.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 12:47:48 -0000

On Aug 2, 2013, at 9:13 AM, SM <sm@resistor.net> wrote:
> In my opinion part of the answer has been provided by Brian Carpenter.  T=
he other part of the answer is the minutes.  The rest of the answer is in s=
omething mentioned in the Note Well.

Do you think I said something that contradicts what Brian said?   I believe=
 that I agree with him.   But he's talking about how you ultimately determi=
ne consensus, whereas I was talking about what hums and shows of hands mean=
, and in what way they are useful.


From Ted.Lemon@nominum.com  Sat Aug  3 05:47:49 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C9BA21E809B for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 T+2QlShpxPVt for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 05:47:42 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF3E21F991F for <ietf@ietf.org>; Sat,  3 Aug 2013 05:47:35 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUfz757kG0gnCWvQXvFZvX2TjUcVOtBYZ@postini.com; Sat, 03 Aug 2013 05:47:35 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2CC051B8295 for <ietf@ietf.org>; Sat,  3 Aug 2013 05:47:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 261D7190060; Sat,  3 Aug 2013 05:47:35 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 05:47:35 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: 6tsch BoF
Thread-Topic: 6tsch BoF
Thread-Index: AQHOjpRUXHUCY2plmUOb4HszrvBChJmA8NmAgALTF4A=
Date: Sat, 3 Aug 2013 12:47:34 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775242081@mbx-01.win.nominum.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <51FA7F8D.9080308@dcrocker.net>
In-Reply-To: <51FA7F8D.9080308@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CC0DACF9CDBE4C4F8E0CCEF3770DA052@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 12:47:49 -0000

On Aug 1, 2013, at 5:32 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> Perhaps that doesn't bother other folk very much but the differential res=
ult was so extreme -- as a single-event experiment -- it strongly suggests =
we should not call for hand-raising.  (The likely explanations for the diff=
erence are pretty straightforward.  Whether our community of engineers want=
s to believe the explanations or not doesn't matter  The data should be suf=
ficiently compelling.)

I thought this was fascinating too.   And there may be some cultural issue =
at work here.   But letting the negative hums indicate a lack of consensus =
all by themselves would have been wrong: that's not how you determine conse=
nsus _either_.

So what do you think should have been done differently?

To be clear:

>> The other question raised in my mind is why the initial result from
>> the hum, which did not have a consensus either way, was not
>> sufficient.
>=20
> Exactly.  This is a point of working group management that should prompt =
some concern.

If when the hum comes out indeterminate, you conclude that you do not have =
consensus, you are holding a vote.


From mehmet.ersue@nsn.com  Sat Aug  3 07:36:57 2013
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 6F2E711E8139 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 07:36:57 -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.037, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iOdu5iiwZSjl for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 07:36:52 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9CB21F99CD for <ietf@ietf.org>; Sat,  3 Aug 2013 07:36:47 -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 r73EagVd024112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 3 Aug 2013 16:36:42 +0200
Received: from DEMUHTC001.nsn-intra.net ([10.159.42.32]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r73EadwZ025024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 3 Aug 2013 16:36:39 +0200
Received: from DEMUHTC006.nsn-intra.net (10.159.42.37) by DEMUHTC001.nsn-intra.net (10.159.42.32) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sat, 3 Aug 2013 16:36:39 +0200
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.59]) by DEMUHTC006.nsn-intra.net ([10.159.42.37]) with mapi id 14.03.0123.003; Sat, 3 Aug 2013 16:36:38 +0200
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: "Ted.Lemon@nominum.com" <Ted.Lemon@nominum.com>, "glenn.deen@nbcuni.com" <glenn.deen@nbcuni.com>
Subject: AW: Re: Berlin was awesome, let's come again
Thread-Topic: Re: Berlin was awesome, let's come again
Thread-Index: AQHOkFbcQEclyPfhkUSaqX4/jrvVpQ==
Date: Sat, 3 Aug 2013 14:36:38 +0000
Message-ID: <ftuu5gxg3xefgn0y4rhdlatd.1375540587757@email.android.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <74D7DE94-7505-493E-9A99-5DCBD43B3633@tzi.org>, <51FB9CD8.7040109@gmail.com> <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>, <8D23D4052ABE7A4490E77B1A012B630775242039@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775242039@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_ftuu5gxg3xefgn0y4rhdlatd1375540587757emailandroidcom_"
MIME-Version: 1.0
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: 3376
X-purgate-ID: 151667::1375540603-00003561-6F37E011/0-0/0-0
Cc: "cabo@tzi.org" <cabo@tzi.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Ersue, Mehmet \(NSN - DE/Munich\)" <mehmet.ersue@nsn.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, 03 Aug 2013 14:36:57 -0000

--_000_ftuu5gxg3xefgn0y4rhdlatd1375540587757emailandroidcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

*+1*


Sent from my Galaxy S3.



-------- Urspr=FCngliche Nachricht --------
Von: ext Ted Lemon <Ted.Lemon@nominum.com>
Datum:
An: "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni.com>
Cc: Carsten Bormann <cabo@tzi.org>,"ietf@ietf.org list" <ietf@ietf.org>
Betreff: Re: Berlin was awesome, let's come again


On Aug 2, 2013, at 1:56 PM, "Deen, Glenn (NBCUniversal)" <glenn.deen@nbcuni=
.com> wrote:
> -1 on doing it during the winter speaking as a Californian who doesn't ev=
en own a winter coat

A winter coat used to be a prerequisite for attending winter IETF, and I do=
n't think that's a bad thing.   You can do quite well in a climate like Ber=
lin's with a stylish suit coat and jacket, plus a scarf and gloves, if you =
prefer not to go the winter coat route.   The styley route is much more exp=
ensive, but you can wear it on those days in LA when it's 50 degrees (f) ou=
t, rare though they may be.   It's also good in San Francisco weather.

Bottom line: IETF _probably_ shouldn't decide where to host its winter meet=
ings on the basis of the completeness of your wardrobe... ;)


--_000_ftuu5gxg3xefgn0y4rhdlatd1375540587757emailandroidcom_
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 Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>*&#43;1*</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style=3D"font-size:75%; color:#575757">Sent from my Galaxy S3.</div>
</div>
<br>
<br>
<br>
-------- Urspr=FCngliche Nachricht --------<br>
Von: ext Ted Lemon &lt;Ted.Lemon@nominum.com&gt; <br>
Datum: <br>
An: &quot;Deen, Glenn (NBCUniversal)&quot; &lt;glenn.deen@nbcuni.com&gt; <b=
r>
Cc: Carsten Bormann &lt;cabo@tzi.org&gt;,&quot;ietf@ietf.org list&quot; &lt=
;ietf@ietf.org&gt; <br>
Betreff: Re: Berlin was awesome, let's come again <br>
<br>
<br>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">On Aug 2, 2013, at 1:56 PM, &quot;Deen, Glenn (NBC=
Universal)&quot; &lt;glenn.deen@nbcuni.com&gt; wrote:<br>
&gt; -1 on doing it during the winter speaking as a Californian who doesn't=
 even own a winter coat<br>
<br>
A winter coat used to be a prerequisite for attending winter IETF, and I do=
n't think that's a bad thing.&nbsp;&nbsp; You can do quite well in a climat=
e like Berlin's with a stylish suit coat and jacket, plus a scarf and glove=
s, if you prefer not to go the winter coat
 route.&nbsp;&nbsp; The styley route is much more expensive, but you can we=
ar it on those days in LA when it's 50 degrees (f) out, rare though they ma=
y be.&nbsp;&nbsp; It's also good in San Francisco weather.<br>
<br>
Bottom line: IETF _probably_ shouldn't decide where to host its winter meet=
ings on the basis of the completeness of your wardrobe... ;)<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_ftuu5gxg3xefgn0y4rhdlatd1375540587757emailandroidcom_--

From heas@shrubbery.net  Sat Aug  3 08:56:48 2013
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3454921F9F98; Sat,  3 Aug 2013 08:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybOLHE9SAq2q; Sat,  3 Aug 2013 08:56:43 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26C6B21F8546; Sat,  3 Aug 2013 08:56:43 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 81594AF19; Sat,  3 Aug 2013 15:56:42 +0000 (UTC)
Date: Sat, 3 Aug 2013 15:56:42 +0000
From: heasley <heas@shrubbery.net>
To: Greg Shepherd <gjshep@gmail.com>
Subject: Re: Berlin was awesome, let's come again
Message-ID: <20130803155642.GD5666@shrubbery.net>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <10229F86C86EB444898E629583FD4171BDE2ABD0@PACDCEXMB06.cable.comcast.com> <CABmDk8naBLVDgUPXYCq-gp4GcCa_iNNt4LrJsAHP++i_BAPERg@mail.gmail.com> <CABFReBp9M+q7fGsojKT+YiYF09MBjDMZMo4rY_nq-b79TVbiFQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABFReBp9M+q7fGsojKT+YiYF09MBjDMZMo4rY_nq-b79TVbiFQ@mail.gmail.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IAOC List <iaoc@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, 03 Aug 2013 15:56:48 -0000

Sat, Aug 03, 2013 at 03:39:27AM -0700, Greg Shepherd:
> On Fri, Aug 2, 2013 at 5:53 AM, Mary Barnes <mary.h.barnes@gmail.com> wrote:
> 
> > I did have some annoyances with the housekeeping, in particular the
> >  rewashing of glasses/mugs in the bathroom sink and someone else's soap bar
> > ending up in my bathroom.
> >
> 
> Can I have my soap back?

i wear shoes.

> 
> > On Fri, Aug 2, 2013 at 6:49 AM, Livingood, Jason <
> > Jason_Livingood@cable.comcast.com> wrote:
> >
> >> +1
> >>
> >>
> >> Very productive venue, easy to access city, several hotels near the venue
> >> for alternatives, walkable area around the venue, lots of options for
> >> restaurants, good public transit system, etc. And I enjoyed the social &
> >> social venue as well (thanks DENIC)!
> >>
> >> I really do hope we return in the future - this location really has many
> >> of the things we as participants like.
> >>
> >> Thank you very much to all of the sponsors and volunteers!!
> >>
> >> Jason
> >>
> >> On 8/2/13 12:58 PM, "Eggert, Lars" <lars@netapp.com> wrote:
> >>
> >> >Venue was great, food options here and in the city were great, all-around
> >> >great experience. Let's come again!
> >> >
> >> >(I do kinda wonder how there wasn't a single local company willing to
> >> >step up to be the host. That's embarrassing to me as a German, esp. if
> >> >the IETF meets in the self-declared IT hub of Germany. Better luck next
> >> >time, I hope.)
> >> >
> >> >Lars
> >>
> >>
> >

From sm@resistor.net  Sat Aug  3 09:43:58 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B36AB21F8447 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 09:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxHHrM92f2LJ for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 09:43:58 -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 7CD5E21F9A10 for <ietf@ietf.org>; Sat,  3 Aug 2013 09:43:57 -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 r73GhnwQ015164; Sat, 3 Aug 2013 09:43:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375548235; bh=EmnISA7WD8BHCQR26hSF7Z2R9ClaMxBRauI+BIAGt3o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uJzvYTSJ3Umlc9W6vY02ztUMx5TjMYKH7+MBSflX35BYQTLpkc3yR10zmedErEpvB Z15iWRGGe0nwPDXUVTqCotevLZN1ykocZlk3z6GkRf0tZ1v+2RfVYw5sr0jNcO5od8 VPlRwU4Wv5fJj32yHoIW9tLR91b8Nyp+F3KTBnuI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375548235; i=@resistor.net; bh=EmnISA7WD8BHCQR26hSF7Z2R9ClaMxBRauI+BIAGt3o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SFBTt5UG9rubbf0Ou+6gedTWbMWSymY0Z4yudqcvEra9i7R/vdHo0GzrjU4ddro3P uunVhJLfMdO+FeBlSboIb8KCoeLZjry2w1ihNFnVauMOCHlOgI1Py7jdUXfJ3rIvRx N4jmhhJakwjlcuacCeLPY6UBy5LFv3HRWUqZGCpM=
Message-Id: <6.2.5.6.2.20130803084319.0c7289b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 03 Aug 2013 09:34:43 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>
From: SM <sm@resistor.net>
Subject: Re: 6tsch BoF
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominu m.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Andy Bierman <andy@yumaworks.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 16:43:59 -0000

Hi Ted,
At 05:47 03-08-2013, Ted Lemon wrote:
>Do you think I said something that contradicts what Brian said?   I 
>believe that I agree with him.   But he's talking about how you 
>ultimately determine consensus, whereas I was talking about what 
>hums and shows of hands mean, and in what way they are useful.

I don't think that Brian was talking about how you ultimately 
determine consensus.  Here is the last paragraph of Brian's message:

  "In the case of a WG-forming BOF, it seems to me that a nucleus
   of people willing and competent to do the work, and a good set of
   arguments why the work needs to be done and how it will make the
   Internet better, are more important than any kind of numbers game."

That one sentence covers all the points which are relevant.  It's an 
Area Director decision.  It does not require consensus or any kind of 
number game.

Regards,
-sm 


From scott.brim@gmail.com  Sat Aug  3 09:59:58 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B5E21F9F9E for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 09:59:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YUQQcGfqSXaG for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 09:59:55 -0700 (PDT)
Received: from mail-qe0-x22a.google.com (mail-qe0-x22a.google.com [IPv6:2607:f8b0:400d:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5898A21F9F84 for <ietf@ietf.org>; Sat,  3 Aug 2013 09:59:52 -0700 (PDT)
Received: by mail-qe0-f42.google.com with SMTP id s14so967031qeb.29 for <ietf@ietf.org>; Sat, 03 Aug 2013 09:59:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=rQ8t5WYxMXJiAZkCxnNJ9WeZw87tQ775TTs8X1BJ9Kk=; b=BX/wK5hqML5S1jNqn93+CP7xILyiVLSZ75EQ7W8q76e1p/wUEg8IOzO+v8ucohmuWy xcWSN18VGd/rfnLuppnS7Jr8xfDUb+t9vpoXxbH+Y67soEXFPdQ11gOoaXMKw0WPi7uF 12RtPnkWi0z+J14iTHTKtQXNVwfbN+zBg7SnSvgrwi3XuPmkE5NQ84lFitK0P6kni88q J5hke+ZAwKg+YwBZCQOV/JCYf1gChEimNZZFuZ2vXBNfTyIOQKOJDSnq2cbVunG78fZj b5cUtTUv6vMq4M0HTlW1yEkFiPVVHJ1EDjcTPxYBFrSYiPETYHRvfiwNVNCWT2gTDjN2 MIQw==
X-Received: by 10.49.47.84 with SMTP id b20mr15904510qen.83.1375549191802; Sat, 03 Aug 2013 09:59:51 -0700 (PDT)
Received: from swbi2mbp.local ([69.38.252.85]) by mx.google.com with ESMTPSA id g5sm1098338qai.9.2013.08.03.09.59.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 Aug 2013 09:59:50 -0700 (PDT)
Message-ID: <51FD3706.1030502@gmail.com>
Date: Sat, 03 Aug 2013 12:59:50 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <CADnDZ8-vUWB=KT+uvgrOUyhFG-2EoR08cwisvcfFbqygdD9+jQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-vUWB=KT+uvgrOUyhFG-2EoR08cwisvcfFbqygdD9+jQ@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Olle E. Johansson" <oej@edvina.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 16:59:58 -0000

AB, saving your entire message for context ... You're fixing the wrong
problem.  The problem is not finding a way to cloak so some unspecified
person doesn't experience abuse.  It's important that we all know who we
are dealing with.  The problem, rather, is what is leading you to think
anonymity might be useful, i.e. the alleged abuse itself.

Scott

On 08/03/13 02:41, Abdussalam Baryun allegedly wrote:
> Hi Adam,
> 
> I don't agree with you. I am a remote participant (2 years and never
> attended meetings) in the IETF organisation, do you think that IETF is
> fare in treating remote participants? I think the current IETF
> direction is in favor of attended-meeting participants, so IMHO one
> reason of some hidding their name is because the IETF still is not yet
> able to control wrong behaviour of participants who think they are
> well known. Thoes wrong behavior abuse peoples rights in IETF. If some
> are well known, the reason is because they got better opportunity in
> going to meetings, or that majority of participants are from two
> regions (North America+Europe).
> 
> For me the IETF reputation is about 40% (evaluated by asking close
> friends that did not participate and including the way I was treated
> within 2 years), still needs more work to build its reputation (e.g. I
> think some old participants need guidance to IETF visions). For me
> participants' good reputation depend on their reactions: if I get a
> nice reply from them, or if they don't only respond to known people,
> or if they acknowledge efforts, or if they encourage other into IETF
> visions, or if they provide good ideas/inputs, or if they manage
> work/WG/IETF well, etc.
> 
> In IETF volunteers' reputations SHOULD always be high and respected,
> but seems like the IETF give chance for abuse so its reputation makes
> some people prefer to be anonymous so they try to save their self
> reputation. We in IETF SHOULD not focus on people's reputation, we
> SHOULD focus on ideas, reasons, work-quality, documents/RFCs
> reputations and process-procedures reputations. We are here to
> document IETF reputation but not to document a person reputation or
> even his/her name. A person's name for me is only important when I
> want to refer to his/her review, draft, idea, etc. Don't forget that
> in procedure; any input into IETF is own also by IETF no matter what
> was the name given, so bad behaviour makes IETF reputation bad and
> then some people leave, or make anonymous names, or don't participate
> just listen. IMO, the majority of subscribers (in WGs) are listeners
> with zero participation.
> 
> AB
> 
> On 8/2/13, Adam Roach <adam@nostrum.com> wrote:
>> Moving to ietf@ietf.org, since I think this is not in any way specific
>> to Berlin.
>>
>>
>> On 8/2/13 12:24, Olle E. Johansson wrote:
>>> In rtcweb we have remote participants that prefer anonymity for a number
>>> of reasons.
>>
>> I'm going to make a broad assumption that the "number of reasons" all
>> relate to privacy. If that is incorrect, please weigh in.
>>
>>> The question is how this is handled in regards to note well, when they
>>> want jabber scribes to relay opinions or proposals to the meeting.
>>>
>>> Just a note for the future. I think we should allow anonymous listeners,
>>> but should they really be allowed to participate?
>>>
>>
>> We had a previous conversation around pseudonyms, which I think
>> concluded that pseudonyms are pretty much okay (and impossible to
>> reliably detect anyway).
>>
>> Given this fact, someone can protect their identity through use of a
>> consistent pseudonym. This has the property of developing a persona
>> behind that pseudonym that the working group members can reasonably
>> interact with.
>>
>> By contrast, attempting to participate in a truly anonymous fashion
>> rather than participating with a pseudonym seems to have very little
>> justification, with significant potential drawback for the working
>> group. The privacy implications are pretty much identical, but it
>> provides the illusion that one can act in a way that has no impact on a
>> persona's reputation. IMHO, this is ripe for bad behavior, bad faith
>> participation, and other abuses.
>>
>> Given the availability of pseudonymous participation, I don't think we
>> need to tolerate anonymous participation.
>>
>> /a
>>
>>

From scott.brim@gmail.com  Sat Aug  3 10:02:50 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1A121F9F5F for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 10:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4NbRGP4YT1bE for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 10:02:50 -0700 (PDT)
Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DC0E621F9B11 for <ietf@ietf.org>; Sat,  3 Aug 2013 10:02:47 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id a1so939031qcx.31 for <ietf@ietf.org>; Sat, 03 Aug 2013 10:02:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=YHFR5ZHGEZ0r9T/Bm1GfNX01TsCiAKb2f4MYN8/s5AQ=; b=L7JKq42u56i1ju2otvOEzFOakEPD98WHfZv3oHQpJ16UtmLIpCt/uELdIdbs70XXsh Mh0S0k5ELBVB5ElBUr8dvnaMma8hZLg39PgpDoR3wIaZaMDyo/NYx0/rOqKFKoRp7IpJ BwZx+JaC49Ge0wtDsI5I/Id88HX/6QkQo2iD/4s/tT0XJy1ZANgNJY8gy3OFza33jFWQ phK/cYP80ftmsjW2J4mLqtpw4lG1KAjw7fKLswyC87TAXfQY64ALndbQlXW0pphHta3Z PHB1mOtUOSBy0UT/024Po8dmEsktrOFrShPRSMsVLbN8lqNoDadtduQs+Srgfvusvwoe jbVQ==
X-Received: by 10.49.29.106 with SMTP id j10mr16212581qeh.37.1375549367390; Sat, 03 Aug 2013 10:02:47 -0700 (PDT)
Received: from swbi2mbp.local ([69.38.252.85]) by mx.google.com with ESMTPSA id y1sm3062078qaj.2.2013.08.03.10.02.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 Aug 2013 10:02:46 -0700 (PDT)
Message-ID: <51FD37B5.3010801@gmail.com>
Date: Sat, 03 Aug 2013 13:02:45 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
References: <01b501ce902e$96092480$c21b6d80$@olddog.co.uk>
In-Reply-To: <01b501ce902e$96092480$c21b6d80$@olddog.co.uk>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'Heasley' <heas@shrubbery.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 17:02:50 -0000

On 08/03/13 05:48, Adrian Farrel allegedly wrote:
> Have you considered not reading it?

+1.  Especially during IETF week, people on various lists are losing
track of their delete key, or the ability to set mail filter rules.

From cos@mip.polyamory.org  Sat Aug  3 10:27:35 2013
Return-Path: <cos@mip.polyamory.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99EBD11E8120 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 10:27: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 nXE+DtvYXmyC for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 10:27:30 -0700 (PDT)
Received: from mip.polyamory.org (mip.aaaaa.org [199.201.145.10]) by ietfa.amsl.com (Postfix) with ESMTP id 836DE11E80E0 for <ietf@ietf.org>; Sat,  3 Aug 2013 10:27:22 -0700 (PDT)
Received: by mip.polyamory.org (Postfix, from userid 1002) id 4E4F710760; Sat,  3 Aug 2013 13:27:15 -0400 (EDT)
Date: Sat, 3 Aug 2013 13:27:15 -0400
From: Ofer Inbar <cos@aaaaa.org>
To: dcrocker@bbiw.net
Subject: Re: 6tsch BoF
Message-ID: <20130803172715.GE29401@mip.aaaaa.org>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <51FA7F8D.9080308@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <51FA7F8D.9080308@dcrocker.net>
User-Agent: Mutt/1.4.2.3i
Organization: American Association Against Acronym Abuse
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 17:27:35 -0000

Dave Crocker <dhc@dcrocker.net> wrote:
> On 8/1/2013 10:50 AM, Ralph Droms wrote:
> > In particular, the effect of humming versus
> >show of hands was pretty obvious.
> 
> The fact that the results were so profoundly different should get our 
> attention, enough to get us to consider specifying how to measure 
> consensus.  From the data you cited, it appears that raising hands 
> carries some sort of social onus, at least for some people some times, 
> that raising hands does not.

Unless I missed something, it was not clear how much of the effect was
due to hands vs. hum, and how much of it was due to people being asked
a second time after they'd already seen (err, heard) the sense of the
room when it was asked just previously.
  -- Cos

From Ted.Lemon@nominum.com  Sat Aug  3 13:14:09 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 413ED21F9C9A for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 13:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level: 
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 yBG7qljlzNkb for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 13:13:59 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 9A5A021F9C05 for <ietf@ietf.org>; Sat,  3 Aug 2013 13:13:59 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUf1khlA9JXOdYrENGn7c0adXwTWlEC6w@postini.com; Sat, 03 Aug 2013 13:13:59 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 39B901B8261 for <ietf@ietf.org>; Sat,  3 Aug 2013 13:13:58 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 18E70190060; Sat,  3 Aug 2013 13:13:58 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sat, 3 Aug 2013 13:13:52 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: 6tsch BoF
Thread-Topic: 6tsch BoF
Thread-Index: AQHOjpRUXHUCY2plmUOb4HszrvBChJmAh0KAgAAkQgCAACMzgIAAGVkAgACa0+qAAjk3AP//+ApMgACv/IA=
Date: Sat, 3 Aug 2013 20:13:52 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752425EA@mbx-01.win.nominum.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com> <6.2.5.6.2.20130803084319.0c7289b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130803084319.0c7289b8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2EBC9FCECE89E642B88EA37554D679D1@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, Andy Bierman <andy@yumaworks.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 20:14:09 -0000

On Aug 3, 2013, at 6:34 PM, SM <sm@resistor.net> wrote:
> That one sentence covers all the points which are relevant.  It's an Area=
 Director decision.  It does not require consensus or any kind of number ga=
me.

The working group charter explicitly requires IETF consensus.   But if you =
mean getting the charter out of the BoF, I think you are right.


From johnl@iecc.com  Sat Aug  3 14:20:19 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D091921E8088 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.952
X-Spam-Level: 
X-Spam-Status: No, score=-109.952 tagged_above=-999 required=5 tests=[AWL=-0.612, BAYES_20=-0.74, 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 uu4K-UEKyarZ for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:20:14 -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 CDA8411E80A2 for <ietf@ietf.org>; Sat,  3 Aug 2013 14:20:13 -0700 (PDT)
Received: (qmail 17325 invoked from network); 3 Aug 2013 21:20:12 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Aug 2013 21:20:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51fd740c.xn--btvx9d.k1308; i=johnl@user.iecc.com; bh=UGoDYWpksAyVzmL0p0kGmH8gt3GNetL86YxG1O6lUNU=; b=nYUKDtCvlKO+UYH3ynI1He2AyRMOcEhVTxsowcShUIY24XueMc5cyaYvwf1jzvgoYJeL0K1Lc6X+/zIfh7ed3KTKLCQT7X6R6bgBPgX92G2rhFjIxV/lIyDNZzBbaEuGjlVNV8aB19Sve9JNhCCWdGHKCRTP/0aftZCBtgrCTL2G9sSdNPqerd6r8+LhvUJJRfVkwZwEK7kRIsZVwNv0rPF8rwLaU4IAmtCFQMUsT/1bEA4srNB+9ayJGpy5NGDC
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51fd740c.xn--btvx9d.k1308; olt=johnl@user.iecc.com; bh=UGoDYWpksAyVzmL0p0kGmH8gt3GNetL86YxG1O6lUNU=; b=RCfYsrTuF3GeYccbPpHeP+KMfWy5N5N5n9ASnNwokNygS95o+UevZrrT7VJpgEjXkGy+7fBnj4bF5l9fQWKieKMFXqJv4uDYby0eUs82RDubdRT5ep53QhDC1J0817NQ7Cbl+5g3a3y+VJE0rWeJ/TcOTSB4eFV6Gl3FlHoliM9zwVdtP0K+wffyiG8Q4MWaneATSN2NpKsQi2A+Z5p8mJlS9fyrsm/pPoGFtzkIdnV1016/m5mSHX56ByvfHf23
Date: 3 Aug 2013 21:19:49 -0000
Message-ID: <20130803211949.2988.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 21:20:19 -0000

>Venue was great, food options here and in the city were great,
>all-around great experience. Let's come again!

Agreed.  Great meeting overall, venue worked well, plenty of places
to eat and stay within reasonable distance, and suitable distractions
for those half days when you don't have any sessions.

Perhaps next time we can come to Berlin sometime other than the middle
of the summer to avoid the heat issues.

R's,
John

From johnl@iecc.com  Sat Aug  3 14:21:07 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2C421F9F6F for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.835
X-Spam-Level: 
X-Spam-Status: No, score=-110.835 tagged_above=-999 required=5 tests=[AWL=0.364, 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 boJ1sUgXtyzi for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:21:03 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 839F721E80AD for <ietf@ietf.org>; Sat,  3 Aug 2013 14:21:02 -0700 (PDT)
Received: (qmail 17567 invoked from network); 3 Aug 2013 21:21:01 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Aug 2013 21:21:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51fd743d.xn--9vv.k1308; i=johnl@user.iecc.com; bh=hRzNNicoERKECfcRELxdPczZas/18TwMiK9dubg5vVQ=; b=LyNBTG6HuWw9FXPMDP+SRSEwPzYp5GVsz0srjKAVACgqVIjYUC/olbI8KRVk62YbWVvKmt9bvFL1wo3X7C+plQXYor5ybC+ho6DZPWhfhi8tWs1xp9WxALdSDkbwcfydVcmkdEoY9p5bZyZ3sbgwgvv7cesIK2fvqJ2UGEZ7yXWvyqBogk+neCWdkRM94PW1nZBR0js4Q7Ez+2/3L0T5J9BYJPACmcX6GE5VUOCkEvd5MMxkB5qC3i4Eya8si6lH
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51fd743d.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=hRzNNicoERKECfcRELxdPczZas/18TwMiK9dubg5vVQ=; b=UpTJS/6J3MaEJi0yw0vE6amtb9czYcnX/8XeuwKg4rJlIRqW+TuKw04sT4z6Wcuv3B9awUFnxvK57HmIebqVOkEd6MSrEagYC9YhylB20jVUGRnCdBgNjBtNIPEZHmzSKyR8+evhxBXkcrGPTHJ1jzCfdj+ir1h8dOnIw+SSmfYa60s2N2ykcZlkiHDgsFAb4BfYz8wOjJ9IYb3PUecU8OY1fXXJpdxnfTzcOPWaB0XNzktGKTMKmGZwHldkh/F/
Date: 3 Aug 2013 21:20:39 -0000
Message-ID: <20130803212039.3010.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <EDD786D8-28EA-4150-A16B-BEB6758288F5@nbcuni.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 21:21:07 -0000

>-1 on doing it during the winter speaking as a Californian who doesn't
>even own a winter coat

I expect you could get a very nice one at KaDeWe.


From barryleiba.mailing.lists@gmail.com  Sat Aug  3 14:23:55 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22F1621F85E6 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.971
X-Spam-Level: 
X-Spam-Status: No, score=-101.971 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M03cQ2N+hk9T for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:23:54 -0700 (PDT)
Received: from mail-vb0-x235.google.com (mail-vb0-x235.google.com [IPv6:2607:f8b0:400c:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 28F1621F8B35 for <ietf@ietf.org>; Sat,  3 Aug 2013 14:23:54 -0700 (PDT)
Received: by mail-vb0-f53.google.com with SMTP id i3so1746031vbh.12 for <ietf@ietf.org>; Sat, 03 Aug 2013 14:23:53 -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=fHWYtU4HWPHfrMXLxJyMMbym6f8VZNJ9Y8y16ZMfmEU=; b=wzJlu53wF9zFt4UXza9tUOQPvt0XBtOmpeOc3ES8SIcaMRtUDDr+fjxhKNCmn5mB46 tLYesU3R+FgHUOE6vW1c7kuml/gljz1Ef9QgyAMB6Ajmh+00cTjr5PUR9Dn5CG3ohVxf K03yBawx4BaDhVIB2cQOk6q6EGQDa/eWYIr8lmcbv5H+/5LkwqmQDem4t+BO1yo/bOr5 1Ce3zFx+JT6sSdZnCoHPr0+4TKb+JY0MJy0SNshZoV0XjK8fN7qWdMknT6WQLguBFJgf TqEHWKceSZDNROGm2AMbp3ypXNb34CR7E78SmE4aHP+uhEWHx1CeLeAjBsRJMAQ6imih //xw==
MIME-Version: 1.0
X-Received: by 10.58.207.195 with SMTP id ly3mr3855415vec.77.1375565033032; Sat, 03 Aug 2013 14:23:53 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Sat, 3 Aug 2013 14:23:52 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130803084319.0c7289b8@resistor.net>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com> <6.2.5.6.2.20130803084319.0c7289b8@resistor.net>
Date: Sat, 3 Aug 2013 23:23:52 +0200
X-Google-Sender-Auth: Pl7E7a2RREPA5zQvLYYmoPs80No
Message-ID: <CAC4RtVDo6RhE-i3ipK8YjA6S5+KBQ=iP66opbFS7FEMeKiXoXA@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Andy Bierman <andy@yumaworks.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, 03 Aug 2013 21:23:55 -0000

>  "In the case of a WG-forming BOF, it seems to me that a nucleus
>   of people willing and competent to do the work, and a good set of
>   arguments why the work needs to be done and how it will make the
>   Internet better, are more important than any kind of numbers game."
>
> That one sentence covers all the points which are relevant.  It's an Area
> Director decision.  It does not require consensus or any kind of number
> game.

Well, where the hum is useful here (and why I prefer to use raised
hands for this particular point) is that, while I don't much care what
the *numbers* are, I very much *do* care if there are objections, and
I need to hear what those objections are.  That's critical.  For that,
I need to have those with the objections willing to be identified and
to tell me what the issues are.

Barry, being an AD and all.

From barryleiba.mailing.lists@gmail.com  Sat Aug  3 14:25:52 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4605621F8B35 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.971
X-Spam-Level: 
X-Spam-Status: No, score=-101.971 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q7Dn5DUbxoW2 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:25:52 -0700 (PDT)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D515321F85D1 for <ietf@ietf.org>; Sat,  3 Aug 2013 14:25:51 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id oz10so1922795veb.31 for <ietf@ietf.org>; Sat, 03 Aug 2013 14:25:51 -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=Z8zW9dHp/34y3mvM//G2xq6Jjzls/92KtBq48/A6cwE=; b=G642K/sxhiwFQO1JQUTEkJAW6S3il7sIDmhtRDIxpDRR1ZUkZMmagq1MjFDunvOoK9 NLk+ImU7Tot0DfUbUuEUO28CVW9ym1viMXzMqr2eenwt4qcclqoVNH5OzGgNMloFwV13 /Y4wQrtpj40xdsQtcC/FLaoMO4rU02uULOM7Diib6jpymMlCnpnx5SH9eonhfkwNw4fi a6AHcu8W+a71+7WonIo/AfHWO1wk7hREuKCMHiZEy130Y+etYwJ4LOCqaoqb7oTms8OS WZRJCGOjbX+Hu0mkTd28GzX8CT4jHEdQBgwRa8yhhtDrfB2QwcEt5+NBuFHcc7FMni/V ru6g==
MIME-Version: 1.0
X-Received: by 10.52.27.6 with SMTP id p6mr1577972vdg.77.1375565151259; Sat, 03 Aug 2013 14:25:51 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Sat, 3 Aug 2013 14:25:51 -0700 (PDT)
In-Reply-To: <20130803211949.2988.qmail@joyce.lan>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <20130803211949.2988.qmail@joyce.lan>
Date: Sat, 3 Aug 2013 23:25:51 +0200
X-Google-Sender-Auth: Ho41BdpgUCikqsTep1WlrE4ue0Q
Message-ID: <CAC4RtVC+6wKiGrQmdv64+56kW9FSNUTTmV4O1NgSxFjwQ6LOpg@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Barry Leiba <barryleiba@computer.org>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 21:25:52 -0000

> Agreed.  Great meeting overall, venue worked well, plenty of places
> to eat and stay within reasonable distance, and suitable distractions
> for those half days when you don't have any sessions.

Hm.

What are these meeting-free half-days of which you speak?  ........

Barry

From johnl@iecc.com  Sat Aug  3 14:35:30 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1581411E80AD for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.861
X-Spam-Level: 
X-Spam-Status: No, score=-110.861 tagged_above=-999 required=5 tests=[AWL=0.338, 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 jy23yZRxGcBq for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 14:35: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 C0B4921F9CF2 for <ietf@ietf.org>; Sat,  3 Aug 2013 14:35:25 -0700 (PDT)
Received: (qmail 21359 invoked from network); 3 Aug 2013 21:35:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Aug 2013 21:35: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; s=51fd779d.xn--9vv.k1308; i=johnl@user.iecc.com; bh=OM85l+VyjF0Zu489c9oMbGUj/P6564ls/7bW2ozsReQ=; b=lQvInqPIgbFVSsisbRDAT+xA85JWKrnNY0Rdhq3MEpLjCAPAwIbXCPcqbeBRklNu+BJmQc6OilZGe2zKUIl/7cBLpvnaYhqUg9D8lV7wZe3HFigE0A3nCcL2d6pZqpJ4a842C2ZEFMRUqpVsj8/a5LwA6GK15DJcCnM3ma1yaLbMZlkI2DfsWahkWF4MOMujTCPCJmQb+L7YeFfzstVwtyju+iqBnEP/loXCfpMgOy0X+qVCMHKIIChU7GxNlhn3
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51fd779d.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=OM85l+VyjF0Zu489c9oMbGUj/P6564ls/7bW2ozsReQ=; b=C2ApWfM9fbm21Yp4u/wURcefyyfQBhY7hOh3MpqAaKlbSjHttVu3fmLzMFwOGcr0xWaGUNKLl42Wg2B+ylTF99wXnC1JU/eBvZq/RT3zmzx1jmo4VFXDIqG4BjK7qf3hLLmW4l07MjdsdMeqm4eB4O4NLhfESFpw9O04IDIdkC+H+LXkNEx1BShjleC/94qXNcvkYzOSa/2rave2D1NTqbLMpYE28pktUvvajGf/dmywpX//E4jokvVyfwgy4M8w
Date: 3 Aug 2013 21:35:02 -0000
Message-ID: <20130803213502.3073.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <6462.1375450137@sandelman.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 21:35:30 -0000

In article <6462.1375450137@sandelman.ca> you write:
>-=-=-=-=-=-
>
>
>Many countries let you claim VAT paid as you leave.

Only on goods you export, not on hotels and meals.

I hope the IETF can figure out how to more efficiently reclaim the VAT
it pays on European expenses so the whole thing is a wash.

R's,
John

From ulrich@herberg.name  Sat Aug  3 15:06:13 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCAB511E80D2 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 15:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 NNW4WkDwPX6h for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 15:06:12 -0700 (PDT)
Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0F40A21F9C13 for <ietf@ietf.org>; Sat,  3 Aug 2013 15:06:11 -0700 (PDT)
Received: by mail-vb0-f46.google.com with SMTP id p13so1735325vbe.5 for <ietf@ietf.org>; Sat, 03 Aug 2013 15:06:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3J+IIjBFuSwCnPuEmRz41onilZ2hDAKzKjZ2/EcsPgE=; b=ZWKmzFRCX4o0L6dlCB0XS4+6bXS3lqgsMDzPRj5vEbzQwn5hRN6ZgFD2eCgY2P1AHk dxiWBj3VQyME4AuVPgHk2sGPz0aoPlbZ3j7rhS8DiE+aizeCn7DUGRx4WBwlyTL7Ghrq xs+fvzu3XgI5Nw8UBUNQKd6beHt7EtcvyqLMc=
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=3J+IIjBFuSwCnPuEmRz41onilZ2hDAKzKjZ2/EcsPgE=; b=StjF1wc0XPMjx+e8W4Tcs494DZVpCdxH/Zr7IBOiFnm4XhNWNw09MHtUGeyckOZVaV S6kbZO0F/RpljUTYNDl/HryC8YqBU0sZ/JfD/p4scO27sIuXg9aAdOvaxlzTXrnPCw+F TNmF/ITU8XctCy0DCYJ6HaRJ2k+1lJie0PCp3kH7VhB1Oq9N+WHbJ0pcapxIZcKQQOlA kBhh1u4WcKuxom7aRl9Zt+XL2XtLTxdgD0FM5dBq6yNgnvDkxG2vuS+x/H0mxM2UBOz3 4MFK5CxsSSAtB8C43LUSXx/A9L+Cj6v5w3LbXhguyzeZ670PKavjXL0N2n1BMzxav6bC Iseg==
MIME-Version: 1.0
X-Received: by 10.58.128.71 with SMTP id nm7mr3905824veb.51.1375567570502; Sat, 03 Aug 2013 15:06:10 -0700 (PDT)
Received: by 10.221.55.70 with HTTP; Sat, 3 Aug 2013 15:06:10 -0700 (PDT)
In-Reply-To: <20130803211949.2988.qmail@joyce.lan>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com> <20130803211949.2988.qmail@joyce.lan>
Date: Sun, 4 Aug 2013 00:06:10 +0200
Message-ID: <CAK=bVC-AvD95h5ucWcVXFxQSeJBveUJNBaqjb8xBHdDvnqh2rg@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Ulrich Herberg <ulrich@herberg.name>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQngyeaDD0036zEfHsIQ+kzDdhwvYTN6LCvbhLjt9TQMoKccy4wooyeIdIxZZsgUyiD4HEda
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Aug 2013 22:06:13 -0000

John,

I think that the heat was exceptional. I have grown up in Munich, and
I have rarely ever seen it that hot (either in Munich or Berlin).
Maybe it's global warming? ;-)

Ulrich

On Sat, Aug 3, 2013 at 11:19 PM, John Levine <johnl@taugh.com> wrote:
>>Venue was great, food options here and in the city were great,
>>all-around great experience. Let's come again!
>
> Agreed.  Great meeting overall, venue worked well, plenty of places
> to eat and stay within reasonable distance, and suitable distractions
> for those half days when you don't have any sessions.
>
> Perhaps next time we can come to Berlin sometime other than the middle
> of the summer to avoid the heat issues.
>
> R's,
> John

From l.wood@surrey.ac.uk  Sat Aug  3 15:27:22 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144A321E809E for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 15:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mi40t71K1dyv for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 15:27:17 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.137]) by ietfa.amsl.com (Postfix) with ESMTP id CE59B11E80E3 for <ietf@ietf.org>; Sat,  3 Aug 2013 15:27:16 -0700 (PDT)
Received: from [85.158.136.51:4368] by server-1.bemta-5.messagelabs.com id AB/63-21460-2C38DF15; Sat, 03 Aug 2013 22:27:14 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-49.messagelabs.com!1375568833!19792628!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1890 invoked from network); 3 Aug 2013 22:27:13 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-2.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 3 Aug 2013 22:27:13 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sat, 3 Aug 2013 23:27:13 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <adam@nostrum.com>
Date: Sat, 3 Aug 2013 23:27:12 +0100
Subject: RE: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
Thread-Topic: Anonymity versus Pseudonymity (was Re: [87attendees] procedural	question with remote participation)
Thread-Index: Ac6QFJjPhIXd+yNkSGiHYZyYMFMujwAgm0P3
Message-ID: <290E20B455C66743BE178C5C84F1240822406074FA@EXMB01CMS.surrey.ac.uk>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com>, <CADnDZ8-vUWB=KT+uvgrOUyhFG-2EoR08cwisvcfFbqygdD9+jQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-vUWB=KT+uvgrOUyhFG-2EoR08cwisvcfFbqygdD9+jQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: oej@edvina.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 22:27:22 -0000

AB,

You write
"Some people prefer to be anonymous so they try to save their self reputati=
on"

Are you pursuing this line of argument because, after
- campaigning for but failing to achieve the abolition of April 1 RFCs
- campaigning for but failing to achieve an acknowledgement in a MANET draf=
t you didn't write.
- campaigning for changes to the posting summary that now regularly lists y=
ou as Number One poster on this list

You believe that your reputation is harmed, would require saving for meanin=
gful interaction, and that you need pseudonymity?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam=
 Baryun [abdussalambaryun@gmail.com]
Sent: 03 August 2013 07:41
To: Adam Roach
Cc: Olle E. Johansson; ietf@ietf.org
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedura=
l    question with remote participation)

Hi Adam,

I don't agree with you. I am a remote participant (2 years and never
attended meetings) in the IETF organisation, do you think that IETF is
fare in treating remote participants? I think the current IETF
direction is in favor of attended-meeting participants, so IMHO one
reason of some hidding their name is because the IETF still is not yet
able to control wrong behaviour of participants who think they are
well known. Thoes wrong behavior abuse peoples rights in IETF. If some
are well known, the reason is because they got better opportunity in
going to meetings, or that majority of participants are from two
regions (North America+Europe).

For me the IETF reputation is about 40% (evaluated by asking close
friends that did not participate and including the way I was treated
within 2 years), still needs more work to build its reputation (e.g. I
think some old participants need guidance to IETF visions). For me
participants' good reputation depend on their reactions: if I get a
nice reply from them, or if they don't only respond to known people,
or if they acknowledge efforts, or if they encourage other into IETF
visions, or if they provide good ideas/inputs, or if they manage
work/WG/IETF well, etc.

In IETF volunteers' reputations SHOULD always be high and respected,
but seems like the IETF give chance for abuse so its reputation makes
some people prefer to be anonymous so they try to save their self
reputation. We in IETF SHOULD not focus on people's reputation, we
SHOULD focus on ideas, reasons, work-quality, documents/RFCs
reputations and process-procedures reputations. We are here to
document IETF reputation but not to document a person reputation or
even his/her name. A person's name for me is only important when I
want to refer to his/her review, draft, idea, etc. Don't forget that
in procedure; any input into IETF is own also by IETF no matter what
was the name given, so bad behaviour makes IETF reputation bad and
then some people leave, or make anonymous names, or don't participate
just listen. IMO, the majority of subscribers (in WGs) are listeners
with zero participation.

AB

On 8/2/13, Adam Roach <adam@nostrum.com> wrote:
> Moving to ietf@ietf.org, since I think this is not in any way specific
> to Berlin.
>
>
> On 8/2/13 12:24, Olle E. Johansson wrote:
>> In rtcweb we have remote participants that prefer anonymity for a number
>> of reasons.
>
> I'm going to make a broad assumption that the "number of reasons" all
> relate to privacy. If that is incorrect, please weigh in.
>
>> The question is how this is handled in regards to note well, when they
>> want jabber scribes to relay opinions or proposals to the meeting.
>>
>> Just a note for the future. I think we should allow anonymous listeners,
>> but should they really be allowed to participate?
>>
>
> We had a previous conversation around pseudonyms, which I think
> concluded that pseudonyms are pretty much okay (and impossible to
> reliably detect anyway).
>
> Given this fact, someone can protect their identity through use of a
> consistent pseudonym. This has the property of developing a persona
> behind that pseudonym that the working group members can reasonably
> interact with.
>
> By contrast, attempting to participate in a truly anonymous fashion
> rather than participating with a pseudonym seems to have very little
> justification, with significant potential drawback for the working
> group. The privacy implications are pretty much identical, but it
> provides the illusion that one can act in a way that has no impact on a
> persona's reputation. IMHO, this is ripe for bad behavior, bad faith
> participation, and other abuses.
>
> Given the availability of pseudonymous participation, I don't think we
> need to tolerate anonymous participation.
>
> /a
>
>

From john-ietf@jck.com  Sat Aug  3 16:25:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCB621F9EF5 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 16:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I0-PdAYhuGI9 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 16:25:40 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EA00B21F9E98 for <ietf@ietf.org>; Sat,  3 Aug 2013 16:25:39 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V5lCW-00011i-10; Sat, 03 Aug 2013 19:25:32 -0400
X-Vipre-Scanned: 00673207002C3100673354-TDI
Date: Sat, 03 Aug 2013 19:25:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Olle E. Johansson" <oej@edvina.net>, Dan York <york@isoc.org>
Subject: Re: procedural question with remote participation
Message-ID: <ECF4A733EFD13FA1753C063B@[192.168.1.128]>
In-Reply-To: <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Aug 2013 23:25:46 -0000

--On Saturday, August 03, 2013 08:55 +0200 "Olle E. Johansson"
<oej@edvina.net> wrote:

>...
>>> Just a note for the future. I think we should allow
>>> anonymous listeners, but should they really be allowed to
>>> participate?
>> 
>> We don't allow anonymous comments at the microphone in
>> face-to-face meetings, requiring all people to clearly state
>> their names and have those names recorded in the meeting
>> minutes and in the Jabber log.    I don't see why we would
>> change this for remote participants.
>...
> (moving to ietf mailing list)
> 
> Absolutely.
> 
> Now, should we add an automatic message when someone joins the
> chat rooms, or a message when meetings begin that all comments
> made in the chat room is also participation under the note
> well?

Ole, 

First, probably to the "when meetings begin" part, but noting
that someone who gets onto the audio a few minutes late is in
exactly the same situation as someone who walks into the meeting
room a few minutes late -- announcements at the beginning of the
session are ineffective.

But, more generally...

I've said some of this in other contexts but, as a periodic
remote attendee, including being remote for IETF 87, I'd support
a more radical proposal, for example:

We regularize remote participation [1] a bit by doing the
following.  At some level, if remote participants expect to be
treated as serious members of the community, they (we) can
reasonably be expected to behave that way.

 * A mechanism for remote participants should be set up
	and remote participants should be to register.  The
	registration procedure should include the Note Well and
	any other announcement the IETF Trust, IAOC, or IESG
	consider necessary (just like the registration procedure
	for f2f attendance).
	
 * In the hope of increased equity, lowered overall
	registration fees, and consequently more access to IETF
	participation by a broader and more diverse community,
	the IAOC should establish a target/ recommended
	registration fee for remote participants.  That fee
	should reflect the portion of the registration fee that
	is not specifically associated with meeting expenses
	(i.e., I don't believe that remote participants should
	be supporting anyone's cookies other than their own).  
	
 * In the interest of maximum participation and inclusion
	of people are aren't attending f2f for economic reasons,
	I think we should treat the registration fee as
	voluntary, with people contributing all or part of it as
	they consider possible.  No questions asked and no
	special waiver procedures.  On the other hand,
	participation without registration should be considered
	as being in extremely bad taste or worse, on a par with
	violations of the IPR disclosure rules.
	
 * I don't see a practical and non-obtrusive way to
	enforce registration, i.e., preventing anyone
	unregistered from speaking, modulo the "bad taste"
	comment above.  But we rarely inspect badges before
	letting people stand in a microphone line either.

In return, the IETF generally (and particularly people in the
room) needs to commit to a level of seriousness about remote
participation that has not consistently been in evidence.  In
particular:

	* Remote participants should have as much access to mic
	lines and the ability to participate in discussions as
	those who are present in the room.   That includes
	recognizing that, if there is an audio lag and it takes
	a few moments to type in a question or comment, some
	flexibility about "the comment queue is closed" may have
	to be in order.  For some sessions, it might require
	doing what ICANN has started doing (at least sometimes),
	which is treating the remote participants as a separate
	mic queue rather than expecting the Jabber scribe (or
	remote participant messenger/ channeler) to get at the
	end of whatever line is most convenient.
	
	* It is really, really, important that those speaking,
	even if they happen to be sitting at the chair's table,
	clearly and carefully identify themselves.  Last week,
	there were a few rooms in which the audio was, to put it
	very politely, a little marginal.  That happens.  But,
	when it combines with people mumbling their names or
	saying them very quickly, the result is as little
	speaker identification as would have been the case if
	the name hadn't been used as all.  In addition, some of
	us suffer from the disability of not being able to keep
	track of unfamiliar voices while juggling a few decks of
	slides, a jabber session, audio, and so on.   "I
	identified myself 10 minutes ago" is not generally
	adequate.
	
	* On several occasions this week, slides were uploaded
	on a just-in-time basis (or an hour or so after that).
	The problem was aggravated by the meeting materials and
	tools agenda pages apparently either lacking "Expires"
	headers or having them set rather long as compared to
	in-meeting changes.  It seems to me that, if the IETF is
	serious about remote participation, pages that reflect
	very volatile material should have "expires" headers set
	to appropriately short intervals sometimes Sunday and be
	left that way until the end of the last session on
	Friday _and_ that it be clearly explained to people
	whose comments depend on visual materials that failure
	to get those materials uploaded before the meeting
	(except in the most unusual of situations) are badly
	hurting the IETF's ability to be open and inclusive.
	The only alternative I can think of to getting really
	serious about having material uploaded early is to have
	a high-reliability and decent resolution video feed of
	the slides or the screen on which they are being
	projected.  And that might still be inadequate for some
	remote participants.

Or we can decide that real participation in the IETF requires
that people be in the room, that remote participants are
involved on a "what you get is what you get" basis, and we stop
pretending otherwise.  For many reasons, I'm not enthused about
that idea, but the things that I, and others, are suggesting and
asking for will cost money and require some changes in the
ordinary way of doing things and it is only fair to mention the
alternative and suggest that it be explicitly considered.

best,
   john


[1] I do mean "participants" here.  I really don't care what the
lurkers do, or how anonymous they are as long as they remain
lurkers.  I object to anonymous participation in any standards
process, including the IETF one, for reasons that have been
discussed repeatedly on this list.


From scott.brim@gmail.com  Sat Aug  3 17:28:00 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF5921F9E48 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 17:28:00 -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 6-VAkWdN3y4m for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 17:27:59 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id C3AE021F9E34 for <ietf@ietf.org>; Sat,  3 Aug 2013 17:27:59 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k18so3832324oag.40 for <ietf@ietf.org>; Sat, 03 Aug 2013 17:27:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ojJuoJe1P4KhAQuadIOidahc/lCHqbyl/8jen0WffW8=; b=Bfz97eT8IQQsUibc3b5pmk+pfw9NlIHv/rIRK0uvaNmQvIZCk9I4c/0N2x3Ze9Lv7u gCCND4c40fN9YrKNUzJ7Liqf/hptCCHcy5KCFn689X/wYrHdQgqkKVqhUsPqWtmFNfyW TQd0nbFeQElRDb0o1to1vIYuuqIqICdxuoJB06RD+uG2x6gWkj1JHtxhviqJfedTKN4I 4jtpwTSUoS5MZMpICphnYBrj8EGfiaGFaaGwHO3xOKMDNQy49wtoCiIuVsogElUaQlJf uhwsZo89vc62+n42Jd8m+cjpwXHZxXbjI198y5J1c+/0SuXQAIYR7Wk9bydx3FuXUlmp 2kEQ==
X-Received: by 10.182.230.163 with SMTP id sz3mr9765205obc.81.1375576078267; Sat, 03 Aug 2013 17:27:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Sat, 3 Aug 2013 17:27:38 -0700 (PDT)
In-Reply-To: <CAC4RtVDo6RhE-i3ipK8YjA6S5+KBQ=iP66opbFS7FEMeKiXoXA@mail.gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com> <6.2.5.6.2.20130803084319.0c7289b8@resistor.net> <CAC4RtVDo6RhE-i3ipK8YjA6S5+KBQ=iP66opbFS7FEMeKiXoXA@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 3 Aug 2013 20:27:38 -0400
Message-ID: <CAPv4CP8b6u_6c+vVz9fmmNQJJPF9_j+yH249_fXKF+cERuZwxQ@mail.gmail.com>
Subject: Re: 6tsch BoF
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, Andy Bierman <andy@yumaworks.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, 04 Aug 2013 00:28:00 -0000

What did you think of Pete Resnick's draft about hums.

From brian.e.carpenter@gmail.com  Sat Aug  3 19:10:36 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 321DB21F9EA1; Sat,  3 Aug 2013 19:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4WPHT7ha1zuH; Sat,  3 Aug 2013 19:10:35 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF8021F9E88; Sat,  3 Aug 2013 19:10:35 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id p11so1973082pdj.4 for <multiple recipients>; Sat, 03 Aug 2013 19:10:35 -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=4FTqPEE3TCyDTOEqQtCZiJfpwECuAv3X81jXc2s7s/A=; b=sXt8Ze6cBBdTm/2Rd10CezF7dmL6tWiDSdIJ8weXH9fwT734Z82tL7rbAF8Zj/YNtQ GsmcN3J5m9LatD7PMjhhJMsATGA5RzUpyl4sSw7vrdYnSTjQtGMXYVqsFrNvEdjW3pK6 1vXcmHWuKiyOmsXsarbdXp7vRFzQLYziha6jBi302/xcnBBvvDddffOTPXC//ywPlpMM 4z2LOk2Vfs8Q18rIG/kHzzzZBYVuvmvjs0IDEKhuG2dLS8+M4IpTF1wNaZm40oMP1+wj Fenh1SS5cs9YzHoY1kv7/Ee3RXMSQG35rb/Lkp1HLBs7kJVdIgxVggxOvVNuPhT5Ncv5 qlAg==
X-Received: by 10.66.26.194 with SMTP id n2mr18147085pag.151.1375582233974; Sat, 03 Aug 2013 19:10:33 -0700 (PDT)
Received: from [192.168.178.23] (210.199.69.111.dynamic.snap.net.nz. [111.69.199.210]) by mx.google.com with ESMTPSA id mr3sm18870570pbb.27.2013.08.03.19.10.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 Aug 2013 19:10:33 -0700 (PDT)
Message-ID: <51FDB815.9000209@gmail.com>
Date: Sun, 04 Aug 2013 14:10:29 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jorge Contreras <cntreras@gmail.com>
Subject: Re: [Trustees] The Trust Agreement
References: <51FACC4A.4020307@gmail.com>	<E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com> <CAP0PwYZ=T541VbjvFJnHcqPXXuhjUQVe33hsOrZ-Uer9OED9BQ@mail.gmail.com>
In-Reply-To: <CAP0PwYZ=T541VbjvFJnHcqPXXuhjUQVe33hsOrZ-Uer9OED9BQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Trustees <trustees@ietf.org>, IETF discussion list <ietf@ietf.org>, Chris Griffiths <cgriffiths@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 02:10:36 -0000

Jorge,

Thanks for the careful explanations. My only quibble is whether the phrase
"other than rights in IETF standards-related documents (such as RFCs,
Internet Drafts and the like)" actually excludes the Tao, which is not
a standards document, but is very relevant to the standards process
and was an RFC in earlier forms. The web page version is clearly
a derivative work of the preceding RFC. However, I can see this being a
problem some time in the future, even if the Tao squeezed past.

For issues #1 and #3, I can see the case for a cautious procedure
for exceptions to the current restrictions. Clearly the Trust shouldn't
have blanket permission to abandon or dispose of assets (except if the
IETF itself winds up, which I believe is already covered).

As for the physical property issue #2 I can see that there's an
inconsistency but (IMHO) we need to be sure that any change is fully
consistent with BCP 101. To be specific, RFC 4371 says:

   A Trust ("the IETF Trust") has been formed for the purpose of
   acquiring, holding, maintaining, and licensing certain existing and
   future intellectual property and other property used in connection
   with the administration of the IETF.

If we are picky, we'd need to slightly modfiy that sentence if
the Trust has the right to abandon or dispose of assets.

Regards
   Brian

On 03/08/2013 23:50, Jorge Contreras wrote:
> Please see below for some specific responses to Brian's concerns.
> 
> 
> On Sat, Aug 3, 2013 at 1:49 AM, Chris Griffiths <cgriffiths@gmail.com>wrote:
> 
>> On Aug 1, 2013, at 10:59 PM, Brian E Carpenter <
>> brian.e.carpenter@gmail.com> wrote:
>>
>> Hi Brian,
>>
>>> Re the Trust's plenary slides (I was not in Berlin):
>>>
>>> I have an allergy to modifying the Trust Agreement unless there's an
>>> overwhelming reason to do so. It was a very hard-won piece of text.
>> I recognize that this was a very hard-won piece of text and agree we
>> should put a much higher threshold in order to update it.  Based on review
>> of some recent items with legal counsel, we were advised that there were
>> some sections that would need to be updated in order to deal with some
>> recent requests and we felt we would ask the community for feedback if we
>> had enough justification to make changes.
>>
> 
> Indeed, I was also part of that original negotiating team in 2005 and have
> recently spent a great deal of time reviewing the records of that
> negotiation.
> 
> 
>>>> Issue #1
>>>> We have recently been asked permission to
>>>> republish the TAO with a creative commons
>>>> license, but unfortunately the current trust
>>>> agreement does not give the trustees the
>>>> rights to do this
>>> It doesn't? You have the right to license "existing and future
>>> intellectual property" according to clause 2.1 of the Trust Agreement.
>>> Is there some particular property of the CC license that causes a
>>> problem?
> 
> Brian - the restriction is contained in Section 9.5 which, as you may
> recall, was added quite late in the negotiation.  It reads as follows:
> 
> 9.5 Licenses. The Trust (acting through the Trustees) shall have the right
> to grant licenses
> 
> for the use of the Trust Assets on such terms, subject to Section 7.1, as
> the Trustees deem
> 
> appropriate; provided, however, that the Trust shall not grant any license
> that would be
> 
> deemed a transfer of ownership or abandonment of any Trust Assets under
> applicable law.
> 
> Specifically, any license granted by the Trust for the use of the Trust
> Assets consisting ofiPR
> 
> other than rights in IETF standards-related documents (such as RFCs,
> Internet Drafts and the
> 
> like) that have been acquired by the Trust through non-exclusive licenses
> granted by their
> 
> contributors pursuant to the IETF community-approved procedures currently
> set forth in RFC
> 
> 3978, and any community-approved updates and revisions thereto, shall
> include provisions
> 
> stating that (a) the licensee agrees to grant and assign to the Trust all
> right, title, and interest it
> 
> may have or claim in any derivative works of licensee that are based on or
> incorporate the
> 
> IPR, and (b) the licensee's use of the IPR and any goodwill associated
> therewith shall inure to
> 
> the benefit of the Trust.
> 
> The last sentence of this clause makes the Trust is quite limited in its
> ability to grant licenses to IPR other than standards-related documents.
>  That is, it cannot grant licenses to non-standards IPR unless the
> requirements of sub-clauses (a) and (b) are met.  If you recall, the
> original negotiating position of CNRI was that the Trust have NO right
> whatsoever to grant licenses to non-standards IPR.  We requested the
> exceptions in clauses (a) and (b) to address planned tools development by
> paid and volunteer contractors.  Those exceptions were negotiated and
> allowed, and now the only way that the Trust can grant licenses to
> non-standards IPR is if the licensee agrees to grant the Trust ownership of
> any derivative works of the IPR.  Such a requirement is normal and
> appropriate when dealing with contractor-developed tools and other
> software.  However, it does NOT work in the case of something like the Tao,
> which is non-standards track, but not a commissioned software tool.  In
> particular, the requirement that derivative works be assigned to the Trust
> is not consistent with the CC-BY license that the Tao team has requested.
>  Thus, in order to allow this and similar requests, which the Trustees feel
> is in the interest of the IETF community, a relaxation of the restrictions
> in Section 9.5 has been suggested.
> 
> 
>>>> Issue #2
>>>> We cannot currently accept physical assets
>>>> like hardware donations into the trust
>>>> Once accepted into the trust, we would be unable
>>>> to dispose of these items in the future if they are
>>>> identified as no longer being needed
>>> It was definitely intended that the Trust would only handle
>>> intellectual property, and that ISOC on behalf of IASA would handle
>>> money and material property. Why change this?
>>>
>>> (I'm not quite sure why the Trust Agreement included the words
>>> "and other property" in the first place. It was there from a very
>>> early draft and was never discussed, as far as I can tell from my
>>> 2005 email archive.)
> 
> As you point out, the Trust does have the ability to accept property other
> than IPR.  This point is not being debated.  You may recall that CNRI
> wanted the Trust to be able to raise funds to support itself, and to accept
> monetary donations.  That is not a path that the Trust has gone down, but
> in 2005 it was unclear what the eventual operating mode would be.
> 
> 
>>>> Issue #3
>>>> Once a domain name or trademark is
>>>> registered by the trust, it cannot be
>>>> abandoned even if it is no longer needed
>>>> We must maintain these in perpetuity
>>> IANAL, but it isn't clear to me that clause 9.4 forces you to do this.
>>> It requires you to "take reasonable steps" and to file applications "as
>>> the Trustees deem necessary in order to maintain and protect the Trust
>>> Assets." If you decide (and minute) that it isn't reasonable or necessary
>>> to maintain veryolddomainname.org, where's the crime?
> 
> Brian - the relevant restriction in contained in Section 7.1(a):  "the
> Trustees shall not, and shall not have the right or power to, (i)
> exchange, distribute,
> assign, sell, transfer, renounce, or convey the Trust Assets, (ii)
> terminate the Trust Assets' registration,"
> 
> These restrictions, intended to prevent the Trustees from improperly
> dissipating the Trust's assets, now prevent the Trust from engaging in
> transactions that would help to conserve its funds (provided by ISOC) and
> the community overall.   As noted before, there are trademark registrations
> being maintained that are no longer necessary (i.e., the IETF SECRETARIAT
> mark, which is duplicative of, and a subset of, the broader IETF mark).
>  These marks cost money to maintain, both in terms of official maintenance
> fees and attorney fees (not paid to me, by the way!)  However, because
> under 7.1.a.ii the Trust can't terminate the registration of any Trust
> Assets, we're stuck with these unnecessary registrations.
> 
> The same applies to physical assets:  historical documents that could be
> donated to a museum, networking equipment that a company wants to donate
> and have the Trust re-donate to worthy causes.  None of these are possible
> because the Trust can't "sell, transfer, renounce or convey the Trust
> Assets".
> 

From ynir@checkpoint.com  Sat Aug  3 19:23:50 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AABB621F859B for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 19:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.492
X-Spam-Level: 
X-Spam-Status: No, score=-10.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 nHFruvAp1Ave for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 19:23:39 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E69AB21F9A10 for <ietf@ietf.org>; Sat,  3 Aug 2013 19:23:38 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r742NWfC013758; Sun, 4 Aug 2013 05:23:32 +0300
X-CheckPoint: {51FDBB24-14-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Sun, 4 Aug 2013 05:23:31 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Olle E. Johansson" <oej@edvina.net>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
Thread-Topic: Anonymity versus Pseudonymity (was Re: [87attendees] procedural	question with remote participation)
Thread-Index: AQHOj3Rq+0K7hAuW1EiJ7x1NQLsIuJmBohWAgAE334CAAUgOAA==
Date: Sun, 4 Aug 2013 02:23:31 +0000
Message-ID: <7A4F637F-10A7-4709-B186-B6D7E0DC6272@checkpoint.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com> <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net>
In-Reply-To: <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.73]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1181bead1971f1ab67c9031eb46625d95a730c0965
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B1071CB9A501FA43B8406659F55FD61A@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 02:23:50 -0000

On Aug 3, 2013, at 9:49 AM, Olle E. Johansson <oej@edvina.net> wrote:

>=20
> 2 aug 2013 kl. 14:13 skrev Scott Brim <scott.brim@gmail.com>:
>=20
>> I'm completely against participating anonymously because of IPR issues.
>> I'm mostly against pseudonymous participation for the same reason.  I
>> need to be able to know who I'm dealing with, in order to know if there
>> are IPR issues that should be brought up.
>=20
> THat's exactly the problem. Unfortunately the world requires the IETF to
> manage IPR. There's a reason why we need to be strict with the note well.
> Anonymous remote *PARTICIPATION* breaks the requirements of the
> note well acceptance in my view.=20

Hi Olle

The participation in the IETF is already pseudonymous. I have a driver's li=
cense, a passport, and a national ID card, all proving that my name is inde=
ed Yoav Nir. But I have never been asked to present any of them at the IETF=
. I claim to work for Check Point, and my email address tends to suggest it=
, but a lot of participants use gmail addresses.

I had participated in IETF mailing lists for 3 years before ever attending =
a meeting, and I got RFC 4478 published before attending one. At that point=
, none of the IETF regulars had ever seen me - I was just a claimed name on=
 the mailing list and on the draft.

As I don't have to prove an identity when registering for meetings, if that=
 had been a ruse, I could continue running with it to this day, although by=
 now there are two participants who can link the IETF participant with the =
name I use at work. BTW: nobody's stopping anybody from creating a new gmai=
l account under the name "Yoav Nir", registering to IETF mailing lists, and=
 posting in my name. Unless I notice it and cry foul, nobody would be the w=
iser.

Yoav


From barryleiba@gmail.com  Sat Aug  3 21:55:01 2013
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 A016C21F9CF8 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 21:55:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.972
X-Spam-Level: 
X-Spam-Status: No, score=-101.972 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vib4wf+SddUg for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 21:55:01 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 36E4F21F9CEA for <ietf@ietf.org>; Sat,  3 Aug 2013 21:55:01 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id c11so1114613qcv.27 for <ietf@ietf.org>; Sat, 03 Aug 2013 21:55:00 -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=o4trMMxg7LtiiE1CwsXyEIpFI+YrzQ4azjeQAZiIx4E=; b=jNxkPRaccgmOY7lC/SZKGM5kWj/+MUnheVGBtvfGh8t9Fa9TOtRyI5dL70WiaAKvth DI8AKjDEU7jkIZoiFaedRAswQF2e8Pi+zE8knfnf2iXWz32zDPC0uwFgUXGfDE+rbzu/ W7p7tAregffdHKbuyIgjBlYjcLQ5/yhOjp3kdehvriN9hZ4w9G0oMZyC8plITFiysbhq gE2ShMHfonNKw/xuBbP/qYEILHgpaoeBhLBt/JKBFKNhuNV/U2+DUljTqZVruapILS/g ENaGc1sPMuEOl+vTf+KCPuBAQ6RdN03HkO6LhSI5o83QOohaPzv6gl46YVjYqpZ1NnoI G4RA==
MIME-Version: 1.0
X-Received: by 10.224.51.12 with SMTP id b12mr20992078qag.53.1375592100707; Sat, 03 Aug 2013 21:55:00 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.59.211 with HTTP; Sat, 3 Aug 2013 21:55:00 -0700 (PDT)
In-Reply-To: <CAPv4CP8b6u_6c+vVz9fmmNQJJPF9_j+yH249_fXKF+cERuZwxQ@mail.gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com> <6.2.5.6.2.20130803084319.0c7289b8@resistor.net> <CAC4RtVDo6RhE-i3ipK8YjA6S5+KBQ=iP66opbFS7FEMeKiXoXA@mail.gmail.com> <CAPv4CP8b6u_6c+vVz9fmmNQJJPF9_j+yH249_fXKF+cERuZwxQ@mail.gmail.com>
Date: Sun, 4 Aug 2013 06:55:00 +0200
X-Google-Sender-Auth: ewBGjQPbJhehq2Co_0EPqXlbhak
Message-ID: <CALaySJJ1FjKMCgOPv567RSMSnkdWDFajt_RMRKnUbKkeA7ePeQ@mail.gmail.com>
Subject: Re: 6tsch BoF
From: Barry Leiba <barryleiba@computer.org>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, Andy Bierman <andy@yumaworks.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, 04 Aug 2013 04:55:01 -0000

> What did you think of Pete Resnick's draft about hums.

I thought well of it; I still do.  When Pete planned to write it, I
offered to co-author it.  But he said that once he got started, it all
just flowed out, and he wanted to present it as just his craziness, at
least at first.

It's not about hums, in particular, but about rough consensus, in
general, however it's reached.  The main point where Pete and I
disagree is whether raised hands are an appropriate replacement for
humming when you're "getting a sense of the room" -- I like hands, he
doesn't.  But we're completely in agreement about what to do with the
data.

Barry

From l.wood@surrey.ac.uk  Sat Aug  3 22:34:17 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B645721F9930 for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 22:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.848
X-Spam-Level: 
X-Spam-Status: No, score=-4.848 tagged_above=-999 required=5 tests=[AWL=1.750,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aVFYYx66dANk for <ietf@ietfa.amsl.com>; Sat,  3 Aug 2013 22:34:11 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.118]) by ietfa.amsl.com (Postfix) with ESMTP id F2F1321F962D for <ietf@ietf.org>; Sat,  3 Aug 2013 22:34:08 -0700 (PDT)
Received: from [193.109.255.147:32643] by server-14.bemta-14.messagelabs.com id A3/DC-23280-FC7EDF15; Sun, 04 Aug 2013 05:34:07 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-72.messagelabs.com!1375594447!9841057!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5629 invoked from network); 4 Aug 2013 05:34:07 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-8.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 4 Aug 2013 05:34:07 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sun, 4 Aug 2013 06:34:06 +0100
From: <l.wood@surrey.ac.uk>
To: <barryleiba@computer.org>, <scott.brim@gmail.com>
Date: Sun, 4 Aug 2013 06:32:49 +0100
Subject: RE: 6tsch BoF
Thread-Topic: 6tsch BoF
Thread-Index: Ac6Qzuc+1nfYQT57SKGqm7kbwLuSagABSeL4
Message-ID: <290E20B455C66743BE178C5C84F1240822406074FB@EXMB01CMS.surrey.ac.uk>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com> <6.2.5.6.2.20130803084319.0c7289b8@resistor.net> <CAC4RtVDo6RhE-i3ipK8YjA6S5+KBQ=iP66opbFS7FEMeKiXoXA@mail.gmail.com> <CAPv4CP8b6u_6c+vVz9fmmNQJJPF9_j+yH249_fXKF+cERuZwxQ@mail.gmail.com>, <CALaySJJ1FjKMCgOPv567RSMSnkdWDFajt_RMRKnUbKkeA7ePeQ@mail.gmail.com>
In-Reply-To: <CALaySJJ1FjKMCgOPv567RSMSnkdWDFajt_RMRKnUbKkeA7ePeQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: sm@resistor.net, andy@yumaworks.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 05:34:17 -0000

Okay,

http://tools.ietf.org/id/draft-resnick-on-consensus-00.txt

can there be anything to discuss on not having consensus, developing two co=
mpeting solutions in the same WG, and then having to downselect to one?

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Barry Leib=
a [barryleiba@computer.org]
Sent: 04 August 2013 05:55
To: Scott Brim
Cc: SM; Andy Bierman; IETF discussion list
Subject: Re: 6tsch BoF

> What did you think of Pete Resnick's draft about hums.

I thought well of it; I still do.  When Pete planned to write it, I
offered to co-author it.  But he said that once he got started, it all
just flowed out, and he wanted to present it as just his craziness, at
least at first.

It's not about hums, in particular, but about rough consensus, in
general, however it's reached.  The main point where Pete and I
disagree is whether raised hands are an appropriate replacement for
humming when you're "getting a sense of the room" -- I like hands, he
doesn't.  But we're completely in agreement about what to do with the
data.

Barry

From rogerj@gmail.com  Sun Aug  4 01:31:05 2013
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400FF21F97C7 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 01:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id govNRLg6cl0w for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 01:31:04 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 7571721F9ADA for <ietf@ietf.org>; Sun,  4 Aug 2013 01:31:02 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id f14so623129wiw.13 for <ietf@ietf.org>; Sun, 04 Aug 2013 01:31: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 :content-type; bh=9qUWD//nywO8q/ZMar/U2la0U1pPUiqP9PFmu4BJLFE=; b=D9ILLafg+cf0rnXunDuroUizE9d1SnX/j2bV5bi3/qQ1+dEOu2hdQnDKgw91kS1H24 dUYSjAtPFYHNr92lP5/EaDZDGTKOwBfX4WTAI2J6vLOlAdGSAKoINdPxTMwBG/Gy8gEf qS5jqenNfqMh32RjER6rHyEviKMgKWKMDGDA2geXnSr0KgLoV0tzHMhGoRnuufGhs+28 rnRfD8RKb30paDgfagHfUYlf6IAzp3FRgm5mDZUFAihgYgQMM0zzLY50xhsZm2W4+Ad4 otqf8Mnt2z52mGYW9wAYI+gXUkIoXz6KoMLWquR595yyn7a7Aj0chhXfBd6h02eGeLAI okPw==
MIME-Version: 1.0
X-Received: by 10.180.8.229 with SMTP id u5mr760951wia.25.1375605061615; Sun, 04 Aug 2013 01:31:01 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sun, 4 Aug 2013 01:31:01 -0700 (PDT)
Received: by 10.216.213.72 with HTTP; Sun, 4 Aug 2013 01:31:01 -0700 (PDT)
In-Reply-To: <586E502A-0083-4C3D-9515-C9B3245BC6E4@cisco.com>
References: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com> <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net> <586E502A-0083-4C3D-9515-C9B3245BC6E4@cisco.com>
Date: Sun, 4 Aug 2013 10:31:01 +0200
Message-ID: <CAKFn1SEMg=nJ90iJp9cTUVAn1jxQp3oX+yqG30FY9vbo2tRbuQ@mail.gmail.com>
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: Ole Jacobsen <ole@cisco.com>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044289ea0c874204e31b0341
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 08:31:05 -0000

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

On 3 Aug 2013 11:14, "Ole Jacobsen (ole)" <ole@cisco.com> wrote:
>
> It was never a distraction until AB started complaining about it. Been
serving a useful purpose for many, many years. Procmail is your friend.
>

+1 for that

--- Roger ---
> Ole J. Jacobsen
> Editor & Publisher
> http://cisco.com/ipj
>
> Sent from my iPhone
>
> On Aug 3, 2013, at 9:12, "Heasley" <heas@shrubbery.net> wrote:
>
> > Am Aug 3, 2013 um 9:05 schrieb Abdussalam Baryun <
abdussalambaryun@gmail.com>:
> >
> >> On 8/3/13, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:
> >>> On 3 aug 2013, at 08:46, Abdussalam Baryun <abdussalambaryun@gmail.co=
m
>
> >>> wrote:
> >>>
> >>>> I prefer if you post at end of Friday (as in the end of working days
of 5 in each week).
> >>
> >>>> However, in my comment below I
> >>>> will follow the week as done in world calender, start from Sunday
> >>>> (mornings) and ends on Saturday (nights).
> >>>
> >>> The day a week starts, and what days are working days in a week,
differs
> >>> between cultures. Many have Sunday-Thursday as working days. Many hav=
e
> >>> Monday as the first day of the week.
> >>
> >> I suggested to Thomas to submit report in end of Friday (read what i
> >
> > I suggest eliminating the report. As it doesn't measure content
quality, one's contribution can't be measured by the email they produce.
So, it is only a guage of  the distraction they produce. The report itself
is a distraction.

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

<p dir=3D"ltr"><br>
On 3 Aug 2013 11:14, &quot;Ole Jacobsen (ole)&quot; &lt;<a href=3D"mailto:o=
le@cisco.com">ole@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; It was never a distraction until AB started complaining about it. Been=
 serving a useful purpose for many, many years. Procmail is your friend.<br=
>
&gt;</p>
<p dir=3D"ltr">+1 for that<br></p>
<p dir=3D"ltr">--- Roger ---<br>
&gt; Ole J. Jacobsen<br>
&gt; Editor &amp; Publisher<br>
&gt; <a href=3D"http://cisco.com/ipj">http://cisco.com/ipj</a><br>
&gt;<br>
&gt; Sent from my iPhone<br>
&gt;<br>
&gt; On Aug 3, 2013, at 9:12, &quot;Heasley&quot; &lt;<a href=3D"mailto:hea=
s@shrubbery.net">heas@shrubbery.net</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Am Aug 3, 2013 um 9:05 schrieb Abdussalam Baryun &lt;<a href=3D"m=
ailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt;:<br>
&gt; &gt;<br>
&gt; &gt;&gt; On 8/3/13, Patrik F=E4ltstr=F6m &lt;<a href=3D"mailto:paf@fro=
bbit.se">paf@frobbit.se</a>&gt; wrote:<br>
&gt; &gt;&gt;&gt; On 3 aug 2013, at 08:46, Abdussalam Baryun &lt;<a href=3D=
"mailto:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt;<br>
&gt; &gt;&gt;&gt; wrote:<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; I prefer if you post at end of Friday (as in the end =
of working days of 5 in each week).<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt; However, in my comment below I<br>
&gt; &gt;&gt;&gt;&gt; will follow the week as done in world calender, start=
 from Sunday<br>
&gt; &gt;&gt;&gt;&gt; (mornings) and ends on Saturday (nights).<br>
&gt; &gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt; The day a week starts, and what days are working days in =
a week, differs<br>
&gt; &gt;&gt;&gt; between cultures. Many have Sunday-Thursday as working da=
ys. Many have<br>
&gt; &gt;&gt;&gt; Monday as the first day of the week.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; I suggested to Thomas to submit report in end of Friday (read=
 what i<br>
&gt; &gt;<br>
&gt; &gt; I suggest eliminating the report. As it doesn&#39;t measure conte=
nt quality, one&#39;s contribution can&#39;t be measured by the email they =
produce. So, it is only a guage of =A0the distraction they produce. The rep=
ort itself is a distraction.<br>

</p>

--f46d044289ea0c874204e31b0341--

From loa@pi.nu  Sun Aug  4 02:08:15 2013
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6C7121F9AF0 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 02:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N6pIwAJMdt7a for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 02:08:02 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id D7ADE21F9AED for <ietf@ietf.org>; Sun,  4 Aug 2013 02:08:01 -0700 (PDT)
Received: from [192.168.1.133] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 96E961800272 for <ietf@ietf.org>; Sun,  4 Aug 2013 11:08:00 +0200 (CEST)
Message-ID: <51FE19F6.6050407@pi.nu>
Date: Sun, 04 Aug 2013 11:08:06 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
References: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com> <EC795E4E-4D4D-4CE2-B7C7-64F223FD4B69@shrubbery.net> <586E502A-0083-4C3D-9515-C9B3245BC6E4@cisco.com> <CAKFn1SEMg=nJ90iJp9cTUVAn1jxQp3oX+yqG30FY9vbo2tRbuQ@mail.gmail.com>
In-Reply-To: <CAKFn1SEMg=nJ90iJp9cTUVAn1jxQp3oX+yqG30FY9vbo2tRbuQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 09:08:15 -0000

All,

If there is a serious drive to discontinue the weekly posting
summary - I strongly object.

I don't think its main benefit is be to stop excessive or of topic
posting. I'm not saying that list managers and list owners should look
at that aspect.

At least for me it serves as a safety net where I can look if I missed
anything and need to go back and look.

/Loa

On 2013-08-04 10:31, Roger Jørgensen wrote:
>
> On 3 Aug 2013 11:14, "Ole Jacobsen (ole)" <ole@cisco.com
> <mailto:ole@cisco.com>> wrote:
>  >
>  > It was never a distraction until AB started complaining about it.
> Been serving a useful purpose for many, many years. Procmail is your friend.
>  >
>
> +1 for that
>
> --- Roger ---
>  > Ole J. Jacobsen
>  > Editor & Publisher
>  > http://cisco.com/ipj
>  >
>  > Sent from my iPhone
>  >
>  > On Aug 3, 2013, at 9:12, "Heasley" <heas@shrubbery.net
> <mailto:heas@shrubbery.net>> wrote:
>  >
>  > > Am Aug 3, 2013 um 9:05 schrieb Abdussalam Baryun
> <abdussalambaryun@gmail.com <mailto:abdussalambaryun@gmail.com>>:
>  > >
>  > >> On 8/3/13, Patrik Fältström <paf@frobbit.se
> <mailto:paf@frobbit.se>> wrote:
>  > >>> On 3 aug 2013, at 08:46, Abdussalam Baryun
> <abdussalambaryun@gmail.com <mailto:abdussalambaryun@gmail.com>>
>  > >>> wrote:
>  > >>>
>  > >>>> I prefer if you post at end of Friday (as in the end of working
> days of 5 in each week).
>  > >>
>  > >>>> However, in my comment below I
>  > >>>> will follow the week as done in world calender, start from Sunday
>  > >>>> (mornings) and ends on Saturday (nights).
>  > >>>
>  > >>> The day a week starts, and what days are working days in a week,
> differs
>  > >>> between cultures. Many have Sunday-Thursday as working days. Many
> have
>  > >>> Monday as the first day of the week.
>  > >>
>  > >> I suggested to Thomas to submit report in end of Friday (read what i
>  > >
>  > > I suggest eliminating the report. As it doesn't measure content
> quality, one's contribution can't be measured by the email they produce.
> So, it is only a guage of  the distraction they produce. The report
> itself is a distraction.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From mcr@sandelman.ca  Sun Aug  4 04:28:36 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3003221F9A29 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 04:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEMkiWdI935y for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 04:28:31 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 4BCAB21F9A23 for <ietf@ietf.org>; Sun,  4 Aug 2013 04:28:29 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id DBB632016E; Sun,  4 Aug 2013 08:34:45 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id D6D0163A7C; Sun,  4 Aug 2013 07:27:00 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C2F3A636AD; Sun,  4 Aug 2013 07:27:00 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org, John C Klensin <john-ietf@jck.com>
Subject: Re: procedural question with remote participation
In-Reply-To: <ECF4A733EFD13FA1753C063B@[192.168.1.128]>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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, 04 Aug 2013 07:27:00 -0400
Message-ID: <32634.1375615620@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Dan York <york@isoc.org>, "Olle E. Johansson" <oej@edvina.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, 04 Aug 2013 11:28:36 -0000

--=-=-=


I attended meetings 36 through 62 in-person, missing about 1 in 4. I've never
attended a meeting in asia-pacific, as about half were paid out of my own
pocket,   That was in the days of multicast, and I never got an mbone tunnel
working, although Joe Abley and I once *saw* them in tcpdump go past us on
the ethernet at ISC, but not get relayed through our tunnels.
Between 63 and 80, I managed to attend 1 in 5, and this one is the first I've
missed since 80.  I missed it because, my WG didn't need to meet, I had no
money, and it abuts an important long weekend. (I got to walk out in 3min)
I have generally good experiences with our remote participation.
Some problems recently:
1) the audio feed started at exactly 9:00 on Monday  A problem if you need
   to check your equipment. I also interrupted at exactly the start time
   of the session, and it took me 20-30s to realize it, and up-arrow-return.

2) Slide decks were late.  PPT(x) files are annoying and inconsiderate.
   Consolidated slide decks are wonderful, even if the agenda order is
   changed.

3) audio delay makes hums via jabber meaningless.

John C Klensin <john-ietf@jck.com> wrote:
    > We regularize remote participation [1] a bit by doing the
    > following.  At some level, if remote participants expect to be
    > treated as serious members of the community, they (we) can
    > reasonably be expected to behave that way.

    > * A mechanism for remote participants should be set up
    > and remote participants should be to register.  The

+1. And I would pay a fee.

    > * Remote participants should have as much access to mic
    > lines and the ability to participate in discussions as
    > those who are present in the room.   That includes

Yes... but I think it might be worth recognizing that in badly run meetings,
access to the mic is a problem to those in the meeting too!  Multiple roaming
wireless mics, and mic-control from the chair would help here.
I.e. let's use the technology for mic-line-up for everyone, local and
remote.

    > * It is really, really, important that those speaking,
    > even if they happen to be sitting at the chair's table,
    > clearly and carefully identify themselves.

+1

    > * On several occasions this week, slides were uploaded
    > on a just-in-time basis (or an hour or so after that).

Agreed.  I'd like to have this as a very clear IETF-wide policy.
No slides 1 week before hand, no time allocation.

    > Or we can decide that real participation in the IETF requires
    > that people be in the room, that remote participants are
    > involved on a "what you get is what you get" basis, and we stop
    > pretending otherwise.  For many reasons, I'm not enthused about
    > that idea, but the things that I, and others, are suggesting and
    > asking for will cost money and require some changes in the
    > ordinary way of doing things and it is only fair to mention the
    > alternative and suggest that it be explicitly considered.


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





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

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

iQCVAwUBUf46gIqHRg3pndX9AQJQSQQAq7FVgEuOfzSwGXXN9bFSnAJPTt86ksCx
7/h+nqL5JhYIH+SXOF3hwNRTlbe/2xIOZkv9nmkMhkAPhHn9ISHTsGyMK3gYYl7U
lqd/FLU1bxk96eeQFQ8sqUSMtQCfanYy2jkSJFXFJSh7yCnZweAHDKt6wWY+8Ch0
820meJqQeps=
=vFxH
-----END PGP SIGNATURE-----
--=-=-=--

From sm@elandsys.com  Sun Aug  4 10:46:58 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EEE21F9C9A for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 10:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXMgaFLwoc+t for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 10:46:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C6A21F9B94 for <ietf@ietf.org>; Sun,  4 Aug 2013 10:46:57 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.222]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r74Hkc8O000952 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Aug 2013 10:46:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375638411; bh=mRq6zx1spxoEPvwXCYIqZRJSWU0sJ+4bzOLnRzFeYbY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0YgZaFi1FowaonEMrobjSti0DNMXWKTIKUe8tCqhLaeYNwpEiszqAVM2W9YwiZ+bS H527Yg2fwD0TEVBHi8lutcDsIv42jqwtnYDweBXtpFFpsbteVfiA4LRktmKfz8kFkd k9DRD5DHEZxUKwfLQvS6yjUd0BzTSDcyTwXCPqy0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1375638411; i=@elandsys.com; bh=mRq6zx1spxoEPvwXCYIqZRJSWU0sJ+4bzOLnRzFeYbY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oXh2XqJC+dSyCqiQptZu0vyJIiBcAIKwnMWnXTog3ThTNoDa3VM8JfHh7DYBf9xLY rzWLNV/2ruvwFDS+tOh0XJTdupRhCzkqp5PdgI26lC6RbkoamNBRlbgDrnkztLDtfQ ageIAP1IqIcGPNK7nNBsHHOUyY7Pk5HizFPuSmuc=
Message-Id: <6.2.5.6.2.20130804091259.0bece8b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 04 Aug 2013 10:45:02 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: The Friday Report
In-Reply-To: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.g mail.com>
References: <CADnDZ88JyOn+XNVmpXXaK7uLbS0dnV8yx203N9X8vcqL0RKvgQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 17:46:58 -0000

Hi Abdussalam,

The IETF Chair used "AB" as your name in his report during the 
plenary.  I assume that it is okay for me to call you 
"Abdussalam".  I should have used "Mr Baryun" as that is how it is 
done in some cultures.

Somebody (outside the IETF) wrote that, in general, those living in 
richer countries appear to treat one another less kindly than their 
counterparts in poorer nations.  In my personal opinion bullying is 
not okay.  If you are of the opinion that you are being bullied 
please feel free to email me if you would like to talk to me about it.

Regards,
S. Moonesamy


From Ted.Lemon@nominum.com  Sun Aug  4 11:09:11 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9038021F992B for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 11:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.557
X-Spam-Level: 
X-Spam-Status: No, score=-106.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 aGRbo5OqwoBR for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 11:09:05 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id D82DF21F9929 for <ietf@ietf.org>; Sun,  4 Aug 2013 11:09:04 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUf6YwGuF4rYdtu7geIYziXD1fxTBoVdG@postini.com; Sun, 04 Aug 2013 11:09:04 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7107F1B8225 for <ietf@ietf.org>; Sun,  4 Aug 2013 11:09:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 673E4190060; Sun,  4 Aug 2013 11:09:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 4 Aug 2013 11:09:04 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
Thread-Topic: Anonymity versus Pseudonymity (was Re: [87attendees] procedural	question with remote participation)
Thread-Index: AQHOj3RnTZkgTjQHpEOGVB7yIIDnW5mCSbiAgAE334CAAUgSgIABCC2A
Date: Sun, 4 Aug 2013 18:09:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775243147@mbx-01.win.nominum.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com> <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net> <7A4F637F-10A7-4709-B186-B6D7E0DC6272@checkpoint.com>
In-Reply-To: <7A4F637F-10A7-4709-B186-B6D7E0DC6272@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <197C77040416E345AA75554669E9DE4A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Olle E. Johansson" <oej@edvina.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, 04 Aug 2013 18:09:11 -0000

On Aug 3, 2013, at 10:23 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> The participation in the IETF is already pseudonymous. I have a driver's =
license, a passport, and a national ID card, all proving that my name is in=
deed Yoav Nir. But I have never been asked to present any of them at the IE=
TF. I claim to work for Check Point, and my email address tends to suggest =
it, but a lot of participants use gmail addresses.

So, you pay cash when you register?

It would probably be difficult to keep your identity secret if there were a=
 discovery process during a patent trial.  You would also have to lie on th=
e stand, and risk severe repercussions if your lie were revealed.

So yes, this is a problem, but it's not clear to me that it's a serious pro=
blem.


From john-ietf@jck.com  Sun Aug  4 11:20:25 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BACF321F8EB5 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 11:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oANa6g2Jp8Np for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 11:20:20 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCC021F9D95 for <ietf@ietf.org>; Sun,  4 Aug 2013 11:20:05 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V62uR-00037g-6Y; Sun, 04 Aug 2013 14:20:03 -0400
X-Vipre-Scanned: 03D8CDAE002C3103D8CEFB-TDI
Date: Sun, 04 Aug 2013 14:20:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael Richardson <mcr@sandelman.ca>, ietf@ietf.org
Subject: Re: procedural question with remote participation
Message-ID: <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
In-Reply-To: <32634.1375615620@sandelman.ca>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Dan York <york@isoc.org>, "Olle E. Johansson" <oej@edvina.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, 04 Aug 2013 18:20:25 -0000

--On Sunday, August 04, 2013 07:27 -0400 Michael Richardson
<mcr@sandelman.ca> wrote:

>...
>     > * On several occasions this week, slides were uploaded
>     > on a just-in-time basis (or an hour or so after that).
> 
> Agreed.  I'd like to have this as a very clear IETF-wide
> policy. No slides 1 week before hand, no time allocation.

I had two different WG chairs (from two different WGs) tell me
this week that their WGs really needed the presentations and
discussion to move forward and they therefore couldn't do
anything other than let things progress when they didn't get the
slides and get them posted before the session started.  This is
part of what I mean by the community not [yet] taking remote
participation seriously.  If having the slides in advance is as
important to remote participants as Michael and I believe, then
the community has to decide that late slides are simply
unacceptable behavior except in the most unusual circumstances,
with "unacceptable" being viewed at a level that justifies
finding replacements for document authors and even WG chairs.

I also note that the 1 week cutoff that Michael suggests would,
in most cases, eliminate "had no choice without impeding WG
progress" as an excuse.  A week in advance of the meeting, there
should be time, if necessary to find someone else to organize
the presentation or discussion (and to prepare and post late
slides that are still posted before the meeting if needed).  If
it is necessary to go ahead without the slides, it is time to
get a warning to that effect and maybe an outline of the issues
to be discussed into the agenda.    If the WG's position is that
slides 12 or 24 hours before the WG's session are acceptable,
then the odds are high that one glitch or another will trigger a
"well, there are no slides posted but they are available in the
room and the discussion is important" decision.

Again, I think the real question is whether we, as a community,
are serious about effective remote participation; serious enough
to back a WG chair who calls off a presentation or replaces a
document author, or an AD who replaces a WG chair, for not
getting with the program.

best,
    john


From Ted.Lemon@nominum.com  Sun Aug  4 11:54:33 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE5521F9E96 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 11:54:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.557
X-Spam-Level: 
X-Spam-Status: No, score=-106.557 tagged_above=-999 required=5 tests=[AWL=0.042, 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 m8Xl1pYPVzA7 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 11:54:22 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7E64321F9223 for <ietf@ietf.org>; Sun,  4 Aug 2013 11:54:21 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUf6jXH8KNZG7KIEshAxfc5lnrKpll/62@postini.com; Sun, 04 Aug 2013 11:54:21 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0C9C81B8293 for <ietf@ietf.org>; Sun,  4 Aug 2013 11:54:20 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E49AF190060; Sun,  4 Aug 2013 11:54:19 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 4 Aug 2013 11:54:20 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: procedural question with remote participation
Thread-Topic: procedural question with remote participation
Thread-Index: AQHOkKDV2CvwGbYE6UKNGm0aB96X6ZmFXykAgABzZgCAAAmTAA==
Date: Sun, 4 Aug 2013 18:54:18 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
In-Reply-To: <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <254261F2AA37904E8DE4ABDFF39BC0B3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Olle E. Johansson" <oej@edvina.net>, Dan York <york@isoc.org>, Michael Richardson <mcr@sandelman.ca>, "<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, 04 Aug 2013 18:54:34 -0000

While I think getting slides in on time is great for a lot of reasons, read=
ing the slides early isn't that important.   What is important is that remo=
te people see the slides at the same time as local people.   For that, it s=
eems to me that Meetecho support does exactly what is needed.   You just fo=
llow the slideshow online, along with the audio.

Of course, in order to have Meetecho support, you need the slides in advanc=
e of the meeting, preferably far enough in advance that it doesn't create a=
 massive hassle for the Meetecho team. But by making Meetecho the place whe=
re the slides are presented, you ensure that everybody is on an equal footi=
ng, without engaging in punitive behavior.

The main reason to want to see the slides in advance is so that the working=
 group chairs can evaluate them to see if they will actually be a good use =
of time.   But that's completely orthogonal to the remote participation iss=
ue.


From ynir@checkpoint.com  Sun Aug  4 12:06:40 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B020421F9957 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 12:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.499
X-Spam-Level: 
X-Spam-Status: No, score=-10.499 tagged_above=-999 required=5 tests=[AWL=0.099, BAD_CREDIT=0.001, 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 OG+DfNuV7Fly for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 12:06:35 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5AFD821F9E1D for <ietf@ietf.org>; Sun,  4 Aug 2013 12:06:32 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r74J6Sjw013013; Sun, 4 Aug 2013 22:06:28 +0300
X-CheckPoint: {51FEA634-D-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Sun, 4 Aug 2013 22:06:27 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
Thread-Topic: Anonymity versus Pseudonymity (was Re: [87attendees] procedural	question with remote participation)
Thread-Index: AQHOj3Rq+0K7hAuW1EiJ7x1NQLsIuJmBohWAgAE334CAAUgOAIABCDGAgAAQB4A=
Date: Sun, 4 Aug 2013 19:06:26 +0000
Message-ID: <FA730ECD-08A5-41F7-945A-2A0EC24B81B1@checkpoint.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com> <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net> <7A4F637F-10A7-4709-B186-B6D7E0DC6272@checkpoint.com> <8D23D4052ABE7A4490E77B1A012B630775243147@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775243147@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.202]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 110f5bbee9add31596e9bff29dca0e756c4730b880
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <53497A81BBD65D459820EF2C5104554C@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Olle E. Johansson" <oej@edvina.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, 04 Aug 2013 19:06:40 -0000

On Aug 4, 2013, at 9:09 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 3, 2013, at 10:23 PM, Yoav Nir <ynir@checkpoint.com> wrote:
>> The participation in the IETF is already pseudonymous. I have a driver's=
 license, a passport, and a national ID card, all proving that my name is i=
ndeed Yoav Nir. But I have never been asked to present any of them at the I=
ETF. I claim to work for Check Point, and my email address tends to suggest=
 it, but a lot of participants use gmail addresses.
>=20
> So, you pay cash when you register?

No, I use a credit card in the name of my company's "head of purchasing", s=
o not in my name.=20

> It would probably be difficult to keep your identity secret if there were=
 a discovery process during a patent trial.  You would also have to lie on =
the stand, and risk severe repercussions if your lie were revealed.

I would never lie at trial. But the name I use at trial doesn't go back to =
the IETF.

> So yes, this is a problem, but it's not clear to me that it's a serious p=
roblem.

I don't think it's a serious problem anyway, but the IETF does not collect =
enough data to "track you down" as a condition for participation. So tracki=
ng you down becomes the lawyer's problem, not something that the IETF can g=
ive away.

Yoav


From Ted.Lemon@nominum.com  Sun Aug  4 12:31:22 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B2B611E80E2 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 12:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.557
X-Spam-Level: 
X-Spam-Status: No, score=-106.557 tagged_above=-999 required=5 tests=[AWL=0.041, BAD_CREDIT=0.001, 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 0MlaukjvOaBO for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 12:31:13 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 26D8011E80D9 for <ietf@ietf.org>; Sun,  4 Aug 2013 12:31:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUf6sAKRD/hXlykWUF2zti3ew7yNeIJSP@postini.com; Sun, 04 Aug 2013 12:31:13 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 12B961B8257 for <ietf@ietf.org>; Sun,  4 Aug 2013 12:31:12 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EA542190060; Sun,  4 Aug 2013 12:31:11 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sun, 4 Aug 2013 12:31:06 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural question with remote participation)
Thread-Topic: Anonymity versus Pseudonymity (was Re: [87attendees] procedural	question with remote participation)
Thread-Index: AQHOj3RnTZkgTjQHpEOGVB7yIIDnW5mCSbiAgAE334CAAUgSgIABCC2AgAAQCQCAAAbjgA==
Date: Sun, 4 Aug 2013 19:31:06 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775243597@mbx-01.win.nominum.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com> <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net> <7A4F637F-10A7-4709-B186-B6D7E0DC6272@checkpoint.com> <8D23D4052ABE7A4490E77B1A012B630775243147@mbx-01.win.nominum.com> <FA730ECD-08A5-41F7-945A-2A0EC24B81B1@checkpoint.com>
In-Reply-To: <FA730ECD-08A5-41F7-945A-2A0EC24B81B1@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8A708E07A521ED4D9051FB8B0E7BF069@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Olle E. Johansson" <oej@edvina.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, 04 Aug 2013 19:31:22 -0000

On Aug 4, 2013, at 3:06 PM, Yoav Nir <ynir@checkpoint.com> wrote:
> No, I use a credit card in the name of my company's "head of purchasing",=
 so not in my name.=20

Why wouldn't that be sufficient to identify you?   Is the head of purchasin=
g going to protect your anonymity?

> I would never lie at trial. But the name I use at trial doesn't go back t=
o the IETF.

If you came to the IETF and were working for company X, registered pseudony=
mously, and didn't disclose IPR belonging to you or company X, and then lat=
er company X sued someone for using their IPR, you and company X would get =
raked over the coals, jointly and severally; the deliberate attempt to dece=
ive would make things worse for you.   And that's the point: to provide you=
 with a strong disincentive to doing such a thing.   So whether the rules p=
revent you from being anonymous, or prevent you from suing, everybody's hap=
py.

(IANAL, so I'm just explaining my understanding of the situation.)



From johnl@iecc.com  Sun Aug  4 12:54:14 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 295B421F9974 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 12:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.583
X-Spam-Level: 
X-Spam-Status: No, score=-106.583 tagged_above=-999 required=5 tests=[AWL=-3.984, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dU64+rNe-jO6 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 12:54: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 BA25221F996A for <ietf@ietf.org>; Sun,  4 Aug 2013 12:54:09 -0700 (PDT)
Received: (qmail 48206 invoked from network); 4 Aug 2013 19:54:05 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Aug 2013 19:54:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51feb15d.xn--30v786c.k1308; i=johnl@user.iecc.com; bh=XIi/6cNWPAalDs2XtA60gsu2L+gJrufentb55xWEfz8=; b=OOx7Y9VkSxDQoaW35aWIWA3ZRF5aS7cq0hn4EZo1qtrO78xBhbyhvvHp3H0tGw0BQGv65h2EiLs5lxQRI8lTbVAbRQvLLs3FUMyR3ePc9GHM1LfIfG3OTgBa3slI4DvdbwJPOft4nHEFfXhtiPBqb2pyOb7pSI4XxXsbjxjRcYuCrNmS3sF8Nxbkx5HadFmPypPyeybxSzw1xZS5wKnb+s8p9sCLJvmcHY4V98wCFuHbFYrzAuW8A32X6Oc6IqU6
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51feb15d.xn--30v786c.k1308; olt=johnl@user.iecc.com; bh=XIi/6cNWPAalDs2XtA60gsu2L+gJrufentb55xWEfz8=; b=gRzzO1cdzKae57kyA/ddaJZPVe+UDinz0oawqGQhZdfDK08pdSTolgGd1v/bslzPeRjFinmOqk2Akqb5wb/x120e5ouxwH2auvhaujOhnA6Pni+PZRoOk16yHjmQzWixOET6F8+YzlSN/cEYAssicmaPv8PSD8pnJKHaHYNm73b6tiaUbDykqfvU6SFQM6QdHXxZf/OogdWvS3VF/NGc/Tmckwu3Edss7LDMnrPsnVvmVlavGkxju3dMSONF0otn
Date: 4 Aug 2013 19:53:42 -0000
Message-ID: <20130804195342.3851.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
In-Reply-To: <51FE19F6.6050407@pi.nu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 19:54:14 -0000

>If there is a serious drive to discontinue the weekly posting
>summary - I strongly object.

As far as I can tell, one person objects, everyone else thinks it's fine.

Seems like rough consensus to me.

R's,
John

From melinda.shore@gmail.com  Sun Aug  4 13:02:25 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED8921E8056 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXcADeQ3T0TW for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:02:25 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id AFEE621E8054 for <ietf@ietf.org>; Sun,  4 Aug 2013 13:02:21 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so2514096pad.0 for <ietf@ietf.org>; Sun, 04 Aug 2013 13:02:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=P79pUG/PdKw/kQUKZP9WeOmH8YEKHjy2OsD87qSnJOI=; b=wZQHAh4lrM3XSQbdY5VXfWGlS99QfcuZ2emoRYRyE9UFc8Ad9DcmXgQtDCfee1lvgI O1Y23vNbTif6k1G2KbgTQUxEp03ONO54qSMdmt701MQ0bDJwlfe+Q3Qn0g4QO1T+qrvw TQ8tO26ZgilrNgR/k3Xcdtuf9O3n0ZNiSuUn5lr+8fq0wcpE8Z32sKI8QdlM9sseEdxI gmO1Yllc4QoAWokE6SycJOKKi5Ymo4O6QdOZ9NkwZB503PtTljhyf0IoyzYIkEGdJeT8 QWEtTLRwPgncuNOg+n8L6VbBU/6Db9sl08dWt+euTHfIxoPWIMDadDQm27+WScu6qLKG nxuw==
X-Received: by 10.66.4.6 with SMTP id g6mr21256365pag.96.1375646538212; Sun, 04 Aug 2013 13:02:18 -0700 (PDT)
Received: from spandex.local (66-230-112-156-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.156]) by mx.google.com with ESMTPSA id aj3sm23592745pad.8.2013.08.04.13.02.16 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 04 Aug 2013 13:02:17 -0700 (PDT)
Message-ID: <51FEB346.7070804@gmail.com>
Date: Sun, 04 Aug 2013 12:02:14 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
References: <20130804195342.3851.qmail@joyce.lan>
In-Reply-To: <20130804195342.3851.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:02:25 -0000

On 8/4/13 11:53 AM, John Levine wrote:
> As far as I can tell, one person objects, everyone else thinks it's fine.

More to the point, the objections that are being raised appear
to be bogus and based in a misunderstanding of how the IETF
operates.

Melinda



From ad707@hermes.cam.ac.uk  Sun Aug  4 13:03:05 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C19221E8082 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:03:05 -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 B5N0W6rfPCcT for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:03:04 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f52]) by ietfa.amsl.com (Postfix) with ESMTP id B1E2821E8085 for <ietf@ietf.org>; Sun,  4 Aug 2013 13:03:04 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:40210) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:ad707) id 1V64W6-0002pq-DC (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Sun, 04 Aug 2013 21:03:02 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V64W6-0002RR-0V (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Sun, 04 Aug 2013 21:03:02 +0100
Received: from [131.111.218.40] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 04 Aug 2013 21:03:01 +0100
Date: 04 Aug 2013 21:03:01 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: johnl@taugh.com
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
Message-ID: <Prayer.1.3.5.1308042103010.3442@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:03:05 -0000

On 04/08/13 20:53, John Levine wrote:
>> If there is a serious drive to discontinue the weekly posting
>> summary - I strongly object.
>
> As far as I can tell, one person objects, everyone else thinks it's fine.
>
> Seems like rough consensus to me.

+1

Aaron

>
> R's,
> John


From tjc@ecs.soton.ac.uk  Sun Aug  4 13:09:42 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABCB11E80E8 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:09:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hQHFmUDWR5am for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:09:39 -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 5207711E80DF for <ietf@ietf.org>; Sun,  4 Aug 2013 13:09:37 -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 r74K9WN5022153; Sun, 4 Aug 2013 21:09:32 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r74K9WN5022153
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1375646972; bh=7yEg+bC25cHu/dI13owhv788Jw8=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=tJr8RmiQYzQRwyh8r3ZRYQ1hDrQDdBwXvREsV5pwMuYgqSyUkNB4IOycWECnUGH4R J+pZifZlYi4mmW98PO6dzA9OmnbXUUquP/tHJ0Us7W0t6aulqzzqDH4yYq4ce8OPzq P0t5D2TKv7PxEp1X5hpwGNra2b1f1csELT7/hU3M=
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 p73L9W0544533840E6 ret-id none; Sun, 04 Aug 2013 21:09:32 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r74K9MV4010133 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 4 Aug 2013 21:09:27 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20130804195342.3851.qmail@joyce.lan>
Date: Sun, 4 Aug 2013 21:09:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|66a5aa4364b66657b503ea97ec67f234p73L9W03tjc|ecs.soton.ac.uk|78B244BA-5C70-42D9-836C-59D9DAFB77AC@ecs.soton.ac.uk>
References: <20130804195342.3851.qmail@joyce.lan> <78B244BA-5C70-42D9-836C-59D9DAFB77AC@ecs.soton.ac.uk>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p73L9W054453384000; tid=p73L9W0544533840E6; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r74K9WN5022153
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:09:42 -0000

On 4 Aug 2013, at 20:53, "John Levine" <johnl@taugh.com> wrote:

>> If there is a serious drive to discontinue the weekly posting
>> summary - I strongly object.
>=20
> As far as I can tell, one person objects, everyone else thinks it's =
fine.
>=20
> Seems like rough consensus to me.

And the code is running=85

Tim


From hadriel.kaplan@oracle.com  Sun Aug  4 13:11:11 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A176821F9E5C for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level: 
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.101,  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 SyLEVAMqUCP2 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:11:05 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 239EB11E80D3 for <ietf@ietf.org>; Sun,  4 Aug 2013 13:11:05 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r74KB0bp018967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Aug 2013 20:11:01 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r74KAxsE007552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Aug 2013 20:10:59 GMT
Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r74KAxps025169; Sun, 4 Aug 2013 20:10:59 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 04 Aug 2013 13:10:58 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
Date: Sun, 4 Aug 2013 16:10:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:11:11 -0000

OK, I'll bite.  Why do you and Michael believe you need to have the =
slides 1 week in advance?

You have the agenda and drafts 2 weeks in advance.  The slides aren't =
normative.  Even when they're not about a draft in particular, the =
slides are not self-standing documents.  They're merely to help with =
discussion.

Not getting the slides at all is a different matter - but 7 days in =
advance is counter-productive.  They should be as up-to-date as =
practical, to take into account mailing list discussions. [or at least =
that's how I justify my same-day, ultra-fresh slides]

If you need to have them on the website 7 days in advance, you really =
need to get a faster Internet connection. ;)

-hadriel


On Aug 4, 2013, at 2:20 PM, John C Klensin <john-ietf@jck.com> wrote:

> --On Sunday, August 04, 2013 07:27 -0400 Michael Richardson
> <mcr@sandelman.ca> wrote:
>=20
>> ...
>>> * On several occasions this week, slides were uploaded
>>> on a just-in-time basis (or an hour or so after that).
>>=20
>> Agreed.  I'd like to have this as a very clear IETF-wide
>> policy. No slides 1 week before hand, no time allocation.
>=20
> I had two different WG chairs (from two different WGs) tell me
> this week that their WGs really needed the presentations and
> discussion to move forward and they therefore couldn't do
> anything other than let things progress when they didn't get the
> slides and get them posted before the session started.  This is
> part of what I mean by the community not [yet] taking remote
> participation seriously.  If having the slides in advance is as
> important to remote participants as Michael and I believe, then
> the community has to decide that late slides are simply
> unacceptable behavior except in the most unusual circumstances,
> with "unacceptable" being viewed at a level that justifies
> finding replacements for document authors and even WG chairs.
>=20
> I also note that the 1 week cutoff that Michael suggests would,
> in most cases, eliminate "had no choice without impeding WG
> progress" as an excuse.  A week in advance of the meeting, there
> should be time, if necessary to find someone else to organize
> the presentation or discussion (and to prepare and post late
> slides that are still posted before the meeting if needed).  If
> it is necessary to go ahead without the slides, it is time to
> get a warning to that effect and maybe an outline of the issues
> to be discussed into the agenda.    If the WG's position is that
> slides 12 or 24 hours before the WG's session are acceptable,
> then the odds are high that one glitch or another will trigger a
> "well, there are no slides posted but they are available in the
> room and the discussion is important" decision.
>=20
> Again, I think the real question is whether we, as a community,
> are serious about effective remote participation; serious enough
> to back a WG chair who calls off a presentation or replaces a
> document author, or an AD who replaces a WG chair, for not
> getting with the program.
>=20
> best,
>    john
>=20


From johnl@iecc.com  Sun Aug  4 13:11:35 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 723BE21F999B for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:11:35 -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=-3.735, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSNZIQt-bBqP for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:11:31 -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 9023D21F9F31 for <ietf@ietf.org>; Sun,  4 Aug 2013 13:11:28 -0700 (PDT)
Received: (qmail 51422 invoked from network); 4 Aug 2013 20:11:28 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 4 Aug 2013 20:11:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=51feb570.xn--3zv.k1308; i=johnl@user.iecc.com; bh=GmKgQe4ojfuB1xNlUShu5y1LKT+uK4z/mYveeI1oHNM=; b=jUkTMIJo+ZNZHAUbRMhB9jV9KQh7bnTJudpzCOFh9d+xlColkukuukL1rSOnY1WC70f9QCUueH5up6jfQAoHCYXgHGiSqTNShKHQ3B7z+cIcN5dwHQYgJWK+vwXxJqG3ZloULjhFG+T7PLg1vuKkRc8oAcJCWhqI7w4PD45SuDUejxEc5ugsuX9kWuMbsXbbw5rUZNJEhxikGhXogl7crMKnlVyvox/ccrNDPRRlgWaJrxnHXCk/c89vGymCeOsY
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=51feb570.xn--3zv.k1308; olt=johnl@user.iecc.com; bh=GmKgQe4ojfuB1xNlUShu5y1LKT+uK4z/mYveeI1oHNM=; b=ZJ0ouANb78LqzSRgmV00NVQWc69hkL7m0n+11v2soLpkaQoV9IoJYDchtKqO9S3R/Dsu7DHIc3QTMeP/8bCggIaJX6BlqqlMoh+HGApwUEfDHFD7BDNtzithxMxH68SLlOFCbZXkW7bmVBKHgHZqoheFKg6sm38rjRdeK0Ye5CHzDg3l6TnTiwDt6es4cg5Jv1bNCgnrmXGObyM6GLzORFL/Clnn6NBnAylAp+N/EtRG9x6UT3R85R0TWCMWSFXC
Date: 4 Aug 2013 20:11:05 -0000
Message-ID: <20130804201105.3986.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Speaking of VAT
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:11:35 -0000

At last week's very successful Berlin meeting, the finances were
thrown of whack by the late discovery that the IETF had to pay 19%
German VAT on the registration fee.  At the IAOC session they said
that about half of that is likely to be reclaimed from VAT paid, but
the net amount is still a large number.

In Buenos Aires, the VAT rate is 21% on most goods and services, with
a special 27% rate on telecom services.

Just saying,

R's,
John

PS: In Vancouver last year there was a combined federal and provincial
VAT, called HST, of 12%.  Now they're split, with the 5% federal VAT,
called GST, at 5%, and the 7% provincial sales tax (PST) applied
separately.


From brian.e.carpenter@gmail.com  Sun Aug  4 13:20:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C102411E80E4 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.509
X-Spam-Level: 
X-Spam-Status: No, score=-102.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYJepRZsfOUg for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:20:40 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id DDBA011E80D5 for <ietf@ietf.org>; Sun,  4 Aug 2013 13:20:39 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id lj1so2524769pab.15 for <ietf@ietf.org>; Sun, 04 Aug 2013 13:20:39 -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=7eNpZdHlHMrfC9ueapG7W0kuY9LhDSTfESbCMlymLVU=; b=J2kc4wq2u5b16l/7kk6xgv70MDtjsYM7FOXzfddHBxkwZ47ZwUKT0xHfg56H8c+83g oPWNr1dFnr0+xeZIuSOiQd+/wmYOWLnKm62qIOp/XsY2yIkKJ1bGErcTxICpmZzmN/o0 jYu1TXa5ZQyyruCCFQR4/It3i4GMcd9oelkLgFEdBEDlyYtd8Rp0H2rRPMvTRfpq2cNP kxOzHrliYakH046gFDfpKs5AmiHHBXAOEMmyV1dG2tPJ05XY417K9Mz+bUNBytUKt2in Hr9jS+sHE9TV8vsvDiMy0txohxZcjb+dmqJE0hxFbnL4x6a0NaPwYSClbqos3ka2Ti9A UsYQ==
X-Received: by 10.66.189.225 with SMTP id gl1mr21754708pac.22.1375647639599; Sun, 04 Aug 2013 13:20:39 -0700 (PDT)
Received: from [192.168.178.23] (6.199.69.111.dynamic.snap.net.nz. [111.69.199.6]) by mx.google.com with ESMTPSA id oe6sm20076745pbb.20.2013.08.04.13.20.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 04 Aug 2013 13:20:38 -0700 (PDT)
Message-ID: <51FEB793.3050506@gmail.com>
Date: Mon, 05 Aug 2013 08:20:35 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org>	<8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>	<ECF4A733EFD13FA1753C063B@[192.168.1.128]>	<32634.1375615620@sandelman.ca>	<057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:20:40 -0000

On 05/08/2013 06:54, Ted Lemon wrote:
> While I think getting slides in on time is great for a lot of reasons, reading the slides early isn't that important.   What is important is that remote people see the slides at the same time as local people.   For that, it seems to me that Meetecho support does exactly what is needed.   You just follow the slideshow online, along with the audio.
> 
> Of course, in order to have Meetecho support, you need the slides in advance of the meeting, preferably far enough in advance that it doesn't create a massive hassle for the Meetecho team. But by making Meetecho the place where the slides are presented, you ensure that everybody is on an equal footing, without engaging in punitive behavior.
> 
> The main reason to want to see the slides in advance is so that the working group chairs can evaluate them to see if they will actually be a good use of time.   But that's completely orthogonal to the remote participation issue.

For remote attendees, there is a distinct advantage in having time to
download & store slides in advance. There are still plenty of places
where real-time bandwidth is an issue and audio and jabber may be
all you can get.

There is another equally important reason for having them well in advance,
for both on-site and remote attendees: so that participants can review
them in advance, decide which of several clashing sessions to attend, and
even prepare questions. This applies even if the slides summarise a draft
that was available two or three weeks in advance. Things are often
expressed differently in the slides.

Finally: a deadline one week before the meeting is no harder to meet
than one minute before the meeting. If it's a zero-tolerance deadline,
people will meet it.

   Brian

From scott.brim@gmail.com  Sun Aug  4 13:25:44 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 775BC11E80EA for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:25:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, 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 WlkuohrrLRFS for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:25:43 -0700 (PDT)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8342B11E80EC for <ietf@ietf.org>; Sun,  4 Aug 2013 13:25:43 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id g12so4645101oah.6 for <ietf@ietf.org>; Sun, 04 Aug 2013 13:25: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=FfU5bkvxtj5gY+Dva9wt59ATPl8MDJ7zgJ7g6KFglbk=; b=PsioZjPcDHVnrMQ8XS4PMHx5wbfNWswBp+tvR/WZJvRtwcwB/ZJkFe6Y/ppB7koKLJ +kqYcgWi8101KdyulI6utF/5Y3UCxeS4QhlSw5wOxsx4CZLf9q7J95tP20HajdSRLiP9 3s0fgVXDQYmpADg39FWvTAKQLnAVJr4ZRLqzIUy0ngqG5vRINucwzHNT8TuSJGjUQgrL PXlNXr0rUWKMP7NfaBAnEYZEfUm+yJ5EQ+9TsNdY3TAd+v9wMNUihqz9DModTbjrTB6b O7ZG/AUlGhF+2SRTTLCgZ8rrgcBLk1IC3cb7VZ2X1g0AlcWj0whq3vks9S3gYAMyHgHT ONIw==
MIME-Version: 1.0
X-Received: by 10.182.220.199 with SMTP id py7mr12193978obc.92.1375647942721;  Sun, 04 Aug 2013 13:25:42 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Sun, 4 Aug 2013 13:25:42 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Sun, 4 Aug 2013 13:25:42 -0700 (PDT)
In-Reply-To: <51FEB793.3050506@gmail.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@192.168.1.128> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <51FEB793.3050506@gmail.com>
Date: Sun, 4 Aug 2013 16:25:42 -0400
Message-ID: <CAPv4CP9qmLtxSJ=ZC03FBZh3_ciDAuheHCxU_yOMXrEDuqcLRg@mail.gmail.com>
Subject: Re: procedural question with remote participation
From: Scott Brim <scott.brim@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c334aaf644b504e324fe09
Cc: "&lt,ietf@ietf.org&gt," <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:25:44 -0000

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

I'm less concerned about having slides than having the issues that need
discussion clear. An agenda of documents and issues tells potential
participants what they need. Slides are needed if and only if there is no
document.

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

<p dir=3D"ltr">I&#39;m less concerned about having slides than having the i=
ssues that need discussion clear. An agenda of documents and issues tells p=
otential participants what they need. Slides are needed if and only if ther=
e is no document.=A0 </p>


--001a11c334aaf644b504e324fe09--

From john-ietf@jck.com  Sun Aug  4 13:55:48 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D877811E80F0 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:55: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 rDf2AiUAfTf0 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 13:55:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2C821F9F3D for <ietf@ietf.org>; Sun,  4 Aug 2013 13:55:43 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V65L3-0003Oe-DN; Sun, 04 Aug 2013 16:55:41 -0400
X-Vipre-Scanned: 04674AEA002C3104674C37-TDI
Date: Sun, 04 Aug 2013 16:55:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: The Friday Report (was Re: Weekly posting summary for	ietf@ietf.org)
Message-ID: <8C1E4FC360C0F4D07C51298A@[192.168.1.128]>
In-Reply-To: <20130804195342.3851.qmail@joyce.lan>
References: <20130804195342.3851.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 20:55:49 -0000

--On Sunday, August 04, 2013 19:53 +0000 John Levine
<johnl@taugh.com> wrote:

>> If there is a serious drive to discontinue the weekly posting
>> summary - I strongly object.
> 
> As far as I can tell, one person objects, everyone else thinks
> it's fine.

I do not want to be recorded as thinking it is fine.  If nothing
else, I think was is being reported is meaningless statistically
(which doesn't mean people can't find value in it).   However, I
do not object to its being posted as long as it isn't used to
justify personal attacks on individuals for their "ranking".

It seems to me that isn't quite what you said, rough consensus
or not.

best,
   john



From ynir@checkpoint.com  Sun Aug  4 14:17:18 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15C721E8095 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.502
X-Spam-Level: 
X-Spam-Status: No, score=-10.502 tagged_above=-999 required=5 tests=[AWL=0.097, 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 H1dY2p+5obng for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:17:13 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8764121E8093 for <ietf@ietf.org>; Sun,  4 Aug 2013 14:17:12 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r74LGlQC027453; Mon, 5 Aug 2013 00:16:51 +0300
X-CheckPoint: {51FEC4BF-D-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Mon, 5 Aug 2013 00:16:46 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: John Levine <johnl@taugh.com>
Subject: Re: Speaking of VAT
Thread-Topic: Speaking of VAT
Thread-Index: AQHOkU7emeo79NMUDUi4kgZ1K7Q/uZmFWu4A
Date: Sun, 4 Aug 2013 21:16:44 +0000
Message-ID: <65A4EBE4-B342-46B3-82C6-8A81674C3EC0@checkpoint.com>
References: <20130804201105.3986.qmail@joyce.lan>
In-Reply-To: <20130804201105.3986.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.202]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 115065c7990385dd29f1584574ba291b75b5985d81
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1D58DE50D8356C429D97AD8714DBEB8B@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 21:17:18 -0000

On Aug 4, 2013, at 11:11 PM, John Levine <johnl@taugh.com> wrote:

> At last week's very successful Berlin meeting, the finances were
> thrown of whack by the late discovery that the IETF had to pay 19%
> German VAT on the registration fee.  At the IAOC session they said
> that about half of that is likely to be reclaimed from VAT paid, but
> the net amount is still a large number.

The usual IANAL and IANAC should not be joined by IANACPA.

But a CPA at my company said that we couldn't reclaim the VAT, because the =
"service" was consumed in Germany. If others hear different from their acco=
unting departments, I'd love to hear about it.

Just another data point.

Yoav=

From hadriel.kaplan@oracle.com  Sun Aug  4 14:27:50 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3087E21E809A for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 SAF6brUiNOOz for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:27:43 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id A713321E8092 for <ietf@ietf.org>; Sun,  4 Aug 2013 14:27:43 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r74LRdMq020589 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Aug 2013 21:27:40 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r74LRcVO023994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Aug 2013 21:27:39 GMT
Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r74LRced021194; Sun, 4 Aug 2013 21:27:38 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 04 Aug 2013 14:27:38 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <51FEB793.3050506@gmail.com>
Date: Sun, 4 Aug 2013 17:27:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <20921C58-D847-48FD-8EE3-0ABD61D24E6B@oracle.com>
References: <CE218890.17010%york@isoc.org>	<8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>	<ECF4A733EFD13FA1753C063B@[192.168.1.128]>	<32634.1375615620@sandelman.ca>	<057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <51FEB793.3050506@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
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, 04 Aug 2013 21:27:50 -0000

On Aug 4, 2013, at 4:20 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> There is another equally important reason for having them well in =
advance,
> for both on-site and remote attendees: so that participants can review
> them in advance, decide which of several clashing sessions to attend, =
and
> even prepare questions. This applies even if the slides summarise a =
draft
> that was available two or three weeks in advance. Things are often
> expressed differently in the slides.

By that logic, I should also write out a script of what I'm going to say =
and post that 1 week in advance, along with a youtube recording of me =
presenting it.  At least for me, most of the content/meat is verbal, not =
pictorial.  The slides aren't a script of text I'm reading out loud.

As for conflicts, I agree they truly do suck, but I wouldn't want you to =
pick/skip mine based on my poor slide-making abilities.  In the worst =
case, you can review the recordings afterward and email =
comments/questions/flames to the list.


> Finally: a deadline one week before the meeting is no harder to meet
> than one minute before the meeting. If it's a zero-tolerance deadline,
> people will meet it.

This would just encourage more presentations to be graphical =
reproductions of the drafts.  I'm cool with having those types of slides =
as well, even well in advance - but only separate from the ones I =
present in a meeting.  We should be encouraging email discussions to =
take place before the physical meeting hour... and I don't want =
set-in-stone slides to skip things introduced by, cover ground already =
covered by, or made moot by, those discussions.  I don't know about =
other folks, but I really have changed slide content based on mailing =
list and in-person discussions before the meeting slot.  This even =
happened to me just this past week at IETF 87.

These aren't presentations of academic papers, corporate position =
statements, or tutorial classes.  Real-time content and discussion is =
good for WG meetings.=20

What *would* be good to have 7 days or more in advance are the Technical =
and O&A Plenary slides.  They shouldn't be changing, afaict.  And that =
way we can figure out if we can have those nights free for other things, =
or if it's worth going to the Plenaries instead.  But I assume those =
slides already are made available well in advance. (right?)

-hadriel


From jari.arkko@piuha.net  Sun Aug  4 14:44:31 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7905921E809A for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.518
X-Spam-Level: 
X-Spam-Status: No, score=-102.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id igXooK0b+QI0 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:44:26 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 1A23B21E8093 for <ietf@ietf.org>; Sun,  4 Aug 2013 14:44:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id DD3F22CC68 for <ietf@ietf.org>; Mon,  5 Aug 2013 00:44:23 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-ESF3XGtcks for <ietf@ietf.org>; Mon,  5 Aug 2013 00:44:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 297732CC50 for <ietf@ietf.org>; Mon,  5 Aug 2013 00:44:22 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20130804195342.3851.qmail@joyce.lan>
Date: Sun, 4 Aug 2013 23:44:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <643527DC-4014-4FE7-ACB3-F67C2122F465@piuha.net>
References: <20130804195342.3851.qmail@joyce.lan>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 21:44:31 -0000

First, I'd like to highlight something that is important. There is no =
inherent preference to posting a lot, a moderate amount, or none at all. =
Everything depends on context. If you are providing useful input and =
furthering the discussion, a lot of mails is ok. And no mails can be a =
problem, too, if you were supposed to participate, such as when you are =
an author of a document on the topic. For instance, when I look at =
Thomas' report, if I don't appear there I probably should have paid more =
attention.=20

In other words, you should not look at how much people post on lists =
alone=85  and no matter what you post, please be considerate of other =
people, avoid repetition, stay on topic, etc.

Secondly, don't we have better things to do than to argue about e-mail =
list summary reports? Several people find them useful. I'm sure there is =
something in the Internet that still needs fixing :-)

Jari


From johnl@taugh.com  Sun Aug  4 14:47:45 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1DC21E80AB for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSXHWtAlCCes for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 14:47:44 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E214021E809A for <ietf@ietf.org>; Sun,  4 Aug 2013 14:47:42 -0700 (PDT)
Received: (qmail 69844 invoked from network); 4 Aug 2013 21:47:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=110d3.51fecbfe.k1308; bh=S/dn8m3JiNbxlMJxzk3dAdm3NwOkA7o3+3c8oYv8brI=; b=LcwjWuOTdicGzFwECPmQPvyAbVnBCQ56wsjk4DuHCa/TJJcHjnxTs2WxprSXV7O03yyv4la295WNzKW9SvctwJzjjsZAKxq4vL+eejmGbczYP+Ju+IMOkVk87A4TolY+/X67k7KIIWXCBizPGvpF2UPTloxvNs2pLGxt5dj1LRPAc4Z8sSJopDeLc0CFwBh5z1igVGXhD6HXWpXx9FSsLxBYqy07nl3vfCq+vWgcc5foDwD3KjxJ7/Uui3OJ45BG
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=110d3.51fecbfe.k1308; bh=S/dn8m3JiNbxlMJxzk3dAdm3NwOkA7o3+3c8oYv8brI=; b=lcVa7+urFmF/jrYb/Yp/V608HbyI2Y6JknJd1VRNEZ4z2buuzp2wk0TVEnmdYDwy45/ubNcXYG8u3yaH7Y46lcokEBml3kYF109rZ5xgUATrfmwcLl+qezHdg6OsDPdFr3ytfQ30eG67/s3gqAfPxIHfegDXRr8Duut2LwG8tyKd+wGJx/P7sZwzPijHxYV2IKywhiewDHW+pFQugF//AztdpFq1qx3QsZ+7SPITG1dICpMkKyet3UCHk8uK01eJ
Received: (ofmipd 127.0.0.1); 4 Aug 2013 21:47:20 -0000
Date: 4 Aug 2013 17:47:41 -0400
Message-ID: <alpine.BSF.2.00.1308041746210.2773@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Yoav Nir" <ynir@checkpoint.com>
Subject: Re: Speaking of VAT
In-Reply-To: <65A4EBE4-B342-46B3-82C6-8A81674C3EC0@checkpoint.com>
References: <20130804201105.3986.qmail@joyce.lan> <65A4EBE4-B342-46B3-82C6-8A81674C3EC0@checkpoint.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>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 21:47:45 -0000

>> At last week's very successful Berlin meeting, the finances were
>> thrown of whack by the late discovery that the IETF had to pay 19%
>> German VAT on the registration fee.  At the IAOC session they said
>> that about half of that is likely to be reclaimed from VAT paid, but
>> the net amount is still a large number.
>
> The usual IANAL and IANAC should not be joined by IANACPA.
>
> But a CPA at my company said that we couldn't reclaim the VAT, because the "service" was consumed in Germany. If others hear different from their accounting departments, I'd love to hear about it.

Ray said the tax guys told him the IETF would get back about half of the 
VAT it paid.  That's unrelated to what anyone can reclaim.

My understanding is that Germany has reciprocal VAT agreements with a 
bunch of countries so if your employer is in one of those countries it may 
be able to reclaim, but since the US isn't one of them I haven't looked in 
detail.

R's,
John

From stephen.farrell@cs.tcd.ie  Sun Aug  4 15:21:44 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33FD111E80D1 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HT5qE6s45mi for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:21:38 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0CA11E80F5 for <ietf@ietf.org>; Sun,  4 Aug 2013 15:21:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A9B5DBE56; Sun,  4 Aug 2013 23:21:08 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 448dOuaEyFq7; Sun,  4 Aug 2013 23:21:08 +0100 (IST)
Received: from [10.0.4.107] (unknown [89.246.150.136]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E3377BE54; Sun,  4 Aug 2013 23:21:07 +0100 (IST)
Message-ID: <51FED3D1.1080000@cs.tcd.ie>
Date: Sun, 04 Aug 2013 23:21:05 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org>	<8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>	<ECF4A733EFD13FA1753C063B@[192.168.1.128]>	<32634.1375615620@sandelman.ca>	<057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <51FEB793.3050506@gmail.com>
In-Reply-To: <51FEB793.3050506@gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 22:21:44 -0000

On 08/04/2013 09:20 PM, Brian E Carpenter wrote:
> Finally: a deadline one week before the meeting is no harder to meet
> than one minute before the meeting.

Disagree. I often end up updating stuff late in the day and that
should continue to be fine.

Secondarily, its my impression that people are as usual taking all
this too seriously. If we cumulatively do our best and if that works
ok, then overall, we're ok.

Improving on current practice is a fine thing too. But claiming or
implying that the imperfections of current practice are disastrous
for the IETF or for all remote participation seems overblown to me.
And only something potentially disastrous ought imply even considering
a zero-tolerance anything in a volunteer organisation.

So I'd say working on ways to make remote participation better
while not making f2f participation more of a pain would be the way
to go.

S.


From melinda.shore@gmail.com  Sun Aug  4 15:37:39 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4DB11E80F7 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 RzclLfSirudp for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:37:39 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 04B7211E80F6 for <ietf@ietf.org>; Sun,  4 Aug 2013 15:37:38 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id bv13so2531181pdb.16 for <ietf@ietf.org>; Sun, 04 Aug 2013 15:37:38 -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=u6awMOQjKPFwWGFWIRb+lUliChedhLwbdU6mNxjHByc=; b=vi9UZJVtXbNSrNK9Tlt3pXC3jZLLhgy4JqNDLANYWgHBIGQ+YMtq1EKXOrTJ4wZiL3 6v5eV59wqYZXlP3C32fhp+KmdTZ0wUYyWfjwpSnVgzPSdrBSE3hGiKGMrDRPU395lqnO /nJcwuwyV6eHWDqvgBwaQd5J4G+CP0SSLD8xAYJHVZKujoDDS6i+PvytViMcW9DJAwnZ XrISI4mY7iJ5wdiu52NK5EUhYCBh+WWok16ePPssqBpp6c700mWc6ukWCmJc4b4nDNAU p6eZGYnM2P0RakiQVMpfOp7vgaNYKDRr54eziBlgHhKNPrNDwJPESAsFrNNK7l+hePli tIdg==
X-Received: by 10.68.90.99 with SMTP id bv3mr19197206pbb.108.1375655858648; Sun, 04 Aug 2013 15:37:38 -0700 (PDT)
Received: from spandex.local (66-230-112-156-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.156]) by mx.google.com with ESMTPSA id vu5sm23855402pab.10.2013.08.04.15.37.37 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 04 Aug 2013 15:37:37 -0700 (PDT)
Message-ID: <51FED7AF.2050504@gmail.com>
Date: Sun, 04 Aug 2013 14:37:35 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org>	<8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net>	<ECF4A733EFD13FA1753C063B@[192.168.1.128]>	<32634.1375615620@sandelman.ca>	<057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <51FEB793.3050506@gmail.com> <51FED3D1.1080000@cs.tcd.ie>
In-Reply-To: <51FED3D1.1080000@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 22:37:39 -0000

We're all different, and for my purposes, in all honesty, having
slides unavailable until 45 seconds before a session start hasn't
been an issue as a remote participant.  It's definitely aggravating
as a chair, though, since we need to get those uploaded via the
meeting materials manager.  Overall, though, I'd say my feelings
about this are substantially similar to Stephen Farrel's:

    So I'd say working on ways to make remote participation better
    while not making f2f participation more of a pain would be the way
    to go.

And it's unclear to me that having slides available a week before
a session would improve remote participation much.

Melinda

From hadriel.kaplan@oracle.com  Sun Aug  4 15:42:17 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDE511E80FC for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.503
X-Spam-Level: 
X-Spam-Status: No, score=-6.503 tagged_above=-999 required=5 tests=[AWL=0.096,  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 DCCysz81zAZg for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:42:01 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 22C9811E80F9 for <ietf@ietf.org>; Sun,  4 Aug 2013 15:42:01 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r74MfpKq025722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 4 Aug 2013 22:41:53 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r74Mfnbg023821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Aug 2013 22:41:50 GMT
Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r74Mfm9b029821; Sun, 4 Aug 2013 22:41:49 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 04 Aug 2013 15:41:48 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <ECF4A733EFD13FA1753C063B@[192.168.1.128]>
Date: Sun, 4 Aug 2013 18:41:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: Dan York <york@isoc.org>, "Olle E. Johansson" <oej@edvina.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 22:42:17 -0000

On Aug 3, 2013, at 7:25 PM, John C Klensin <john-ietf@jck.com> wrote:

> First, probably to the "when meetings begin" part, but noting
> that someone who gets onto the audio a few minutes late is in
> exactly the same situation as someone who walks into the meeting
> room a few minutes late -- announcements at the beginning of the
> session are ineffective.

Jabber appears to have some way of setting a banner/announcement thing =
that shows up when you first join a jabber session, because I've seen =
such a thing on occasion.  I don't know if it's defined in some standard =
way in XMPP or a proprietary extension.  But assuming it's either =
standard or defacto and popular, we could put the NOTE WELL in it (or a =
URL to a NOTE WELL).

Likewise for the IETF web pages with the audio links, so that you see =
the NOTE WELL before clicking the audio link.  Or even have an annoying =
pop-up if you prefer. (ugh)


> We regularize remote participation [1] a bit by doing the
> following.  At some level, if remote participants expect to be
> treated as serious members of the community, they (we) can
> reasonably be expected to behave that way.
>=20
> * A mechanism for remote participants should be set up
> 	and remote participants should be to register.  The
> 	registration procedure should include the Note Well and
> 	any other announcement the IETF Trust, IAOC, or IESG
> 	consider necessary (just like the registration procedure
> 	for f2f attendance).

Sure - to *participate*, i.e. have a chance at the mic.  Not to =
listen/watch/read.=20


> * In the hope of increased equity, lowered overall
> 	registration fees, and consequently more access to IETF
> 	participation by a broader and more diverse community,
> 	the IAOC should establish a target/ recommended
> 	registration fee for remote participants.  That fee
> 	should reflect the portion of the registration fee that
> 	is not specifically associated with meeting expenses
> 	(i.e., I don't believe that remote participants should
> 	be supporting anyone's cookies other than their own). =20
> =09
> * In the interest of maximum participation and inclusion
> 	of people are aren't attending f2f for economic reasons,
> 	I think we should treat the registration fee as
> 	voluntary, with people contributing all or part of it as
> 	they consider possible.  No questions asked and no
> 	special waiver procedures.  On the other hand,
> 	participation without registration should be considered
> 	as being in extremely bad taste or worse, on a par with
> 	violations of the IPR disclosure rules.

I don't agree - I go to the meetings physically, but I *want* remote =
people to participate.  It's to everyone's benefit that they do so, =
including the physical attendees.  I don't want to charge them for it.  =
Making them register (for free) is fine, but don't make them pay money.  =
Don't even make them feel guilty.  The people who can afford the time =
and money to go to the physical meetings still get their money's worth.


> * I don't see a practical and non-obtrusive way to
> 	enforce registration, i.e., preventing anyone
> 	unregistered from speaking, modulo the "bad taste"
> 	comment above.  But we rarely inspect badges before
> 	letting people stand in a microphone line either.

Sure there is.  Have the current "[wg-name]@jabber.ietf.org" jabber =
rooms be for open access lurking, from any XMPP domain, and not allow =
microphone representation in the WG by simply having jabber scribes =
ignore such requests in those rooms.  And have separate rooms that =
require registering, like "[wg-name]@members.ietf.org" or whatever, =
where you have to have a registered account on 'members.ietf.org'.  I =
assume XMPP servers support such a policy?  It would be a free account, =
but require filling out the blue-sheet type information, verified email =
address, etc.  Or maybe even have it all in the same current jabber room =
but only accounts with "members.ietf.org" as the domain portion are =
represented at the mic by the jabber scribes.


> In return, the IETF generally (and particularly people in the
> room) needs to commit to a level of seriousness about remote
> participation that has not consistently been in evidence.  In
> particular:
>=20
> 	* Remote participants should have as much access to mic
> 	lines and the ability to participate in discussions as
> 	those who are present in the room.   That includes
> 	recognizing that, if there is an audio lag and it takes
> 	a few moments to type in a question or comment, some
> 	flexibility about "the comment queue is closed" may have
> 	to be in order.  For some sessions, it might require
> 	doing what ICANN has started doing (at least sometimes),
> 	which is treating the remote participants as a separate
> 	mic queue rather than expecting the Jabber scribe (or
> 	remote participant messenger/ channeler) to get at the
> 	end of whatever line is most convenient.

Do you find this is an actual problem in WG meetings?  My experience has =
been the opposite.  The WG chairs always seem to let jabber participants =
get their 2 cents in, even if the queue line has been capped... =
especially if there's lag.


> 	* It is really, really, important that those speaking,
> 	even if they happen to be sitting at the chair's table,
> 	clearly and carefully identify themselves.  Last week,
> 	there were a few rooms in which the audio was, to put it
> 	very politely, a little marginal.  That happens.  But,
> 	when it combines with people mumbling their names or
> 	saying them very quickly, the result is as little
> 	speaker identification as would have been the case if
> 	the name hadn't been used as all.  In addition, some of
> 	us suffer from the disability of not being able to keep
> 	track of unfamiliar voices while juggling a few decks of
> 	slides, a jabber session, audio, and so on.   "I
> 	identified myself 10 minutes ago" is not generally
> 	adequate.

Do you find this is an actual problem in WG meetings?  Are the jabber =
scribes not able to tell you who is at the mic if you ask them?  People =
have forgotten to state their names in WGs I go to, but the scribes have =
been fairly vocal about reminding folks to do it.

-hadriel



From ad707@hermes.cam.ac.uk  Sun Aug  4 15:56:40 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB8B11E80FB for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:56:40 -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 ZS+iP5CnvqkJ for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 15:56:40 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id E9ACB21F9958 for <ietf@ietf.org>; Sun,  4 Aug 2013 15:56:39 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:56535) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:ad707) id 1V67E6-0006ey-1g (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Sun, 04 Aug 2013 23:56:38 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V67E6-0006wr-Eh (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Sun, 04 Aug 2013 23:56:38 +0100
Received: from [131.111.218.40] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 04 Aug 2013 23:56:38 +0100
Date: 04 Aug 2013 23:56:38 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: melinda.shore@gmail.com
Subject: Re: procedural question with remote participation
Message-ID: <Prayer.1.3.5.1308042356380.22856@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 22:56:40 -0000

On 04/08/13 23:37, Melinda Shore wrote:
> We're all different, and for my purposes, in all honesty, having
> slides unavailable until 45 seconds before a session start hasn't
> been an issue as a remote participant.  It's definitely aggravating
> as a chair, though, since we need to get those uploaded via the
> meeting materials manager.  Overall, though, I'd say my feelings
> about this are substantially similar to Stephen Farrel's:
>
>     So I'd say working on ways to make remote participation better
>     while not making f2f participation more of a pain would be the way
>     to go.

Thanks for pointing this out.

>
> And it's unclear to me that having slides available a week before
> a session would improve remote participation much.

On top of it, we probably are familiar with such scenes that many 
presenters get suggestions from WG peers about their work and upgrade their 
slides day before the WG meetings.

For diversity, we need to take remote participants seriously. At the same 
time, we should also care for the IETFers who are submitting their work.

Thanks,
Aaron


>
> Melinda

From spencerdawkins.ietf@gmail.com  Sun Aug  4 16:10:40 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F298221E80AD for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 16:10:39 -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.048,  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 P-YKQGjMdRxj for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 16:10:38 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 7D68621E804E for <ietf@ietf.org>; Sun,  4 Aug 2013 16:10:35 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id k18so4946481oag.12 for <ietf@ietf.org>; Sun, 04 Aug 2013 16:10:35 -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; bh=jNamou9fPgeo05lr3Lq4gS1IVQXIfHYhMzNAkJXoYSs=; b=Zc35J9vceujzh1DV857360/vnW0LU+OpVXOJ1lUMF3N9/QSwNNsopoOegclOC8UOWd HYtBW/9PCkDbV+J6J+csmwG6DeYWHyFV51m+xjMJUq0UDK0fqFQOpxmd62WdWW5RofkK 0b+19sMLu3l0LiamqvZ0P4afqfUhL9y+35I0n5FyBaPsiMlM5JE4K1FNFQNzVkAZrj1r v6NnZCk22hmjNgXKPOxAWYe++Ky18hqOjNe49pD3i8XLSXIoyHLaJKs5airKDKi11NYe ZYMZ0z5+/wUUb7aQFSWAUOtR/UMMKdEFgBqXolEKVVvI4JE8c7MAeaKZ2IEqcCYJGen/ HECg==
X-Received: by 10.60.117.34 with SMTP id kb2mr12261395oeb.54.1375657835037; Sun, 04 Aug 2013 16:10:35 -0700 (PDT)
Received: from [192.168.0.23] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id h3sm21035658oeo.2.2013.08.04.16.10.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 04 Aug 2013 16:10:34 -0700 (PDT)
Message-ID: <51FEDF60.2010902@gmail.com>
Date: Sun, 04 Aug 2013 18:10:24 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com>
In-Reply-To: <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com>
Content-Type: multipart/alternative; boundary="------------080704040309060501000102"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Aug 2013 23:10:40 -0000

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

On 8/4/2013 3:10 PM, Hadriel Kaplan wrote:
> OK, I'll bite.  Why do you and Michael believe you need to have the slides 1 week in advance?
>
> You have the agenda and drafts 2 weeks in advance.  The slides aren't normative.  Even when they're not about a draft in particular, the slides are not self-standing documents.  They're merely to help with discussion.
>
> Not getting the slides at all is a different matter - but 7 days in advance is counter-productive.  They should be as up-to-date as practical, to take into account mailing list discussions. [or at least that's how I justify my same-day, ultra-fresh slides]
>
> If you need to have them on the website 7 days in advance, you really need to get a faster Internet connection. ;)

I'm a TSV AD, but I'm sending this note wearing no hat (someone last 
week asked me why I wasn't wearing a cowboy hat if I was from Texas - 
no, not even a cowboy hat).

I read through the discussion on this, and I'm only responding to 
Hadriel because his post was the last one I saw before replying. Thank 
you all for sharing your thoughts.

YMMV ("Your Mileage May Vary"), but I have been sponsored for several 
years by a company that sends a sizable number of folks to IETF who are 
not native English speakers. Having slides early helps non-native 
English speakers (I believe I've heard that some slide decks are 
translated into other languages, although I wouldn't know, because I 
read the slides in English).

After his first IETF (Paris/63), Fuyou Maio said to me, "understanding 
spoken English is the short board in the water barrel" (the idea being 
that your effectiveness at the IETF is limited by your ability to 
quickly parse spoken English). The folks I talk to get plenty of chances 
to translate spoken English during Q&A, and don't need additional 
practice translating the presentations in real time. Yes, I know people 
say things that aren't on their slides, but if what's on their slides 
doesn't help other people understand what they are saying, they probably 
shouldn't be using those slides.

In the mid-2000s, I remember an admonition for chairs to write out the 
questions the chairs are taking a hum on, to accommodate non-native 
English speakers (and to write out all the questions before taking the 
first hum, to accommodate anyone who agrees with the second choice but 
prefer the fourth choice when they hear it after humming).

I'm having a hard time making the "a week early or you don't present" 
case for slide cutoffs, because we DO talk during the meeting week - and 
in groups RTCWeb, with a Thursday slot and a Friday slot, we had time to 
talk a lot. If the cutoff was for presentations of new individual 
drafts, that's a different question, so there might be some way to make 
non-Procrustean improvements(*).

I agree with the "chairs looking at slides for sanity" point. I'm 
remembering more than one working group where we chairs got 
presentations that included about a slide per minute for the time 
allocated to the topic - noticing that even one day before saved us from 
the ever-popular "we can't talk about this presentation because we don't 
have time" moment.

During IETF 87, I had reason to consult the proceedings for the 
non-workgroup-forming RUTS BOF ("Requirements for Unicast 
Transport/Sessions" at IETF 43, minutes at 
http://www.ietf.org/proceedings/43/43rd-ietf-98dec-142.html#TopOfPage) 
<http://www.ietf.org/proceedings/43/43rd-ietf-98dec-142.html#TopOfPage>. 
This was the applications-focused wishlist for transport from 1998, when 
COPS, RADIUS, L2TP, HTTP-NG, SIP, NFSv4, SS7, IP Telephony and BGP4 were 
all trying to figure out whether they needed to (continue to, in some 
cases) rely on TCP for transport, or do "something else". I'm 
remembering that there were slides, and I would love to have them to 
refer to, but *none* of the slide decks made it into the proceedings. 
That was pre-Meeting Materials page, but even my experience with the 
Meeting Materials page was that it's easier for slide decks arriving 
late to go missing than for slide decks that arrived early.

As I reminded myself while starting to present v4 of the chair slides in 
TSVAREA and realizing that what Martin was projecting was v1 (only a day 
older), getting slidesets nailed down early limits the number of times 
when you're surprised at what's being projected.

I love consolidated slide decks. I bet anyone does, whose laptop 
blue-screened while hooking up to a projector in the late 1990s. Nothing 
good happens during transitions, whether switching laptops or switching 
presentations :-)

None of this should be taken as disagreement with proposals to 
experiment with room shapes, whiteboards, , etc. that I heard last week.

None of this should be taken as evidence of love for an unbroken stream 
of presentations of drafts that aren't tied to issues discussed on 
mailing lists, or as disagreement with the idea that presentations 
aren't always the best way to communicate at the IETF.

Thanks,

Spencer, who also might disagree with some of this when he wakes up at a 
normal hour ... and that hasn't happened yet ...

(*) from http://www.thefreedictionary.com/Procrustean, "producing or 
designed to produce strict conformity by ruthless or arbitrary means".

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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 8/4/2013 3:10 PM, Hadriel Kaplan
      wrote:<br>
    </div>
    <blockquote
      cite="mid:6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com"
      type="cite">
      <pre wrap="">OK, I'll bite.  Why do you and Michael believe you need to have the slides 1 week in advance?

You have the agenda and drafts 2 weeks in advance.  The slides aren't normative.  Even when they're not about a draft in particular, the slides are not self-standing documents.  They're merely to help with discussion.

Not getting the slides at all is a different matter - but 7 days in advance is counter-productive.  They should be as up-to-date as practical, to take into account mailing list discussions. [or at least that's how I justify my same-day, ultra-fresh slides]

If you need to have them on the website 7 days in advance, you really need to get a faster Internet connection. ;)
</pre>
    </blockquote>
    <br>
    I'm a TSV AD, but I'm sending this note wearing no hat (someone last
    week asked me why I wasn't wearing a cowboy hat if I was from Texas
    - no, not even a cowboy hat).<br>
    <br>
    I read through the discussion on this, and I'm only responding to
    Hadriel because his post was the last one I saw before replying.
    Thank you all for sharing your thoughts.<br>
    <br>
    YMMV ("Your Mileage May Vary"), but I have been sponsored for
    several years by a company that sends a sizable number of folks to
    IETF who are not native English speakers. Having slides early helps
    non-native English speakers (I believe I've heard that some slide
    decks are translated into other languages, although I wouldn't know,
    because I read the slides in English).<br>
    <br>
    After his first IETF (Paris/63), Fuyou Maio said to me,
    "understanding spoken English is the short board in the water
    barrel" (the idea being that your effectiveness at the IETF is
    limited by your ability to quickly parse spoken English). The folks
    I talk to get plenty of chances to translate spoken English during
    Q&amp;A, and don't need additional practice translating the
    presentations in real time. Yes, I know people say things that
    aren't on their slides, but if what's on their slides doesn't help
    other people understand what they are saying, they probably
    shouldn't be using those slides.<br>
    <br>
    In the mid-2000s, I remember an admonition for chairs to write out
    the questions the chairs are taking a hum on, to accommodate
    non-native English speakers (and to write out all the questions
    before taking the first hum, to accommodate anyone who agrees with
    the second choice but prefer the fourth choice when they hear it
    after humming).<br>
    <br>
    I'm having a hard time making the "a week early or you don't
    present" case for slide cutoffs, because we DO talk during the
    meeting week - and in groups RTCWeb, with a Thursday slot and a
    Friday slot, we had time to talk a lot. If the cutoff was for
    presentations of new individual drafts, that's a different question,
    so there might be some way to make non-Procrustean improvements(*).<br>
    <br>
    I agree with the "chairs looking at slides for sanity" point. I'm
    remembering more than one working group where we chairs got
    presentations that included about a slide per minute for the time
    allocated to the topic - noticing that even one day before saved us
    from the ever-popular "we can't talk about this presentation because
    we don't have time" moment.<br>
    <br>
    During IETF 87, I had reason to consult the proceedings for the
    non-workgroup-forming RUTS BOF ("Requirements for Unicast
    Transport/Sessions" at IETF 43, minutes at <a
      moz-do-not-send="true"
href="http://www.ietf.org/proceedings/43/43rd-ietf-98dec-142.html#TopOfPage">http://www.ietf.org/proceedings/43/43rd-ietf-98dec-142.html#TopOfPage)</a>.
    This was the applications-focused wishlist for transport from 1998,
    when COPS, RADIUS, L2TP, HTTP-NG, SIP, NFSv4, SS7, IP Telephony and
    BGP4 were all trying to figure out whether they needed to (continue
    to, in some cases) rely on TCP for transport, or do "something
    else". I'm remembering that there were slides, and I would love to
    have them to refer to, but *none* of the slide decks made it into
    the proceedings. That was pre-Meeting Materials page, but even my
    experience with the Meeting Materials page was that it's easier for
    slide decks arriving late to go missing than for slide decks that
    arrived early.<br>
    <br>
    As I reminded myself while starting to present v4 of the chair
    slides in TSVAREA and realizing that what Martin was projecting was
    v1 (only a day older), getting slidesets nailed down early limits
    the number of times when you're surprised at what's being projected.<br>
    <br>
    I love consolidated slide decks. I bet anyone does, whose laptop
    blue-screened while hooking up to a projector in the late 1990s.
    Nothing good happens during transitions, whether switching laptops
    or switching presentations :-)<br>
    <br>
    None of this should be taken as disagreement with proposals to
    experiment with room shapes, whiteboards, , etc. that I heard last
    week.<br>
    <br>
    None of this should be taken as evidence of love for an unbroken
    stream of presentations of drafts that aren't tied to issues
    discussed on mailing lists, or as disagreement with the idea that
    presentations aren't always the best way to communicate at the
    IETF.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    <br>
    <br>
    Thanks,<br>
    <br>
    Spencer, who also might disagree with some of this when he wakes up
    at a normal hour ... and that hasn't happened yet ...<br>
    <br>
    (*) from <a href="http://www.thefreedictionary.com/Procrustean">http://www.thefreedictionary.com/Procrustean</a>,
    "<span style="color: rgb(0, 0, 0); font-family: Arial; font-size:
      13px; font-style: normal; font-variant: normal; font-weight:
      normal; letter-spacing: normal; line-height: normal; orphans:
      auto; text-align: left; text-indent: 0px; text-transform: none;
      white-space: normal; widows: auto; word-spacing: 0px;
      -webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
      255); display: inline !important; float: none;">producing or
      designed to produce strict conformity by ruthless or arbitrary
      means".</span>
  </body>
</html>

--------------080704040309060501000102--

From rpelletier@isoc.org  Sun Aug  4 16:52:22 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFBF711E810D for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 16:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.738
X-Spam-Level: 
X-Spam-Status: No, score=-101.738 tagged_above=-999 required=5 tests=[AWL=-0.739, BAYES_50=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 xOuqljfX4IjU for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 16:52:17 -0700 (PDT)
Received: from smtp117.iad.emailsrvr.com (smtp117.iad.emailsrvr.com [207.97.245.117]) by ietfa.amsl.com (Postfix) with ESMTP id 5F26F11E8105 for <ietf@ietf.org>; Sun,  4 Aug 2013 16:52:04 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp51.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id E35E8207DF; Sun,  4 Aug 2013 19:51:58 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp51.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 35E13207AD;  Sun,  4 Aug 2013 19:51:57 -0400 (EDT)
Subject: Re: Speaking of VAT
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <alpine.BSF.2.00.1308041746210.2773@joyce.lan>
Date: Mon, 5 Aug 2013 01:51:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F2A42A1-8223-4103-A880-26F19423A510@isoc.org>
References: <20130804201105.3986.qmail@joyce.lan> <65A4EBE4-B342-46B3-82C6-8A81674C3EC0@checkpoint.com> <alpine.BSF.2.00.1308041746210.2773@joyce.lan>
To: "John R Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1085)
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, 04 Aug 2013 23:52:22 -0000

On Aug 4, 2013, at 11:47 PM, John R Levine wrote:

>>> At last week's very successful Berlin meeting, the finances were
>>> thrown of whack by the late discovery that the IETF had to pay 19%
>>> German VAT on the registration fee.  At the IAOC session they said
>>> that about half of that is likely to be reclaimed from VAT paid, but
>>> the net amount is still a large number.
>>=20
>> The usual IANAL and IANAC should not be joined by IANACPA.
>>=20
>> But a CPA at my company said that we couldn't reclaim the VAT, =
because the "service" was consumed in Germany. If others hear different =
from their accounting departments, I'd love to hear about it.
>=20
> Ray said the tax guys told him the IETF would get back about half of =
the VAT it paid.  That's unrelated to what anyone can reclaim.
>=20
> My understanding is that Germany has reciprocal VAT agreements with a =
bunch of countries so if your employer is in one of those countries it =
may be able to reclaim, but since the US isn't one of them I haven't =
looked in detail.

The IAOC posted an FAQ on the subject at: =
<https://www.ietf.org/meeting/87/vat.html>

See the links in the FAQ related to non-European countries that can =
reclaim the VAT.

Ray
IAD

The Google English translation of the list is:

Andorra
Korea, Democratic People's Republic of
Antigua and Barbuda
Korea, Republic of (as of 1 January 1999)
Australia
Croatia (as of 1 January 2010)
Bahamas
Kuwait
Bahrain
Lebanon
Bermuda
Liberia
Bosnia and Herzegovina (1 January 2006)
Libya
British Virgin Islands
Liechtenstein
Brunei Darussalam
Macao
Grand Cayman Island
Maldives
China (Taiwan) (1 July 2010)
Macedonia (from 1 April 2000)
Gibraltar
Netherlands Antilles (30 April 1999)
Grenada
Norway
Greenland
Oman
Guernsey
Pakistan (from 1 July 2008)
Hong Kong (PR China)
Solomon Islands
Iraq
San Marino
Iran
Saudi Arabia
Iceland
Switzerland
Israel (from 14 July 1998)
St. Vincent and the Grenadines
Jamaica
Swaziland
Japan
Vatican
Jersey
United Arab Emirates
Canada
United States of America (USA)
Qatar


>=20
> R's,
> John


From hadriel.kaplan@oracle.com  Sun Aug  4 18:36:47 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461BA21E80C6 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 18:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level: 
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094,  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 p1OeaWaLbfPn for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 18:36:41 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6BA2A21E80C0 for <ietf@ietf.org>; Sun,  4 Aug 2013 18:36:28 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r751aPMg023486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Aug 2013 01:36:26 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r751aOY5014476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Aug 2013 01:36:25 GMT
Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r751aOxZ014473; Mon, 5 Aug 2013 01:36:24 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 04 Aug 2013 18:36:24 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <51FEDF60.2010902@gmail.com>
Date: Sun, 4 Aug 2013 21:36:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <242BB82A-5946-406B-A560-AA9EB6058196@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 01:36:47 -0000

Regarding the need for presentations early to get them translated, and =
the "non-Procrustean"[1] improvement of having cutoffs for presentations =
of new drafts: new drafts are still submitted 2 weeks in advance, and =
ISTM that a real non-Procrustean tactic would be to let the WG chairs do =
their jobs.  If you've got a 40 page slide-deck chock full of text, =
giving a detailed tutorial on some mechanism, it's a different situation =
from the norm. (and I'd argue you're probably doing it wrong, but ymmv)  =
But those appear to be the exceptions, not the rule; and WG chairs can =
handle push-back for exceptions if they need to.  We don't have to =
create new draconian rules.

But for the general case, the truth is that Fuyou Maio is right - you =
really do need to be able to parse English quickly to truly participate =
effectively in an IETF physical meeting.  And you need to be reasonably =
swift in either reading it, or following the speaker's words.  It's not =
nice to say, but it's the truth.  Real-time direct human communication =
is why we have the physical meetings to begin with, instead of only =
mailing lists and virtual meetings. (and for cross-wg-pollination, and =
for cookies)

The good news is the mailing lists and drafts themselves are in plain =
ascii which should make language translation software easier to use, and =
the physical meetings are voice/video/jabber recorded so you can get =
them translated afterwards to listen/watch/read, and once you do you can =
always raise objections/issues in email afterwards and try to reverse =
any decisions made in physical meetings.  That's better than any other =
international standards body I've ever participated in. (IEEE, 3GPP, =
ETSI, ATIS)  Some have a more strict submissions in-advance policy, but =
even for them their physical meetings require high-level English =
abilities to participate effectively, in practice.  I don't see a =
realistic alternative to that, while still getting things accomplished =
in a timely manner.

It's easy to say those things since I'm a native English speaker [2], =
and not a nice concept in general... but if we're honest with ourselves =
I think we have to recognize the unvarnished truth.  Obviously there are =
exceptions - the 40 page slide-deck full of text is an exception.  But =
those appear to be uncommon cases, afaict.

-hadriel
[1] It's ironic you use the word "Procrustean" in an email about =
non-native English speakers needing translation.  If you'd asked me what =
the word meant, I'd have guessed it either meant those who enjoyed the =
edges of bread or pizza, or those who advocate Earth plate tectonics =
theory.

[2] well, technically English is not my native language, but I learned =
it at a young enough age to cover that up... mostly.



On Aug 4, 2013, at 7:10 PM, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:

> On 8/4/2013 3:10 PM, Hadriel Kaplan wrote:
>> OK, I'll bite.  Why do you and Michael believe you need to have the =
slides 1 week in advance?
>>=20
>> You have the agenda and drafts 2 weeks in advance.  The slides aren't =
normative.  Even when they're not about a draft in particular, the =
slides are not self-standing documents.  They're merely to help with =
discussion.
>>=20
>> Not getting the slides at all is a different matter - but 7 days in =
advance is counter-productive.  They should be as up-to-date as =
practical, to take into account mailing list discussions. [or at least =
that's how I justify my same-day, ultra-fresh slides]
>>=20
>> If you need to have them on the website 7 days in advance, you really =
need to get a faster Internet connection. ;)
>>=20
>=20
> I'm a TSV AD, but I'm sending this note wearing no hat (someone last =
week asked me why I wasn't wearing a cowboy hat if I was from Texas - =
no, not even a cowboy hat).
>=20
> I read through the discussion on this, and I'm only responding to =
Hadriel because his post was the last one I saw before replying. Thank =
you all for sharing your thoughts.
>=20
> YMMV ("Your Mileage May Vary"), but I have been sponsored for several =
years by a company that sends a sizable number of folks to IETF who are =
not native English speakers. Having slides early helps non-native =
English speakers (I believe I've heard that some slide decks are =
translated into other languages, although I wouldn't know, because I =
read the slides in English).
>=20
> After his first IETF (Paris/63), Fuyou Maio said to me, "understanding =
spoken English is the short board in the water barrel" (the idea being =
that your effectiveness at the IETF is limited by your ability to =
quickly parse spoken English). The folks I talk to get plenty of chances =
to translate spoken English during Q&A, and don't need additional =
practice translating the presentations in real time. Yes, I know people =
say things that aren't on their slides, but if what's on their slides =
doesn't help other people understand what they are saying, they probably =
shouldn't be using those slides.
>=20
> In the mid-2000s, I remember an admonition for chairs to write out the =
questions the chairs are taking a hum on, to accommodate non-native =
English speakers (and to write out all the questions before taking the =
first hum, to accommodate anyone who agrees with the second choice but =
prefer the fourth choice when they hear it after humming).
>=20
> I'm having a hard time making the "a week early or you don't present" =
case for slide cutoffs, because we DO talk during the meeting week - and =
in groups RTCWeb, with a Thursday slot and a Friday slot, we had time to =
talk a lot. If the cutoff was for presentations of new individual =
drafts, that's a different question, so there might be some way to make =
non-Procrustean improvements(*).
>=20
> I agree with the "chairs looking at slides for sanity" point. I'm =
remembering more than one working group where we chairs got =
presentations that included about a slide per minute for the time =
allocated to the topic - noticing that even one day before saved us from =
the ever-popular "we can't talk about this presentation because we don't =
have time" moment.
>=20
> During IETF 87, I had reason to consult the proceedings for the =
non-workgroup-forming RUTS BOF ("Requirements for Unicast =
Transport/Sessions" at IETF 43, minutes at =
http://www.ietf.org/proceedings/43/43rd-ietf-98dec-142.html#TopOfPage). =
This was the applications-focused wishlist for transport from 1998, when =
COPS, RADIUS, L2TP, HTTP-NG, SIP, NFSv4, SS7, IP Telephony and BGP4 were =
all trying to figure out whether they needed to (continue to, in some =
cases) rely on TCP for transport, or do "something else". I'm =
remembering that there were slides, and I would love to have them to =
refer to, but *none* of the slide decks made it into the proceedings. =
That was pre-Meeting Materials page, but even my experience with the =
Meeting Materials page was that it's easier for slide decks arriving =
late to go missing than for slide decks that arrived early.
>=20
> As I reminded myself while starting to present v4 of the chair slides =
in TSVAREA and realizing that what Martin was projecting was v1 (only a =
day older), getting slidesets nailed down early limits the number of =
times when you're surprised at what's being projected.
>=20
> I love consolidated slide decks. I bet anyone does, whose laptop =
blue-screened while hooking up to a projector in the late 1990s. Nothing =
good happens during transitions, whether switching laptops or switching =
presentations :-)
>=20
> None of this should be taken as disagreement with proposals to =
experiment with room shapes, whiteboards, , etc. that I heard last week.
>=20
> None of this should be taken as evidence of love for an unbroken =
stream of presentations of drafts that aren't tied to issues discussed =
on mailing lists, or as disagreement with the idea that presentations =
aren't always the best way to communicate at the IETF.                   =
                                                         =20
>=20
> Thanks,
>=20
> Spencer, who also might disagree with some of this when he wakes up at =
a normal hour ... and that hasn't happened yet ...
>=20
> (*) from http://www.thefreedictionary.com/Procrustean, "producing or =
designed to produce strict conformity by ruthless or arbitrary means".


From spencerdawkins.ietf@gmail.com  Sun Aug  4 19:36:09 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D83011E811F for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 19:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[AWL=0.048,  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 lTwK9MjASw-8 for <ietf@ietfa.amsl.com>; Sun,  4 Aug 2013 19:36:08 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 284B611E80C5 for <ietf@ietf.org>; Sun,  4 Aug 2013 19:36:08 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id n10so4949814oag.8 for <ietf@ietf.org>; Sun, 04 Aug 2013 19:36:07 -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=Ixw2/mx7/8RU5QcuyBirT4r0o1LeFrfAtCe/ioyNtvQ=; b=agXMblyA2mWd603P6OTEaVSSjS222fJIRMzHTok8o+jv48v0wQ8VFBLW/6OygPUbQT zXZ2m90tj3qwUmA4214Qntg6UUgkze87p7hxMORWn7h6xUlW8VAg2BqB6ZsEoODyWOvT 8UlX6NvPMCgCnSQ5stLxwkobTKp/KyEs2+VrUDIR7z3W9PMhXo/gUzkSVFJelYyPXVKj DVdnPayFDAhspU43Pkay0bEH3+v0o+b4prnKeYvwEepBBHuDLDKMj93qWaRel2A4aDiM 1Vj6BRFwxnZNBMkJ+5aXjAE9yzRuoklqzkndppBENsmjWUozD69WiBju1FymOUkK4YzS Yfvg==
X-Received: by 10.60.83.19 with SMTP id m19mr13061513oey.9.1375670167437; Sun, 04 Aug 2013 19:36:07 -0700 (PDT)
Received: from [192.168.0.23] (173-97-116-174.pools.spcsdns.net. [173.97.116.174]) by mx.google.com with ESMTPSA id mt3sm21887867oeb.1.2013.08.04.19.36.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 04 Aug 2013 19:36:06 -0700 (PDT)
Message-ID: <51FF0F7C.2040503@gmail.com>
Date: Sun, 04 Aug 2013 21:35:40 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com> <242BB82A-5946-406B-A560-AA9EB6058196@oracle.com>
In-Reply-To: <242BB82A-5946-406B-A560-AA9EB6058196@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 02:36:09 -0000

On 8/4/2013 8:36 PM, Hadriel Kaplan wrote:
> Regarding the need for presentations early to get them translated, and the "non-Procrustean"[1] improvement of having cutoffs for presentations of new drafts: new drafts are still submitted 2 weeks in advance, and ISTM that a real non-Procrustean tactic would be to let the WG chairs do their jobs.  If you've got a 40 page slide-deck chock full of text, giving a detailed tutorial on some mechanism, it's a different situation from the norm. (and I'd argue you're probably doing it wrong, but ymmv)  But those appear to be the exceptions, not the rule; and WG chairs can handle push-back for exceptions if they need to.  We don't have to create new draconian rules.

Oh, I wouldn't dream of having rules about that. What I was trying to 
say in my not-enough-sleep-last-week way was that I was imagining so 
many justifiable exceptions (chair slides, on-the-fly hums, reports from 
design teams and hallway conversations the day before) that having rules 
wouldn't help, so, agreed.

> But for the general case, the truth is that Fuyou Maio is right - you really do need to be able to parse English quickly to truly participate effectively in an IETF physical meeting.  And you need to be reasonably swift in either reading it, or following the speaker's words.  It's not nice to say, but it's the truth.  Real-time direct human communication is why we have the physical meetings to begin with, instead of only mailing lists and virtual meetings. (and for cross-wg-pollination, and for cookies)

Right, but Fuyou was talking about *spoken* English being more 
challenging than written English (if you can't *read* English fairly 
quickly, drafts and mailing lists are impenetrable, and you're done in 
the IETF). I'm told that it's easier for non-native English speakers to 
read slides than to parse spoken English for anyone who talks faster 
than I do.

I'm not saying that should override other considerations. I was 
responding to a question several people asked, if anyone would benefit 
from having slides early (for the purposes of this e-mail, 24 hours 
early would be plenty early enough). Other people provided other 
answers, and I hadn't seen that answer go past.

Thanks,

Spencer

p.s. I DID footnote "Procrustean" with a definition, but that's 
perfectly reasonable to point to as "not helpful for non-native English 
speakers" - please feel free to keep me relatively honest.

From randy@psg.com  Mon Aug  5 00:05:17 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D377711E8150 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 00:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4ah3RpMUEiP for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 00:05:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) by ietfa.amsl.com (Postfix) with ESMTP id 82C0011E814F for <ietf@ietf.org>; Mon,  5 Aug 2013 00:05:12 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V6Eqr-00058g-DT; Mon, 05 Aug 2013 07:05:09 +0000
Date: Mon, 05 Aug 2013 09:05:08 +0200
Message-ID: <m2txj439ej.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: 6tsch BoF
In-Reply-To: <CAPv4CP8b6u_6c+vVz9fmmNQJJPF9_j+yH249_fXKF+cERuZwxQ@mail.gmail.com>
References: <81B94276-0050-434D-8451-26068E199CA5@gmail.com> <CABCOCHStZmY8DM-ehNGtM4eMz-qQuKOeAy06y9Hpe5oZ2dTnLg@mail.gmail.com> <B42E4980-1A8C-45C2-8A52-8C9C4955431E@checkpoint.com> <CABCOCHQ14OKAQKrPqsNHBS7abyS8VLTdsQd=USQ4YzN6ot9ipA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077523C63D@mbx-01.win.nominum.com> <6.2.5.6.2.20130801225725.0d388d50@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077524206F@mbx-01.win.nominum.com> <6.2.5.6.2.20130803084319.0c7289b8@resistor.net> <CAC4RtVDo6RhE-i3ipK8YjA6S5+KBQ=iP66opbFS7FEMeKiXoXA@mail.gmail.com> <CAPv4CP8b6u_6c+vVz9fmmNQJJPF9_j+yH249_fXKF+cERuZwxQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 07:05:18 -0000

> What did you think of Pete Resnick's draft about hums.

i like it a lot and have used it in other fora which are somewhat loose
or confused about consensus.

randy

From stpeter@stpeter.im  Mon Aug  5 01:37:34 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1589E21F8EEA for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 01:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.395
X-Spam-Level: 
X-Spam-Status: No, score=-102.395 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbP1zlSqaF9s for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 01:37:28 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B08D721F9D5D for <ietf@ietf.org>; Mon,  5 Aug 2013 01:37:28 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0DFDE40347; Mon,  5 Aug 2013 02:39:57 -0600 (MDT)
Message-ID: <51FF6447.6040005@stpeter.im>
Date: Mon, 05 Aug 2013 02:37:27 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com>
In-Reply-To: <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, "Olle E. Johansson" <oej@edvina.net>, Dan York <york@isoc.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 08:37:34 -0000

On 8/4/13 4:41 PM, Hadriel Kaplan wrote:
> 
> On Aug 3, 2013, at 7:25 PM, John C Klensin <john-ietf@jck.com>
> wrote:
> 
>> First, probably to the "when meetings begin" part, but noting that
>> someone who gets onto the audio a few minutes late is in exactly
>> the same situation as someone who walks into the meeting room a few
>> minutes late -- announcements at the beginning of the session are
>> ineffective.
> 
> Jabber appears to have some way of setting a banner/announcement
> thing that shows up when you first join a jabber session, because
> I've seen such a thing on occasion.  I don't know if it's defined in
> some standard way in XMPP or a proprietary extension.  But assuming
> it's either standard or defacto and popular, we could put the NOTE
> WELL in it (or a URL to a NOTE WELL).
> 
> Likewise for the IETF web pages with the audio links, so that you see
> the NOTE WELL before clicking the audio link.  Or even have an
> annoying pop-up if you prefer. (ugh)

I don't want to promise too much, but in time for Vancouver I'll
probably finish some code that sends you all sorts of helpful
information when you join the jabber room. There is a standardized "room
subject" message but not all IM clients show you that, so I plan to have
it sent as a one-off message when you join the chatroom.

Further discussion, if any, on the tools-discuss@ietf.org list.

Peter

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



From dave@cridland.net  Mon Aug  5 02:08:04 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF96C21F898A for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.544
X-Spam-Level: 
X-Spam-Status: No, score=-1.544 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EwfhSxFIbWNw for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:07:54 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4435921F8640 for <ietf@ietf.org>; Mon,  5 Aug 2013 02:07:30 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id o17so5487860oag.7 for <ietf@ietf.org>; Mon, 05 Aug 2013 02:07:28 -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=uDvOCmT9ovSY5B8acHrf0NqHjIx3+8WlpZ1RYGnqYfs=; b=MCgLh3KVe38qDv8Lmo/9T7b92MpGQHFL8aeHsKsDtW6TPj/CYTGLCWFt+7Vv+dnBK4 H4X2ark7qW0/L3TEfxd9nlTknaYyNA68lcbvasU2ybZEBecFTku6Xf1YSdSlTVTcvk3+ HhXVlOIUT42B2b9pF6dwiNzqO4flqM8zjMPEk=
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=uDvOCmT9ovSY5B8acHrf0NqHjIx3+8WlpZ1RYGnqYfs=; b=XnNC+ajz+7tIVaTmhi3HubYXpG0DxJcfp4g/g+LH2E6pGfPYvpLg64sqqkoyCR3iEs WEuL+q/MHa/5MmHN3jhEpB5qQ9iW1+Y0TIrw5OO/8VrjHBuH1JKnBScC+BdB+YVamp3Y uaBiBx3TvQz4x6jUSfBlB5kTy51c9FQcglWrmpIf5NgfNEoobuNIvEk8fttSVxgi0bqV EtSkm0Xk1yZRvRPhErz+W+uEdUyFACGLNIiuwBPZwxAjoau6BeWHXzxUCAW1w4jcnJLc mHch2Fv8i/7INj9Pqu0DWKdwUk2/YeuR/30g9DnRHTKX/ef8BgzUb0lkbE54k63IyhG5 G7FQ==
MIME-Version: 1.0
X-Received: by 10.60.133.233 with SMTP id pf9mr13729198oeb.46.1375693648681; Mon, 05 Aug 2013 02:07:28 -0700 (PDT)
Received: by 10.60.38.131 with HTTP; Mon, 5 Aug 2013 02:07:28 -0700 (PDT)
In-Reply-To: <51FF6447.6040005@stpeter.im>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com> <51FF6447.6040005@stpeter.im>
Date: Mon, 5 Aug 2013 10:07:28 +0100
Message-ID: <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com>
Subject: Re: procedural question with remote participation
From: Dave Cridland <dave@cridland.net>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=047d7b4720783fee4c04e32fa3ce
X-Gm-Message-State: ALoCoQnQmV/l+6eGuSFYCzU/BM1FPxseVHc/vQ5QPx/cwUwly8O8/RAwuCBxFm7l+TkCybOqHQJ4
Cc: John C Klensin <john-ietf@jck.com>, "Olle E. Johansson" <oej@edvina.net>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Dan York <york@isoc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 09:08:04 -0000
X-List-Received-Date: Mon, 05 Aug 2013 09:08:04 -0000

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

On Mon, Aug 5, 2013 at 9:37 AM, Peter Saint-Andre <stpeter@stpeter.im>wrote:

> I don't want to promise too much, but in time for Vancouver I'll
> probably finish some code that sends you all sorts of helpful
> information when you join the jabber room. There is a standardized "room
> subject" message but not all IM clients show you that, so I plan to have
> it sent as a one-off message when you join the chatroom.
>
> Further discussion, if any, on the tools-discuss@ietf.org list.
>

I'd be happy to help, and will meander toward that list.

One thing for this August Body to consider - we can (quite) easily have new
occupants to the room not be "participants" - in the XEP-0045 sense of the
term. This would mean new occupants would lack voice, and be unable to add
to the discussion - until they've jumped through some hoops.

One such hoop might be acknowledging the (privately sent) Note Well message
(thus equating XEP-0045 Participant with IETF Participant to some degree).
Another might be that we tell them to go away if their XEP-0054 vCard
doesn't include sufficient detail (like their full name and email address,
for example), taking us a step toward remote registration.

Dave.

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

<div dir=3D"ltr">On Mon, Aug 5, 2013 at 9:37 AM, Peter Saint-Andre <span di=
r=3D"ltr">&lt;<a href=3D"mailto:stpeter@stpeter.im" target=3D"_blank">stpet=
er@stpeter.im</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im"><span style=3D"color:rgb(34,34,34)">I do=
n&#39;t want to promise too much, but in time for Vancouver I&#39;ll</span>=
<br>
</div>
probably finish some code that sends you all sorts of helpful<br>
information when you join the jabber room. There is a standardized &quot;ro=
om<br>
subject&quot; message but not all IM clients show you that, so I plan to ha=
ve<br>
it sent as a one-off message when you join the chatroom.<br>
<br>
Further discussion, if any, on the <a href=3D"mailto:tools-discuss@ietf.org=
">tools-discuss@ietf.org</a> list.<br></blockquote><div><br></div><div>I&#3=
9;d be happy to help, and will meander toward that list.</div><div><br></di=
v>
<div>One thing for this August Body to consider - we can (quite) easily hav=
e new occupants to the room not be &quot;participants&quot; - in the XEP-00=
45 sense of the term. This would mean new occupants would lack voice, and b=
e unable to add to the discussion - until they&#39;ve jumped through some h=
oops.</div>
<div><br></div><div>One such hoop might be acknowledging the (privately sen=
t) Note Well message (thus equating XEP-0045 Participant with IETF Particip=
ant to some degree). Another might be that we tell them to go away if their=
 XEP-0054 vCard doesn&#39;t include sufficient detail (like their full name=
 and email address, for example), taking us a step toward remote registrati=
on.</div>
<div><br></div><div>Dave.</div></div></div></div>

--047d7b4720783fee4c04e32fa3ce--

From stephen.farrell@cs.tcd.ie  Mon Aug  5 02:30:09 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E81A21F9CA8 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.98
X-Spam-Level: 
X-Spam-Status: No, score=-101.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eI+gO-FF+pqA for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:30:01 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4C76F21F994C for <ietf@ietf.org>; Mon,  5 Aug 2013 02:29:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 96119BE50; Mon,  5 Aug 2013 10:28:55 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mx59sIrdxabP; Mon,  5 Aug 2013 10:28:50 +0100 (IST)
Received: from [10.0.4.107] (unknown [89.246.150.136]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7167DBE29; Mon,  5 Aug 2013 10:28:49 +0100 (IST)
Message-ID: <51FF7050.7060606@cs.tcd.ie>
Date: Mon, 05 Aug 2013 10:28:48 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com> <51FF6447.6040005@stpeter.im> <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com>
In-Reply-To: <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Dan York <york@isoc.org>, "Olle E. Johansson" <oej@edvina.net>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 09:30:10 -0000

On 08/05/2013 10:07 AM, Dave Cridland wrote:
> One such hoop might be acknowledging the (privately sent) Note Well message
> (thus equating XEP-0045 Participant with IETF Participant to some degree).
> Another might be that we tell them to go away if their XEP-0054 vCard
> doesn't include sufficient detail (like their full name and email address,
> for example), taking us a step toward remote registration.

I hope folks who invest effort in tooling try to make it all
easier and not harder. Right now we don't have good tools that
allow remote folks to easily provide "live" input (and maybe
that's just because its a hard problem). So I'd say we should
keep trying to make that better and not worry yet about how to
control abuse of what's not currently usable.

On 08/04/2013 11:41 PM, Hadriel Kaplan wrote:
> And have separate rooms that require registering, like
> "[wg-name]@members.ietf.org" or whatever,

We don't have, nor (I believe) do we want, "members." And we do
want good technical input regardless of source. About the only
reason to try control that via registration is due to patent
nonsense. That is (unfortunately) a real reason, and we do have
to take it into account, but please let's all bear in mind that
99% of those patents are total crap (regardless of country afaik)
and let's not be driven by the stupidity but rather let's put
that in its proper place as a regrettable cost of being open.

Sorry to go on about that, but I don't think onerous registration
schemes are really needed to e.g. do floor control. And since the
former ("registration" stuff) is easy, and the latter (esp. with
remote audio input in our environment) is not, we might easily end
up doing the easy thing, and making it all worse.

Cheers,
S.



From sm@resistor.net  Mon Aug  5 02:35:57 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7A1B21F9048 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25INVPl6SgQc for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:35: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 059F521F8640 for <ietf@ietf.org>; Mon,  5 Aug 2013 02:33:37 -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 r759UoLj018165; Mon, 5 Aug 2013 02:30:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1375695056; bh=NxqfRdfaVYSt4hxDQd+z7VBoKorCNBE+wusBJgsSFUU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3+Idl+OJRIPxx2a00N10uynjMsO2fUd8zX3IVKMAS5iZxTL7QVCzleecYG4CVlsN7 M3/O16R6YiAJAkbcc9KpALYHy61XbqPT9h/GI+MoZJyRme+3TaK9nIemYt2KCFwZ5X 2PWtsgLt2P2srkzsLKopqlEjwRFoQYVda+6jF4So=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1375695056; i=@resistor.net; bh=NxqfRdfaVYSt4hxDQd+z7VBoKorCNBE+wusBJgsSFUU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=wIC1aDHGpaQgIygBMDK4HzuOCDl6mazaHeVLuho8PhlqtVWRkBVDMr8RwyjktOHiB VUyR9TE8GVud0K3ZaDy9yCXmNhjGD6ODwGyD6ZDEql0c6I7MxSTTe09XTbw/lwrh99 1MNtsKQyhNPhaTz4OA3KlBRCg6qIDPcyoJ0gfkUg=
Message-Id: <6.2.5.6.2.20130805002145.0bb83420@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 05 Aug 2013 02:26:57 -0700
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: SM <sm@resistor.net>
Subject: Re: procedural question with remote participation
In-Reply-To: <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 09:35:57 -0000

At 13:10 04-08-2013, Hadriel Kaplan wrote:
>OK, I'll bite.  Why do you and Michael believe you need to have the 
>slides 1 week in advance?

One generation's bad behavior becomes the next generation's best 
practice.  It would be appreciated if those slides could be made 
available in advance.

>You have the agenda and drafts 2 weeks in advance.  The slides 
>aren't normative.  Even

I do not have the agenda two weeks in advance.

Nowadays, there are "if time permits" slots in addition to A.O.B.

What is the meaning of "normative" in the above?

>If you need to have them on the website 7 days in advance, you 
>really need to get a faster Internet connection. ;)

Ok. :-)

At 14:27 04-08-2013, Hadriel Kaplan wrote:
>What *would* be good to have 7 days or more in advance are the 
>Technical and O&A Plenary slides.  They shouldn't be changing, 
>afaict.  And that way we can figure out if we can have those nights 
>free for other things, or if it's worth going to the Plenaries 
>instead.  But I assume those slides already are made available well 
>in advance. (right?)

The Technical and other Plenary slides are not made available well in 
advance.  Someone asked the following question:

   "Does she have a clue that she just asked for feedback from an audience
    that can't see the link she put on the screen?"

There was a discussion about beer from the tap after that.  Please 
open a new thread if you would like to discuss about that. :-)

At 15:21 04-08-2013, Stephen Farrell wrote:
>And only something potentially disastrous ought imply even considering
>a zero-tolerance anything in a volunteer organisation.

It is after all a volunteer organisation.  I hope that people were 
not surprised that I did not ask for the Spice Girls session to be cancelled.

At 15:41 04-08-2013, Hadriel Kaplan wrote:
>Do you find this is an actual problem in WG meetings?  Are the 
>jabber scribes not able to tell you who is at the mic if you ask 
>them?  People have forgotten to state their names

Some of the Jabber scribes are not able to tell me who are at the 
microphone when I ask them.  If it was my decision to make (and it is 
not), the Jabber scribe would be allowed to comment at the microphone 
even after the microphone line is capped.  A person can always argue 
that it is an arbitrary decision.  :-)

As an off-topic comment, it's not because the Meetecho people are 
nice that one should expect them to act as Jabber scribes.

At 18:36 04-08-2013, Hadriel Kaplan wrote:
>But for the general case, the truth is that Fuyou Maio is right - 
>you really do need to be able to parse English quickly to truly 
>participate effectively in an IETF physical meeting.  And you need 
>to be reasonably swift in either reading it, or following the 
>speaker's words.  It's not nice to
>  say, but it's the truth.  Real-time direct human communication is 
> why we have the physical meetings to begin with, instead of only 
> mailing lists and virtual meetings. (and for cross-wg-pollination, 
> and for cookies)

Yes.

Some sessions are easy to follow.  For example, I read some slides 
posted a few days before and I had an idea of what would be 
discussed.  I looked for the slides for a BoF as it was not clear to 
me what one of these items on the agenda was about.  The slides were 
not available.  I didn't bother asking about them.  The correct 
question would have been about the item on the agenda instead of the slides.

Regards,
-sm 


From scott.brim@gmail.com  Mon Aug  5 02:40:54 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B9C821F9E1D for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:40: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=[AWL=-0.000, 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 aZzHIK6DCPg3 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 02:40:53 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2C92721F8411 for <ietf@ietf.org>; Mon,  5 Aug 2013 02:39:17 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id h1so5795018oag.10 for <ietf@ietf.org>; Mon, 05 Aug 2013 02:38:55 -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=PnT3quR50c8A0eZOEE1YHdLDXwNaTTGSSBn/Fc8U3vc=; b=ZHwMSzK6EDcbodmDXbLJXXgFa0NJC6Nw3lN1o8pZEcv+yXAOfyEcZXvytrC+bwbfvG ABb5BJoMLlTasHSa0DZ7C6Qm0smKA1vhbVDkiJ0q7e0ImH3kCBzhOH8JIKMXpU/rV2lZ N2O9XmEOfqB7ojf94kdKCIbQNc6pDZbFB+gNtotZDIstZut2h0x/PdrPJ8nMFSMMLofv tlZn+/fB4n3F7UHaSpDgFKFGzrzxSxUUBk9g1/pNARuoDMerjER7V9xMrFxAGaOlnxRu N+95WGK9mhnKGCEVJ4peHz0DuMP8/UwjdPNqdMchUrWgZNDlPuArBXhowUqi4cyksZlK bBjQ==
MIME-Version: 1.0
X-Received: by 10.60.135.167 with SMTP id pt7mr13773213oeb.59.1375695535375; Mon, 05 Aug 2013 02:38:55 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Mon, 5 Aug 2013 02:38:55 -0700 (PDT)
Received: by 10.182.44.105 with HTTP; Mon, 5 Aug 2013 02:38:55 -0700 (PDT)
In-Reply-To: <51FF0F7C.2040503@gmail.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@192.168.1.128> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com> <242BB82A-5946-406B-A560-AA9EB6058196@oracle.com> <51FF0F7C.2040503@gmail.com>
Date: Mon, 5 Aug 2013 05:38:55 -0400
Message-ID: <CAPv4CP8ZEUTTdk0ToYohxTFTfWDDQiBu1c27f3TJAyrA_Hy38A@mail.gmail.com>
Subject: Re: procedural question with remote participation
From: Scott Brim <scott.brim@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b3a849cb48da004e33013eb
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, 05 Aug 2013 09:40:55 -0000

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

> Right, but Fuyou was talking about *spoken* English being more
challenging than written English (if you can't *read* English fairly
quickly, drafts and mailing lists are impenetrable, and you're done in the
IETF). I'm told that it's easier for non-native English speakers to read
slides than to parse spoken English for anyone who talks faster than I do.

Aside: this is yet another reason why a really thorough jabber scribe is
useful.

swb

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

<p dir=3D"ltr">&gt; Right, but Fuyou was talking about *spoken* English bei=
ng more challenging than written English (if you can&#39;t *read* English f=
airly quickly, drafts and mailing lists are impenetrable, and you&#39;re do=
ne in the IETF). I&#39;m told that it&#39;s easier for non-native English s=
peakers to read slides than to parse spoken English for anyone who talks fa=
ster than I do.</p>

<p dir=3D"ltr">Aside: this is yet another reason why a really thorough jabb=
er scribe is useful.=A0 </p>
<p dir=3D"ltr">swb </p>

--047d7b3a849cb48da004e33013eb--

From ad707@hermes.cam.ac.uk  Mon Aug  5 03:14:49 2013
Return-Path: <ad707@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5E721F969F for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 03:14:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfgtHiyBl9Hk for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 03:14:47 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f52]) by ietfa.amsl.com (Postfix) with ESMTP id D50A021F9048 for <ietf@ietf.org>; Mon,  5 Aug 2013 03:14:45 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:49705) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:ad707) id 1V6HoK-0006rs-ET (Exim 4.80_167-5a66dd3) (return-path <ad707@hermes.cam.ac.uk>); Mon, 05 Aug 2013 11:14:44 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:ad707) id 1V6HoK-0005Tu-E0 (Exim 4.72) (return-path <ad707@hermes.cam.ac.uk>); Mon, 05 Aug 2013 11:14:44 +0100
Received: from [128.232.100.175] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.5); 05 Aug 2013 11:14:44 +0100
Date: 05 Aug 2013 11:14:44 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: scott.brim@gmail.com
Subject: Re: procedural question with remote participation
Message-ID: <Prayer.1.3.5.1308051114440.16776@hermes-2.csi.cam.ac.uk>
X-Mailer: Prayer v1.3.5
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Sender: Aaron Yi DING <ad707@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 10:14:49 -0000

On 05/08/13 10:38, Scott Brim wrote:
>
> > Right, but Fuyou was talking about *spoken* English being more 
> > challenging than written English (if you can't *read* English fairly 
> > quickly, drafts and mailing lists are impenetrable, and you're done in 
> > the IETF). I'm told that it's easier for non-native English speakers to 
> > read slides than to parse spoken English for anyone who talks faster 
> > than I do.
>


don't forget there are accents as well which make the parsing challenging 
even more :)

Aaron


> Aside: this is yet another reason why a really thorough jabber scribe is 
> useful.


PS: good ones normally don't have time, and random volunteers may not meet 
your expectation. sign..


>
> swb

From olaf@NLnetLabs.nl  Mon Aug  5 04:08:52 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32FF621F9E80 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JZVj+3UKuCRR for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:08:51 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3782E21F8C93 for <ietf@ietf.org>; Mon,  5 Aug 2013 04:08:50 -0700 (PDT)
Received: from [IPv6:2001:7b8:206:1:7211:24ff:fe8c:627a] ([IPv6:2001:7b8:206:1:7211:24ff:fe8c:627a]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r75B8kYK095598 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 5 Aug 2013 13:08:47 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.3 open.nlnetlabs.nl r75B8kYK095598
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1375700928; bh=91p558gISk7OhwH88hpdQ/EglFmnVTdHxg/4D5GODvQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=AoNk4Ox9n8c5fvUqX5qwkuzesvw6It/O16xkY+ZxO7AauKk2FrjuIned2ljLR90gI zdk0UpSJV76I29SsZ4ocM+1LWtzrBszr7aIRpYL6qbyCg0BKs6Waeen1xRKLBM/a/s 4AnqLHJM1AjbyvzaXqiVfriZ+arioxi/anOtdtyA=
Content-Type: multipart/signed; boundary="Apple-Mail=_1626C7A1-D940-4CF0-AA14-8A81C6A0605B"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>
Date: Mon, 5 Aug 2013 13:08:46 +0200
Message-Id: <2681ABBB-DDC3-48DE-A6B3-29771701AF05@NLnetLabs.nl>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>
To: Chris Griffiths <cgriffiths@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]); Mon, 05 Aug 2013 13:08:48 +0200 (CEST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 11:08:52 -0000

--Apple-Mail=_1626C7A1-D940-4CF0-AA14-8A81C6A0605B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 3, 2013, at 8:48 AM, Chris Griffiths <cgriffiths@gmail.com> =
wrote:

> IETF Community,
>=20
> The IETF Trust Trustees would like feedback from the community on =
several issues:
> 	- We have received requests that we cannot accommodate and have =
consulted legal counsel to review our options
> 	- The trust agreement does not allow the trustees to effectively =
manage some trust assets=20

=46rom this mail it is not clear what type of feedback you are looking =
for. I like your direct question from the slide deck better. There you =
asked:
> Does the community feel these are reasonable reasons to update the =
trust agreement?=20

The answer to that question is: yes. It seems reasonable to open up the =
agreement in order to fulfill its purpose in reasonable, effective, and =
pragmatic ways.

I would expect the trust to come back with a proposal once there seems =
to be consensus that the the agreement should be opened. My requirement =
would be that that proposal reflects that the Trust will deal with the =
assets in a way that is sensible and serves community needs.

Best, and thanks,

--Olaf

PS. As an aside, something that might be helpful for other readers of =
this thread: The word agreement in "Trust Agreement" might be confusing =
to the community, but I think that it is important to point out that the =
agreement can, since July 1, 2010, be modified unilaterally by the trust =
(see 10.1 for details and boundary conditions).  So except the due =
diligence that is needed to reflect the communities requirements there =
is no further negotiation needed with the Settlers.




--Apple-Mail=_1626C7A1-D940-4CF0-AA14-8A81C6A0605B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQIcBAEBAgAGBQJR/4e+AAoJEFRqER47aqpkhUMP/0BtkKhiFVmqHuS8W7riFBuV
OEdoJ4dtv4UkLNxtvJ61Vi8RpB9Ef6rJKUydqTWq13lRkRVJ0PdELkNHp14huFI2
toNfrP0hDFTqAHwQlqGHjUTjhW0accMGgQtJzvcvV0ze7bDSi4xib/1X1ZpnorU9
pMWn4fU2ZuWv20IP+yLcfWLXqAqy7lhnf2H59HkZZF2rvSSwOklISsUJhrX0XpEV
5VmI3Ufl0+3G/ItIta+KvG1OasfyLbP4SFq7DwZX8rkHhYTz9Ko7RdcDRgmNr6fJ
oN5uomc5GSN+lmEPjcqKI3ZLWGu0Bu2QKDwCnF//Wv0F1djAVw6zJc72uFEtWLIb
B/SEx1B8ZNDwz12ELk1HWSRV2vCcKNl7WXwPhUTn+JCk5Ayz7wyW1JeQlFomxnkU
5o9ROXhwI6xjU2xabuMd+rU/hN3ne8YMkYb4AWrdwgybcr94bgNoKw+Ls4QsrKft
CFEQF1d2Wc7ns5uW752aq3G6H83CfiSi+xA9ueVR8xfE2nAUqYwkcPXOVM0bskCL
8lpDhjRKRe76g3MPK9Z3TPAT/XSjuhHL1c04tD6qWzH5NeuuM9PD4T/LfRZnpzAI
HxffGR8zrE+qMLeEB0hD5SEt+cDc70d/gFW5ADBWWyG44Dy8JlBd3Lr0rvfpswiw
UjUUjX+Kn2sxIuQo3WJT
=bitZ
-----END PGP SIGNATURE-----

--Apple-Mail=_1626C7A1-D940-4CF0-AA14-8A81C6A0605B--

From spencerdawkins.ietf@gmail.com  Mon Aug  5 04:30:48 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA9621F9E77 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:30: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=[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 yBnjtYt33bVq for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:30:44 -0700 (PDT)
Received: from mail-ea0-x234.google.com (mail-ea0-x234.google.com [IPv6:2a00:1450:4013:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 2A04921F9A14 for <ietf@ietf.org>; Mon,  5 Aug 2013 04:30:44 -0700 (PDT)
Received: by mail-ea0-f180.google.com with SMTP id h10so1564329eaj.39 for <ietf@ietf.org>; Mon, 05 Aug 2013 04:30: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=0w7mcBGdD7MiKEIbe9sQHN519YSW455xbVXVNaEF0IY=; b=KyOXLs56Jr8P3YaW/Orw85WRRUhXvK2vubwzyK7iKKirljwypcwS3Vl1NPU29Cmifw uGMOwCiHM25I9vflK8uDukAAvjKZkAbwzNk7p/XHLakb60WZsx7kbsl3vVkuGHtK18v2 wzyUbVloQUyQoXC/MA6/0TLqpWrVudGLZ/M4VTTJ5iTy7cj9+5PNzlkC/OOy2SuoBhHL bbrkCWMRbvounzHSMbYIJq110WTqM/rrBx84pflhi8X+ByUQo2NizniNmZ6pdxV/svDM 38TNouBXoUFkkmOIhTvjVz0Te6aJ2HLsqVVtcK58NxMBlQ5gSdRj43gNXx8GNveyfv6s cv0Q==
MIME-Version: 1.0
X-Received: by 10.15.74.199 with SMTP id j47mr16273719eey.154.1375702236367; Mon, 05 Aug 2013 04:30:36 -0700 (PDT)
Received: by 10.223.197.72 with HTTP; Mon, 5 Aug 2013 04:30:36 -0700 (PDT)
In-Reply-To: <Prayer.1.3.5.1308051114440.16776@hermes-2.csi.cam.ac.uk>
References: <Prayer.1.3.5.1308051114440.16776@hermes-2.csi.cam.ac.uk>
Date: Mon, 5 Aug 2013 06:30:36 -0500
Message-ID: <CAKKJt-cGXsk0u+Cnor_BnSdBPf+ae7jKtsZg=ZzgFS9kuJwrVA@mail.gmail.com>
Subject: Re: [87attendees] procedural question with remote participation
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
Content-Type: multipart/alternative; boundary=001a11c3876e1dad8a04e331a33b
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, 05 Aug 2013 11:30:48 -0000

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

On Monday, August 5, 2013, Aaron Yi DING wrote:

> On 05/08/13 10:38, Scott Brim wrote:
>
>>
>> > Right, but Fuyou was talking about *spoken* English being more >
>> challenging than written English (if you can't *read* English fairly >
>> quickly, drafts and mailing lists are impenetrable, and you're done in >
>> the IETF). I'm told that it's easier for non-native English speakers to >
>> read slides than to parse spoken English for anyone who talks faster > than
>> I do.
>>
>>
>
> don't forget there are accents as well which make the parsing challenging
> even more challenging.
>

When I have talked to non-native English speakers at the IETF newcomers
tutorial, pointing out that many of the speakers they're working to
understand are also not not native English speakers often turns out to be
encouraging. ...

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

<br><br>On Monday, August 5, 2013, Aaron Yi DING  wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">On 05/08/13 10:38, Scott Brim wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&gt; Right, but Fuyou was talking about *spoken* English being more &gt; ch=
allenging than written English (if you can&#39;t *read* English fairly &gt;=
 quickly, drafts and mailing lists are impenetrable, and you&#39;re done in=
 &gt; the IETF). I&#39;m told that it&#39;s easier for non-native English s=
peakers to &gt; read slides than to parse spoken English for anyone who tal=
ks faster &gt; than I do.<br>

<br>
</blockquote>
<br>
<br>
don&#39;t forget there are accents as well which make the parsing challengi=
ng even more challenging.<br>
</blockquote><div><br></div><div>When I have talked to=A0non-native English=
 speakers at the IETF newcomers tutorial<span></span>, pointing out that ma=
ny of the speakers they&#39;re working to understand are also not not nativ=
e English speakers often turns out to be encouraging. ...=A0<br>
</div>

--001a11c3876e1dad8a04e331a33b--

From hadriel.kaplan@oracle.com  Mon Aug  5 04:32:15 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28DC121F9E9E for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 vgnl2SRZvPVq for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:32:09 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 47D0E21F9E80 for <ietf@ietf.org>; Mon,  5 Aug 2013 04:32:09 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r75BW1uP001307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Aug 2013 11:32:02 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r75BVvQq002662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Aug 2013 11:31:58 GMT
Received: from abhmt119.oracle.com (abhmt119.oracle.com [141.146.116.71]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r75BVviT014081; Mon, 5 Aug 2013 11:31:57 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 05 Aug 2013 04:31:57 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <51FF7050.7060606@cs.tcd.ie>
Date: Mon, 5 Aug 2013 07:31:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D49ADBED-B7C1-4101-B27F-C78125D1BB9A@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com> <51FF6447.6040005@stpeter.im> <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com> <51FF7050.7060606@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 11:32:15 -0000

On Aug 5, 2013, at 5:28 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:

> I hope folks who invest effort in tooling try to make it all
> easier and not harder. Right now we don't have good tools that
> allow remote folks to easily provide "live" input (and maybe
> that's just because its a hard problem). So I'd say we should
> keep trying to make that better and not worry yet about how to
> control abuse of what's not currently usable.

Yup, afaict we were doing ok until IETF 87... but at least one anonymous =
jabber participant (named "Guest") did remotely speak multiple times at =
the mic on one of the RAI working group sessions this past week (at =
RTCWEB if I recall).  I was personally ok with it, but it was awkward.  =
If folks feel it's inappropriate, then we need something else.  I'd be =
ok with just having jabber scribes ignore anonymous participants.


> On 08/04/2013 11:41 PM, Hadriel Kaplan wrote:
>> And have separate rooms that require registering, like
>> "[wg-name]@members.ietf.org" or whatever,
>=20
> We don't have, nor (I believe) do we want, "members."

Yeah, "members.ietf.org" was a poor choice of domain name.  I wasn't =
making a formal proposal - just thinking out loud.  I'd be happier if =
the tools team figures out something simpler and less onerous anyway.  I =
was just noting it's not an impossible task to accomplish, some way or =
other.


> And we do
> want good technical input regardless of source. About the only
> reason to try control that via registration is due to patent
> nonsense. That is (unfortunately) a real reason, and we do have
> to take it into account, but please let's all bear in mind that
> 99% of those patents are total crap (regardless of country afaik)
> and let's not be driven by the stupidity but rather let's put
> that in its proper place as a regrettable cost of being open.

Amen to that!

-hadriel


From scott.brim@gmail.com  Mon Aug  5 04:44:17 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7498F21F9E9F for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QTiw65s1cWJm for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:44:14 -0700 (PDT)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 950CD21F8CB4 for <ietf@ietf.org>; Mon,  5 Aug 2013 04:43:48 -0700 (PDT)
Received: by mail-qa0-f42.google.com with SMTP id bv4so894814qab.15 for <ietf@ietf.org>; Mon, 05 Aug 2013 04:43:48 -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:x-enigmail-version:content-type :content-transfer-encoding; bh=KclE42JLMOCnPXb6u91J+uU0yn0atKNGPCp5u95M5vQ=; b=JgwOEbkyiIivYiU/PCjL0CJj7s6ZQOBHwrXVr0ZusXna1oXAAH3sJRSfunizQMQea/ 9R/5iPcxhQTc4/2RqxISYZcaznypYIPwbzt+GGu6ndUT9xD4yoGFe50mckaCVln686qm lhZOJMU8l8UUAEMR4xrSrZ+A8v01bBHXcvj+MraxsdQOOEI82o/gDsKaNND62keMBTLU WSY5Ch6qIMpuc2ZPETgYmfwFJRngSAe7zVxprwNz5YiIrz79WI2HFHpBnS2CfPwU/ccL xAArKMDy8XWQlb0X9RnHFItlc8dPgpmpZxcZsbWlyF0Xh10yvoPF17C5Xpyo8slxfRAJ RoZQ==
X-Received: by 10.224.64.202 with SMTP id f10mr28176069qai.6.1375703028020; Mon, 05 Aug 2013 04:43:48 -0700 (PDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com. [67.241.75.185]) by mx.google.com with ESMTPSA id y1sm2763809qaj.2.2013.08.05.04.43.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 04:43:47 -0700 (PDT)
Message-ID: <51FF8FF2.3010501@gmail.com>
Date: Mon, 05 Aug 2013 07:43:46 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com> <51FF6447.6040005@stpeter.im> <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com> <51FF7050.7060606@cs.tcd.ie> <D49ADBED-B7C1-4101-B27F-C78125D1BB9A@oracle.com>
In-Reply-To: <D49ADBED-B7C1-4101-B27F-C78125D1BB9A@oracle.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 11:44:17 -0000

On 08/05/13 07:31, Hadriel Kaplan allegedly wrote:
> Yup, afaict we were doing ok until IETF 87... but at least one anonymous jabber participant (named "Guest") did remotely speak multiple times at the mic on one of the RAI working group sessions this past week (at RTCWEB if I recall).  I was personally ok with it, but it was awkward.  If folks feel it's inappropriate, then we need something else.  I'd be ok with just having jabber scribes ignore anonymous participants.

It's inappropriate. Tell them they need to provide at least a name.


From ynir@checkpoint.com  Mon Aug  5 04:52:05 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4072E21F9EB8 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.506
X-Spam-Level: 
X-Spam-Status: No, score=-10.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 agq8XTrrXE4P for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:51:58 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7005B21F9EB6 for <ietf@ietf.org>; Mon,  5 Aug 2013 04:51:49 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r75Bpa29018342; Mon, 5 Aug 2013 14:51:36 +0300
X-CheckPoint: {51FF91C8-10-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Mon, 5 Aug 2013 14:51:36 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: procedural question with remote participation
Thread-Topic: procedural question with remote participation
Thread-Index: AQHOkKDYYJz6DCbfgE+z5E8wvm6A4JmFdA6AgACmbYCAAAhjAIAABfYAgAAiZoCAAANPAIAAAjEA
Date: Mon, 5 Aug 2013 11:51:36 +0000
Message-ID: <5BBF9797-5CBF-41C7-A7CE-E9F28BD08FE9@checkpoint.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com> <51FF6447.6040005@stpeter.im> <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com> <51FF7050.7060606@cs.tcd.ie> <D49ADBED-B7C1-4101-B27F-C78125D1BB9A@oracle.com> <51FF8FF2.3010501@gmail.com>
In-Reply-To: <51FF8FF2.3010501@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.1]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11bfdd80eb6bab9c46a506ee58952f696b33ae7512
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CFBE8AAE20B28247AA740B22B6237C2C@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 11:52:05 -0000

On Aug 5, 2013, at 2:43 PM, Scott Brim <scott.brim@gmail.com> wrote:

> On 08/05/13 07:31, Hadriel Kaplan allegedly wrote:
>> Yup, afaict we were doing ok until IETF 87... but at least one anonymous=
 jabber participant (named "Guest") did remotely speak multiple times at th=
e mic on one of the RAI working group sessions this past week (at RTCWEB if=
 I recall).  I was personally ok with it, but it was awkward.  If folks fee=
l it's inappropriate, then we need something else.  I'd be ok with just hav=
ing jabber scribes ignore anonymous participants.
>=20
> It's inappropriate. Tell them they need to provide at least a name.
>=20

Would it be better if they were called "Emma" instead of "Guest" ?


From scott.brim@gmail.com  Mon Aug  5 04:56:00 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2153321F9CF8 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:55: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=[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 rbmbMJ2p+55x for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 04:55:58 -0700 (PDT)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id C25A521F9D2A for <ietf@ietf.org>; Mon,  5 Aug 2013 04:55:44 -0700 (PDT)
Received: by mail-qa0-f49.google.com with SMTP id cr7so894586qab.8 for <ietf@ietf.org>; Mon, 05 Aug 2013 04:55:43 -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:x-enigmail-version:content-type :content-transfer-encoding; bh=KDx302l7tv972ovGOWSadvnRvKaABpxVBNaVCfNmCuc=; b=zK+utyhZwJQ4y4nrXvhvwylcj47pnwVHl580hrQsury3HusqvUup70dSnUuxuJhTzF Ky9qGC/nHooAQcROGgG1nbfAKvxpmW8VYk4hTK2I/vK5HERmQrPQdMnHCMG1QpJjYRxz 36IrCEoP0eVCOEu57wPuLrn4R+X0spmb2g08zPGM8Lc0o+mPbi25jUr7BPSojILrZl9L M108n4ibqQhRoCp8MOJrHULGp4hj9RxDdXWXlWmUMfFIidS1Et59xurxCEDE3j2rd1ph q0rUJhIOH2RGZYsGJnHTuslm0s6PfCmBsUsP/Xcr0uZWFmjJOO3UNt41c50METvCPQ1J /heA==
X-Received: by 10.229.48.9 with SMTP id p9mr79980qcf.68.1375703743257; Mon, 05 Aug 2013 04:55:43 -0700 (PDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com. [67.241.75.185]) by mx.google.com with ESMTPSA id i1sm2796236qas.10.2013.08.05.04.55.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 04:55:42 -0700 (PDT)
Message-ID: <51FF92BD.7070006@gmail.com>
Date: Mon, 05 Aug 2013 07:55:41 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@192.168.1.128> <55ED2A76-7900-4288-981E-0B67E1D4F8FA@oracle.com> <51FF6447.6040005@stpeter.im> <CAKHUCzwa23JDYtQd_g1gxG_RdbshkqwpMsXT7oXkvRbPoGZcVw@mail.gmail.com> <51FF7050.7060606@cs.tcd.ie> <D49ADBED-B7C1-4101-B27F-C78125D1BB9A@oracle.com> <51FF8FF2.3010501@gmail.com> <5BBF9797-5CBF-41C7-A7CE-E9F28BD08FE9@checkpoint.com>
In-Reply-To: <5BBF9797-5CBF-41C7-A7CE-E9F28BD08FE9@checkpoint.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 11:56:00 -0000

On 08/05/13 07:51, Yoav Nir allegedly wrote:
> 
> On Aug 5, 2013, at 2:43 PM, Scott Brim <scott.brim@gmail.com> wrote:
> 
>> On 08/05/13 07:31, Hadriel Kaplan allegedly wrote:
>>> Yup, afaict we were doing ok until IETF 87... but at least one anonymous jabber participant (named "Guest") did remotely speak multiple times at the mic on one of the RAI working group sessions this past week (at RTCWEB if I recall).  I was personally ok with it, but it was awkward.  If folks feel it's inappropriate, then we need something else.  I'd be ok with just having jabber scribes ignore anonymous participants.
>>
>> It's inappropriate. Tell them they need to provide at least a name.
>>
> 
> Would it be better if they were called "Emma" instead of "Guest" ?
> 

Yes.  Ask lawyers.

From abdussalambaryun@gmail.com  Mon Aug  5 05:03:21 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B96921F9E99 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599, 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 JVI9gMYC7r5r for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:03:20 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4344A21F9E37 for <ietf@ietf.org>; Mon,  5 Aug 2013 05:03:20 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so3250707pbc.31 for <ietf@ietf.org>; Mon, 05 Aug 2013 05:03:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2OSTGVlvyEo3NAaWy+3BGEOZTHYNNbkP/FFijT0VFFY=; b=JK1M4YBJtHcnrpu6r/R19w6suHFTgEmEoxy2t3dLHcdZlqufemu16mhTqQbAeHyXh4 vI7rEyNdSwvjA+JSbiV4IR9Q0O+q+T2DKFa5kK0RmlnHtqnRVV+92TkuWZk4IQmB1B+1 cgt4n6Ic9uh+Aq+iSqqg9Kn0rGZWxjn61XaE1yJ9KX1YGW6SfUFIiwd7oIS8uWG6nAn6 BKjahrWTZR68Hzg29IfIkextPJRoq+8d1irEQgevKexFCH8MasK3bEDGLd8WuYxSsk+s lrPNlGOuGeYCkMHdOoTGx7W5JbJJpj39KUUvBawXS3deI2U5dPzixdkrs+PsF+6iunAX nriA==
MIME-Version: 1.0
X-Received: by 10.66.254.41 with SMTP id af9mr21472038pad.174.1375704200003; Mon, 05 Aug 2013 05:03:20 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Mon, 5 Aug 2013 05:03:19 -0700 (PDT)
In-Reply-To: <8C1E4FC360C0F4D07C51298A@192.168.1.128>
References: <20130804195342.3851.qmail@joyce.lan> <8C1E4FC360C0F4D07C51298A@192.168.1.128>
Date: Mon, 5 Aug 2013 13:03:19 +0100
Message-ID: <CADnDZ8-z=UQyfdxt-kkFLx1t1kiu_BLkaRQ3jznDcBw=K4CnwA@mail.gmail.com>
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=047d7b15fd9b28478004e33218ce
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, 05 Aug 2013 12:03:21 -0000

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

I agree with you John, I also not objecting it but wanted more meaning into
the report when I receive it, as I suggested before for clarifications.
I don't think majority in IETF think it is meaningless so that is why I
want to clarify the meaning and discuss what most may not want to discuss.
If this was already discussed could some one point me to a discussion about
a weekly post that is done for long and which it may be  meaningless by
some and understoond the meaning by others. I will add that the report can
be misleading, and that I have no intention to write a code for something
that is not IETF procedure, but I have intention to clarify such message
received each week in IETF that has a lack of information or meaning agreed
on.

AB


On Sun, Aug 4, 2013 at 9:55 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Sunday, August 04, 2013 19:53 +0000 John Levine
> <johnl@taugh.com> wrote:
>
> >> If there is a serious drive to discontinue the weekly posting
> >> summary - I strongly object.
> >
> > As far as I can tell, one person objects, everyone else thinks
> > it's fine.
>
> I do not want to be recorded as thinking it is fine.  If nothing
> else, I think was is being reported is meaningless statistically
> (which doesn't mean people can't find value in it).   However, I
> do not object to its being posted as long as it isn't used to
> justify personal attacks on individuals for their "ranking".
>
> It seems to me that isn't quite what you said, rough consensus
> or not.
>
> best,
>    john
>
>
>

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

<div dir=3D"ltr"><div>I agree with you John, I also not objecting it=A0but =
wanted more meaning into the report=A0when I receive it,=A0as I suggested b=
efore for clarifications.</div><div>I don&#39;t think majority in IETF thin=
k it is meaningless so that is why I want to clarify the meaning and discus=
s what most may not want to discuss. If this was already discussed could so=
me one point me to a discussion about a weekly post that is done for long a=
nd which it may be=A0 meaningless by some=A0and=A0understoond the meaning b=
y others. I will add that the report can be=A0misleading, and that I have n=
o intention to write a code for something that is not IETF=A0procedure, but=
 I have intention to clarify such message received=A0each week in IETF that=
 has a lack of information or=A0meaning agreed on.</div>
<div>=A0</div><div>AB</div></div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Sun, Aug 4, 2013 at 9:55 PM, John C Klensin <span di=
r=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-i=
etf@jck.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
--On Sunday, August 04, 2013 19:53 +0000 John Levine<br>
<div class=3D"im">&lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a=
>&gt; wrote:<br>
<br>
&gt;&gt; If there is a serious drive to discontinue the weekly posting<br>
&gt;&gt; summary - I strongly object.<br>
&gt;<br>
&gt; As far as I can tell, one person objects, everyone else thinks<br>
&gt; it&#39;s fine.<br>
<br>
</div>I do not want to be recorded as thinking it is fine. =A0If nothing<br=
>
else, I think was is being reported is meaningless statistically<br>
(which doesn&#39;t mean people can&#39;t find value in it). =A0 However, I<=
br>
do not object to its being posted as long as it isn&#39;t used to<br>
justify personal attacks on individuals for their &quot;ranking&quot;.<br>
<br>
It seems to me that isn&#39;t quite what you said, rough consensus<br>
or not.<br>
<br>
best,<br>
=A0 =A0john<br>
<br>
<br>
</blockquote></div><br></div>

--047d7b15fd9b28478004e33218ce--

From hadriel.kaplan@oracle.com  Mon Aug  5 05:11:16 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4096E21F9DBD for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.509
X-Spam-Level: 
X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXpZEWH1qn8g for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:11:09 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0752221F9DAF for <ietf@ietf.org>; Mon,  5 Aug 2013 05:11:06 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r75CB0qQ005924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Aug 2013 12:11:01 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r75CAxFg000472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Aug 2013 12:11:00 GMT
Received: from abhmt103.oracle.com (abhmt103.oracle.com [141.146.116.55]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r75CAxgE000460; Mon, 5 Aug 2013 12:10:59 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 05 Aug 2013 05:10:59 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <6.2.5.6.2.20130805002145.0bb83420@resistor.net>
Date: Mon, 5 Aug 2013 08:10:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <32B1624C-2A3B-4DFF-9322-EA84D41938E6@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <6.2.5.6.2.20130805002145.0bb83420@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 12:11:16 -0000

On Aug 5, 2013, at 5:26 AM, SM <sm@resistor.net> wrote:

> At 13:10 04-08-2013, Hadriel Kaplan wrote:
>> You have the agenda and drafts 2 weeks in advance.  The slides aren't =
normative.  Even
>=20
> I do not have the agenda two weeks in advance.

Huh.  Sounds like a WG Chair problem.  I believe draft agendas are due 2 =
weeks in advance, and final agendas due 1 week in advance.  Or at least =
that was the excuse I was given when I've been denied requests to add =
stuff to WG agendas on previous occasions - the Chairs told me I was =
asking too late. (as they should have)


> What is the meaning of "normative" in the above?

I was trying to be cute by using the term from our drafts/RFCs, as in =
normative references vs. informative, or the document's RFC2119-type =
text is normative while examples are informative.  I meant the slides =
are just helpful guides, like pictorial examples, vs. the draft itself =
which is the real proposal.  I guess the joke flopped. :(


> Some of the Jabber scribes are not able to tell me who are at the =
microphone when I ask them.  If it was my decision to make (and it is =
not), the Jabber scribe would be allowed to comment at the microphone =
even after the microphone line is capped.  A person can always argue =
that it is an arbitrary decision.  :-)

Again, this sounds like a WG Chair problem.  If you find that happening, =
send a private email to that working group's Chair(s) reminding them of =
the jabber folks.  And if they ignore you, then send a private email to =
the Area Director(s).  WG Chairs and ADs are generally decent human =
beings, at least in private.  ;)


> As an off-topic comment, it's not because the Meetecho people are nice =
that one should expect them to act as Jabber scribes.

I don't expect Meetecho people to jabber scribe.  I expect other folks =
in the room to volunteer.  It's a heck of a lot easier/better than being =
the minute taker.  That's why I volunteer for being a scribe - to avoid =
being a minute taker. :)

-hadriel



From scott.brim@gmail.com  Mon Aug  5 05:12:39 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B80321F9DD6 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 LrehaKoIqmap for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:12:38 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 23DA421F9A87 for <ietf@ietf.org>; Mon,  5 Aug 2013 05:12:35 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id nd7so1633963qeb.24 for <ietf@ietf.org>; Mon, 05 Aug 2013 05:12:34 -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:x-enigmail-version:content-type :content-transfer-encoding; bh=aE6kInMyqodXEp2pJrVm/Je/ICpRAohmRiV3/h75eSs=; b=eeiUz8rCL+STpqyMOUuq2CsfYIp/t8JDZYuvhfZ94GHF673raR/nYCkiDlhXBAgj37 Rnf5OCgKdXwPiTVz07lKNwfjGtLJ4KzImuSTiqAyoOHRq9vk9CdrZH5ruY0btrrnD/IP v4katRA/jHcIyfN0SoQSgORqV4zcq4qlG9TQtViDoq7RhpwUJm0vO+8PuQOliI+ku4Je RBHP8UuaVq2oUwRnUuiqbkN7dzwRvAlDMk2Y3bpWi0XqjZ0m7XSobEYaF4N/FlJj8pig xCSv0mRZkYI7ISrA4WdY3fI/6rl2EXrhqUYUmj84QvagawPNGWdumrrLDK5swSplCAxp BL0A==
X-Received: by 10.229.230.129 with SMTP id jm1mr6133354qcb.7.1375704754492; Mon, 05 Aug 2013 05:12:34 -0700 (PDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com. [67.241.75.185]) by mx.google.com with ESMTPSA id a4sm2917058qai.3.2013.08.05.05.12.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 05:12:33 -0700 (PDT)
Message-ID: <51FF96B0.9030702@gmail.com>
Date: Mon, 05 Aug 2013 08:12:32 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
References: <20130804195342.3851.qmail@joyce.lan> <8C1E4FC360C0F4D07C51298A@192.168.1.128> <CADnDZ8-z=UQyfdxt-kkFLx1t1kiu_BLkaRQ3jznDcBw=K4CnwA@mail.gmail.com>
In-Reply-To: <CADnDZ8-z=UQyfdxt-kkFLx1t1kiu_BLkaRQ3jznDcBw=K4CnwA@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Mon, 05 Aug 2013 12:12:40 -0000

If one or two people are doing most of the posting to a list, that means
something is out of balance.  Summary statistics can be used as an
indicator that something should be done to encourage diversity, or get
people back on topic, etc.

From ron.even.tlv@gmail.com  Mon Aug  5 05:36:50 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1286C21F9473; Mon,  5 Aug 2013 05:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level: 
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[AWL=-0.595, BAYES_05=-1.11, 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 AxaJc+DMqn-b; Mon,  5 Aug 2013 05:36:47 -0700 (PDT)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 910DA21F969F; Mon,  5 Aug 2013 05:36:46 -0700 (PDT)
Received: by mail-ea0-f177.google.com with SMTP id f15so1572260eak.36 for <multiple recipients>; Mon, 05 Aug 2013 05:36:40 -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=6qf9WOgrwLrQj+4FUsGAVIydcMN3g0cuk8FDDn75lXE=; b=wArx/2vF5vsxD6fqWTL51P2vAVKOnlf0C33TXpvprMnwo/HzHfUTxclAiOqngj8h4W /WcOd9dxhGGPAkGRI0wecspSdkYrA94TFZKoy2c3tNBvP6BWv8GBI7peF/SDFqE1adrx WfAuUvQDIg31/Tc2qZcF4SQJLmfs0K9gwZjuf0j6iZBxG3GCUo4S2L47wgVTIDt0DnZR /utdaBlUjEVFp3e6Z8cDh0QKA6b6q66+qJwzppC6NveaiGImY8ImFWiLTqr78yRNYd/Z gSIudXMZx1dgPGC1TZh7BAf5TJxWTyE/UGCf48NOSs6fHEFpeUXffVBpob/U7+pbZnNb sy9g==
X-Received: by 10.15.26.199 with SMTP id n47mr16975662eeu.88.1375706200822; Mon, 05 Aug 2013 05:36:40 -0700 (PDT)
Received: from RoniE (bzq-79-176-222-74.red.bezeqint.net. [79.176.222.74]) by mx.google.com with ESMTPSA id l42sm32998889eeo.14.2013.08.05.05.36.38 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 05 Aug 2013 05:36:39 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-allen-dispatch-imei-urn-as-instanceid.all@tools.ietf.org>
Subject: Gen-ART IETF LC review of draft-allen-dispatch-imei-urn-as-instanceid-10
Date: Mon, 5 Aug 2013 15:34:34 +0300
Message-ID: <00a401ce91d8$26b96210$742c2630$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A5_01CE91F1.4C073650"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6R2AMm9KzL7XkgSVWmyWq12ZGCoA==
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, 05 Aug 2013 12:36:50 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00A5_01CE91F1.4C073650
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-allen-dispatch-imei-urn-as-instanceid-10

Reviewer: Roni Even

Review Date:2013-8-5

IETF LC End Date: 2013-8-16

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as an Informational RFC.

 

 

Major issues:

 

Minor issues:

 

Why is it going to be an Informational RFC, considering that there is a lot
of normative language in the document.

 

 

 

Nits/editorial comments:

According to RFC editor guidelines
(http://www.rfc-editor.org/policy.html#policy.abstract) the abstract section
should not contain citations unless they are completely defined within the
Abstract.

 


------=_NextPart_000_00A5_01CE91F1.4C073650
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;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.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;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-allen-dispatch-imei-urn-as-instanceid-10</span><o:p></o:p></p=
><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;5<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-8&#8211;16<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 an Informational =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Why is it =
going to be an Informational RFC, considering that there is a lot of =
normative language in the document.</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"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>According =
to RFC editor guidelines (</span><a =
href=3D"http://www.rfc-editor.org/policy.html#policy.abstract">http://www=
.rfc-editor.org/policy.html#policy.abstract</a>)<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> the <a =
name=3Dpolicy.abstract>abstract section <span =
style=3D'color:black'>should not contain citations unless they are =
completely defined within the Abstract.</span></a><span =
style=3D'color:black'><o:p></o:p></span></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00A5_01CE91F1.4C073650--


From hadriel.kaplan@oracle.com  Mon Aug  5 05:37:28 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C59CF21F9EF8 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 VN2w8ka93qjk for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 05:37:21 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3E15421F9EFC for <ietf@ietf.org>; Mon,  5 Aug 2013 05:37:20 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r75CbIu5031957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 5 Aug 2013 12:37:18 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r75CbHrN028230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Aug 2013 12:37:17 GMT
Received: from abhmt110.oracle.com (abhmt110.oracle.com [141.146.116.62]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r75CbHt6002631; Mon, 5 Aug 2013 12:37:17 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 05 Aug 2013 05:37:16 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: The Friday Report (was Re: Weekly posting summary for ietf@ietf.org)
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CADnDZ8-z=UQyfdxt-kkFLx1t1kiu_BLkaRQ3jznDcBw=K4CnwA@mail.gmail.com>
Date: Mon, 5 Aug 2013 08:37:15 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD210CB1-0D38-4E75-B26B-8F6FD2A5AEEB@oracle.com>
References: <20130804195342.3851.qmail@joyce.lan> <8C1E4FC360C0F4D07C51298A@192.168.1.128> <CADnDZ8-z=UQyfdxt-kkFLx1t1kiu_BLkaRQ3jznDcBw=K4CnwA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
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, 05 Aug 2013 12:37:28 -0000

On Aug 5, 2013, at 8:03 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> I agree with you John, I also not objecting it but wanted more meaning =
into the report when I receive it, as I suggested before for =
clarifications.

It's just a weekly posting summary of raw stats - it's not a ranking =
system, popularity contest, or twitter trending list.  It's not =
important, and doesn't matter.  Lots of people have been at the top of =
that list, and we didn't get a reward or rebuke.  Even if the summary =
script was stopped, people who care can generate their own.  What's more =
important is the content quality of the emails, and no automated script =
can measure that (except for ones the NSA has I guess).


> I don't think majority in IETF think it is meaningless so that is why =
I want to clarify the meaning and discuss what most may not want to =
discuss.

Dude, the majority of the IETF probably thinks this entire mailing list =
is meaningless.

-hadriel


From paul.hoffman@vpnc.org  Mon Aug  5 06:09:38 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D14FF21F8C65 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 06:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.796
X-Spam-Level: 
X-Spam-Status: No, score=-101.796 tagged_above=-999 required=5 tests=[AWL=0.803, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wv2ZUp0fZuGH for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 06:09:37 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id C949A21F9F70 for <ietf@ietf.org>; Mon,  5 Aug 2013 06:09:33 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r75D9TQY065068 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 5 Aug 2013 06:09:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <2681ABBB-DDC3-48DE-A6B3-29771701AF05@NLnetLabs.nl>
Date: Mon, 5 Aug 2013 06:09:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA2ABA06-6861-44DE-83FA-D6A251E45E73@vpnc.org>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <2681ABBB-DDC3-48DE-A6B3-29771701AF05@NLnetLabs.nl>
To: Chris Griffiths <cgriffiths@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 13:09:38 -0000

On Aug 5, 2013, at 4:08 AM, Olaf Kolkman <olaf@NLnetLabs.nl> wrote:

>> Does the community feel these are reasonable reasons to update the =
trust agreement?=20
>=20
> The answer to that question is: yes. It seems reasonable to open up =
the agreement in order to fulfill its purpose in reasonable, effective, =
and pragmatic ways.
>=20
> I would expect the trust to come back with a proposal once there seems =
to be consensus that the the agreement should be opened. My requirement =
would be that that proposal reflects that the Trust will deal with the =
assets in a way that is sensible and serves community needs.


+1

--Paul Hoffman=

From tobias.gondrom@gondrom.org  Mon Aug  5 06:21:32 2013
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D70721F9E80 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 06:21:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.361
X-Spam-Level: 
X-Spam-Status: No, score=-95.361 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jfak5f70xHMR for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 06:21: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 D196821F9F51 for <ietf@ietf.org>; Mon,  5 Aug 2013 06:21:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=L5aDYqnAHyPnhzXXuR5M7ICOSpon+cnEVlT9tAu74otkeOsr6PZ6Dg+8IrmCQHMhd5oNt2KYs0omHfNo5C3oZTNIVt0AyHtgtjLEV820HK/cfnEzDP9mKczp+f/fIzEE; h=Received:Received:User-Agent:In-Reply-To:References:MIME-Version:Content-Type:Subject:From:Date:To:CC:Message-ID;
Received: (qmail 12016 invoked from network); 5 Aug 2013 15:21:13 +0200
Received: from unknown (HELO host234.msm.che.vodafone) (212.183.128.167) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (RC4-MD5 encrypted, authenticated); 5 Aug 2013 15:21:13 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <EA2ABA06-6861-44DE-83FA-D6A251E45E73@vpnc.org>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <2681ABBB-DDC3-48DE-A6B3-29771701AF05@NLnetLabs.nl> <EA2ABA06-6861-44DE-83FA-D6A251E45E73@vpnc.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----TBVT1TQ7RMHM3WWRCD175AAJMRUAWG"
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
Date: Mon, 05 Aug 2013 15:21:01 +0200
To: Paul Hoffman <paul.hoffman@vpnc.org>, Chris Griffiths <cgriffiths@gmail.com>
Message-ID: <6b7cc487-1ddb-4e7b-bc3d-4877ba67a26c@email.android.com>
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 13:21:32 -0000

------TBVT1TQ7RMHM3WWRCD175AAJMRUAWG
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

+1

Tobias Gondrom

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
>On Aug 5, 2013, at 4:08 AM, Olaf Kolkman <olaf@NLnetLabs.nl> wrote:
>
>>> Does the community feel these are reasonable reasons to update the
>trust agreement? 
>> 
>> The answer to that question is: yes. It seems reasonable to open up
>the agreement in order to fulfill its purpose in reasonable, effective,
>and pragmatic ways.
>> 
>> I would expect the trust to come back with a proposal once there
>seems to be consensus that the the agreement should be opened. My
>requirement would be that that proposal reflects that the Trust will
>deal with the assets in a way that is sensible and serves community
>needs.
>
>
>+1
>
>--Paul Hoffman

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------TBVT1TQ7RMHM3WWRCD175AAJMRUAWG
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head></head><body>+1<br>
<br>
Tobias Gondrom<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 class="k9mail">On Aug 5, 2013, at 4:08 AM, Olaf Kolkman &lt;olaf@NLnetLabs.nl&gt; wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">Does the community feel these are reasonable reasons to update the trust agreement? </blockquote><br />The answer to that question is: yes. It seems reasonable to open up the agreement in order to fulfill its purpose in reasonable, effective, and pragmatic ways.<br /><br />I would expect the trust to come back with a proposal once there seems to be consensus that the the agreement should be opened. My requirement would be that that proposal reflects that the Trust will deal with the assets in a way that is sensible and serves community needs.</blockquote><br /><br />+1<br /><br />--Paul Hoffman</pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html>
------TBVT1TQ7RMHM3WWRCD175AAJMRUAWG--


From mcr@sandelman.ca  Mon Aug  5 07:18:55 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2789E21F9EF4 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 07:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.404
X-Spam-Level: 
X-Spam-Status: No, score=-2.404 tagged_above=-999 required=5 tests=[AWL=0.195,  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 ZD2j8fVZTpeU for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 07:18:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id CE49321F9EF2 for <ietf@ietf.org>; Mon,  5 Aug 2013 07:18:48 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F36DF2018B for <ietf@ietf.org>; Mon,  5 Aug 2013 11:25:07 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 96CA663A88; Mon,  5 Aug 2013 10:17:17 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 82C4A63732 for <ietf@ietf.org>; Mon,  5 Aug 2013 10:17:17 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
In-Reply-To: <51FEDF60.2010902@gmail.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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, 05 Aug 2013 10:17:17 -0400
Message-ID: <14937.1375712237@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, 05 Aug 2013 14:18:55 -0000

--=-=-=


Spencer Dawkins <spencerdawkins.ietf@gmail.com> quoted Hadiel really poorly,
which confused me as you who said this, but I think it was Hadriel now:
    > OK, I'll bite.  Why do you and Michael believe you need to have the
    > slides 1 week in advance?

1) As a WG chair, I'd like to see the slides from a (new) presenter in
   advance to make sure that the *presentation* is on topic, there aren't
   too many slides, and that ideally, it is a request for discussion rather
   than a presentation.
   That's where the deadline comes from.  I don't suggest that

2) As a remote participate, I'd much rather have consolidate slides.
   That requires a bit of time/effort on the part of the chairs.

3) As an open-standards body, I believe it is hypocritical for us to be
   posting slides in a vendor proprietary format or one from a "standards"
   body that seems to have all of features we dislike (like pay to vote).
   (I'm okay with the secretariat doing conversion, but they are not instant)
   (And,open source tools running on open platforms sometimes do not
   render the slides as intended due to lack of a font or a other thing)

    > Not getting the slides at all is a different matter - but 7 days in
    > advance is counter-productive.  They should be as up-to-date as
    > practical, to take into account mailing list discussions. [or at least
    > that's how I justify my same-day, ultra-fresh slides]

I distinquish between rev-00 of slides and rev-09.  I don't have a problem
with updates to the slides, assuming you can find the "Export as PDF"
button. It would be best if you didn't create new slides due to numbering
changes.
I also understand that ADs running area meeting aren't going to have status
updates 7 days in advance, nor do I expect them to.

I had not considered Spencer's point about translation, and frankly it is a
really really really good point.

    > None of this should be taken as disagreement with proposals to
    > experiment with
    > room shapes, whiteboards, , etc. that I heard last week.

+1

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


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



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

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

iQCVAwUBUf+z6oqHRg3pndX9AQK/KwP/XfPW0yNkFYUWlWMKUYBKz2pqcOVx/zoV
U+Ke6IEhB5zynUGp9EfD7C0596icECk54bC1hbKa8TL3t2lW+PDY34OF+DnkVxjH
IXxT5lJnkEBFl9/ngdV9K8uru1C5rldxJ/bPLDjqGFH9Aa4TRemeUcA3CpR45WFP
NZTFxiRxKEM=
=OGkA
-----END PGP SIGNATURE-----
--=-=-=--

From john-ietf@jck.com  Mon Aug  5 07:29:20 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE0E21F9EFC; Mon,  5 Aug 2013 07:29:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.652
X-Spam-Level: 
X-Spam-Status: No, score=-102.652 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfgaauyxYska; Mon,  5 Aug 2013 07:29:14 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7F221F9F21; Mon,  5 Aug 2013 07:29:12 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V6LmZ-0005jg-Kg; Mon, 05 Aug 2013 10:29:11 -0400
Date: Mon, 05 Aug 2013 10:29:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jorge Contreras <cntreras@gmail.com>, Chris Griffiths <cgriffiths@gmail.com>
Subject: Re: [Trustees] The Trust Agreement
Message-ID: <6A0614C8AB667C45BE5D7A0D@JcK-HP8200.jck.com>
In-Reply-To: <CAP0PwYZ=T541VbjvFJnHcqPXXuhjUQVe33hsOrZ-Uer9OED9BQ@mail.gmail.com>
References: <51FACC4A.4020307@gmail.com> <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com> <CAP0PwYZ=T541VbjvFJnHcqPXXuhjUQVe33hsOrZ-Uer9OED9BQ@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: Trustees <trustees@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 14:29:20 -0000

--On Saturday, August 03, 2013 06:50 -0500 Jorge Contreras
<cntreras@gmail.com> wrote:

> Please see below for some specific responses to Brian's
> concerns.
>...

Jorge,

Given this explanation, I'm ok with seeing a specific proposal.
I think that proposal should reflect a minimum change model.  As
far as CC is concerned, I'm not persuaded that it meets out need
but not persuaded that it would cause great harm for
non-standards documents either.  I hope you and the IETF Trust
can continue to educate us as needed.

best,
   john






From paul.hoffman@vpnc.org  Mon Aug  5 07:48:06 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 799FA21F9E4F; Mon,  5 Aug 2013 07:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.14
X-Spam-Level: 
X-Spam-Status: No, score=-102.14 tagged_above=-999 required=5 tests=[AWL=0.459, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4YP2jKfGXFM; Mon,  5 Aug 2013 07:48:05 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7D77421F9E28; Mon,  5 Aug 2013 07:48:05 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r75Em2xA068213 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 5 Aug 2013 07:48:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-228.dsl.dynamic.sonic.net [50.1.98.228] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Trustees] The Trust Agreement
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6A0614C8AB667C45BE5D7A0D@JcK-HP8200.jck.com>
Date: Mon, 5 Aug 2013 07:48:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6293027D-1954-43B7-B47C-BF85229A0F3A@vpnc.org>
References: <51FACC4A.4020307@gmail.com> <E57BB916-AC97-4A10-B239-A413C47BE559@gmail.com> <CAP0PwYZ=T541VbjvFJnHcqPXXuhjUQVe33hsOrZ-Uer9OED9BQ@mail.gmail.com> <6A0614C8AB667C45BE5D7A0D@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: Trustees <trustees@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 14:48:06 -0000

On Aug 5, 2013, at 7:29 AM, John C Klensin <john-ietf@jck.com> wrote:

> As
> far as CC is concerned, I'm not persuaded that it meets out need
> but not persuaded that it would cause great harm for
> non-standards documents either.

At the risk of opening up the paint cabinet inside the bike shed: what =
do you think meets our "need"? I ask this specifically about the Tao, =
the document that was brought up as a good use for the Creative Commons =
Attribution-ShareAlike ("BY-SA") license (see =
<http://creativecommons.org/licenses/>). That license seemed to meet the =
desire (not need) to make the Tao more easily distributed to a wider =
audience, in multiple languages, and thus open the IETF up to more =
people.

--Paul Hoffman=

From cgriffiths@gmail.com  Mon Aug  5 07:50:39 2013
Return-Path: <cgriffiths@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED88021F9956 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 07:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I09RZMlRNpMz for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 07:50:38 -0700 (PDT)
Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id D2FF421F8F2E for <ietf@ietf.org>; Mon,  5 Aug 2013 07:50:35 -0700 (PDT)
Received: by mail-qa0-f41.google.com with SMTP id bs12so1012921qab.0 for <ietf@ietf.org>; Mon, 05 Aug 2013 07:50:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=PQXXlOGQhLV0W1nE3ur3kYGL5cwffryWaIVRwpiwtd4=; b=UmDahGhYX1qp+H9+J1dS0bPpiCw6DG4VGQn6U0tiIZtMLME18WQFqAgsBCeqnHttRY NZ3kmiuTmRlQUYYwSAWgEAXDgrpYuGmRkqnOfFgctfSsSu6Ui8o/8urgFk0785AHJ/gd 2J2BICziSDQjf2UCrC9+31ZRWabYjT0j9ElL+v68D+lFcQouZGbRMN6XxPnV6GjY+8SN 931seaQBiWMJU7XzBQ7ai28x6+RC9w9PN9wnTW9B/n3wh7PHxpG49JQqovEJL2OunCWt dkyoYfJ5LArGXdxfLEv9M30aSGYIHefuMmYNciBRdhPu9GXTFdaQ89pIw6x49X30ebgo jcBA==
X-Received: by 10.229.114.134 with SMTP id e6mr6167465qcq.99.1375714233315; Mon, 05 Aug 2013 07:50:33 -0700 (PDT)
Received: from ?IPv6:2600:200f:1:112:d8af:9475:6ac0:6645? ([2600:200f:1:112:d8af:9475:6ac0:6645]) by mx.google.com with ESMTPSA id i1sm3747531qas.10.2013.08.05.07.50.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 07:50:32 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_0B1113E8-5988-4133-B60B-3CE9292B7243"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Chris Griffiths <cgriffiths@gmail.com>
In-Reply-To: <2681ABBB-DDC3-48DE-A6B3-29771701AF05@NLnetLabs.nl>
Date: Mon, 5 Aug 2013 10:50:26 -0400
Message-Id: <CD6C91D4-B5C3-4A17-ADD3-411C5A0921F5@gmail.com>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <2681ABBB-DDC3-48DE-A6B3-29771701AF05@NLnetLabs.nl>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 14:50:39 -0000

--Apple-Mail=_0B1113E8-5988-4133-B60B-3CE9292B7243
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 5, 2013, at 7:08 AM, Olaf Kolkman <olaf@NLnetLabs.nl> wrote:

>=20
> On Aug 3, 2013, at 8:48 AM, Chris Griffiths <cgriffiths@gmail.com> =
wrote:
>=20
>> IETF Community,
>>=20
>> The IETF Trust Trustees would like feedback from the community on =
several issues:
>> 	- We have received requests that we cannot accommodate and have =
consulted legal counsel to review our options
>> 	- The trust agreement does not allow the trustees to effectively =
manage some trust assets=20
>=20
> =46rom this mail it is not clear what type of feedback you are looking =
for. I like your direct question from the slide deck better. There you =
asked:
>> Does the community feel these are reasonable reasons to update the =
trust agreement?=20

This was my intention Olaf, thank you for the feedback.


> The answer to that question is: yes. It seems reasonable to open up =
the agreement in order to fulfill its purpose in reasonable, effective, =
and pragmatic ways.
>=20
> I would expect the trust to come back with a proposal once there seems =
to be consensus that the the agreement should be opened. My requirement =
would be that that proposal reflects that the Trust will deal with the =
assets in a way that is sensible and serves community needs.

We will certainly do that once there is consensus on this.

>=20
> Best, and thanks,
>=20
> --Olaf
>=20
> PS. As an aside, something that might be helpful for other readers of =
this thread: The word agreement in "Trust Agreement" might be confusing =
to the community, but I think that it is important to point out that the =
agreement can, since July 1, 2010, be modified unilaterally by the trust =
(see 10.1 for details and boundary conditions).  So except the due =
diligence that is needed to reflect the communities requirements there =
is no further negotiation needed with the Settlers.


--Apple-Mail=_0B1113E8-5988-4133-B60B-3CE9292B7243
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBCgAGBQJR/7u2AAoJEE4wr5snmnsMnw0H/Ras8Qvj6PqnZ6Xr9EgpC+5F
SgJoVjt9SYY8qxNwvBwqvZeZ8ZlE2ippn/dvtm1y3WBPZARqpiPgY+jN0VmR/Quz
Ro8u8vWdfoE2g/oGJFvqyLMLpxaDJXGypDDa+wAdghrcwjN34mjECMc9RvrGTvAi
WXTd/IYfdU7lmSju52WJIHwfwiHJAKaY41TAYWgdCWK8DTe8owOHVPDTxuoKRjTo
G89P/ncXGL3Gec+8h4qeu7HKPm3IBFxbRNkX8IUQHL9wNMnsisedfWQztgPmsLkw
hwECMkU+J6kuBMlaEe2a+jUSwfUjtaTMpMYXnLX8QnQvFbmL3dIbo1jeJ8Cqu5o=
=dHYf
-----END PGP SIGNATURE-----

--Apple-Mail=_0B1113E8-5988-4133-B60B-3CE9292B7243--

From jnc@mercury.lcs.mit.edu  Mon Aug  5 08:11:31 2013
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 C73AF21F9EC3; Mon,  5 Aug 2013 08:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Level: 
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[AWL=0.136,  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 53AhWNxu5FKU; Mon,  5 Aug 2013 08:11: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 A3F7321F99C3; Mon,  5 Aug 2013 08:11:25 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 199D518C123; Mon,  5 Aug 2013 11:11:25 -0400 (EDT)
To: ietf@ietf.org, trustees@ietf.org
Subject: Re: [Trustees] The Trust Agreement
Message-Id: <20130805151125.199D518C123@mercury.lcs.mit.edu>
Date: Mon,  5 Aug 2013 11:11:25 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 15:11:32 -0000

    > From: Brian E Carpenter <brian.e.carpenter@gmail.com>

    > Thanks for the careful explanations.

I'll second that; it does seem that some tweaking may be in order.

    > Clearly the Trust shouldn't have blanket permission to abandon or
    > dispose of assets

When the time comes to draft actual wording, I would suggest that there be a
requirement for a notification to the IETF-Announce list at least one month
(or so?) prior to any actual disposal or abandonment, or completion of any
agreement to dispose. (Maybe only for IP, and not real property too, such as
old servers, etc?) I can't imagine the Trust would be disposing of stuff very
often, so I think this would be a reasonable requirement.

	Noel

From john@jck.com  Mon Aug  5 09:02:19 2013
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 DD1AC21F8C20 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 09:02: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 FQBiQyfxFuDt for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 09:02:14 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 23E3021F9F3D for <ietf@ietf.org>; Mon,  5 Aug 2013 09:01:53 -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 1V6NE7-0005r9-9k; Mon, 05 Aug 2013 12:01:43 -0400
Date: Mon, 05 Aug 2013 12:01:38 -0400
From: John C Klensin <john@jck.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Yoav Nir <ynir@checkpoint.com>
Subject: Re: Anonymity versus Pseudonymity (was Re: [87attendees] procedural	question with remote participation)
Message-ID: <95990DC99B1CD9AF95A88B43@JcK-HP8200.jck.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775243597@mbx-01.win.nominum.com>
References: <BBE1B978-B49E-4A55-BD0F-92B72662202E@edvina.net> <51FB9951.7090700@nostrum.com> <51FBA251.9040804@gmail.com> <FF620748-848A-4399-9D59-4637D19CD4D9@edvina.net> <7A4F637F-10A7-4709-B186-B6D7E0DC6272@checkpoint.com> <8D23D4052ABE7A4490E77B1A012B630775243147@mbx-01.win.nominum.com> <FA730ECD-08A5-41F7-945A-2A0EC24B81B1@checkpoint.com> <8D23D4052ABE7A4490E77B1A012B630775243597@mbx-01.win.nominum.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: "Olle E. Johansson" <oej@edvina.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 16:02:20 -0000

--On Sunday, August 04, 2013 19:31 +0000 Ted Lemon
<Ted.Lemon@nominum.com> wrote:

> If you came to the IETF and were working for company X,
> registered pseudonymously, and didn't disclose IPR belonging
> to you or company X, and then later company X sued someone for
> using their IPR, you and company X would get raked over the
> coals, jointly and severally; the deliberate attempt to
> deceive would make things worse for you.   And that's the
> point: to provide you with a strong disincentive to doing such
> a thing.   So whether the rules prevent you from being
> anonymous, or prevent you from suing, everybody's happy.

If company X wanted to collaborate with Yoav in preserving his
pseudonym (i.e., not disclosing the binding to his name), they
could presumably file a disclosure without identifying the
particular employee for whom the disclosure was made.
Especially with the ambiguities created by anonymous and
pseudonymous remote participation, I assume we would not decline
to post an IPR disclosure from an organization on the grounds
that we didn't know who was affiliated with it who participated
in the IETF.

> (IANAL, so I'm just explaining my understanding of the
> situation.)

ditto.

best,
  john






From superuser@gmail.com  Mon Aug  5 10:36:20 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BC821F9DE1; Mon,  5 Aug 2013 10:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zM7gArkbRBeo; Mon,  5 Aug 2013 10:36:18 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id CE10021F9DCE; Mon,  5 Aug 2013 10:36:16 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id en1so1812072wid.14 for <multiple recipients>; Mon, 05 Aug 2013 10:36: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=vPAUTz7a0ot2q8ra52Tz4eNGJImLQq9JLRGbfsI3APQ=; b=CJfhMmrxzsMuRbCyMU2erMqgrzUsq3uPTWiRHtXEzlOBZm6zwDVW9S3TDHVDB5u/qW zQ8L4MIqWdUhFe654RfIocAsDKKBPqzLBQzaWQmdkP7tgQ/rPear03nKLJkE5LQhPMho jE5tvaaUU8FOdkvs4SfBX0R0k9T91H0apv7FVjsCvkcmlaiC4sJGT02jKunI+heSn8b5 DsmzkrC91/hjpCM7kKKVK6BE4Yqhjt7WKBTLer5Z6d/LoAYeYKzvVq2sgwUTANlgX1nN iuDJUGThirR+OvfH38NdHIJc8rI3KveFfZ7nAg4L32Ja1SCOWd+BqrIQOrGJ5i26EbBs gvhQ==
MIME-Version: 1.0
X-Received: by 10.180.189.9 with SMTP id ge9mr4081195wic.52.1375724174482; Mon, 05 Aug 2013 10:36:14 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Mon, 5 Aug 2013 10:36:14 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130724111528.0d2bf428@resistor.net>
References: <20130715230614.25146.34230.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130724111528.0d2bf428@resistor.net>
Date: Mon, 5 Aug 2013 10:36:14 -0700
Message-ID: <CAL0qLwZuNLE6qSksxa7z83WxEUWO1OYsBORWfsMA2naJaNx0NQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-weirds-rdap-sec-04.txt> (Security Services for the Registration Data Access Protocol) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=001a11c34302baa56b04e336bee6
Cc: ietf <ietf@ietf.org>, "weirds@ietf.org" <weirds@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 17:36:20 -0000

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

Hi SM, thanks for your comments.  I'm shepherding the document, so replies
inline:

On Wed, Jul 24, 2013 at 12:21 PM, SM <sm@resistor.net> wrote:

> According to Section 1, the Registration Data Access Protocol is a Lookup
> Format,
> JSON Responses and HTTP usage.  This looks like a weird protocol to me.
>  If the said protocol is HTTP + JSON (responses) it would be clearer to the
> reader to explain that in one specification.  Section 1 mentions that:
>
>   "One goal of RDAP is to provide security services that do not exist in
>    the WHOIS"
>
> I don't see how adding a fourth document helps to achieve that goal.
>

RDAP is far from the first protocol specification to exist across multiple
RFCs, so this approach isn't uncommon.  That said, I take it you believe
the material here should be rolled into one of the other documents?


> In Section 3.1:
>
>   'To that end, RDAP clients and servers MUST implement the
>    authentication framework specified in "HTTP Authentication:
>    Basic and Digest Access Authentication" [RFC2617].'
>
> This draft refers to the above authentication framework as the RDAP
> authentication framework.  The draft then explains how the "basic" and
> "digest" schemes work.  This is "how-to" stuff.  The draft sets the
> following requirement:
>
>   'If the "basic" scheme is used, HTTP Over TLS [RFC2818] MUST be used
>    to protect the client's credentials from disclosure while in transit
>   (see Section 3.4).'
>
> If I understood correctly HTTPS is needed for security only if the "basic"
> scheme" is used.
>

Correct, that's what it says.


>   "RDAP SHOULD be capable of supporting future authentication methods
>    defined for use with HTTP."
>
> That sounds like a "SHOULD CONSIDER".  Given how ill-defined the protocol
> is I doubt that the above is actionable.
>

You said two important things here:

1) Can you please elaborate on why you think this is "ill-defined" and, if
possible, how this could be remedied?

2) Insofar as this draft amounts to a requirements document, I take "SHOULD
be capable" to mean the actual implementation needs to have hooks for the
stated capability, or have a very good reason for not providing those hooks
(e.g., the same capability is available some other way).


In Section 3.1.1:
>
>   "RDAP MAY include a federated authentication mechanism that permits
>    a client to access multiple RDAP servers in the same federation
>    with one credential."
>
> Using an upper-case "may" does not bring much in terms of security.  The
> draft takes the stance that security is an optional feature.
>

More precisely, the draft takes the stance that federated authentication is
an option.  The working group doesn't feel the need to elevate this to
SHOULD or MUST, likely because operators might not be compelled to federate
themselves with anyone for whatever local security or privacy reasons apply.


>
> Section 3.1.1 looks like an executive summary for federated authentication.
>

Right, and the benefits it provides in the context of RDAP.  Is that a
criticism or an observation?  What do you suggest?


> In Section 3.3:
>
>   "An RDAP service has to be available to be useful.  There are no RDAP-
>    unique requirements to provide availability, but as a general
>    security consideration a service operator needs to be aware of the
>    issues associated with denial of service."
>
> The text says that the service must be available to be useful and that
> there isn't any requirement for the service to be available.
>

The next sentence (which you omitted) provides the context.  Operators are
advised to be aware of denial-of-service considerations, and there's a
document referenced that provides useful information.  Depending on the
uptake of RDAP and the other services that begin to depend upon it, it
might become a DoS target.  Hardening against such attacks will be
important to begin with, but might become critical later.  I think this is
not a waste of space.


> In Section 3.4:
>
>   "Web services such as RDAP commonly use HTTP Over TLS [RFC2818] to
>    provide that protection by encrypting all traffic sent on the
>    connection between client and server."
>
> The above describes the protocol as a web service.
>

It is a web service, in as much as it uses web protocols.  Is there some
improvement you'd like to suggest?


>
>   "When this scheme is used, HTTP Over TLS MUST be used to protect the
>    client's credentials from disclosure while in transit.'
>
> The above repeats a "MUST" mentioned in a previous section.
>

True, this can be fixed by replacing it with a reference to Section 3.1.


>
> In Section 5:
>
>   "RDAP might need to be extended to provide this service in the future."
>
> This does not look like a security consideration.
>

Non-repudiation (which is the context of the paragraph from which that
sentence was taken) is one of the classic properties of security, so I
don't agree.  It's useful to point out to the reader that non-repudiation
is not provided by any of the capabilities discussed here, and its absence
might be conspicuous.



>
>   "Code injection refers to adding code into a computer system
>    or program to alter the course of execution."
>
> I can only wonder about who is the target audience after reading the above.
>

It's true that the specific things called out in that paragraph are not
specific to RDAP, but rather to anything built atop HTTP.  Do you suggest
something else, perhaps something more general like a statement that any
known HTTP-based attack might also affect an RDAP service?



>
> The security considerations section seems like an attempt to write
> something about security as there isn't nothing to say about the protocol.
>

SecDir often scratches its head when a document says very little, so what
you're saying is often the case.  However, sometimes it's enough to say
"This is built on top of HTTP, so all the security issues known about HTTP
and HTTPS also apply here."  Do you have a specific suggestion?


>
> Overall, the draft does not look like a technical specification.  It looks
> like the working group took FYI 36 as a template for designing a security
> service instead of thinking about security and designing a security service.
>

That seems a little sharp.

This draft is manifestly not a technical specification insofar as it does
not define a new protocol.  I would say it's partly a requirements document
and partly an applicability statement, and the latter at least is normally
a standards track document.

I don't know what "thinking about security" we are expected to do beyond
making use of the security services that have already been made available
to applications built atop HTTP.  Do you have any specific suggestions?

-MSK

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

<div dir=3D"ltr">Hi SM, thanks for your comments.=A0 I&#39;m shepherding th=
e document, so replies inline:<br><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Wed, Jul 24, 2013 at 12:21 PM, SM <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</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">According to Section 1, the Registration Dat=
a Access Protocol is a Lookup Format,<br>
JSON Responses and HTTP usage. =A0This looks like a weird protocol to me. =
=A0If the said protocol is HTTP + JSON (responses) it would be clearer to t=
he reader to explain that in one specification. =A0Section 1 mentions that:=
<br>

<br>
=A0 &quot;One goal of RDAP is to provide security services that do not exis=
t in<br>
=A0 =A0the WHOIS&quot;<br>
<br>
I don&#39;t see how adding a fourth document helps to achieve that goal.<br=
></blockquote><div><br></div><div>RDAP is far from the first protocol speci=
fication to exist across multiple RFCs, so this approach isn&#39;t uncommon=
.=A0 That said, I take it you believe the material here should be rolled in=
to one of the other documents?<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
In Section 3.1:<br>
<br>
=A0 &#39;To that end, RDAP clients and servers MUST implement the<br>
=A0 =A0authentication framework specified in &quot;HTTP Authentication:<br>
=A0 =A0Basic and Digest Access Authentication&quot; [RFC2617].&#39;<br>
<br>
This draft refers to the above authentication framework as the RDAP authent=
ication framework. =A0The draft then explains how the &quot;basic&quot; and=
 &quot;digest&quot; schemes work. =A0This is &quot;how-to&quot; stuff. =A0T=
he draft sets the following requirement:<br>

<br>
=A0 &#39;If the &quot;basic&quot; scheme is used, HTTP Over TLS [RFC2818] M=
UST be used<br>
=A0 =A0to protect the client&#39;s credentials from disclosure while in tra=
nsit<br>
=A0 (see Section 3.4).&#39;<br>
<br>
If I understood correctly HTTPS is needed for security only if the &quot;ba=
sic&quot; scheme&quot; is used.<br></blockquote><div><br></div><div>Correct=
, that&#39;s what it says.<br>=A0<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

=A0 &quot;RDAP SHOULD be capable of supporting future authentication method=
s<br>
=A0 =A0defined for use with HTTP.&quot;<br>
<br>
That sounds like a &quot;SHOULD CONSIDER&quot;. =A0Given how ill-defined th=
e protocol is I doubt that the above is actionable.<br></blockquote><div><b=
r></div><div>You said two important things here:<br><br></div><div>1) Can y=
ou please elaborate on why you think this is &quot;ill-defined&quot; and, i=
f possible, how this could be remedied?<br>
<br></div><div>2) Insofar as this draft amounts to a requirements document,=
 I take &quot;SHOULD be capable&quot; to mean the actual implementation nee=
ds to have hooks for the stated capability, or have a very good reason for =
not providing those hooks (e.g., the same capability is available some othe=
r way).<br>
<br><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
In Section 3.1.1:<br>
<br>
=A0 &quot;RDAP MAY include a federated authentication mechanism that permit=
s<br>
=A0 =A0a client to access multiple RDAP servers in the same federation<br>
=A0 =A0with one credential.&quot;<br>
<br>
Using an upper-case &quot;may&quot; does not bring much in terms of securit=
y. =A0The draft takes the stance that security is an optional feature.<br><=
/blockquote><div><br></div><div>More precisely, the draft takes the stance =
that federated authentication is an option.=A0 The working group doesn&#39;=
t feel the need to elevate this to SHOULD or MUST, likely because operators=
 might not be compelled to federate themselves with anyone for whatever loc=
al security or privacy reasons apply.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Section 3.1.1 looks like an executive summary for federated authentication.=
<br></blockquote><div><br></div><div>Right, and the benefits it provides in=
 the context of RDAP.=A0 Is that a criticism or an observation?=A0 What do =
you suggest?<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<br>
In Section 3.3:<br>
<br>
=A0 &quot;An RDAP service has to be available to be useful. =A0There are no=
 RDAP-<br>
=A0 =A0unique requirements to provide availability, but as a general<br>
=A0 =A0security consideration a service operator needs to be aware of the<b=
r>
=A0 =A0issues associated with denial of service.&quot;<br>
<br>
The text says that the service must be available to be useful and that ther=
e isn&#39;t any requirement for the service to be available.<br></blockquot=
e><div><br></div><div>The next sentence (which you omitted) provides the co=
ntext.=A0 Operators are advised to be aware of denial-of-service considerat=
ions, and there&#39;s a document referenced that provides useful informatio=
n.=A0 Depending on the uptake of RDAP and the other services that begin to =
depend upon it, it might become a DoS target.=A0 Hardening against such att=
acks will be important to begin with, but might become critical later.=A0 I=
 think this is not a waste of space.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<br>
In Section 3.4:<br>
<br>
=A0 &quot;Web services such as RDAP commonly use HTTP Over TLS [RFC2818] to=
<br>
=A0 =A0provide that protection by encrypting all traffic sent on the<br>
=A0 =A0connection between client and server.&quot;<br>
<br>
The above describes the protocol as a web service.<br></blockquote><div><br=
></div><div>It is a web service, in as much as it uses web protocols.=A0 Is=
 there some improvement you&#39;d like to suggest?<br>=A0<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">

<br>
=A0 &quot;When this scheme is used, HTTP Over TLS MUST be used to protect t=
he<br>
=A0 =A0client&#39;s credentials from disclosure while in transit.&#39;<br>
<br>
The above repeats a &quot;MUST&quot; mentioned in a previous section.<br></=
blockquote><div><br></div><div>True, this can be fixed by replacing it with=
 a reference to Section 3.1.<br>=A0 <br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">

<br>
In Section 5:<br>
<br>
=A0 &quot;RDAP might need to be extended to provide this service in the fut=
ure.&quot;<br>
<br>
This does not look like a security consideration.<br></blockquote><div><br>=
</div><div>Non-repudiation (which is the context of the paragraph from whic=
h that sentence was taken) is one of the classic properties of security, so=
 I don&#39;t agree.=A0 It&#39;s useful to point out to the reader that non-=
repudiation is not provided by any of the capabilities discussed here, and =
its absence might be conspicuous.<br>
<br>=A0 <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=A0 &quot;Code injection refers to adding code into a computer system<br>
=A0 =A0or program to alter the course of execution.&quot;<br>
<br>
I can only wonder about who is the target audience after reading the above.=
<br></blockquote><div><br></div><div>It&#39;s true that the specific things=
 called out in that paragraph are not specific to RDAP, but rather to anyth=
ing built atop HTTP.=A0 Do you suggest something else, perhaps something mo=
re general like a statement that any known HTTP-based attack might also aff=
ect an RDAP service?<br>
<br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The security considerations section seems like an attempt to write somethin=
g about security as there isn&#39;t nothing to say about the protocol.<br><=
/blockquote><div><br></div><div>SecDir often scratches its head when a docu=
ment says very little, so what you&#39;re saying is often the case.=A0 Howe=
ver, sometimes it&#39;s enough to say &quot;This is built on top of HTTP, s=
o all the security issues known about HTTP and HTTPS also apply here.&quot;=
=A0 Do you have a specific suggestion?<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
Overall, the draft does not look like a technical specification. =A0It look=
s like the working group took FYI 36 as a template for designing a security=
 service instead of thinking about security and designing a security servic=
e.<br>
</blockquote><div><br></div><div>That seems a little sharp.<br><br>This dra=
ft is manifestly not a technical specification insofar as it does not defin=
e a new protocol.=A0 I would say it&#39;s partly a requirements document an=
d partly an applicability statement, and the latter at least is normally a =
standards track document.<br>
<br></div><div>I don&#39;t know what &quot;thinking about security&quot; we=
 are expected to do beyond making use of the security services that have al=
ready been made available to applications built atop HTTP.=A0 Do you have a=
ny specific suggestions?<br>
<br>-MSK<br></div></div></div></div>

--001a11c34302baa56b04e336bee6--

From john-ietf@jck.com  Mon Aug  5 10:39:13 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A07CE21F9E3F for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 10:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Level: 
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5WRWTfbqmAlo for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 10:39:00 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D9B8821F9DCE for <ietf@ietf.org>; Mon,  5 Aug 2013 10:38:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V6OkF-0005y3-FD for ietf@ietf.org; Mon, 05 Aug 2013 13:38:59 -0400
Date: Mon, 05 Aug 2013 13:38:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
Message-ID: <3FBCE2280D3F2550A2B3043F@JcK-HP8200.jck.com>
In-Reply-To: <14937.1375712237@sandelman.ca>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com> <14937.1375712237@sandelman.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 17:39:13 -0000

Hi.

I seem to have missed a lot of traffic since getting a few
responses yesterday.  I think the reasons why slides should be
available well in advance of the meeting have been covered well
by others.  And, as others have suggested, I'm willing to see
updates to those slides if things change in the hours leading
up to the meeting, but strongly prefer that those updates come
as new alides with update-type "numbers" or other
identification rather than new decks.  In other words, if a
deck is posted in advance with four slides numbered 1, 2, 3,
and 4, and additional information is needed for 3, I'd prefer
to see the updated deck consist of slides 1, 2, 3, 3a, 3b, 4 or
1, 2, 3a, 3b, 3c, 4, rather than 1, 2, 3, 4, 5, 6.  I also
prefer consolidated decks but, if WG chairs find that too
difficult, I'm happy to do my own consolidating if everyting is
available enough in advance for me to do sol

Almost independent of the above, the idea that one should just
watch the slides on Meetecho implies that Meetecho is
available in every session (it isn't) and that everything
works.  In addition, they either need the slides in advance or
need to be able to broadcast real-time video at a resolution
that makes the slides readable.  The latter was not the case
last week in some of the sessions in which Meetecho was
transmitting the slides sometimes due in part to interesting
speaker-training issues.

The reasons to discourage anonymity aren't just "patent
nonsense" (although that should be sufficient and I rather like
the pun).  Despite all we say and believe about individual
participation, the IETF has a legitimate need to understand the
difference between comments on a specification from an audience
with diverse perspectives and organized campaigns or a loud
minority with a shared perspective.  That requires
understanding whether speakers are largely independent of each
other (versus what have sometimes been referred to as sock
puppets for one individual) or whether they are part of an
organization mounting a systematic campaign to get a particular
position adopted (or not adopted).  The latter can also raise
some rather nasty antitrust / anti-competitiveness issues.
Clear identification of speakers, whether in the room or
remote, can be a big help in those regards, even though it
can't prevent all problems.  And the IETF having a policy that
requires clear identification at least establishes that we,
organizationally and procedurally, are opposed to nefarious,
deceptive, and posslbly illegal behavior.

A rule about having slides well in advance helps in another
way: slides that are bad news for some reasons but posted
several days in advance of the meeting provide opportunities
for comments and adjustments (from WG Chairs and others).  Ones
that are posted five minutes before (or 10 minutes after) a
session lose that potential advantage.  Again, I don't think we
should get rigid about it: if slides are posted in advance
and then supplemented or revised after feedback is received,
everyone benefits.

I want to stress that, while I think registration of remote
people who intend to participate is desirable for many reasons,
I think trying to condition microphone use (either remote on
in-room) with proof of registration and mapping of names would
be looking for a lot of trouble with probably no significant
benefits.

best,
   john





From jmpolk@cisco.com  Mon Aug  5 11:36:31 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03AE721F8F3C for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 fEJr40ELRPIh for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 11:36:25 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C0E2621F8D90 for <ietf@ietf.org>; Mon,  5 Aug 2013 11:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4370; q=dns/txt; s=iport; t=1375727784; x=1376937384; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=3eiYNUT4PU7uufVxtWYeMaig3FcUEwEi1t+etATp5lQ=; b=VeGwh4y3bOnqt54qZnj1Dt9YahiqtkcypK6abO9MIfuKgkUOAHThJYC8 v9lOCCWo9HcOuFa11y7831OSzSismOWjN/JU969NyslTEGqR32LY5A2L3 5Bgu/BMqLTKo3rkhieiOwjSeBg0Npv+9/xkzIF2o1yeHQ6ekhKO19c27i s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhsFACPw/1GtJV2d/2dsb2JhbABbgwa/eoEhFnSCJAEBAQQ4Ak8HBBgJFRAPCj4GASwCh3S1PJAghA0DiSqgBYM1Hg
X-IronPort-AV: E=Sophos;i="4.89,820,1367971200"; d="scan'208";a="243686310"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-7.cisco.com with ESMTP; 05 Aug 2013 18:36:24 +0000
Received: from jmpolk-WS.cisco.com ([10.89.8.39]) (authenticated bits=0) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r75IaNlW019010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 5 Aug 2013 18:36:24 GMT
Message-Id: <201308051836.r75IaNlW019010@rcdn-core-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 05 Aug 2013 13:36:04 -0500
To: John C Klensin <john-ietf@jck.com>, <ietf@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: procedural question with remote participation
In-Reply-To: <3FBCE2280D3F2550A2B3043F@JcK-HP8200.jck.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com> <14937.1375712237@sandelman.ca> <3FBCE2280D3F2550A2B3043F@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 18:36:31 -0000

At 12:38 PM 8/5/2013, John C Klensin wrote:
>Hi.
>
>I seem to have missed a lot of traffic since getting a few
>responses yesterday.  I think the reasons why slides should be
>available well in advance of the meeting have been covered well
>by others.  And, as others have suggested, I'm willing to see
>updates to those slides if things change in the hours leading
>up to the meeting, but strongly prefer that those updates come
>as new alides with update-type "numbers" or other
>identification rather than new decks.  In other words, if a
>deck is posted in advance with four slides numbered 1, 2, 3,
>and 4, and additional information is needed for 3, I'd prefer
>to see the updated deck consist of slides 1, 2, 3, 3a, 3b, 4 or
>1, 2, 3a, 3b, 3c, 4, rather than 1, 2, 3, 4, 5, 6.

How exactly do you do this in pptx? Numbering slides is a linear 
operation AFAICT, and it's binary (it's either on or off). Please 
educate me if I'm wrong; lord knows I don't know don't know how to do 
everything flag/setting in powerpoint...

And, in my 8 years as TSVWG chair, I've rarely had completely new 
individual slides sprinkled throughout an existing deck. Rather, I've 
received updated slides - each with part of their content altered. 
Does this fall into your desire for a "3a", or is that just "3" 
(because 3a means an entirely new slide from scratch)?

BTW - I'm very much *not* in favor of stipulating to my WG that 
slides must be turned in 7 days in advance of a TSVWG meeting. I 
personally think no more than a 48 hour advanced window should ever 
be considered.

James

>I also
>prefer consolidated decks but, if WG chairs find that too
>difficult, I'm happy to do my own consolidating if everyting is
>available enough in advance for me to do sol
>
>Almost independent of the above, the idea that one should just
>watch the slides on Meetecho implies that Meetecho is
>available in every session (it isn't) and that everything
>works.  In addition, they either need the slides in advance or
>need to be able to broadcast real-time video at a resolution
>that makes the slides readable.  The latter was not the case
>last week in some of the sessions in which Meetecho was
>transmitting the slides sometimes due in part to interesting
>speaker-training issues.
>
>The reasons to discourage anonymity aren't just "patent
>nonsense" (although that should be sufficient and I rather like
>the pun).  Despite all we say and believe about individual
>participation, the IETF has a legitimate need to understand the
>difference between comments on a specification from an audience
>with diverse perspectives and organized campaigns or a loud
>minority with a shared perspective.  That requires
>understanding whether speakers are largely independent of each
>other (versus what have sometimes been referred to as sock
>puppets for one individual) or whether they are part of an
>organization mounting a systematic campaign to get a particular
>position adopted (or not adopted).  The latter can also raise
>some rather nasty antitrust / anti-competitiveness issues.
>Clear identification of speakers, whether in the room or
>remote, can be a big help in those regards, even though it
>can't prevent all problems.  And the IETF having a policy that
>requires clear identification at least establishes that we,
>organizationally and procedurally, are opposed to nefarious,
>deceptive, and posslbly illegal behavior.
>
>A rule about having slides well in advance helps in another
>way: slides that are bad news for some reasons but posted
>several days in advance of the meeting provide opportunities
>for comments and adjustments (from WG Chairs and others).  Ones
>that are posted five minutes before (or 10 minutes after) a
>session lose that potential advantage.  Again, I don't think we
>should get rigid about it: if slides are posted in advance
>and then supplemented or revised after feedback is received,
>everyone benefits.
>
>I want to stress that, while I think registration of remote
>people who intend to participate is desirable for many reasons,
>I think trying to condition microphone use (either remote on
>in-room) with proof of registration and mapping of names would
>be looking for a lot of trouble with probably no significant
>benefits.
>
>best,
>    john


From brian.e.carpenter@gmail.com  Mon Aug  5 13:28:48 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDADB21F9F08; Mon,  5 Aug 2013 13:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.514
X-Spam-Level: 
X-Spam-Status: No, score=-102.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HG1X7W0K8T3k; Mon,  5 Aug 2013 13:28:48 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 401EF21F9BD3; Mon,  5 Aug 2013 13:28:48 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id lb1so3738067pab.26 for <multiple recipients>; Mon, 05 Aug 2013 13:28:47 -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=wlSWn43FLpAK5Az2kn408OXiYv9r7JRP2zoukqC44Wk=; b=nilA+9A9w8uc+7SC4P9tSzcKZ05zz8GskcPQJk5y9/+k3gIBtQZCtymXLkUkxUVbIV nT39SOuVoZGslcyX5baa/DMGagTkcEAZ73KkiAO9QPktF9E9bWsE+9ydkqiLnqbyJFWk CwBdSY1fivMnxM5BBTx5jldCdQgP9Bget8rscUyZNYi1ohSGTjn/tqiruZ3yISJGt62C DiHAACPJL/Lu0Jj+2zGQEEl+txi8rYvSYOud7pPWHstedOYiH7Tz25biQgHFMq0gWJat z0sicVv8ASo9/+mUk5B9vr9GERziilVieaD4lbAxV0br/Bu/jj1TNGG6dS+m97m4ipAS 96Fg==
X-Received: by 10.68.253.227 with SMTP id ad3mr20481231pbd.63.1375734527862; Mon, 05 Aug 2013 13:28:47 -0700 (PDT)
Received: from [192.168.178.20] (38.198.69.111.dynamic.snap.net.nz. [111.69.198.38]) by mx.google.com with ESMTPSA id oe6sm801567pbb.20.2013.08.05.13.28.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 05 Aug 2013 13:28:46 -0700 (PDT)
Message-ID: <52000AFD.7070509@gmail.com>
Date: Tue, 06 Aug 2013 08:28:45 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [Trustees] The Trust Agreement
References: <20130805151125.199D518C123@mercury.lcs.mit.edu>
In-Reply-To: <20130805151125.199D518C123@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: trustees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 20:28:49 -0000

On 06/08/2013 03:11, Noel Chiappa wrote:
>     > From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> 
>     > Thanks for the careful explanations.
> 
> I'll second that; it does seem that some tweaking may be in order.
> 
>     > Clearly the Trust shouldn't have blanket permission to abandon or
>     > dispose of assets
> 
> When the time comes to draft actual wording, I would suggest that there be a
> requirement for a notification to the IETF-Announce list at least one month
> (or so?) prior to any actual disposal or abandonment, or completion of any
> agreement to dispose. (Maybe only for IP, and not real property too, such as
> old servers, etc?) I can't imagine the Trust would be disposing of stuff very
> often, so I think this would be a reasonable requirement.

Agreed; that's very much in the spirit of how we set up the Trust
to be responsive to the community. It doesn't seem like the sort of detail
to be embedded in the Trust Agreement though - more like part of a tiny
addendum to BCP 101. (Since I have raised that question, I hereby volunter
to draft it if necessary.)

    Brian

From stephen.farrell@cs.tcd.ie  Mon Aug  5 18:07:13 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC5021F9DAB for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 18:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g4ZqDuuZTZtH for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 18:07:05 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 086E621F925A for <ietf@ietf.org>; Mon,  5 Aug 2013 18:06:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E8CF3BE55; Tue,  6 Aug 2013 02:06:46 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7h9dga2I0oEs; Tue,  6 Aug 2013 02:06:46 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.44.64.202]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id EDD8DBE4D; Tue,  6 Aug 2013 02:06:45 +0100 (IST)
Message-ID: <52004C1B.60509@cs.tcd.ie>
Date: Tue, 06 Aug 2013 02:06:35 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>,  Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com> <14937.1375712237@sandelman.ca> <3FBCE2280D3F2550A2B3043F@JcK-HP8200.jck.com>
In-Reply-To: <3FBCE2280D3F2550A2B3043F@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 01:07:13 -0000

On 08/05/2013 12:31 PM, Hadriel Kaplan wrote:
>  but at least one anonymous jabber participant (named "Guest") did
> remotely speak multiple times at the mic on one of the RAI working
> group sessions this past week (at RTCWEB if I recall).  I was
> personally ok with it, but it was awkward.

Ah. I wasn't aware of that. Not stylish at all IMO on the part of
whoever was "Guest". I'd be confident that the chairs and
participants will deal with it ok though. We do manage to deal
with silliness (e.g. people with bad ideas) all the time, so I
don't see why this'd pose an insurmountable problem to a wg.

On 08/05/2013 06:38 PM, John C Klensin wrote:
> The reasons to discourage anonymity aren't just "patent
> nonsense" (although that should be sufficient and I rather like
> the pun).  

Thanks. The pun was accidental as it happens, but I did leave
it in after I spotted it :-)

Puns aside, its an important point. Most patents are nonsense
(in terms of being really inventive) and we shouldn't base
our processes anywhere near primarily on the existence of that
nonsense.

> Despite all we say and believe about individual
> participation, the IETF has a legitimate need to understand the
> difference between comments on a specification from an audience
> with diverse perspectives and organized campaigns or a loud
> minority with a shared perspective.

Good point. We have similar issues with folks who do lots of
contract work I guess. But, IMO we should first make sure we can
hear the good points that are to be made, and only then modulate
our reactions to those in terms of who-pays-whom or whatever.

Put another way, regardless of patents or who's paying, if
someone (even anonymously) comes up with a really good technical
point, then we do have to pay attention. But I think we do do that.

In contrast, I think the real challenge remote participants face
is being heard. And when/if we solve that problem, I suspect that
remote participants with bad ideas will be a far worse problem
than those who'd like to submarine a patent or further a subtle
corporate agenda.

So again that leads me back to trying to encourage folks to just
make the tools better for us all and to only then try figure out
how we need to manage that. Perhaps Hadriel's anecdote above
means that how we use jabber is, after about a decade, now mature
enough that we ought think more about how we formalise its use.
I'm ok with waiting another longish time before even thinking
about how to do the same with successful inbound audio for
example.

S.


From john-ietf@jck.com  Mon Aug  5 19:52:43 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 160E221F9C59 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 19:52:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.647
X-Spam-Level: 
X-Spam-Status: No, score=-102.647 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QS8JWYFABmJJ for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 19:52:37 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3564621F92A5 for <ietf@ietf.org>; Mon,  5 Aug 2013 19:52:37 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V6XNu-0006ap-Bo; Mon, 05 Aug 2013 22:52:30 -0400
Date: Mon, 05 Aug 2013 22:52:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: procedural question with remote participation
Message-ID: <A98CBB828F3FE217424F3CFE@JcK-HP8200.jck.com>
In-Reply-To: <52004C1B.60509@cs.tcd.ie>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <6EE46715-DDCD-4D26-9644-F0FC317FB122@oracle.com> <51FEDF60.2010902@gmail.com> <14937.1375712237@sandelman.ca> <3FBCE2280D3F2550A2B3043F@JcK-HP8200.jck.com> <52004C1B.60509@cs.tcd.ie>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 02:52:43 -0000

--On Tuesday, August 06, 2013 02:06 +0100 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
> On 08/05/2013 06:38 PM, John C Klensin wrote:
>> The reasons to discourage anonymity aren't just "patent
>> nonsense" (although that should be sufficient and I rather
>> like the pun).  
> 
> Thanks. The pun was accidental as it happens, but I did leave
> it in after I spotted it :-)
> 
> Puns aside, its an important point. Most patents are nonsense
> (in terms of being really inventive) and we shouldn't base
> our processes anywhere near primarily on the existence of that
> nonsense.

Agreed, modulo observations about how much time we seem to put
into fine-tuning IPR policies and devising threats to make to
those who don't seem inclined to comply.

>> Despite all we say and believe about individual
>> participation, the IETF has a legitimate need to understand
>> the difference between comments on a specification from an
>> audience with diverse perspectives and organized campaigns or
>> a loud minority with a shared perspective.
> 
> Good point. We have similar issues with folks who do lots of
> contract work I guess. But, IMO we should first make sure we
> can hear the good points that are to be made, and only then
> modulate our reactions to those in terms of who-pays-whom or
> whatever.

Indeed.

> Put another way, regardless of patents or who's paying, if
> someone (even anonymously) comes up with a really good
> technical point, then we do have to pay attention. But I think
> we do do that.

When, as you indirectly point out, we can "hear" them.

> In contrast, I think the real challenge remote participants
> face is being heard. And when/if we solve that problem, I
> suspect that remote participants with bad ideas will be a far
> worse problem than those who'd like to submarine a patent or
> further a subtle corporate agenda.

Of course, that is also true of participants who show up and
more f2f meetings.

> So again that leads me back to trying to encourage folks to
> just make the tools better for us all and to only then try
> figure out how we need to manage that. Perhaps Hadriel's
> anecdote above means that how we use jabber is, after about a
> decade, now mature enough that we ought think more about how
> we formalise its use. I'm ok with waiting another longish time
> before even thinking about how to do the same with successful
> inbound audio for example.

I'm actually not a big fan of inbound audio, at least not yet.
It is subject to the same technical and operational issues that
make outbound audio fragile, including the difficulties of clear
and "standard" pronunciation plus the same "how to raise your
hand, get in line, or otherwise ask for the floor" issues that
Jabber does.  But, if we are going to rely on Jabber for input,
we need to move toward treating it as a source of input with the
same priority as those in the room (and relatively more real
time), not something that is a nice-to-have when it happens to
work.

best,
    john




From jcurran@istaff.org  Mon Aug  5 19:58:32 2013
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBEC421F9EC4 for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 19:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7vIJpRC0Lfi for <ietf@ietfa.amsl.com>; Mon,  5 Aug 2013 19:58:27 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3148A21F9F96 for <ietf@ietf.org>; Mon,  5 Aug 2013 19:58:24 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=[192.168.1.6]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1V6XTb-000L8h-IA; Tue, 06 Aug 2013 02:58:23 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19v2OtCNOcjs/slM3SnYZ70
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: John Curran <jcurran@istaff.org>
In-Reply-To: <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
Date: Mon, 5 Aug 2013 22:58:20 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <95B816F2-7B6D-405B-8695-9244FEF0576F@istaff.org>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 02:58:32 -0000

On Aug 4, 2013, at 2:20 PM, John C Klensin <john-ietf@jck.com> wrote:

> I also note that the 1 week cutoff that Michael suggests would,
> in most cases, eliminate "had no choice without impeding WG
> progress" as an excuse.  A week in advance of the meeting, there
> should be time, if necessary to find someone else to organize
> the presentation or discussion (and to prepare and post late
> slides that are still posted before the meeting if needed).  If
> it is necessary to go ahead without the slides, it is time to
> get a warning to that effect and maybe an outline of the issues
> to be discussed into the agenda.    If the WG's position is that
> slides 12 or 24 hours before the WG's session are acceptable,
> then the odds are high that one glitch or another will trigger a
> "well, there are no slides posted but they are available in the
> room and the discussion is important" decision.

John - 
 
 I've participated in many IETFs in person but have been remote
 for the last two meetings.  I agree that the slides are essential
 in many cases for following the discussion, and furthermore agree 
 that it is a complete pain to have to hunt for the slides when they
 haven't been posted and are instead just in the room, or on the list, 
 or at some URL being passed around, etc.

 Noting all that agreement, I don't support a "one week" slide cutoff;
 the downside of not having a presentation slot as a result would be 
 a disproportionate impact to working group productivity... delaying
 presentation of an important topic for 4 months just because the slides 
 showed up late (but still days before the actual session) would be 
 creating a purely administrative and artificial impediment to getting
 things done.

 Now, something in ietf tools that emailed the WG Chairs (and AD?) noting
 that slides aren't up for presentations occurring _tomorrow_ and/or kept 
 track of presenters with chronic problems missing the deadline getting 
 their slide decks in the night before might be very useful, and help 
 quite a bit with improving remote participants ability to follow along.

My .02,
/John

From daedulus@btconnect.com  Tue Aug  6 02:37:59 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A42D11E80E0 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 02:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.17
X-Spam-Level: 
X-Spam-Status: No, score=-2.17 tagged_above=-999 required=5 tests=[AWL=-1.429,  BAYES_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hjib1qqJZjAo for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 02:37:53 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0249.outbound.messaging.microsoft.com [213.199.154.249]) by ietfa.amsl.com (Postfix) with ESMTP id 2512711E80E1 for <ietf@ietf.org>; Tue,  6 Aug 2013 02:37:49 -0700 (PDT)
Received: from mail225-DB9-R.bigfish.com (10.174.16.237) by DB9EHSOBE020.bigfish.com (10.174.14.83) with Microsoft SMTP Server id 14.1.225.22; Tue, 6 Aug 2013 09:37:47 +0000
Received: from mail225-DB9 (localhost [127.0.0.1])	by mail225-DB9-R.bigfish.com (Postfix) with ESMTP id C76A7340268; Tue,  6 Aug 2013 09:37:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail225-DB9 (localhost.localdomain [127.0.0.1]) by mail225-DB9 (MessageSwitch) id 1375781841195786_3737; Tue,  6 Aug 2013 09:37:21 +0000 (UTC)
Received: from DB9EHSMHS003.bigfish.com (unknown [10.174.16.237])	by mail225-DB9.bigfish.com (Postfix) with ESMTP id 2CC77E003F; Tue,  6 Aug 2013 09:37:21 +0000 (UTC)
Received: from DBXPRD0711HT003.eurprd07.prod.outlook.com (157.56.254.181) by DB9EHSMHS003.bigfish.com (10.174.14.13) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 6 Aug 2013 09:37:19 +0000
Received: from AMXPRD0111HT004.eurprd01.prod.exchangelabs.com (157.56.250.117) by pod51017.outlook.com (10.255.178.36) with Microsoft SMTP Server (TLS) id 14.16.341.1; Tue, 6 Aug 2013 09:37:19 +0000
Message-ID: <000401ce9288$7f210100$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: John R Levine <johnl@taugh.com>, Yoav Nir <ynir@checkpoint.com>
References: <20130804201105.3986.qmail@joyce.lan><65A4EBE4-B342-46B3-82C6-8A81674C3EC0@checkpoint.com> <alpine.BSF.2.00.1308041746210.2773@joyce.lan>
Subject: Re: Speaking of VAT
Date: Tue, 6 Aug 2013 10:29:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 06 Aug 2013 09:37:59 -0000

---- Original Message -----
From: "John R Levine" <johnl@taugh.com>
To: "Yoav Nir" <ynir@checkpoint.com>
Cc: <ietf@ietf.org>
Sent: Sunday, August 04, 2013 10:47 PM
Subject: Re: Speaking of VAT
>
> Ray said the tax guys told him the IETF would get back about half of
the
> VAT it paid.  That's unrelated to what anyone can reclaim.
>
> My understanding is that Germany has reciprocal VAT agreements with a
> bunch of countries so if your employer is in one of those countries it
may
> be able to reclaim, but since the US isn't one of them I haven't
looked in
> detail.

John

VAT is a European Union tax that all member states are required to levy
on the supply of goods and services, although there is flexibility about
the rate it is levied at and what it is levied on.

As a VAT-registered business, mandatory when turnover exceeds a
threshold, I tot up the VAT I have charged and the VAT I have paid and
the difference goes to (or comes back from) the tax authorities.  This
applies across the European Union so there is no problem about where the
VAT is
paid - any European Union country will do - and equally, VAT must be
charged
whereever a supply is made.

There is no requirement to charge VAT on the export of goods outside the
European Union - technically, they are zero-rated - but in general, it
must be charged on the export of services.  The exemption on the export
of goods has generated a lot of fraud in the past few years, especially
on high
value goods such as computer chips, and so has
attracted the attention of the tax authorities.

Only businesses can reclaim the tax - private individuals cannot.

VAT as implemented in the European Union is an administrative and
bureaucratic nightmare, generating work for armies of lawyers,
accountants and administrators.  I would be wary of extrapolating
any aspect of European VAT to taxes of the same name in other
parts of the world (smile - things could be worse:-).  The European
Union's VAT was the first, I think.

Tom Petch

> R's,
> John
>



From moore@network-heretics.com  Tue Aug  6 06:08:20 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9C6721F9E46 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 06:08: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 BkhW5Wptl0p9 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 06:08:15 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id B988A21F9E36 for <ietf@ietf.org>; Tue,  6 Aug 2013 06:08:13 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 979DE20D0B for <ietf@ietf.org>; Tue,  6 Aug 2013 09:08:12 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Tue, 06 Aug 2013 09:08:12 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=DLNai2xyObHGtSXkEpt7WT QaLAU=; b=bXfQaFPF5/feqMOFOTnSzAnbXKZ3mRVBnSgEd2C7Oqg/dne1nz/X3J 9NDRpU1ZlPewxMQHUSzDY2cVyAY+JhhTOts0YVJBzpLz5uuac0ARfWb+cASxVQcO c9kpswHkuW+yoURBSbjzVf51t750Yh4SMYRAZs9NuDHMhmHr5/16s=
X-Sasl-enc: RFX4HTxNsED+WQjXf3N8ZHSHL7v05lu3f4rNQ3eKiqFy 1375794492
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0C2EBC00E7F; Tue,  6 Aug 2013 09:08:11 -0400 (EDT)
Message-ID: <5200F53A.6020408@network-heretics.com>
Date: Tue, 06 Aug 2013 09:08:10 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 13:08:21 -0000

On 08/04/2013 02:54 PM, Ted Lemon wrote:
> While I think getting slides in on time is great for a lot of reasons, reading the slides early isn't that important.   What is important is that remote people see the slides at the same time as local people.   For that, it seems to me that Meetecho support does exactly what is needed.   You just follow the slideshow online, along with the audio.

I agree that remote people should see the slides at the same time as 
local people, except that I think that in both cases this should be well 
before the meeting.  The slides shouldn't be shown at the meeting unless 
needed to illustrate a point of active discussion.

People keep acting as if the purpose of these meetings - the reason 
people spend thousands of euro and travel thousands of km - is to watch 
slides.

Keith


From Aaron.Ding@cl.cam.ac.uk  Tue Aug  6 06:49:59 2013
Return-Path: <Aaron.Ding@cl.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4469D21F967C for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 06:49: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.745, BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JzZ5goxNo1he for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 06:49:53 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id 5238921F8994 for <ietf@ietf.org>; Tue,  6 Aug 2013 06:49:53 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-1b.csi.cam.ac.uk ([131.111.9.33]:54461) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtp id 1V6he4-0002qA-0k (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 14:49:52 +0100
Received: from [127.0.0.1] (helo=webmail-1.hermes.cam.ac.uk) by webmail-1b.csi.cam.ac.uk with esmtp id 1V6he4-000P64-5U (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 14:49:52 +0100
Received: from c0175.aw.cl.cam.ac.uk ([128.232.100.175]) by webmail-1.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 06 Aug 2013 14:49:52 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 06 Aug 2013 14:49:52 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: moore@network-heretics.com
Subject: Re: procedural question with remote participation
Message-ID: <4fbf72fd1c87f455ebb6ea487fdd8c5e@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.2
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 13:49:59 -0000

On 06/08/13 14:08, Keith Moore wrote:
> On 08/04/2013 02:54 PM, Ted Lemon wrote:
>> While I think getting slides in on time is great for a lot of reasons, 
>> reading the slides early isn't that important.   What is important is 
>> that remote people see the slides at the same time as local people.   
>> For that, it seems to me that Meetecho support does exactly what is 
>> needed.   You just follow the slideshow online, along with the audio.
> 
> I agree that remote people should see the slides at the same time as 
> local people, except that I think that in both cases this should be 
> well before the meeting.  The slides shouldn't be shown at the meeting 
> unless needed to illustrate a point of active discussion.
> 
> People keep acting as if the purpose of these meetings - the reason 
> people spend thousands of euro and travel thousands of km - is to watch 
> slides.


interesting.. out of pure curiosity, "People keep acting", you mean, 
who?

Thanks,
Aaron


PS: this whole tread is about the key word "slides". If one of the key 
purposes is NOT about presentation, what are talking about here? plz 
correct me, if I got it wrong...


> 
> Keith

From johnl@iecc.com  Tue Aug  6 07:15:09 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCA0521F9A38 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 07:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.332
X-Spam-Level: 
X-Spam-Status: No, score=-110.332 tagged_above=-999 required=5 tests=[AWL=0.867, 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 6vBGOHln4kkS for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 07:15: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 4B7EF21F8EA8 for <ietf@ietf.org>; Tue,  6 Aug 2013 07:15:00 -0700 (PDT)
Received: (qmail 20949 invoked from network); 6 Aug 2013 14:14:43 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 6 Aug 2013 14:14:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520104d3.xn--hew.k1308; i=johnl@user.iecc.com; bh=GyAf6xRugbJpWGbWsy8RYlLTAwW9RhOaUIh9cB7+QgI=; b=Msze6MZIgu6aLPnu3rg80lu7iPaNnETkbwZEpJqbPwxGgLSi16RFYlVr+L47oVD4GCYIWZyLYiavITzmlj7eU+6INzWQrM/T2o0muLRJ+hrFcyumzjtaOLFyPQnkprl8ppSYr1HruzxDX4nLdnN/mQLIHxhCTJTykOfJLisFxU2JDrIsPbGW9lspJ36OpIyGms6Ticw8yznk4yCIrnJ3u086XA7jTKKfT8VBjnRQElbR1nwJT3KZIykfJaHr3JTP
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520104d3.xn--hew.k1308; olt=johnl@user.iecc.com; bh=GyAf6xRugbJpWGbWsy8RYlLTAwW9RhOaUIh9cB7+QgI=; b=MIHZuEncRmzN2Z08CHzyU0IzKpRM7UQ/RoYT6JPLyRyFQ+w4Q4P9+0UzZYzbUMpsb6BLHnIEprMTbu37s/iNcZy012G2PjLssfufjyqcWbom8btOmcyUO6wDjMmeCjS4knLjmRzjxAV14PGLL9pS5xet3An84UpDwTVO5OxZIs5GJnMfI3VdlfvlDJmpeS2M+drpN6iBRiiYEniX1L/5pwlD/V+Hq58Wq1oJAtw1dzb6ySpUmUaeRTNsV4CsI9ab
Date: 6 Aug 2013 14:14:21 -0000
Message-ID: <20130806141421.35149.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Speaking of VAT
In-Reply-To: <000401ce9288$7f210100$4001a8c0@gateway.2wire.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 14:15:09 -0000

>> My understanding is that Germany has reciprocal VAT agreements with a
>> bunch of countries so if your employer is in one of those countries it may
>> be able to reclaim, but since the US isn't one of them I haven't looked in
>> detail.
>
>John
>
>VAT is a European Union tax that all member states are required to levy
>on the supply of goods and services, although there is flexibility about
>the rate it is levied at and what it is levied on. ...

Yes, but there are also reciprocal agreements separate from the usual
credit for VAT paid, with non-EU countries including Israel.  The page
that Ray pointed to describes this.

R's,
John

From Aaron.Ding@cl.cam.ac.uk  Tue Aug  6 07:26:16 2013
Return-Path: <Aaron.Ding@cl.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9245421F9D52 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 07:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id myWQgNQ9dQuL for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 07:26:10 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 353A621F99BE for <ietf@ietf.org>; Tue,  6 Aug 2013 07:26:07 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-1b.csi.cam.ac.uk ([131.111.9.33]:47692) by ppsw-33.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtp id 1V6iD7-0007R4-iH (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 15:26:05 +0100
Received: from [127.0.0.1] (helo=webmail-1.hermes.cam.ac.uk) by webmail-1b.csi.cam.ac.uk with esmtp id 1V6iD7-000UdK-LQ (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 15:26:05 +0100
Received: from c0175.aw.cl.cam.ac.uk ([128.232.100.175]) by webmail-1.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 06 Aug 2013 15:26:05 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 06 Aug 2013 15:26:05 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
Message-ID: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.2
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 14:26:16 -0000

to clarify, imho:

presentation != slides

making the best out of IETF meetings for both f2f and remote 
participants is hard and yet worth our try.

back to our slides shipping tread, everybody has own opinion toward 
whether "I" prefer/believe the slides should be uploaded earlier or not 
so, and obeying our own principle when doing our own presentation 
materials is definitely appreciated, but don't force it upon others 
please. (of course WG chairs can recommend WG presenters to follow the 
same agenda for better coordination within the group, and in that case 
f2f and remote participants can be duly notified via WG mailing list, in 
advance)

Thanks,
Aaron


On 06/08/13 14:49, Aaron Yi DING wrote:
> On 06/08/13 14:08, Keith Moore wrote:
>> On 08/04/2013 02:54 PM, Ted Lemon wrote:
>>> While I think getting slides in on time is great for a lot of 
>>> reasons, reading the slides early isn't that important.   What is 
>>> important is that remote people see the slides at the same time as 
>>> local people.   For that, it seems to me that Meetecho support does 
>>> exactly what is needed.   You just follow the slideshow online, along 
>>> with the audio.
>> 
>> I agree that remote people should see the slides at the same time as 
>> local people, except that I think that in both cases this should be 
>> well before the meeting.  The slides shouldn't be shown at the meeting 
>> unless needed to illustrate a point of active discussion.
>> 
>> People keep acting as if the purpose of these meetings - the reason 
>> people spend thousands of euro and travel thousands of km - is to 
>> watch slides.
> 
> 
> interesting.. out of pure curiosity, "People keep acting", you mean, 
> who?
> 
> Thanks,
> Aaron
> 
> 
> PS: this whole tread is about the key word "slides". If one of the key 
> purposes is NOT about presentation, what are talking about here? plz 
> correct me, if I got it wrong...
> 
>> 
>> Keith


From andrewf@plixer.com  Tue Aug  6 08:06:33 2013
Return-Path: <andrewf@plixer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28AB021F9A0C for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 08:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 iY4K4PYbY6WZ for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 08:06:28 -0700 (PDT)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id C2D3821F99A0 for <ietf@ietf.org>; Tue,  6 Aug 2013 08:06:27 -0700 (PDT)
Received: from [10.11.1.15] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 6 Aug 2013 11:06:25 -0400
Message-ID: <520110F0.5030100@plixer.com>
Date: Tue, 6 Aug 2013 11:06:24 -0400
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com>
In-Reply-To: <5200F53A.6020408@network-heretics.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 15:06:33 -0000

On 08/06/2013 09:08 AM, Keith Moore wrote:
> On 08/04/2013 02:54 PM, Ted Lemon wrote:
>> While I think getting slides in on time is great for a lot of 
>> reasons, reading the slides early isn't that important.   What is 
>> important is that remote people see the slides at the same time as 
>> local people.   For that, it seems to me that Meetecho support does 
>> exactly what is needed.   You just follow the slideshow online, along 
>> with the audio.
>
> I agree that remote people should see the slides at the same time as 
> local people, except that I think that in both cases this should be 
> well before the meeting.  The slides shouldn't be shown at the meeting 
> unless needed to illustrate a point of active discussion.
>
> People keep acting as if the purpose of these meetings - the reason 
> people spend thousands of euro and travel thousands of km - is to 
> watch slides.
Hi Keith,

I think this sort of misses the point.  At least for me as a remote 
participant.

I'm not interested in arguing about whether slides are good or bad. I am 
interested in following (and being involved) in the WG meeting.  When 
there are slides I want to be able to see them clearly from my remote 
location.  Having them integrated with Meetecho works fine.  Having 
slides and other materials available to download ahead of time is also 
OK.  I can work with what is available, but having slides brought to the 
meeting on USB (it happens) does me no good.  Also people using pointing 
devices, that can't be seen remotely, to point to areas on each slide 
doesn't help.

As of today when the slides are available (or if there are no slides and 
just talk) I can follow WG meetings quite well.  Being able to actively 
engage in any discussion remotely is, IMO, pretty much limited to the 
mailing lists.  Getting involved in an active discussion at a WG meeting 
remotely is currently difficult at best and impossible at worst.

I'm all in favor of discussions in WG meetings, but from where I sit we 
still have a ways to go to fully integrate remote participants. Making 
slides available soon enough to be viewed by remote attendees during the 
meeting seems like an achievable step towards better integration of 
remote participants.  The usefulness of doing this is also independent 
of whether the slides are for a presentation or to illustrate a point of 
discussion.

As Ted noted, "What is important is that remote people see the slides at 
the same time as local people."  That is the point.

-Andrew

From york@isoc.org  Mon Aug  5 02:20:44 2013
Return-Path: <york@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 DD38C21F8FF8; Mon,  5 Aug 2013 02:20:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.721
X-Spam-Level: 
X-Spam-Status: No, score=-102.721 tagged_above=-999 required=5 tests=[AWL=-0.722, BAYES_00=-2.599, J_CHICKENPOX_57=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hms4WV5bKNcH; Mon,  5 Aug 2013 02:20:39 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0157.outbound.protection.outlook.com [207.46.163.157]) by ietfa.amsl.com (Postfix) with ESMTP id 198A721F9926; Mon,  5 Aug 2013 02:16:39 -0700 (PDT)
Received: from BLUPR06MB067.namprd06.prod.outlook.com (10.242.187.146) by BLUPR06MB066.namprd06.prod.outlook.com (10.242.187.145) with Microsoft SMTP Server (TLS) id 15.0.731.16; Mon, 5 Aug 2013 09:15:34 +0000
Received: from BLUPR06MB067.namprd06.prod.outlook.com ([169.254.16.8]) by BLUPR06MB067.namprd06.prod.outlook.com ([169.254.16.8]) with mapi id 15.00.0731.000; Mon, 5 Aug 2013 09:15:33 +0000
From: Dan York <york@isoc.org>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOj4xYAESB6gTMDUWfnDZhDyWFn5mGWZMy
Date: Mon, 5 Aug 2013 09:15:32 +0000
Message-ID: <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org>
References: <51FBAF39.1090003@cisco.com>
In-Reply-To: <51FBAF39.1090003@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:470:1f07:309:9178:c04a:6eaa:83ab]
x-forefront-prvs: 0929F1BAED
x-forefront-antispam-report: SFV:NSPM; SFS:(24454002)(51704005)(377454003)(199002)(189002)(49866001)(15202345003)(54316002)(36756003)(65816001)(80022001)(53806001)(54356001)(76482001)(47976001)(47736001)(33656001)(79102001)(50986001)(56776001)(77982001)(59766001)(74366001)(81542001)(69226001)(74876001)(47446002)(19580405001)(74502001)(74662001)(46102001)(31966008)(15395725003)(81342001)(80976001)(19580395003)(19580385001)(83322001)(16406001)(74706001)(76786001)(76796001)(51856001)(63696002)(83072001)(4396001)(56816003)(77096001)(3826001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR06MB066; H:BLUPR06MB067.namprd06.prod.outlook.com; CLIP:2001:470:1f07:309:9178:c04a:6eaa:83ab; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-Mailman-Approved-At: Tue, 06 Aug 2013 08:15:50 -0700
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Aug 2013 09:20:46 -0000

On the topic of badge-sensing at the mic, I seem to recall that we had this=
 working at an IETF sometime back in the RAI working groups. It was maybe 4=
 or 5 years ago and I think it may have been some student(s) under Henning =
Schulzrinne at Columbia... but I am not sure about that.  I remember that w=
hen you went to the mic you put your badge up to this sensor and your name =
appeared in the jabber room. We used it in several of the RAI sessions at t=
hat IETF. Unfortunately I don't remember how well it worked or why it wasn'=
t continued. There may be someone out there who can provide some insight. (=
And if it was Henning's students we can just drop him a note.)

Dan

--
Dan York
york@isoc.org
+1-802-735-1624
skype:danyork
http://twitter.com/danyork

On Aug 2, 2013, at 10:26 AM, "Paul Aitken" <paitken@cisco.com> wrote:

> I've remotely participated in several IETFs.
>=20
> I find that the biggest problem with remote attendance is the lack of vis=
ual cues. I've come to realise just how important these are in a meeting.
> -are people paying attention, are they interested / confused / distracted=
 / bored?
>=20
> Also there's no way for local attendees (in the WG room) to know that rem=
ote attendees are "at the mic" and whose turn it is to speak.
>=20
> There's been some discussion on the "87attendees" mailer about badge sens=
ing at the mic - whether QR codes, NFC, or RFID. This could help remote att=
endees too.
>=20
> eg, see what they did with NFC + mic here: http://www.5thbar.me/blog/2012=
/09/14/nfc-enabled-badges-at-the-5thbar-mobile-marketing-forum/=20
>=20
> P.
> _______________________________________________
> iaoc-rps mailing list
> iaoc-rps@ietf.org
> https://www.ietf.org/mailman/listinfo/iaoc-rps

From dhc@dcrocker.net  Tue Aug  6 08:28:00 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5912921F9F62; Tue,  6 Aug 2013 08:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 u2H1652iIlxN; Tue,  6 Aug 2013 08:27:55 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 68E7921F9C53; Tue,  6 Aug 2013 08:27:55 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r76FRoIU008755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Aug 2013 08:27:53 -0700
Message-ID: <520115F3.6050908@dcrocker.net>
Date: Tue, 06 Aug 2013 08:27:47 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Dan York <york@isoc.org>
Subject: Re: [iaoc-rps] RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org>
In-Reply-To: <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 06 Aug 2013 08:27:53 -0700 (PDT)
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Paul Aitken <paitken@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 15:28:00 -0000

On 8/5/2013 2:15 AM, Dan York wrote:
> On the topic of badge-sensing at the mic, I seem to recall that we had this working at an IETF sometime back in the RAI working groups. It was maybe 4 or 5 years ago and I think it may have been some student(s) under Henning Schulzrinne at Columbia... but I am not sure about that.  I remember that when you went to the mic you put your badge up to this sensor and your name appeared in the jabber room. We used it in several of the RAI sessions at that IETF. Unfortunately I don't remember how well it worked or why it wasn't continued. There may be someone out there who can provide some insight. (And if it was Henning's students we can just drop him a note.)

It was an experiment.  It was awkward and inaccurate.  It also raised 
basic privacy concerns, what with wearing something that can be tracked 
as you move around.

An entirely different approach would be to have all speakers make a 
'reservation' into a single meetecho (or whatever) online queue, and 
then get called in order, whether local or remote and independent of 
what microphone they are at.  This gets accurate identification into the 
online system, with the entry task distributed.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hildjj@cursive.net  Tue Aug  6 08:41:41 2013
Return-Path: <hildjj@cursive.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF9F821E8082 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 08:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ERovFMdebPl0 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 08:41:40 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5DC21E805F for <ietf@ietf.org>; Tue,  6 Aug 2013 08:41:39 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so598613pbc.17 for <ietf@ietf.org>; Tue, 06 Aug 2013 08:41:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=6QClTCWWBxgOKrHAp/DAQbRDLzStyDsDVpCMobPZDYE=; b=iuLwPX25e/PkNXyNMjneoy7jEdFzq7q59oJA6LZ68VsRObFtImyl7v3q398hpYnxyc CTqHhVwGUxrulPpbKv+H5gYK4hiuVBvoGEiAKOmZC93B3l5e68ECOqxzzSuAv5gocaB5 dW2S73gP2svM5CXFCIf0X6LCqQt+QjJIQPx5o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=6QClTCWWBxgOKrHAp/DAQbRDLzStyDsDVpCMobPZDYE=; b=bNTnmIZNcM24cd1wddAs0XmYEiEnk9+jJoqs3e6yR373BdwvZ6YnNbpWqQg/iycBl2 MjygRtXqwd6ckTIS8Y5D0Wqpchqbq2bL79XiOuxoJ+OE1BH32Ova34VZp5j9arSraiuI QKY21fy0+WbtAKVh23kyHFns2pNSHdkph2Tsum4nutxm2uHzlLmep++J9e+w4OhzOD7W NopKpzDoKzE4K7B10ofJ0vkIXH1L5MJab11D7rxP2m6VbHAcRLLCGJI+zrtcHgf82ct/ mRq0lqRiH7RaePeEVq+LCw4Qb/xtreejoLDaYPQyIC4DmyfS2loaB+ykMnM1T2b9SDUf pGAQ==
X-Gm-Message-State: ALoCoQkeE0n8wday/bOmFnkC/xy3Mlyq3YZL50+tMMs5Gd/NSetk+9rTUy0iPNII/y05N0UXrts5
X-Received: by 10.68.253.161 with SMTP id ab1mr2216877pbd.76.1375803699036; Tue, 06 Aug 2013 08:41:39 -0700 (PDT)
Received: from [10.129.24.70] (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPSA id sp4sm2634156pbc.45.2013.08.06.08.41.33 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 06 Aug 2013 08:41:37 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 06 Aug 2013 09:41:23 -0600
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Joe Hildebrand <hildjj@cursive.net>
To: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <CE26746A.13BA5%joe@cursive.net>
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
In-Reply-To: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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: Tue, 06 Aug 2013 15:41:41 -0000

On 7/29/13 4:54 AM, "Phillip Hallam-Baker" <hallam@gmail.com> wrote:

>There are existing specs that does what CBOR does just as well that have
>actual users.

Some of these were approached, and none of them thought that having a
standard for their format was worth the amount of heartache that dealing
with the IETF would entail.  If you can get one of those communities
interested, that would be cool.

> There are requirements that the individuals proposing this chose not to
>address.

Re-enumerating those for this discussion might be useful.

-- 
Joe Hildebrand





From mcr@sandelman.ca  Tue Aug  6 10:26:05 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 294E421E805A for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 10:26:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 059JQFFTu0p0 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 10:26:00 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 5669921E8088 for <ietf@ietf.org>; Tue,  6 Aug 2013 10:25:50 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id BABF12016F for <ietf@ietf.org>; Tue,  6 Aug 2013 14:32:15 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A495C63A88; Tue,  6 Aug 2013 13:24:21 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9534863732 for <ietf@ietf.org>; Tue,  6 Aug 2013 13:24:21 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
In-Reply-To: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk>
References: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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: Tue, 06 Aug 2013 13:24:21 -0400
Message-ID: <4205.1375809861@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: Tue, 06 Aug 2013 17:26:05 -0000

If the WG/session chairs did not receive the slides at least a few days prior
to the meeting, then it is really hard for the WG chairs to make sure that
the slides support a discussion, rather than a presentation.

Given that we have meetings on Friday morning, and some people are very busy
during the week, and travel time can be 24h for some trips, asking that the
chair has received the slides *a week* before the WG session, being Friday
morning, seems to actually be cutting it really close.

If a discussion leader can not get some slides into the WG chairs' inbox by
the Friday morning before the IETF meeting, then I question whether the WG
chair should give them any time.

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



From mcr@sandelman.ca  Tue Aug  6 10:32:57 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B2521F9ED4; Tue,  6 Aug 2013 10:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 YvicwIJH7jOE; Tue,  6 Aug 2013 10:32:52 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id D4E8221F9E39; Tue,  6 Aug 2013 10:32:51 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id E35502016F; Tue,  6 Aug 2013 14:39:17 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id CE36363A88; Tue,  6 Aug 2013 13:31:23 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id BF4E263732; Tue,  6 Aug 2013 13:31:23 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "iaoc-rps\@ietf.org" <iaoc-rps@ietf.org>, "ietf\@ietf.org" <ietf@ietf.org>
Subject: Re: [iaoc-rps] RPS Accessibility
In-Reply-To: <520115F3.6050908@dcrocker.net>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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: Tue, 06 Aug 2013 13:31:23 -0400
Message-ID: <5328.1375810283@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: Tue, 06 Aug 2013 17:32:57 -0000

--=-=-=


Dave Crocker <dhc@dcrocker.net> wrote:
    > An entirely different approach would be to have all speakers make a
    > 'reservation' into a single meetecho (or whatever) online queue, and then get
    > called in order, whether local or remote and independent of what microphone
    > they are at.  This gets accurate identification into the online system, with
    > the entry task distributed.

+1.
And move the microphones to the people, rather than the other way around.

We can easily have three or four microphones that can play leap-frog around
the room.

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



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

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

iQCVAwUBUgEy6YqHRg3pndX9AQKsQwP/QyLj+eWvIqKXitMTiUudg+8wGkmmTc8L
yqP5HV84CPjoJsAxshXNZgVtwlAtci//D0omLEuugGCFo/wPMP+X/Mz1bM2MdbfU
r11pNke56WHrMu1LEd2Z4gdXNWes1QpCPs32Az0c2F24msrSpXVxCyt4/zGR5RyB
UWo7zRBMjNk=
=oKyQ
-----END PGP SIGNATURE-----
--=-=-=--

From hallam@gmail.com  Tue Aug  6 10:34:23 2013
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 B54C421E8089; Tue,  6 Aug 2013 10:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069,  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 0XTDshD5Gpaf; Tue,  6 Aug 2013 10:34:22 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 48F6221F9F13; Tue,  6 Aug 2013 10:34:22 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so641328wes.19 for <multiple recipients>; Tue, 06 Aug 2013 10:34: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:date:message-id:subject:from:to :cc:content-type; bh=SVLqnW6sbAKFs3w1POn0q3M6KVePqi4h2HFwGayzgCk=; b=cbyryvHsphM40Ptde0zDWn4NLlVC5rUJwBFMM9OLRZVnmwJgSvMMaoTFgVS9FdWIWr JaXHiitL3bCQTQ2cMrpGRglqJXK5CZE7pbT2tlhBcTO7q4AINpqsfEZkpjdngsK1hcFb 5WR/4/c7AqZmyWhQYByd65REW5/8uKVOKZljgq0PMU4Ht7xHqDAO4grkZCeYku7uga28 Sad7FLbF64WxtXoY5FCorpkIxF1nw2B42qZwHv2LTR+1a6frKfW6LWKGRPtdZN1mb9z1 F3hVIpowz8uTU+6jgUZ08CPsq7XiLIcuPKymd/ut0KtKDFsKf9wyZRwPMAquxeHZEpt2 saIA==
MIME-Version: 1.0
X-Received: by 10.180.184.84 with SMTP id es20mr2783913wic.37.1375810461321; Tue, 06 Aug 2013 10:34:21 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Tue, 6 Aug 2013 10:34:21 -0700 (PDT)
In-Reply-To: <CE26746A.13BA5%joe@cursive.net>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net>
Date: Tue, 6 Aug 2013 13:34:21 -0400
Message-ID: <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Joe Hildebrand <hildjj@cursive.net>
Content-Type: multipart/alternative; boundary=001a11c2259cd34f9e04e34ad59b
Cc: IETF Discussion Mailing List <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 17:34:23 -0000

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

On Tue, Aug 6, 2013 at 11:41 AM, Joe Hildebrand <hildjj@cursive.net> wrote:

> On 7/29/13 4:54 AM, "Phillip Hallam-Baker" <hallam@gmail.com> wrote:
>
> >There are existing specs that does what CBOR does just as well that have
> >actual users.
>
> Some of these were approached, and none of them thought that having a
> standard for their format was worth the amount of heartache that dealing
> with the IETF would entail.  If you can get one of those communities
> interested, that would be cool.
>
> > There are requirements that the individuals proposing this chose not to
> >address.
>
> Re-enumerating those for this discussion might be useful.
>

The issue here is whether this proposal should be an IETF Proposed STANDARD.

I think that is nuts and I would think it just as much nuts if it was my
proposal. We have no real world implementation experience by which I mean
using it in a protocol and not writing some python

Usually when the IETF publishes an algorithm it is given INFORMATIONAL or
EXPERIMENTAL status. That is what originally happened with JSON, RFC 4627
has INFORMATIONAL status despite the fact that at the time it was written
there was a lot of implementation.

Using the individual submissions track as a way to circumvent working group
process when there is an actual IETF JSON working group seems completely
wrong to me.


For the record, the issues I see are:

1) This is an entirely new encoding and semantics. It is not JSON in binary
which is what we actually need.

2) No support for tag compression.

3) No support for decimal floating point.

4) Its all or nothing, no layering.


The first one is my main complaint. I want to be able to use the binary and
text JSON encodings interchangeably and not have the upper layers to have
to bother with it at all.

That is why I designed a system where a single reader can read binary and
text without the need for any additional state (beyond tracking how the
current item is encoded.)


What I like in JSON is the lack of features and the fact that JSON covers
95% of all my needs as is. All I want to add in to get to 100% features are
the ability to encode floating point without loss and the ability to
efficiently encode binary blobs.

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

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

<div dir=3D"ltr">On Tue, Aug 6, 2013 at 11:41 AM, Joe Hildebrand <span dir=
=3D"ltr">&lt;<a href=3D"mailto:hildjj@cursive.net" target=3D"_blank">hildjj=
@cursive.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 7/29/13 4:54 AM, &quot;=
Phillip Hallam-Baker&quot; &lt;<a href=3D"mailto:hallam@gmail.com">hallam@g=
mail.com</a>&gt; wrote:<br>

<br>
&gt;There are existing specs that does what CBOR does just as well that hav=
e<br>
&gt;actual users.<br>
<br>
</div>Some of these were approached, and none of them thought that having a=
<br>
standard for their format was worth the amount of heartache that dealing<br=
>
with the IETF would entail. =A0If you can get one of those communities<br>
interested, that would be cool.<br>
<div class=3D"im"><br>
&gt; There are requirements that the individuals proposing this chose not t=
o<br>
&gt;address.<br>
<br>
</div>Re-enumerating those for this discussion might be useful.<span class=
=3D"HOEnZb"><font color=3D"#888888"><br>
</font></span></blockquote></div><br>The issue here is whether this proposa=
l should be an IETF Proposed STANDARD.</div><div class=3D"gmail_extra"><br>=
</div><div class=3D"gmail_extra">I think that is nuts and I would think it =
just as much nuts if it was my proposal. We have no real world implementati=
on experience by which I mean using it in a protocol and not writing some p=
ython</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Usually whe=
n the IETF publishes an algorithm it is given INFORMATIONAL or EXPERIMENTAL=
 status. That is what originally happened with JSON, RFC 4627 has INFORMATI=
ONAL status despite the fact that at the time it was written there was a lo=
t of implementation.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Using the i=
ndividual submissions track as a way to circumvent working group process wh=
en there is an actual IETF JSON working group seems completely wrong to me.=
<br>
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br><=
/div><div class=3D"gmail_extra">For the record, the issues I see are:</div>=
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">1) This is =
an entirely new encoding and semantics. It is not JSON in binary which is w=
hat we actually need.=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">2) No suppo=
rt for tag compression.</div><div class=3D"gmail_extra"><br></div><div clas=
s=3D"gmail_extra">3) No support for decimal floating point.</div><div class=
=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">4) Its all or nothing, no layering.</d=
iv><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra">The first one is my main complaint. I want to =
be able to use the binary and text JSON encodings interchangeably and not h=
ave the upper layers to have to bother with it at all.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">That is why=
 I designed a system where a single reader can read binary and text without=
 the need for any additional state (beyond tracking how the current item is=
 encoded.)</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div><br></=
div><div>What I like in JSON is the lack of features and the fact that JSON=
 covers 95% of all my needs as is. All I want to add in to get to 100% feat=
ures are the ability to encode floating point without loss and the ability =
to efficiently encode binary blobs.=A0</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--001a11c2259cd34f9e04e34ad59b--

From jabley@hopcount.ca  Tue Aug  6 10:42:13 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C18A421F9E31 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 10:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrF+IqMDM6RW for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 10:42:13 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0969821F9E39 for <ietf@ietf.org>; Tue,  6 Aug 2013 10:41:57 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so752012pbb.19 for <ietf@ietf.org>; Tue, 06 Aug 2013 10:41:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vjH6AFujI/AH8NX56+1lX4TGNmB5yvwRXrYNrpHDP4M=; b=NcZ5uU9mWx+hbQda0EYh0IQYysTBShjFWw9kgUSVHlWWrmmf8QRWCtFxPX8uHVHh36 llpX+DAPNbVNpMTRpYiMHT7HhTIAb9LULH59Lwkvne7Ph2TCLV1VrbzWeRX10x6D7ZNK WK+KoG7tahcdjMWlpuDo5eqMWCWikKJHIO6+Y=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=vjH6AFujI/AH8NX56+1lX4TGNmB5yvwRXrYNrpHDP4M=; b=dHx2NteJxCJ+KcHIeXsq2o5XBy9m327pt/CF5oTpNsXB96td5JsmFFCrOWbwhg+9xR 9rlI++zHxYOt4KXYLKAMEaAJnqX04MjvVz/VYK9xOecl5F/oORR3dBN6ZHp+LTK4g2Ik GLIycVrhtmcIeWT3WVjhrjMZoK7fLrff8HapmwqHeaTSZs0lkUy3mEF2DfdDCQhGSQk6 Rkr1ywf7DVm4bfi/sC3I+iiDY3LWCzNwXLNjZElRnHMWhTT/GkR/+A1KphzpK06nZeCQ It667h4u+XqEQRYWl8G1hgjnzTjQ04xi6d2XSEp+C4R3Lv5fQzxfN2+ljpiGo9FbhZle y+Cg==
X-Gm-Message-State: ALoCoQmvNxsyzDKiUYXPnAtS7yU73kfujGJFk7bQzJaTZ04U7R8G7ZFe8gPJ6CzNdv29A5j7sPxC
X-Received: by 10.68.227.4 with SMTP id rw4mr2693515pbc.182.1375810917563; Tue, 06 Aug 2013 10:41:57 -0700 (PDT)
Received: from [199.212.90.33] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id tr10sm3197384pbc.22.2013.08.06.10.41.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 10:41:56 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk>
Date: Tue, 6 Aug 2013 13:41:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca>
References: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk>
To: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 17:42:13 -0000

On 2013-08-06, at 10:26, Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk> wrote:

> to clarify, imho:
>=20
> presentation !=3D slides

In my experience, slides are mainly useful:

1. To convey information which is difficult to express accurately by =
voice only (e.g. graphs, names of drafts, big numbers)

2. To distract the e-mail-reading audience in the room so that they look =
up and pay attention.

An example of (2) can be found in =
<http://www.ietf.org/proceedings/87/slides/slides-87-dnsop-8.pdf> where =
I presented a one-slide problem statement that consisted entirely filled =
with an xkcd cartoon. Once the room is suitably filled with hilarity, =
it's much easier to enrage people with your stupid idea.

I don't think that having slides available in advance helps =
significantly with (1) in an ietf context (where we are continuing a =
conversation from a list, and not generally introducing new material). =
(2) is not really pertinent for a remote audience (if they've bothered =
to attend at all, you can surely assume they are paying attention.)

Many people use slideware as a teleprompter so that they can remember =
what to say at the mic. I've done that before. I'm not proud of it.

The best outcome at a working group meeting is that, as a presenter, you =
spend most of your time listening rather than talking. If the mic line =
is empty, you probably should not have been on the agenda.


Joe=

From lear@cisco.com  Tue Aug  6 10:53:08 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76CB721E80AA for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 10:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.052
X-Spam-Level: 
X-Spam-Status: No, score=-110.052 tagged_above=-999 required=5 tests=[AWL=0.546, 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 Tpslp81Ko05N for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 10:53:02 -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 976AD21E80A1 for <ietf@ietf.org>; Tue,  6 Aug 2013 10:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3919; q=dns/txt; s=iport; t=1375811565; x=1377021165; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=3zKKHLeGDQAgqoGwckbedWN0z1TiR+6WYh+8TygrAuM=; b=Rf2UE1P8kHckh/+S/7aVIUDzQAjjVwxRFjmSxhfixtfe2uZDwElKJ6VZ MOZVgFrnPABoXldNl8zOEyD2UoLNbEqWGt3OUKWmbNr52mKF8i3edbtHv F566KpQufUtDkGArCZhNXSeJqd5HpJk57B1z12x3yiGiCAAaXIu0I9SqI k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAJM3AVKQ/khL/2dsb2JhbABagwY1g2CFXbYQgR8WdIIkAQEBAgEBI1UBEAsECgoJFgsCAgkDAgECASsaBg0BBwEBBYgBBgylK5FdjlSBRgeCZ4EnA5dhkU6DGTqBNQ
X-IronPort-AV: E=Sophos;i="4.89,827,1367971200"; d="scan'208,217";a="16868980"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 06 Aug 2013 17:52:29 +0000
Received: from mctiny.local ([10.61.171.67]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r76HqRF5021957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 17:52:27 GMT
Message-ID: <520137DE.4030308@cisco.com>
Date: Tue, 06 Aug 2013 19:52:30 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: procedural question with remote participation
References: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk> <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca>
In-Reply-To: <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------000801000604020904080602"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 17:53:08 -0000

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

Hey Joe,

On 8/6/13 7:41 PM, Joe Abley wrote:
> An example of (2) can be found in <http://www.ietf.org/proceedings/87/slides/slides-87-dnsop-8.pdf> where I presented a one-slide problem statement that consisted entirely filled with an xkcd cartoon. Once the room is suitably filled with hilarity, it's much easier to enrage people with your stupid idea.
>
> I don't think that having slides available in advance helps significantly with (1) in an ietf context (where we are continuing a conversation from a list, and not generally introducing new material). (2) is not really pertinent for a remote audience (if they've bothered to attend at all, you can surely assume they are paying attention.)

What?  People remotely can't read email?  Heck we can do more than
that.  We can cook a meal.  Try that while an IETF is going on.

>
> Many people use slideware as a teleprompter so that they can remember what to say at the mic. I've done that before. I'm not proud of it.

But if those lines contain *questions*, it gets you to the point where
there is discussion, which is just fine, as you point out here:
>
> The best outcome at a working group meeting is that, as a presenter, you spend most of your time listening rather than talking. If the mic line is empty, you probably should not have been on the agenda.
>

100% agree.

Eliot

--------------000801000604020904080602
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">
    Hey Joe,<br>
    <br>
    <div class="moz-cite-prefix">On 8/6/13 7:41 PM, Joe Abley wrote:<br>
    </div>
    <blockquote
      cite="mid:621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca"
      type="cite">
      <pre wrap="">
An example of (2) can be found in <a class="moz-txt-link-rfc2396E" href="http://www.ietf.org/proceedings/87/slides/slides-87-dnsop-8.pdf">&lt;http://www.ietf.org/proceedings/87/slides/slides-87-dnsop-8.pdf&gt;</a> where I presented a one-slide problem statement that consisted entirely filled with an xkcd cartoon. Once the room is suitably filled with hilarity, it's much easier to enrage people with your stupid idea.

I don't think that having slides available in advance helps significantly with (1) in an ietf context (where we are continuing a conversation from a list, and not generally introducing new material). (2) is not really pertinent for a remote audience (if they've bothered to attend at all, you can surely assume they are paying attention.)</pre>
    </blockquote>
    <br>
    What?Â  People remotely can't read email?Â  Heck we can do more than
    that.Â  We can cook a meal.Â  Try that while an IETF is going on.<br>
    <br>
    <blockquote
      cite="mid:621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca"
      type="cite">
      <pre wrap="">

Many people use slideware as a teleprompter so that they can remember what to say at the mic. I've done that before. I'm not proud of it.</pre>
    </blockquote>
    <br>
    But if those lines contain <b>questions</b>, it gets you to the
    point where there is discussion, which is just fine, as you point
    out here:<br>
    <blockquote
      cite="mid:621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca"
      type="cite">
      <pre wrap="">

The best outcome at a working group meeting is that, as a presenter, you spend most of your time listening rather than talking. If the mic line is empty, you probably should not have been on the agenda.

</pre>
    </blockquote>
    <br>
    100% agree.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------000801000604020904080602--

From hadriel.kaplan@oracle.com  Tue Aug  6 11:00:46 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A85521F9E80 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.485
X-Spam-Level: 
X-Spam-Status: No, score=-6.485 tagged_above=-999 required=5 tests=[AWL=0.114,  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 sL32U+Ci-pgx for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:00:34 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 2D95021F9E0B for <ietf@ietf.org>; Tue,  6 Aug 2013 11:00:28 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r76I0Pcs025231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Aug 2013 18:00:26 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r76I0OnA004424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 18:00:25 GMT
Received: from abhmt101.oracle.com (abhmt101.oracle.com [141.146.116.53]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r76I0ODc028995; Tue, 6 Aug 2013 18:00:24 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 06 Aug 2013 11:00:24 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca>
Date: Tue, 6 Aug 2013 14:00:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6651C30B-3263-4A56-BAA5-9C0797C82EF6@oracle.com>
References: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk> <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca>
To: Joe Abley <jabley@hopcount.ca>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 18:00:46 -0000

On Aug 6, 2013, at 1:41 PM, Joe Abley <jabley@hopcount.ca> wrote:

> In my experience, slides are mainly useful:
>=20
> 1. To convey information which is difficult to express accurately by =
voice only (e.g. graphs, names of drafts, big numbers)

Yup.


> 2. To distract the e-mail-reading audience in the room so that they =
look up and pay attention.

YES!  (Crap, I thought we were supposed to keep that purpose a secret!) =20=

And no way am I uploading my jokes in advance and having people see them =
in advance - it ruins the joke completely!  Sheesh, they're barely funny =
enough as is.


> An example of (2) can be found in =
<http://www.ietf.org/proceedings/87/slides/slides-87-dnsop-8.pdf> where =
I presented a one-slide problem statement that consisted entirely filled =
with an xkcd cartoon.

Huh, who knew DNS Ops was rocket science?  :)
(I like the hack idea, btw... mostly because I like your xkcd cartoon, =
of course)


> Many people use slideware as a teleprompter so that they can remember =
what to say at the mic. I've done that before. I'm not proud of it.

Yeah me too, but I'd prefer people pay attention to what I say, rather =
than the text on the slides.

-hadriel


From moore@network-heretics.com  Tue Aug  6 11:03:36 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FEA521F9FED for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:03:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KFB9GtjGsFRj for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:03:27 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 35BF521F9263 for <ietf@ietf.org>; Tue,  6 Aug 2013 11:03:27 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 83A4220D6B for <ietf@ietf.org>; Tue,  6 Aug 2013 14:03:26 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 06 Aug 2013 14:03:26 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=gb2AMRTyHpOWEeSkLhFL4J xaOKk=; b=URCvlSnqqAfEQrsrCTXiaDEsyI5fPRUpJVBflPn9SqIeEC3cb5Rk2C Oy49AEoGG0HsIhPZpkzBs9wPSd92bvB0stYXALi4JCfcesgQ+w6NyJNphL7t+DjI HV4mRFcHpIbaBIBzWg4GwOjl2Hg0Qpud4CdWd9fjrMFy3FG12PrmY=
X-Sasl-enc: CFr+fGJ5GpUgZpn3YGKQkyBAXNlTuiHdPGJDGnmMpVUn 1375812205
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id B2573680085; Tue,  6 Aug 2013 14:03:25 -0400 (EDT)
Message-ID: <52013A6B.1090704@network-heretics.com>
Date: Tue, 06 Aug 2013 14:03:23 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com>
In-Reply-To: <520110F0.5030100@plixer.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 18:03:36 -0000

On 08/06/2013 11:06 AM, Andrew Feren wrote:
> On 08/06/2013 09:08 AM, Keith Moore wrote:
>> On 08/04/2013 02:54 PM, Ted Lemon wrote:
>>> While I think getting slides in on time is great for a lot of 
>>> reasons, reading the slides early isn't that important.   What is 
>>> important is that remote people see the slides at the same time as 
>>> local people.   For that, it seems to me that Meetecho support does 
>>> exactly what is needed.   You just follow the slideshow online, 
>>> along with the audio.
>>
>> I agree that remote people should see the slides at the same time as 
>> local people, except that I think that in both cases this should be 
>> well before the meeting.  The slides shouldn't be shown at the 
>> meeting unless needed to illustrate a point of active discussion.
>>
>> People keep acting as if the purpose of these meetings - the reason 
>> people spend thousands of euro and travel thousands of km - is to 
>> watch slides.
> Hi Keith,
>
> I think this sort of misses the point.  At least for me as a remote 
> participant.

Actually I think the desire to get slides out early largely misses the 
point.   Or at least, it's an effort optimizing what should be the rare 
case.

I fully agree that slides should be easily available to both local and 
remote participants well prior to any meeting in which a presentation 
will be made.  (Say a plenary session where presentations are normal and 
appropriate.)   While speakers might like to revise their slides at the 
last minute, there's no reason why they shouldn't be expected to upload 
preliminary slides well in advance (because the key to an effective 
presentation is good preparation, after all) and a revised version (if 
necessary) later. This isn't at all rocket science, and there's no 
reason why it should not be done.

But if we really want to make remote participation effective, we need to 
figure out better ways to involve remote participants in _discussions_ - 
not only in plenaries, WG meetings, BOFs, etc., but also in hallway and 
bar conversations.   Having a local speaker read something from a laptop 
that was typed into a Jabber session by a remote participant is better 
than nothing.   But surely we can do better.

> As of today when the slides are available (or if there are no slides 
> and just talk) I can follow WG meetings quite well.  Being able to 
> actively engage in any discussion remotely is, IMO, pretty much 
> limited to the mailing lists.  Getting involved in an active 
> discussion at a WG meeting remotely is currently difficult at best and 
> impossible at worst.

It used to be the case that Internet access at IETF meetings was flaky, 
either because of the wireless network or because of the network 
connection or both.   More recently the performance of the meeting 
Internet access has been stellar.   If we put the same kind of effort 
into facilitating remote participation in discussions, I suspect we 
could move from "difficult at best and impossible at worse" to "works 
well".  Of course, it might take awhile, but it's those very kinds of 
discussions that are so essential to broad consensus that (when it 
works) makes our standards effective.   The fact that it doesn't work 
well now is not a good argument for not making it work well in the future.

(We're supposed to be creating the future, after all.  That's our job.)

It's also the case that the fact that facilities for involving remote 
participants in conversation haven't historically worked well, is used 
as a justification for continuing to have this dysfunctional style of 
conducting working group meetings, thus making very poor use of local 
participants' time and money.

I'm all for making presentation slides available to local and remote 
participants well before the meeting.   But if we're only concerned with 
making presentation slides available, we're selling ourselves very 
short.  That's the point I'm trying to make.

Keith


From jabley@hopcount.ca  Tue Aug  6 11:04:48 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C87421F84DB for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zumRf8-lDyLS for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:04:48 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2EF21F9F5C for <ietf@ietf.org>; Tue,  6 Aug 2013 11:04:40 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so772830pbc.7 for <ietf@ietf.org>; Tue, 06 Aug 2013 11:04:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=oxjiE68P4hKD0gF0GkomMwvU7Ism4oH8kaaqGgupWUg=; b=c0cL+WQ3oXz/jzrlBTqs/qaqsMMpmr6GJic7LXpfHotT7tbZ2J9sgZFV0D/gHvTMOq G4TX8sm5MnPLD6QyRhx+ClrlWLMqD/mXlfra/GDec/m1LaKo9+m0ZJ8R4/vZA0bRozMp x6oJjy/TY6LPD+TB0G0q+y1ytYzRxuYIkEjyE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=oxjiE68P4hKD0gF0GkomMwvU7Ism4oH8kaaqGgupWUg=; b=AbMvBswI7wmdq267Y9TnhaxDbY0IlueWeJgFwJWQmPl+ONFFG2DJg91gLRXiTKbMOm 3LM7cLBSXYgODknWoaa5jCVtwM2JxXruUZ6hLavAIRx0fNuDg547vI6/D3nWH0Uhxt4U +va9xjOQrJb3pd8GQpNLMhoeyO0xBY/Qh6MhgYavM/vIrozW+kBzHvE88XrLDh72veZu TfCI+Rh3vvMmy8/NJm3Ps9WhXFEEW+XSUNxn1r2BbgSJCRDUrZPI8ET3zCITwBiy1aaw XxlrmEOs5uw5sDx6CeGIxEj3GKys2mFt4K7dg+/jGMET1XgxgtrMExO9IcwJzRa6lNPd Otwg==
X-Gm-Message-State: ALoCoQlvhEXL4sPGY4/Hmtii7Yc88k73+Ies++iVhJZb+udrVgaa92Y9ANuicHqQ29u9cN5Z1A1H
X-Received: by 10.66.161.138 with SMTP id xs10mr127819pab.56.1375812277769; Tue, 06 Aug 2013 11:04:37 -0700 (PDT)
Received: from [199.212.90.33] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id vu5sm5415218pab.10.2013.08.06.11.04.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 11:04:36 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6651C30B-3263-4A56-BAA5-9C0797C82EF6@oracle.com>
Date: Tue, 6 Aug 2013 14:04:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <78595867-4668-4976-BE8E-A8D50B20A04D@hopcount.ca>
References: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk> <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca> <6651C30B-3263-4A56-BAA5-9C0797C82EF6@oracle.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 18:04:48 -0000

On 2013-08-06, at 14:00, Hadriel Kaplan <hadriel.kaplan@oracle.com> =
wrote:

>> An example of (2) can be found in =
<http://www.ietf.org/proceedings/87/slides/slides-87-dnsop-8.pdf> where =
I presented a one-slide problem statement that consisted entirely filled =
with an xkcd cartoon.
>=20
> Huh, who knew DNS Ops was rocket science?  :)
> (I like the hack idea, btw... mostly because I like your xkcd cartoon, =
of course)

Of course! And now people who aren't even following dnsop are reading =
the slides, and maybe even the draft. It's a triumph of social =
engineering. :-)


Joe


From doug.mtview@gmail.com  Tue Aug  6 11:08:08 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A389521F8FA1 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.298
X-Spam-Level: 
X-Spam-Status: No, score=-0.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_PAIN=2.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 grLO-j2tbCdz for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:08:08 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1E25621E809F for <ietf@ietf.org>; Tue,  6 Aug 2013 11:07:57 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id l18so1816369qak.18 for <ietf@ietf.org>; Tue, 06 Aug 2013 11:07:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=P1OxGs2rabnfWnjDxu554S0KQnOKeK2dfju1RPKnJws=; b=K2+SYWY67DfpV9NrZPnpTOcNtF4mUwkDFk4OlBWDfzZW3te4ih99e+Oz5CIr2lx0bg rvYp8c5YbCaA8+sirEnMxJLEjwqSY4AFGMfWtrcpIcWaG7E3iQxBOMRb94BLCYq50Lt7 Pr9nxSbP2/PCuy29MHMA09mLi8r/JxIAryN+oyXBobLd2qxy6wyBBsqzG95BtFx+e7pZ N4fs1id+uiVc0yT4vwa96wjIMcxss4UcUIVaK5EajeAfHEjoMA368aD91eF41a641x53 DZl7XSv/aZBJkOpt7VtNhAFEvFQOTrocS9N2bmfH8/vmf1xP/jhwZrdaCLbFGjAAMVsv Rxkg==
X-Received: by 10.224.35.196 with SMTP id q4mr4984688qad.106.1375812476389; Tue, 06 Aug 2013 11:07:56 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id q15sm5906221qak.5.2013.08.06.11.07.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 11:07:55 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_929029CD-3541-4660-A990-312FE5745768"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <520137DE.4030308@cisco.com>
Date: Tue, 6 Aug 2013 11:07:54 -0700
Message-Id: <56368675-775C-44D5-957E-F269BF9EDAC3@gmail.com>
References: <27b6e6cbf5cc3caa8264fafca6399b43@cam.ac.uk> <621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca> <520137DE.4030308@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 18:08:08 -0000

--Apple-Mail=_929029CD-3541-4660-A990-312FE5745768
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 6, 2013, at 10:52 AM, Eliot Lear <lear@cisco.com> wrote:

> But if those lines contain questions, it gets you to the point where =
there is discussion, which is just fine, as you point out here:
>>=20
>> The best outcome at a working group meeting is that, as a presenter, =
you spend most of your time listening rather than talking. If the mic =
line is empty, you probably should not have been on the agenda.
Dear Eliot and Joe,

The context of local conversations often use shorthand references to the =
material presented rather than restating the content to ensure remote =
participants understand what is being said. =20

The IETF should devise a strategy able to virtualize both the local =
protector and PA in the event the venue no long has access to the =
Internet but where the meetings are still able to proceed.  Ensure =
remote participants are not considered secondary.  If fact, paying some =
access fee (that should be able to avoid VAT) might be reasonable.

Regards,
Douglas otis=

--Apple-Mail=_929029CD-3541-4660-A990-312FE5745768
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 6, 2013, at 10:52 AM, Eliot Lear &lt;<a href="mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrote:</div><br><blockquote type="cite">
  
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  
  <div bgcolor="#FFFFFF" text="#000000">
    But if those lines contain <b>questions</b>, it gets you to the
    point where there is discussion, which is just fine, as you point
    out here:<blockquote cite="mid:621F09B7-292E-40C2-8580-118F4C1A7BC6@hopcount.ca" type="cite"><pre wrap="">The best outcome at a working group meeting is that, as a presenter, you spend most of your time listening rather than talking. If the mic line is empty, you probably should not have been on the agenda.
</pre></blockquote></div></blockquote><div>Dear Eliot and Joe,</div><div><br></div><div>The context of local conversations often use shorthand references to the material presented rather than restating the content to ensure remote participants understand what is being said. &nbsp;</div><div><br></div><div>The IETF should devise a strategy able to virtualize both the local protector and PA in the event the venue no long has access to the Internet but where the meetings are still able to proceed. &nbsp;Ensure remote participants are not considered secondary. &nbsp;If fact, paying some access fee (that should be able to avoid VAT) might be reasonable.</div><div><br></div><div>Regards,</div><div>Douglas otis</div></div></body></html>
--Apple-Mail=_929029CD-3541-4660-A990-312FE5745768--

From jabley@hopcount.ca  Tue Aug  6 11:13:29 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D073621F9971 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_73=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewrt-nnIhyy1 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:13:29 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2114021F99E9 for <ietf@ietf.org>; Tue,  6 Aug 2013 11:13:29 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up15so778760pbc.40 for <ietf@ietf.org>; Tue, 06 Aug 2013 11:13:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qoLtaCPo2VMQa7EB4svlHzwVlAMXGRvQimx+C9BGwgI=; b=pEe9LIpDMuYy8mlAJ3eQoX6O6x3ww3Ix5rJGO5FTBhAEsbOtlIpMTQO/d98+F2xxfo CQFtwzIDKXNH7Lz8rEt/m+fXHq96PDyi4TdrRQ6AVPfkTNXMSgHYxDVbBb3+yLYMFjII wkVWpRHNGQO2iY4715aaJKDe5xdMRAlbgwLNQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=qoLtaCPo2VMQa7EB4svlHzwVlAMXGRvQimx+C9BGwgI=; b=mWV78lJ5pMtSYlrWDK9Q8KVZYMLq9YJ6ftUJ5L9uyB71mzz6lRlcJwMEO6lp58ytVu 06QLFRT/bNWGIllDdVmP7afyG9XzFuvvTUiIcWQAN6TN6Bx/IGcOcTZD+a4nRyWylYah j+mJH6JeYpC9OeHTgpoga92fED1t0smhyDb7wL8VHSqQrm3dUqvQQjqMaF4WFCqmEGFO 9wc4LRA3Dnmqa3sVIT4ea0/sgXFkUIMB+XMhdmJuOxqRpUc/ZIzZ51L5m1amzkbi2AVd zhzzxbsQHkAYQcodky0f+7zlmjrREsn9PaH4Sw26Geb3G9eRuXWgDbWS96YZLZg35eLz Sa+Q==
X-Gm-Message-State: ALoCoQm32Wx6b/dGAhHVcKcUVjonS38yiOC2cp1hRRcmd7t/T2uswqBZdXL37it23x9dYMIiMbzo
X-Received: by 10.66.253.40 with SMTP id zx8mr150472pac.71.1375812808745; Tue, 06 Aug 2013 11:13:28 -0700 (PDT)
Received: from [199.212.90.33] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id ue9sm5455673pab.7.2013.08.06.11.13.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 11:13:27 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [iaoc-rps] RPS Accessibility
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <520115F3.6050908@dcrocker.net>
Date: Tue, 6 Aug 2013 14:13:27 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D12B775-E093-493B-9B6A-679F8F78A30B@hopcount.ca>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, Paul Aitken <paitken@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 18:13:30 -0000

On 2013-08-06, at 11:27, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/5/2013 2:15 AM, Dan York wrote:
>> [...]  I remember that when you went to the mic you put your badge up =
to this sensor and your name appeared in the jabber room.

... and the main screen in the room, if we're thinking about the same =
experiment. I seem to think it might have been in Hiroshima.

> It was an experiment.  It was awkward and inaccurate.  It also raised =
basic privacy concerns, what with wearing something that can be tracked =
as you move around.

I thought it was less awkward and inaccurate than relying on =
poly-accented and rushed (or missing) announcements of name and =
affiliation through the microphone. It was an improvement for jabber =
scribes, wg chairs trying to do minutes, remote participants and people =
in the room who are interested in who is talking, but not interested =
enough to stand up and demand that the name and affiliation be repeated.

I remember the privacy concerns being expressed, but I also have been =
subscribed to more XXattendees mailing lists than I care to remember, =
and I had compartmentalised both sets of complaints into the same bucket =
that usually makes me unsubscribe from XXattendees by Tuesday.

The NFC badge idea was a good one, I think, and I think it should happen =
again (even if it's opt-in at registration time, to reduce anxiety for =
those worried about their loss of privacy in a public meeting.)

Or perhaps future IETFers.app releases could talk using bluetooth to a =
transponder duct-taped to the mic stand and realise the same outcomes =
(and if you don't like that, you can always touch "no" in the =
appropriate place on your phone).


Joe


From hildjj@cursive.net  Tue Aug  6 11:18:58 2013
Return-Path: <hildjj@cursive.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE30921E808F for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1Y+V2nuTcyv for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:18:58 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7A01521E8085 for <ietf@ietf.org>; Tue,  6 Aug 2013 11:18:55 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id p11so543218pdj.18 for <ietf@ietf.org>; Tue, 06 Aug 2013 11:18:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=/sXkNnISWnJ+g0+jz13ix5E69qj37BnHJkFyF3LZfvA=; b=OZj7E+4zLS16wnEMj0jSe7Oj2g5jvy3Acl/6An0j7nTZvBcsG+eMqc3Vh27A7kQCGX D3DdIj/4JarX1wfYAVzyviy95VJJ7nC2iV66p6QfHjLX0DAEPThguHUIOVAbr7EPGxPb eiw38pr5RMD2s9nUMcwI3Z4/phmH9arQtz/JI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=/sXkNnISWnJ+g0+jz13ix5E69qj37BnHJkFyF3LZfvA=; b=gc23zNa9GIqc2HbjqmKKv/pIMSlc1QqJ9ehQUl5+ci3lZ8XHMiNwWCnskMu9udFsKM DoIA7AwDlB2tO2mNnu9I+RxnGkqnqVYxPNc9q/rIPTpiOCxcHNNyZPc75/n4hfdrkVPn 34Dh/hoZ6i0+4Zpv0rk5KWC5yj4gbp+wvyYCsWtxQbyCKAHsfdcN2luIjsN1igyc7/g6 qCVOTnRxz6XR2ycO0TtrLpUAInmsuMhVgejIUjDzm6A8QkEPBu2G3tVjlfgx8VOf+8uS W6thPPgweDBjAyl11/NyBge12zuDpjHkRQ2lXty18l63Q9RjINbtZ14CAWbEa51P8iMZ 6u2A==
X-Gm-Message-State: ALoCoQlPIesnGkSSykm/3en+WvgVY05Ez6ohdj/O9BgHCc/9WiuEMJheTiNwH5S9y+j9dS8Q/1Oo
X-Received: by 10.66.221.8 with SMTP id qa8mr3675pac.188.1375813134012; Tue, 06 Aug 2013 11:18:54 -0700 (PDT)
Received: from [10.129.24.70] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPSA id dg3sm3338383pbc.24.2013.08.06.11.18.49 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 06 Aug 2013 11:18:52 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 06 Aug 2013 12:18:41 -0600
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Joe Hildebrand <hildjj@cursive.net>
To: Phillip Hallam-Baker <hallam@gmail.com>
Message-ID: <CE2692E4.13C33%joe@cursive.net>
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
In-Reply-To: <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 18:18:58 -0000

On 8/6/13 11:34 AM, "Phillip Hallam-Baker" <hallam@gmail.com> wrote:

>The issue here is whether this proposal should be an IETF Proposed
>STANDARD.

standards-track != standard, right?

>I think that is nuts and I would think it just as much nuts if it was my
>proposal. We have no real world implementation experience by which I mean
>using it in a protocol and not writing some python

When I parse your words closely, I see you calling the idea "nuts", but
the emotional reaction I had was that you had called *me* "nuts".
Regardless, this seems a little out of proportion to what I thought was a
relatively polite attempt at dialog.  I'm worried that this kind of
interaction is exactly the sort of thing that scares new communities away
from participating here.

>Usually when the IETF publishes an algorithm it is given INFORMATIONAL or
>EXPERIMENTAL status. That is what originally happened with JSON, RFC 4627
>has INFORMATIONAL status despite the fact that at the time it was written
>there was a lot of implementation.

I would argue that if 4627 had received the more-thorough review that
would have come from being on standards track, it might not have had as
many problems as we're finding that it does.

>Using the individual submissions track as a way to circumvent working
>group process when there is an actual IETF JSON working group seems
>completely wrong to me.

First, this isn't JSON, even though interop with JSON was a goal.

Second, if the JSON wg wanted to recharter with a broader mission that
included CBOR and other similar protocols, that might be interesting to
me.  I don't get the sense from what I've seen in that group that there
would be enough energy for that, but that is obviously not for me to
decide.

Third, I think I said in my long message that I wouldn't mind having a
working group look at this, so I'm not sure why you'd accuse me of
circumventing process here.

>For the record, the issues I see are:
>
>1) This is an entirely new encoding and semantics. It is not JSON in
>binary which is what we actually need.

To me, it appears to be a proper superset of the parts of JSON that are
safe to use.

>2) No support for tag compression.

That's an interesting requirement, and one that I think could be added to
the design if there were others that felt motivated to help.  I think I
can see a way that it could be added later: create a new tag that precedes
a map of string-to-int conversions.

However, my intuition is that this wouldn't have radically better behavior
than gzip, and so I'd like to see some numbers to prove that the
complexity was worthwhile.

>3) No support for decimal floating point.

Section 2.4.3 describes decimal fractions.  Can you describe what other
behavior you'd like?  Or are you arguing that you'd like to see that moved
to being a core type?

>4) Its all or nothing, no layering.

Could you say more about that?  I see the tagging system as being exactly
a layering system, where you are explicitly invited to ignore any tag you
don't implement.

>The first one is my main complaint. I want to be able to use the binary
>and text JSON encodings interchangeably and not have the upper layers to
>have to bother with it at all.

I think I understand this.  I could see where my CBOR event-based parser
could also take JSON in, and generate the exact same events.  I might even
do that as a proof of concept.  Could you say more about what in CBOR you
think violates this?

Understandably, some type information will be lost converting
CBOR-to-JSON, but that will be true for anything that we come up with in
this space, I think.

>What I like in JSON is the lack of features and the fact that JSON covers
>95% of all my needs as is. All I want to add in to get to 100% features
>are the ability to encode floating point without loss and the ability to
>efficiently encode binary blobs.

I'd add dates to this, but I mostly agree with you.  CBOR, to me, was
close enough to what I wanted, explained in a way that made it easy to
implement, and I could ignore the bits that I didn't need for my use
cases.  I got over the fact that it was different than what I had
originally wanted, that it has some complexifying features like streaming
(added at the request of the community), and that we couldn't get any of
the existing players in the space to bring their work to us.

-- 
Joe Hildebrand





From br@brianrosen.net  Tue Aug  6 11:29:46 2013
Return-Path: <br@brianrosen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F98E21F8B04 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.171
X-Spam-Level: 
X-Spam-Status: No, score=-102.171 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 vpPZWkc094C2 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 11:29:40 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id B3E5F21E8088 for <ietf@ietf.org>; Tue,  6 Aug 2013 11:29:36 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id g10so558445pdj.12 for <ietf@ietf.org>; Tue, 06 Aug 2013 11:29:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=k3SCx5ikKfpHSTXVaz2fvnONmybe9xTV+9i66rmKoGs=; b=FYeI0iCtfkYyf2EClhkLrZ3lX/+ofuDjL5HcwnGv/AwO/RSNWiuehE2Uy94tZlLYiS H7UzsTKsKNX+gvd20hm6fW+6v1g8Oh9RETpTzgcremxFUpYJvKA2ml+lRPHHiUAdn8Dx cGnehhvbyLH8R3eM4C7OIbNZdqYQHqj5+Mfqnte17Ply/yrptoqp1orz7xAlzwyX8mLA KGJ55g7iYVqUhOrPr/WZ34/kTP6TXpb3dhrIj6e09Y8zULK7lIyH/oxG+y8c+KWJejCn QOQHCoHCM3AKaJXEuDL7OviOalrhAn4OK0/FNddum7iNek+KYMB5XrtNwpyTbpruF8Xj dW2w==
X-Gm-Message-State: ALoCoQlz3ucSwAm7zg1NErzPn1jQ4GDyTnjX1MqtAw6OyDuLupPjlnN6bcWmLQ8GI07988WlIKs5
MIME-Version: 1.0
X-Received: by 10.66.227.39 with SMTP id rx7mr259322pac.44.1375813773519; Tue, 06 Aug 2013 11:29:33 -0700 (PDT)
Received: by 10.70.23.225 with HTTP; Tue, 6 Aug 2013 11:29:33 -0700 (PDT)
X-Originating-IP: [24.112.236.47]
In-Reply-To: <5328.1375810283@sandelman.ca>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <5328.1375810283@sandelman.ca>
Date: Tue, 6 Aug 2013 14:29:33 -0400
Message-ID: <CAOPrzE0pMop6NBR1kO_UW269UNibuMQ6dbx5sh5bZkvefYwvzw@mail.gmail.com>
Subject: Re: RPS Accessibility
From: Brian Rosen <br@brianrosen.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=047d7b111f3f3f8c3904e34b9bfa
Cc: "iaoc-rps@ietf.org" <iaoc-rps@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, 06 Aug 2013 18:29:46 -0000

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

Could be an app that put you in the queue and used your
laptop/tablet/smartphone microphone to get the audio.

On Tuesday, August 6, 2013, Michael Richardson wrote:

>
> Dave Crocker <dhc@dcrocker.net <javascript:;>> wrote:
>     > An entirely different approach would be to have all speakers make a
>     > 'reservation' into a single meetecho (or whatever) online queue, and
> then get
>     > called in order, whether local or remote and independent of what
> microphone
>     > they are at.  This gets accurate identification into the online
> system, with
>     > the entry task distributed.
>
> +1.
> And move the microphones to the people, rather than the other way around.
>
> We can easily have three or four microphones that can play leap-frog around
> the room.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca <javascript:;>>, Sandelman
> Software Works
>
>
>

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

Could be an app that put you in the queue and used your laptop/tablet/smart=
phone microphone to get the audio.<span></span><br><br>On Tuesday, August 6=
, 2013, Michael Richardson  wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Dave Crocker &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#3=
9;, &#39;dhc@dcrocker.net&#39;)">dhc@dcrocker.net</a>&gt; wrote:<br>
=A0 =A0 &gt; An entirely different approach would be to have all speakers m=
ake a<br>
=A0 =A0 &gt; &#39;reservation&#39; into a single meetecho (or whatever) onl=
ine queue, and then get<br>
=A0 =A0 &gt; called in order, whether local or remote and independent of wh=
at microphone<br>
=A0 =A0 &gt; they are at. =A0This gets accurate identification into the onl=
ine system, with<br>
=A0 =A0 &gt; the entry task distributed.<br>
<br>
+1.<br>
And move the microphones to the people, rather than the other way around.<b=
r>
<br>
We can easily have three or four microphones that can play leap-frog around=
<br>
the room.<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;c=
vml&#39;, &#39;mcr+IETF@sandelman.ca&#39;)">mcr+IETF@sandelman.ca</a>&gt;, =
Sandelman Software Works<br>
<br>
<br>
</blockquote>

--047d7b111f3f3f8c3904e34b9bfa--

From cabo@tzi.org  Tue Aug  6 12:11:34 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1F921F9DF6 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djbkFqsVDR7U for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:11:28 -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 30D5B21F995E for <ietf@ietf.org>; Tue,  6 Aug 2013 12:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r76JBOTe006832; Tue, 6 Aug 2013 21:11:24 +0200 (CEST)
Received: from [192.168.217.105] (p54891DAF.dip0.t-ipconnect.de [84.137.29.175]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 05697434; Tue,  6 Aug 2013 21:11:23 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CE2692E4.13C33%joe@cursive.net>
Date: Tue, 6 Aug 2013 21:11:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E81E938-203B-4E8A-BCAF-467782DA3E03@tzi.org>
References: <CE2692E4.13C33%joe@cursive.net>
To: Joe Hildebrand <hildjj@cursive.net>
X-Mailer: Apple Mail (2.1508)
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: Tue, 06 Aug 2013 19:11:34 -0000

>> 2) No support for tag compression.

(I assume this was about map keys, not about tags.)

> That's an interesting requirement, and one that I think could be added =
to
> the design if there were others that felt motivated to help.  I think =
I
> can see a way that it could be added later: create a new tag that =
precedes
> a map of string-to-int conversions.

I'd probably do it the other way around:

	tagN([{1: "foo", 2: "bar"}, ...abbreviated data item...])
Where an abbreviated data item of the form
	[1, 2, 3, {1: "beer", 2: "wine", "baz": 1}, 5, 6]
would then be interpreted as
	[1, 2, 3, {"foo": "beer", "bar": "wine", "baz": 1}, 5, 6]

Yes, processing of this kind is easy to add as a tag.
If the first parameter is instead a URI (preferably ni: scheme), it =
could save carrying around a large dictionary.

> However, my intuition is that this wouldn't have radically better =
behavior
> than gzip, and so I'd like to see some numbers to prove that the
> complexity was worthwhile.

I share that intuition.  CBOR is intended to be useful also in those =
environments where running a full compression algorithm is impractical; =
here such a scheme could still have benefits.

>> The first one is my main complaint. I want to be able to use the =
binary
>> and text JSON encodings interchangeably and not have the upper layers =
to
>> have to bother with it at all.

(The applications I have in mind use media types, but:)

> I think I understand this.  I could see where my CBOR event-based =
parser
> could also take JSON in, and generate the exact same events.  I might =
even
> do that as a proof of concept.  Could you say more about what in CBOR =
you
> think violates this?

Well, if you don't have a media type, and don't know whether you'll get =
a JSON text or a CBOR data item, you may need to mechanically =
distinguish them.
E.g., the following six characters can occur at the start of a JSON =
text.
All are valid as start (or only) byte of a CBOR data item:

Byte    JSON meaning                CBOR interpretation

%x20  ; Space                       -1
%x09  ; Horizontal tab              9
%x0A  ; Line feed or New line       10
%x0D  ; Carriage return             13
%x5B  ; [ left square bracket       starts byte string
%x7B  ; { left curly bracket        starts UTF-8 string

(Well, for any valid JSON texts, heuristics might tell you the string =
data items a CBOR parser sees are unrealistically large.)

If a CBOR application does require initial signature bytes for =
self-description purposes, I would suggest using something like

	0xd8 0xf8 ...data item...

which decodes as tag248(data item); we could define 248 as a no-op tag.

(I'm still working on your other message -- lots of juicy input, thank =
you!)

Gr=FC=DFe, Carsten


From Ted.Lemon@nominum.com  Tue Aug  6 12:14:12 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 134D021E80AE; Tue,  6 Aug 2013 12:14:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.559
X-Spam-Level: 
X-Spam-Status: No, score=-106.559 tagged_above=-999 required=5 tests=[AWL=0.040, 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 NYoDcCdeXWU2; Tue,  6 Aug 2013 12:14:05 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 517EE21F995E; Tue,  6 Aug 2013 12:14:05 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUgFK/MrWLjci7g6v0GFwlhbJjZUG/1aP@postini.com; Tue, 06 Aug 2013 12:14:05 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BEE241B8295; Tue,  6 Aug 2013 12:14:04 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B644D190060; Tue,  6 Aug 2013 12:14:04 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 12:14:04 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOkDNSS43GUutwDE+rfApQjh1upZmGzZ0AgAH6VoCAAD88AA==
Date: Tue, 6 Aug 2013 19:14:04 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net>
In-Reply-To: <520115F3.6050908@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <1295F7DFA01A514A84608F8E5B062BBE@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, Paul Aitken <paitken@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:14:12 -0000

On Aug 6, 2013, at 11:27 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> It was an experiment.  It was awkward and inaccurate.  It also raised bas=
ic privacy concerns, what with wearing something that can be tracked as you=
 move around.

Ironically, this IETF everyone who stayed at the Intercontinental was walki=
ng around with an RFID key in their pocket the whole meeting.   How many of=
 us put them in faraday cages?

I thought the experiment in Hiroshima went well, and wish we had made it st=
andard practice.   It is _really_ hard to get people to say their names con=
sistently in a way that is intelligible to the note-taker; I would go so fa=
r as to say that this is unachievable.


From Ted.Lemon@nominum.com  Tue Aug  6 12:15:35 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63DC721F9DB2; Tue,  6 Aug 2013 12:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level: 
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 xhuRomtlWTS9; Tue,  6 Aug 2013 12:15:27 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id EB20521F9B18; Tue,  6 Aug 2013 12:15:26 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUgFLTq44qMSfnk0Qy4i0p/gZPOg7S99y@postini.com; Tue, 06 Aug 2013 12:15:27 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id EADB21B8295; Tue,  6 Aug 2013 12:15:25 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E4765190060; Tue,  6 Aug 2013 12:15:25 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 12:15:25 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOkDNSS43GUutwDE+rfApQjh1upZmGzZ0AgAH6VoCAAD+cgA==
Date: Tue, 6 Aug 2013 19:15:25 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net>
In-Reply-To: <520115F3.6050908@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8456FC8AD9078D4CBF089D1C91AA00A9@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, Paul Aitken <paitken@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:15:36 -0000

On Aug 6, 2013, at 11:27 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> An entirely different approach would be to have all speakers make a 'rese=
rvation' into a single meetecho (or whatever) online queue, and then get ca=
lled in order, whether local or remote and independent of what microphone t=
hey are at.  This gets accurate identification into the online system, with=
 the entry task distributed.

I would not mind this system intensely, but bear in mind that it requires e=
verybody to bring a mobile device of some sort that can be used to do this =
registration, and they will have to keep that device out and active during =
all meetings.   If their battery dies, they can no longer participate, or w=
ill require exception handling.


From johnl@iecc.com  Tue Aug  6 12:19:58 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840BF21F9A13 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.432
X-Spam-Level: 
X-Spam-Status: No, score=-110.432 tagged_above=-999 required=5 tests=[AWL=0.767, 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 0S2c-5agam5F for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:19:54 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0A521F98AD for <ietf@ietf.org>; Tue,  6 Aug 2013 12:19:53 -0700 (PDT)
Received: (qmail 3546 invoked from network); 6 Aug 2013 19:19:52 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 6 Aug 2013 19:19:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52014c57.xn--hew.k1308; i=johnl@user.iecc.com; bh=y83qKY8ndAKy5txnE+mXxmMlazlYNWD/nKjYJOIzKrA=; b=O+j1f93fy4hmxqvBAAUK+HiPCXNAI2Dg6YNozqSm4fGUHZIFxxthgpZl+LJTT8CEdH5Gt3zRJFMPbuxv42cfCFreVK8v+iwQiCZ/D7PGkCelVtmYax0YUvV0jQBcnVeWnkr6F7e9km1WJOVQ9mJH3AHibfGAkxGc7PfclnFZ1WdLwfScGtbt9x2N6MozOIPW+q/OGEkgt6x4vLPUMc0TzqgCXer3rNc50T2RTBKthxnPnADF7w2hcsaEdnHlQqJh
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52014c57.xn--hew.k1308; olt=johnl@user.iecc.com; bh=y83qKY8ndAKy5txnE+mXxmMlazlYNWD/nKjYJOIzKrA=; b=mGiaswp4CpK15YMipwHy5rGCRhtyO1waEffP0AykruWDZ9XD3wq/rriCasZxm9qSe4SwRNyTqi8b1psJsv1F2cJ7hWOySicbIo/el6v9C3bQEDAmYnju4A8yjMjniNy2tBdNlDCUE2hKf5xVvQnRtl6ZTVCYrvrGQSMvSrSJ07p65Mb03RXl4J702fc492kIJEOUfGykJRNaoA3ePb/ZntiKEvfuvMtIRc6eGWoAhNK8oDub4oxv5qop2xCRhuJD
Date: 6 Aug 2013 19:19:29 -0000
Message-ID: <20130806191929.36199.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:19:58 -0000

>Ironically, this IETF everyone who stayed at the Intercontinental was walking around
>with an RFID key in their pocket the whole meeting.   How many of us put them in
>faraday cages?

I put all of my cards in a faraday cage, but perhaps that's just me,
and because I carry an RFID passport card.

R's,
John

From Aaron.Ding@cl.cam.ac.uk  Tue Aug  6 12:35:47 2013
Return-Path: <Aaron.Ding@cl.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8E721F9F52 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCv4fqLtQGnK for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:35:41 -0700 (PDT)
Received: from ppsw-52.csi.cam.ac.uk (ppsw-52.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f52]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD8B21F9F2B for <ietf@ietf.org>; Tue,  6 Aug 2013 12:35:41 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-2b.csi.cam.ac.uk ([131.111.9.35]:38292) by ppsw-52.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.138]:25) with esmtp id 1V6n2i-0007yO-D4 (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 20:35:40 +0100
Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2b.csi.cam.ac.uk with esmtp id 1V6n2h-000XbM-VZ (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 20:35:40 +0100
Received: from s218i40.wolfson.cam.ac.uk ([131.111.218.40]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 06 Aug 2013 20:35:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 06 Aug 2013 20:35:39 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: moore@network-heretics.com
Subject: Re: procedural question with remote participation
Message-ID: <22caad687b128c92809dec711ecf9dda@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.2
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:35:47 -0000

On 06/08/13 19:03, Keith Moore wrote:
> 
> But if we're only concerned with making presentation slides available, 
> we're selling ourselves very short.  That's the point I'm trying to 
> make.
> 
> Keith


Hi Keith,

Thanks for clarifying it - agree with you fully on this point.

Keeping a clear goal in mind helps improve our current practice, and I 
pretty much like what Joe hinted:


On 06/08/13 18:41, Joe Abley wrote:
> The best outcome at a working group meeting is that, as a presenter, 
> you spend most of your time listening rather than talking. If the mic 
> line is empty, you probably should not have been on the agenda.  Joe


How to get remote participants involved in meaningful discussion 
deserves our close attention, besides to improve the experience for f2f 
participants, e.g., presenters. (IMO, when to upload slides and how to 
coordinate is a WG specific issue and WG/session chairs can define a 
rule of conduct in their own meetings so it works best there, for both 
remote and f2f)

Cheers,
Aaron


PS: I personally find it rather funny to see people claiming one's own 
approach works better and so forth implicitly indicating they really 
understand what remote/f2f participants need, and even so, we others 
should follow... which somehow reminds me Dave Crocker once joked in 
another thread that

"almost everyone claims that they are a better than average driver" ;)

From jabley@hopcount.ca  Tue Aug  6 12:38:08 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E02021F9FF3 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5TDnFcJUEPF for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:38:08 -0700 (PDT)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E720721F9FE9 for <ietf@ietf.org>; Tue,  6 Aug 2013 12:38:07 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id jh10so1166417pab.31 for <ietf@ietf.org>; Tue, 06 Aug 2013 12:38:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=X4QOFezbc3iE29NbTBn0+CldVrHWwNA5ZkZSnYQrtfA=; b=Pk9tBFJ9Kel3FaIhsSJhoVlF+mTYkBJgF2WPHCMNY/UzjskGLgWSahFjmXXKXzU5QC kUem+fViAJtQs4Log4MVTNiM4reGOaKq0mCbrCYz1rpYb20ut4YpnGd7spl+/N7ONcsC ZGCMESaTdsJICaTHzMAUL8NdvgZkcHCE23ynQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=X4QOFezbc3iE29NbTBn0+CldVrHWwNA5ZkZSnYQrtfA=; b=NtQfrrlQzuMFVgb4du4Zwd2DhdhrFCKu4n3dVXu7bJCLlpPHIFswia5mbedIyFgsRr NZly0TJNROCG2hjxr0v0w8cQFChh6KgybXuAXfRzjL1sowFg4kyEFh6TmTGQqpqO6pTL LI2n1RuuZpR6Oy1sOKjyJakyx1ERmms1SOdeCcgXNcB+U5BM7IkzapA6BtTdUmTF6Gqv ewj0yWBCyxBWBwzDweszG+qRCYT1r0RjDuRN+cvafvve3gmzo6IP8jDtBK1V4u84lin9 jHM3sa25m6ZbQA6RjhLGpyPLtfOP+ajJc5/H0q/VXJTrI3YyAb18jJKWsUc3D6EV5TPD Dh/w==
X-Gm-Message-State: ALoCoQkZ+UkIGN5Bh1ayaP7lF7Wc0e/WNSFfbnbxtP66NvNSqXqf8D/ffUbPWX9sBUdOgAtxlB/O
X-Received: by 10.66.26.112 with SMTP id k16mr500195pag.65.1375817887662; Tue, 06 Aug 2013 12:38:07 -0700 (PDT)
Received: from [199.212.90.33] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id fa5sm3650194pbb.3.2013.08.06.12.38.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 12:38:06 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <22caad687b128c92809dec711ecf9dda@cam.ac.uk>
Date: Tue, 6 Aug 2013 15:38:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6057562-0D20-472C-9951-2E462E4AE221@hopcount.ca>
References: <22caad687b128c92809dec711ecf9dda@cam.ac.uk>
To: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
X-Mailer: Apple Mail (2.1508)
Cc: moore@network-heretics.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:38:08 -0000

On 2013-08-06, at 15:35, Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk> wrote:

> PS: I personally find it rather funny to see people claiming one's own =
approach works better and so forth implicitly indicating they really =
understand what remote/f2f participants need,

For the record, I have zero experience consuming my own in-person =
presentations whilst attending remotely.

I will say that Dan York did a stand-up job in dnsop last week =
channeling jabber chatter to the microphone.


Joe


From hildjj@cursive.net  Tue Aug  6 12:46:00 2013
Return-Path: <hildjj@cursive.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 425AF21F9DDE for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xtXef-bopii for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:45:59 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 7555121F9DCB for <ietf@ietf.org>; Tue,  6 Aug 2013 12:45:59 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so893388pbb.6 for <ietf@ietf.org>; Tue, 06 Aug 2013 12:45:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=xB4kywXgxgS5E02MiA/vFI6Vof5APO1qVhUWZu17miA=; b=TRRf6SVjtbDp7TPPRvIVS1iGKDYZ4ci06WKJ6Z7ChDT0OnGb6v7Qq4+iqiA3wfzawE Js1oPNMxSVN8rDtK/85/g264/UZRLNP/DgqT5W70gM3TCWTUcS87YqlsZxUZB2TuVNqs kZ+AMHKq6UX5/JT+HWKMW7/W3OWePomQikd10=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=xB4kywXgxgS5E02MiA/vFI6Vof5APO1qVhUWZu17miA=; b=YJtjTVBYbTviYkhR61AdW/VbKrK+yQUr1CW8Mmil9sOsII2dxv/UaFqnFQ7Npd4xD0 2TpgRxNazUrsu02Mi1JIeBcqO70wRBj9hidzzppN2F60gL6FUiXz5oTesTxCuKSap9TY 0ozKfYYS/C51gM0cGTW6Hkrs7PvcnV9rWalym4SYyu0iVE4kHburAFMXqk3M5Su39fmA /dVDEhVHnw/WJcuQws4Rrpl35b6HqR+OI2LF3j0D2DIMgFE2wBxUHBMVYDviCf43xe4x yZ8141SaVw49adCVj3aPm/S2qLbw2RBc5DxNOq8RnQeP0PXC7rFgZxdnNCe849QZZ1Ge G9hQ==
X-Gm-Message-State: ALoCoQm1UqAYKiKwIZQkH5BFeB5+h0CncOJFE8ZKT92c3feewwRa9CrufSx6jCM7w3g6btnLjSxD
X-Received: by 10.68.28.1 with SMTP id x1mr3211472pbg.113.1375818359167; Tue, 06 Aug 2013 12:45:59 -0700 (PDT)
Received: from [10.129.24.70] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPSA id il4sm3620392pbb.36.2013.08.06.12.45.53 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 06 Aug 2013 12:45:57 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 06 Aug 2013 13:45:46 -0600
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Joe Hildebrand <hildjj@cursive.net>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <CE26AA2D.13CCC%joe@cursive.net>
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
In-Reply-To: <4E81E938-203B-4E8A-BCAF-467782DA3E03@tzi.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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: Tue, 06 Aug 2013 19:46:00 -0000

On 8/6/13 1:11 PM, "Carsten Bormann" <cabo@tzi.org> wrote:

>If a CBOR application does require initial signature bytes for
>self-description purposes, I would suggest using something like
>
>	0xd8 0xf8 ...data item...
>
>which decodes as tag248(data item); we could define 248 as a no-op tag.

Or a no-op simple value; we could easily pick one that did not generate a
valid first character for JSON.

-- 
Joe Hildebrand





From Aaron.Ding@cl.cam.ac.uk  Tue Aug  6 12:54:56 2013
Return-Path: <Aaron.Ding@cl.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 737E521F9B0A; Tue,  6 Aug 2013 12:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 mfhARXpTl-Gr; Tue,  6 Aug 2013 12:54:50 -0700 (PDT)
Received: from ppsw-32.csi.cam.ac.uk (ppsw-32.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f32]) by ietfa.amsl.com (Postfix) with ESMTP id 89A4E21F9A1E; Tue,  6 Aug 2013 12:54:50 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-2b.csi.cam.ac.uk ([131.111.9.35]:40475) by ppsw-32.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtp id 1V6nLF-00048n-0i (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 20:54:49 +0100
Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2b.csi.cam.ac.uk with esmtp id 1V6nLF-000Z9k-5K (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Tue, 06 Aug 2013 20:54:49 +0100
Received: from s218i40.wolfson.cam.ac.uk ([131.111.218.40]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Tue, 06 Aug 2013 20:54:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Tue, 06 Aug 2013 20:54:49 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: mcr+ietf@sandelman.ca
Subject: Re: [iaoc-rps] RPS Accessibility
Message-ID: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.2
Cc: iaoc-rps@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:54:56 -0000

On 06/08/13 18:31, Michael Richardson wrote:
> 
> Dave Crocker <dhc@dcrocker.net> wrote:
>     > An entirely different approach would be to have all speakers make 
> a
>     > 'reservation' into a single meetecho (or whatever) online queue, 
> and then get
>     > called in order, whether local or remote and independent of what 
> microphone
>     > they are at.  This gets accurate identification into the online 
> system, with
>     > the entry task distributed.
> 
> +1.

+1 too.

> And move the microphones to the people, rather than the other way 
> around.

This is indeed friendly, although standing up to walk a bit is also 
good, at least f2f participants won't sit on chairs the whole day..  
adding this option to the existing one will be nice.


Cheers,
Aaron

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


From dhc@dcrocker.net  Tue Aug  6 12:57:50 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECEC021F9A1E; Tue,  6 Aug 2013 12:57:50 -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 R-lcx-x+nbFX; Tue,  6 Aug 2013 12:57:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E879211E80D1; Tue,  6 Aug 2013 12:57:37 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r76JvVfO015020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Aug 2013 12:57:35 -0700
Message-ID: <52015528.8050608@dcrocker.net>
Date: Tue, 06 Aug 2013 12:57:28 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [iaoc-rps] RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 06 Aug 2013 12:57:35 -0700 (PDT)
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, Paul Aitken <paitken@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:57:51 -0000

On 8/6/2013 12:15 PM, Ted Lemon wrote:
> On Aug 6, 2013, at 11:27 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> An entirely different approach would be to have all speakers make a 'reservation' into a single meetecho (or whatever) online queue, and then get called in order, whether local or remote and independent of what microphone they are at.  This gets accurate identification into the online system, with the entry task distributed.
>
> I would not mind this system intensely, but bear in mind that it requires everybody to bring a mobile device of some sort that can be used to do this registration, and they will have to keep that device out and active during all meetings.   If their battery dies, they can no longer participate, or will require exception handling.


Lean over to a neighbor and ask them to put you into the queue.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jabley@hopcount.ca  Tue Aug  6 12:58:15 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA6AA21F9C6F for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDC0FQTHvFxS for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 12:58:15 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 127EB21F9B53 for <ietf@ietf.org>; Tue,  6 Aug 2013 12:58:14 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so911060pbb.27 for <ietf@ietf.org>; Tue, 06 Aug 2013 12:58:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=sAvzwU8Ahea0XIXdqWbxk8cSRBJvF8Wa5C77QWQ3hFc=; b=QZAYJ7y0Ld2Jg/OPfLCxQ4DfMDea5PNU7vCnAkBZ2LRh75B0GlTvDoV6W3YOdujRf9 QDKlccMvwS0p3HFDNE9FXogO1C/cVYC0taqVeqNIbF9vnuAb62hnTiqd8eC2Ing+/cFL V6KPHPd6/f71/v4aauLJEqcL7wgS+OwV34uRo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=sAvzwU8Ahea0XIXdqWbxk8cSRBJvF8Wa5C77QWQ3hFc=; b=nm+TvbV6g2pwsjj2AwMtrSvqwv63XwYrrr+rKrvboN6TEwyJtm4/eXPrKs3x0BAqJw 0mCb9dZIBpmhm++MT0QUxEyw94scXB+6VeIb/PZIB1370qkeVVbLzZomA05aIQfXGMVw dA6JlQAM3wfOO5LbxzQ2D4BhnzQZoRO6lgQItN6O6cnCSA84rsTyWDKaRvqAWEzFJBFe wVuw3MxX0EJAcBpEXCtLHPB2Feq9i9xsbsa/85wj4kl6Sy4xXSRAokvqd8gxWs2rNPEV D0szBv8n1D3lO5GC7VvP84n2MqDs18140/I9J3on7fd04XIDlPSIK/DHgGlpvVAnQum0 +y1A==
X-Gm-Message-State: ALoCoQmuV5/ajiKKSwrEncfWxAT1IwoypH9GOfPZbqNJHGsw0wM3I4J56ZDgJi/p9W6ByspzQ+gZ
X-Received: by 10.66.2.164 with SMTP id 4mr598833pav.55.1375819093745; Tue, 06 Aug 2013 12:58:13 -0700 (PDT)
Received: from [199.212.90.33] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id a5sm3710215pbw.4.2013.08.06.12.58.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 12:58:12 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [iaoc-rps] RPS Accessibility
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk>
Date: Tue, 6 Aug 2013 15:58:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca>
References: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk>
To: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
X-Mailer: Apple Mail (2.1508)
Cc: iaoc-rps@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 19:58:16 -0000

On 2013-08-06, at 15:54, Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk> wrote:

> On 06/08/13 18:31, Michael Richardson wrote:
>=20
>> And move the microphones to the people, rather than the other way =
around.
>=20
> This is indeed friendly, although standing up to walk a bit is also =
good, at least f2f participants won't sit on chairs the whole day..  =
adding this option to the existing one will be nice.

For what it's worth (not much) I would miss the line at the mic. There =
are useful conversations that happen within the line that I think we =
would lose if the mic followed the speaker, and I also think that =
pipelining the people at the mic promotes more fluid conversation. But =
these are minor points, and I'm mainly just waxing nostalgic.


Joe=

From melinda.shore@gmail.com  Tue Aug  6 13:03:57 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB3821E809A for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 13:03: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 FCABiivhpIyS for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 13:03:57 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1308E21F9EE9 for <ietf@ietf.org>; Tue,  6 Aug 2013 13:03:56 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp2so917868pbb.14 for <ietf@ietf.org>; Tue, 06 Aug 2013 13:03:56 -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=Q6vnFXI2CSpVG3tEo/i17v/QsmYqaLJm8ghNTFuqj+s=; b=Mz/77TfHvXmHt3eu0NbhbDcGc4DTXsum13k0IqrpeSU1b7lWhqIhDByRqvH+rywsA5 oIKPbgu46dET0SQbeKFCZRPQR5Kc5dXabg/L3hZCJD79OGWUOgOoC6CFIgLcMl+nxTR5 e3XftKczwyUQ3Tu0Mg7VyW+GU13i2LcEGtwHjQ7tPLNN2nHIO2B990IFBcKjf+xBJ+qk tw09c/kdGZMvuIp0xf1AXgdbUTy5oMiv0MWuN4VURXsLc6/bj5YfaBr/c7zWwFzol2c7 kp4ESKjnrjbe8/vYN+4qBKf3LEQapisYVnkxQx7qUsXCWagP6BBxjuliAhQlaDq5ueIW APhw==
X-Received: by 10.68.201.6 with SMTP id jw6mr3262550pbc.202.1375819436747; Tue, 06 Aug 2013 13:03:56 -0700 (PDT)
Received: from spandex.local (66-230-112-160-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.160]) by mx.google.com with ESMTPSA id iu7sm3725265pbc.8.2013.08.06.13.03.55 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 13:03:55 -0700 (PDT)
Message-ID: <520156A9.3090802@gmail.com>
Date: Tue, 06 Aug 2013 12:03:53 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
References: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk> <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca>
In-Reply-To: <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 20:03:57 -0000

On 8/6/13 11:58 AM, Joe Abley wrote:
> For what it's worth (not much) I would miss the line at the mic.
> There are useful conversations that happen within the line that I
> think we would lose if the mic followed the speaker, and I also think
> that pipelining the people at the mic promotes more fluid
> conversation. But these are minor points, and I'm mainly just waxing
> nostalgic.

I actually think that this is not a small point.  The people in
line are the people with issues and the ability to hash stuff out
quickly is pretty nice.

Melinda


From Ted.Lemon@nominum.com  Tue Aug  6 13:16:43 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD5021F9DDC; Tue,  6 Aug 2013 13:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.56
X-Spam-Level: 
X-Spam-Status: No, score=-106.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 p1Fr1Xb9jKlm; Tue,  6 Aug 2013 13:16:37 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id C5F1F21F9D89; Tue,  6 Aug 2013 13:16:33 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUgFZoaD/2QcoRa1Bz4jSodb9InYpr+bg@postini.com; Tue, 06 Aug 2013 13:16:33 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 68AF31B8288; Tue,  6 Aug 2013 13:16:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 629F7190060; Tue,  6 Aug 2013 13:16:33 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 13:16:33 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOkDNSS43GUutwDE+rfApQjh1upZmGzZ0AgAH6VoCAACKJgIAALicA
Date: Tue, 6 Aug 2013 20:16:32 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775247EC1@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <5328.1375810283@sandelman.ca>
In-Reply-To: <5328.1375810283@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20437700EFCEBE4BAD2158C478AEB03E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc-rps@ietf.org" <iaoc-rps@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, 06 Aug 2013 20:16:43 -0000

On Aug 6, 2013, at 1:31 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrot=
e:
> We can easily have three or four microphones that can play leap-frog arou=
nd
> the room.

+1

Of course, then we need a facilitator to wrest it away from filibusterers o=
r simply a mechanism for the chairs to mute a mic.


From Ted.Lemon@nominum.com  Tue Aug  6 13:30:17 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 435FC11E80D1; Tue,  6 Aug 2013 13:30:17 -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 MoD2NnA0x9R8; Tue,  6 Aug 2013 13:30:10 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 56DF721F9AC4; Tue,  6 Aug 2013 13:30:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUgFc0nQ+h4AckHYwsMbJ0n1RhgMebRU8@postini.com; Tue, 06 Aug 2013 13:30:10 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D6EB11B8294; Tue,  6 Aug 2013 13:30:08 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 9845C190060; Tue,  6 Aug 2013 13:30:06 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 13:30:06 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Paul Aitken <paitken@cisco.com>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOkDNSS43GUutwDE+rfApQjh1upZmGzZ0AgAH6VoCAAD88AIAADmgAgAAG1YA=
Date: Tue, 6 Aug 2013 20:30:05 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775248028@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.com> <52015714.9010104@cisco.com>
In-Reply-To: <52015714.9010104@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <8295663E9675524C95ED44CCCE3CF234@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, "<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: Tue, 06 Aug 2013 20:30:17 -0000

On Aug 6, 2013, at 4:05 PM, Paul Aitken <paitken@cisco.com> wrote:
> Could there be a conflict if IETF badges also have RFID tags attached, eg=
 we get "Room 1283" at the mic?

No.  Only known IDs would register.   The RFID badge just has a number=97it=
 doesn't say "Room 1283."


From hadriel.kaplan@oracle.com  Tue Aug  6 13:37:20 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7501721F9EF0; Tue,  6 Aug 2013 13:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.488
X-Spam-Level: 
X-Spam-Status: No, score=-6.488 tagged_above=-999 required=5 tests=[AWL=0.111,  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 Ac5iOhGoG9zI; Tue,  6 Aug 2013 13:37:14 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0000B21F9E6B; Tue,  6 Aug 2013 13:37:13 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r76KbC6H003392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Aug 2013 20:37:13 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r76KbCRd022737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 20:37:12 GMT
Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r76KbBHN029630; Tue, 6 Aug 2013 20:37:11 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 06 Aug 2013 13:37:11 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [iaoc-rps] RPS Accessibility
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com>
Date: Tue, 6 Aug 2013 16:37:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: iaoc-rps@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 20:37:20 -0000

[to no one in particular]

Uhhh... I can't tell if you folks are being serious about this idea or =
not, but in case you are being serious... ISTM there's such a thing as =
too much technology being a bad thing.  If you think technical glitches =
now-and-then cause issues with remote participants today, wait until =
physical participants have to deal with glitches in something like this. =
 "KISS" isn't just a rock-band from the 70's, it's also a useful =
principle known to many today.

If the problem is "we don't know who's speaking", then fix that problem. =
 In WGs I go to, both the WG chairs and the jabber scribes regularly =
yell "NAME!" if someone forgets to say it.  Unlike DNS Ops, this isn't =
rocket science.

Besides, it's not a bad thing to make people get in mic lines, if for no =
other reason than to have a small barrier threshold for folks to decide =
it's worth it to say something.[1]

-hadriel
[1] yes, I recognize the irony in this statement, since I get up to the =
mic every 15 seconds and say inane things.  We can't stop all people =
like me from wasting meeting time, we can just reduce the number of =
similar people wasting time.


On Aug 6, 2013, at 3:15 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 6, 2013, at 11:27 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> An entirely different approach would be to have all speakers make a =
'reservation' into a single meetecho (or whatever) online queue, and =
then get called in order, whether local or remote and independent of =
what microphone they are at.  This gets accurate identification into the =
online system, with the entry task distributed.
>=20
> I would not mind this system intensely, but bear in mind that it =
requires everybody to bring a mobile device of some sort that can be =
used to do this registration, and they will have to keep that device out =
and active during all meetings.   If their battery dies, they can no =
longer participate, or will require exception handling.
>=20


From Ted.Lemon@nominum.com  Tue Aug  6 13:46:20 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6D521F9F2B; Tue,  6 Aug 2013 13:46:20 -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 dYPMkj5T90l4; Tue,  6 Aug 2013 13:46:14 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id E4BC611E80EA; Tue,  6 Aug 2013 13:46:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUgFgkAVDVpWs8kx47LYkqaqNtmZe+HLm@postini.com; Tue, 06 Aug 2013 13:46:14 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id DA34E1B8288; Tue,  6 Aug 2013 13:46:07 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id D23EE190060; Tue,  6 Aug 2013 13:46:07 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 6 Aug 2013 13:46:07 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOkDNSS43GUutwDE+rfApQjh1upZmGzZ0AgAH6VoCAAD+cgIAAFtSAgAAChIA=
Date: Tue, 6 Aug 2013 20:46:06 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com> <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com>
In-Reply-To: <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <272A7D10A49B1348A580A6825A1E741E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<iaoc-rps@ietf.org>" <iaoc-rps@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 20:46:20 -0000

On Aug 6, 2013, at 4:37 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com> wrot=
e:
> If the problem is "we don't know who's speaking", then fix that problem. =
 In WGs I go to, both the WG chairs and the jabber scribes regularly yell "=
NAME!" if someone forgets to say it.  Unlike DNS Ops, this isn't rocket sci=
ence.

This doesn't work very well.   In one meeting where I was scribing this IET=
F, I had to shout NAME at the same person several times, because he didn't =
state his name clearly enough for me to be sure I'd gotten it, and so it di=
dn't stick.   I hate doing this=97I think it's disruptive, and nobody likes=
 getting yelled at.   I certainly don't like _having_ to yell.


From dougb@dougbarton.us  Tue Aug  6 13:47:35 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C99721E809B for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 13:47:35 -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 mVZJpLt9Q2rz for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 13:47:35 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0926721F9EEB for <ietf@ietf.org>; Tue,  6 Aug 2013 13:47:35 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:538:c54:26c8:7f50] (unknown [IPv6:2001:470:d:5e7:538:c54:26c8:7f50]) by dougbarton.us (Postfix) with ESMTPSA id 95EFE22BA6 for <ietf@ietf.org>; Tue,  6 Aug 2013 20:47:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1375822053; bh=ZIIbmsGadMx1MfMslYGqarfrD3xiKTXCvaLFQWmqzW0=; h=Date:From:To:Subject:References:In-Reply-To; b=sKu1UZ+FhRnZOydDZrP8mjc2X3AUYEDtXHhVQsRWTqkyq3Q+JvJ1ryhgaOuCLVEbR HjScEgSXq6jghkYvXaU7DnFCg8TKxQfugM1VegeH7NjYqNbAIXw7StU+OW7r775X/g ip639hr9pyK+r77qVLqitxv06GcGPcev+nqor79E=
Message-ID: <520160E5.6090506@dougbarton.us>
Date: Tue, 06 Aug 2013 13:47:33 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com> <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com> <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 20:47:35 -0000

On 08/06/2013 01:46 PM, Ted Lemon wrote:
> On Aug 6, 2013, at 4:37 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com> wrote:
>> If the problem is "we don't know who's speaking", then fix that problem.  In WGs I go to, both the WG chairs and the jabber scribes regularly yell "NAME!" if someone forgets to say it.  Unlike DNS Ops, this isn't rocket science.
>
> This doesn't work very well.   In one meeting where I was scribing this IETF, I had to shout NAME at the same person several times, because he didn't state his name clearly enough for me to be sure I'd gotten it, and so it didn't stick.   I hate doing this—I think it's disruptive, and nobody likes getting yelled at.   I certainly don't like _having_ to yell.

Then come up with an alternate proposal. Fixing this problem is 
non-optional.


From dougb@dougbarton.us  Tue Aug  6 13:48:15 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7723211E80EA for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 13:48: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 d3i4UZfsIwNh for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 13:48:11 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE2221E808E for <ietf@ietf.org>; Tue,  6 Aug 2013 13:48:11 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:538:c54:26c8:7f50] (unknown [IPv6:2001:470:d:5e7:538:c54:26c8:7f50]) by dougbarton.us (Postfix) with ESMTPSA id C9CEC22BA6 for <ietf@ietf.org>; Tue,  6 Aug 2013 20:48:10 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1375822090; bh=YYSp04Bjk2K4IXMyW9zkpcJHcBTraMDTamSRsejIpgc=; h=Date:From:To:Subject:References:In-Reply-To; b=ChiFJQf8xwRKM8Z8y/9Oh0cTDB/dAEkOLd6yjm/pcm5Uf2/MTWoEA0WNLP0FdOwmp eDVSwFT9iqHI0lITnUwvNR6xSZL28OYAOHHuXrrkzEZPxXlPtSfmK5yI5USgk/mPhx /xPlQtIzI4SKEAt9jhitNikghA1D36c4kpFOAc1I=
Message-ID: <5201610A.7030109@dougbarton.us>
Date: Tue, 06 Aug 2013 13:48:10 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
References: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk> <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca>
In-Reply-To: <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 20:48:15 -0000

On 08/06/2013 12:58 PM, Joe Abley wrote:
> For what it's worth (not much) I would miss the line at the mic. There are useful conversations that happen within the line that I think we would lose if the mic followed the speaker

If the conversations are useful, should they not be happening as part of 
the meeting?

From mcr@sandelman.ca  Tue Aug  6 14:03:58 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A303C21F9EF5; Tue,  6 Aug 2013 14:03:56 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9FiJRsf2wOrs; Tue,  6 Aug 2013 14:03:41 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 4387F21F9E9E; Tue,  6 Aug 2013 14:03:40 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6FAD32016F; Tue,  6 Aug 2013 18:09:58 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 99C9863A88; Tue,  6 Aug 2013 17:02:03 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8A77963732; Tue,  6 Aug 2013 17:02:03 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian Rosen <br@brianrosen.net>
Subject: Re: RPS Accessibility
In-Reply-To: <CAOPrzE0pMop6NBR1kO_UW269UNibuMQ6dbx5sh5bZkvefYwvzw@mail.gmail.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <5328.1375810283@sandelman.ca> <CAOPrzE0pMop6NBR1kO_UW269UNibuMQ6dbx5sh5bZkvefYwvzw@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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: Tue, 06 Aug 2013 17:02:03 -0400
Message-ID: <4718.1375822923@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "iaoc-rps@ietf.org" <iaoc-rps@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, 06 Aug 2013 21:03:58 -0000

Brian Rosen <br@brianrosen.net> wrote:
    > Could be an app that put you in the queue and used your laptop/tablet/
    > smartphone microphone to get the audio.

I was thinking that too, but I didn't want to get ahead of the problem
statement of "mic access" :-)


From moore@network-heretics.com  Tue Aug  6 14:15:12 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 515FB21F9962 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PC64aOsovBUh for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:15:07 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id C7EB421F997B for <ietf@ietf.org>; Tue,  6 Aug 2013 14:15:06 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CAC6F2129F for <ietf@ietf.org>; Tue,  6 Aug 2013 17:15:04 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 06 Aug 2013 17:15:04 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=JH84lbi2NBI4lNn1z3qRj3 LCrQk=; b=GzYNgT9+YB1WeRaupq+4KYpBG0cZqBCA8GVXkoedd6keGUM2MQ+hhY 0FzdNPgGK6wQqCTzWH+QaFZZx86RnBfoPO8frQ2B9OEFLKwmxzS4jtmebRDmrzJ5 vSsApf9xru9k8ms3wtvJMAgqKY68fTJrgKhSneuXwric+eSyDX6I8=
X-Sasl-enc: Z1L3xv3/tgIxJn++oLwneD+qgY8F5jAD3zNb+wopmVPs 1375823704
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 3DDA36800A5; Tue,  6 Aug 2013 17:15:04 -0400 (EDT)
Message-ID: <52016755.5050409@network-heretics.com>
Date: Tue, 06 Aug 2013 17:15:01 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
References: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk> <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca> <520156A9.3090802@gmail.com>
In-Reply-To: <520156A9.3090802@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 21:15:12 -0000

On 08/06/2013 04:03 PM, Melinda Shore wrote:
> On 8/6/13 11:58 AM, Joe Abley wrote:
>> For what it's worth (not much) I would miss the line at the mic.
>> There are useful conversations that happen within the line that I
>> think we would lose if the mic followed the speaker, and I also think
>> that pipelining the people at the mic promotes more fluid
>> conversation. But these are minor points, and I'm mainly just waxing
>> nostalgic.
> I actually think that this is not a small point.  The people in
> line are the people with issues and the ability to hash stuff out
> quickly is pretty nice.
This only works if the queue is fairly short.  When the queue gets 
longer, and the microphones are in fixed positions, it's not unusual for 
the topic to jump around from one speaker to the next - and then each 
speaker has to re-establish what context he's talking about. It's very 
hard to get convergence under those conditions.

I'd actually like to see the microphone queue discipline replaced with 
something that could handle more than two currently active speakers.   
Multiple wireless microphones would probably work well enough, if we 
could change the room setup to make access to those microphones fairer.

(though it could still be challenging to incorporate remote speakers 
into the mix)

Keith


From dougb@dougbarton.us  Tue Aug  6 14:15:52 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E321521F9E5E for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:15:52 -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 z04bZr3AzSIH for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:15:52 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id A32D521F9E9E for <ietf@ietf.org>; Tue,  6 Aug 2013 14:15:34 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:538:c54:26c8:7f50] (unknown [IPv6:2001:470:d:5e7:538:c54:26c8:7f50]) by dougbarton.us (Postfix) with ESMTPSA id 4E3E222B1A for <ietf@ietf.org>; Tue,  6 Aug 2013 21:15:34 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1375823734; bh=rBNRqwVXbtwwgTD1fu70sGc4KfNIEHrbIqMuEwgwt8Q=; h=Date:From:To:Subject:References:In-Reply-To; b=JJv2+uJCbE8kHjomIM2x/IFq4pH4CyM7yyu7ANqwbO4NnOX+AphqaVu/icqKQYmQm /aZVsIdLSyhcRqI8qmQVX05QI35UIjX4vTJJ+E3QKgJlTBCdJ00MKCVlSoQpkqDo74 wEpJbaQbCFS8iGTLh2xU5KcrxR37caYN9L8fFDCk=
Message-ID: <52016776.9090100@dougbarton.us>
Date: Tue, 06 Aug 2013 14:15:34 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re:  RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com> <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com> <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com> <520160E5.6090506@dougbarton.us>
In-Reply-To: <520160E5.6090506@dougbarton.us>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 21:15:53 -0000

On 08/06/2013 01:47 PM, Doug Barton wrote:
> On 08/06/2013 01:46 PM, Ted Lemon wrote:
>> On Aug 6, 2013, at 4:37 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com>
>> wrote:
>>> If the problem is "we don't know who's speaking", then fix that
>>> problem.  In WGs I go to, both the WG chairs and the jabber scribes
>>> regularly yell "NAME!" if someone forgets to say it.  Unlike DNS Ops,
>>> this isn't rocket science.
>>
>> This doesn't work very well.   In one meeting where I was scribing
>> this IETF, I had to shout NAME at the same person several times,
>> because he didn't state his name clearly enough for me to be sure I'd
>> gotten it, and so it didn't stick.   I hate doing this—I think it's
>> disruptive, and nobody likes getting yelled at.   I certainly don't
>> like _having_ to yell.
>
> Then come up with an alternate proposal. Fixing this problem is
> non-optional.

Apologies if this came off as too terse, or even worse, insulting to 
Ted. I had a longer response in the works then decided to not go too far 
into the weeds, and may have trimmed a bit too much.

What I've seen in other groups that has worked is a volunteer to record 
the names of speakers *before* they get to the mic, and then each 
speaker is announced. Of course that's one more volunteer to find, but 
it's pretty light duty, and I suspect that some in our crowd would like 
to have the extra mic time. :)

In any case, we must fix these problems. All arguments of the form "But 
it's hard ..." are out of scope.

Perhaps what is necessary is a solution-focused group to hash out the 
problem space and come up with workable ideas? I would gladly 
participate in such a group.

Doug


From mrex@sap.com  Tue Aug  6 14:36:25 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA5A21F9D5E for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K61SxqOhvwMi for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:36:20 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 410B521F84CD for <ietf@ietf.org>; Tue,  6 Aug 2013 14:36:20 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r76LaDkP020045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Aug 2013 23:36:13 +0200 (MEST)
Subject: Re: [iaoc-rps] RPS Accessibility
In-Reply-To: <520160E5.6090506@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Date: Tue, 6 Aug 2013 23:36:13 +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: <20130806213613.C1C221A8EC@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, 06 Aug 2013 21:36:25 -0000

Doug Barton wrote:
> Ted Lemon wrote:
>>
>> M, Hadriel Kaplan <hadriel.kaplan@oracle.com> wrote:
>>> If the problem is "we don't know who's speaking", then fix that problem.
>>
>> This doesn't work very well. [...] nobody likes getting yelled at.
>> I certainly don't like _having_ to yell.
> 
> Then come up with an alternate proposal.
> Fixing this problem is non-optional.


I would neither want to yell at other, nor enjoy being yelled at.
Still I might need a reminder.  How about a visual cues that would/should
work for most participants in a f2f meeting?

Supply the chairs (~8 rooms?) with signs at least A4 size, or A3
maybe even using all caps and something like:

      TELL US YOUR NAME,
           PLEASE
      (and affiliation)

The chair could raise the sign towards persons at the mic when they forget,
slowly moving it up in the air and over the head (and ultimately waving it...)
until the message has been received.


Maybe attaching such a sign to the MIC from the start could
additionally improve the situation.

-Martin

From petithug@acm.org  Tue Aug  6 14:40:47 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758D021E809A for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:40:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.012,  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 U6ypiF6uLrat for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 14:40:46 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 9832A21F9FE9 for <ietf@ietf.org>; Tue,  6 Aug 2013 14:40:46 -0700 (PDT)
Received: from [IPv6:2601:9:4bc0:25:9091:36cc:203a:90b2] (unknown [IPv6:2601:9:4bc0:25:9091:36cc:203a:90b2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 6DA8C20EF8 for <ietf@ietf.org>; Tue,  6 Aug 2013 23:40:44 +0200 (CEST)
Message-ID: <52016D5A.809@acm.org>
Date: Tue, 06 Aug 2013 14:40:42 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Microphone protocol
X-Enigmail-Version: 1.5.1
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, 06 Aug 2013 21:40:47 -0000

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

As I was watching the conversations in the microphone lines during some of the
WG sessions, I thought that we could make a small improvement in the
organization that could result in a better meeting.  My first observation was
that there is two different type of interactions at the microphones:  The
first one is between a participant and the presenter or the chairs.  The
second one is participants responding to the first participant, e.g:

1. The presenter proposes some alternatives.

2. Someone at the mic explains her preferences

3. Someone else explains to (2) why she is wrong

Generally this triggers a back and forth between (2) and (3) which very often
is not fully captured by one of the microphones, because people start talking
to each other directly.

My second observation was that there is generally 2 microphones, or a multiple
of two microphones in each meeting room.

So the idea would be to dedicate one microphone for the primary interactions
(2) and a different microphone for the secondary interactions (3).  We could
have the microphone farther from the presenter being the primary microphone
and oriented toward the presenter.  People line up behind it to interact with
the presenter/chairs.

The second microphone (which is between the presenter and the primary
microphone) is oriented in the opposite direction, i.e. in direction of the
primary microphone.  People line up behind it to respond to the participant at
the primary microphone.

I see two potential advantages:

- - There is only one line to interact with the presenter, so the chairs do not
have to manage two lines.  The secondary microphone line stays empty if nobody
wants to respond to someone at the primary microphone. and empties each time a
new participant reaches the primary microphone.

- - Discussions are more natural because participants in a discussion face each
other (primary faces presenters, secondary faces primary).

With some quick explanations from the chairs at the beginning of a session,
the direction of each microphone could be all that is needed to find the role
of each microphone.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBCAAGBQJSAW1WAAoJECnERZXWan7Es/MQAOfGkIzQtCkLMbBRgOVoLUVw
sR99BcyQ87b/Gkzcn8JKJFCVt85CC/0GpJVhJ9IATnBkKesJTX4ctmT95/UhFF5U
UonOtkdVADq0d1rIHjVVAEwNanuyeyb7JgVUDT4is0gRi3CtkPwzl7hZ+brY3B+p
N3/BTCHm9M3iLOtr9SHYEcmogH4IePOlk1p1f4cH4+Gh0dxuSPs4xHthWTsq2pva
K2TAQzaORGxBXlaq9BVYiL7UbfnWXcIpVFoe0c9DT2q33XgWStHoTB6Uakt5XkBS
L1uSSQGSx0Yk5HXjwQoGo0oqPOnn16kCDYzBH4L3C1F7ZZwX3/LhfsiFNhHjTMDh
zR4kOS4DVDKqxaeKdlebGh1c+P5/W4GqlGAgLa7QxQfZu7gBAOs+MG+qw7iZNyU5
8lFi2wivgs292OlPwW1LHID5KwbtIW9dXYtNYlDs5KL1zczHmv1fLHbNcwmdAnA6
ablmVfO3nwnfkZrLExebKBMkEggazipgP4qyDzEhY9zb9RD0sBjmmZyfTUG30GEV
z/K79pB7HjdQxyOiksmeq5pVfCfFN/oZmqlnhhStla/QaYQ/67gnopdhX30sEiMm
25XcHBZCkaG5itPWeI8HjuXmqdd4PjhWEenvWN+Ryn3FNAxzZS7D+o3L7Z7lkag1
7pmiTveYpqL5lOpczirq
=Ds9N
-----END PGP SIGNATURE-----

From uyeshiro@ifa.hawaii.edu  Tue Aug  6 14:45:58 2013
Return-Path: <uyeshiro@ifa.hawaii.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 0D9B021E80B6; Tue,  6 Aug 2013 14:45:58 -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 hFlnDnwCn4tE; Tue,  6 Aug 2013 14:45:52 -0700 (PDT)
Received: from hale.ifa.hawaii.edu (hale.ifa.hawaii.edu [128.171.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF7321F995B; Tue,  6 Aug 2013 14:45:52 -0700 (PDT)
Received: from XeonAL (xeonal [128.171.163.193]) by hale.ifa.hawaii.edu (8.13.8/8.13.8) with ESMTP id r76Ljc1d011048; Tue, 6 Aug 2013 11:45:44 -1000 (HST)
From: "Robin Uyeshiro" <uyeshiro@IfA.Hawaii.Edu>
To: "'Brian Rosen'" <br@brianrosen.net>, "'Michael Richardson'" <mcr+ietf@sandelman.ca>
Subject: RE: RPS Accessibility
Date: Tue, 6 Aug 2013 11:45:54 -1000
Message-ID: <AF632AC6FE034A82AB9929DE28A9715B@XeonAL>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0099_01CE929A.8A570260"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6863
In-Reply-To: <CAOPrzE0pMop6NBR1kO_UW269UNibuMQ6dbx5sh5bZkvefYwvzw@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Thread-Index: Ac6S0vfjkZ8QC0PbSMuPx1+zHYJMmAAGj7Jg
Importance: Normal
Cc: iaoc-rps@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 21:45:58 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0099_01CE929A.8A570260
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I would think any kind of multiple non-fixed microphone setup (maybe =
even
fixed microphones) would need to be tested pretty thoroughly before use, =
as
feedback problems can ruin a discussion.  That would include laptop
microphones.  One way to alleviate this would be to require the use of
near-field microphones, mics that only pick up sounds generated close to =
the
mic. They are pretty cheap. =20
=20
Of course, this wouldn't apply to remote participants :)

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Brian Rosen
Sent: Tuesday, August 06, 2013 8:30 AM
To: Michael Richardson
Cc: iaoc-rps@ietf.org; ietf@ietf.org
Subject: Re: RPS Accessibility


Could be an app that put you in the queue and used your
laptop/tablet/smartphone microphone to get the audio.

On Tuesday, August 6, 2013, Michael Richardson wrote:



Dave Crocker <dhc@dcrocker.net <javascript:;> > wrote:
    > An entirely different approach would be to have all speakers make =
a
    > 'reservation' into a single meetecho (or whatever) online queue, =
and
then get
    > called in order, whether local or remote and independent of what
microphone
    > they are at.  This gets accurate identification into the online
system, with
    > the entry task distributed.

+1.
And move the microphones to the people, rather than the other way =
around.

We can easily have three or four microphones that can play leap-frog =
around
the room.

--
Michael Richardson <mcr+IETF@sandelman.ca <javascript:;> >, Sandelman
Software Works





------=_NextPart_000_0099_01CE929A.8A570260
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.23507"></HEAD>
<BODY>
<DIV><SPAN class=3D296563721-06082013><FONT color=3D#0000ff size=3D2 =
face=3DArial>I=20
would think any kind of multiple non-fixed microphone setup (maybe even =
fixed=20
microphones) would need to be tested pretty thoroughly before use, as =
feedback=20
problems can ruin a discussion.&nbsp; That would include laptop=20
microphones.&nbsp; One way to alleviate this would be to require the use =
of=20
near-field microphones, mics that only pick up sounds generated close to =
the=20
mic. They are pretty cheap.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=3D296563721-06082013><FONT color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D296563721-06082013><FONT color=3D#0000ff size=3D2 =
face=3DArial>Of=20
course, this wouldn't apply to remote participants =
:)</FONT></SPAN></DIV>
<BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px" dir=3Dltr>
  <DIV></DIV>
  <DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader =
align=3Dleft><FONT size=3D2=20
  face=3DTahoma>-----Original Message-----<BR><B>From:</B> =
ietf-bounces@ietf.org=20
  [mailto:ietf-bounces@ietf.org] <B>On Behalf Of </B>Brian =
Rosen<BR><B>Sent:</B>=20
  Tuesday, August 06, 2013 8:30 AM<BR><B>To:</B> Michael=20
  Richardson<BR><B>Cc:</B> iaoc-rps@ietf.org; =
ietf@ietf.org<BR><B>Subject:</B>=20
  Re: RPS Accessibility<BR><BR></FONT></DIV>Could be an app that put you =
in the=20
  queue and used your laptop/tablet/smartphone microphone to get the=20
  audio.<SPAN></SPAN><BR><BR>On Tuesday, August 6, 2013, Michael =
Richardson=20
  wrote:<BR>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; =
PADDING-LEFT: 1ex"=20
  class=3Dgmail_quote><BR>Dave Crocker &lt;<A=20
    onclick=3D"_e(event, 'cvml', 'dhc@dcrocker.net')"=20
    href=3D"javascript:;">dhc@dcrocker.net</A>&gt; wrote:<BR>&nbsp; =
&nbsp; &gt; An=20
    entirely different approach would be to have all speakers make =
a<BR>&nbsp;=20
    &nbsp; &gt; 'reservation' into a single meetecho (or whatever) =
online queue,=20
    and then get<BR>&nbsp; &nbsp; &gt; called in order, whether local or =
remote=20
    and independent of what microphone<BR>&nbsp; &nbsp; &gt; they are =
at.=20
    &nbsp;This gets accurate identification into the online system,=20
    with<BR>&nbsp; &nbsp; &gt; the entry task =
distributed.<BR><BR>+1.<BR>And=20
    move the microphones to the people, rather than the other way=20
    around.<BR><BR>We can easily have three or four microphones that can =
play=20
    leap-frog around<BR>the room.<BR><BR>--<BR>Michael Richardson &lt;<A =

    onclick=3D"_e(event, 'cvml', 'mcr+IETF@sandelman.ca')"=20
    href=3D"javascript:;">mcr+IETF@sandelman.ca</A>&gt;, Sandelman =
Software=20
    Works<BR><BR><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0099_01CE929A.8A570260--


From hadriel.kaplan@oracle.com  Tue Aug  6 15:15:28 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BA421F9EB0; Tue,  6 Aug 2013 15:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,  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 Nj9q3vn2wFOa; Tue,  6 Aug 2013 15:15:22 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBAD21F99BB; Tue,  6 Aug 2013 15:15:22 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r76MFKit014292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 6 Aug 2013 22:15:21 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r76MFJYL014940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 22:15:20 GMT
Received: from abhmt104.oracle.com (abhmt104.oracle.com [141.146.116.56]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r76MFJHV004462; Tue, 6 Aug 2013 22:15:19 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 06 Aug 2013 15:15:19 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [iaoc-rps] RPS Accessibility
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com>
Date: Tue, 6 Aug 2013 18:15:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B73EA80D-0145-497E-BCA5-5BCA64966D60@oracle.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com> <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com> <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: "<iaoc-rps@ietf.org>" <iaoc-rps@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 22:15:28 -0000

On Aug 6, 2013, at 4:46 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 6, 2013, at 4:37 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com> =
wrote:
>> If the problem is "we don't know who's speaking", then fix that =
problem.  In WGs I go to, both the WG chairs and the jabber scribes =
regularly yell "NAME!" if someone forgets to say it.  Unlike DNS Ops, =
this isn't rocket science.
>=20
> This doesn't work very well.   In one meeting where I was scribing =
this IETF, I had to shout NAME at the same person several times, because =
he didn't state his name clearly enough for me to be sure I'd gotten it, =
and so it didn't stick.   I hate doing this=97I think it's disruptive, =
and nobody likes getting yelled at.   I certainly don't like _having_ to =
yell.

Yeah, the best scenario (other than the person just remembering to say =
their name), is for the Chairs to remind them - because they have their =
own microphones so they don't have to actually yell.

But another thing that works well is to have the jabber scribe sit in a =
seat right next to the microphone, because then they don't have to yell =
either.

-hadriel


From mrex@sap.com  Tue Aug  6 15:52:37 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABDF621F8C9D for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 15:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F14yM8AV+0Cm for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 15:52:32 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id CA45621F9D38 for <ietf@ietf.org>; Tue,  6 Aug 2013 15:52:31 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r76MqSIH002969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Aug 2013 00:52:28 +0200 (MEST)
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <CAK=bVC-AvD95h5ucWcVXFxQSeJBveUJNBaqjb8xBHdDvnqh2rg@mail.gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Date: Wed, 7 Aug 2013 00:52:28 +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: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 22:52:37 -0000

Ulrich Herberg wrote:
> 
> I think that the heat was exceptional. I have grown up in Munich, and
> I have rarely ever seen it that hot (either in Munich or Berlin).
> Maybe it's global warming? ;-)

Damn coincidences!

IETF 39 was in Munich (August 1997)  Arabella&Sheraton @ Arabella Park,
and it was HOT pretty much the whole week.

-Martin

From andy@yumaworks.com  Tue Aug  6 16:29:13 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BBDE21F9C4E for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level: 
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.443,  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 Be5W4U1PgPhU for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:29:08 -0700 (PDT)
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by ietfa.amsl.com (Postfix) with ESMTP id E0DC521F9C6A for <ietf@ietf.org>; Tue,  6 Aug 2013 16:29:06 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so1110307pbc.35 for <ietf@ietf.org>; Tue, 06 Aug 2013 16:29:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mtpxBnI9U9B1H3YNjmUR5HBxp9qgS6OyjCM+fNfus4g=; b=j5GRfZNlMLTGfBWxghvgPfqe7s1uPEIUEygtl3IQqbxi08ljci/cZo0LLhvsDZlNOK jBt2mWBCpz0/7XLX/DSfgprytbdCvOV0P3jxuX3oPDT5HauRD4LJoKcVyOT2aMciYppN oiKpnLl5nnMEHUqk+6R4yt7MjjtKZmBYR+oVhQGVIVC3BJrLr/jm22xsDLbmVHcF5YKl TB6R0XVo9qJo43dRJSx44OPyE77N2ctMKh8eYPy/DZHkH2Rdrj7JnWER/C20HJKNu2cb EvegTw5/7IwcALglx8hpB/3Rdv3JcRczcrkbQd1uge3Z/li4ZykSFo704mAd+yCEVWrp vY4g==
X-Gm-Message-State: ALoCoQlWoIr7P+tKQCQheLKQ/mYvr4mBXB76aKZfw88f/T3WhNWXGxxVZIn7wf2HpCQp2/jtFXtT
MIME-Version: 1.0
X-Received: by 10.68.60.132 with SMTP id h4mr443030pbr.177.1375831744418; Tue, 06 Aug 2013 16:29:04 -0700 (PDT)
Received: by 10.70.12.161 with HTTP; Tue, 6 Aug 2013 16:29:04 -0700 (PDT)
In-Reply-To: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp>
References: <CAK=bVC-AvD95h5ucWcVXFxQSeJBveUJNBaqjb8xBHdDvnqh2rg@mail.gmail.com> <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp>
Date: Tue, 6 Aug 2013 16:29:04 -0700
Message-ID: <CABCOCHQjrong7C-O+Uai5_-hRxeGLk1BrpEP_mQSCBABO9meiQ@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Andy Bierman <andy@yumaworks.com>
To: mrex@sap.com
Content-Type: text/plain; charset=ISO-8859-1
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: Tue, 06 Aug 2013 23:29:13 -0000

On Tue, Aug 6, 2013 at 3:52 PM, Martin Rex <mrex@sap.com> wrote:
> Ulrich Herberg wrote:
>>
>> I think that the heat was exceptional. I have grown up in Munich, and
>> I have rarely ever seen it that hot (either in Munich or Berlin).
>> Maybe it's global warming? ;-)
>
> Damn coincidences!
>
> IETF 39 was in Munich (August 1997)  Arabella&Sheraton @ Arabella Park,
> and it was HOT pretty much the whole week.
>

Yes -- they said the same thing last time -- no need for ventilation since
it never gets too hot here.  I noticed the locals on the 200 bus to
the beer festival were just as miserable as me.
I stopped in a McDonalds for a diet coke, but the ice machine was broken.
(I was told it was too hot for it to make ice. Since I was the only American
in there, nobody noticed the ice machine didn't work but me ;-)

I would still come back -- this was a great city for an IETF -- I just hope
for once we get normal weather for July.


> -Martin

Andy

From john-ietf@jck.com  Tue Aug  6 16:36:55 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF44D21E80B5 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.644
X-Spam-Level: 
X-Spam-Status: No, score=-102.644 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BF869SSfDuSC for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:36:42 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id ABFC521E80AD for <ietf@ietf.org>; Tue,  6 Aug 2013 16:36: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 1V6qnv-0009y6-Rl; Tue, 06 Aug 2013 19:36:39 -0400
Date: Tue, 06 Aug 2013 19:36:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: mrex@sap.com
Subject: Re: Berlin was awesome, let's come again
Message-ID: <AEE62174BA499F0161E8E9FA@JcK-HP8200.jck.com>
In-Reply-To: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp>
References: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 23:36:56 -0000

--On Wednesday, August 07, 2013 00:52 +0200 Martin Rex
<mrex@sap.com> wrote:

>...
> IETF 39 was in Munich (August 1997)  Arabella&Sheraton @
> Arabella Park, and it was HOT pretty much the whole week.

If I recall, another very successful meeting in a place we
should go back to.  

Now, if only the IAOC could work out a better weather contract
for both Europe and, perhaps, a required March thaw in
Minneapolis.

   john




From moore@network-heretics.com  Tue Aug  6 16:48:33 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF7621E80BF for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:48:33 -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 tMDUfpNG1j2D for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:48:28 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD9121F9A96 for <ietf@ietf.org>; Tue,  6 Aug 2013 16:48:28 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2607D210A1 for <ietf@ietf.org>; Tue,  6 Aug 2013 19:48:16 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Tue, 06 Aug 2013 19:48:20 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=KHb7QJEIO2Uq+Et8vACT7b aDFqI=; b=KjH+3JSvcoTlEN8UJLv7KM/qnpPnDlNYCKT7/M+PfW9mDmyO6/7Tnp e97KPZ6T5cgiVjmMAxm/9m7u4mlT8ZC4XR+vPPjGcaFGi/w2O9LkEryZ10dlEh0n BDkDHRRPj6ERdO5HnXAn763zg+Wfw/IPkaUESaq30tnfIxaYjWd9Y=
X-Sasl-enc: jJ/fVCsUKk8OPoBf2V00MhloekbalPjgKArtDHmH2QG4 1375832893
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id A6F2AC00E8B; Tue,  6 Aug 2013 19:48:13 -0400 (EDT)
Message-ID: <52018B3A.1080803@network-heretics.com>
Date: Tue, 06 Aug 2013 19:48:10 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
References: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp> <AEE62174BA499F0161E8E9FA@JcK-HP8200.jck.com>
In-Reply-To: <AEE62174BA499F0161E8E9FA@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Aug 2013 23:48:33 -0000

On 08/06/2013 07:36 PM, John C Klensin wrote:
>> ...
>> IETF 39 was in Munich (August 1997)  Arabella&Sheraton @
>> Arabella Park, and it was HOT pretty much the whole week.
> If I recall, another very successful meeting in a place we
> should go back to.

I liked Munich as a destination.   But the hotel / meeting facility in 
Berlin far surpassed the Sheraton in Munich in every way imaginable.

Keith


From doug.mtview@gmail.com  Tue Aug  6 16:59:21 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21CD521E80C5 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:59:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-2.700, 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 uCMlo4tyjyW4 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 16:59:20 -0700 (PDT)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id B1E6021E80BF for <ietf@ietf.org>; Tue,  6 Aug 2013 16:59:20 -0700 (PDT)
Received: by mail-pa0-f43.google.com with SMTP id hz10so1415769pad.30 for <ietf@ietf.org>; Tue, 06 Aug 2013 16:59:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DXlHX1Wdre+ybAE1bvV1xJ6ag9qz/Avswe5GV0HxQDA=; b=rKdb6gCmQM83IJztCMcM/f958Pr5TBR7AZbabR93sSmK7tjMJTQbDUMm1vyotYyXmz TeUzUeuqSeQ51XK1VlzBRcGJCwL9ns8KDz8SxE3ha2KJ/s1m3vhHLwH/GGOgCt1j2v3y AMZ7HmcPrK2AmKXuaX5CDqiXx1vup8aPFFTfmqTEOM5FN5vYMUYhLjVMniSyWaqVu0zs u2qCw4T53ZiEjT8fe66H6Ta2Tlpl9C+JheAPAB3VMbABSX763cxX4xdHm5Sn7WOPt8Jn u9m3H6sQsjka75PgIdMDqdA5Ni5leyAUXWAJYGnC1g+lxEfWFE6Js2i+EY5O97kvYgJF burw==
X-Received: by 10.67.22.67 with SMTP id hq3mr1308327pad.132.1375833559737; Tue, 06 Aug 2013 16:59:19 -0700 (PDT)
Received: from [192.168.2.241] (c-98-207-206-162.hsd1.ca.comcast.net. [98.207.206.162]) by mx.google.com with ESMTPSA id ll5sm6602421pab.19.2013.08.06.16.59.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Aug 2013 16:59:18 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Berlin was awesome, let's come again
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <52018B3A.1080803@network-heretics.com>
Date: Tue, 6 Aug 2013 16:59:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F753600-141A-423E-87EE-A5A333BC0472@gmail.com>
References: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp> <AEE62174BA499F0161E8E9FA@JcK-HP8200.jck.com> <52018B3A.1080803@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org 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, 06 Aug 2013 23:59:21 -0000

On Aug 6, 2013, at 4:48 PM, Keith Moore <moore@network-heretics.com> =
wrote:

> On 08/06/2013 07:36 PM, John C Klensin wrote:
>>> ...
>>> IETF 39 was in Munich (August 1997)  Arabella&Sheraton @
>>> Arabella Park, and it was HOT pretty much the whole week.
>> If I recall, another very successful meeting in a place we
>> should go back to.
>=20
> I liked Munich as a destination.   But the hotel / meeting facility in =
Berlin far surpassed the Sheraton in Munich in every way imaginable.

Dear Keith,

Agreed.  One minor downside was needing an additional flight.  It seems =
AB who handles about a third of the traffic rather than Lufthansa that =
handles about one fifth, was not the best choice where a 6 hour layover =
extended an hour on the tarmac in a hot plane.=20

Regards,
Douglas Otis=

From hgs@cs.columbia.edu  Tue Aug  6 17:42:11 2013
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C357A11E80F9; Tue,  6 Aug 2013 17:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9xehXmjYWLz; Tue,  6 Aug 2013 17:42:07 -0700 (PDT)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id 45FB911E80F2; Tue,  6 Aug 2013 17:42:06 -0700 (PDT)
Received: from [192.168.2.163] (bas2-toronto09-845512453.dsl.bell.ca [50.101.127.5]) (user=hgs10 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r770fsYP020179 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 6 Aug 2013 20:41:54 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [iaoc-rps] RPS Accessibility
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org>
Date: Tue, 6 Aug 2013 20:41:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B74728EF-C578-4E4B-8E62-7AD45870A679@cs.columbia.edu>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org>
To: Dan York <york@isoc.org>
X-Mailer: Apple Mail (2.1508)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Paul Aitken <paitken@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 00:42:11 -0000

Yes, a group from my lab did this, using short-range RFID. (The range =
was about 1-2 inches.) It required a bit of a setup which made it hard =
to replicate at scale, but it worked reasonably well.

Privacy concerns are an issue, but you'd have to be very close to the =
person to sense the card (and you can obviously leave it behind any time =
you'd want to) - it would be much more convenient to track people using =
BlueTooth or WiFi MAC addresses, if you'd be so inclined, or just use =
video cameras. Yes, you can use long-range directional antennas to =
increase your read range, but those would be rather hard to hide. As was =
mentioned, the hotel room cards use very much the same technology, and =
you can't really leave them behind when you leave the building.

Henning

On Aug 5, 2013, at 5:15 AM, Dan York <york@isoc.org> wrote:

> On the topic of badge-sensing at the mic, I seem to recall that we had =
this working at an IETF sometime back in the RAI working groups. It was =
maybe 4 or 5 years ago and I think it may have been some student(s) =
under Henning Schulzrinne at Columbia... but I am not sure about that.  =
I remember that when you went to the mic you put your badge up to this =
sensor and your name appeared in the jabber room. We used it in several =
of the RAI sessions at that IETF. Unfortunately I don't remember how =
well it worked or why it wasn't continued. There may be someone out =
there who can provide some insight. (And if it was Henning's students we =
can just drop him a note.)
>=20
> Dan
>=20
> --
> Dan York
> york@isoc.org
> +1-802-735-1624
> skype:danyork
> http://twitter.com/danyork
>=20
> On Aug 2, 2013, at 10:26 AM, "Paul Aitken" <paitken@cisco.com> wrote:
>=20
>> I've remotely participated in several IETFs.
>>=20
>> I find that the biggest problem with remote attendance is the lack of =
visual cues. I've come to realise just how important these are in a =
meeting.
>> -are people paying attention, are they interested / confused / =
distracted / bored?
>>=20
>> Also there's no way for local attendees (in the WG room) to know that =
remote attendees are "at the mic" and whose turn it is to speak.
>>=20
>> There's been some discussion on the "87attendees" mailer about badge =
sensing at the mic - whether QR codes, NFC, or RFID. This could help =
remote attendees too.
>>=20
>> eg, see what they did with NFC + mic here: =
http://www.5thbar.me/blog/2012/09/14/nfc-enabled-badges-at-the-5thbar-mobi=
le-marketing-forum/=20
>>=20
>> P.
>> _______________________________________________
>> iaoc-rps mailing list
>> iaoc-rps@ietf.org
>> https://www.ietf.org/mailman/listinfo/iaoc-rps
>=20


From johnl@iecc.com  Tue Aug  6 18:02:37 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D0D21F9D5F for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 18:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.461
X-Spam-Level: 
X-Spam-Status: No, score=-110.461 tagged_above=-999 required=5 tests=[AWL=0.738, 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 1tGsljXUzn+D for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 18:02:32 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7246521F9D5E for <ietf@ietf.org>; Tue,  6 Aug 2013 18:02:31 -0700 (PDT)
Received: (qmail 71729 invoked from network); 7 Aug 2013 01:02:30 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 Aug 2013 01:02:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52019ca6.xn--i8sz2z.k1308; i=johnl@user.iecc.com; bh=0kZSd4zvx8EfCcHMSu6QYNXxVsPybUwE9mf5woAwwmk=; b=qlLtynJH8F1ZsrIh3nAUEe+6dVcJkGotXTte7pcIhIrGVWKRtFqbwHlzXFfR5OuqO7QqjZrHkPh54ORtHB2WBDpBwRw/9+sGZBTh2nnUhoVCjGu02INIXyCIPPvGIFlTUcxQ49hgiYspOejNoZx6Rhy4VDxHso4Qm9BydtDnzSzYz5OM9K65/HWUjfwhen5AV9L7vyHu8WtEX49/19hymdpl1ine1RB1xK+O39qZhumE02dlxRPLOHt6Ia0gR4gA
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52019ca6.xn--i8sz2z.k1308; olt=johnl@user.iecc.com; bh=0kZSd4zvx8EfCcHMSu6QYNXxVsPybUwE9mf5woAwwmk=; b=NplFVd8hfe7slValJP4XiLtRHJ7Y43Rruw3dKNYeWosNDb0/3V3kdc8OjiuioLjO4pxdxyPbNjcFvO5di/CYWh9zz9cxnlYr9bynuyEysSBZ6WJHRJRgBeSw0BkYAbbc6Go5SH6u74FSrwEVQamcrMIgby7TlWtYkmGTC8FPb8HNfSfIyNOCthDcZaRxFWnykgaHc4/7fG2DD3BFWhUt2WJ2+jdfrUMtjUCX6RbE6d8B5QY6EpR4EbaKXYnpgMb5
Date: 7 Aug 2013 01:02:08 -0000
Message-ID: <20130807010208.38351.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
In-Reply-To: <1F753600-141A-423E-87EE-A5A333BC0472@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 01:02:37 -0000

>Agreed.  One minor downside was needing an additional flight.  It seems AB who
>handles about a third of the traffic rather than Lufthansa that handles about one
>fifth, was not the best choice where a 6 hour layover extended an hour on the tarmac
>in a hot plane. 

With any luck, the next time we meet in Germany, they'll have opened
the new and much larger Berlin Brandenburg airport which will enable
far more direct intercontinental flights.


From randy@psg.com  Tue Aug  6 21:22:48 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E6D21F9EE1; Tue,  6 Aug 2013 21:22:48 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c30+xKFlUwiL; Tue,  6 Aug 2013 21:22:43 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) by ietfa.amsl.com (Postfix) with ESMTP id EC9EE21F9ED8; Tue,  6 Aug 2013 21:22:42 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V6vGi-00052B-7D; Wed, 07 Aug 2013 04:22:40 +0000
Date: Wed, 07 Aug 2013 06:22:39 +0200
Message-ID: <m2li4ew2nk.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [iaoc-rps] RPS Accessibility
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.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: IAOC RPS <iaoc-rps@ietf.org>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 04:22:48 -0000

> Ironically, this IETF everyone who stayed at the Intercontinental was
> walking around with an RFID key in their pocket the whole meeting.
> How many of us put them in faraday cages?

one.  i made it a habit

> I thought the experiment in Hiroshima went well

count me in the privacy concerns camp

randy

From johnl@iecc.com  Tue Aug  6 21:33:22 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0BA421E8054 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 21:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.487
X-Spam-Level: 
X-Spam-Status: No, score=-110.487 tagged_above=-999 required=5 tests=[AWL=0.712, 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 w8mtoCkCg1dB for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 21:33:18 -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 77AC021E8050 for <ietf@ietf.org>; Tue,  6 Aug 2013 21:33:18 -0700 (PDT)
Received: (qmail 5346 invoked from network); 7 Aug 2013 04:33:17 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 Aug 2013 04:33:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5201ce0d.xn--btvx9d.k1308; i=johnl@user.iecc.com; bh=0Fq6FeFrhbBpZ42DZk89QK5XbpHZTYfITzOdY7hyRrw=; b=hwF57RBFxRw7IQPq20yg7qhdkSAsxWxZuxMTluAbsL8WXmLjMDSynMMGdXVIFowirPOWGW2Y7v7cRSVWWGWzN4gmM3wOpdP8vhIgpJsvV6syW/XZXmWuwxkB3mHXV4M/ry8kedYlv2Q0i7nLzcUOTFG6/C+hjXHG70wK5HgvvGKHpJn+PlO1PibtYKjRigGW6UIu8+SCi6zUHFmi6yV6YUUZ1AWFgUDf7u59gN5EZ8WN9+S1Gpj+IAPQdEzCYyYY
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5201ce0d.xn--btvx9d.k1308; olt=johnl@user.iecc.com; bh=0Fq6FeFrhbBpZ42DZk89QK5XbpHZTYfITzOdY7hyRrw=; b=qEQmdQZOYzRoJ0kAA4L0uEP1bHAIh+InjZLZUQfrvxWgOleQo2iA1lk3ggyRrbGXt/HLwia2XMEIWrzC5YcJ3oLZITfVZrMKc2LdgElLIdHrkOaoWA/LPFqx7X3Vk7xhwtL/4OpStLvr7vDHyQ+B/gW8Z8D998Rb3AdzkMBtw31aW1a1fk41vUtR9kbP+D8LjgVfbz6E/Gn9EoTlWuziTHNmpAWwhgKqqnIZxheXfXLrkBvp8rJBrx4mLM7dYzI2
Date: 7 Aug 2013 04:32:55 -0000
Message-ID: <20130807043255.39248.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
In-Reply-To: <m2li4ew2nk.wl%randy@psg.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 04:33:22 -0000

In article <m2li4ew2nk.wl%randy@psg.com> you write:
>> Ironically, this IETF everyone who stayed at the Intercontinental was
>> walking around with an RFID key in their pocket the whole meeting.
>> How many of us put them in faraday cages?
>
>one.  i made it a habit

Two.  I have a wallet with a built-in tinfoil hat.

http://www.idstronghold.com/RFID-Blocking-Secure-Wallet-Bi-Fold-10-Slots/productinfo/IDSH7005/


From framefritti@gmail.com  Tue Aug  6 23:26:26 2013
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 508BA21E8051 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 23:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_57=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRTFslyH-2xw for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 23:26:25 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id CD95C21E8050 for <ietf@ietf.org>; Tue,  6 Aug 2013 23:26:25 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so1491923pbb.13 for <ietf@ietf.org>; Tue, 06 Aug 2013 23:26:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=1jzbo4nbqBsHy9Hmoy/wlw6cSpS9yMBD5fwCp17uy9g=; b=CKZzbvC+a6fZAjJ1zYfHhDs+wzIP8T/dMOXucKvnU+bz52ihoHISaOxojnPHQb4L9R XalRa1yyQLkH6mwI6Q5pjl6nZnhOGltzoHTM5g7TEU7QC9bkG7WD6S57oh6ggLp9U6uu +qSgFDQLeR5zCKqTyZ3xunQxZJXj3rUkMFCGAMGjWLKJj0aHxND8GlrgVUijg3BISawh Nxe87njJwjaiY6WndQLyfUQ5daQO+eKbysrpJLF7VaUKDntSgJyR8RIrl5SiPBkQEBbT WU8OewL0hc471aA0c1M9twXZB38jruaNLnjz1ENg/B8Yqn3wFryyjj7L3w9mTIrdsIIF rgow==
MIME-Version: 1.0
X-Received: by 10.66.241.34 with SMTP id wf2mr2603161pac.111.1375856784516; Tue, 06 Aug 2013 23:26:24 -0700 (PDT)
Received: by 10.70.72.165 with HTTP; Tue, 6 Aug 2013 23:26:24 -0700 (PDT)
In-Reply-To: <B74728EF-C578-4E4B-8E62-7AD45870A679@cs.columbia.edu>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <B74728EF-C578-4E4B-8E62-7AD45870A679@cs.columbia.edu>
Date: Wed, 7 Aug 2013 08:26:24 +0200
Message-ID: <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@mail.gmail.com>
Subject: Re: [iaoc-rps] RPS Accessibility
From: Riccardo Bernardini <framefritti@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 06:26:26 -0000

Just thinking out aloud....

What about a web-cam (maybe a wireless one? Never tried to use
them...) right under the mic, so that it takes a picture of the badge
and shows it on the screen?  Everyone (right?) in a meeting has a
badge  wit his/her/its :) name and affiliation, so privacy concerns
are just comparable to those of wearing a badge.

Of course, this is not applicable to jabber participants, in that case
you need a different solution.

On Wed, Aug 7, 2013 at 2:41 AM, Henning Schulzrinne <hgs@cs.columbia.edu> w=
rote:
> Yes, a group from my lab did this, using short-range RFID. (The range was=
 about 1-2 inches.) It required a bit of a setup which made it hard to repl=
icate at scale, but it worked reasonably well.
>
> Privacy concerns are an issue, but you'd have to be very close to the per=
son to sense the card (and you can obviously leave it behind any time you'd=
 want to) - it would be much more convenient to track people using BlueToot=
h or WiFi MAC addresses, if you'd be so inclined, or just use video cameras=
. Yes, you can use long-range directional antennas to increase your read ra=
nge, but those would be rather hard to hide. As was mentioned, the hotel ro=
om cards use very much the same technology, and you can't really leave them=
 behind when you leave the building.
>
> Henning
>
> On Aug 5, 2013, at 5:15 AM, Dan York <york@isoc.org> wrote:
>
>> On the topic of badge-sensing at the mic, I seem to recall that we had t=
his working at an IETF sometime back in the RAI working groups. It was mayb=
e 4 or 5 years ago and I think it may have been some student(s) under Henni=
ng Schulzrinne at Columbia... but I am not sure about that.  I remember tha=
t when you went to the mic you put your badge up to this sensor and your na=
me appeared in the jabber room. We used it in several of the RAI sessions a=
t that IETF. Unfortunately I don't remember how well it worked or why it wa=
sn't continued. There may be someone out there who can provide some insight=
. (And if it was Henning's students we can just drop him a note.)
>>
>> Dan
>>
>> --
>> Dan York
>> york@isoc.org
>> +1-802-735-1624
>> skype:danyork
>> http://twitter.com/danyork
>>
>> On Aug 2, 2013, at 10:26 AM, "Paul Aitken" <paitken@cisco.com> wrote:
>>
>>> I've remotely participated in several IETFs.
>>>
>>> I find that the biggest problem with remote attendance is the lack of v=
isual cues. I've come to realise just how important these are in a meeting.
>>> -are people paying attention, are they interested / confused / distract=
ed / bored?
>>>
>>> Also there's no way for local attendees (in the WG room) to know that r=
emote attendees are "at the mic" and whose turn it is to speak.
>>>
>>> There's been some discussion on the "87attendees" mailer about badge se=
nsing at the mic - whether QR codes, NFC, or RFID. This could help remote a=
ttendees too.
>>>
>>> eg, see what they did with NFC + mic here: http://www.5thbar.me/blog/20=
12/09/14/nfc-enabled-badges-at-the-5thbar-mobile-marketing-forum/
>>>
>>> P.
>>> _______________________________________________
>>> iaoc-rps mailing list
>>> iaoc-rps@ietf.org
>>> https://www.ietf.org/mailman/listinfo/iaoc-rps
>>
>

From moore@network-heretics.com  Tue Aug  6 23:39:08 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFAC21E80E6 for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 23:39:08 -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 UYLA-qsXu-Vd for <ietf@ietfa.amsl.com>; Tue,  6 Aug 2013 23:38:55 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1378A11E8109 for <ietf@ietf.org>; Tue,  6 Aug 2013 23:38:54 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 162572095F for <ietf@ietf.org>; Wed,  7 Aug 2013 02:38:54 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 07 Aug 2013 02:38:54 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=aWfRNAuGh55oRD7UC5hBxH iQAqM=; b=rgfTJdNGyArDB2vB8cC+EBLjNe4p5HKdCX8kskoO8mEZ0d03szN6yL aUc7ggKBKF0ZaxJoFe0W4bQoQJzIH6MKM2XqAlVS8SHk2TVgGhmKdDGRmb9Bi+Fg RApWPKuxdf7lm0XjUk0YtSqpfdRVGL4Vep/UwAMiiQJnLZpJs5sIA=
X-Sasl-enc: KetuYxPq7i7jilIpinJv3JqvYJu2bHfKNj64EdhrT7QC 1375857533
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 7FD1C6800D8; Wed,  7 Aug 2013 02:38:53 -0400 (EDT)
Message-ID: <5201EB79.1060407@network-heretics.com>
Date: Wed, 07 Aug 2013 02:38:49 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [iaoc-rps] RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <B74728EF-C578-4E4B-8E62-7AD45870A679@cs.columbia.edu> <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@mail.gmail.com>
In-Reply-To: <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@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, 07 Aug 2013 06:39:08 -0000

On 08/07/2013 02:26 AM, Riccardo Bernardini wrote:
> Just thinking out aloud....
>
> What about a web-cam (maybe a wireless one? Never tried to use
> them...) right under the mic, so that it takes a picture of the badge
> and shows it on the screen?  Everyone (right?) in a meeting has a
> badge  wit his/her/its:)  name and affiliation, so privacy concerns
> are just comparable to those of wearing a badge.
Except that this would preclude use of portable/wireless microphones to 
let people engage in more effective conversation.

Even if there continues to be some sort of queue or other discipline to 
determine who speaks next, we need to get away from the habit of forcing 
people to walk through narrow rows of chairs and stand in a queue behind 
a fixed-location microphone in order to speak.

Keith


From barryleiba.mailing.lists@gmail.com  Wed Aug  7 01:03:56 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B301A11E80E6 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 01:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level: 
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yCzBqf3iAa4 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 01:03:56 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 2E77221E80DA for <ietf@ietf.org>; Wed,  7 Aug 2013 01:03:56 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id cy12so1440820veb.32 for <ietf@ietf.org>; Wed, 07 Aug 2013 01:03:55 -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:message-id:subject :from:to:cc:content-type; bh=4cgRLXQf2NozycwL1MmZVUrwopqVxiG8VqVSfedKimo=; b=QDjxnWOfzMdLmob/PRhi3Jl41mV8JtDg5H5czYs+9Ox0Tg4Ft4J4L1IhGYMCxlGM24 W3FJnWrJfzGgc1FOCJHCUMytyJbLG2OekdgcdfKNyimeaL+KTfq78M0iQotr4QATX344 VMNAEN5/5FCsnGUv8xVN9SN0CX9HhKiC2kykXBgIQOaKJAx4qhEOFGJQLZQ5PuXejYM9 Lkz0kyzKtrOvrf+QLF0KyJXhNwLtPKFVa7o7b0xjtZOJj9HBajFdm6RsbQTRsQeMX8mA 7c10+Mf2fNGLcLM5jIpZjghIdGsuKl1guqDP6ROfUAeoCGMbMPQj6LuKe0VNw9EOCSvg xq5Q==
MIME-Version: 1.0
X-Received: by 10.52.164.227 with SMTP id yt3mr502896vdb.107.1375862635606; Wed, 07 Aug 2013 01:03:55 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.137.227 with HTTP; Wed, 7 Aug 2013 01:03:55 -0700 (PDT)
In-Reply-To: <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com>
Date: Wed, 7 Aug 2013 10:03:55 +0200
X-Google-Sender-Auth: Bkb7HhvFtiEppJtbj0NYNTiq-yE
Message-ID: <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Joe Hildebrand <hildjj@cursive.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: Wed, 07 Aug 2013 08:03:56 -0000

A couple of procedural points here:

> The issue here is whether this proposal should be an IETF Proposed STANDARD.
...
> Usually when the IETF publishes an algorithm it is given INFORMATIONAL or
> EXPERIMENTAL status. That is what originally happened with JSON, RFC 4627
> has INFORMATIONAL status despite the fact that at the time it was written
> there was a lot of implementation.

First, Proposed Standard is just that: a proposal.  It does not
require implementations.  It requires that it be "generally stable,
has resolved known design choices, is believed to be well-understood,
has received significant community review, and appears to enjoy enough
community interest to be considered valuable."  That's from RFC 2026,
Section 4.1.1, which goes on to say, "Usually, neither implementation
nor operational experience is required for the designation of a
specification as a Proposed Standard."

I believe that CBOR qualifies, which is why I agreed to AD-sponsor it.
 In the process, I'm looking to see if we have rough consensus that
all this is the case.  Your substantive comments on the document, as
well as those of others, should address those points (as some of your
comments indeed do).

Second, RFC 4627 is Informational because it was not meant to be the
standard definition of JSON.  It was meant only to register the media
type.  But one thing led to another, and it did become the referenced
definition, which is why the JSON working group is working on fixing
its gaps and moving it to Standards Track.

> Using the individual submissions track as a way to circumvent working group
> process when there is an actual IETF JSON working group seems completely
> wrong to me.

No one is circumventing anything.  The JSON working group is not
chartered to deal with this or other documents like it, and we won't
be rechartering it to do so any time soon.  And remember that any time
I'm sponsoring a document as AD, part of what I'm doing is what
working group chairs do in a working group: judging rough consensus on
the document's content and the issues that concern whether it's
intended status is appropriate.  If you (and/or others) can show that
there are solid reasons that this should not be a Proposed Standard,
or if I do not see rough consensus to publish it, I will not bring it
to the rest of the IESG.

Barry, Applications AD

From cabo@tzi.org  Wed Aug  7 01:24:56 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A135721F8EC3 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 01:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.943
X-Spam-Level: 
X-Spam-Status: No, score=-105.943 tagged_above=-999 required=5 tests=[AWL=0.306, 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 zW5fJfZBEomo for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 01:24:49 -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 BABA521F8EB5 for <ietf@ietf.org>; Wed,  7 Aug 2013 01:24:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r778Of6u000453; Wed, 7 Aug 2013 10:24:41 +0200 (CEST)
Received: from [172.24.101.75] (unknown [193.104.215.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EF10F5BE; Wed,  7 Aug 2013 10:24:39 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CE26AA2D.13CCC%joe@cursive.net>
Date: Wed, 7 Aug 2013 10:24:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8D03BAC-2B26-4459-81EC-F7EE1B6DCCA1@tzi.org>
References: <CE26AA2D.13CCC%joe@cursive.net>
To: Joe Hildebrand <hildjj@cursive.net>
X-Mailer: Apple Mail (2.1508)
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: Wed, 07 Aug 2013 08:24:56 -0000

On Aug 6, 2013, at 21:45, Joe Hildebrand <hildjj@cursive.net> wrote:

> On 8/6/13 1:11 PM, "Carsten Bormann" <cabo@tzi.org> wrote:
>=20
>> If a CBOR application does require initial signature bytes for
>> self-description purposes, I would suggest using something like
>>=20
>> 	0xd8 0xf8 ...data item...
>>=20
>> which decodes as tag248(data item); we could define 248 as a no-op =
tag.
>=20
> Or a no-op simple value; we could easily pick one that did not =
generate a
> valid first character for JSON.

Well, simple values don't have "content".
Using one as a signature would mean the data item ends right on the =
simple value, and the actual payload would be a second data item.  I'd =
rather have a single data item that is just (ignorably) tagged.

Yes, picking a tag number that encodes into a file signature that can't =
be a valid start for JSON (or many other kinds of things, e.g. UTF-8 =
text) is easy, as demonstrated above.

Gr=FC=DFe, Carsten


From superuser@gmail.com  Wed Aug  7 01:28:31 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD8821E8097 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 01:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, 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 4nz36QYTwTEy for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 01:28:30 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 78EB611E80E6 for <ietf@ietf.org>; Wed,  7 Aug 2013 01:28:30 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id z12so1253775wgg.22 for <ietf@ietf.org>; Wed, 07 Aug 2013 01:28: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=Sxv/bm4Xuk/EJ54vWBKA/4eb7jc+A8vzJVfBzMpK2RM=; b=WW7HHABUQCv+BvZ5mKHY5U4UuvKItW0e2by3/jykGD2iPRQqo/vZlGOzrJ8QrBaPfG NH55Td02qIyfE2XiFnGR7iHk0xDGZqViWEZgZY84p/Hbx29OIEDh9EvIyu6lzPXllRYj ExnQsQEc5hDxIXuO0/evNH0p+AVqryI2+1dTcjxeodiAitfp5lzWL4kDSrz01dYELebv d3FQ2+2upmFCd/ojrlydKSYmtHw4pfJbjM8gxP4a5TGYN66BY4SoNreE16lFnbqysjAr a2VXMsUstHwyjgdgxVWUfG+TyCBUo29FEpATF86mO/QO+IPupi4GqvMgOZZ0DLdrFj4S chGQ==
MIME-Version: 1.0
X-Received: by 10.194.201.168 with SMTP id kb8mr1456473wjc.63.1375864109627; Wed, 07 Aug 2013 01:28:29 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Wed, 7 Aug 2013 01:28:29 -0700 (PDT)
In-Reply-To: <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com>
Date: Wed, 7 Aug 2013 01:28:29 -0700
Message-ID: <CAL0qLwb=QncDyjh_qqXm4AqzURBtxRNUgTSaSO6X8E9PchEF0A@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=047d7ba9730e83804d04e35753b4
Cc: Joe Hildebrand <hildjj@cursive.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: Wed, 07 Aug 2013 08:28:31 -0000

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

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

> > Using the individual submissions track as a way to circumvent working
> group
> > process when there is an actual IETF JSON working group seems completely
> > wrong to me.
>
> No one is circumventing anything.  The JSON working group is not
> chartered to deal with this or other documents like it, and we won't
> be rechartering it to do so any time soon.  And remember that any time
> I'm sponsoring a document as AD, part of what I'm doing is what
> working group chairs do in a working group: judging rough consensus on
> the document's content and the issues that concern whether it's
> intended status is appropriate.  If you (and/or others) can show that
> there are solid reasons that this should not be a Proposed Standard,
> or if I do not see rough consensus to publish it, I will not bring it
> to the rest of the IESG.
>
>
I would add that CBOR has already seen enough interest and feedback that I
believe it would pass a call for adoption in APPSAWG, and be processed
there onto the standards track.  That would make Barry's job quite a bit
easier, since it would then be our job to host the discussion and record
consensus in that context.  It would also get a shorter IETF Last Call.

Instead, it's going what is for all intents and purposes a tougher route.
I'm not suggesting we derail its progress to do it the other way, but it
does suggest to me that the route it's following is hardly a shortcut or
bypass of some kind.

-MSK

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

<div dir=3D"ltr">On Wed, Aug 7, 2013 at 1:03 AM, Barry Leiba <span dir=3D"l=
tr">&lt;<a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryl=
eiba@computer.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; Using the individual submissions track =
as a way to circumvent working group<br><div class=3D"im">
&gt; process when there is an actual IETF JSON working group seems complete=
ly<br>
&gt; wrong to me.<br>
<br>
</div>No one is circumventing anything. =A0The JSON working group is not<br=
>
chartered to deal with this or other documents like it, and we won&#39;t<br=
>
be rechartering it to do so any time soon. =A0And remember that any time<br=
>
I&#39;m sponsoring a document as AD, part of what I&#39;m doing is what<br>
working group chairs do in a working group: judging rough consensus on<br>
the document&#39;s content and the issues that concern whether it&#39;s<br>
intended status is appropriate. =A0If you (and/or others) can show that<br>
there are solid reasons that this should not be a Proposed Standard,<br>
or if I do not see rough consensus to publish it, I will not bring it<br>
to the rest of the IESG.<br>
<br></blockquote><div><br></div><div>I would add that CBOR has already seen=
 enough interest and feedback that I believe it would pass a call for adopt=
ion in APPSAWG, and be processed there onto the standards track.=A0 That wo=
uld make Barry&#39;s job quite a bit easier, since it would then be our job=
 to host the discussion and record consensus in that context.=A0 It would a=
lso get a shorter IETF Last Call.<br>
<br>Instead, it&#39;s going what is for all intents and purposes a tougher =
route.=A0 I&#39;m not suggesting we derail its progress to do it the other =
way, but it does suggest to me that the route it&#39;s following is hardly =
a shortcut or bypass of some kind.<br>
<br></div><div>-MSK<br></div></div></div></div>

--047d7ba9730e83804d04e35753b4--

From Ted.Lemon@nominum.com  Wed Aug  7 07:51:23 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9F0721E813C for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 07:51:23 -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 AmI8NWg1r69p for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 07:51:15 -0700 (PDT)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 73C8A21E811A for <ietf@ietf.org>; Wed,  7 Aug 2013 07:51:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKUgJe4k4lHy+DcY/6TVH7ERVADD+r2QRa@postini.com; Wed, 07 Aug 2013 07:51:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E74E81B8282 for <ietf@ietf.org>; Wed,  7 Aug 2013 07:51:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E149E190060; Wed,  7 Aug 2013 07:51:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 07:51:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: RPS Accessibility
Thread-Topic: RPS Accessibility
Thread-Index: AQHOk32MkUTB7bL7SU62aTcbJBAAqg==
Date: Wed, 7 Aug 2013 14:51:08 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775248D4B@mbx-01.win.nominum.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246930@mbx-01.win.nominum.com> <8721A396-DA60-4961-8B4F-D6D41ED94E62@oracle.com> <8D23D4052ABE7A4490E77B1A012B630775248121@mbx-01.win.nominum.com> <520160E5.6090506@dougbarton.us> <52016776.9090100@dougbarton.us>
In-Reply-To: <52016776.9090100@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <BE224E7CDA57FC4C96CF6067432ED77D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 14:51:23 -0000

On Aug 6, 2013, at 5:15 PM, Doug Barton <dougb@dougbarton.us> wrote:
> What I've seen in other groups that has worked is a volunteer to record t=
he names of speakers *before* they get to the mic, and then each speaker is=
 announced. Of course that's one more volunteer to find, but it's pretty li=
ght duty, and I suspect that some in our crowd would like to have the extra=
 mic time. :)

This is a bit low-tech, but would certainly work.


From Ted.Lemon@nominum.com  Wed Aug  7 07:52:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2D4011E8141 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 07:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.037, 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 YbPf1ITT2iD9 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 07:52:42 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 4994A11E813F for <ietf@ietf.org>; Wed,  7 Aug 2013 07:52:41 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUgJfOVUvKGTG8UXO5I/Dbbff5LUePrOC@postini.com; Wed, 07 Aug 2013 07:52:41 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E85161B8288 for <ietf@ietf.org>; Wed,  7 Aug 2013 07:52:40 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id E1057190060; Wed,  7 Aug 2013 07:52:40 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 07:52:40 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<mrex@sap.com>" <mrex@sap.com>
Subject: Re: [iaoc-rps] RPS Accessibility
Thread-Topic: [iaoc-rps] RPS Accessibility
Thread-Index: AQHOkDNSS43GUutwDE+rfApQjh1upZmGzZ0AgAH6VoCAAD+cgIAAFtSAgAAChICAAABkgIAADZmAgAEhlQA=
Date: Wed, 7 Aug 2013 14:52:40 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775248D8D@mbx-01.win.nominum.com>
References: <20130806213613.C1C221A8EC@ld9781.wdf.sap.corp>
In-Reply-To: <20130806213613.C1C221A8EC@ld9781.wdf.sap.corp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9106EE7535405448BF28B0B8461763C5@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 14:52:48 -0000

On Aug 6, 2013, at 5:36 PM, Martin Rex <mrex@sap.com> wrote:
> Maybe attaching such a sign to the MIC from the start could
> additionally improve the situation.

There were signs like this attached to all the mics in all the rooms at thi=
s IETF.   I never looked at them, and I doubt anybody else did either.   Ce=
rtainly the evidence would suggest that they did not!   :}


From paitken@cisco.com  Tue Aug  6 13:06:01 2013
Return-Path: <paitken@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 73DF521F9EA3; Tue,  6 Aug 2013 13:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.521
X-Spam-Level: 
X-Spam-Status: No, score=-10.521 tagged_above=-999 required=5 tests=[AWL=0.078, 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 txAw4kBWiJDG; Tue,  6 Aug 2013 13:05:56 -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 51C8121F972C; Tue,  6 Aug 2013 13:05:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=278; q=dns/txt; s=iport; t=1375819555; x=1377029155; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=JrUHO2dsJzteqw2XcukCQiqUB1Ium1eb87FqgYiOoXc=; b=Nr+lbYSXV33zI1VUJPs0HETGj4weu+/cZiIrLwPJXAlnWoqHzJPFOLS7 0DJNeMAERIyFlAyTkwR2slBT/dIFLUwvDDsQUxe7ao/na9D0jPZVhiR7L ZzM7MbNmGAtrOiyWghMNOFIsOY8sEH46GW3RmWNjQp7n/+0cDkt9Iy1Lu U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYFABNWAVKQ/khN/2dsb2JhbABagwY2jFaydYEfFnSCJAEBAQQ4QAEQCxgJFg8JAwIBAgFFBg0BBwEBiAy3RpAaB4QOA5dhhiWLKYMY
X-IronPort-AV: E=Sophos;i="4.89,827,1367971200"; d="scan'208";a="158083022"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 06 Aug 2013 20:05:44 +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 r76K5fhA021804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 20:05:42 GMT
Received: from [10.61.80.46] (ams3-vpn-dhcp4143.cisco.com [10.61.80.46]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r76K5enx018367; Tue, 6 Aug 2013 21:05:40 +0100 (BST)
Message-ID: <52015714.9010104@cisco.com>
Date: Tue, 06 Aug 2013 21:05:40 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [iaoc-rps] RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775246905@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 07 Aug 2013 08:03:38 -0700
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, "<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: Tue, 06 Aug 2013 20:06:01 -0000

Ted Lemon wrote:
> Ironically, this IETF everyone who stayed at the Intercontinental was 
> walking around with an RFID key in their pocket the whole meeting.

Could there be a conflict if IETF badges also have RFID tags attached, 
eg we get "Room 1283" at the mic?

P.

From paitken@cisco.com  Tue Aug  6 13:14:10 2013
Return-Path: <paitken@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 E6F3121F9EE0; Tue,  6 Aug 2013 13:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.222
X-Spam-Level: 
X-Spam-Status: No, score=-10.222 tagged_above=-999 required=5 tests=[AWL=-0.224, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6, 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 j8L-q+VMa5L0; Tue,  6 Aug 2013 13:14:06 -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 C058321F9ED2; Tue,  6 Aug 2013 13:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2723; q=dns/txt; s=iport; t=1375820046; x=1377029646; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=xAexqLygHztRIKg7DA2hwkaR6bfwSogtZsDLGZbrjVg=; b=VXwvpATzhr/ZkIqQb5scpASyEt8cFx+DwLZI9gmRQ5kwiHFs3m/faKVC Nr++HSET/TC/pat86VOkaG1y+DMSqX+96NS13J017muC8/AV06vs8tfpE svv5G3l9ENnj28z9sL93hH2424OsBtypK3GPXlQ0P+nV+5e8QrvE70N8v w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAG9YAVKQ/khR/2dsb2JhbABagwY1AYk8tg+BHxZ0giQBAQEEeAEQCwQBAgcKCRYPCQMCAQIBRQYNAQcBAYgMDLc/kBoHCYQFA5dhgSqEe4spgxg
X-IronPort-AV: E=Sophos;i="4.89,827,1367971200"; d="scan'208,217";a="16872516"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 06 Aug 2013 20:14:04 +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 r76KE1JD026774 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Aug 2013 20:14:02 GMT
Received: from [10.61.80.46] (ams3-vpn-dhcp4143.cisco.com [10.61.80.46]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r76KDxeY018659; Tue, 6 Aug 2013 21:14:00 +0100 (BST)
Message-ID: <52015907.2020906@cisco.com>
Date: Tue, 06 Aug 2013 21:13:59 +0100
From: Paul Aitken <paitken@cisco.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: [iaoc-rps] RPS Accessibility
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <520115F3.6050908@dcrocker.net> <2D12B775-E093-493B-9B6A-679F8F78A30B@hopcount.ca>
In-Reply-To: <2D12B775-E093-493B-9B6A-679F8F78A30B@hopcount.ca>
Content-Type: multipart/alternative; boundary="------------080709050907060300030200"
X-Mailman-Approved-At: Wed, 07 Aug 2013 08:03:38 -0700
Cc: "iaoc-rps@ietf.org" <iaoc-rps@ietf.org>, Dan York <york@isoc.org>, 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: Tue, 06 Aug 2013 20:14:11 -0000

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

Joe Abley wrote:
> Or perhaps future IETFers.app releases could talk using bluetooth to a 
> transponder duct-taped to the mic stand and realise the same outcomes 
> (and if you don't like that, you can always touch "no" in the 
> appropriate place on your phone).

Instead of requiring additional hardware on the mic stand + duct tape:

    "Zoosh, a new technology developed by Sunnyvale startup Naratte
    <http://www.naratte.com/>, aims to deliver all the benefits of NFC
    (near-field communication) with any device that has a speaker and
    microphone. Instead of relying on NFC chips, Zoosh uses ultrasound
    to perform secure mobile transactions."

http://venturebeat.com/2011/06/19/narattes-zoosh-enables-nfc-with-just-a-speaker-and-microphone/

Obviously this requires everyone to carry an app-enabled device to the mic.

P.

--------------080709050907060300030200
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">Joe Abley wrote:<br>
    </div>
    <blockquote
      cite="mid:2D12B775-E093-493B-9B6A-679F8F78A30B@hopcount.ca"
      type="cite">
      Or perhaps future IETFers.app releases could talk using bluetooth
      to a transponder duct-taped to the mic stand and realise the same
      outcomes (and if you don't like that, you can always touch "no" in
      the appropriate place on your phone).</blockquote>
    <br>
    Instead of requiring additional hardware on the mic stand + duct
    tape:<br>
    <br>
    <blockquote>"Zoosh, a new technology developed by Sunnyvale startup
      <a href="http://www.naratte.com/" target="_blank">Naratte</a>,
      aims to deliver all the benefits of NFC (near-field communication)
      with any device that has a speaker and microphone. Instead of
      relying on NFC chips, Zoosh uses ultrasound to perform secure
      mobile transactions."<br>
      <br>
    </blockquote>
<a class="moz-txt-link-freetext" href="http://venturebeat.com/2011/06/19/narattes-zoosh-enables-nfc-with-just-a-speaker-and-microphone/">http://venturebeat.com/2011/06/19/narattes-zoosh-enables-nfc-with-just-a-speaker-and-microphone/</a><br>
    <br>
    Obviously this requires everyone to carry an app-enabled device to
    the mic.<br>
    <br>
    P.<br>
  </body>
</html>

--------------080709050907060300030200--

From Ted.Lemon@nominum.com  Wed Aug  7 08:10:58 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12C3D21F9DB4 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:10:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.037, 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 DLBFlMY9FDHa for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:10:51 -0700 (PDT)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id EB69E11E813D for <ietf@ietf.org>; Wed,  7 Aug 2013 08:10:24 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUgJjYPZuGmIKCMwBvSTgsNO3/dbwpj3D@postini.com; Wed, 07 Aug 2013 08:10:25 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9742E1B8282 for <ietf@ietf.org>; Wed,  7 Aug 2013 08:10:24 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8ED07190060; Wed,  7 Aug 2013 08:10:24 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 08:10:24 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: Berlin was awesome, let's come again
Thread-Topic: Berlin was awesome, let's come again
Thread-Index: AQHOj28oj49pml6dWkKR3T/uNQeRaZmEdNmAgAAM8wCABMPuAIAADFIAgAADPgCAAAMZgIAA/pIA
Date: Wed, 7 Aug 2013 15:10:24 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775248EBB@mbx-01.win.nominum.com>
References: <20130806225228.4F2771A8EC@ld9781.wdf.sap.corp> <AEE62174BA499F0161E8E9FA@JcK-HP8200.jck.com> <52018B3A.1080803@network-heretics.com> <1F753600-141A-423E-87EE-A5A333BC0472@gmail.com>
In-Reply-To: <1F753600-141A-423E-87EE-A5A333BC0472@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <15CD9FBA3A67BF46B59202A6BD1931DF@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org 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, 07 Aug 2013 15:10:59 -0000

On Aug 6, 2013, at 7:59 PM, Douglas Otis <doug.mtview@gmail.com> wrote:
> Agreed.  One minor downside was needing an additional flight.  It seems A=
B who handles about a third of the traffic rather than Lufthansa that handl=
es about one fifth, was not the best choice where a 6 hour layover extended=
 an hour on the tarmac in a hot plane.=20

I just took a train.   But yeah, Munich is clearly easier to fly to.   I wo=
uld personally love it if IETF did another Munich meeting, because I haven'=
t been there since I was seven, and I've always wanted to go back (I missed=
 the previous Munich meeting, much to my frustration).


From jnc@mercury.lcs.mit.edu  Wed Aug  7 08:13:58 2013
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 D29D121F9DB4 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level: 
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,  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 2FEt6RDtDUCb for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:13:48 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 0D02F21F9C68 for <ietf@ietf.org>; Wed,  7 Aug 2013 08:13:37 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 10FDE18C17E; Wed,  7 Aug 2013 11:13:34 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Berlin was awesome, let's come again
Message-Id: <20130807151334.10FDE18C17E@mercury.lcs.mit.edu>
Date: Wed,  7 Aug 2013 11:13:34 -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, 07 Aug 2013 15:13:58 -0000

    > From: Ted Lemon <Ted.Lemon@nominum.com>

    > I would personally love it if IETF did another Munich meeting, because
    > I haven't been there since I was seven, and I've always wanted to go back

"Many fine lunches and dinners". Some things never change...

	Noel

From Ted.Lemon@nominum.com  Wed Aug  7 08:16:33 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D818411E814D for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.037, 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 L52n70N8evP2 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:16:26 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 15A9F21E8137 for <ietf@ietf.org>; Wed,  7 Aug 2013 08:16:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUgJkvolkVSe4+3KtME5WSFtdyYzRYFf6@postini.com; Wed, 07 Aug 2013 08:16:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AC3401B8288 for <ietf@ietf.org>; Wed,  7 Aug 2013 08:16:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A68DB190060; Wed,  7 Aug 2013 08:16:14 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 08:16:08 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John Levine <johnl@taugh.com>
Subject: Faraday cages...
Thread-Topic: Faraday cages...
Thread-Index: AQHOk4EKqEf7p1HLpUWM3SrXFoUEgg==
Date: Wed, 7 Aug 2013 15:16:07 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com>
References: <20130807043255.39248.qmail@joyce.lan>
In-Reply-To: <20130807043255.39248.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22FEB473D6BD414185288241754BEFBC@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 15:16:33 -0000

Dare I ask how many IETFers also kept their cell phones in faraday cages fo=
r the duration of the conference?


From hadriel.kaplan@oracle.com  Wed Aug  7 08:19:03 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFF0811E814D for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:19:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.5
X-Spam-Level: 
X-Spam-Status: No, score=-6.5 tagged_above=-999 required=5 tests=[AWL=0.099, 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 IDnrEgaNpsV5 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 08:18:57 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 582C311E8142 for <ietf@ietf.org>; Wed,  7 Aug 2013 08:18:57 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r77FItTL028523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Aug 2013 15:18:55 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r77FIsqd011870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Aug 2013 15:18:54 GMT
Received: from abhmt108.oracle.com (abhmt108.oracle.com [141.146.116.60]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r77FIsHc000337; Wed, 7 Aug 2013 15:18:54 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 07 Aug 2013 08:18:54 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [iaoc-rps] RPS Accessibility
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@mail.gmail.com>
Date: Wed, 7 Aug 2013 11:18:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <888D2E68-8181-48F5-BD2A-5B9ED7084F90@oracle.com>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <B74728EF-C578-4E4B-8E62-7AD45870A679@cs.columbia.edu> <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@mail.gmail.com>
To: Riccardo Bernardini <framefritti@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
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, 07 Aug 2013 15:19:04 -0000

On Aug 7, 2013, at 2:26 AM, Riccardo Bernardini <framefritti@gmail.com> =
wrote:

> Just thinking out aloud....
>=20
> What about a web-cam (maybe a wireless one? Never tried to use
> them...) right under the mic, so that it takes a picture of the badge
> and shows it on the screen?  Everyone (right?) in a meeting has a
> badge  wit his/her/its :) name and affiliation, so privacy concerns
> are just comparable to those of wearing a badge.

Ummm... methinks female participants might find such a camera offensive.

-hadriel


From chelliot@gmail.com  Wed Aug  7 09:26:26 2013
Return-Path: <chelliot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F2C11E80E2 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 09:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.867
X-Spam-Level: 
X-Spam-Status: No, score=-1.867 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpRSEHwO7LIV for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 09:26:26 -0700 (PDT)
Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 1A68221F9C6E for <ietf@ietf.org>; Wed,  7 Aug 2013 09:26:21 -0700 (PDT)
Received: by mail-lb0-f174.google.com with SMTP id w20so830409lbh.33 for <ietf@ietf.org>; Wed, 07 Aug 2013 09:26:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=tStZtJeCZt9+9u7mF96TCmwB4NFGKDqGbMcmReWn3LI=; b=EBh3GSckjoIC2Q77Q7L2FV4BAJnN+vplrbmuh7KOxvBWtf4BAb6F9ngNqvRVlPEJXl FYvLGJwy3vZrY9w2a2dcg4RP5f9pWe66jglsxgjencCCN4wlE9JK5U3a6Ff72Ms1SwAA DpzxRiVgkcApo/0FHG9vTCLo3OXazPTpmNkSBbdqM07j3QePrHXcWrMDqu/DhOot6OOf TKciBDhRscBpJ/a0yyw7IbLAoqscyy8SKFDPH7DZ+vf9J9UJC7h+LZS+/eqxEpTPobeY 4GCLHrT9s1j1f6GQkeBdh0/axpCocFMFots43D3i2WnC6MrYkMWcwuE0N62vJptFi8gd R/bA==
X-Received: by 10.152.9.37 with SMTP id w5mr1808205laa.23.1375892780694; Wed, 07 Aug 2013 09:26:20 -0700 (PDT)
MIME-Version: 1.0
Sender: chelliot@gmail.com
Received: by 10.114.3.44 with HTTP; Wed, 7 Aug 2013 09:26:00 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com>
From: Chris Elliott <chelliot@pobox.com>
Date: Wed, 7 Aug 2013 12:26:00 -0400
X-Google-Sender-Auth: MwTWd-CLXOZj6eYJ6ENH5L05q20
Message-ID: <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com>
Subject: Re: Faraday cages...
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e014946f47141d604e35e0050
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: chelliot@pobox.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, 07 Aug 2013 16:26:26 -0000

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

My wallet supposedly has a RFID-blocking layer, but I've not actually
tested it. I think the only RFID-capable thing in my wallet is my US
passport.

I used my cell phone in Berlin extensively, both roaming and on wifi,
obviously, so both radios were active for most of the time I was there.
Clearly, I'm not as para^G^G^G^Gconcerned about being tracked or hacked as
some others.

Chris.


On Wed, Aug 7, 2013 at 11:16 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> Dare I ask how many IETFers also kept their cell phones in faraday cages
> for the duration of the conference?
>
>


-- 
Chris Elliott
chelliot@pobox.com

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

<div dir=3D"ltr">My wallet supposedly has a RFID-blocking layer, but I&#39;=
ve not actually tested it. I think the only RFID-capable thing in my wallet=
 is my US passport.<div><br></div><div>I used my cell phone in Berlin exten=
sively, both roaming and on wifi, obviously, so both radios were active for=
 most of the time I was there. Clearly, I&#39;m not as para^G^G^G^Gconcerne=
d about being tracked or hacked as some others.</div>

<div><br></div><div>Chris.</div></div><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">On Wed, Aug 7, 2013 at 11:16 AM, Ted Lemon <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">T=
ed.Lemon@nominum.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">Dare I ask how many IETFers also kept their =
cell phones in faraday cages for the duration of the conference?<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Chris Elliot=
t<br><a href=3D"mailto:chelliot@pobox.com">chelliot@pobox.com</a><br>
</div>

--089e014946f47141d604e35e0050--

From bmanning@isi.edu  Wed Aug  7 10:10:17 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF3AF21F8447 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_57=0.6, 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 Kf2cQpN8Ykzf for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:09:58 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6283611E815F for <ietf@ietf.org>; Wed,  7 Aug 2013 10:09:58 -0700 (PDT)
Received: from [192.168.24.119] (h-66-166-210-203.lsan.ca.megapath.net [66.166.210.203]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r77H81bB000082 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 7 Aug 2013 10:09:29 -0700 (PDT)
Subject: Re: [iaoc-rps] RPS Accessibility
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: manning bill <bmanning@isi.edu>
In-Reply-To: <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@mail.gmail.com>
Date: Wed, 7 Aug 2013 10:08:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <40E6E2F2-D514-467E-85E6-E099C26A9E37@isi.edu>
References: <51FBAF39.1090003@cisco.com> <D97C2C01-0A1C-4599-AB26-DC6FA8F4FE5D@isoc.org> <B74728EF-C578-4E4B-8E62-7AD45870A679@cs.columbia.edu> <CABSMSPVr-h9S+oRVSsRGyuV=yA6F1684JDXVWf2aUE849zr2ww@mail.gmail.com>
To: Riccardo Bernardini <framefritti@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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, 07 Aug 2013 17:10:18 -0000

would this mandate wearing badges only in certain locations, e.g. over =
the left breast?

/bill


On 6August2013Tuesday, at 23:26, Riccardo Bernardini wrote:

> Just thinking out aloud....
>=20
> What about a web-cam (maybe a wireless one? Never tried to use
> them...) right under the mic, so that it takes a picture of the badge
> and shows it on the screen?  Everyone (right?) in a meeting has a
> badge  wit his/her/its :) name and affiliation, so privacy concerns
> are just comparable to those of wearing a badge.
>=20
> Of course, this is not applicable to jabber participants, in that case
> you need a different solution.
>=20
> On Wed, Aug 7, 2013 at 2:41 AM, Henning Schulzrinne =
<hgs@cs.columbia.edu> wrote:
>> Yes, a group from my lab did this, using short-range RFID. (The range =
was about 1-2 inches.) It required a bit of a setup which made it hard =
to replicate at scale, but it worked reasonably well.
>>=20
>> Privacy concerns are an issue, but you'd have to be very close to the =
person to sense the card (and you can obviously leave it behind any time =
you'd want to) - it would be much more convenient to track people using =
BlueTooth or WiFi MAC addresses, if you'd be so inclined, or just use =
video cameras. Yes, you can use long-range directional antennas to =
increase your read range, but those would be rather hard to hide. As was =
mentioned, the hotel room cards use very much the same technology, and =
you can't really leave them behind when you leave the building.
>>=20
>> Henning
>>=20
>> On Aug 5, 2013, at 5:15 AM, Dan York <york@isoc.org> wrote:
>>=20
>>> On the topic of badge-sensing at the mic, I seem to recall that we =
had this working at an IETF sometime back in the RAI working groups. It =
was maybe 4 or 5 years ago and I think it may have been some student(s) =
under Henning Schulzrinne at Columbia... but I am not sure about that.  =
I remember that when you went to the mic you put your badge up to this =
sensor and your name appeared in the jabber room. We used it in several =
of the RAI sessions at that IETF. Unfortunately I don't remember how =
well it worked or why it wasn't continued. There may be someone out =
there who can provide some insight. (And if it was Henning's students we =
can just drop him a note.)
>>>=20
>>> Dan
>>>=20
>>> --
>>> Dan York
>>> york@isoc.org
>>> +1-802-735-1624
>>> skype:danyork
>>> http://twitter.com/danyork
>>>=20
>>> On Aug 2, 2013, at 10:26 AM, "Paul Aitken" <paitken@cisco.com> =
wrote:
>>>=20
>>>> I've remotely participated in several IETFs.
>>>>=20
>>>> I find that the biggest problem with remote attendance is the lack =
of visual cues. I've come to realise just how important these are in a =
meeting.
>>>> -are people paying attention, are they interested / confused / =
distracted / bored?
>>>>=20
>>>> Also there's no way for local attendees (in the WG room) to know =
that remote attendees are "at the mic" and whose turn it is to speak.
>>>>=20
>>>> There's been some discussion on the "87attendees" mailer about =
badge sensing at the mic - whether QR codes, NFC, or RFID. This could =
help remote attendees too.
>>>>=20
>>>> eg, see what they did with NFC + mic here: =
http://www.5thbar.me/blog/2012/09/14/nfc-enabled-badges-at-the-5thbar-mobi=
le-marketing-forum/
>>>>=20
>>>> P.
>>>> _______________________________________________
>>>> iaoc-rps mailing list
>>>> iaoc-rps@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/iaoc-rps
>>>=20
>>=20


From scott.brim@gmail.com  Wed Aug  7 10:25:46 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F86421F8790 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:25: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=[AWL=0.000,  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 RL7SLa1S7MUK for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:25:29 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 083C711E80E2 for <ietf@ietf.org>; Wed,  7 Aug 2013 10:24:56 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id o17so3916610oag.21 for <ietf@ietf.org>; Wed, 07 Aug 2013 10:24:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=M5j2Bt/N2PldNcstlPve8E4nad6k3B2fSZcVbLboi1g=; b=0AgQlckbwz6dR1UfVw4GxvmPfNb+YYOIyTaXXHzXX6sRNqsdJdahwgtTE0T+gkLo/B Lw3qUDwvf+iL0/UVu+3yDdjVFMu/3qCrKcgIDaMzrGECDMJ6x5MnRpf8fs8iTRBjvYV4 M26LPu+TmL+Hikb78ee8CSMjfz01it/3ZOqht8QtmA3PW7FyaCVlm+ozTA1stxnv4RQp oVwd8d57YMe5c5lq5dL07kzgFv3ZZxSFOGfrd2U4Z6jIX5xBVyzhJCUsx6YEH+fPV5Io RIlMYSD1QrbMJEmLHTaNVG3QREMvZXakIuBDKs02lNj2w6xNpouDTa4FvKjNGSsYIs/O NhhA==
X-Received: by 10.60.60.228 with SMTP id k4mr1315211oer.84.1375896291121; Wed, 07 Aug 2013 10:24:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Wed, 7 Aug 2013 10:24:31 -0700 (PDT)
In-Reply-To: <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 7 Aug 2013 13:24:31 -0400
Message-ID: <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com>
Subject: Re: Faraday cages...
To: chelliot@pobox.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 17:25:46 -0000

On Wed, Aug 7, 2013 at 12:26 PM, Chris Elliott <chelliot@pobox.com> wrote:
> My wallet supposedly has a RFID-blocking layer, but I've not actually tested
> it. I think the only RFID-capable thing in my wallet is my US passport.

Take a look at what's in your passport with an NFC tool.  For example,
you can retrieve the photo.

I keep my passport in a "cage" when I'm not handing it to someone.
I'm not concerned about my phone.

From Ted.Lemon@nominum.com  Wed Aug  7 10:28:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1487F21F848A for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.037, 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 u0ocNxnaLGGX for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:28:41 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id BB4E121F9DA3 for <ietf@ietf.org>; Wed,  7 Aug 2013 10:28:39 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUgKDx49BEo63mBBtqcneZm8iC6qG5XwH@postini.com; Wed, 07 Aug 2013 10:28:39 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 115251B8294 for <ietf@ietf.org>; Wed,  7 Aug 2013 10:28:39 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EA749190060; Wed,  7 Aug 2013 10:28:38 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 10:28:39 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Faraday cages...
Thread-Topic: Faraday cages...
Thread-Index: AQHOk4EKqEf7p1HLpUWM3SrXFoUEgpmKY/EAgAAQWYCAAAEnAA==
Date: Wed, 7 Aug 2013 17:28:38 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com>
In-Reply-To: <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FA3EEDC6FB483E41A5F2C292827197AB@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 17:28:48 -0000

On Aug 7, 2013, at 1:24 PM, Scott Brim <scott.brim@gmail.com> wrote:
> I keep my passport in a "cage" when I'm not handing it to someone.
> I'm not concerned about my phone.

Likewise.   The point being, handing everyone in IETF an RFID tag probably =
doesn't have new privacy implications for most of them, and giving them a f=
araday cage, as was done in Hiroshima, addresses the remaining implications=
 for those people who do not carry powered-on cell phones or laptops for pr=
ivacy reasons.   If you carry a powered on cell phone, I don't think you ca=
n argue that carrying an RFID tag with a simple number in it makes things a=
ny worse.

Actually, the main argument I'd make against IETF RFID tags is that it's mo=
re plastic to throw out.


From jabley@hopcount.ca  Wed Aug  7 10:43:15 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7865811E812E for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SPp6svTefp3 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 10:43:14 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D4C4D21F8640 for <ietf@ietf.org>; Wed,  7 Aug 2013 10:43:14 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id 5so1625370pdd.20 for <ietf@ietf.org>; Wed, 07 Aug 2013 10:43:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=o1dwJCUbNgEOE0Q3ZzWeR1goZpbhIGYgTjxR/JtVxMk=; b=Pw8p95zd7WwF6gQsL9xaTGWuMUHTyGpvJgQXmPuNDTFNpWH/3C9m/OszSTZCVkeRra zY54p38HR2b1X9CjUP01FjU8yVJR6knrzsEal5n916ZAcnTQcrcHwptXJ4nwXnAcIXKu wyOqG8PFs1757d6Xm4Z/ZO2sa6aObSHi3GdIE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=o1dwJCUbNgEOE0Q3ZzWeR1goZpbhIGYgTjxR/JtVxMk=; b=kPMp4qfZD+7F6Jrc1lzY8A1I33lHNR+e4kdtrlI7NcuUQeyGyDOArrJx53UnnYmFhm p968uji5KjTovPjrkHKMuYFm1f/5N+sPKb/vmVcbzFWvDz+ayiFRbqZ/mN6ESTDXwnNK KVBQa4mZiOV5tKV7BpG+njJOJGjT4pfGl8lDl63gUoTsPqkYaMnAvDDhDVcKaKWbOYbw IT8gplsQr0cKQIseopKIw+JQR0FPmOAct7tK/5JPRV8BKhEZSJPaXNS/YYWY6zeMJ9Nh 30WxGrkm9pQ8Mst0Q4DoCih5x1vitO8T2/qJx7BcgmWi44ZNn7rvoeGIBOf2075G0Z8i YxyA==
X-Gm-Message-State: ALoCoQmfZd/K8vRBSFTVUwhS8FQ8w31baKKxUF98fIly1S2UnkAU3ioVBfZ427vOFgFKYRp/wUeV
X-Received: by 10.68.213.70 with SMTP id nq6mr1704071pbc.191.1375897394473; Wed, 07 Aug 2013 10:43:14 -0700 (PDT)
Received: from [199.212.90.33] (198-84-196-106.cpe.teksavvy.com. [198.84.196.106]) by mx.google.com with ESMTPSA id wr9sm9443730pbc.7.2013.08.07.10.43.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 Aug 2013 10:43:12 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Faraday cages...
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
Date: Wed, 7 Aug 2013 13:43:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <160AC8CD-03DC-477F-80F8-E684C9C1D85D@hopcount.ca>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1508)
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 17:43:15 -0000

On 2013-08-07, at 13:28, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> [...] I don't think you can argue that carrying an RFID tag with a =
simple number in it makes things any worse.

That sounds right.

The purpose of the badge is to dilute your personal privacy and announce =
your identity to those close enough to see. You can't always tell who is =
looking at your badge. People who see your badge in more than one place =
can infer that you have moved between places. If you don't want people =
to see your badge, you can take it off.

The privacy concerns with badges seem very similar to the privacy =
concerns of carrying RFID tags.

I do not hear a lot of expressed concern about wearing a badge.


Joe


From scott@kitterman.com  Wed Aug  7 11:02:59 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10D8721F8B4E for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 11:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8i4mjT8Kcx9 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 11:02:52 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD1421F9D4A for <ietf@ietf.org>; Wed,  7 Aug 2013 11:01:39 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id A2D6F20E40D4; Wed,  7 Aug 2013 14:01:38 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1375898498; bh=17IgvjAOHZb3kEM0BIUSFoa6uBvKTYox3vw8bT6NEQs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=R/BQMdnnywoeN4mtM+w/Ulewr9PT46zJcANugEznB4GcOwNbckJ/CPz5UZUzmj5r+ RPp4ecMZVNWsff7xAxvoGpmq2j9X695zUW1K5pyJQFN9IDShkoRadTqSkag/Xy/1MQ zuygQp+9HuKRq1pwZa2F/cmlCYxtuoNhGFstxybQ=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 8C10820E40A4;  Wed,  7 Aug 2013 14:01:38 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Faraday cages...
Date: Wed, 07 Aug 2013 14:01:35 -0400
Message-ID: <2869608.qgl48W6i5H@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <160AC8CD-03DC-477F-80F8-E684C9C1D85D@hopcount.ca>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <160AC8CD-03DC-477F-80F8-E684C9C1D85D@hopcount.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 18:02:59 -0000

On Wednesday, August 07, 2013 13:43:06 Joe Abley wrote:
> On 2013-08-07, at 13:28, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> > [...] I don't think you can argue that carrying an RFID tag with a simple
> > number in it makes things any worse.
> That sounds right.
> 
> The purpose of the badge is to dilute your personal privacy and announce
> your identity to those close enough to see. You can't always tell who is
> looking at your badge. People who see your badge in more than one place can
> infer that you have moved between places. If you don't want people to see
> your badge, you can take it off.

In RFID terms, that's what the Faraday cage is for.

> The privacy concerns with badges seem very similar to the privacy concerns
> of carrying RFID tags.
> 
> I do not hear a lot of expressed concern about wearing a badge.

It's more common to have a pocket available than a Faraday cage.

Scott K


From scott.brim@gmail.com  Wed Aug  7 11:13:06 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B7411E814D for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 11:13:06 -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 OKF0VwnjTi3o for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 11:13:06 -0700 (PDT)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id CA36D11E80DE for <ietf@ietf.org>; Wed,  7 Aug 2013 11:13:05 -0700 (PDT)
Received: by mail-qc0-f169.google.com with SMTP id m15so1080925qcq.14 for <ietf@ietf.org>; Wed, 07 Aug 2013 11:13:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=bS1A4QEVR99XpAV192DqHY51Q9SWaqtloLX48HhBDVE=; b=AFL6ghHnvf41Q/iuYQ0XsOp3IfR7Ca4EOy+Lc7YjO2FI8WjOqnWhqeTWeB0dquqwl3 eoQJRz9247+V+TbAiKb1m6sQs3VWTTNrF+8hTSc/P+hdRaej3v2xrBkbjLym3Id2bvyL xastNVrztsdLw/xBolfk/pS5ERWjvP5vwkUfSBkFoHosM7VxrgfNBz9akuW0O4e0eZLm aZC5M7SnqXG66otX8+HsOF88ZEbjExTUE6AVBGeyktmGTl5/EcgExz8mfUPmtLYPgz9o yOjId/tAv2gf4IXH4OfoYxZHR2iBNPfYCLD70eF13LHTb9WJDnwywU7WeazjCk6fjjte 4dTw==
X-Received: by 10.49.104.47 with SMTP id gb15mr1942266qeb.89.1375899185376; Wed, 07 Aug 2013 11:13:05 -0700 (PDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com. [67.241.75.185]) by mx.google.com with ESMTPSA id t9sm455343qap.8.2013.08.07.11.13.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 Aug 2013 11:13:04 -0700 (PDT)
Message-ID: <52028E2B.1000607@gmail.com>
Date: Wed, 07 Aug 2013 14:12:59 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: Faraday cages...
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <160AC8CD-03DC-477F-80F8-E684C9C1D85D@hopcount.ca> <2869608.qgl48W6i5H@scott-latitude-e6320>
In-Reply-To: <2869608.qgl48W6i5H@scott-latitude-e6320>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 18:13:07 -0000

I hope the RFID badges transmit (optional) pictures as well, so when I
harvest them I can use them to associate names with faces.

From carlosm3011@gmail.com  Wed Aug  7 13:06:33 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BB521E8092; Wed,  7 Aug 2013 13:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 hJNA9RM9kWtF; Wed,  7 Aug 2013 13:06:26 -0700 (PDT)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2EFE721F962D; Wed,  7 Aug 2013 13:06:20 -0700 (PDT)
Received: by mail-la0-f41.google.com with SMTP id ec20so1542512lab.14 for <multiple recipients>; Wed, 07 Aug 2013 13:06:20 -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=dCOU9KjhEI680gdKSePCFINv3ErfTZojP7TY79Q9/g0=; b=QabPyvSC512F07DCroNLPYqrFfktDM2rJm7mCNwKZy4PFEp/WnvrJlan++OsMIFEJp ooiEvYcMxGdEhJe8BAGl0qLBvNGahah2RFOMhNaWN/zVjx7hMt2k7Okim1YvCVNjKdcR eEenanFUZCNsqkNiRAl5RmJi3+Z4D5EIN6iUEetUkM8Ye1HHhQI3xMIntfjV6f7F/bA6 WfQiPUr2cJug33+fkmXrdjREwA4B8Xv5DclaTcxhbhTfiZ3/vRr/QC/KL8D/9tPpwVrr PgGkFiVlyPqnnWLZKsrytc+n/gyItG0TvbfCmIjEUyLI2LJvV3bDuOuhnwSYuFL3vUpX 7RSA==
MIME-Version: 1.0
X-Received: by 10.152.121.73 with SMTP id li9mr2188396lab.42.1375905979956; Wed, 07 Aug 2013 13:06:19 -0700 (PDT)
Received: by 10.112.168.225 with HTTP; Wed, 7 Aug 2013 13:06:19 -0700 (PDT)
In-Reply-To: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
References: <C084FA61-AF56-470A-A123-EE8F71DF201C@netapp.com>
Date: Wed, 7 Aug 2013 17:06:19 -0300
Message-ID: <CA+z-_EXWOUXyhuyh5UXyiO56hN6-qa8CktnLC4PNgJDPfneG_A@mail.gmail.com>
Subject: Re: Berlin was awesome, let's come again
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=089e0117744d2e063204e3611376
Cc: IAOC List <IAOC@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 20:06:35 -0000

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

Agreed!

Berlin - Vancouver - Prague my three favourites.

cheers!

~Carlos


On Fri, Aug 2, 2013 at 7:58 AM, Eggert, Lars <lars@netapp.com> wrote:

> Venue was great, food options here and in the city were great, all-around
> great experience. Let's come again!
>
> (I do kinda wonder how there wasn't a single local company willing to step
> up to be the host. That's embarrassing to me as a German, esp. if the IETF
> meets in the self-declared IT hub of Germany. Better luck next time, I
> hope.)
>
> Lars
>



-- 
--
=========================
Carlos M. Martinez-Cagnazzo
http://cagnazzo.name
=========================

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

<div dir=3D"ltr">Agreed!<div><br></div><div>Berlin - Vancouver - Prague my =
three favourites.</div><div><br></div><div>cheers!</div><div><br></div><div=
>~Carlos</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_=
quote">
On Fri, Aug 2, 2013 at 7:58 AM, Eggert, Lars <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lars@netapp.com" target=3D"_blank">lars@netapp.com</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
Venue was great, food options here and in the city were great, all-around g=
reat experience. Let&#39;s come again!<br>
<br>
(I do kinda wonder how there wasn&#39;t a single local company willing to s=
tep up to be the host. That&#39;s embarrassing to me as a German, esp. if t=
he IETF meets in the self-declared IT hub of Germany. Better luck next time=
, I hope.)<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Lars<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>--<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>Carlos M. Martinez-Cagnazzo<br><a href=3D"http://cagnazzo.name=
" target=3D"_blank">http://cagnazzo.name</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
</div>

--089e0117744d2e063204e3611376--

From carlosm3011@gmail.com  Wed Aug  7 13:14:23 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE0F21F9D3B for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[AWL=-0.811, BAYES_20=-0.74, 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 tLLus+fQi6t8 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:14:20 -0700 (PDT)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7852321F9D5E for <ietf@ietf.org>; Wed,  7 Aug 2013 13:13:52 -0700 (PDT)
Received: by mail-la0-f51.google.com with SMTP id fp13so1523398lab.38 for <ietf@ietf.org>; Wed, 07 Aug 2013 13:13:51 -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=YwE72M7sMeXR/lfJ612YPX4KmobgYZHZUWrXkz7DZ3Q=; b=1FhjOHWPZpAqzUHLLk49tesaORPYLM2N7/T3Ixn1P+Ms/SfkG7Ff0HXbM9fUTTZFIp efIEjjcP8JXArQfeYQMXZpmGCQ3kjYV61BthKzlZVhUApI+Pn/XQOlWB5o8x3O/TR5EI 95hZm5f9CiVtlkAwaOrzRVlGoCFbgBTgkQ+RjT7OQq735R+SzDE56UsL8mhrmZ/E6AN+ dRYj+TbMyb/+pJIguq6WerIyFbaQ/1IfKN2z8kyWsyxEijvAif+3ylXmbghRWtoJ6RQz +D7ACKhW+YgBqI/8Sspy3MyS+vpGO2y5BfMa2joe1S57t+dsI/2yfMkdoGCBETOMx78J mHYg==
MIME-Version: 1.0
X-Received: by 10.152.21.225 with SMTP id y1mr2240703lae.18.1375906431280; Wed, 07 Aug 2013 13:13:51 -0700 (PDT)
Received: by 10.112.168.225 with HTTP; Wed, 7 Aug 2013 13:13:51 -0700 (PDT)
In-Reply-To: <20130804201105.3986.qmail@joyce.lan>
References: <20130804201105.3986.qmail@joyce.lan>
Date: Wed, 7 Aug 2013 17:13:51 -0300
Message-ID: <CA+z-_EVXV19=5n_gbkOBdbTJJZ3vRSJRB0SiWdGrU1puDxEZoA@mail.gmail.com>
Subject: Re: Speaking of VAT
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=089e0158b6bc14aeb604e3612e23
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 20:14:23 -0000

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

Hello,


On Sun, Aug 4, 2013 at 5:11 PM, John Levine <johnl@taugh.com> wrote:

> At last week's very successful Berlin meeting, the finances were
> thrown of whack by the late discovery that the IETF had to pay 19%
> German VAT on the registration fee.  At the IAOC session they said
> that about half of that is likely to be reclaimed from VAT paid, but
> the net amount is still a large number.
>
> In Buenos Aires, the VAT rate is 21% on most goods and services, with
> a special 27% rate on telecom services.


Non-nationals can claim VAT back on almost every purchase made during their
stay in Argentina. Given the timeframes involved and that I now doubt that
the IAOC is going to ever be taken again by surprise by any tax-related
matters, I dare say this would be a non-issue for the (hopefully upcoming)
BA meeting.

You can even claim VAT back on that case of Malbec wine many will be surely
be taking back home.

Just keep your receipts and plan an hour extra for the paperwork at the
airport.

cheers!

~Carlos

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

<div dir=3D"ltr">Hello,<br><div class=3D"gmail_extra"><br><br><div class=3D=
"gmail_quote">On Sun, Aug 4, 2013 at 5:11 PM, John 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:1p=
x #ccc solid;padding-left:1ex">At last week&#39;s very successful Berlin me=
eting, the finances were<br>
thrown of whack by the late discovery that the IETF had to pay 19%<br>
German VAT on the registration fee. =A0At the IAOC session they said<br>
that about half of that is likely to be reclaimed from VAT paid, but<br>
the net amount is still a large number.<br>
<br>
In Buenos Aires, the VAT rate is 21% on most goods and services, with<br>
a special 27% rate on telecom services.</blockquote><div><br></div><div>Non=
-nationals can claim VAT back on almost every purchase made during their st=
ay in Argentina. Given the timeframes involved and that I now doubt that th=
e IAOC is going to ever be taken again by surprise by any tax-related matte=
rs, I dare say this would be a non-issue for the (hopefully upcoming) BA me=
eting.</div>
<div><br></div><div>You can even claim VAT back on that case of Malbec wine=
 many will be surely be taking back home.</div><div><br></div><div>Just kee=
p your receipts and plan an hour extra for the paperwork at the airport.</d=
iv>
<div><br></div><div>cheers!</div><div><br></div><div>~Carlos</div></div></d=
iv></div>

--089e0158b6bc14aeb604e3612e23--

From christopher.morrow@gmail.com  Wed Aug  7 13:27:33 2013
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD00F21F9B81 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:27:33 -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 ttO8OX1pgsV3 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:27:33 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id BE27821F9B01 for <ietf@ietf.org>; Wed,  7 Aug 2013 13:27:32 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id fn20so1523414lab.23 for <ietf@ietf.org>; Wed, 07 Aug 2013 13:27:30 -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:message-id:subject :from:to:cc:content-type; bh=FwEVsdhOsO6FCeXLBm1usJM7zAEB8oD7bQL+kcal4QI=; b=fShBH+yH+aKAQkH71AR0j0X2WpAD5wvmaHNubXMd5ok70bTmfFrx+/jVqH3fpLVP8j OW68xdontAdk9fTBZxkrgmdGFh1fekTF/x2HZGmwkJnHpixWHdUw8NWPJvrsdZen2ekt UDae/Mnrq4thHuN5UFsnOoccbwDk0g7dGCAbPnHPg3g2o2kb+BiJ1vKx9RpLSukdvaCF Og8MLy0iGrjpV5rwvsUQWtRAr2QC5viNItHnGB6CdYC+u8ONeuYQ9KLHuMRb2KEsOxI4 KV5cwe+JZ9SKiQ7BG5br2Yt1TJhzjNPRCRXuwj8FjGRnPKZKf9d4efu7mLLshHhn1t4h 9Y8Q==
MIME-Version: 1.0
X-Received: by 10.112.57.49 with SMTP id f17mr987215lbq.26.1375907250363; Wed, 07 Aug 2013 13:27:30 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.22.196 with HTTP; Wed, 7 Aug 2013 13:27:30 -0700 (PDT)
In-Reply-To: <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com>
Date: Wed, 7 Aug 2013 16:27:30 -0400
X-Google-Sender-Auth: 4M1l-2azZq0On2ZLb0eTHNtiWzg
Message-ID: <CAL9jLabR6YDJeX4Ui-oQX6sa98Yt2e+RpxRMg73yFFwbTjFv4Q@mail.gmail.com>
Subject: Re: Faraday cages...
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 20:27:33 -0000

On Wed, Aug 7, 2013 at 1:24 PM, Scott Brim <scott.brim@gmail.com> wrote:
> On Wed, Aug 7, 2013 at 12:26 PM, Chris Elliott <chelliot@pobox.com> wrote:
>> My wallet supposedly has a RFID-blocking layer, but I've not actually tested
>> it. I think the only RFID-capable thing in my wallet is my US passport.
>
> Take a look at what's in your passport with an NFC tool.  For example,
> you can retrieve the photo.

for US passports it seems you have to scan the inside of the back
cover, scanning from the outside doesn't find/activate the rfid token,
yes?

You also need to generate the key material to access the data (DOB +
expiry date of passport + passport number?)

> I keep my passport in a "cage" when I'm not handing it to someone.
> I'm not concerned about my phone.

it seems like simply not waving the passport around open is close to
good enough?
I recall seeing a blackhat/something-or-other demo with a briefcase
that'd read the token though? perhaps with enough wattage you can burn
through the rf shield in the cover?

From ole@cisco.com  Wed Aug  7 13:31:07 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460B621F9AF5 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.427
X-Spam-Level: 
X-Spam-Status: No, score=-110.427 tagged_above=-999 required=5 tests=[AWL=0.172, 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 ZZoT7Xyhog3h for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:31:01 -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 A685621F856A for <ietf@ietf.org>; Wed,  7 Aug 2013 13:31:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=392; q=dns/txt; s=iport; t=1375907461; x=1377117061; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=UQdi841lsMU8F02PCHPijNdHhgo+lTyb21Adkgf1wiY=; b=R/5MXdxQuPOlCCQeQfK+5iOWpHgrt8yKKyUDJoYcRKyo7ltLnOnm9lNj /3feztdzlMGp0OP7hS+l5zb9a/2moy6+pc0GLFW8QsDIwdX+ymz5BgwDc k2MCvwQflLJt2jkD9APEyQcMzkReiL1i16syOb3qyjFnuUG+PgH0Jbom8 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAHStAlKrRDoI/2dsb2JhbABbgwY2vxOBHRZ0giQBAQEDATo/BQsLRlcGLodvBbhBjmKBOAeEDgOJK5RciymDNxw
X-IronPort-AV: E=Sophos;i="4.89,835,1367971200"; d="scan'208";a="85565379"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 07 Aug 2013 20:31:00 +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 r77KUw3w002476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Aug 2013 20:30:58 GMT
Date: Wed, 7 Aug 2013 13:30:58 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Faraday cages...
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
Message-ID: <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: John Levine <johnl@taugh.com>, "<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, 07 Aug 2013 20:31:07 -0000

On Wed, 7 Aug 2013, Ted Lemon wrote:

> Actually, the main argument I'd make against IETF RFID tags is that 
> it's more plastic to throw out.
> 

Unless we adopt the WIDE practice where the tag is re-used from 
meeting to meeting. It's an elegant solution, and not that different
from the reason I own a complete set of Suica, Pasmo, ICOCA, PASPY
and London Oyster cards.

Ole

From cabo@tzi.org  Wed Aug  7 13:53:55 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E2821F9AF8 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKie0EYoXkYu for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:53:50 -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 8ECE621F9C6E for <ietf@ietf.org>; Wed,  7 Aug 2013 13:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r77KrSlG017039; Wed, 7 Aug 2013 22:53:28 +0200 (CEST)
Received: from [192.168.217.105] (p5489221B.dip0.t-ipconnect.de [84.137.34.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 56A00A7D; Wed,  7 Aug 2013 22:53:28 +0200 (CEST)
Subject: Re: Speaking of VAT
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20130804201105.3986.qmail@joyce.lan>
Date: Wed, 7 Aug 2013 22:53:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E8FC6BA-FDEE-4C44-9485-758C3553E33F@tzi.org>
References: <20130804201105.3986.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 20:53:56 -0000

On Aug 4, 2013, at 22:11, John Levine <johnl@taugh.com> wrote:

> At last week's very successful Berlin meeting, the finances were
> thrown of whack by the late discovery that the IETF had to pay 19%
> German VAT on the registration fee.  At the IAOC session they said
> that about half of that is likely to be reclaimed from VAT paid, but
> the net amount is still a large number.

I don't get it.

Given the above, the VAT adjustment is going to cost the IETF ~ 10 % =
revenue.

At the same time, the attendance increased by more than that.

What was thrown out of whack, please?

Gr=FC=DFe, Carsten

PS.: As a European attendee, of course I enjoy the ability to make a VAT =
claim.
In effect, I'm recovering the VAT that IETF paid on goods and services =
in Berlin, and that is exactly what the concept of VAT is about.  =
Raising the price to maintain net revenue at $650 would be disingenuous, =
as the VAT recovered by the IETF is an additional source of income to =
the IETF on top of that net revenue.


From Ted.Lemon@nominum.com  Wed Aug  7 13:56:13 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9470721F99CE for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.563
X-Spam-Level: 
X-Spam-Status: No, score=-106.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVMrYwEGCnXd for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 13:56:06 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 429D321F9BA2 for <ietf@ietf.org>; Wed,  7 Aug 2013 13:55:57 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUgK0XAs8ny163CxznlHlZnAomdyH1kFo@postini.com; Wed, 07 Aug 2013 13:55:57 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8C2711B8298 for <ietf@ietf.org>; Wed,  7 Aug 2013 13:55:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6BADA190060; Wed,  7 Aug 2013 13:55:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 7 Aug 2013 13:55:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Jacobsen <ole@cisco.com>
Subject: Re: Faraday cages...
Thread-Topic: Faraday cages...
Thread-Index: AQHOk4EKqEf7p1HLpUWM3SrXFoUEgpmKY/EAgAAQWYCAAAEnAIAAMvEAgAAG+gA=
Date: Wed, 7 Aug 2013 20:55:55 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net>
In-Reply-To: <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4F3A6CAEE8912745B756909F48C5ACFF@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2013 20:56:13 -0000

On Aug 7, 2013, at 4:30 PM, Ole Jacobsen <ole@cisco.com> wrote:
> Unless we adopt the WIDE practice where the tag is re-used from=20
> meeting to meeting. It's an elegant solution, and not that different
> from the reason I own a complete set of Suica, Pasmo, ICOCA, PASPY
> and London Oyster cards.

That is where I was going with that remark, yes.   :)


From huitema@microsoft.com  Wed Aug  7 17:18:18 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9385511E8184 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 17:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZ9TDbiiU0se for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 17:18:12 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9C311E817B for <ietf@ietf.org>; Wed,  7 Aug 2013 17:18:10 -0700 (PDT)
Received: from BLUPR03CA032.namprd03.prod.outlook.com (10.141.30.25) by BLUPR03MB004.namprd03.prod.outlook.com (10.255.208.38) with Microsoft SMTP Server (TLS) id 15.0.731.11; Thu, 8 Aug 2013 00:18:02 +0000
Received: from BN1AFFO11FD010.protection.gbl (2a01:111:f400:7c10::23) by BLUPR03CA032.outlook.office365.com (2a01:111:e400:879::25) with Microsoft SMTP Server (TLS) id 15.0.731.16 via Frontend Transport; Thu, 8 Aug 2013 00:18:03 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD010.mail.protection.outlook.com (10.58.52.70) with Microsoft SMTP Server (TLS) id 15.0.745.15 via Frontend Transport; Thu, 8 Aug 2013 00:18:02 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.230]) by TK5EX14MLTC104.redmond.corp.microsoft.com ([157.54.79.159]) with mapi id 14.03.0136.001; Thu, 8 Aug 2013 00:17:34 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Ole Jacobsen <ole@cisco.com>
Subject: RE: Faraday cages...
Thread-Topic: Faraday cages...
Thread-Index: AQHOk4Eo+PwNVowznkC6OlPq7r/DAJmJ7pgAgAAQWYCAAAEnAIAAMvEAgAAG+YCAADfpwA==
Date: Thu, 8 Aug 2013 00:17:33 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(199002)(51704005)(76482001)(50466002)(69226001)(76786001)(83072001)(4396001)(33656001)(77982001)(59766001)(23726002)(49866001)(47976001)(74706001)(55846006)(47736001)(77096001)(46102001)(50986001)(16406001)(20776003)(6806004)(31966008)(54316002)(47776003)(46406003)(83322001)(56816003)(47446002)(63696002)(53806001)(81542001)(74876001)(81342001)(66066001)(76796001)(80976001)(80022001)(74366001)(65816001)(44976005)(54356001)(74662001)(74502001)(51856001)(56776001)(79102001); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR03MB004; H:mail.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 093290AD39
X-OriginatorOrg: DuplicateDomain-a84fc36a-4ed7-4e57-ab1c-3e967bcbad48.microsoft.com
X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 131.107.125.37
X-MS-Exchange-CrossPremises-AuthSource: BN1AFFO11FD010.protection.gbl
X-MS-Exchange-CrossPremises-AuthAs: Anonymous
X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-Antispam-ScanContext: DIR:Originating; SFV:NSPM; SKIP:0; 
X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
X-OrganizationHeadersPreserved: BLUPR03MB004.namprd03.prod.outlook.com
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 00:18:19 -0000

>> Unless we adopt the WIDE practice where the tag is re-used from=20
>> meeting to meeting. It's an elegant solution, and not that different=20
>> from the reason I own a complete set of Suica, Pasmo, ICOCA, PASPY and=20
>> London Oyster cards.
>
> That is where I was going with that remark, yes.   :)

Why bother with RFID tags, or badges? Simply register with your cell phone.=
 We can then scan your Wi-Fi and Blue-Tooth signals when you approach the m=
ic.

-- Christian Huitema





From hgs@cs.columbia.edu  Wed Aug  7 18:39:56 2013
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1420021F9A14 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 18:39:56 -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 kQTUomfZ020G for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 18:39:50 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id 2472521F9D23 for <ietf@ietf.org>; Wed,  7 Aug 2013 18:39:49 -0700 (PDT)
Received: from [172.16.150.18] (69-165-173-105.dsl.teksavvy.com [69.165.173.105]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r781dmlP012908 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 7 Aug 2013 21:39:49 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Faraday cages...
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <2869608.qgl48W6i5H@scott-latitude-e6320>
Date: Wed, 7 Aug 2013 21:39:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5714B2BD-8607-47CD-9250-05E4C775291C@cs.columbia.edu>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <160AC8CD-03DC-477F-80F8-E684C9C1D85D@hopcount.ca> <2869608.qgl48W6i5H@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1508)
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: Thu, 08 Aug 2013 01:39:56 -0000

As far as I know, the simple metallically-coated anti-static plastic bag =
that's provided with EZPass (and similar electronic toll systems) is =
quite effective and very cheap. Aluminum foil will also do in a pinch.

On Aug 7, 2013, at 2:01 PM, Scott Kitterman <scott@kitterman.com> wrote:

> On Wednesday, August 07, 2013 13:43:06 Joe Abley wrote:
>> On 2013-08-07, at 13:28, Ted Lemon <Ted.Lemon@nominum.com> wrote:
>>> [...] I don't think you can argue that carrying an RFID tag with a =
simple
>>> number in it makes things any worse.
>> That sounds right.
>>=20
>> The purpose of the badge is to dilute your personal privacy and =
announce
>> your identity to those close enough to see. You can't always tell who =
is
>> looking at your badge. People who see your badge in more than one =
place can
>> infer that you have moved between places. If you don't want people to =
see
>> your badge, you can take it off.
>=20
> In RFID terms, that's what the Faraday cage is for.
>=20
>> The privacy concerns with badges seem very similar to the privacy =
concerns
>> of carrying RFID tags.
>>=20
>> I do not hear a lot of expressed concern about wearing a badge.
>=20
> It's more common to have a pocket available than a Faraday cage.
>=20
> Scott K
>=20
>=20


From hgs@cs.columbia.edu  Wed Aug  7 18:42:19 2013
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D373C11E8190 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 18:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HirxuGFVKbYI for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 18:42:14 -0700 (PDT)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id 65A8211E819B for <ietf@ietf.org>; Wed,  7 Aug 2013 18:42:12 -0700 (PDT)
Received: from [172.16.150.18] (69-165-173-105.dsl.teksavvy.com [69.165.173.105]) (user=hgs10 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r781g9xX011439 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 7 Aug 2013 21:42:10 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Faraday cages...
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
Date: Wed, 7 Aug 2013 21:42:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6FCAD933-0E14-4667-A21C-AF1F9F3409ED@cs.columbia.edu>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1508)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 01:42:20 -0000

What we tried for our experiment was simple: you turn in your RFID card =
at the end of the meeting, and it is randomly re-used for the next one, =
i.e., a new number is assigned each meeting. Unfortunately, we only got =
a relatively small fraction of RFID badges back, if I recall correctly, =
as people presumably forgot to turn them in.

On Aug 7, 2013, at 1:28 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 7, 2013, at 1:24 PM, Scott Brim <scott.brim@gmail.com> wrote:
>> I keep my passport in a "cage" when I'm not handing it to someone.
>> I'm not concerned about my phone.
>=20
> Likewise.   The point being, handing everyone in IETF an RFID tag =
probably doesn't have new privacy implications for most of them, and =
giving them a faraday cage, as was done in Hiroshima, addresses the =
remaining implications for those people who do not carry powered-on cell =
phones or laptops for privacy reasons.   If you carry a powered on cell =
phone, I don't think you can argue that carrying an RFID tag with a =
simple number in it makes things any worse.
>=20
> Actually, the main argument I'd make against IETF RFID tags is that =
it's more plastic to throw out.
>=20
>=20


From rpelletier@isoc.org  Wed Aug  7 19:10:03 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB5021F9B5F for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 19:10:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.637
X-Spam-Level: 
X-Spam-Status: No, score=-102.637 tagged_above=-999 required=5 tests=[AWL=-0.434, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 hAuWpbHU7cFA for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 19:09:58 -0700 (PDT)
Received: from smtp134.ord.emailsrvr.com (smtp134.ord.emailsrvr.com [173.203.6.134]) by ietfa.amsl.com (Postfix) with ESMTP id A48E621F99ED for <ietf@ietf.org>; Wed,  7 Aug 2013 19:09:58 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp13.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 818B0198140; Wed,  7 Aug 2013 22:09:56 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp13.relay.ord1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 1336E198110;  Wed,  7 Aug 2013 22:09:56 -0400 (EDT)
References: <20130804201105.3986.qmail@joyce.lan> <1E8FC6BA-FDEE-4C44-9485-758C3553E33F@tzi.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <1E8FC6BA-FDEE-4C44-9485-758C3553E33F@tzi.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <07F33177-DAC0-4CC2-AA4F-D7A563ED7C82@isoc.org>
X-Mailer: iPhone Mail (10B329)
From: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: Speaking of VAT
Date: Wed, 7 Aug 2013 22:09:51 -0400
To: Carsten Bormann <cabo@tzi.org>
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 02:10:03 -0000

On Aug 7, 2013, at 4:53 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Aug 4, 2013, at 22:11, John Levine <johnl@taugh.com> wrote:
>=20
>> At last week's very successful Berlin meeting, the finances were
>> thrown of whack by the late discovery that the IETF had to pay 19%
>> German VAT on the registration fee.  At the IAOC session they said
>> that about half of that is likely to be reclaimed from VAT paid, but
>> the net amount is still a large number.
>=20
> I don't get it.
>=20
> Given the above, the VAT adjustment is going to cost the IETF ~ 10 % reven=
ue.
>=20
> At the same time, the attendance increased by more than that.
>=20
> What was thrown out of whack, please?
>=20
> Gr=C3=BC=C3=9Fe, Carsten
>=20
> PS.: As a European attendee, of course I enjoy the ability to make a VAT c=
laim.
> In effect, I'm recovering the VAT that IETF paid on goods and services in B=
erlin, and that is exactly what the concept of VAT is about.

In effect you're getting a $103.78 reduction in your $650 registration fee.=20=


>  Raising the price to maintain net revenue at $650 would be disingenuous, a=
s the VAT recovered by the IETF is an additional source of income to the IET=
F on top of that net revenue.

The VAT paid on the Registration Fees will be about $137,000 USD.=20

The VAT we expect to recover is about $65,000 USD after paying fees to a ser=
vice company to recover the VAT.=20

Ray
IAD



>=20

From johnl@taugh.com  Wed Aug  7 19:28:55 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8E811E8166 for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 19:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SitzEJuC8mLu for <ietf@ietfa.amsl.com>; Wed,  7 Aug 2013 19:28:54 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5845011E8133 for <ietf@ietf.org>; Wed,  7 Aug 2013 19:28:53 -0700 (PDT)
Received: (qmail 37868 invoked from network); 8 Aug 2013 02:28:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=93eb.52030263.k1308; bh=HQQLorzHTqziOvNc3eAVLqlhRzMuq5SjGoK3Qbj6QH4=; b=MqmVyvYI53vCkFMS9iSc/lEOwyvUuRrFWA3fXJ01/kPIEbyFBz3A30eeKWSja0URZORyLKHnhGErfCqu4LpvbY9iIPh5fzKutMup7CZgzDsOG1bkWhCVaAIVJRUKIulvzxZS8uRLd8pxBlU8gEor/kD1xp9wRaoJwBchad0D3PbNstbPyjegQBxrCnO3lPUOnC4agTsT3ALur28DabO/tJaSWEaqjJ5phcr9gau9cNOeVTvTZAMZ9purNcoBEWq8
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=93eb.52030263.k1308; bh=HQQLorzHTqziOvNc3eAVLqlhRzMuq5SjGoK3Qbj6QH4=; b=JWJWx/na/YHxzocjDuW0lB4Yn4cJTkJP7tUV4ns1wJsNA1T18VC0TrJwUzR8Wm0u3G9dztuGaiO5+EP/7WdmvzNUkaiX1oCKgdm3R6RSZXUS20Twxom8hB8CN5M3nuLNRAISXudOLQbH8QxyStBOh9NyoUKZ/+JZzivYfXtHuYZ0zEnjApU0wuLRIlDMmVGFiRhj5FZx+xurs69mZsnCIXH9RpHLVz3rRvh3OSE1RO31hqoEbbuPaRvD40OpwHtz
Received: (ofmipd 127.0.0.1); 8 Aug 2013 02:28:29 -0000
Date: 7 Aug 2013 22:28:51 -0400
Message-ID: <alpine.BSF.2.00.1308072228300.50155@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Christian Huitema" <huitema@microsoft.com>
Subject: RE: Faraday cages...
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.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>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 02:28:55 -0000

> Why bother with RFID tags, or badges? Simply register with your cell 
> phone. We can then scan your Wi-Fi and Blue-Tooth signals when you 
> approach the mic.

You must not have seen my cell phone.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From daedulus@btconnect.com  Thu Aug  8 02:44:02 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE32211E81D0 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 02:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.084
X-Spam-Level: 
X-Spam-Status: No, score=-3.084 tagged_above=-999 required=5 tests=[AWL=0.915,  BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EevWLw1iEICY for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 02:43:57 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id 754C811E81CD for <ietf@ietf.org>; Thu,  8 Aug 2013 02:43:57 -0700 (PDT)
Received: from mail1-co9-R.bigfish.com (10.236.132.239) by CO9EHSOBE040.bigfish.com (10.236.130.103) with Microsoft SMTP Server id 14.1.225.22; Thu, 8 Aug 2013 09:43:56 +0000
Received: from mail1-co9 (localhost [127.0.0.1])	by mail1-co9-R.bigfish.com (Postfix) with ESMTP id E00A336012B; Thu,  8 Aug 2013 09:43:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -18
X-BigFish: PS-18(zzbb2dI9371I542I1418Idb82hzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah1de096h5eeeK8275bh8275dh1de097hz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail1-co9 (localhost.localdomain [127.0.0.1]) by mail1-co9 (MessageSwitch) id 1375955034750776_2269; Thu,  8 Aug 2013 09:43:54 +0000 (UTC)
Received: from CO9EHSMHS013.bigfish.com (unknown [10.236.132.233])	by mail1-co9.bigfish.com (Postfix) with ESMTP id A8E4C34004C; Thu,  8 Aug 2013 09:43:54 +0000 (UTC)
Received: from AMSPRD0710HT002.eurprd07.prod.outlook.com (157.56.249.85) by CO9EHSMHS013.bigfish.com (10.236.130.23) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 8 Aug 2013 09:43:54 +0000
Received: from DBXPRD0210HT001.eurprd02.prod.outlook.com (157.56.253.181) by pod51017.outlook.com (10.255.160.165) with Microsoft SMTP Server (TLS) id 14.16.341.1; Thu, 8 Aug 2013 09:43:45 +0000
Message-ID: <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Chris Griffiths <cgriffiths@gmail.com>, ietf <ietf@ietf.org>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
Date: Thu, 8 Aug 2013 10:42:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.181]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 09:44:02 -0000

Chris

I would not like to see the Trust Agreement change to accommodate issues
one or two - I think that the agreement got that one right.

Three is different.  The Trust ought to be able to dispose of rights
that are not needed, never will be and are costing money.  But how can
that be expressed without giving carte blanche to dispose of everything,
for whatever purposes?  We need a proposal as to how that line would be
drawn - I do not have any sound ideas on this.

Can you indicate what annual or one-off costs we are talking about?  The
domain names I have dealt with have been cheap enough not to be
concerned about, once I found the best way to deal with them, although I
understand that the IETF is operating in a different realm and so may
have costs of a different magnitude.

Tom Petch

----- Original Message -----
From: "Chris Griffiths" <cgriffiths@gmail.com>
To: <ietf@ietf.org>
Sent: Saturday, August 03, 2013 7:48 AM

IETF Community,

The IETF Trust Trustees would like feedback from the community on
several issues:
- We have received requests that we cannot accommodate and have
consulted legal counsel to review our options
- The trust agreement does not allow the trustees to effectively manage
some trust assets

The Trust was created in December 2005 by the Internet Society and the
Corporation for National Research Initiatives (CNRI) for the purpose of
"the advancement of education and public interest by acquiring, holding,
maintaining and licensing certain existing and future intellectual
property and other property used in connection with the Internet
standards process and its administration, for the advancement of the
science and technology associated with the Internet and related
technology."
<http://trustee.ietf.org/docs/IETF-Trust-Agreement-Executed-12-15-05.pdf
>

Issue 1

We have recently been asked permission to republish the TAO with a
creative commons license, but according to counsel, the current trust
agreement does not give the trustees the rights to do this.

- Without specific language being added to the trust agreement, we
cannot grant these types of requests.
- The current open request for a creative commons license from 6/18/2013
cannot be completed.

Issue 2

We cannot currently accept physical assets like hardware donations into
the trust.  Once accepted into the trust, we would be unable to dispose
of these items in the future if they are identified as no longer being
needed.

- This removes flexibility in managing assets in the trust, and we
currently use alternative methods of accepting donations outside of the
trust.

Issue 3

Once a domain name or trademark is registered by the trust, it cannot be
abandoned even if it is no longer needed.

- We must maintain these in perpetuity based on legal counsel review of
the current language

You can also find the latest trust report that covers these items and
was presented at the IETF 87 plenary here:
http://www.ietf.org/proceedings/87/slides/slides-87-iesg-opsplenary-4

Thank you and we look forward to getting your feedback.

Chris Griffiths
Chair, IETF Trust



From andrewf@plixer.com  Thu Aug  8 05:44:16 2013
Return-Path: <andrewf@plixer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E8B21E809E for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 05:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Omx5FIhI-UsG for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 05:44:11 -0700 (PDT)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id 457B721E8097 for <ietf@ietf.org>; Thu,  8 Aug 2013 05:44:10 -0700 (PDT)
Received: from [10.11.1.15] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 8 Aug 2013 08:44:09 -0400
Message-ID: <520392A4.3030905@plixer.com>
Date: Thu, 8 Aug 2013 08:44:20 -0400
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com> <52013A6B.1090704@network-heretics.com>
In-Reply-To: <52013A6B.1090704@network-heretics.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 12:44:16 -0000

Hi Keith,

Thanks for clarifying.  Put that way I agree 100%.

-Andrew

On 08/06/2013 02:03 PM, Keith Moore wrote:
> On 08/06/2013 11:06 AM, Andrew Feren wrote:
>> On 08/06/2013 09:08 AM, Keith Moore wrote:
>>> On 08/04/2013 02:54 PM, Ted Lemon wrote:
>>>> While I think getting slides in on time is great for a lot of 
>>>> reasons, reading the slides early isn't that important.   What is 
>>>> important is that remote people see the slides at the same time as 
>>>> local people. For that, it seems to me that Meetecho support does 
>>>> exactly what is needed.   You just follow the slideshow online, 
>>>> along with the audio.
>>>
>>> I agree that remote people should see the slides at the same time as 
>>> local people, except that I think that in both cases this should be 
>>> well before the meeting.  The slides shouldn't be shown at the 
>>> meeting unless needed to illustrate a point of active discussion.
>>>
>>> People keep acting as if the purpose of these meetings - the reason 
>>> people spend thousands of euro and travel thousands of km - is to 
>>> watch slides.
>> Hi Keith,
>>
>> I think this sort of misses the point.  At least for me as a remote 
>> participant.
>
> Actually I think the desire to get slides out early largely misses the 
> point.   Or at least, it's an effort optimizing what should be the 
> rare case.
>
> I fully agree that slides should be easily available to both local and 
> remote participants well prior to any meeting in which a presentation 
> will be made.  (Say a plenary session where presentations are normal 
> and appropriate.)   While speakers might like to revise their slides 
> at the last minute, there's no reason why they shouldn't be expected 
> to upload preliminary slides well in advance (because the key to an 
> effective presentation is good preparation, after all) and a revised 
> version (if necessary) later. This isn't at all rocket science, and 
> there's no reason why it should not be done.
>
> But if we really want to make remote participation effective, we need 
> to figure out better ways to involve remote participants in 
> _discussions_ - not only in plenaries, WG meetings, BOFs, etc., but 
> also in hallway and bar conversations.   Having a local speaker read 
> something from a laptop that was typed into a Jabber session by a 
> remote participant is better than nothing.   But surely we can do better.
>
>> As of today when the slides are available (or if there are no slides 
>> and just talk) I can follow WG meetings quite well.  Being able to 
>> actively engage in any discussion remotely is, IMO, pretty much 
>> limited to the mailing lists.  Getting involved in an active 
>> discussion at a WG meeting remotely is currently difficult at best 
>> and impossible at worst.
>
> It used to be the case that Internet access at IETF meetings was 
> flaky, either because of the wireless network or because of the 
> network connection or both.   More recently the performance of the 
> meeting Internet access has been stellar.   If we put the same kind of 
> effort into facilitating remote participation in discussions, I 
> suspect we could move from "difficult at best and impossible at worse" 
> to "works well".  Of course, it might take awhile, but it's those very 
> kinds of discussions that are so essential to broad consensus that 
> (when it works) makes our standards effective.   The fact that it 
> doesn't work well now is not a good argument for not making it work 
> well in the future.
>
> (We're supposed to be creating the future, after all.  That's our job.)
>
> It's also the case that the fact that facilities for involving remote 
> participants in conversation haven't historically worked well, is used 
> as a justification for continuing to have this dysfunctional style of 
> conducting working group meetings, thus making very poor use of local 
> participants' time and money.
>
> I'm all for making presentation slides available to local and remote 
> participants well before the meeting.   But if we're only concerned 
> with making presentation slides available, we're selling ourselves 
> very short.  That's the point I'm trying to make.
>
> Keith
>


From john-ietf@jck.com  Thu Aug  8 07:43:20 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1C321F9B66 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:43:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.642
X-Spam-Level: 
X-Spam-Status: No, score=-102.642 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StJZFgV4kAm9 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:43:14 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A98B421F8BCE for <ietf@ietf.org>; Thu,  8 Aug 2013 07:43: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 1V7RQk-000DkM-JL; Thu, 08 Aug 2013 10:43:10 -0400
Date: Thu, 08 Aug 2013 10:43:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Feren <andrewf@plixer.com>, James Polk <jmpolk@cisco.com>
Subject: Re: procedural question with remote participation
Message-ID: <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
In-Reply-To: <520110F0.5030100@plixer.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 14:43:20 -0000

--On Tuesday, August 06, 2013 11:06 -0400 Andrew Feren
<andrewf@plixer.com> wrote:

>...
> I think this sort of misses the point.  At least for me as a
> remote participant.
> 
> I'm not interested in arguing about whether slides are good or
> bad. I am interested in following (and being involved) in the
> WG meeting.  When there are slides I want to be able to see
> them clearly from my remote location.  Having them integrated
> with Meetecho works fine.  Having slides and other materials
>...

Let me say part of this differently, with the understanding I
may be more fussy (or older and less tolerant) than Andrew is...

If the IETF is going to claim that remote participation (rather
than remote passive listening/ observation with mailing list
follow up) is feasible, then it has to work.  If, as a remote
participant, I could be guaranteed zero-delay transmission and
receipt of audio and visual materials (including high enough
resolution of slides to be able to read all of them) and that
speakers (in front of the room and at the mic) would identify
themselves clearly and then speak clearly and at reasonable
speed, enunciating every word, I wouldn't care whether slides
were posted in advance or not.  

Realistically, that doesn't happen.  In some cases (e.g.,
lag-free audio) it is beyond the state of the art or a serious
technical challenge (e.g., video that is high enough resolution
that I can slides that have been prepared with 12 point type).
In others, we haven't done nearly enough speaker training or it
hasn't been effective (e.g., people mumbling, speaking very
quickly, swallowing words, or wandering out of microphone or
camera range).   And sometimes there are just problems (e.g.,
intermittent audio or video, servers crashing, noisy audio
cables or other audio or video problems in the room).   

In those cases, as a remote participant, I need all the help I
can get.  I'd rather than no one ever use a slide that has
information on it in a type size that would be smaller than 20
pt on A4 paper.  But 14 pt and even 12 pt happen, especially if
the slides were prepared with a tool that quietly shrinks things
to fit in the image area.  If I'm in the room and such a slide
is projected, I can walk to the front to see if if I'm not
already in front and can't deduce what I need from context.  If
I'm remote and have such a slide in advance, I can zoom in on it
or otherwise get to the information I need (assuming high enough
resolution).  If I'm remote and reading the slide off video,
especially low resolution video, is hopeless.  

More generally, being able to see an outline of what the speaker
is talking about is of huge help when the audio isn't completely
clear.  Others have mentioned this, but, if I couldn't read and
understand slides in English easily in real time, it would be of
even more help if I had the slides far enough in advance to be
able to read through them at my own pace before the WG session
and even make notes abut what they are about in my most-familiar
language ... and that is true whether I'm remote or in the room.

And, yes, for my purposes, 48 hours ahead of the WG meeting
would be plenty.  But I can read and understand English in real
time.  If the IETF cares about diversity as well as about remote
participation and someone whose English is worse than mine is
trying to follow several WGs, 48 hours may not be enough without
requiring a lot of extra effort.

That is not, however, the key reason I said "a week".  The more
important part of the reason is that a one-week cutoff gives the
WG Chair (or IETF or IAB Chairs for the plenaries) the time to
make adjustments.  If there is a nominal one week deadline, then
the WG Chair has lots of warning when things don't show up.  She
can respond by getting on someone's case, by accepting a firm
promise and a closer deadline, by finding someone else to take
charge of the presentation or discussion-leading, or by
rearranging the agenda.  And exceptions can be explained to the
WG on the mailing list.  With a 48 hour deadline, reasonable
ways to compensate are much less likely, the Chair is likely to
have only the choice that was presented this time (accepting
late slides or hurting the WG's ability to consider important
issues) and one needs to start talking about sanctions for bad
behavior.   I would never suggest a firm "one week or no agenda
time" rule.  I am suggesting something much more like a "one
week or the WG Chair needs to make an exception, explain it to
the WG, and be accountable if the late slides cause too much of
a problem".  There is some similarity between this and the
current I-D cutoff rule and its provision for AD-authorized
exceptions.  That similarity is intentional.


--On Monday, August 05, 2013 13:36 -0500 James Polk
<jmpolk@cisco.com> wrote:

> At 12:38 PM 8/5/2013, John C Klensin wrote:
>> Hi.
>> 
>> I seem to have missed a lot of traffic since getting a few
>> responses yesterday.  I think the reasons why slides should be
>> available well in advance of the meeting have been covered
>> well by others.  And, as others have suggested, I'm willing
>> to see updates to those slides if things change in the hours
>> leading up to the meeting, but strongly prefer that those
>> updates come as new alides with update-type "numbers" or other
>> identification rather than new decks.  In other words, if a
>> deck is posted in advance with four slides numbered 1, 2, 3,
>> and 4, and additional information is needed for 3, I'd prefer
>> to see the updated deck consist of slides 1, 2, 3, 3a, 3b, 4
>> or 1, 2, 3a, 3b, 3c, 4, rather than 1, 2, 3, 4, 5, 6.
> 
> How exactly do you do this in pptx? Numbering slides is a
> linear operation AFAICT, and it's binary (it's either on or
> off). Please educate me if I'm wrong; lord knows I don't know
> don't know how to do everything flag/setting in powerpoint...

Hmm.  First, I missed the IESG Statement requiring the people
use pptx or any other particular piece of
presentation-preparation software, much less the IETF consensus
for that statement.  If the tools you choose to use don't meet
the needs of the IETF, that doesn't seem to me to be an IETF
problem.

Second and more important, while having slide preparation
software number pages, I'm not aware of anything that prevents
you from typing in numbers, especially with something that is as
inherently page (slide)-oriented as presentation-preparation
software.  Yes, it is an annoyance, but having the need to
update slides within a short interval before the meeting/
presentation/ discussion is an annoyance to participants who
depend on the ability to access those slides and who might want
to prepare reference or discussion notes in advance.

> And, in my 8 years as TSVWG chair, I've rarely had completely
> new individual slides sprinkled throughout an existing deck.
> Rather, I've received updated slides - each with part of their
> content altered. Does this fall into your desire for a "3a",
> or is that just "3" (because 3a means an entirely new slide
> from scratch)?

3a.  

> BTW - I'm very much *not* in favor of stipulating to my WG
> that slides must be turned in 7 days in advance of a TSVWG
> meeting. I personally think no more than a 48 hour advanced
> window should ever be considered.

See above.

   best,
   john


From hallam@gmail.com  Thu Aug  8 07:47:19 2013
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 AF5C811E81D6 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  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 jjuzzkvMvyP1 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:47:18 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE0021F9D52 for <ietf@ietf.org>; Thu,  8 Aug 2013 07:47:18 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id j17so663249wiw.7 for <ietf@ietf.org>; Thu, 08 Aug 2013 07:47: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=e8JFV4moKLNhyBAWavlG1H+Xti70dgBiqWee1batfdo=; b=llEFDnqx/VsMKzYZbqL3gyuDr4nhHtd10lUY2zsSTioZpL3reJHSOV3u+bsueceKBm f89FS3c1jYcFe3DdXiv+FiIxzi+VLnziSvD45mrKoTWm+SUeBr1AbaiH/NG0Idy3yIp2 egviItmm8jIUefsZwIo40ifSJ1pWawVey/Camgod1GzMK5eX5qXV/OQn0nQrtdAQxfYw izfR5FUvzmocE0+PqyqyPDXBX058SHhzVsuoEx+704k3V5MSbaRACYtDOxkTFcurZgkN NjefGKXoQkrPqOXYd22n25VHv5LZCLxgRqmgJelmJ6jzJuSl/tc+oyOI3fdmIrSH1vta iMrA==
MIME-Version: 1.0
X-Received: by 10.194.85.198 with SMTP id j6mr3567896wjz.51.1375973236035; Thu, 08 Aug 2013 07:47:16 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 07:47:15 -0700 (PDT)
In-Reply-To: <CAL0qLwb=QncDyjh_qqXm4AqzURBtxRNUgTSaSO6X8E9PchEF0A@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAL0qLwb=QncDyjh_qqXm4AqzURBtxRNUgTSaSO6X8E9PchEF0A@mail.gmail.com>
Date: Thu, 8 Aug 2013 10:47:15 -0400
Message-ID: <CAMm+LwgerUOFHgTVrwbekDX-hePzw8QuGAhTn=sPtp2CnNS02g@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=089e0103eea2f4567004e370bb1c
Cc: Joe Hildebrand <hildjj@cursive.net>, Barry Leiba <barryleiba@computer.org>, 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, 08 Aug 2013 14:47:19 -0000

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

The point is that there would BE discussion. Consensus is not enough, the
process has to be open. A consensus formed by keeping people out of the
room is no consensus at all.

Though if the discussion was of the form 'this was already decided' then
that effort would be a farce as well.


What we need for 90% of IETF specifications is nothing more than an easy
way to extend JSON to encode binary blobs without BASE64 encoding. Just
that, nothing more. Instead we have a reinvention of ASN.1 without a schema.

When I say nothing more, I don't mean the rest would be 'nice to have' or
harmless, I mean that it is positively harmful.


I want to be able to mix binary and text forms of the JSON encoding in the
same object. For example, we have part A that collects JSON datagrams from
B and C and puts a wrapper round them. This is a very common requirement in
a network protocol (and one of the things that XML was meant to do but is
horrible at). If we can mix and match Text/Binary JSON this is very simple,
the packager can just include the input from B and C into its output stream
as opaque blobs without having to decide whether to convert them to make
the inner format compatible with the outer wrapper or each other.


The way that we normally decide issues as important as a data encoding
format is to have an open competition where multiple proposals can be made
by anyone with an idea. That is how W3C managed the binary encoding of XML
and how the HTTP 2.0 compression issue is being addressed. The process for
CBOR has been that Carsten writes a spec and then Paul Hoffman acts as Czar
deciding which requirements are to go in it.


At any rate, I have an open source tool on source forge now that generates
an Internet Draft, Examples and sample code from a simple abstract schema.
It currently uses JSON coding but I will be adding a binary encoding, hence
my interest.

I would be happy to add an IETF Proposed Standard binary encoding that had
been the result of an open process.



On Wed, Aug 7, 2013 at 4:28 AM, Murray S. Kucherawy <superuser@gmail.com>wrote:

> On Wed, Aug 7, 2013 at 1:03 AM, Barry Leiba <barryleiba@computer.org>wrote:
>
>> > Using the individual submissions track as a way to circumvent working
>> group
>> > process when there is an actual IETF JSON working group seems completely
>> > wrong to me.
>>
>> No one is circumventing anything.  The JSON working group is not
>> chartered to deal with this or other documents like it, and we won't
>> be rechartering it to do so any time soon.  And remember that any time
>> I'm sponsoring a document as AD, part of what I'm doing is what
>> working group chairs do in a working group: judging rough consensus on
>> the document's content and the issues that concern whether it's
>> intended status is appropriate.  If you (and/or others) can show that
>> there are solid reasons that this should not be a Proposed Standard,
>> or if I do not see rough consensus to publish it, I will not bring it
>> to the rest of the IESG.
>>
>>
> I would add that CBOR has already seen enough interest and feedback that I
> believe it would pass a call for adoption in APPSAWG, and be processed
> there onto the standards track.  That would make Barry's job quite a bit
> easier, since it would then be our job to host the discussion and record
> consensus in that context.  It would also get a shorter IETF Last Call.
>
> Instead, it's going what is for all intents and purposes a tougher route.
> I'm not suggesting we derail its progress to do it the other way, but it
> does suggest to me that the route it's following is hardly a shortcut or
> bypass of some kind.
>
> -MSK
>



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

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

<div dir=3D"ltr">The point is that there would BE discussion. Consensus is =
not enough, the process has to be open. A consensus formed by keeping peopl=
e out of the room is no consensus at all.<div><br></div><div>Though if the =
discussion was of the form &#39;this was already decided&#39; then that eff=
ort would be a farce as well.</div>
<div><br></div><div><br></div><div>What we need for 90% of IETF specificati=
ons is nothing more than an easy way to extend JSON to encode binary blobs =
without BASE64 encoding. Just that, nothing more. Instead we have a reinven=
tion of ASN.1 without a schema.</div>
<div><br></div><div>When I say nothing more, I don&#39;t mean the rest woul=
d be &#39;nice to have&#39; or harmless, I mean that it is positively harmf=
ul.</div><div><br></div><div><br></div><div>I want to be able to mix binary=
 and text forms of the JSON encoding in the same object. For example, we ha=
ve part A that collects JSON datagrams from B and C and puts a wrapper roun=
d them. This is a very common requirement in a network protocol (and one of=
 the things that XML was meant to do but is horrible at). If we can mix and=
 match Text/Binary JSON this is very simple, the packager can just include =
the input from B and C into its output stream as opaque blobs without havin=
g to decide whether to convert them to make the inner format compatible wit=
h the outer wrapper or each other.</div>
<div><br></div><div><br></div><div>The way that we normally decide issues a=
s important as a data encoding format is to have an open competition where =
multiple proposals can be made by anyone with an idea. That is how W3C mana=
ged the binary encoding of XML and how the HTTP 2.0 compression issue is be=
ing addressed. The process for CBOR has been that Carsten writes a spec and=
 then Paul Hoffman acts as Czar deciding which requirements are to go in it=
.</div>
<div><br></div><div><br></div><div>At any rate, I have an open source tool =
on source forge now that generates an Internet Draft, Examples and sample c=
ode from a simple abstract schema. It currently uses JSON coding but I will=
 be adding a binary encoding, hence my interest.=A0</div>
<div><br></div><div>I would be happy to add an IETF Proposed Standard binar=
y encoding that had been the result of an open process.=A0</div><div><br></=
div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Wed, Aug 7, 2013 at 4:28 AM, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Wed, A=
ug 7, 2013 at 1:03 AM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"mailto:=
barryleiba@computer.org" target=3D"_blank">barryleiba@computer.org</a>&gt;<=
/span> wrote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; Using the individual submissions track =
as a way to circumvent working group<br><div>
&gt; process when there is an actual IETF JSON working group seems complete=
ly<br>
&gt; wrong to me.<br>
<br>
</div>No one is circumventing anything. =A0The JSON working group is not<br=
>
chartered to deal with this or other documents like it, and we won&#39;t<br=
>
be rechartering it to do so any time soon. =A0And remember that any time<br=
>
I&#39;m sponsoring a document as AD, part of what I&#39;m doing is what<br>
working group chairs do in a working group: judging rough consensus on<br>
the document&#39;s content and the issues that concern whether it&#39;s<br>
intended status is appropriate. =A0If you (and/or others) can show that<br>
there are solid reasons that this should not be a Proposed Standard,<br>
or if I do not see rough consensus to publish it, I will not bring it<br>
to the rest of the IESG.<br>
<br></blockquote><div><br></div></div><div>I would add that CBOR has alread=
y seen enough interest and feedback that I believe it would pass a call for=
 adoption in APPSAWG, and be processed there onto the standards track.=A0 T=
hat would make Barry&#39;s job quite a bit easier, since it would then be o=
ur job to host the discussion and record consensus in that context.=A0 It w=
ould also get a shorter IETF Last Call.<br>

<br>Instead, it&#39;s going what is for all intents and purposes a tougher =
route.=A0 I&#39;m not suggesting we derail its progress to do it the other =
way, but it does suggest to me that the route it&#39;s following is hardly =
a shortcut or bypass of some kind.<span class=3D"HOEnZb"><font color=3D"#88=
8888"><br>

<br></font></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div=
>-MSK<br></div></font></span></div></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--089e0103eea2f4567004e370bb1c--

From scott.brim@gmail.com  Thu Aug  8 07:54:02 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB9E111E812D for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 Gq-uD8XLGL2F for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 07:54:01 -0700 (PDT)
Received: from mail-qe0-x231.google.com (mail-qe0-x231.google.com [IPv6:2607:f8b0:400d:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 002CD11E8168 for <ietf@ietf.org>; Thu,  8 Aug 2013 07:54:00 -0700 (PDT)
Received: by mail-qe0-f49.google.com with SMTP id 1so1703210qec.8 for <ietf@ietf.org>; Thu, 08 Aug 2013 07:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/r1ZO2o5ziDArQ9MNUWzypV7iwjMqoe6W5f4KTbya04=; b=w0ZcaTH0ZMT89JHG4UYaD5wZ44gb+bRrbtOp6flESnje1dWdJ7eD3R2Zv8V81QNl53 4x2Y9wDg8g7udpjflldvnU4rR5Dyhg0DPeExOoXbB13jYVcUjsuGHgUMFE/vsGdkaLQe jR0UH4tl/JgbGVQx1OBCNp/zi9N43PsQge6PnNRA8bVRqFd4mplXSjp98Yb/h/7EvbWY TkAry0rQ8bWxfFerkbx4pSCXMrVAdKnN1k0qxTVSTPBZrIlbXWTsuyVhkQ5AtbDzP93I OOI4CdhX1I5mWUggr59nlyWHUdXdXkgYd5DmfnS0HSVlmYLTj5HrglVB3y2QgwxZVS+D rNBQ==
X-Received: by 10.229.181.193 with SMTP id bz1mr1528509qcb.13.1375973633153; Thu, 08 Aug 2013 07:53:53 -0700 (PDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com. [67.241.75.185]) by mx.google.com with ESMTPSA id a8sm17614792qae.11.2013.08.08.07.53.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 07:53:52 -0700 (PDT)
Message-ID: <5203B0FE.20301@gmail.com>
Date: Thu, 08 Aug 2013 10:53:50 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com> <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
In-Reply-To: <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 14:54:02 -0000

Well, I've worked remotely for 16 years and in most meetings I don't get
to see the slides until the meeting starts.  Usually I can only see them
via some conferencing tool.  Sometimes I get a copy in mail the week
after.  So I think the IETF is already doing pretty well at making
materials available, and insisting on getting slides far in advance of
the meeting is beyond what most people get in reality outside of the
IETF.  I would call this a SHOULD not a MUST.

From alexey.melnikov@isode.com  Thu Aug  8 08:26:53 2013
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 8348111E8132; Thu,  8 Aug 2013 08:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.776
X-Spam-Level: 
X-Spam-Status: No, score=-101.776 tagged_above=-999 required=5 tests=[AWL=0.824, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOc09VmXuFz0; Thu,  8 Aug 2013 08:26:48 -0700 (PDT)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id 51D0C11E814C; Thu,  8 Aug 2013 08:26:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1375975607; d=isode.com; s=selector; i=@isode.com; bh=TwASpAMHgbRb/efhcyU0hoR/qAsNrA/hDcbn97XbcDk=; 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=dGsMd30XxnVnmdoE+/YsZZKk6PQpRdCwG5h+/at+DacCMecQ5Pk6+/hfS5E+jqdttn6Fb6 CDTpt0xzqVKPNEz6BmiLWHvNapgUzeUmm4LpAnlKQ1qoNoqzblosni5+02oZb8zrjMV17Y zjDQF50ilBBiC3Fb/xl3mvOXvVJJsb4=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by statler.isode.com (submission channel) via TCP with ESMTPA  id <UgO4tgB9nlKm@statler.isode.com>; Thu, 8 Aug 2013 16:26:46 +0100
Message-ID: <5203B8BC.9080108@isode.com>
Date: Thu, 08 Aug 2013 16:26:52 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: ietf@ietf.org
Subject: Re: [TLS] Last Call: <draft-ietf-tls-oob-pubkey-09.txt>  (Out-of-Band Public Key Validation for Transport Layer Security (TLS)) to Proposed Standard
References: <20130802072350.14846.84073.idtracker@ietfa.amsl.com>
In-Reply-To: <20130802072350.14846.84073.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: tls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 15:26:53 -0000

On 02/08/2013 08:23, The IESG wrote:
> The IESG has received a request from the Transport Layer Security WG
> (tls) to consider the following document:
> - 'Out-of-Band Public Key Validation for Transport Layer Security (TLS)'
>    <draft-ietf-tls-oob-pubkey-09.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-08-16. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document specifies a new certificate type and two TLS
>     extensions, one for the client and one for the server, for exchanging
>     raw public keys in Transport Layer Security (TLS) and Datagram
>     Transport Layer Security (DTLS) for use with out-of-band public key
>     validation.
Hi,
I just read the document and support its publication.

I think I found one minor issue:

Section 4.1 says:

    In order to indicate the support of out-of-band raw public keys,
    clients MUST include the 'client_certificate_type' and
    'server_certificate_type' extensions in an extended client hello
    message.  The hello extension mechanism is described in TLS 1.2
    [RFC5246].

In Section 5 (the first example):

client_hello,
    server_certificate_type=(RawPublicKey) -> // [1]

So it looks like the example doesn't comply with the MUST requirement in 
the Section 4.1 ("client_certificate_type" is missing) or the 
requirement stated in Section 4.1 is incorrect. I suspect you meant 
"'client_certificate_type' and/or 'server_certificate_type'" in Section 4.1.

Best Regards,
Alexey





From dhc@dcrocker.net  Thu Aug  8 08:43:52 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD92911E814E for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 08:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n0SZrAI1imnk for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 08:43:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0011221F99ED for <ietf@ietf.org>; Thu,  8 Aug 2013 08:43:47 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r78FhiQv030175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 8 Aug 2013 08:43:47 -0700
Message-ID: <5203BCAC.5050701@dcrocker.net>
Date: Thu, 08 Aug 2013 08:43:40 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com> <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com> <5203B0FE.20301@gmail.com>
In-Reply-To: <5203B0FE.20301@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 08 Aug 2013 08:43:47 -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, 08 Aug 2013 15:43:53 -0000

On 8/8/2013 7:53 AM, Scott Brim wrote:
> Well, I've worked remotely for 16 years and in most meetings I don't get
> to see the slides until the meeting starts.  Usually I can only see them
> via some conferencing tool.  Sometimes I get a copy in mail the week
> after.  So I think the IETF is already doing pretty well at making
> materials available, and insisting on getting slides far in advance of
> the meeting is beyond what most people get in reality outside of the
> IETF.  I would call this a SHOULD not a MUST.


  suspect Scott's experiences matches that of many of us, but let's 
consider possible sampling bias here, which might limit the 
applicability of that experience to the IETF...

There is a difference between being a native English speaker who is 
already integrated into an on-going work effort, versus someone who 
might be neither, as is often true for IETF meetings.

Informative slides that are available ahead of time can be extremely 
helpful, for establishing the context of the presentation/discussion and 
for outlining the main points.

For someone new to a topic or with language limitations, that can make 
the difference between understanding the flow of speech, versus not.

So let's be careful about whether slides ahead of time need to be a 
requirement, rather than being considered only a nice-to-have.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hallam@gmail.com  Thu Aug  8 09:13:07 2013
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 6F74C11E8138 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 09:13:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[AWL=-0.554, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wU0ExmbRpPpb for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 09:13:06 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4ECBA11E8132 for <ietf@ietf.org>; Thu,  8 Aug 2013 09:13:02 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hr7so768747wib.4 for <ietf@ietf.org>; Thu, 08 Aug 2013 09:13:01 -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=WZOf42CiXXpj6NzAxdK5SmJbpTdvS1K0g5ujvqIxjmI=; b=IgSjCxWVkIS51qie7OFSeY8+A1+daoV/zi9CmnG5TlNiV09Q1jICkklpwQD2WZyvtt Du3xWD4zlYThrb7jkU2jOkUSe57MN8p7ioWFrlxSRVkzkn1NfULX6M/mf+7LqxpW5F2o 7Qbt0L45+fT/9gDEQ/rqlwu6jbtaM7iGnA3qRlNEOowwXcON3WB7w8mGfL+AyNDZ6xkZ jXxSvDflPdptA5Q1D74b9UTXz6x3tqpMYg/yQyVW5THj08nGPSI9RtuBijBPoqO5FSZB YM/gqzOGUmgX+xkhGi3drm/oNuwEdMC8QOGlqqwum0cDrGUkw7KMVqywAXGC8UEylZyt YSTA==
MIME-Version: 1.0
X-Received: by 10.180.126.2 with SMTP id mu2mr5452026wib.63.1375978381377; Thu, 08 Aug 2013 09:13:01 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 09:13:01 -0700 (PDT)
Date: Thu, 8 Aug 2013 12:13:01 -0400
Message-ID: <CAMm+Lwji9MOzd2sykLEgxkT0v1tZoEnj=CUu12HiOciCio-w4g@mail.gmail.com>
Subject: Models of building platform standards
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8f642dfca4084104e371eec3
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 16:13:07 -0000

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

The situation with CBOR illustrates a difference of design philosophy that
I think is of much wider relevance. Consider the normal process of
engineering design:

1) Use use cases to develop requirements
2) Perform triage on requirements to focus on most important ones and
3) Implement
4) Test, if necessary return to 1, 2, 3

What makes platform standards different is that the criteria for performing
triage are very different. In normal engineering the engineer talks to the
product manager and puts a dollar cost on each of the various features the
product manager asks for. Which is often guesswork but the engineer is the
person who will suffer if the guess is wrong.

[If the engineer works for Dilbert's boss, it is the pointy haired one who
makes the commitments]


In platform engineering the ultimate use of the platform is unknown and so
triage is not driven by a cost/benefit analysis in the same way. So what
tends to happen is that Working Groups attempt to limit the requirements to
the absolute minimum in order to make the specification as simple as
possible.

The unfortunate fact is that this frequently produces the exact opposite
outcome. PKIX is a very complex standard because it has grown to meet
requirements organically. As a result it has three certificate issue
protocols, two mechanisms for revocation and still lacks a standardized
discovery protocol. When I was asked to design a successor for PKIX in XML
back in 2000, I implemented every feature of PKIX in a 20 page spec. The
spec later formed the basis for the assertion layer in SAML and XKMS where
they did get larger, but nowhere near as large as PKIX.


So I think the approach is broken. Instead of trying to do triage by
limiting use cases and requirements before considering design alternatives
we should instead rank them. So no use case that meets a minimal criteria
of plausibility is rejected but it is understood that the final design need
not cover all the use cases.

The reason for taking this approach is that having to deal with a large
number of requirements forces people to consider a higher level of
abstraction rather than the 'one off' approach that tries to avoid
complexity in the short term by adopting design approaches that are sure to
result in horrors later.






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

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

<div dir=3D"ltr"><div>The situation with CBOR illustrates a difference of d=
esign philosophy that I think is of much wider relevance. Consider the norm=
al process of engineering design:</div><div><br></div><div>1) Use use cases=
 to develop requirements<br>
</div><div>2) Perform triage on requirements to focus on most important one=
s and=A0<br></div><div>3) Implement<br></div><div>4) Test, if necessary ret=
urn to 1, 2, 3<br></div><div><br></div><div>What makes platform standards d=
ifferent is that the criteria for performing triage are very different. In =
normal engineering the engineer talks to the product manager and puts a dol=
lar cost on each of the various features the product manager asks for. Whic=
h is often guesswork but the engineer is the person who will suffer if the =
guess is wrong.</div>
<div><br></div><div>[If the engineer works for Dilbert&#39;s boss, it is th=
e pointy haired one who makes the commitments]</div><div><br></div><div><br=
></div><div>In platform engineering the ultimate use of the platform is unk=
nown and so triage is not driven by a cost/benefit analysis in the same way=
. So what tends to happen is that Working Groups attempt to limit the requi=
rements to the absolute minimum in order to make the specification as simpl=
e as possible.</div>
<div><br></div><div>The unfortunate fact is that this frequently produces t=
he exact opposite outcome. PKIX is a very complex standard because it has g=
rown to meet requirements organically. As a result it has three certificate=
 issue protocols, two mechanisms for revocation and still lacks a standardi=
zed discovery protocol. When I was asked to design a successor for PKIX in =
XML back in 2000, I implemented every feature of PKIX in a 20 page spec. Th=
e spec later formed the basis for the assertion layer in SAML and XKMS wher=
e they did get larger, but nowhere near as large as PKIX.</div>
<div><br></div><div><br></div><div>So I think the approach is broken. Inste=
ad of trying to do triage by limiting use cases and requirements before con=
sidering design alternatives we should instead rank them. So no use case th=
at meets a minimal criteria of plausibility is rejected but it is understoo=
d that the final design need not cover all the use cases.</div>
<div><br></div><div>The reason for taking this approach is that having to d=
eal with a large number of requirements forces people to consider a higher =
level of abstraction rather than the &#39;one off&#39; approach that tries =
to avoid complexity in the short term by adopting design approaches that ar=
e sure to result in horrors later.</div>
<div><br></div><div><br></div><div><br></div><div><br></div><br clear=3D"al=
l"><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/" targe=
t=3D"_blank">http://hallambaker.com/</a><br>
</div>

--e89a8f642dfca4084104e371eec3--

From hallam@gmail.com  Thu Aug  8 10:48:02 2013
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 AFBDD1F0D55 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 10:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, 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 q8PETj7fPThp for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 10:48:01 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id E6DF21F0D53 for <ietf@ietf.org>; Thu,  8 Aug 2013 10:47:58 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id en1so868382wid.0 for <ietf@ietf.org>; Thu, 08 Aug 2013 10:47:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mMkEGgp3OdirQWeQNkgA9YoDXTF96kr6+PU31BjmVo8=; b=gYkebFF557toW/e+6q30+em7ob87mp83Z2zqUkesOPLrSn2IEH3dDFEkez6pMyEEPd PbwljzDqUmmCbNIZ8eGodYJBKl5xLyvFdX+bYJA8qE+yMFCdZrsO+fQUMentdbr7LA0h QaFcuPlTglWZnXae5mAD+bJc0+Wabxppg0AGZh5biJWpXbiEMZOrw4t3AWGiIcNPY+wJ GklsRRvrOPA0IP5+B/lNgmfxlgFVD3fUEsOG4XYuGSgLbpRvJ5p2ZUyp2VqL2dWAZoO4 YYQwFOKWUTNiPTBh9mjSWcjqxvBol8dr/YtxhPKxKaTmNUDrB4OxaSqW6cNWyA9SNq+Z 5kGw==
MIME-Version: 1.0
X-Received: by 10.180.183.40 with SMTP id ej8mr42625wic.37.1375984077979; Thu, 08 Aug 2013 10:47:57 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 10:47:57 -0700 (PDT)
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com>
Date: Thu, 8 Aug 2013 13:47:57 -0400
Message-ID: <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com>
Subject: Re: Faraday cages...
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Christian Huitema <huitema@microsoft.com>
Content-Type: multipart/alternative; boundary=001a11c2297a2f47f804e3734290
Cc: Ole Jacobsen <ole@cisco.com>, John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 17:48:02 -0000

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

On Wed, Aug 7, 2013 at 8:17 PM, Christian Huitema <huitema@microsoft.com>wrote:

> >> Unless we adopt the WIDE practice where the tag is re-used from
> >> meeting to meeting. It's an elegant solution, and not that different
> >> from the reason I own a complete set of Suica, Pasmo, ICOCA, PASPY and
> >> London Oyster cards.
> >
> > That is where I was going with that remark, yes.   :)
>
> Why bother with RFID tags, or badges? Simply register with your cell
> phone. We can then scan your Wi-Fi and Blue-Tooth signals when you approach
> the mic.
>
> -- Christian Huitema
>

'Simply'

What is this simple technology of which you speak? I find that the best we
can do with electronic systems is about 99% and that takes a huge amount of
effort. I have a whole drawerful of bluetooth headsets and thats where they
will stay because none of them works well enough to be useful.

I have the whole Apple/Nest/Sonos/Windows/etc suite in the house. The UI
sucks because my phone takes about 45 seconds to context switch to a new
applet. Often it takes a lot longer as the applet begs to be updated for no
particular reason.


If we want to do simple then use a BARCODE.

A webcam is cheaper and easier to come by than wireless scanning devices.
They are just as reliable and there is only one device with a source of
power involved. We could easily add QR codes to the front and rear of the
badges.

A side benefit would be that we also equip ourselves for showing video of
people at the mic at the same time (should that prove desirable).

No privacy issues, much more robust. It even deals with the issue I have
occasionally had where I have had a plane delay and gone straight from the
airport to a WG meeting before picking up my badge. Rare exceptions like
that are easy to declare, just state it in advance at the mic. I doubt the
RFID cars and the associated readers will work as well. Trying to reuse my
cell phone is an exercise in the crazy.



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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Aug 7, 2013 at 8:17 PM, Christian Huitema <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:huitema@microsoft.com" target=3D"_blank">huitema@mic=
rosoft.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt;&gt; Unless we adopt t=
he WIDE practice where the tag is re-used from<br>
&gt;&gt; meeting to meeting. It&#39;s an elegant solution, and not that dif=
ferent<br>
&gt;&gt; from the reason I own a complete set of Suica, Pasmo, ICOCA, PASPY=
 and<br>
&gt;&gt; London Oyster cards.<br>
&gt;<br>
&gt; That is where I was going with that remark, yes. =A0 :)<br>
<br>
</div>Why bother with RFID tags, or badges? Simply register with your cell =
phone. We can then scan your Wi-Fi and Blue-Tooth signals when you approach=
 the mic.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Christian Huitema<br></font></span></blockquote><div><br></div><div>&#39=
;Simply&#39;</div><div>=A0</div><div>What is this simple technology of whic=
h you speak? I find that the best we can do with electronic systems is abou=
t 99% and that takes a huge amount of effort. I have a whole drawerful of b=
luetooth headsets and thats where they will stay because none of them works=
 well enough to be useful.</div>
<div><br></div><div>I have the whole Apple/Nest/Sonos/Windows/etc suite in =
the house. The UI sucks because my phone takes about 45 seconds to context =
switch to a new applet. Often it takes a lot longer as the applet begs to b=
e updated for no particular reason.</div>
<div><br></div><div><br></div><div>If we want to do simple then use a BARCO=
DE.</div><div><br></div><div>A webcam is cheaper and easier to come by than=
 wireless scanning devices. They are just as reliable and there is only one=
 device with a source of power involved. We could easily add QR codes to th=
e front and rear of the badges.</div>
<div><br></div><div>A side benefit would be that we also equip ourselves fo=
r showing video of people at the mic at the same time (should that prove de=
sirable).</div><div><br></div><div>No privacy issues, much more robust. It =
even deals with the issue I have occasionally had where I have had a plane =
delay and gone straight from the airport to a WG meeting before picking up =
my badge. Rare exceptions like that are easy to declare, just state it in a=
dvance at the mic. I doubt the RFID cars and the associated readers will wo=
rk as well. Trying to reuse my cell phone is an exercise in the crazy.</div=
>
<div><br></div><div><br></div></div><div><br></div>-- <br>Website: <a href=
=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2297a2f47f804e3734290--

From Ted.Lemon@nominum.com  Thu Aug  8 11:44:21 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4A811E8203 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 11:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 QnFh+SJTVg+M for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 11:44:15 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id D6E4711E8163 for <ietf@ietf.org>; Thu,  8 Aug 2013 11:44:14 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUgPm+fwyay5656qrhERua+bx5ogykKt/@postini.com; Thu, 08 Aug 2013 11:44:14 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6D8DE1B82A0 for <ietf@ietf.org>; Thu,  8 Aug 2013 11:44:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 48ED6190060; Thu,  8 Aug 2013 11:44:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 8 Aug 2013 11:44:03 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Faraday cages...
Thread-Topic: Faraday cages...
Thread-Index: AQHOk4EKqEf7p1HLpUWM3SrXFoUEgpmKY/EAgAAQWYCAAAEnAIAAMvEAgAAG+gCAADhVgIABJXqAgAAPrYA=
Date: Thu, 8 Aug 2013 18:44:03 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com>
In-Reply-To: <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B0C1BFC4496BCF49941CF7AC5EC64DB1@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Christian Huitema <huitema@microsoft.com>, Ole Jacobsen <ole@cisco.com>, John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 18:44:21 -0000

On Aug 8, 2013, at 1:47 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> Why bother with RFID tags, or badges? Simply register with your cell phon=
e. We can then scan your Wi-Fi and Blue-Tooth signals when you approach the=
 mic.
>=20
> -- Christian Huitema
>=20
> 'Simply'
> =20
> What is this simple technology of which you speak? I find that the best w=
e can do with electronic systems is about 99% and that takes a huge amount =
of effort. I have a whole drawerful of bluetooth headsets and thats where t=
hey will stay because none of them works well enough to be useful.

I am fairly sure Christian was being ironic.


From hallam@gmail.com  Thu Aug  8 11:52:12 2013
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 EED3221F8488; Thu,  8 Aug 2013 11:52:11 -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, 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 eYFjd92vefxb; Thu,  8 Aug 2013 11:52:10 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1C0DD21F9D98; Thu,  8 Aug 2013 11:52:08 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hr7so929420wib.4 for <multiple recipients>; Thu, 08 Aug 2013 11:52: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=L8SIwv1MJyfKOYAlGV7IvmKvFIeSwtkHcoGNCpTtU1k=; b=G5JaNolMZG92UgtCItJpSOQ1UlHMayWcsTG93xO4/AXmjFsAV8hmHGMTzIqGyfeuA3 L48Vrl+vSyE7hN/JEkzbd6GeMzhC/V/nn/dRjJ6WzP64XxS0ACmUM1i/6iw1936dPypR SyK2mSe2r8KIhXKRmxouW6c8GvXbX3Y1wjpptX6kTQ2OUMDRUDw+9AXvkyEqJJFlf7jZ 1tXn9TVuek+dMRWPal/DxX0HVtDPePv1ur6Tg4clejb++av9B4a0K5yz5TobfILyMHg0 3UjyGq2cdmB7mi7y3Le897vF/2q8+I279Wt79TDqkWRj/ykrxyQ9qtBYR9oHUhDopfJn aW5Q==
MIME-Version: 1.0
X-Received: by 10.180.183.40 with SMTP id ej8mr177353wic.37.1375987926995; Thu, 08 Aug 2013 11:52:06 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 11:52:06 -0700 (PDT)
In-Reply-To: <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com>
Date: Thu, 8 Aug 2013 14:52:06 -0400
Message-ID: <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Barry Leiba <barryleiba@computer.org>, "iesg@ietf.org" <iesg@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c2297a9a975b04e3742703
Cc: Joe Hildebrand <hildjj@cursive.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: Thu, 08 Aug 2013 18:52:12 -0000

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

Barry,

Could you please answer the questions I put to you privately:

* Will CBOR become the default binary JSON encoding?
* Will other IETF WGs be expected to adopt CBOR as their binary encoding?
* Will you consider publishing alternative binary encodings of JSON?

I accept that there are circumstances where an individual submission is
appropriate. But I do not think that something that is designed to be built
on by other IETF Working Groups is appropriate for individual submission.

Adding a media type or a PKIX feature or HTTP header are all case where
individual submission to Proposed STANDARD is quite appropriate. CBOR is
not.


The test I think should apply here is the dog food test: Is anyone else
going to be expected to eat the product.


In this case we have a specification that I am likely going to have to
argue against as flawed in every WG which might use it. Which is likely to
mean a lot of unnecessary WG effort, IESG effort and appeals.

Most of us here have experience of using ASN.1, XML and JSON. Most of us
have had a considerable amount of unnecessary pain as a result of ASN.1 and
XML. The Web Services world would probably have taken off much quicker if
there has been some debate and discussion before the decision was taken to
turn XML into the standard for data exchange.

Here we have a situation where you have decided to take a short cut on a
decision that could hardly be more fundamental to the design of network
protocols and handed the whole design process off to two individuals to
make a design decision in private.


For example, take the following messages from the CBOR authors:

On Wed, May 22, 2013 at 12:16 PM, Paul Hoffman <paul.hoffman@vpnc.org>
 wrote:

> On May 22, 2013, at 9:14 AM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
>
> > I think we can all agree that *A* binary format would be useful and that
> two dozen are not useful.
>
> Nope, that is patently absurd. That would only be true if everyone agreed
> on all the design goals and decisions for the one binary format, and that
> clearly cannot happen.


I think that one binary format for JSON data structures is an eminently
achievable goal. There is a limited design space, the JSON model covers
almost all necessary data types, the main exception being binary blobs.

At the very most there might be space for one, two or three binary
encodings for use in IETF protocols. But isn't the notion that binary
encodings become like EAP authentication methods and we end up with two
dozen what is really absurd?


On Wed, May 22, 2013 at 6:42 PM, Tony Finch <dot@dotat.at> wrote:

> Why not BSON or BJSON or UBJSON or MsgPack or ... ?


I never did see that question answered on the list. To be clear, there are
reasons why I don't think the formats Tony suggests cannot become a
universal standard but those objections also apply to CBOR which also has
the problem of not being based on the JSON data model.

The reason that I don't find putting the reasons in the draft an acceptable
substitute to answering the three people who raised the point is that it
was a cop out. Paul and Carsten gave their design rationale unilaterally
and were not prepared to have their decisions challenged.


Neither Paul nor Carsten have ever been noted for ranting about why XML and
ASN.1 are broken. Which I see as a problem because to do a better job than
those two, you really have to understand why those projects went so badly
wrong.

ASN.1 came very close to getting it right but they only did extensibility
as an afterthought and the way they ended up handling it means that you
can't use ASN.1 without a code writing tool which means that you can't use
it from Perl, Python etc. unless someone has written the tool for those.

XML might have been the solution but the XML design team was charged with
writing a document markup language that could be defined using SGML DTD and
data markup only needs about 5% of the features in XML as a result.



On Wed, Aug 7, 2013 at 4:03 AM, Barry Leiba <barryleiba@computer.org> wrote:

> A couple of procedural points here:
>
> > The issue here is whether this proposal should be an IETF Proposed
> STANDARD.
> ...
> > Usually when the IETF publishes an algorithm it is given INFORMATIONAL or
> > EXPERIMENTAL status. That is what originally happened with JSON, RFC 4627
> > has INFORMATIONAL status despite the fact that at the time it was written
> > there was a lot of implementation.
>
> First, Proposed Standard is just that: a proposal.  It does not
> require implementations.  It requires that it be "generally stable,
> has resolved known design choices, is believed to be well-understood,
> has received significant community review, and appears to enjoy enough
> community interest to be considered valuable."  That's from RFC 2026,
> Section 4.1.1, which goes on to say, "Usually, neither implementation
> nor operational experience is required for the designation of a
> specification as a Proposed Standard."
>
> I believe that CBOR qualifies, which is why I agreed to AD-sponsor it.
>  In the process, I'm looking to see if we have rough consensus that
> all this is the case.  Your substantive comments on the document, as
> well as those of others, should address those points (as some of your
> comments indeed do).
>
> Second, RFC 4627 is Informational because it was not meant to be the
> standard definition of JSON.  It was meant only to register the media
> type.  But one thing led to another, and it did become the referenced
> definition, which is why the JSON working group is working on fixing
> its gaps and moving it to Standards Track.
>
> > Using the individual submissions track as a way to circumvent working
> group
> > process when there is an actual IETF JSON working group seems completely
> > wrong to me.
>
> No one is circumventing anything.  The JSON working group is not
> chartered to deal with this or other documents like it, and we won't
> be rechartering it to do so any time soon.  And remember that any time
> I'm sponsoring a document as AD, part of what I'm doing is what
> working group chairs do in a working group: judging rough consensus on
> the document's content and the issues that concern whether it's
> intended status is appropriate.  If you (and/or others) can show that
> there are solid reasons that this should not be a Proposed Standard,
> or if I do not see rough consensus to publish it, I will not bring it
> to the rest of the IESG.
>
> Barry, Applications AD
>



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

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

<div dir=3D"ltr">Barry,<div><br></div><div>Could you please answer the ques=
tions I put to you privately:=A0</div><div><br></div><div>* Will CBOR becom=
e the default binary JSON encoding?</div><div>* Will other IETF WGs be expe=
cted to adopt CBOR as their binary encoding?</div>
<div>* Will you consider publishing alternative binary encodings of JSON?</=
div><div><br></div><div>I accept that there are circumstances where an indi=
vidual submission is appropriate. But I do not think that something that is=
 designed to be built on by other IETF Working Groups is appropriate for in=
dividual submission.</div>
<div><br></div><div>Adding a media type or a PKIX feature or HTTP header ar=
e all case where individual submission to Proposed STANDARD is quite approp=
riate. CBOR is not.</div><div><br></div><div><br></div><div>The test I thin=
k should apply here is the dog food test: Is anyone else going to be expect=
ed to eat the product.</div>
<div><br></div><div><br></div><div>In this case we have a specification tha=
t I am likely going to have to argue against as flawed in every WG which mi=
ght use it. Which is likely to mean a lot of unnecessary WG effort, IESG ef=
fort and appeals.</div>
<div><br></div><div>Most of us here have experience of using ASN.1, XML and=
 JSON. Most of us have had a considerable amount of unnecessary pain as a r=
esult of ASN.1 and XML. The Web Services world would probably have taken of=
f much quicker if there has been some debate and discussion before the deci=
sion was taken to turn XML into the standard for data exchange.</div>
<div><br></div><div>Here we have a situation where you have decided to take=
 a short cut on a decision that could hardly be more fundamental to the des=
ign of network protocols and handed the whole design process off to two ind=
ividuals to make a design decision in private.</div>
<div><br></div><div><br></div><div>For example, take the following messages=
 from the CBOR authors:</div><div><br></div><div><div class=3D"im" style=3D=
"font-family:arial,sans-serif;font-size:12.800000190734863px"><div class=3D=
"" style=3D"color:rgb(34,34,34)">
<div class=3D"im">On Wed, May 22, 2013 at 12:16 PM, Paul Hoffman=A0<span di=
r=3D"ltr">&lt;<a href=3D"mailto:paul.hoffman@vpnc.org" target=3D"_blank">pa=
ul.hoffman@vpnc.org</a>&gt;</span>=A0wrote:<br></div></div><div class=3D"gm=
ail_extra" style=3D"color:rgb(34,34,34)">
<div class=3D""><div class=3D"adm"></div><div class=3D"im"><div class=3D"gm=
ail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex">
<div>On May 22, 2013, at 9:14 AM, Phillip Hallam-Baker &lt;<a href=3D"mailt=
o:hallam@gmail.com" target=3D"_blank">hallam@gmail.com</a>&gt; wrote:<br><b=
r>&gt; I think we can all agree that *A* binary format would be useful and =
that two dozen are not useful.<br>
<br></div>Nope, that is patently absurd. That would only be true if everyon=
e agreed on all the design goals and decisions for the one binary format, a=
nd that clearly cannot happen.</blockquote></div></div></div></div></div>
</div><div><br></div><div>I think that one binary format for JSON data stru=
ctures is an eminently achievable goal. There is a limited design space, th=
e JSON model covers almost all necessary data types, the main exception bei=
ng binary blobs.</div>
<div><br></div><div>At the very most there might be space for one, two or t=
hree binary encodings for use in IETF protocols. But isn&#39;t the notion t=
hat binary encodings become like EAP authentication methods and we end up w=
ith two dozen what is really absurd?</div>
<div><br></div><div><br></div><div><span style=3D"color:rgb(80,0,80);font-f=
amily:arial,sans-serif;font-size:12.800000190734863px">On Wed, May 22, 2013=
 at 6:42 PM, Tony Finch=A0</span><span dir=3D"ltr" style=3D"color:rgb(80,0,=
80);font-family:arial,sans-serif;font-size:12.800000190734863px">&lt;<a hre=
f=3D"mailto:dot@dotat.at" target=3D"_blank">dot@dotat.at</a>&gt;</span><spa=
n style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:12.800=
000190734863px">=A0wrote:</span><br style=3D"color:rgb(80,0,80);font-family=
:arial,sans-serif;font-size:12.800000190734863px">
<blockquote class=3D"gmail_quote" style=3D"color:rgb(80,0,80);font-family:a=
rial,sans-serif;font-size:12.800000190734863px;margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">
Why not BSON or BJSON or UBJSON or MsgPack or ... ?</blockquote><div><br></=
div><div>I never did see that question answered on the list. To be clear, t=
here are reasons why I don&#39;t think the formats Tony suggests cannot bec=
ome a universal standard but those objections also apply to CBOR which also=
 has the problem of not being based on the JSON data model.</div>
<div><br></div><div>The reason that I don&#39;t find putting the reasons in=
 the draft an acceptable substitute to answering the three people who raise=
d the point is that it was a cop out. Paul and Carsten gave their design ra=
tionale unilaterally and were not prepared to have their decisions challeng=
ed.</div>
<div><br></div><div><br></div><div>Neither Paul nor Carsten have ever been =
noted for ranting about why XML and ASN.1 are broken. Which I see as a prob=
lem because to do a better job than those two, you really have to understan=
d why those projects went so badly wrong.=A0</div>
</div><div><br></div><div>ASN.1 came very close to getting it right but the=
y only did extensibility as an afterthought and the way they ended up handl=
ing it means that you can&#39;t use ASN.1 without a code writing tool which=
 means that you can&#39;t use it from Perl, Python etc. unless someone has =
written the tool for those.</div>
<div><br></div><div>XML might have been the solution but the XML design tea=
m was charged with writing a document markup language that could be defined=
 using SGML DTD and data markup only needs about 5% of the features in XML =
as a result.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Aug 7, 2013 at 4:03 AM, Barry Leiba <span dir=3D"ltr">&lt;<=
a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryleiba@comp=
uter.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">A couple of procedural points here:<br>
<div class=3D"im"><br>
&gt; The issue here is whether this proposal should be an IETF Proposed STA=
NDARD.<br>
</div>...<br>
<div class=3D"im">&gt; Usually when the IETF publishes an algorithm it is g=
iven INFORMATIONAL or<br>
&gt; EXPERIMENTAL status. That is what originally happened with JSON, RFC 4=
627<br>
&gt; has INFORMATIONAL status despite the fact that at the time it was writ=
ten<br>
&gt; there was a lot of implementation.<br>
<br>
</div>First, Proposed Standard is just that: a proposal. =A0It does not<br>
require implementations. =A0It requires that it be &quot;generally stable,<=
br>
has resolved known design choices, is believed to be well-understood,<br>
has received significant community review, and appears to enjoy enough<br>
community interest to be considered valuable.&quot; =A0That&#39;s from RFC =
2026,<br>
Section 4.1.1, which goes on to say, &quot;Usually, neither implementation<=
br>
nor operational experience is required for the designation of a<br>
specification as a Proposed Standard.&quot;<br>
<br>
I believe that CBOR qualifies, which is why I agreed to AD-sponsor it.<br>
=A0In the process, I&#39;m looking to see if we have rough consensus that<b=
r>
all this is the case. =A0Your substantive comments on the document, as<br>
well as those of others, should address those points (as some of your<br>
comments indeed do).<br>
<br>
Second, RFC 4627 is Informational because it was not meant to be the<br>
standard definition of JSON. =A0It was meant only to register the media<br>
type. =A0But one thing led to another, and it did become the referenced<br>
definition, which is why the JSON working group is working on fixing<br>
its gaps and moving it to Standards Track.<br>
<div class=3D"im"><br>
&gt; Using the individual submissions track as a way to circumvent working =
group<br>
&gt; process when there is an actual IETF JSON working group seems complete=
ly<br>
&gt; wrong to me.<br>
<br>
</div>No one is circumventing anything. =A0The JSON working group is not<br=
>
chartered to deal with this or other documents like it, and we won&#39;t<br=
>
be rechartering it to do so any time soon. =A0And remember that any time<br=
>
I&#39;m sponsoring a document as AD, part of what I&#39;m doing is what<br>
working group chairs do in a working group: judging rough consensus on<br>
the document&#39;s content and the issues that concern whether it&#39;s<br>
intended status is appropriate. =A0If you (and/or others) can show that<br>
there are solid reasons that this should not be a Proposed Standard,<br>
or if I do not see rough consensus to publish it, I will not bring it<br>
to the rest of the IESG.<br>
<br>
Barry, Applications AD<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--001a11c2297a9a975b04e3742703--

From mcr@sandelman.ca  Thu Aug  8 12:23:50 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1C111E81F7 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 12:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.41
X-Spam-Level: 
X-Spam-Status: No, score=-2.41 tagged_above=-999 required=5 tests=[AWL=0.189,  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 l0mMC-k0RmEq for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 12:23:49 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id C67B911E8211 for <ietf@ietf.org>; Thu,  8 Aug 2013 12:23:46 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2251D20263 for <ietf@ietf.org>; Thu,  8 Aug 2013 16:30:18 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 5F532A904C; Thu,  8 Aug 2013 15:22:15 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1FFF1B8EA6 for <ietf@ietf.org>; Thu,  8 Aug 2013 15:22:14 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: procedural question with remote participation
In-Reply-To: <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com> <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 08 Aug 2013 15:22:14 -0400
Message-ID: <6621.1375989734@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 19:23:50 -0000

--=-=-=


John C Klensin <john-ietf@jck.com> wrote:
    > In those cases, as a remote participant, I need all the help I
    > can get.  I'd rather than no one ever use a slide that has
    > information on it in a type size that would be smaller than 20
    > pt on A4 paper.  But 14 pt and even 12 pt happen, especially if
    > the slides were prepared with a tool that quietly shrinks things
    > to fit in the image area.  If I'm in the room and such a slide
    > is projected, I can walk to the front to see if if I'm not
    > already in front and can't deduce what I need from context.  If
    > I'm remote and have such a slide in advance, I can zoom in on it
    > or otherwise get to the information I need (assuming high enough
    > resolution).  If I'm remote and reading the slide off video,
    > especially low resolution video, is hopeless.

Also, I can't go back to the previous slide if the system is just remote
projection.

Good quality mumble-free audio + pre-distributed slides locally rendered
beats any amount of lag-free video.

I also can go ahead and find out if the speaker is going to cover an
important point, or if I have to bring it *now*.

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



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

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

iQCVAwUBUgPv5IqHRg3pndX9AQKtAQQAoCI3dA+c3CXuIWWySCDSo1OoIcmF8W0b
8SsC3e+bYeGDuzm1PgZiLFlHZ9oWwCK21gX90rDHXrKSfBmpFRmLSVT/Bp2ldyLM
KD9RCW3ORwmfUw1Jy/5v5Iy+2xs4HhPRk5ge5srIQb0xHHKM2f0G/klZy/z5RcTQ
ElidOkUj8NQ=
=Ul1D
-----END PGP SIGNATURE-----
--=-=-=--

From hallam@gmail.com  Thu Aug  8 12:39:58 2013
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 48FE311E820F for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 12:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.51
X-Spam-Level: 
X-Spam-Status: No, score=-2.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 EhvNNsXoHXMe for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 12:39:57 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 928D211E8213 for <ietf@ietf.org>; Thu,  8 Aug 2013 12:39:41 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id en1so972052wid.6 for <ietf@ietf.org>; Thu, 08 Aug 2013 12:39:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ivSaK6nXx5lCW5OOY3t1BKmXJVD3W3isNTlo3iSTAf8=; b=dY3rgTFCbLhqlo5HSo9hvmEHCCblMTy1m05iRBowOZEQWJnuxYJY3LdcY9wKVKSbq8 E+kSw6w3i9F0JuxAA9IjgZPIY8IU+hlk1V66Q9k7QCGvPDKTHWhLFk+6OpYw3+vOPLDI o37ChGFSxfquH2C7s5RqKVBMmtE3tEoxXzJwMi478r5eQ4VWv5FDBu5ZG4RrmwaIoEdt 4cyiH94TMdkwVNcagVjMNTWFC3Q/BgrkHuK5n+9Fo3UyEsNoEzzIs6BbRrgb439uIPXn uUvq1sgIvVxZGkp+YnNV3X2n6/BVFbHjDhG9uPvuDnCoCAxGVPFT0TpRy6Th3rnXgT4X NdJQ==
MIME-Version: 1.0
X-Received: by 10.194.219.233 with SMTP id pr9mr4325418wjc.8.1375990780672; Thu, 08 Aug 2013 12:39:40 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 12:39:40 -0700 (PDT)
In-Reply-To: <520156A9.3090802@gmail.com>
References: <3724a64039194f79ba538ed5adbb44e5@cam.ac.uk> <37137597-637A-40E6-BEA8-AE89E662904A@hopcount.ca> <520156A9.3090802@gmail.com>
Date: Thu, 8 Aug 2013 15:39:40 -0400
Message-ID: <CAMm+Lwh0v1gKmsu_FaRsSpPDecJY5RdAak8m9aeafGyAu57jnw@mail.gmail.com>
Subject: Re: [iaoc-rps] RPS Accessibility
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1b7e6b2404604e374d1b6
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, 08 Aug 2013 19:39:58 -0000

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

On Tue, Aug 6, 2013 at 4:03 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 8/6/13 11:58 AM, Joe Abley wrote:
> > For what it's worth (not much) I would miss the line at the mic.
> > There are useful conversations that happen within the line that I
> > think we would lose if the mic followed the speaker, and I also think
> > that pipelining the people at the mic promotes more fluid
> > conversation. But these are minor points, and I'm mainly just waxing
> > nostalgic.
>
> I actually think that this is not a small point.  The people in
> line are the people with issues and the ability to hash stuff out
> quickly is pretty nice



They can also negotiate and reorganize each other.

For example, if I am at the mic wanting to raise a new topic  and there is
someone with an issue on the current one they will usually ask if they can
cut in. Another frequent case is when someone raises an issue and someone
actually knows the answer.

That sort of thing can be pretty important when a statement of fact is made
that is wrong, particularly when it is the alleged opinion of someone else.
In Orlando someone asserted X had stated Y would happen which being in the
security area and knowing that Y was idiotic and X was most unlikely to
have said it, I pointed out that the speaker had likely misunderstood. When
I later met up with X they were surprised anyone would think they thought Y
because that would be idiotic.



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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Aug 6, 2013 at 4:03 PM, Melinda Shore <span dir=3D"ltr">&lt=
;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.shore=
@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 8/6/13 11:58 AM, Joe Ab=
ley wrote:<br>
&gt; For what it&#39;s worth (not much) I would miss the line at the mic.<b=
r>
&gt; There are useful conversations that happen within the line that I<br>
&gt; think we would lose if the mic followed the speaker, and I also think<=
br>
&gt; that pipelining the people at the mic promotes more fluid<br>
&gt; conversation. But these are minor points, and I&#39;m mainly just waxi=
ng<br>
&gt; nostalgic.<br>
<br>
</div>I actually think that this is not a small point. =A0The people in<br>
line are the people with issues and the ability to hash stuff out<br>
quickly is pretty nice</blockquote><div><br></div><div><br></div><div>They =
can also negotiate and reorganize each other.</div><div><br></div><div>For =
example, if I am at the mic wanting to raise a new topic =A0and there is so=
meone with an issue on the current one they will usually ask if they can cu=
t in. Another frequent case is when someone raises an issue and someone act=
ually knows the answer.=A0</div>
<div><br></div><div>That sort of thing can be pretty important when a state=
ment of fact is made that is wrong, particularly when it is the alleged opi=
nion of someone else. In Orlando someone asserted X had stated Y would happ=
en which being in the security area and knowing that Y was idiotic and X wa=
s most unlikely to have said it, I pointed out that the speaker had likely =
misunderstood. When I later met up with X they were surprised anyone would =
think they thought Y because that would be idiotic.</div>
</div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http:=
//hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c1b7e6b2404604e374d1b6--

From cgriffiths@gmail.com  Thu Aug  8 12:47:18 2013
Return-Path: <cgriffiths@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E4F21F9C46 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 12:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level: 
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[AWL=-0.349, 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 iwu+-+9kNEpU for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 12:47:18 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1619D21F9E7C for <ietf@ietf.org>; Thu,  8 Aug 2013 12:47:18 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id k5so2638856iea.18 for <ietf@ietf.org>; Thu, 08 Aug 2013 12:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=50pOuEX9aF5ufqP0WRlaOWkd8Qi8A2ra0tqM+dr9QbY=; b=G4sRuSikK5BStrrfYJhHCQcPRBTJl7PtSdNcYktL5y+d7Roh+6UgJ6EivrgMDD+3Zv QtKw3LhwysyaYHkzrpzHbLb0fM7dtVz9d7ThtSXk+I+QzbVt1V4IpRtlAbYw0ItyUf1I hbzPls+eIVZZh+OPZUlJToM8+pGCMCJjGhMfVxHst9SsdhIDn79GstNPC6a/BlDREsVT zREyzZwxwfnkMhxx4ffwEY/dgEUxSwuBl27PFy2xR8l2GuRfvIVT5kyl9ExS2RH0KOh/ 4vfvUsfhGvpyLdbujI0EyQMWMILKc55PiaqxKPGOA2mMEE/L0ESqR65pkDC8EVWUPvRf Yzeg==
X-Received: by 10.50.25.39 with SMTP id z7mr256414igf.59.1375991237706; Thu, 08 Aug 2013 12:47:17 -0700 (PDT)
Received: from [10.38.82.243] (mobile-198-228-199-132.mycingular.net. [198.228.199.132]) by mx.google.com with ESMTPSA id jg5sm8641366igb.0.2013.08.08.12.47.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 12:47:16 -0700 (PDT)
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com>
X-Mailer: iPhone Mail (10B350)
From: Chris Griffiths <cgriffiths@gmail.com>
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
Date: Thu, 8 Aug 2013 15:47:11 -0400
To: "t.p." <daedulus@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, 08 Aug 2013 19:47:19 -0000

On Aug 8, 2013, at 5:42 AM, t.p. <daedulus@btconnect.com> wrote:

> Chris
>=20
> I would not like to see the Trust Agreement change to accommodate issues
> one or two - I think that the agreement got that one right.

Thank you for this feedback.


> Three is different.  The Trust ought to be able to dispose of rights
> that are not needed, never will be and are costing money.  But how can
> that be expressed without giving carte blanche to dispose of everything,
> for whatever purposes?  We need a proposal as to how that line would be
> drawn - I do not have any sound ideas on this.

I think providing thoughtful language around seeking community feedback and r=
equiring time frames to dispose of items would be needed in this case.

> Can you indicate what annual or one-off costs we are talking about?  The
> domain names I have dealt with have been cheap enough not to be
> concerned about, once I found the best way to deal with them, although I
> understand that the IETF is operating in a different realm and so may
> have costs of a different magnitude.

I agree some domains are not very expensive, however trademarks require lega=
l work for registering and filing for them.  While not huge numbers, we want=
 to raise the issue that keeping these items requires overhead and expense t=
hat seems to not be warranted in some cases, and we want to discussed and ge=
t feedback on if keeping these and paying for them makes sense.

Thanks


> Tom Petch
>=20
> ----- Original Message -----
> From: "Chris Griffiths" <cgriffiths@gmail.com>
> To: <ietf@ietf.org>
> Sent: Saturday, August 03, 2013 7:48 AM
>=20
> IETF Community,
>=20
> The IETF Trust Trustees would like feedback from the community on
> several issues:
> - We have received requests that we cannot accommodate and have
> consulted legal counsel to review our options
> - The trust agreement does not allow the trustees to effectively manage
> some trust assets
>=20
> The Trust was created in December 2005 by the Internet Society and the
> Corporation for National Research Initiatives (CNRI) for the purpose of
> "the advancement of education and public interest by acquiring, holding,
> maintaining and licensing certain existing and future intellectual
> property and other property used in connection with the Internet
> standards process and its administration, for the advancement of the
> science and technology associated with the Internet and related
> technology."
> <http://trustee.ietf.org/docs/IETF-Trust-Agreement-Executed-12-15-05.pdf
>=20
> Issue 1
>=20
> We have recently been asked permission to republish the TAO with a
> creative commons license, but according to counsel, the current trust
> agreement does not give the trustees the rights to do this.
>=20
> - Without specific language being added to the trust agreement, we
> cannot grant these types of requests.
> - The current open request for a creative commons license from 6/18/2013
> cannot be completed.
>=20
> Issue 2
>=20
> We cannot currently accept physical assets like hardware donations into
> the trust.  Once accepted into the trust, we would be unable to dispose
> of these items in the future if they are identified as no longer being
> needed.
>=20
> - This removes flexibility in managing assets in the trust, and we
> currently use alternative methods of accepting donations outside of the
> trust.
>=20
> Issue 3
>=20
> Once a domain name or trademark is registered by the trust, it cannot be
> abandoned even if it is no longer needed.
>=20
> - We must maintain these in perpetuity based on legal counsel review of
> the current language
>=20
> You can also find the latest trust report that covers these items and
> was presented at the IETF 87 plenary here:
> http://www.ietf.org/proceedings/87/slides/slides-87-iesg-opsplenary-4
>=20
> Thank you and we look forward to getting your feedback.
>=20
> Chris Griffiths
> Chair, IETF Trust
>=20
>=20

From cabo@tzi.org  Thu Aug  8 12:58:55 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360C611E8225; Thu,  8 Aug 2013 12:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9gCERiLa0Jry; Thu,  8 Aug 2013 12:58:49 -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 CB6C411E822F; Thu,  8 Aug 2013 12:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r78JwJrM009599; Thu, 8 Aug 2013 21:58:19 +0200 (CEST)
Received: from [192.168.217.105] (p5489221B.dip0.t-ipconnect.de [84.137.34.27]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 86A8C152; Thu,  8 Aug 2013 21:58:18 +0200 (CEST)
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
Date: Thu, 8 Aug 2013 21:58:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-bormann-cbor-04.all@tools.ietf.org, gen-art@ietf.org, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 19:58:55 -0000

On Jul 30, 2013, at 09:05, Martin Thomson <martin.thomson@gmail.com> =
wrote:

> What would cause this to be tragic, is if publication of this were
> used to prevent other work in this area from subsequently being
> published.

Indeed.

As Paul and I have repeatedly said, CBOR is not trying to be the final, =
definitive, binary object representation for all purposes.  It was =
written to some specific objectives, clearly stated in the document.  It =
is being proposed for standards-track because specific ongoing work that =
works well with these objectives will benefit greatly from being able to =
reference a common specification.  If the objectives for other work are =
different, that work may benefit from using a different format, existing =
or newly designed.

We had some offline discussion of what can be done to make this more =
apparent from the document, and decided to start at the most visible =
part, the abstract.

In -04, the abstract says:

   The Concise Binary Object Representation (CBOR) is a data format
   whose design goals include the possibility of extremely small code
   size, fairly small message size, and extensibility without the need
   for version negotiation.  These design goals make it different from
   earlier binary serializations such as ASN.1 and MessagePack.

Now this seemed fairly clear to the authors, but without context it =
might be read as trying to be the final, end-all format because it only =
talks about earlier formats.
We propose to fix this (at the danger of being slightly tautological) by =
making it clear other formats will be created in the future:

   The Concise Binary Object Representation (CBOR) is a data format
   whose design goals include the possibility of extremely small code
   size, fairly small message size, and extensibility without the need
   for version negotiation.  These design goals make it different from
   earlier binary serializations such as ASN.1 and MessagePack, or other
   binary serializations that may be created in the future.

Serialization/encoding of data structures for transmission continues to =
be an exciting (if sometimes arcane) subject of computer science and its =
long history will not end with CBOR.

(CC to ietf@ietf.org because some discussion there appears to be =
related.)

Gr=FC=DFe, Carsten


From brian.e.carpenter@gmail.com  Thu Aug  8 13:46:58 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 435BF11E8223 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 13:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.511
X-Spam-Level: 
X-Spam-Status: No, score=-102.511 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SkM2cUHCo0E9 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 13:46:57 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 20EFB11E8136 for <ietf@ietf.org>; Thu,  8 Aug 2013 13:46:55 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id kq13so4007164pab.25 for <ietf@ietf.org>; Thu, 08 Aug 2013 13:46: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=RdQjf12l5kZ1lo339kyjsE8CDXy0Wuq6YwqzGRCC+ys=; b=VSEU05liPh31gvcoAgwxfIFMY8GoKXmMN2NE22I8ZZpt8fwF0OZVq7qqy8fbnugzwJ rN/Nlasogl7JOIxRbzssriRZvRodogh6F6tUQnh3MMbYBdL63P6We4PmHgjAk8Rwfnq2 ftlXfNYgElwEjLfnvLxvF7JG0gL6oTV1SZKpfGuR8IJXWb9KN1IZbc5L5qwA5Y/ykmLG 4sv+K/8bQqZWaPNH0/r4jcfKQT8uXptTvS6sedGWeLP8EhYlzYZs1AGqUQIN41eho6GU vR7JMRUGBP8gTwgNEIYzlvOam4KHSyzXR/y3CvjHbL2iuuLCCGWmreNnBxhJwsO31AAB +MuA==
X-Received: by 10.66.155.102 with SMTP id vv6mr8082483pab.89.1375994814756; Thu, 08 Aug 2013 13:46:54 -0700 (PDT)
Received: from [192.168.178.20] (110.200.69.111.dynamic.snap.net.nz. [111.69.200.110]) by mx.google.com with ESMTPSA id fk4sm18339027pab.23.2013.08.08.13.46.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 13:46:53 -0700 (PDT)
Message-ID: <520403B1.4060607@gmail.com>
Date: Fri, 09 Aug 2013 08:46:41 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Chris Griffiths <cgriffiths@gmail.com>
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>	<02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com>
In-Reply-To: <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 20:46:58 -0000

I've been doing some more thinking about this, and I have received
quite a bit of private feedback about my previous comments, ranging
from "don't be so picky, let these guys do their thankless job" to
"please be more picky, this is the thin end of the wedge."

So - this isn't really about being picky, except that a legal agreement
more or less forces us to be picky. Also, I appreciate as much as anybody
that the Trustees are doing a thankless job for the benefit of the
community. But if we look at the three issues together, we have to
also consider *why* the Trust was created in the first place. My summary:
it was created to ensure that the intellectual property important for the
openness of Internet standards could never be alienated or altered
except for the benefit of the community.

I can understand why, in certain circumstances, the community might
agree that some physical property, such as a worn-out pencil sharpener,
should be disposed of, or that a specific piece of intellectual property
might be agreed by the community to no longer important and therefore
could be released by the Trust. The first case is pretty easy and I think
we *could* give the Trustees the authority to dispose of useless
physical property. Intellectual property is much harder, because who
is to judge what's important?

We might reach consensus that it's OK to release change control over
the Tao (although I'm not sure I agree with that - what's so hard about
keeping it under an RFC-like license?). We probably wouldn't reach
consensus to release change control over RFC 791. But who would care
to write down legally sound text drawing the line between those two
extremes?

A couple more comments in line...

On 09/08/2013 07:47, Chris Griffiths wrote:
> On Aug 8, 2013, at 5:42 AM, t.p. <daedulus@btconnect.com> wrote:
> 
>> Chris
>>
>> I would not like to see the Trust Agreement change to accommodate issues
>> one or two - I think that the agreement got that one right.

As I said, if the Trust has a worn-out piece of equipment, they should
be able to dispose of it. But this dilemma can be avoided by not
acquiring equipment at all.

> 
> Thank you for this feedback.
> 
> 
>> Three is different.  The Trust ought to be able to dispose of rights
>> that are not needed, never will be and are costing money.  But how can
>> that be expressed without giving carte blanche to dispose of everything,
>> for whatever purposes?  We need a proposal as to how that line would be
>> drawn - I do not have any sound ideas on this.
> 
> I think providing thoughtful language around seeking community feedback and requiring time frames to dispose of items would be needed in this case.

I note that the Trust Agreement does not explicitly recognise that the
Trustees should follow BCP 101, including aspects such as:

 "To ensure that the IASA is run in a transparent and accountable manner."

 "the IAOC and IAD
  will ensure that guidelines are developed for regular operational
  decision making.  Where appropriate, these guidelines should be
  developed with public input.  In all cases, they must be made public"

If we're going to add something about community feedback to the Trust Agreement
it should probably be more general rather than just for the specific
matter of asset disposal. It's always been understood that the transparency
requirement for the IAOC also applies to the Trust, but to my surprise we
never wrote it down.

>> Can you indicate what annual or one-off costs we are talking about?  The
>> domain names I have dealt with have been cheap enough not to be
>> concerned about, once I found the best way to deal with them, although I
>> understand that the IETF is operating in a different realm and so may
>> have costs of a different magnitude.
> 
> I agree some domains are not very expensive, however trademarks require legal work for registering and filing for them.  While not huge numbers, we want to raise the issue that keeping these items requires overhead and expense that seems to not be warranted in some cases, and we want to discussed and get feedback on if keeping these and paying for them makes sense.

There's also the issue that (as I understand it) specific marks like "IETF
Secretariat" may be easier to defend than a more generic mark like plain "IETF".
IANAL.

   Brian

> Thanks
> 
> 
>> Tom Petch
>>
>> ----- Original Message -----
>> From: "Chris Griffiths" <cgriffiths@gmail.com>
>> To: <ietf@ietf.org>
>> Sent: Saturday, August 03, 2013 7:48 AM
>>
>> IETF Community,
>>
>> The IETF Trust Trustees would like feedback from the community on
>> several issues:
>> - We have received requests that we cannot accommodate and have
>> consulted legal counsel to review our options
>> - The trust agreement does not allow the trustees to effectively manage
>> some trust assets
>>
>> The Trust was created in December 2005 by the Internet Society and the
>> Corporation for National Research Initiatives (CNRI) for the purpose of
>> "the advancement of education and public interest by acquiring, holding,
>> maintaining and licensing certain existing and future intellectual
>> property and other property used in connection with the Internet
>> standards process and its administration, for the advancement of the
>> science and technology associated with the Internet and related
>> technology."
>> <http://trustee.ietf.org/docs/IETF-Trust-Agreement-Executed-12-15-05.pdf
>>
>> Issue 1
>>
>> We have recently been asked permission to republish the TAO with a
>> creative commons license, but according to counsel, the current trust
>> agreement does not give the trustees the rights to do this.
>>
>> - Without specific language being added to the trust agreement, we
>> cannot grant these types of requests.
>> - The current open request for a creative commons license from 6/18/2013
>> cannot be completed.
>>
>> Issue 2
>>
>> We cannot currently accept physical assets like hardware donations into
>> the trust.  Once accepted into the trust, we would be unable to dispose
>> of these items in the future if they are identified as no longer being
>> needed.
>>
>> - This removes flexibility in managing assets in the trust, and we
>> currently use alternative methods of accepting donations outside of the
>> trust.
>>
>> Issue 3
>>
>> Once a domain name or trademark is registered by the trust, it cannot be
>> abandoned even if it is no longer needed.
>>
>> - We must maintain these in perpetuity based on legal counsel review of
>> the current language
>>
>> You can also find the latest trust report that covers these items and
>> was presented at the IETF 87 plenary here:
>> http://www.ietf.org/proceedings/87/slides/slides-87-iesg-opsplenary-4
>>
>> Thank you and we look forward to getting your feedback.
>>
>> Chris Griffiths
>> Chair, IETF Trust
>>
>>
> 

From huitema@microsoft.com  Thu Aug  8 13:53:58 2013
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC2FC11E821E for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 13:53:44 -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 VxYfvq-71LTu for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 13:53:23 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0209.outbound.protection.outlook.com [207.46.163.209]) by ietfa.amsl.com (Postfix) with ESMTP id 94DB511E8228 for <ietf@ietf.org>; Thu,  8 Aug 2013 13:53:23 -0700 (PDT)
Received: from BLUPR03CA034.namprd03.prod.outlook.com (10.141.30.27) by BLUPR03MB199.namprd03.prod.outlook.com (10.255.212.150) with Microsoft SMTP Server (TLS) id 15.0.731.16; Thu, 8 Aug 2013 20:53:16 +0000
Received: from BY2FFO11FD024.protection.gbl (2a01:111:f400:7c0c::26) by BLUPR03CA034.outlook.office365.com (2a01:111:e400:879::27) with Microsoft SMTP Server (TLS) id 15.0.731.16 via Frontend Transport; Thu, 8 Aug 2013 20:53:16 +0000
Received: from mail.microsoft.com (131.107.125.37) by BY2FFO11FD024.mail.protection.outlook.com (10.1.15.213) with Microsoft SMTP Server (TLS) id 15.0.745.15 via Frontend Transport; Thu, 8 Aug 2013 20:53:16 +0000
Received: from TK5EX14MBXC273.redmond.corp.microsoft.com ([169.254.1.38]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0136.001; Thu, 8 Aug 2013 20:52:40 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: RE: Faraday cages...
Thread-Topic: Faraday cages...
Thread-Index: AQHOk4Eo+PwNVowznkC6OlPq7r/DAJmJ7pgAgAAQWYCAAAEnAIAAMvEAgAAG+YCAADfpwIABJeeAgAAPrYCAACGbgA==
Date: Thu, 8 Aug 2013 20:52:40 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.73]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(199002)(189002)(11905935001)(51704005)(77096001)(63696002)(15202345003)(53806001)(19580385001)(76482001)(56816003)(76796001)(80022001)(74662001)(54356001)(65816001)(76786001)(74366001)(54316002)(47446002)(81686001)(19580395003)(46102001)(23726002)(47776003)(59766001)(79102001)(33656001)(81542001)(49866001)(74706001)(20776003)(46406003)(50466002)(83072001)(69226001)(77982001)(6806004)(83322001)(81342001)(16406001)(74876001)(74502001)(4396001)(56776001)(31966008)(44976005)(80976001)(50986001)(47736001)(66066001)(51856001)(47976001)(55846006); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR03MB199; H:mail.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 093290AD39
X-OriginatorOrg: DuplicateDomain-a84fc36a-4ed7-4e57-ab1c-3e967bcbad48.microsoft.com
X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 131.107.125.37
X-MS-Exchange-CrossPremises-AuthSource: BY2FFO11FD024.protection.gbl
X-MS-Exchange-CrossPremises-AuthAs: Anonymous
X-MS-Exchange-CrossPremises-AVStamp-Service: 1.0
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-Antispam-ScanContext: DIR:Originating; SFV:NSPM; SKIP:0; 
X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent
X-OrganizationHeadersPreserved: BLUPR03MB199.namprd03.prod.outlook.com
Cc: Ole Jacobsen <ole@cisco.com>, John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 20:53:59 -0000

>> Why bother with RFID tags, or badges? Simply register with your cell pho=
ne. We can then scan your Wi-Fi and Blue-Tooth signals when you approach th=
e mic.
>>=20
>> -- Christian Huitema
>>=20
>> 'Simply'
>> =20
>> What is this simple technology of which you speak? I find that the best =
we can do with electronic systems is about 99% and that takes a huge amount=
 of effort. I have a whole drawerful of bluetooth headsets and thats where =
they will stay because none of them works well enough to be useful.
>
> I am fairly sure Christian was being ironic.

:-)

I was. On the other hand, there are systems out there that will, for exampl=
e, track customers as they move in a shop. They do that by listening to the=
 Bluetooth radios. They definitely do not requests the customers to install=
 an application or pair their devices. An extract form a research paper on =
the subject (http://www.gim-international.com/issues/articles/id1443-Blueto=
oth_Tracking.html) asserts that "Bluetooth tracking on the basis of MAC add=
resses does not violate privacy law. In fact, it simply makes use of a gene=
ral Bluetooth function: scanning for nearby devices. Everyone is free to us=
e this function, for instance when turning on a mobile phone in a public pl=
ace." So it must be just fine.

-- Christian Huitema





From paul.hoffman@vpnc.org  Thu Aug  8 14:04:27 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFA6C11E8228 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y3eRun-tC2Iy for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:04:27 -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 40ABA11E8221 for <ietf@ietf.org>; Thu,  8 Aug 2013 14:04:27 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r78L4OpB010799 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 8 Aug 2013 14:04:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <520403B1.4060607@gmail.com>
Date: Thu, 8 Aug 2013 14:04:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>	<02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf <ietf@ietf.org>, Chris Griffiths <cgriffiths@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, 08 Aug 2013 21:04:27 -0000

On Aug 8, 2013, at 1:46 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> We might reach consensus that it's OK to release change control over
> the Tao (although I'm not sure I agree with that - what's so hard =
about
> keeping it under an RFC-like license?).

Nothing is "hard" about it. The question is whether granting a different =
license will help the goals of the Tao more than the current license. =
Many people (including me, the current editor) think that a =
lighter-weight license would get the Tao read by more people.

--Paul Hoffman=

From dougb@dougbarton.us  Thu Aug  8 14:09:39 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1526321E805F for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 gsqlJE-xpvhe for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:09:29 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id B226E11E8221 for <ietf@ietf.org>; Thu,  8 Aug 2013 14:09:29 -0700 (PDT)
Received: from [192.168.0.23] (home [12.207.105.210]) by dougbarton.us (Postfix) with ESMTPSA id 3283622B1A for <ietf@ietf.org>; Thu,  8 Aug 2013 21:09:29 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1375996169; bh=Jb3BiNTjBJOO6dShtQ9HCewymF4M6kxRjjB7AdUNvg8=; h=Date:From:To:Subject:References:In-Reply-To; b=c/JaKaCQz3rKJKaKIwwXozhun4O67NLsob6n2p7vTe4XczU+K0J1UTWheA2dDTjD3 Godyvz+39zA8s7I8aa/aWjew0X9n+pbTkxh68CU03uAmcy9wVE/5P4cJHqaR7ZljBn 28aQUjmimaZXMTB3SaZnXqKez5AbUwE//Iv52hPI=
Message-ID: <52040908.6010008@dougbarton.us>
Date: Thu, 08 Aug 2013 14:09:28 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>	<02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org>
In-Reply-To: <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 21:09:39 -0000

On 08/08/2013 02:04 PM, Paul Hoffman wrote:
> On Aug 8, 2013, at 1:46 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
>> We might reach consensus that it's OK to release change control over
>> the Tao (although I'm not sure I agree with that - what's so hard about
>> keeping it under an RFC-like license?).
>
> Nothing is "hard" about it. The question is whether granting a different license will help the goals of the Tao more than the current license. Many people (including me, the current editor) think that a lighter-weight license would get the Tao read by more people.

Can you elaborate on why the license makes a difference?


From paul.hoffman@vpnc.org  Thu Aug  8 14:17:27 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1668811E822C for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WpHa6XUwiQGS for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:17:26 -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 009B421F9A72 for <ietf@ietf.org>; Thu,  8 Aug 2013 14:17:21 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r78LHIqT011308 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 8 Aug 2013 14:17:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52040908.6010008@dougbarton.us>
Date: Thu, 8 Aug 2013 14:17:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>	<02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org> <52040908.6010008@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 21:17:27 -0000

On Aug 8, 2013, at 2:09 PM, Doug Barton <dougb@dougbarton.us> wrote:

> On 08/08/2013 02:04 PM, Paul Hoffman wrote:
>> On Aug 8, 2013, at 1:46 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>=20
>>> We might reach consensus that it's OK to release change control over
>>> the Tao (although I'm not sure I agree with that - what's so hard =
about
>>> keeping it under an RFC-like license?).
>>=20
>> Nothing is "hard" about it. The question is whether granting a =
different license will help the goals of the Tao more than the current =
license. Many people (including me, the current editor) think that a =
lighter-weight license would get the Tao read by more people.
>=20
> Can you elaborate on why the license makes a difference?

We have been told it would make it easier for people to make and =
distribute translations.

--Paul Hoffman=

From cntreras@gmail.com  Thu Aug  8 14:21:50 2013
Return-Path: <cntreras@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A72821F9B9F for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:21:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=-0.698, 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 BWO04OHb6CDH for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:21:47 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 42C8421F9A72 for <ietf@ietf.org>; Thu,  8 Aug 2013 14:21:47 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id s9so2858376iec.34 for <ietf@ietf.org>; Thu, 08 Aug 2013 14:21:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=A1cc1LnECKcLSFbnA/SvPBAszdpC/gxcjOxlZKolxVg=; b=dhIA2YLTBK5G+/pDvZxyQsGRX83nxe/q4lK27t3s4cro8yDWa5uBq1dq5fXNU5mlJb YjY+OG/KRT+Pt7sWeM0VyfKhDiohXGT2KA989Z4fXus6s6O7b4QWYJ0eHeoDt8/uYtq1 Qi5Kf8hqKfpKoq/figCgtLVXMkwPNwd9Hv4UoaOGGzj8xgITHG5NiNhIrtV0W5KyIzcz lzEXSZ4WHytjNYKNbz61ytgLmOttJMGbDNcj0zPH1vUfxR1g4bR6pOTHJxenpvFWzkQT Vuth0j4tzL0u+s+aWfsjFCm8aeFvD8gcc8urSabj6gOhREDIx6MlnETQV0w9/h9E6XbE drLQ==
X-Received: by 10.42.113.8 with SMTP id a8mr3026979icq.71.1375996906895; Thu, 08 Aug 2013 14:21:46 -0700 (PDT)
Received: from [10.35.247.3] (mobile-198-228-204-210.mycingular.net. [198.228.204.210]) by mx.google.com with ESMTPSA id ri10sm9126426igc.1.2013.08.08.14.21.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 08 Aug 2013 14:21:45 -0700 (PDT)
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org> <52040908.6010008@dougbarton.us> <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com>
X-Mailer: iPhone Mail (10B350)
From: Jorge Contreras <cntreras@gmail.com>
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
Date: Thu, 8 Aug 2013 17:21:43 -0400
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 21:21:50 -0000

>>=20
>> Can you elaborate on why the license makes a difference?
>=20
> We have been told it would make it easier for people to make and distribut=
e translations.
>=20
> --Paul Hoffman

Actually, verbatim translations are already allowed under the existing IETF d=
ocument license. It's other modifications that are not allowed under IETF, b=
ut which CC-BY would permit.=20=

From johnl@iecc.com  Thu Aug  8 14:31:17 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB6811E822E for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.005
X-Spam-Level: 
X-Spam-Status: No, score=-105.005 tagged_above=-999 required=5 tests=[AWL=-4.820, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TCaib8sGvhw for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:31:13 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0B8E511E8223 for <ietf@ietf.org>; Thu,  8 Aug 2013 14:31:12 -0700 (PDT)
Received: (qmail 38174 invoked from network); 8 Aug 2013 21:31:07 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Aug 2013 21:31: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; s=52040e1b.xn--3zv.k1308; i=johnl@user.iecc.com; bh=3jFUKoZOYwu3C2d4ioepsG+tlT8ywBb4qH7xX8DpKD8=; b=kzXwqbayXbPuaMTgEdFOGBpoM6ZGLdGQC3gPECRQQdy5hhDi7IMBgb2SZ1xpHXSurU/Si2k8MAuWgC6b3JoebT1guvt2HxkF7TUarMcH5L95DQQnpKOBuLD4h4bW8uHOTTdgjadm9jU0NvxGVER25UO5+V2E7rfkvviv/E+TuU2AV2o4I0VNBDqbDkXpzdjuxavH6hQnxFxbu632WUtj8ORPApRC8T/xkD+ddFgt6DzZQ45I/iw2cW3zh2YjVhZo
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52040e1b.xn--3zv.k1308; olt=johnl@user.iecc.com; bh=3jFUKoZOYwu3C2d4ioepsG+tlT8ywBb4qH7xX8DpKD8=; b=AbdDoWaZwEGKy1NV+YWP6ewC6eRH5TAORQ9tO66QlZBW0wCqr6oaOhxnKyNKDfZaG8tCtuEJpVDY/hmSckjWDTU9qdVjCHBECSjac9HGdQNgLoBlCZiWAJnqtYIL0+3+ZaGpvxYWbM1CqTsi6j0U0L7cDwdi5CuZELLk28Y5Ez5ZFTz/BrgfoUoGYF+cOe1tWJEzIskzjbGsBBWXVqzJa0Dp7KrLScoSpAFyMx9pN1R8Bqu/JwdAnoLWc9z5Xo3/
Date: 8 Aug 2013 21:30:45 -0000
Message-ID: <20130808213045.60763.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
In-Reply-To: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: cgriffiths@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, 08 Aug 2013 21:31:17 -0000

>We have recently been asked permission to republish the TAO with a creative commons
>license, but according to counsel, the current trust agreement does not give the
>trustees the rights to do this.
>
>- Without specific language being added to the trust agreement, we cannot grant these
>types of requests.  

I'm looking at section 9.5 of the trust agreement, and I'm looking at
the CC Attribution-NoDerivs 3.0 license, and I don't see what's in the
CC license that conflicts with the trust agreement.  The TA says that
derivatives belong to the IETF, the CC license says no derivatives, the
TA says that the goodwill belongs to the IETF, the CC license says no
disparaging, which isn't the same thing but leans in the same direction.

If they want a different CC license, that's easy, the answer is no.

http://creativecommons.org/licenses/by-nd/3.0/legalcode

>Once a domain name or trademark is registered by the trust, it cannot be abandoned
>even if it is no longer needed.  
>
>- We must maintain these in perpetuity based on legal counsel review of the current language

I have more sympathy for this one.  Although the renewal fee for a
domain name is usually trivial, what happens if some third party files
a UDRP challenge to or a lawsuit about a domain name that the IETF is
no longer using?  Do they have to run up legal bills responding to and
fighting it?

For trademarks, the renewal fee is $400 payable 5 years and 10 years
after registration, and every 10 years after that.  But along with the
renewal fee, the registrant has to send in a sworn statement saying
that the mark is still in use in commerce, listing the goods and
services on which it's used, and if requested providing samples.  If
the IETF isn't actually using the mark, what is the trust supposed to
do?  Furthermore, unlike patent or copyrights, a trademark owner has
to police unauthorized use and challenge it legally, or risk losing
the trademark to what's known as genericide.  This is a lot of work
for a trademark you want, and it's absurd for one you don't.

My suggestion would be that the abandonment process take a year,
requiring four quarterly announcements and solicitation of comments to
a public venue such as the IETF general list.  After the year,
considering all responses received, if the trustees believe that there
is consensus to abandon, they do so.

If people are concerned that the trustees would do something silly,
the solution is to pick better trustees, not to make more complex
rules.

R's,
John

From paul.hoffman@vpnc.org  Thu Aug  8 14:49:53 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97CCC11E80FA for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:49:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RmQ3qUX0xGE5 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 14:49:52 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8030711E8230 for <ietf@ietf.org>; Thu,  8 Aug 2013 14:49:52 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r78LnlBx012190 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 8 Aug 2013 14:49:47 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com>
Date: Thu, 8 Aug 2013 14:49:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E786C85-65A8-4843-9763-056B0A679D72@vpnc.org>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org> <52040908.6010008@dougbarton.us> <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org> <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com>
To: Jorge Contreras <cntreras@gmail.com>
X-Mailer: Apple Mail (2.1508)
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, 08 Aug 2013 21:49:53 -0000

On Aug 8, 2013, at 2:21 PM, Jorge Contreras <cntreras@gmail.com> wrote:

> Actually, verbatim translations are already allowed under the existing =
IETF document license. It's other modifications that are not allowed =
under IETF, but which CC-BY would permit.=20

That sounds right. Someone might want to add commentary (even in =
English) to the Tao, such as to discuss local participants, diversity, =
and so on.

--Paul Hoffman=

From ynir@checkpoint.com  Thu Aug  8 15:01:18 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FFD121F9BBD for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 15:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.52
X-Spam-Level: 
X-Spam-Status: No, score=-10.52 tagged_above=-999 required=5 tests=[AWL=0.079,  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 DpWaLWgXlElt for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 15:01:11 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3FE9D11E813F for <ietf@ietf.org>; Thu,  8 Aug 2013 15:00:17 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r78LxV0s029164; Fri, 9 Aug 2013 00:59:31 +0300
X-CheckPoint: {520414C3-E-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Fri, 9 Aug 2013 00:59:31 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Jorge Contreras <cntreras@gmail.com>
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
Thread-Topic: Community Feedback:  IETF Trust Agreement Issues
Thread-Index: AQHOkDLVPcfQ5lssCES7VP4uTB0ygZmLF1hTgAB2HICAABCggIAABPKAgAABbACAAAIwAIAAATyAgAAKjYA=
Date: Thu, 8 Aug 2013 21:59:30 +0000
Message-ID: <89F22F85-B3F1-4A8F-8F09-D32583BEAC02@checkpoint.com>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org> <52040908.6010008@dougbarton.us> <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org> <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com>
In-Reply-To: <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.237]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 118aaeda971af41c4bf066b9350b4b0cd52aafb59b
Content-Type: text/plain; charset="us-ascii"
Content-ID: <48F1B6DFEF2DEB47BA5447CACF223361@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Paul Hoffman <paul.hoffman@vpnc.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, 08 Aug 2013 22:01:18 -0000

On Aug 9, 2013, at 12:21 AM, Jorge Contreras <cntreras@gmail.com> wrote:

>=20
>>>=20
>>> Can you elaborate on why the license makes a difference?
>>=20
>> We have been told it would make it easier for people to make and distrib=
ute translations.
>>=20
>> --Paul Hoffman
>=20
> Actually, verbatim translations are already allowed under the existing IE=
TF document license. It's other modifications that are not allowed under IE=
TF, but which CC-BY would permit.

Interesting. What does "verbatim translation" mean?  Word-for-word? There i=
s a reason why searching for "google translate funny" yields 63,000 results=
. How much would I be allowed to paraphrase and yet keep within the license=
?

Yoav


From dougb@dougbarton.us  Thu Aug  8 15:33:47 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24CA511E8230 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 15:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAqO8EGd+7TG for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 15:33:44 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4C611E8161 for <ietf@ietf.org>; Thu,  8 Aug 2013 15:33:25 -0700 (PDT)
Received: from [192.168.0.23] (home [12.207.105.210]) by dougbarton.us (Postfix) with ESMTPSA id 1AB5B22B30; Thu,  8 Aug 2013 22:33:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1376001202; bh=W+NMKzngqaIQGGGDsyh4GX07OPu7thHnGJfErKwTNyM=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=hrN2maBgap0xx5e+tgSsjIQxHZ3GqhwSRvE+RJc1pnkSaviu6bSUhraRDjPN/zE7j r8lAwJzmKkjwBIdzmcCG8Y14yaHh9otJoIGRragzuvyvBGwsWTwZo6MQA6vo0hF1PS KxUuMXXbm1wdWxtq5cDcNpMYZeBNBq6YVTLcNwXo=
Message-ID: <52041CB1.9020502@dougbarton.us>
Date: Thu, 08 Aug 2013 15:33:21 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org> <52040908.6010008@dougbarton.us> <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org> <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com> <7E786C85-65A8-4843-9763-056B0A679D72@vpnc.org>
In-Reply-To: <7E786C85-65A8-4843-9763-056B0A679D72@vpnc.org>
X-Enigmail-Version: 1.5.2
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 22:33:47 -0000

On 08/08/2013 02:49 PM, Paul Hoffman wrote:
> On Aug 8, 2013, at 2:21 PM, Jorge Contreras <cntreras@gmail.com> wrote:
>
>> Actually, verbatim translations are already allowed under the existing IETF document license. It's other modifications that are not allowed under IETF, but which CC-BY would permit.
>
> That sounds right. Someone might want to add commentary (even in English) to the Tao, such as to discuss local participants, diversity, and so on.

It's not at all clear to me why the current license would prohibit that, 
or why the CC license would make it easier or better. As long as the 
commentary is clearly separated from the text of the Tao, there is no 
conflict.

What I'm looking for is a clear statement to the effect of, "We cannot 
do X with the current license because ...; and the CC license would make 
that better because ..."

Doug


From johnl@iecc.com  Thu Aug  8 16:20:38 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE6B11E8242 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 16:20:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.051
X-Spam-Level: 
X-Spam-Status: No, score=-106.051 tagged_above=-999 required=5 tests=[AWL=-3.452, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c4TT9IrqY9gj for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 16:20: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 416E011E816E for <ietf@ietf.org>; Thu,  8 Aug 2013 16:20:32 -0700 (PDT)
Received: (qmail 57620 invoked from network); 8 Aug 2013 23:20:22 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 8 Aug 2013 23:20:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520427b6.xn--9vv.k1308; i=johnl@user.iecc.com; bh=kEdxNEbe4k1binKZHZnIK1lGId+Ksjw0+HHtjLOd2gQ=; b=OpOEU7PyUF+kiFAnBOIWJY8b2HryYa5TyPyNoMn+YGkO2WcHhiTseTc9o/YQTeeujBekKBoVAcdsSDbaP8y+iouYxpYRJkrbS7LMF6tzAzIQmhkg63Fx/gazJrsKdmiVs8v3weBsS/5gqSYzclX6bDiY7M1ZsebjK5g/EridqhSS1TmRRsOLHNQroN3VXLByqRWQ55dDjTpGcQHYMeXZXhcV/cllYFx90jKyk25MVimu6ETafTOs+ueZb7OIvWxN
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520427b6.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=kEdxNEbe4k1binKZHZnIK1lGId+Ksjw0+HHtjLOd2gQ=; b=g9u0hkfdr6qjbCtczJrPhf0Z4wqcLzurWyzM0pX9prBV+zxCg7Lwhba1LaGT7ivx0b9aJP4+kc3woah28TpNBshYphuWgM2DSg0XqS2h7SJZ3nIxwYPljgyJ9K4+LbnxuZDIeAQya3YcYG5RElbXLT1AyfY9cif6p2JZVOD53rPZ+eHhcrC8ZsqHI/x//6QZoK8p1TK/yO+kifuFMLQ8r+/ebOzM81bJYwTIETh92MWuswcvw1CVx8jKXb4cbqeh
Date: 8 Aug 2013 23:20:00 -0000
Message-ID: <20130808232000.61327.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
In-Reply-To: <7E786C85-65A8-4843-9763-056B0A679D72@vpnc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paul.hoffman@vpnc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 23:20:38 -0000

>> Actually, verbatim translations are already allowed under the existing IETF
>document license. It's other modifications that are not allowed under IETF, but which
>CC-BY would permit. 
>
>That sounds right. Someone might want to add commentary (even in English) to the Tao,
>such as to discuss local participants, diversity, and so on.

Someone might, or they might rewrite it to say that IETF meetings have
simultaneous translation, and while the IAB is all U.S. greybeards,
the IESG members are chosen to represent the gender and ethnic balance
of the whole world.  Or they might rewrite it to say that the IETF has
corporate members, you have work for one to participate, and all RFCs
are standards.

The CC license says

 You must not distort, mutilate, modify or take other derogatory
 action in relation to the Work which would be prejudicial to the
 Original Author's honor or reputation.

Would those changes be prejudicial to your honor or reputation, or are
they just wrong?  How much are we willing to spend to find out?

It's extremely hard to let just one of the cat's paws out of the bag.
In practice either we have change control or we don't, and I don't see
much sentiment for giving it up to unknown CC users.

On the other hand, if they just want a CC license, it looks to me like
they can use CC BY-ND right now.

R's,
John

From hallam@gmail.com  Thu Aug  8 16:41:46 2013
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 5B9BF21F9D07 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 16:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.515
X-Spam-Level: 
X-Spam-Status: No, score=-2.515 tagged_above=-999 required=5 tests=[AWL=0.084,  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 iFZgYD7Z1NDs for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 16:41:45 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3D421F9D02 for <ietf@ietf.org>; Thu,  8 Aug 2013 16:41:44 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so3090825wes.33 for <ietf@ietf.org>; Thu, 08 Aug 2013 16:41: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=eKzdIOJWfZfWdhS3NufCCTaKsRvh+fGjgzJ5aABXYXg=; b=QjHVp6JtIrVReJXbXwPKc3RYQB/8XuTgeN7D6gtrGlQTzAQHdXKAMYiF9ZEnCIkMzR C5uRFGKChb6Mgrxewz4OBkHlMw+ebYCuG33+RJ99aSoiFuQb15cwE6pGJsOPtwHee34k PDL56pDZ897LncUHYnNLawk9dATUiy5qdDIr9dZA636g6cTJDIW62KLyFXPHYMrtanDp G8kKUoGHZMJEDSDN/OCovxcQpmOiCLWv/gm46cAGvPV3nL+Akb+4+hfd3NGJ2a3M9M2I lHrPsdie3hPu9I9bw5yjwybQ+cM7wXQu8zEmY6yJ1Iu2J/oHo9FZiHG4IN9HmnqjUlYd wREg==
MIME-Version: 1.0
X-Received: by 10.194.85.198 with SMTP id j6mr4706882wjz.51.1376005303438; Thu, 08 Aug 2013 16:41:43 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 16:41:43 -0700 (PDT)
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com>
Date: Thu, 8 Aug 2013 19:41:43 -0400
Message-ID: <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com>
Subject: Re: Faraday cages...
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Christian Huitema <huitema@microsoft.com>
Content-Type: multipart/alternative; boundary=089e0103eea252156c04e3783335
Cc: Ole Jacobsen <ole@cisco.com>, John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Aug 2013 23:41:46 -0000

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

Hmmm didn't a certain large company whose name rhymes with scroogle
recently get whacked with a huge fine for violating privacy in a similar
manner in the EU?

Like you say, must be just fine it says so on the net.


On Thu, Aug 8, 2013 at 4:52 PM, Christian Huitema <huitema@microsoft.com>wrote:

>
> >> Why bother with RFID tags, or badges? Simply register with your cell
> phone. We can then scan your Wi-Fi and Blue-Tooth signals when you approach
> the mic.
> >>
> >> -- Christian Huitema
> >>
> >> 'Simply'
> >>
> >> What is this simple technology of which you speak? I find that the best
> we can do with electronic systems is about 99% and that takes a huge amount
> of effort. I have a whole drawerful of bluetooth headsets and thats where
> they will stay because none of them works well enough to be useful.
> >
> > I am fairly sure Christian was being ironic.
>
> :-)
>
> I was. On the other hand, there are systems out there that will, for
> example, track customers as they move in a shop. They do that by listening
> to the Bluetooth radios. They definitely do not requests the customers to
> install an application or pair their devices. An extract form a research
> paper on the subject (
> http://www.gim-international.com/issues/articles/id1443-Bluetooth_Tracking.html)
> asserts that "Bluetooth tracking on the basis of MAC addresses does not
> violate privacy law. In fact, it simply makes use of a general Bluetooth
> function: scanning for nearby devices. Everyone is free to use this
> function, for instance when turning on a mobile phone in a public place."
> So it must be just fine.
>
> -- Christian Huitema
>
>
>
>
>


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

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

<div dir=3D"ltr">Hmmm didn&#39;t a certain large company whose name rhymes =
with scroogle recently get whacked with a huge fine for violating privacy i=
n a similar manner in the EU?<div><br></div><div>Like you say, must be just=
 fine it says so on the net.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Aug 8, 2013 at 4:52 PM, Christian Huitema <span dir=3D"ltr">&lt;<a href=3D=
"mailto:huitema@microsoft.com" target=3D"_blank">huitema@microsoft.com</a>&=
gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
&gt;&gt; Why bother with RFID tags, or badges? Simply register with your ce=
ll phone. We can then scan your Wi-Fi and Blue-Tooth signals when you appro=
ach the mic.<br>
&gt;&gt;<br>
&gt;&gt; -- Christian Huitema<br>
&gt;&gt;<br>
&gt;&gt; &#39;Simply&#39;<br>
&gt;&gt;<br>
&gt;&gt; What is this simple technology of which you speak? I find that the=
 best we can do with electronic systems is about 99% and that takes a huge =
amount of effort. I have a whole drawerful of bluetooth headsets and thats =
where they will stay because none of them works well enough to be useful.<b=
r>

&gt;<br>
&gt; I am fairly sure Christian was being ironic.<br>
<br>
</div>:-)<br>
<br>
I was. On the other hand, there are systems out there that will, for exampl=
e, track customers as they move in a shop. They do that by listening to the=
 Bluetooth radios. They definitely do not requests the customers to install=
 an application or pair their devices. An extract form a research paper on =
the subject (<a href=3D"http://www.gim-international.com/issues/articles/id=
1443-Bluetooth_Tracking.html" target=3D"_blank">http://www.gim-internationa=
l.com/issues/articles/id1443-Bluetooth_Tracking.html</a>) asserts that &quo=
t;Bluetooth tracking on the basis of MAC addresses does not violate privacy=
 law. In fact, it simply makes use of a general Bluetooth function: scannin=
g for nearby devices. Everyone is free to use this function, for instance w=
hen turning on a mobile phone in a public place.&quot; So it must be just f=
ine.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Christian Huitema<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div>

--089e0103eea252156c04e3783335--

From moore@network-heretics.com  Thu Aug  8 17:23:02 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFA311E816F for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 17:23:02 -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 j-EZ6ioHCk53 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 17:22:57 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id C223321F8F3C for <ietf@ietf.org>; Thu,  8 Aug 2013 17:22:53 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6339A20BB5 for <ietf@ietf.org>; Thu,  8 Aug 2013 20:22:48 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 08 Aug 2013 20:22:48 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=QhgzZRVSq8CqoJA0JpxV2B Ait+8=; b=eTAzVWq1RgvfGUwtbZKiXRcPkBxHGgBFIMe63Wj8tzr9jYz+NvjsXa vV32aG4cV08myK07x9ygyfSrszzwdAktzvxf9AJZDVoZniIngp/q+zBXthvQxBJs 6XxwOUoIUhXNZL/z0Jm7wn/YQjQF1uS4cPyM148pJ+Rp9nAtxlswg=
X-Sasl-enc: /vwvldYra5Zy6inAmoEewy0yNiqGKs/vO9kvXpdzTQy0 1376007768
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id C017CC00E84; Thu,  8 Aug 2013 20:22:47 -0400 (EDT)
Message-ID: <5204364E.7080905@network-heretics.com>
Date: Thu, 08 Aug 2013 20:22:38 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Faraday cages...
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com>
In-Reply-To: <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 00:23:03 -0000

On 08/08/2013 07:41 PM, Phillip Hallam-Baker wrote:
> Hmmm didn't a certain large company whose name rhymes with scroogle 
> recently get whacked with a huge fine for violating privacy in a 
> similar manner in the EU?

The rules are different for large companies with funny names.

Keith


From ggm@algebras.org  Thu Aug  8 17:31:36 2013
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB4221F9D5C for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 17:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.376
X-Spam-Level: 
X-Spam-Status: No, score=-0.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_MUTUALBENEFIT=2, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, 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 Pu8Xm5721aUL for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 17:31:31 -0700 (PDT)
Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC1511E816F for <ietf@ietf.org>; Thu,  8 Aug 2013 17:31:31 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so4087820pbb.10 for <ietf@ietf.org>; Thu, 08 Aug 2013 17:31:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=13hJHJAU7cMTT1K+bupl96Cl0BD4t7XhTInUfGsq854=; b=kFLoCIEhDLu1OvkNHegopYZb457fkr7oZ1PQ33r+HxMBaWMXKZ4f8XP+ZSCtNZcXwM KLhQw5XutSREyyZoAKyTDG3t48/3huQZJPlFjfvDBDgIiWX5AchdAH1KpdtyAOgeGoZp JcVK0HZ33swd4DfGNGi+FljJ3jVouhnfKxwo1QstEF5cmM+e35NZSlBJfJHpYZ+34Glx aH0UvDusUNPoMnYx6gEiKiKHBAfGsVRg8/3Nu4CRchJK3AQOPA9UdaNWL80GDbqeZ/Jw gvtXdJHof/1PXC5mC6GQv+nB6GCairppEWYya1Z8suwWxKuQeS0ZQhw1m0B1ea9ntUBd cVTw==
X-Gm-Message-State: ALoCoQnB/sgVl4GTkWA2PhFnlI60ah4sj/Iv7+pRVRwWs7tCWawdHiiC2bXizipnVV+vtAJadX/j
MIME-Version: 1.0
X-Received: by 10.66.155.36 with SMTP id vt4mr8716385pab.93.1376008289564; Thu, 08 Aug 2013 17:31:29 -0700 (PDT)
Received: by 10.70.1.133 with HTTP; Thu, 8 Aug 2013 17:31:29 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:d068:24f8:b0a2:18a0]
In-Reply-To: <5204364E.7080905@network-heretics.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com>
Date: Fri, 9 Aug 2013 10:31:29 +1000
Message-ID: <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com>
Subject: Re: Faraday cages...
From: George Michaelson <ggm@algebras.org>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=047d7bacc01a4ec99504e378e58d
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 00:31:36 -0000

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

When next you walk into a target or big W, ask to see the conditions of
entry. Along with implied consent to have your bags checked at any time,
you have probably given consent to be video'ed and tracked at their behest.
The poster is on the wall somewhere usually. Your statutory rights cannot
be abrogated but equally, the grey areas have been 'informed'.

BT tracking inside the store is passive collection of data you are
radiating. The store's use of the BT location and timing of presence
against shelves is private information of immense value to them. They share
it for mutual benefit with suppliers, or for money. I doubt they give much
away.

The large international scroogle rhyming company was compiling third party
uses of the data to inform location as a service, and were not solely
collecting information inside their own physical territory you entered,
with implied consent: they were harvesting data in the public space and
then providing insight into that data into the public space.

They relate because its harvesting RF. They don't relate in much else to my
mind.

-G


On Fri, Aug 9, 2013 at 10:22 AM, Keith Moore <moore@network-heretics.com>wrote:

> On 08/08/2013 07:41 PM, Phillip Hallam-Baker wrote:
>
>> Hmmm didn't a certain large company whose name rhymes with scroogle
>> recently get whacked with a huge fine for violating privacy in a similar
>> manner in the EU?
>>
>
> The rules are different for large companies with funny names.
>
> Keith
>
>

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

<div dir=3D"ltr">When next you walk into a target or big W, ask to see the =
conditions of entry. Along with implied consent to have your bags checked a=
t any time, you have probably given consent to be video&#39;ed and tracked =
at their behest. The poster is on the wall somewhere usually. Your statutor=
y rights cannot be abrogated but equally, the grey areas have been &#39;inf=
ormed&#39;.<div>
<br></div><div>BT tracking inside the store is passive collection of data y=
ou are radiating. The store&#39;s use of the BT location and timing of pres=
ence against shelves is private information of immense value to them. They =
share it for mutual benefit with suppliers, or for money. I doubt they give=
 much away.</div>
<div><br></div><div>The large international scroogle rhyming company was co=
mpiling third party uses of the data to inform location as a service, and w=
ere not solely collecting information inside their own physical territory y=
ou entered, with implied consent: they were harvesting data in the public s=
pace and then providing insight into that data into the public space.</div>
<div><br></div><div>They relate because its harvesting RF. They don&#39;t r=
elate in much else to my mind.</div><div><br></div><div>-G</div></div><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Aug 9, 201=
3 at 10:22 AM, Keith Moore <span dir=3D"ltr">&lt;<a href=3D"mailto:moore@ne=
twork-heretics.com" target=3D"_blank">moore@network-heretics.com</a>&gt;</s=
pan> 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 08/08/2013 07:41 PM, Ph=
illip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hmmm didn&#39;t a certain large company whose name rhymes with scroogle rec=
ently get whacked with a huge fine for violating privacy in a similar manne=
r in the EU?<br>
</blockquote>
<br></div>
The rules are different for large companies with funny names.<span class=3D=
"HOEnZb"><font color=3D"#888888"><br>
<br>
Keith<br>
<br>
</font></span></blockquote></div><br></div>

--047d7bacc01a4ec99504e378e58d--

From hallam@gmail.com  Thu Aug  8 17:48:53 2013
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 EE50C11E817B for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 17:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNHJ2QDr+TGF for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 17:48:53 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id BB8CA11E817D for <ietf@ietf.org>; Thu,  8 Aug 2013 17:48:52 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id en1so1170863wid.6 for <ietf@ietf.org>; Thu, 08 Aug 2013 17:48:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NQxK/c8F3S6bNsgnhXlA213L6VqSL/qvrhPdf0nKmwE=; b=y5s2ovSDCKw2z4LukBzxWSb/I7q8iv5t/qGEEGUrEfRA4I0NC5fEuhDMVFeVoEahjt 6geOEOwuBHfSoVAjKrv53Tt6GGNWNcl8ojIw75vVuO5jWKm6ZoQ+ls/eg6Ob6Pd6Dn2J KvINGiBCzCPqZ5xwqDxJHJEzhrLq0PbY//lYY6nPVhtiBxATP2HzF13UFJQM/Rc/5WOb Wdo5luZGKKt/La+hHo87dB2MXmCRlmDSGC0iQt+EJebE2sxXvEzWHHBiWncVc92wj0JV Ck3Nlu4XgWy+TfIuEUYV6lbvwcRDnk2OO4bidcPkZYPM/sfihgakXyzN24FNn0Tpgn5K hjFQ==
MIME-Version: 1.0
X-Received: by 10.194.219.233 with SMTP id pr9mr4848000wjc.8.1376009331907; Thu, 08 Aug 2013 17:48:51 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 8 Aug 2013 17:48:51 -0700 (PDT)
In-Reply-To: <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com>
Date: Thu, 8 Aug 2013 20:48:51 -0400
Message-ID: <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com>
Subject: Re: Faraday cages...
From: Phillip Hallam-Baker <hallam@gmail.com>
To: George Michaelson <ggm@algebras.org>
Content-Type: multipart/alternative; boundary=001a11c1b7e66fa0ec04e37923c8
Cc: Keith Moore <moore@network-heretics.com>, 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, 09 Aug 2013 00:48:54 -0000

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

On Thu, Aug 8, 2013 at 8:31 PM, George Michaelson <ggm@algebras.org> wrote:

> When next you walk into a target or big W, ask to see the conditions of
> entry. Along with implied consent to have your bags checked at any time,
> you have probably given consent to be video'ed and tracked at their behest.
> The poster is on the wall somewhere usually. Your statutory rights cannot
> be abrogated but equally, the grey areas have been 'informed'.
>

The efficacy of such notices has not been tested in court and when they are
tested it is likely to cost the target about $2 million+ in legal fees.

Since the IETF meets around the world the last thing we need is to spend
time checking the legality of the badge at the mic system. And even though
the IETF is not likely to be a target, I would hate to have some of the
less popular with governments organizations I am involved in copy what the
IETF does and then find themselves being targeted with a selective
prosecution.

Barcodes have the potential to work really well and require almost no
change from current practice. The only downside to a barcode is that they
are slightly easier to forge. Though in the IETF context, forgery would
likely consist of people copying other people's badges for fun rather than
to avoid paying.


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

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

<div dir=3D"ltr">On Thu, Aug 8, 2013 at 8:31 PM, George Michaelson <span di=
r=3D"ltr">&lt;<a href=3D"mailto:ggm@algebras.org" target=3D"_blank">ggm@alg=
ebras.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D=
"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">When next you walk into a t=
arget or big W, ask to see the conditions of entry. Along with implied cons=
ent to have your bags checked at any time, you have probably given consent =
to be video&#39;ed and tracked at their behest. The poster is on the wall s=
omewhere usually. Your statutory rights cannot be abrogated but equally, th=
e grey areas have been &#39;informed&#39;.</div>
</blockquote><div><br></div><div>The efficacy of such notices has not been =
tested in court and when they are tested it is likely to cost the target ab=
out $2 million+ in legal fees.</div><div><br></div><div>Since the IETF meet=
s around the world the last thing we need is to spend time checking the leg=
ality of the badge at the mic system. And even though the IETF is not likel=
y to be a target, I would hate to have some of the less popular with govern=
ments organizations I am involved in copy what the IETF does and then find =
themselves being targeted with a selective prosecution.</div>
<div><br></div><div>Barcodes have the potential to work really well and req=
uire almost no change from current practice. The only downside to a barcode=
 is that they are slightly easier to forge. Though in the IETF context, for=
gery would likely consist of people copying other people&#39;s badges for f=
un rather than to avoid paying.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c1b7e66fa0ec04e37923c8--

From ggm@algebras.org  Thu Aug  8 18:02:44 2013
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2BA121F9A37 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.376
X-Spam-Level: 
X-Spam-Status: No, score=-1.376 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, 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 0nYVE6bhh0NR for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:02:40 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 47B2211E8178 for <ietf@ietf.org>; Thu,  8 Aug 2013 18:02:40 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fz6so1539383pac.31 for <ietf@ietf.org>; Thu, 08 Aug 2013 18:02:40 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pLDp6P0mPvkf/kXraPDtEb4uTba2HyIBX6lnT5+ivKY=; b=j4dprJJEyb03QLleUOvQaH6se8B8SCRpJWOAr22oz3Edhz6sM1YPKUd5DH+7YTMwVZ M3gp42vrsEPg7T8AFwvUL75uT40rWLY75uvvMMHc2FiNZ2+LBkXKpwr5ZierrWELaql7 tKPKjLCxU4tpnE6VD8mE9pjwEvZmFuGya544hyVqHu5wBKqVvavRQHpjiDv3f+G04bgS d1Tg1hGFRCmPCHhkcWmYJM4/Y8GVsUHVww3GrbPwoFXOB1b8QB9+A+z3RkDSlcBSoXbB lMS9jAUweYlGxtWo+eij7CdoRWYK4f35E/4R4HPT9MPUs3ULiK/I19B0YRwPKZhx19ac dPkw==
X-Gm-Message-State: ALoCoQnKbcYqPPk9byHYBLryLTwbrb2G2QUahDFnpuEIc8zh66bhKkpvWqs8pjqrKhLkDUiKwdBM
MIME-Version: 1.0
X-Received: by 10.68.17.230 with SMTP id r6mr8745880pbd.112.1376010159940; Thu, 08 Aug 2013 18:02:39 -0700 (PDT)
Received: by 10.70.1.133 with HTTP; Thu, 8 Aug 2013 18:02:39 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:d068:24f8:b0a2:18a0]
In-Reply-To: <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com>
Date: Fri, 9 Aug 2013 11:02:39 +1000
Message-ID: <CAKr6gn0Mi0_x2X_iaGT97xNbGhoaxEXa8JFL7mWyAu1MyZma=A@mail.gmail.com>
Subject: Re: Faraday cages...
From: George Michaelson <ggm@algebras.org>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=bcaec520ee93ca77f604e37954cc
Cc: Keith Moore <moore@network-heretics.com>, 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, 09 Aug 2013 01:02:44 -0000

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

Philip, I'm not disagreeing. I responded to Keith's mail relating what we
do to what was done harvesting WiFi. Like the store, we're in a room. we're
in a world of implied and actual consent (you do actually have to give some
consents when you register for IETF)

-G


On Fri, Aug 9, 2013 at 10:48 AM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> On Thu, Aug 8, 2013 at 8:31 PM, George Michaelson <ggm@algebras.org>wrote:
>
>> When next you walk into a target or big W, ask to see the conditions of
>> entry. Along with implied consent to have your bags checked at any time,
>> you have probably given consent to be video'ed and tracked at their behest.
>> The poster is on the wall somewhere usually. Your statutory rights cannot
>> be abrogated but equally, the grey areas have been 'informed'.
>>
>
> The efficacy of such notices has not been tested in court and when they
> are tested it is likely to cost the target about $2 million+ in legal fees.
>
> Since the IETF meets around the world the last thing we need is to spend
> time checking the legality of the badge at the mic system. And even though
> the IETF is not likely to be a target, I would hate to have some of the
> less popular with governments organizations I am involved in copy what the
> IETF does and then find themselves being targeted with a selective
> prosecution.
>
> Barcodes have the potential to work really well and require almost no
> change from current practice. The only downside to a barcode is that they
> are slightly easier to forge. Though in the IETF context, forgery would
> likely consist of people copying other people's badges for fun rather than
> to avoid paying.
>
>
> --
> Website: http://hallambaker.com/
>

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

<div dir=3D"ltr">Philip, I&#39;m not disagreeing. I responded to Keith&#39;=
s mail relating what we do to what was done harvesting WiFi. Like the store=
, we&#39;re in a room. we&#39;re in a world of implied and actual consent (=
you do actually have to give some consents when you register for IETF)<div>
<br></div><div>-G</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Fri, Aug 9, 2013 at 10:48 AM, Phillip Hallam-Baker <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">hal=
lam@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Thu, A=
ug 8, 2013 at 8:31 PM, George Michaelson <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:ggm@algebras.org" target=3D"_blank">ggm@algebras.org</a>&gt;</span> w=
rote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">When next you walk into a t=
arget or big W, ask to see the conditions of entry. Along with implied cons=
ent to have your bags checked at any time, you have probably given consent =
to be video&#39;ed and tracked at their behest. The poster is on the wall s=
omewhere usually. Your statutory rights cannot be abrogated but equally, th=
e grey areas have been &#39;informed&#39;.</div>

</blockquote><div><br></div></div><div>The efficacy of such notices has not=
 been tested in court and when they are tested it is likely to cost the tar=
get about $2 million+ in legal fees.</div><div><br></div><div>Since the IET=
F meets around the world the last thing we need is to spend time checking t=
he legality of the badge at the mic system. And even though the IETF is not=
 likely to be a target, I would hate to have some of the less popular with =
governments organizations I am involved in copy what the IETF does and then=
 find themselves being targeted with a selective prosecution.</div>

<div><br></div><div>Barcodes have the potential to work really well and req=
uire almost no change from current practice. The only downside to a barcode=
 is that they are slightly easier to forge. Though in the IETF context, for=
gery would likely consist of people copying other people&#39;s badges for f=
un rather than to avoid paying.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div><br></div></font></span></div><span class=3D"HOEnZb"><f=
ont color=3D"#888888">-- <br>Website: <a href=3D"http://hallambaker.com/" t=
arget=3D"_blank">http://hallambaker.com/</a><br>
</font></span></div></div>
</blockquote></div><br></div>

--bcaec520ee93ca77f604e37954cc--

From moore@network-heretics.com  Thu Aug  8 18:05:41 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7434811E817D for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSoqdA-eKJB3 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:05:35 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0F78F11E8178 for <ietf@ietf.org>; Thu,  8 Aug 2013 18:05:35 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0C2E120B6F; Thu,  8 Aug 2013 21:05:33 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 08 Aug 2013 21:05:34 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=GKBXYO/K2+IvOVN5AMpbv9 RyGdY=; b=MXFbYw+bQc3Ut6moKI4UMJpxeX0mLQijUu7BbPsAHp7Kqhm5APv1XS 3MMBbPZIGed8pCftFLNVjyWPR1nGipixavnBxe76UlJkANimRp3DaYxCVItWzH6u 1iXje3pQ8cWN9+pGl529Egyq2P28BBY65svynRgNMikRKmBMKqG6A=
X-Sasl-enc: P18wTTf5NPeLSeGeIbdVuU0H8j+UeB08W4eVNjatmcyJ 1376010333
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E97FA68009A; Thu,  8 Aug 2013 21:05:32 -0400 (EDT)
Message-ID: <52044054.7020205@network-heretics.com>
Date: Thu, 08 Aug 2013 21:05:24 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Faraday cages...
References: <20130807043255.39248.qmail@joyce.lan> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com>
In-Reply-To: <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 09 Aug 2013 01:05:41 -0000

On 08/08/2013 08:48 PM, Phillip Hallam-Baker wrote:
> Barcodes have the potential to work really well and require almost no 
> change from current practice.

Except that current practice is broken anyway and we desperately need to 
change it, not add more mechanisms to reinforce continued use of it.

Actually I think all of this emphasis on being able to reliably identify 
every speaker is a bit beside the point.   With rare exceptions, who is 
speaking is not nearly as relevant as what is being said.   Of course 
there are times when it's important or useful to know who is speaking - 
say if it's an AD, or the document author/editor, or a person with whom 
there needs to be a followup discussion.   But when we find ourselves 
working so hard to make sure that we can reliably identify every speaker 
(and perhaps also to exclude anonymous / pseudonymous input), maybe 
that's a distraction.   Maybe we should instead be concentrating on how 
to make sure that our standards have been written in light of a wide 
degree of input about requirements, are technically sound, and have 
enjoyed thorough review.

Would being able to reliably know exactly who said everything that was 
said in a WG meeting visibly improve the quality of our standards?   If 
the answer is not a clear "yes" (and I don't think it is) then I suggest 
that this topic is a distraction.

Keith


From ggm@algebras.org  Thu Aug  8 18:08:03 2013
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A693521F9AED for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:08:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Level: 
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=0.800,  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 lsXhfkY5LMc1 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:07:54 -0700 (PDT)
Received: from mail-pb0-f50.google.com (mail-pb0-f50.google.com [209.85.160.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5D021F9F2D for <ietf@ietf.org>; Thu,  8 Aug 2013 18:07:50 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo5so4066173pbc.23 for <ietf@ietf.org>; Thu, 08 Aug 2013 18:07:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pzKr4s614voWpolxABpKb0iCfVq1cYpGaR3+cfhwILw=; b=lNZI9AR0Gm39vUqiKZPxj8G0zhq4ULhVLm2ygdZ8w8ISvnHSwiJvLlW+t06rZEq6sD sE7QwnlYg4pZqw09Pl1oFWsalRSdopx/nJ9X1S/b85PlXzNTcpg6r+CbsWMBtFZ2mNNC HkHuxqe3KqZL1Ky4iqFPuFN3l4kbiTjKiH7qDRtnCLDSkaQ2Ex88AhJ53OnQdd8t7i95 ptOsPtieoOFhV1D8//cAKt20XUNGJO2Do4V3A9kbjYoTT2e+HGejxbRUccG1z3WjXn5P pKYZogy+Y9aH0xMIHF+zkfTF3Lj1jHWYkONtjX1giVKmuuEDUS5L5tcxCWBEQxP/KPFE gx6g==
X-Gm-Message-State: ALoCoQlNj/7GhlLTds+aittK1P5GepC7NgFa7KcnAK/D9vgbhNTfAws+wqHpoxTc5D25oVpZTSZH
MIME-Version: 1.0
X-Received: by 10.66.246.106 with SMTP id xv10mr8883127pac.100.1376010466412;  Thu, 08 Aug 2013 18:07:46 -0700 (PDT)
Received: by 10.70.1.133 with HTTP; Thu, 8 Aug 2013 18:07:46 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:d068:24f8:b0a2:18a0]
In-Reply-To: <52044054.7020205@network-heretics.com>
References: <20130807043255.39248.qmail@joyce.lan> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com> <52044054.7020205@network-heretics.com>
Date: Fri, 9 Aug 2013 11:07:46 +1000
Message-ID: <CAKr6gn3w4uMMY7tA0m0jpcErzer6vkwFZE01HNUrY6t4bky-xQ@mail.gmail.com>
Subject: Re: Faraday cages...
From: George Michaelson <ggm@algebras.org>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=047d7b111ad30ed9e504e379678d
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, 09 Aug 2013 01:08:04 -0000

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

On Fri, Aug 9, 2013 at 11:05 AM, Keith Moore <moore@network-heretics.com>wrote:

>
> Would being able to reliably know exactly who said everything that was
> said in a WG meeting visibly improve the quality of our standards?   If the
> answer is not a clear "yes" (and I don't think it is) then I suggest that
> this topic is a distraction.
>
> Keith
>
>
With this I heartily agree. I think there is nothing to see here which will
really make much difference, or cannot be solved in other ways after the
event anyway. The problem is not one which technology can solve, because
the problem isn't that kind of problem.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 9, 2013 at 11:05 AM, Keith Moore <span dir=3D"ltr">&lt;=
<a href=3D"mailto:moore@network-heretics.com" target=3D"_blank">moore@netwo=
rk-heretics.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br></div>
Would being able to reliably know exactly who said everything that was said=
 in a WG meeting visibly improve the quality of our standards? =A0 If the a=
nswer is not a clear &quot;yes&quot; (and I don&#39;t think it is) then I s=
uggest that this topic is a distraction.<span class=3D"HOEnZb"><font color=
=3D"#888888"><br>

<br>
Keith<br>
<br>
</font></span></blockquote></div><br></div><div class=3D"gmail_extra">With =
this I heartily agree. I think there is nothing to see here which will real=
ly make much difference, or cannot be solved in other ways after the event =
anyway. The problem is not one which technology can solve, because the prob=
lem isn&#39;t that kind of problem.</div>
</div>

--047d7b111ad30ed9e504e379678d--

From marka@isc.org  Thu Aug  8 18:19:12 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E603011E817D for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level: 
X-Spam-Status: No, score=-1.213 tagged_above=-999 required=5 tests=[AWL=-1.214, BAYES_00=-2.599, GB_MUTUALBENEFIT=2, J_CHICKENPOX_52=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kmnoJBC59PG for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 18:19:07 -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 CF0A811E817E for <ietf@ietf.org>; Thu,  8 Aug 2013 18:19:05 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 84D95C9424; Fri,  9 Aug 2013 01:18:53 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1376011145; bh=nhxEp8+tcrkknTttVvui25uCPZQPvvMmv9UXZjqbP20=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=qhM1QBd7wMaYLxbi7HZU9uioKQChU7/pXN5/HX2c+Y6SHi8Lnq0qmM5Fh3oDQZSES MPcGbTA2QBgeVNob3/yDtIkEIGxq+qXGU3Dv7DRiI4fTE/8UP0RHEHOOSjThya5OdW QMi8Jxw+9a54tDt+JRoZHJZ4qOFNd16NUHDFEqO0=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Fri,  9 Aug 2013 01:18:53 +0000 (UTC) (envelope-from marka@isc.org)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 05AE3160390; Fri,  9 Aug 2013 01:23:16 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id nVquZpjA05G9; Fri,  9 Aug 2013 01:23:15 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 35AAE160392; Fri,  9 Aug 2013 01:23:15 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 02A2E160391; Fri,  9 Aug 2013 01:23:15 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 3E156382F052; Fri,  9 Aug 2013 11:18:50 +1000 (EST)
To: George Michaelson <ggm@algebras.org>
From: Mark Andrews <marka@isc.org>
References: <20130807043255.39248.qmail@joyce.lan> <8D23D4052ABE7A4490E77B1A012B630775248FA4@mbx-01.win.nominum.com> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com>
Subject: Re: Faraday cages...
In-reply-to: Your message of "Fri, 09 Aug 2013 10:31:29 +1000." <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com>
Date: Fri, 09 Aug 2013 11:18:50 +1000
Message-Id: <20130809011850.3E156382F052@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 01:19:12 -0000

In message <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com>
, George Michaelson writes:
> 
> When next you walk into a target or big W, ask to see the conditions of
> entry. Along with implied consent to have your bags checked at any time,
> you have probably given consent to be video'ed and tracked at their behest.
> The poster is on the wall somewhere usually. Your statutory rights cannot
> be abrogated but equally, the grey areas have been 'informed'.

You expect to video'ed and bag checked for stock loss prevention.  There
is no implied consent for anything else.  You don't need to track mobile
phones for stock loss prevention.
 
> BT tracking inside the store is passive collection of data you are
> radiating. The store's use of the BT location and timing of presence
> against shelves is private information of immense value to them. They share
> it for mutual benefit with suppliers, or for money. I doubt they give much
> away.
> 
> The large international scroogle rhyming company was compiling third party
> uses of the data to inform location as a service, and were not solely
> collecting information inside their own physical territory you entered,
> with implied consent: they were harvesting data in the public space and
> then providing insight into that data into the public space.
> 
> They relate because its harvesting RF. They don't relate in much else to my
> mind.

The main difference is the levels of encryption used in the two standards.
For WiFi there are still a large percentage of networks sending in the clear.
For BlueTooth there were no non-encrypted channels in the base spec (1.0)
support for them was added in 1.1 [1].

With BlueTooth you get presence.
With WiFi you get presence + data

Mark

[1] http://en.wikipedia.org/wiki/Bluetooth#Bluetooth_v1.1
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From narten@us.ibm.com  Thu Aug  8 21:53:16 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA9E521F9E68 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 21:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.449
X-Spam-Level: 
X-Spam-Status: No, score=-109.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_SAVELE=2.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 vKo+ogF2Y7tJ for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 21:53:09 -0700 (PDT)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id D5B4621F9BF2 for <ietf@ietf.org>; Thu,  8 Aug 2013 21:53:08 -0700 (PDT)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 8 Aug 2013 22:53:08 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 8 Aug 2013 22:53:07 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 137E63E4003E for <ietf@ietf.org>; Thu,  8 Aug 2013 22:52:43 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r794r6iO163182 for <ietf@ietf.org>; Thu, 8 Aug 2013 22:53:06 -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 r794r5US017810 for <ietf@ietf.org>; Thu, 8 Aug 2013 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r794r58E017793 for <ietf@ietf.org>; Thu, 8 Aug 2013 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r794r4lM030285 for <ietf@ietf.org>; Fri, 9 Aug 2013 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r794r4fv030231 for ietf@ietf.org; Fri, 9 Aug 2013 00:53:04 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201308090453.r794r4fv030231@rotala.raleigh.ibm.com>
Date: Fri, 09 Aug 2013 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13080904-7282-0000-0000-00001A3A9A18
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 04:53:16 -0000

Total of 288 messages in the last 7 days.
 
script run at: Fri Aug  9 00:53:03 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.29% |   21 |  6.58% |   137704 | ted.lemon@nominum.com
  4.86% |   14 |  4.24% |    88736 | scott.brim@gmail.com
  4.51% |   13 |  3.79% |    79279 | johnl@taugh.com
  3.82% |   11 |  4.27% |    89389 | hadriel.kaplan@oracle.com
  2.78% |    8 |  4.66% |    97597 | hallam@gmail.com
  3.47% |   10 |  3.18% |    66490 | moore@network-heretics.com
  3.12% |    9 |  3.19% |    66877 | john-ietf@jck.com
  2.43% |    7 |  2.11% |    44224 | ynir@checkpoint.com
  2.43% |    7 |  1.97% |    41295 | aaron.ding@cl.cam.ac.uk
  2.08% |    6 |  2.03% |    42597 | jabley@hopcount.ca
  1.74% |    5 |  2.24% |    46840 | brian.e.carpenter@gmail.com
  1.74% |    5 |  2.17% |    45393 | cgriffiths@gmail.com
  1.74% |    5 |  1.72% |    36025 | sm@resistor.net
  1.74% |    5 |  1.55% |    32513 | cabo@tzi.org
  1.74% |    5 |  1.55% |    32472 | mcr+ietf@sandelman.ca
  1.74% |    5 |  1.54% |    32264 | barryleiba@computer.org
  1.74% |    5 |  1.42% |    29701 | dougb@dougbarton.us
  1.39% |    4 |  1.72% |    35986 | abdussalambaryun@gmail.com
  1.74% |    5 |  1.34% |    28087 | paul.hoffman@vpnc.org
  1.04% |    3 |  1.62% |    33914 | spencerdawkins.ietf@gmail.com
  1.39% |    4 |  1.26% |    26452 | ulrich@herberg.name
  1.39% |    4 |  1.21% |    25379 | hgs@cs.columbia.edu
  1.04% |    3 |  1.41% |    29477 | ggm@algebras.org
  1.04% |    3 |  1.25% |    26200 | mary.h.barnes@gmail.com
  0.69% |    2 |  1.49% |    31154 | superuser@gmail.com
  1.04% |    3 |  1.13% |    23755 | hildjj@cursive.net
  0.69% |    2 |  1.37% |    28593 | cntreras@gmail.com
  1.04% |    3 |  1.00% |    20881 | stephen.farrell@cs.tcd.ie
  1.04% |    3 |  0.98% |    20456 | paitken@cisco.com
  1.04% |    3 |  0.94% |    19716 | ole@cisco.com
  1.04% |    3 |  0.92% |    19193 | mcr@sandelman.ca
  1.04% |    3 |  0.89% |    18567 | dhc@dcrocker.net
  1.04% |    3 |  0.87% |    18120 | adrian@olddog.co.uk
  1.04% |    3 |  0.86% |    18025 | lars@netapp.com
  1.04% |    3 |  0.86% |    18017 | melinda.shore@gmail.com
  1.04% |    3 |  0.85% |    17892 | joelja@bogus.com
  0.69% |    2 |  0.84% |    17550 | l.wood@surrey.ac.uk
  0.69% |    2 |  0.82% |    17211 | daedulus@btconnect.com
  0.69% |    2 |  0.81% |    16966 | huitema@microsoft.com
  0.69% |    2 |  0.77% |    16166 | andrewf@plixer.com
  0.69% |    2 |  0.74% |    15583 | grmocg@gmail.com
  0.69% |    2 |  0.73% |    15295 | carlosm3011@gmail.com
  0.69% |    2 |  0.71% |    14909 | doug.mtview@gmail.com
  0.69% |    2 |  0.71% |    14817 | olaf@nlnetlabs.nl
  0.69% |    2 |  0.69% |    14423 | petithug@acm.org
  0.69% |    2 |  0.69% |    14359 | james.h.manger@team.telstra.com
  0.69% |    2 |  0.64% |    13368 | andy@yumaworks.com
  0.69% |    2 |  0.63% |    13122 | rpelletier@isoc.org
  0.69% |    2 |  0.58% |    12238 | arturo.servin@gmail.com
  0.69% |    2 |  0.58% |    12064 | heas@shrubbery.net
  0.69% |    2 |  0.56% |    11702 | glenn.deen@nbcuni.com
  0.69% |    2 |  0.55% |    11585 | jari.arkko@piuha.net
  0.69% |    2 |  0.54% |    11318 | oej@edvina.net
  0.69% |    2 |  0.49% |    10285 | mrex@sap.com
  0.35% |    1 |  0.82% |    17173 | cpignata@cisco.com
  0.69% |    2 |  0.47% |     9886 | randy@psg.com
  0.69% |    2 |  0.43% |     8965 | jnc@mercury.lcs.mit.edu
  0.35% |    1 |  0.60% |    12460 | ron.even.tlv@gmail.com
  0.35% |    1 |  0.49% |    10339 | narten@us.ibm.com
  0.35% |    1 |  0.48% |     9952 | jmpolk@cisco.com
  0.35% |    1 |  0.45% |     9462 | uyeshiro@ifa.hawaii.edu
  0.35% |    1 |  0.45% |     9364 | mehmet.ersue@nsn.com
  0.35% |    1 |  0.45% |     9336 | rogerj@gmail.com
  0.35% |    1 |  0.45% |     9333 | lear@cisco.com
  0.35% |    1 |  0.45% |     9330 | gjshep@gmail.com
  0.35% |    1 |  0.44% |     9299 | dave@cridland.net
  0.35% |    1 |  0.42% |     8862 | cgriffiths@dyn.com
  0.35% |    1 |  0.41% |     8603 | marka@isc.org
  0.35% |    1 |  0.41% |     8490 | framefritti@gmail.com
  0.35% |    1 |  0.40% |     8304 | bmanning@isi.edu
  0.35% |    1 |  0.37% |     7831 | br@brianrosen.net
  0.35% |    1 |  0.37% |     7734 | aallen@blackberry.com
  0.35% |    1 |  0.36% |     7615 | jgunn6@csc.com
  0.35% |    1 |  0.36% |     7582 | tobias.gondrom@gondrom.org
  0.35% |    1 |  0.36% |     7517 | york@isoc.org
  0.35% |    1 |  0.35% |     7345 | chelliot@pobox.com
  0.35% |    1 |  0.34% |     7092 | loa@pi.nu
  0.35% |    1 |  0.34% |     7090 | listsebby@me.com
  0.35% |    1 |  0.34% |     7056 | jcurran@istaff.org
  0.35% |    1 |  0.34% |     7056 | iana-questions@iana.org
  0.35% |    1 |  0.34% |     7035 | tony@att.com
  0.35% |    1 |  0.33% |     7011 | rg+ietf@qualcomm.com
  0.35% |    1 |  0.32% |     6788 | alexey.melnikov@isode.com
  0.35% |    1 |  0.31% |     6483 | spromano@unina.it
  0.35% |    1 |  0.31% |     6398 | pthaler@broadcom.com
  0.35% |    1 |  0.31% |     6390 | morrowc.lists@gmail.com
  0.35% |    1 |  0.30% |     6372 | tjc@ecs.soton.ac.uk
  0.35% |    1 |  0.30% |     6371 | adam@nostrum.com
  0.35% |    1 |  0.30% |     6221 | john@jck.com
  0.35% |    1 |  0.30% |     6209 | stpeter@stpeter.im
  0.35% |    1 |  0.29% |     6156 | scott@kitterman.com
  0.35% |    1 |  0.29% |     6043 | housley@vigilsec.com
  0.35% |    1 |  0.28% |     5890 | amorris@amsl.com
  0.35% |    1 |  0.28% |     5856 | sm+ietf@elandsys.com
  0.35% |    1 |  0.28% |     5856 | lberger@labn.net
  0.35% |    1 |  0.28% |     5843 | jason_livingood@cable.comcast.com
  0.35% |    1 |  0.27% |     5667 | martin.thomson@gmail.com
  0.35% |    1 |  0.26% |     5413 | warren@kumari.net
  0.35% |    1 |  0.25% |     5310 | henrik@levkowetz.com
  0.35% |    1 |  0.25% |     5250 | rsk@gsp.org
  0.35% |    1 |  0.25% |     5250 | paf@frobbit.se
  0.35% |    1 |  0.25% |     5186 | zhaoqin@bupt.edu.cn
  0.35% |    1 |  0.24% |     5016 | cos@aaaaa.org
--------+------+--------+----------+------------------------
100.00% |  288 |100.00% |  2093311 | Total


From superuser@gmail.com  Thu Aug  8 22:19:51 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAF7B21F9E37 for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 22:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.067,  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 6FLtK1UKxcWa for <ietf@ietfa.amsl.com>; Thu,  8 Aug 2013 22:19:51 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 299D721F9E35 for <ietf@ietf.org>; Thu,  8 Aug 2013 22:19:51 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id u55so3241518wes.27 for <ietf@ietf.org>; Thu, 08 Aug 2013 22: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=44pMCP5YcFcHVIA5pXUb+Z3LoHFTsfoLXiPsItZVJ2U=; b=S5jGLyCgMDfDAfWxwZ0gz/ELo3k1noo5kzOvPyWXQ6E30/5zQBfgm72MDjiPtAdWmm yA9C1Ltb9ouxS6+MbNNGHh2Bd+wmJkNVwhISYZRHPr3PGq5qrxxjgovtJvJ4hX7sfL3s LfNq5JhOjDCExeWxbmG+fJng6zo0Raf7gLo4zUVDZt5hifBnFv16mErB5M2MDi3smVOC zXm+VC5ETbRsVgzkia3e0uLdbcZC/7LHYY8b2b7VEgxyQkprbvLeXiBlSqvbpQX5Q+w0 UJ8KTfRZkgwXz/lt2iGIJaSQWHniG+VytgyYuwEvl3Y/C+3MQ8Q98aXjIX6doFMankgA 9b8g==
MIME-Version: 1.0
X-Received: by 10.194.48.116 with SMTP id k20mr5355420wjn.23.1376025590332; Thu, 08 Aug 2013 22:19:50 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Thu, 8 Aug 2013 22:19:50 -0700 (PDT)
In-Reply-To: <CAMm+LwgerUOFHgTVrwbekDX-hePzw8QuGAhTn=sPtp2CnNS02g@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAL0qLwb=QncDyjh_qqXm4AqzURBtxRNUgTSaSO6X8E9PchEF0A@mail.gmail.com> <CAMm+LwgerUOFHgTVrwbekDX-hePzw8QuGAhTn=sPtp2CnNS02g@mail.gmail.com>
Date: Thu, 8 Aug 2013 22:19:50 -0700
Message-ID: <CAL0qLwYAYRWA=gMm-h2X7zjb_qdKhFUvxQqtM47DUume1a7F+w@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=047d7ba975e68383fc04e37cec36
Cc: Joe Hildebrand <hildjj@cursive.net>, Barry Leiba <barryleiba@computer.org>, 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, 09 Aug 2013 05:19:52 -0000

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

On Thu, Aug 8, 2013 at 7:47 AM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> The point is that there would BE discussion. Consensus is not enough, the
> process has to be open. A consensus formed by keeping people out of the
> room is no consensus at all.
>

I believe this is why an AD-sponsored document undergoes a Last Call twice
the length of a document that comes out of a working group, and the
comments are typically sent to this list, which is open by definition and
also goes to a more general audience than a working group list would.

I don't see any evidence of attempts to exclude participation here, unless
your concern is sufficiently general that you also believe the Individual
Submission route needs to be abolished because it's too closed.

-MSK

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

<div dir=3D"ltr">On Thu, Aug 8, 2013 at 7:47 AM, Phillip Hallam-Baker <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.com" target=3D"_blank">hall=
am@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">The point is that there wou=
ld BE discussion. Consensus is not enough, the process has to be open. A co=
nsensus formed by keeping people out of the room is no consensus at all.</d=
iv>
</blockquote><div><br></div><div>I believe this is why an AD-sponsored docu=
ment undergoes a Last Call twice the length of a document that comes out of=
 a working group, and the comments are typically sent to this list, which i=
s open by definition and also goes to a more general audience than a workin=
g group list would.<br>
<br></div><div>I don&#39;t see any evidence of attempts to exclude particip=
ation here, unless your concern is sufficiently general that you also belie=
ve the Individual Submission route needs to be abolished because it&#39;s t=
oo closed.<br>
<br></div><div>-MSK<br></div></div></div></div>

--047d7ba975e68383fc04e37cec36--

From Ted.Lemon@nominum.com  Fri Aug  9 06:39:49 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 993C011E80FC for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 06:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.034, 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 MIXx5XTvrMcq for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 06:39:30 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7A511E80DC for <ietf@ietf.org>; Fri,  9 Aug 2013 06:39:29 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUgTxD+jLU09RguKDLUdvByinYjptNZuJ@postini.com; Fri, 09 Aug 2013 06:39:29 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B591F1B8298 for <ietf@ietf.org>; Fri,  9 Aug 2013 06:39:27 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1A417190060; Fri,  9 Aug 2013 06:39:27 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 9 Aug 2013 06:39:14 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Faraday cages...
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52044054.7020205@network-heretics.com>
Date: Fri, 9 Aug 2013 09:39:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <3F97BF72-62A7-4A69-908B-A4C01D75A8ED@nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <CAO_Rpc+2ZLkzoF=vBLc2GC2C5ONOmWEo1iAu00ANpAyAm7O7bg@mail.gmail.com> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com> <52044054.7020205@network-heretics. com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
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, 09 Aug 2013 13:39:49 -0000

On Aug 8, 2013, at 9:05 PM, Keith Moore <moore@network-heretics.com> =
wrote:
> Would being able to reliably know exactly who said everything that was =
said in a WG meeting visibly improve the quality of our standards?   If =
the answer is not a clear "yes" (and I don't think it is) then I suggest =
that this topic is a distraction.

If you mean will it improve what is written on the page, probably not.   =
Will it decrease the likelihood of someone participating without =
identifying themself, and then violating the IPR rules?   Possibly.

AFAIK that's why we do it.   Not so much because it is an iron-clad =
preventative, but because it to some degree removes the illusion of =
anonymity that might tempt someone to do something like that, or just be =
careless about it.


From david.black@emc.com  Fri Aug  9 08:12:38 2013
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 40D2C21F9F7F; Fri,  9 Aug 2013 08:12:38 -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 BGXXwHK-WSKl; Fri,  9 Aug 2013 08:12:33 -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 0767221E8116; Fri,  9 Aug 2013 08:05:09 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79EsEOd003669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 10:54:15 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Fri, 9 Aug 2013 10:53:57 -0400
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79Err6x005981; Fri, 9 Aug 2013 10:53:55 -0400
Received: from mxhub37.corp.emc.com (128.222.70.104) by mxhub36.corp.emc.com (10.254.93.84) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 9 Aug 2013 10:53:54 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub37.corp.emc.com ([128.222.70.104]) with mapi; Fri, 9 Aug 2013 10:53:53 -0400
From: "Black, David" <david.black@emc.com>
To: "d3e3e3@gmail.com" <d3e3e3@gmail.com>, "joe.abley@icann.org" <joe.abley@icann.org>, General Area Review Team <gen-art@ietf.org>
Date: Fri, 9 Aug 2013 10:53:52 -0400
Subject: Gen-ART review of draft-eastlake-rfc5342bis-04
Thread-Topic: Gen-ART review of draft-eastlake-rfc5342bis-04
Thread-Index: Ac6VEEKdA2xd69LGR46X1qbivgZDPw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C2B7446@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
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: Fri, 09 Aug 2013 15:12:38 -0000

The -04 version of this draft resolves the typo/thinko that snuck into
the -03 version, and fixed a number of related instances of that problem
that I missed in that review.

The -04 version of this draft is ready for publication as a BCP RFC.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Sunday, June 09, 2013 1:47 PM
> To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> Cc: joelja@bogus.com; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-eastlake-rfc5342bis-03
>=20
> The -03 version of this draft resolves all of the concerns raised by
> the Gen-ART review of the -02 version.
>=20
> Unfortunately, a serious typo/thinko snuck into the -03 version (been
> there, done that, myself).  Section 3.2 currently says:
>=20
>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-0E-00-42) to be used for documentation purposes.
>=20
> The parenthetical expansion of the protocol number is incorrect.
> The correct expansion uses -5E- instead of -0E-:
>=20
>    00-42 is a protocol number under the IANA OUI (that is,
>    00-00-5E-00-42) to be used for documentation purposes.
>=20
> I strongly suggest submitting a -04 version of this draft to make
> the necessary single character correction (e.g., as opposed to using
> a RFC Editor Note for that purpose).
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Wednesday, June 05, 2013 6:13 PM
> > To: d3e3e3@gmail.com; joe.abley@icann.org; General Area Review Team
> > Cc: Black, David; joelja@bogus.com; ietf@ietf.org
> > Subject: Gen-ART review of draft-eastlake-rfc5342bis-02
> >
> > 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-eastlake-rfc5342bis-02
> > Reviewer: David L. Black
> > Review Date: June 5, 2013
> > IETF LC End Date: June 4, 2013
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > This draft updates the IANA registered Ethernet parameters for IETF use=
,
> > including recording values assigned for documentation.  It also makes s=
ome
> > minor changes to IANA procedures.
> >
> > IANA should review this entire draft, not just its IANA Considerations
> > section;
> > Pearl Liang appears to have done that comprehensive review for IANA.
> >
> > Major issues: None
> >
> > Minor issues: One, the IANA review also found this issue.
> >
> > Section 3.2 states:
> >
> > 	IANA will assign "00-00-0E-00-42" as the protocol number under the
> > 	IANA OUI to be used for documentation purposes.
> >
> > IANA has not made this assignment, but this assignment request is not
> > recorded in the IANA Considerations section where IANA actions are
> > requested and recorded by IANA after they have been performed.  This
> > assignment needs to be added to the IANA Considerations section;
> > see item 5 in the IANA review.
> >
> > Nits/editorial comments:
> >
> > Section 1: This document uses an "IESG Ratification" process for some
> > assignments.  This is not the same process as the "IESG Approval" proce=
ss
> > defined in RFC 5226.  As those names could be confused by a casual read=
er
> > who is not strongly familiar with IANA processes, I suggest adding a
> > statement that the "IESG Ratification" process is defined in this docum=
ent
> > and is not the same as the "IESG Approval" process in RFC 5226.  This c=
ould
> > be added after the sentence that cites RFC 5226.
> >
> > Section 1.4: It would be helpful to point out that there is no OUI assi=
gned
> > for documentation purposes, but there are identifiers based on the IANA=
 OUI
> > that have been assigned for documentation purposes.
> >
> > In general, the use of the acronym IAB for Individual Address Block is
> > unfortunate, but unavoidable, and this is clearly pointed out in the
> > definition of the IAB acronym in section 1.2.  Nothing can or should be
> > done about this.
> >
> > idnits 2.12.17 did not find any nits.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From david.black@emc.com  Fri Aug  9 08:19:36 2013
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 9A0BC11E8196; Fri,  9 Aug 2013 08:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxH3MI7Ew7wF; Fri,  9 Aug 2013 08:19:28 -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 86E9021F9EFC; Fri,  9 Aug 2013 08:11:18 -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 r79ElVGn030222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Aug 2013 10:47:31 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 9 Aug 2013 10:47:07 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r79El6Ae021361; Fri, 9 Aug 2013 10:47:06 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Fri, 9 Aug 2013 10:47:05 -0400
From: "Black, David" <david.black@emc.com>
To: "housley@vigilsec.com" <housley@vigilsec.com>, "tim.polk@nist.gov" <tim.polk@nist.gov>, "Sam Hartman (hartmans@painless-security.com)" <hartmans@painless-security.com>, "Dacheng Zhang (zhangdacheng@huawei.com)" <zhangdacheng@huawei.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Fri, 9 Aug 2013 10:47:05 -0400
Subject: Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Topic: Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6VD0rmlAaf+56PTd+LLDqqvEOcAQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@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
Cc: "Black, David" <david.black@emc.com>, "karp@ietf.org" <karp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 15:19:36 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-karp-crypto-key-table-08
Reviewer: David L. Black
Review Date: August 9, 2013
IETF LC End Date: April 29, 2013
IETF Telechat Date: August 15, 2013

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

This draft describes a conceptual key database for use by protocols.
It's definitely useful and valuable work, as key management is often
an afterthought in protocol design, even when security functionality
is actively worked on in the design process.  The draft text is in
good shape and reads cleanly.

The draft authors have addressed most of the issues and concerns from
the GenART review of the -07 version of this draft, but three issues
remain.  I am particularly concerned with the first issue about whether
FCFS is appropriate for these security-related registries, and believe
that topic deserves IESG discussion.  The three issues are ([9], [A] and
[C] are the issue identifiers used on the original Gen-ART review of the
-07 version of this draft):

Major issue:

[9] I suggest Expert Review for the new IANA registries, not just=20
First Come First Served, so that someone with a security "clue" can
check that the proposed registrations are reasonable.

Minor issues:

[A] Overall - I would like to see a paragraph added on how this database
conceptually relates to the IPsec Peer Authorization Database (PAD) -
see RFC 4301, section 4.4.3.

[C] (Section 3) Where does key selection occur?  I would suggest that
the database return all possible keys and let the protocol figure out
what to use.  This is particularly important for inbound traffic for
obvious reasons.

Nits/editorial comments:

First paragraph in 8.1.2 should be at end of 8.1.1.

idnits 2.12.17 found two nits - the latter one (2119 reference/boilerplate)
needs attention:

  ** There are 2 instances of too long lines in the document, the longest o=
ne
     being 6 characters in excess of 72.

  ** The document seems to lack a both a reference to RFC 2119 and the
     recommended RFC 2119 boilerplate, even if it appears to use RFC 2119
     keywords.=20

     RFC 2119 keyword, line 194: '...tion of key material.  The KDF MAY use=
...'
     RFC 2119 keyword, line 196: '... or received but MUST NOT depend on ot=
...'

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 john@jck.com  Fri Aug  9 11:36:38 2013
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 052AF11E8156 for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 11:36: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 CQ3ZUC8jbDjn for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 11:36:31 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDFF11E81B5 for <ietf@ietf.org>; Fri,  9 Aug 2013 11:30:11 -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 1V7rRv-000GZa-FL; Fri, 09 Aug 2013 14:30:07 -0400
Date: Fri, 09 Aug 2013 14:30:02 -0400
From: John C Klensin <john@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: Community Feedback:  IETF Trust Agreement Issues
Message-ID: <49D8ED1A738989CEE231D89B@JcK-HP8200.jck.com>
In-Reply-To: <20130808232000.61327.qmail@joyce.lan>
References: <20130808232000.61327.qmail@joyce.lan>
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: paul.hoffman@vpnc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 18:36:38 -0000

--On Thursday, August 08, 2013 23:20 +0000 John Levine
<johnl@taugh.com> wrote:

>> That sounds right. Someone might want to add commentary (even
>> in English) to the Tao, such as to discuss local
>> participants, diversity, and so on.
> 
> Someone might, or they might rewrite it to say that IETF
> meetings have simultaneous translation, and while the IAB is
> all U.S. greybeards, the IESG members are chosen to represent
> the gender and ethnic balance of the whole world.  Or they
> might rewrite it to say that the IETF has corporate members,
> you have work for one to participate, and all RFCs are
> standards.
>...
> It's extremely hard to let just one of the cat's paws out of
> the bag. In practice either we have change control or we
> don't, and I don't see much sentiment for giving it up to
> unknown CC users.

I have to agree with John Levine about this.  The decision to
move the Tao to a web page didn't change the degree to which we
refer to it as an authoritative document.  As long as we are
going to do that, we need to maintain chance control over
anything pretending to be that document. That view is, IMO,
entirely consistent with the change approval process specified
in RFC 6722.  Also like John, I don't see a problem with CC
BY-ND if someone wants that on some sort of principle.

But I really don't think we should be changing the Trust
agreement in this area unless someone can identify one or more
cases in which there are specific benefits to the IETF from
doing so.  For the reasons above, I don't think the Tao and a CC
license that permits modifications is it.  Indeed, I can more
easily see if for a subset of Independent Stream RFCs rather
than something that the IETF points to as an authority
(disclaimers or not), but we haven't heard a request from the
ISE.

    john


From barryleiba@gmail.com  Fri Aug  9 11:58:04 2013
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 93A1E21F9C00; Fri,  9 Aug 2013 11:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.969
X-Spam-Level: 
X-Spam-Status: No, score=-101.969 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ojtlc+rLrXrz; Fri,  9 Aug 2013 11:58:04 -0700 (PDT)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0F51421F9C38; Fri,  9 Aug 2013 11:53:09 -0700 (PDT)
Received: by mail-qc0-f169.google.com with SMTP id m15so2402182qcq.0 for <multiple recipients>; Fri, 09 Aug 2013 11:52:51 -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:message-id:subject :from:to:cc:content-type; bh=5A3hIr9rYjQLR74jx56tPKbiiWEJMGWkZ1D+kegRyKM=; b=s0tOdotkz0HbwDGPGGwaQetbxqu5qI08qzzRQnX5izUO8u/+bB/pEAYZbXssU1cyhM 962rCGL18bglXFM6861C05NE6xcfvtS0arXrCEl5p4BuZijzXuIyVaAbpwAQot5vykJc FdeBuJUZ6Y4SX+DOj4fKzFfWNArwtMgg8mTZ32G0lZsIYZaAe6b+olk7SdS8xXGq/AYr xk6x262Z0RKZPofDhpkRbLkkWYcd5O3t00LLYiLDuFR1bx7BFquqv85RjbeQ68m5lUXQ N8LKmlxghXlv5hAtrUHh+YUAVj6kmVYO4QgdB65RYS537wGM04L695CXkOchg56NVpwv iKVw==
MIME-Version: 1.0
X-Received: by 10.224.65.3 with SMTP id g3mr12454123qai.42.1376074371078; Fri, 09 Aug 2013 11:52:51 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.224.59.211 with HTTP; Fri, 9 Aug 2013 11:52:51 -0700 (PDT)
In-Reply-To: <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com>
Date: Fri, 9 Aug 2013 20:52:51 +0200
X-Google-Sender-Auth: Vb6FkPvajXby8S1BeRpE1gILHPE
Message-ID: <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Joe Hildebrand <hildjj@cursive.net>, "iesg@ietf.org" <iesg@ietf.org>, 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, 09 Aug 2013 18:58:04 -0000

> * Will CBOR become the default binary JSON encoding?

That would be up to the implementors.  If they like it, they will
implement it and use it in other protocols.  No one is suggesting at
this point that there be any specific direction about that -- it's
being proposed as one possible tool.

> * Will other IETF WGs be expected to adopt CBOR as their binary encoding?

Expected by whom?  By me?  No.  By the IESG?  No.  Whom else are you asking?

> * Will you consider publishing alternative binary encodings of JSON?

Again, as you asked *me*, I'll take the "you" in the question as
referring to me.  Of course I will consider that.  My criteria will be
the same as they are for all requests to sponsor documents: I have to
think it's sensible and useful, I have to see reasonable community
support for publishing, and a good level of review that convinces me
that it meets the guidelines for its intended status.  We have to be
able to get something that can meaningfully be called IETF consensus.

> I accept that there are circumstances where an individual submission is
> appropriate. But I do not think that something that is designed to be built
> on by other IETF Working Groups is appropriate for individual submission.

We actually do that all the time.  As I said in my other response,
AD-sponsorship is not a fast or easy path for a document, skirting
reasonable process by not giving it to a working group.  For simple
registrations and such, keeping things lightweight makes sense.  But
for something such as this (or DMARC, which I'm also considering
AD-sponsoring), I expect a good deal of support and review -- arguably
*more* than we have had with many working group documents.

CBOR was discussed quite a bit on the apps-discuss list and is now
being discussed on the main IETF list.  It doesn't get more open than
this.  And, I'll repeat what I've said before: there are no "short
cuts" being taken here.

To the rest of the community: Does anyone else think it is not
appropriate to publish CBOR as a Proposed Standard, and see who uses
it?

> In this case we have a specification that I am likely going to have to argue
> against as flawed in every WG which might use it.

Yes, I see your arguments, and I appreciate them.  We need that kind
of input.  I'll let the authors continue to address your comments as
they see they need to.  But I'll also ask the rest of the community...

To the rest of the community: What is your view of Phill's technical
arguments with CBOR?  Do you agree that CBOR is flawed?

Now, as I see it, a main argument you have, Phill, is that *no* new
binary encoding should be proposed as a standard without a working
group to study what's there, what's needed, what the goals should be,
and what the right approach is to fulfilling those goals.  Am I
correct?

With that model, the answer that your goals are valid but are
different to ours... would not be a valid one -- we would have to
agree on the goals, and only develop a standard that met that
agreement.  Am I correct?

To the rest of the community: Do you agree with that concern?  Do you
think such an analysis and selection of common goals, leading to one
(or perhaps two) new binary encodings being proposed is what we should
be doing?  Or is it acceptable to have work such as CBOR proposed
without that analysis?

Barry

From carlosm3011@gmail.com  Fri Aug  9 12:36:00 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B948911E81BD for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 12:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.423
X-Spam-Level: 
X-Spam-Status: No, score=-2.423 tagged_above=-999 required=5 tests=[AWL=0.176,  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 Ms08HdzlgZHE for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 12:36:00 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id DEAE611E81D0 for <ietf@ietf.org>; Fri,  9 Aug 2013 12:30:00 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id o10so3419787lbi.40 for <ietf@ietf.org>; Fri, 09 Aug 2013 12:29:59 -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=x80FpaOndgPf4w8A4AgG3pSyybcW5dXI6h0bHKTUcng=; b=nlUmyXkeCTTr0+31mXR8yI0k9Ds5sOtjDGr6pxwRrcViCge5vALdy/qb31Y87mRBc9 mAP20JFrTv8aaazHqKc3b96+d+JPqukTFQJOSy8Smp/YxEG0M50d5G+kgdzktNbPBDko b4AKmVgFX5iG2/a4QGRIzy2ivbgf/4i9p5FH5sUxhbkXLIwOHfcflEWQJBLLawAIsdrO oJyeOk07ThE0QVFz7v6toxoN1vkzbzNjrqVJLOkqXx+tLQf7w8GaOQvzUA6z3HA7/BOK ZmxmscSe1O5H4h+cDBoE10A4dkrzn1MspZq2QkA0oA/H4cD/9c0z03y1qh5iLPRPQKX+ Z5HA==
MIME-Version: 1.0
X-Received: by 10.112.205.106 with SMTP id lf10mr3006177lbc.77.1376076599546;  Fri, 09 Aug 2013 12:29:59 -0700 (PDT)
Received: by 10.112.168.225 with HTTP; Fri, 9 Aug 2013 12:29:59 -0700 (PDT)
In-Reply-To: <89F22F85-B3F1-4A8F-8F09-D32583BEAC02@checkpoint.com>
References: <C2F0EF7B-9069-4A9A-A2DE-3549E8B71A40@gmail.com> <02cd01ce941b$b8561480$4001a8c0@gateway.2wire.net> <27D9955E-5EC9-4B8A-8B5C-EE2C71107EB1@gmail.com> <520403B1.4060607@gmail.com> <AC0B966E-82C6-4687-BAAB-C298804CF87B@vpnc.org> <52040908.6010008@dougbarton.us> <D3F4085E-C504-47A9-BCC1-3C92D03BF289@vpnc.org> <C5091F69-B6CF-442A-9542-9A680924DC51@gmail.com> <89F22F85-B3F1-4A8F-8F09-D32583BEAC02@checkpoint.com>
Date: Fri, 9 Aug 2013 16:29:59 -0300
Message-ID: <CA+z-_EXqepp=BAXXTFaoa2NTKxhS3LN0xxEQGXW7oJUUKi-mNA@mail.gmail.com>
Subject: Re: Community Feedback: IETF Trust Agreement Issues
From: Carlos Martinez-Cagnazzo <carlosm3011@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=001a11c3d70ce657d204e388cccc
Cc: "ietf@ietf.org" <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 19:36:01 -0000

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

Verbatim translation, as I understand from what I hear from my wife (who
works as a professional translator) is where you don't introduce any
semantic changes whatsoever within the reasonable limitations imposed by
the need of mapping between the different languages you're working with.
When translating between European languages this is relatively easy. When
you bring Chinese, Japanese and other Asian languages into the picture, it
gets more complicated.

I think it all boils down to the 'reasonable limitations'. If you give
wings to your poetic flare,  you might get into trouble. If you stick to
the original text, you'll be fine.

This distinction makes more sense when discussing non-technical
translations. In our field, well, there is not a lot of room for poetic
flare.

Cheers!

~Carlos


On Thu, Aug 8, 2013 at 6:59 PM, Yoav Nir <ynir@checkpoint.com> wrote:

>
> On Aug 9, 2013, at 12:21 AM, Jorge Contreras <cntreras@gmail.com> wrote:
>
> >
> >>>
> >>> Can you elaborate on why the license makes a difference?
> >>
> >> We have been told it would make it easier for people to make and
> distribute translations.
> >>
> >> --Paul Hoffman
> >
> > Actually, verbatim translations are already allowed under the existing
> IETF document license. It's other modifications that are not allowed under
> IETF, but which CC-BY would permit.
>
> Interesting. What does "verbatim translation" mean?  Word-for-word? There
> is a reason why searching for "google translate funny" yields 63,000
> results. How much would I be allowed to paraphrase and yet keep within the
> license?
>
> Yoav
>
>


-- 
--
=========================
Carlos M. Martinez-Cagnazzo
h <http://cagnazzo.name>ttp://cagnazzo.me
=========================

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

<div dir=3D"ltr">Verbatim translation, as I understand from what I hear fro=
m my wife (who works as a professional translator) is where you don&#39;t i=
ntroduce any semantic changes whatsoever within the reasonable limitations =
imposed by the need of mapping between the different languages you&#39;re w=
orking with. When translating between European languages this is relatively=
 easy. When you bring Chinese, Japanese and other Asian languages into the =
picture, it gets more complicated.<div>
<br></div><div>I think it all boils down to the &#39;reasonable limitations=
&#39;. If you give wings to your poetic flare, =A0you might get into troubl=
e. If you stick to the original text, you&#39;ll be fine.=A0</div><div><br>
</div><div>This distinction makes more sense when discussing non-technical =
translations. In our field, well, there is not a lot of room for poetic fla=
re.</div><div><br></div><div>Cheers!</div><div><br></div><div>~Carlos</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Aug 8, 2013 at 6:59 PM, Yoav Nir <span dir=3D"ltr">&lt;<a href=3D"mailto:y=
nir@checkpoint.com" target=3D"_blank">ynir@checkpoint.com</a>&gt;</span> wr=
ote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>
On Aug 9, 2013, at 12:21 AM, Jorge Contreras &lt;<a href=3D"mailto:cntreras=
@gmail.com">cntreras@gmail.com</a>&gt; wrote:<br>
<br>
&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Can you elaborate on why the license makes a difference?<br>
&gt;&gt;<br>
&gt;&gt; We have been told it would make it easier for people to make and d=
istribute translations.<br>
&gt;&gt;<br>
&gt;&gt; --Paul Hoffman<br>
&gt;<br>
&gt; Actually, verbatim translations are already allowed under the existing=
 IETF document license. It&#39;s other modifications that are not allowed u=
nder IETF, but which CC-BY would permit.<br>
<br>
</div></div>Interesting. What does &quot;verbatim translation&quot; mean? =
=A0Word-for-word? There is a reason why searching for &quot;google translat=
e funny&quot; yields 63,000 results. How much would I be allowed to paraphr=
ase and yet keep within the license?<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Yoav<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div dir=3D"ltr">--<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Carlos M. Martinez-Cagnazzo<br><a href=3D"ht=
tp://cagnazzo.name" target=3D"_blank">h</a>ttp://<a href=3D"http://cagnazzo=
.me" target=3D"_blank">cagnazzo.me</a><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
</div>
</div>

--001a11c3d70ce657d204e388cccc--

From hallam@gmail.com  Fri Aug  9 13:30:06 2013
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 919FF21F9DAA; Fri,  9 Aug 2013 13:30:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599, 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 ufrSwvlQUNL9; Fri,  9 Aug 2013 13:30:05 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 786DE21F9D04; Fri,  9 Aug 2013 13:23:50 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id k13so3834728wgh.13 for <multiple recipients>; Fri, 09 Aug 2013 13:23:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lZt2kAum6Lhz6sJP+VZLDs6zCLH27vodXKdpafMc3sU=; b=sqO/Ixbmju/+Hxj0FXBksN9R6Qf5OQ6KIMDnBX4/qBsQIB+ObcHV1RRkPq6EVFLWOe pMZU66RIRcwndpVE8etl0hv89CSQWvyPBUbVeTVVb4m4tnhg+MsJH2+Z9LUKuJIxWhQ8 juNsKOZykykvHAIqNvuwxuZtHkMA4LvtyrAS2aWJfzq6s6EIkWNe2eUfZXGNfzaobj7H nMAQ/dRmShIyEiag7c1I7p+rAUOallznftvpKks27BRtZStQ+lylGWF2zGabmi+FIzIF MAWf5MuFGb+rOrHJN5qK/tly9yf7Rw/r1YuQSZeDm85vGbxq624TrOyUii+wNZx47/3v dvqw==
MIME-Version: 1.0
X-Received: by 10.180.95.133 with SMTP id dk5mr1181291wib.33.1376079829481; Fri, 09 Aug 2013 13:23:49 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Fri, 9 Aug 2013 13:23:49 -0700 (PDT)
In-Reply-To: <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
Date: Fri, 9 Aug 2013 16:23:49 -0400
Message-ID: <CAMm+LwgmEYXMroiTjbS8aZg3uihm5bQmTdK-bmV5Fx2t7u4jXg@mail.gmail.com>
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=f46d0444e87f6b418c04e3898da9
Cc: draft-bormann-cbor-04.all@tools.ietf.org, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Aug 2013 20:30:06 -0000

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

On Thu, Aug 8, 2013 at 3:58 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Jul 30, 2013, at 09:05, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
> > What would cause this to be tragic, is if publication of this were
> > used to prevent other work in this area from subsequently being
> > published.
>
> Indeed.
>
> As Paul and I have repeatedly said, CBOR is not trying to be the final,
> definitive, binary object representation for all purposes.  It was written
> to some specific objectives, clearly stated in the document.  It is being
> proposed for standards-track because specific ongoing work that works well
> with these objectives will benefit greatly from being able to reference a
> common specification.  If the objectives for other work are different, that
> work may benefit from using a different format, existing or newly designed.
>

I do not expect you to succeed in being the final definitive format.

But if you are not prepared to try then I don't want the result.


You keep talking about your design requirements, but where are the use
cases that drive them? When I am discussing a specification I am always
referring to illustrative use cases that motivate the requirements. When
you are discussing your spec you wave away every objection by saying it
isn't a design requirement but I have never seen you give the rationale.

Coming back to Martin's comments about the type system. I think that is
what JSON does so well. It has exactly as much type system as is useful and
no more. The developers realized that there was no need to distinguish
lists and sets because both are going to serialize as lists on the wire.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Aug 8, 2013 at 3:58 PM, Carsten Bormann <span dir=3D"ltr">&=
lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;</=
span> wrote:<br>
<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 Jul 30, 2013, at 09:05,=
 Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thom=
son@gmail.com</a>&gt; wrote:<br>

<br>
&gt; What would cause this to be tragic, is if publication of this were<br>
&gt; used to prevent other work in this area from subsequently being<br>
&gt; published.<br>
<br>
</div>Indeed.<br>
<br>
As Paul and I have repeatedly said, CBOR is not trying to be the final, def=
initive, binary object representation for all purposes. =A0It was written t=
o some specific objectives, clearly stated in the document. =A0It is being =
proposed for standards-track because specific ongoing work that works well =
with these objectives will benefit greatly from being able to reference a c=
ommon specification. =A0If the objectives for other work are different, tha=
t work may benefit from using a different format, existing or newly designe=
d.<br>
</blockquote><div><br></div><div>I do not expect you to succeed in being th=
e final definitive format.</div><div><br></div><div>But if you are not prep=
ared to try then I don&#39;t want the result.</div><div><br></div><div>
<br></div><div>You keep talking about your design requirements, but where a=
re the use cases that drive them? When I am discussing a specification I am=
 always referring to illustrative use cases that motivate the requirements.=
 When you are discussing your spec you wave away every objection by saying =
it isn&#39;t a design requirement but I have never seen you give the ration=
ale.</div>
<div><br></div><div>Coming back to Martin&#39;s comments about the type sys=
tem. I think that is what JSON does so well. It has exactly as much type sy=
stem as is useful and no more. The developers realized that there was no ne=
ed to distinguish lists and sets because both are going to serialize as lis=
ts on the wire.=A0</div>
<div>=A0<br></div></div><div><br></div>-- <br>Website: <a href=3D"http://ha=
llambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--f46d0444e87f6b418c04e3898da9--

From martin.thomson@gmail.com  Fri Aug  9 13:30:58 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDEE11E81C4; Fri,  9 Aug 2013 13:30:58 -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.116,  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 TCyscihpdi5X; Fri,  9 Aug 2013 13:30:57 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6668C21F9AB3; Fri,  9 Aug 2013 13:25:52 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id u55so3945581wes.27 for <multiple recipients>; Fri, 09 Aug 2013 13:25:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=X7K14Np5A4GUhrtRGQlO/DwcCmjFzkxprw2F3HfahAQ=; b=ocXzDyvoYSIWRu+OvRw8slJC6j0o2yTHKAGq2yLOrIcis2DSISOhkRx92n5DA92Mft 1MWpLLuP1rrH3CxvlAJ/W9NacwOB8zC0/PTnLFJ4opxkimriR864VW0JqJ1P1b7lpJpq ukn7xGtQhGQ7RXD1vEG4NsBaWIqFD6fV7zw40LDyC+B1deI5/aSQojToz0dkMjSbfvRf VYynGawkHAaB81yE5OY5omwAcs4kG7tc3W3IVYcMRSv3XHHFXrY2qMBcrUmA/PFVyyLT oXEO7PrcPaB+vlbMPQ/c/nogkITtUc0ZISutq2xR2T6PIKwuF3ZsNAxq0upvgrenOj9G WH9g==
MIME-Version: 1.0
X-Received: by 10.180.11.200 with SMTP id s8mr1224604wib.10.1376079951279; Fri, 09 Aug 2013 13:25:51 -0700 (PDT)
Received: by 10.194.28.39 with HTTP; Fri, 9 Aug 2013 13:25:51 -0700 (PDT)
In-Reply-To: <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
Date: Fri, 9 Aug 2013 21:25:51 +0100
Message-ID: <CABkgnnW2LY6s0_EsZMX40Wx8BMNvmsunjRR3EMa-don1rdfRJw@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Martin Thomson <martin.thomson@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=UTF-8
Cc: Joe Hildebrand <hildjj@cursive.net>, "iesg@ietf.org" <iesg@ietf.org>, 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, 09 Aug 2013 20:30:58 -0000

On 9 August 2013 19:52, Barry Leiba <barryleiba@computer.org> wrote:
> To the rest of the community: Does anyone else think it is not
> appropriate to publish CBOR as a Proposed Standard, and see who uses
> it?

I'm ambivalent on this point.  I don't see CBOR as being useful, but I
don't believe that we should be setting the bar for PS so high that
this doesn't meet it.

> To the rest of the community: What is your view of Phill's technical
> arguments with CBOR?  Do you agree that CBOR is flawed?

PHB's comments were valid.  Though I'll point out that a clear
applicability statement is one potential way to allow something like
this to advance without directly addressing those concerns.  I might
prefer that those concerns be addressed directly, but I also want a
pony.

> To the rest of the community: Do you agree with that concern?  Do you
> think such an analysis and selection of common goals, leading to one
> (or perhaps two) new binary encodings being proposed is what we should
> be doing?  Or is it acceptable to have work such as CBOR proposed
> without that analysis?

I'm not 100% convinced either way in this case.  I can see the
potential here for damage in either direction: choose one format and
it might not be applicable in a wide array of valid use cases; or
allow multiple, narrowly-focused formats and end up with no
consistency at all.

(CBOR attempts to cover several branches of the latter case, by
defining a narrowly-focused, but somewhat general-purpose mechanism
that can be arbitrarily extended.)

I'm also highly cynical regarding the ability of a working group to
produce anything that avoids these sorts of problems.  I'm so glad
that I'm not an area director.

From tbray@textuality.com  Fri Aug  9 13:53:16 2013
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 AFD4E11E81AC for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 13:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.809
X-Spam-Level: 
X-Spam-Status: No, score=-2.809 tagged_above=-999 required=5 tests=[AWL=0.167,  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 EB2UqI9VqjUN for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 13:53:07 -0700 (PDT)
Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by ietfa.amsl.com (Postfix) with ESMTP id 54E0E1F0D1A for <ietf@ietf.org>; Fri,  9 Aug 2013 13:46:27 -0700 (PDT)
Received: by mail-lb0-f174.google.com with SMTP id w20so3471206lbh.5 for <ietf@ietf.org>; Fri, 09 Aug 2013 13:46:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=IFR2fOwYe+MrUBtVgS9Ct2jIICXMJm2UQxtUh3gyuK8=; b=oDDMuk20qcmLY0D465TATfSl7OAnLCneO+k65CyjVbXCweUkpJQFVcTN+f67F4dsFX H5Nt/bq0nu8kl/VMB1OOfkyadiYFIcuSfdoz+K5RxzDmejaSdb5XZtO2B/CHsrKSdBPD P0y/iAlCKeNEJ4D88qfR27f/WWidvEDwKk6odIDqzTfh+RaAsFWOfSxRbOMvPu4/lNXD wF6cflLJipVy5XhIJNflasGZm6JKrxiyU7SBmovi6D8w+qYM/yR0Hjn4TQPE1SbSG4h5 cTE9d/k6gWhFt2UI5kqKLkFrvM5sVmQTlVUaXkFahFr+KvdYiIvHjxXl1Bb0HMEi5CZ3 EEzg==
X-Gm-Message-State: ALoCoQm8I8gdfz0/TVbGELhPxFDxF5D1+Hg8g0hWECsUk+REhvso3MaJtqHXNmq6Ra1850QbCwMF
MIME-Version: 1.0
X-Received: by 10.112.198.39 with SMTP id iz7mr5159968lbc.24.1376081184881; Fri, 09 Aug 2013 13:46:24 -0700 (PDT)
Received: by 10.114.175.138 with HTTP; Fri, 9 Aug 2013 13:46:24 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
Date: Fri, 9 Aug 2013 13:46:24 -0700
Message-ID: <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Tim Bray <tbray@textuality.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a11c233ea35115a04e389de80
Cc: Joe Hildebrand <hildjj@cursive.net>, "iesg@ietf.org" <iesg@ietf.org>, 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, 09 Aug 2013 20:53:16 -0000

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

On Fri, Aug 9, 2013 at 11:52 AM, Barry Leiba <barryleiba@computer.org>wrote=
:

> To the rest of the community: Does anyone else think it is not
> appropriate to publish CBOR as a Proposed Standard, and see who uses
> it?
>

I have two moderate concerns:

1. I haven=E2=80=99t seen any particularly convincing evidence that CBOR wo=
uld, in
production, achieve any meaningful reductions in serialization time or
deserialization time or code footprint or memory footprint.
2. I think CBOR does too much; I=E2=80=99d discard half the features and se=
e who
uses *that*.  Well, if it doesn=E2=80=99t take off they can always try CBOR=
-lite
next year.

But I do not see it as actively harmful, am not screaming or lying down in
the road; go ahead and give it an RFC number and see what happens.

I=E2=80=99d also like to compliment Barry on his restraint and courtesy in =
dealing
with Phillip here; far more than I would have been able to muster.

 -T



>
> > In this case we have a specification that I am likely going to have to
> argue
> > against as flawed in every WG which might use it.
>
> Yes, I see your arguments, and I appreciate them.  We need that kind
> of input.  I'll let the authors continue to address your comments as
> they see they need to.  But I'll also ask the rest of the community...
>
> To the rest of the community: What is your view of Phill's technical
> arguments with CBOR?  Do you agree that CBOR is flawed?
>
> Now, as I see it, a main argument you have, Phill, is that *no* new
> binary encoding should be proposed as a standard without a working
> group to study what's there, what's needed, what the goals should be,
> and what the right approach is to fulfilling those goals.  Am I
> correct?
>
> With that model, the answer that your goals are valid but are
> different to ours... would not be a valid one -- we would have to
> agree on the goals, and only develop a standard that met that
> agreement.  Am I correct?
>
> To the rest of the community: Do you agree with that concern?  Do you
> think such an analysis and selection of common goals, leading to one
> (or perhaps two) new binary encodings being proposed is what we should
> be doing?  Or is it acceptable to have work such as CBOR proposed
> without that analysis?
>
> Barry
>

--001a11c233ea35115a04e389de80
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Aug 9, 2013 at 11:52 AM, Barry Leiba <span dir=3D"=
ltr">&lt;<a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barry=
leiba@computer.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">To the rest of the community: Does anyone el=
se think it is not<br>
appropriate to publish CBOR as a Proposed Standard, and see who uses<br>
it?<br></blockquote><div><br></div><div>I have two moderate concerns:<br><b=
r>1. I haven=E2=80=99t seen any particularly convincing evidence that CBOR =
would, in production, achieve any meaningful reductions in serialization ti=
me or deserialization time or code footprint or memory footprint.<br>
</div><div>2. I think CBOR does too much; I=E2=80=99d discard half the feat=
ures and see who uses *that*.=C2=A0 Well, if it doesn=E2=80=99t take off th=
ey can always try CBOR-lite next year.<br><br>But I do not see it as active=
ly harmful, am not screaming or lying down in the road; go ahead and give i=
t an RFC number and see what happens.<br>
<br>I=E2=80=99d also like to compliment Barry on his restraint and courtesy=
 in dealing with Phillip here; far more than I would have been able to must=
er.<br><br>=C2=A0-T<br></div><div><br>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">

<br>
&gt; In this case we have a specification that I am likely going to have to=
 argue<br>
&gt; against as flawed in every WG which might use it.<br>
<br>
Yes, I see your arguments, and I appreciate them. =C2=A0We need that kind<b=
r>
of input. =C2=A0I&#39;ll let the authors continue to address your comments =
as<br>
they see they need to. =C2=A0But I&#39;ll also ask the rest of the communit=
y...<br>
<br>
To the rest of the community: What is your view of Phill&#39;s technical<br=
>
arguments with CBOR? =C2=A0Do you agree that CBOR is flawed?<br>
<br>
Now, as I see it, a main argument you have, Phill, is that *no* new<br>
binary encoding should be proposed as a standard without a working<br>
group to study what&#39;s there, what&#39;s needed, what the goals should b=
e,<br>
and what the right approach is to fulfilling those goals. =C2=A0Am I<br>
correct?<br>
<br>
With that model, the answer that your goals are valid but are<br>
different to ours... would not be a valid one -- we would have to<br>
agree on the goals, and only develop a standard that met that<br>
agreement. =C2=A0Am I correct?<br>
<br>
To the rest of the community: Do you agree with that concern? =C2=A0Do you<=
br>
think such an analysis and selection of common goals, leading to one<br>
(or perhaps two) new binary encodings being proposed is what we should<br>
be doing? =C2=A0Or is it acceptable to have work such as CBOR proposed<br>
without that analysis?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Barry<br>
</font></span></blockquote></div><br></div></div>

--001a11c233ea35115a04e389de80--

From hallam@gmail.com  Fri Aug  9 14:03:35 2013
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 C8F5D21E8087; Fri,  9 Aug 2013 14:03:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.513
X-Spam-Level: 
X-Spam-Status: No, score=-2.513 tagged_above=-999 required=5 tests=[AWL=0.087,  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 Wb2nyVE32Val; Fri,  9 Aug 2013 14:03:34 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id CA60C21F9D89; Fri,  9 Aug 2013 13:57:00 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id t57so900939wes.38 for <multiple recipients>; Fri, 09 Aug 2013 13:57: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=dYrhVJ7+1CvlSak/8ZbNMVjKnBt/g9Uh+OU+wSqxRKM=; b=mt+OanSnplZ749q+OzbWrkRYFbFZe2H9nt82XWEaY6imUT3bnbcmmbyqbf+VBQftS5 WJtukHe+oQBi8u/E9kJqs+RKG5mMc3REgPRcu3dcH4JzhX0f3FyBLTtIEVlhRhryGeBe jTGVPJKFs+YDy6oaui3vYnjvqPAlU/dmjglrBpX5lEteY7sFDkH5hL1H3xTky/nzthCl UdQ5SMXGniflSMHYWz1QJpc84/GOSkgzaIMlV8qFqfePCClO76oykU0ftLL+6v4M0pw8 cJcxwACvbv3qoBoTO+GDR7my2kNltfLszeW/1zr05GYxeheuzPkspOI7RLZ6TMYuWVdi nNog==
MIME-Version: 1.0
X-Received: by 10.180.10.99 with SMTP id h3mr1318821wib.0.1376081819942; Fri, 09 Aug 2013 13:56:59 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Fri, 9 Aug 2013 13:56:59 -0700 (PDT)
In-Reply-To: <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
Date: Fri, 9 Aug 2013 16:56:59 -0400
Message-ID: <CAMm+Lwj2TuBTOB75bFaz+BwzwmZ49zeU7aDwKKH1SopkQ7YYzA@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a11c260160f454b04e38a044e
Cc: Joe Hildebrand <hildjj@cursive.net>, "iesg@ietf.org" <iesg@ietf.org>, 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, 09 Aug 2013 21:03:35 -0000

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

On Fri, Aug 9, 2013 at 2:52 PM, Barry Leiba <barryleiba@computer.org> wrote:

> > * Will CBOR become the default binary JSON encoding?
>
> That would be up to the implementors.  If they like it, they will
> implement it and use it in other protocols.  No one is suggesting at
> this point that there be any specific direction about that -- it's
> being proposed as one possible tool.
>
> > * Will other IETF WGs be expected to adopt CBOR as their binary encoding?
>
> Expected by whom?  By me?  No.  By the IESG?  No.  Whom else are you
> asking?


Actually I just want it in writing because my past experience of a similar
platform type spec was that it was just another option for developers right
up to the point where it was published when I found myself in a BOF where
the members were being told that they 'had' to use the IETF platform for
their work because that is what had been 'decided'.

Understand here that I am not accusing you Barry of doing that but you
won't be AD forever.



> > * Will you consider publishing alternative binary encodings of JSON?
>
> Again, as you asked *me*, I'll take the "you" in the question as
> referring to me.  Of course I will consider that.  My criteria will be
> the same as they are for all requests to sponsor documents: I have to
> think it's sensible and useful, I have to see reasonable community
> support for publishing, and a good level of review that convinces me
> that it meets the guidelines for its intended status.  We have to be
> able to get something that can meaningfully be called IETF consensus.


During the discussions there was a clear subset who wanted to have JSON
plus length encoded binary blobs/unicode strings as opposed to CBOR. Would
publication of CBOR as a proposed standard make it less likely that such a
proposal would be acceptable to you?



> > I accept that there are circumstances where an individual submission is
> > appropriate. But I do not think that something that is designed to be
> built
> > on by other IETF Working Groups is appropriate for individual submission.
>
> We actually do that all the time.  As I said in my other response,
> AD-sponsorship is not a fast or easy path for a document, skirting
> reasonable process by not giving it to a working group.  For simple
> registrations and such, keeping things lightweight makes sense.  But
> for something such as this (or DMARC, which I'm also considering
> AD-sponsoring), I expect a good deal of support and review -- arguably
> *more* than we have had with many working group documents.
>

I don't see DMARC as being the same as CBOR.

DMARC is primarily a mechanism that has standalone value that is built on
top of S/MIME. CBOR is a proposal that has no value unless other people
choose to build on top of it.



> CBOR was discussed quite a bit on the apps-discuss list and is now
> being discussed on the main IETF list.  It doesn't get more open than
> this.  And, I'll repeat what I've said before: there are no "short
> cuts" being taken here.
>

The proposers have maintained full proprietary control of the spec at all
times. They are the only arbiters of what they consider to be the
appropriate design goals. I don't consider the opportunity to state my
complaints to be participation.


Now, as I see it, a main argument you have, Phill, is that *no* new
> binary encoding should be proposed as a standard without a working
> group to study what's there, what's needed, what the goals should be,
> and what the right approach is to fulfilling those goals.  Am I
> correct?
>

I think that nothing should be described as an IETF Proposed STANDARD
unless the IETF proposes to use it. I know that the process document is
loosey-goosey on this but I think that until someone takes CBOR and uses it
as a part of a mousetrap that it isn't going to be an IETF proposed
standard regardless of what it says on the RFC.

Publishing a fully specified but untried proposal as EXPERIMENTAL would
seem to me to be exactly the right course for this type of thing. It is
what we are currently doing in HTTP Authentication mechanisms. If any get
traction they can be promoted to Proposed Standard.

I think that the bar to getting something published as a static document
should be pretty low. But the bar for standards track is a little
different.



> With that model, the answer that your goals are valid but are
> different to ours... would not be a valid one -- we would have to
> agree on the goals, and only develop a standard that met that
> agreement.  Am I correct?
>

I think that the design goals have to be decided with respect to use cases.
I have use cases driven by running code. I don't know what the use cases
are that drive the CBOR design requirements. All I know is that whenever a
proposal is made that Carsten and Paul don't like their response is 'that
is not one of our design goals'.

It might well be that there is a need for more than one binary encoding. It
is possible that my desire to have a binary encoding that can be formally
shown to be equivalent to JSON is not what people want. It might be that
people really do want to have a binary encoding that has the rich type
system of CBOR. There might even be more niches that need to be filled.


But my preferred process would be this

1) Publish any proposal that is fully described as Experimental

2) Wait

3) When the first WG that is going to use a binary encoding of JSON is
ready to emit a specification, revisit the question of which format(s) to
make a standard. If there are multiple groups that have decided to use
different formats we should find out why and if there are sound reasons,
that might lead to yet another format or it might mean that there really is
a need for more than one. If there are multiple groups that have all chosen
the same one then we have a winner. If there is only one group, well make
their choice Proposed Standard and see if path dependence kicks in.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 9, 2013 at 2:52 PM, Barry Leiba <span dir=3D"ltr">&lt;<=
a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryleiba@comp=
uter.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; * Will CBOR become th=
e default binary JSON encoding?<br>
<br>
</div>That would be up to the implementors. =A0If they like it, they will<b=
r>
implement it and use it in other protocols. =A0No one is suggesting at<br>
this point that there be any specific direction about that -- it&#39;s<br>
being proposed as one possible tool.<br>
<div class=3D"im"><br>
&gt; * Will other IETF WGs be expected to adopt CBOR as their binary encodi=
ng?<br>
<br>
</div>Expected by whom? =A0By me? =A0No. =A0By the IESG? =A0No. =A0Whom els=
e are you asking?</blockquote><div><br></div><div>Actually I just want it i=
n writing because my past experience of a similar platform type spec was th=
at it was just another option for developers right up to the point where it=
 was published when I found myself in a BOF where the members were being to=
ld that they &#39;had&#39; to use the IETF platform for their work because =
that is what had been &#39;decided&#39;.</div>
<div><br></div><div>Understand here that I am not accusing you Barry of doi=
ng that but you won&#39;t be AD forever.</div><div><br></div><div>=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im">
&gt; * Will you consider publishing alternative binary encodings of JSON?<b=
r>
<br>
</div>Again, as you asked *me*, I&#39;ll take the &quot;you&quot; in the qu=
estion as<br>
referring to me. =A0Of course I will consider that. =A0My criteria will be<=
br>
the same as they are for all requests to sponsor documents: I have to<br>
think it&#39;s sensible and useful, I have to see reasonable community<br>
support for publishing, and a good level of review that convinces me<br>
that it meets the guidelines for its intended status. =A0We have to be<br>
able to get something that can meaningfully be called IETF consensus.</bloc=
kquote><div><br></div><div>During the discussions there was a clear subset =
who wanted to have JSON plus length encoded binary blobs/unicode strings as=
 opposed to CBOR. Would publication of CBOR as a proposed standard make it =
less likely that such a proposal would be acceptable to you?</div>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"i=
m">
&gt; I accept that there are circumstances where an individual submission i=
s<br>
&gt; appropriate. But I do not think that something that is designed to be =
built<br>
&gt; on by other IETF Working Groups is appropriate for individual submissi=
on.<br>
<br>
</div>We actually do that all the time. =A0As I said in my other response,<=
br>
AD-sponsorship is not a fast or easy path for a document, skirting<br>
reasonable process by not giving it to a working group. =A0For simple<br>
registrations and such, keeping things lightweight makes sense. =A0But<br>
for something such as this (or DMARC, which I&#39;m also considering<br>
AD-sponsoring), I expect a good deal of support and review -- arguably<br>
*more* than we have had with many working group documents.<br></blockquote>=
<div><br></div><div>I don&#39;t see DMARC as being the same as CBOR.</div><=
div><br></div><div>DMARC is primarily a mechanism that has standalone value=
 that is built on top of S/MIME. CBOR is a proposal that has no value unles=
s other people choose to build on top of it.</div>
<div><br></div><div>=A0<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
CBOR was discussed quite a bit on the apps-discuss list and is now<br>
being discussed on the main IETF list. =A0It doesn&#39;t get more open than=
<br>
this. =A0And, I&#39;ll repeat what I&#39;ve said before: there are no &quot=
;short<br>
cuts&quot; being taken here.<br></blockquote><div><br></div><div>The propos=
ers have maintained full proprietary control of the spec at all times. They=
 are the only arbiters of what they consider to be the appropriate design g=
oals. I don&#39;t consider the opportunity to state my complaints to be par=
ticipation.</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Now, as I see it, a main argument you have, Phill, is that *no* new<br>
binary encoding should be proposed as a standard without a working<br>
group to study what&#39;s there, what&#39;s needed, what the goals should b=
e,<br>
and what the right approach is to fulfilling those goals. =A0Am I<br>
correct?<br></blockquote><div><br></div><div>I think that nothing should be=
 described as an IETF Proposed STANDARD unless the IETF proposes to use it.=
 I know that the process document is loosey-goosey on this but I think that=
 until someone takes CBOR and uses it as a part of a mousetrap that it isn&=
#39;t going to be an IETF proposed standard regardless of what it says on t=
he RFC.</div>
<div><br></div><div>Publishing a fully specified but untried proposal as EX=
PERIMENTAL would seem to me to be exactly the right course for this type of=
 thing. It is what we are currently doing in HTTP Authentication mechanisms=
. If any get traction they can be promoted to Proposed Standard.</div>
<div><br></div><div>I think that the bar to getting something published as =
a static document should be pretty low. But the bar for standards track is =
a little different.=A0</div><div><br></div><div>=A0<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">

With that model, the answer that your goals are valid but are<br>
different to ours... would not be a valid one -- we would have to<br>
agree on the goals, and only develop a standard that met that<br>
agreement. =A0Am I correct?<br></blockquote><div><br></div><div>I think tha=
t the design goals have to be decided with respect to use cases. I have use=
 cases driven by running code. I don&#39;t know what the use cases are that=
 drive the CBOR design requirements. All I know is that whenever a proposal=
 is made that Carsten and Paul don&#39;t like their response is &#39;that i=
s not one of our design goals&#39;.</div>
<div><br></div><div>It might well be that there is a need for more than one=
 binary encoding. It is possible that my desire to have a binary encoding t=
hat can be formally shown to be equivalent to JSON is not what people want.=
 It might be that people really do want to have a binary encoding that has =
the rich type system of CBOR. There might even be more niches that need to =
be filled.</div>
<div><br></div></div><div><br></div><div>But my preferred process would be =
this</div><div><br></div><div>1) Publish any proposal that is fully describ=
ed as Experimental</div><div><br></div><div>2) Wait</div><div><br></div>
<div>3) When the first WG that is going to use a binary encoding of JSON is=
 ready to emit a specification, revisit the question of which format(s) to =
make a standard. If there are multiple groups that have decided to use diff=
erent formats we should find out why and if there are sound reasons, that m=
ight lead to yet another format or it might mean that there really is a nee=
d for more than one. If there are multiple groups that have all chosen the =
same one then we have a winner. If there is only one group, well make their=
 choice Proposed Standard and see if path dependence kicks in.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c260160f454b04e38a044e--

From hallam@gmail.com  Fri Aug  9 14:18:14 2013
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 CAF0B21F9D2A; Fri,  9 Aug 2013 14:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, 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 ptzmJ3P1qwI2; Fri,  9 Aug 2013 14:18:14 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id E217D21F9D04; Fri,  9 Aug 2013 14:12:40 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e12so4014628wgh.9 for <multiple recipients>; Fri, 09 Aug 2013 14:12: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=0If7994XqRNiZGrG0W/nTRjKC9GpqZbmKgZs4bhS8FM=; b=AzInsh9kZe1In05Xr5trGEJtUye+zcp0JQxSrbZ+3+1sExNCAov5QcP42DUmIioWoZ wdNrE8fwv5WbFMSZFEewiYTX0CzeT9qNhIuUdad1hmLnqIfjzmu8JAljgeWjOBTlIe7/ B4MjFJ3KM91eKFbRAKdFoGb4QTtd6WTJ7ZdqfE5y9tDZFLrzGOrDD44/MIq0t0XN8Keo /GP5I/K1OAbgTBsaHt4Qo2QSNodGngROX1eJ5ITRYOOnTq+Tj7aMZwF2W5J2cWIb2ncy Slkj53gYsNwbkK3/NnsgMZ+QaV9rA51b2jQGV2PLE1dYpbo+FoGKqT3P/5E6KTCHZ5WW LR+w==
MIME-Version: 1.0
X-Received: by 10.180.10.99 with SMTP id h3mr1347296wib.0.1376082758777; Fri, 09 Aug 2013 14:12:38 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Fri, 9 Aug 2013 14:12:38 -0700 (PDT)
In-Reply-To: <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com>
Date: Fri, 9 Aug 2013 17:12:38 -0400
Message-ID: <CAMm+LwjmZu2Gw9aHAfT_81QxASTyG2i64b06gkdp6z+yOfKxSQ@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: multipart/alternative; boundary=001a11c2601604c2f804e38a3c78
Cc: Joe Hildebrand <hildjj@cursive.net>, Barry Leiba <barryleiba@computer.org>, "iesg@ietf.org" <iesg@ietf.org>, 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, 09 Aug 2013 21:18:15 -0000

--001a11c2601604c2f804e38a3c78
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 9, 2013 at 4:46 PM, Tim Bray <tbray@textuality.com> wrote:

> On Fri, Aug 9, 2013 at 11:52 AM, Barry Leiba <barryleiba@computer.org>wro=
te:
>
>> To the rest of the community: Does anyone else think it is not
>> appropriate to publish CBOR as a Proposed Standard, and see who uses
>> it?
>>
>
> I have two moderate concerns:
>
> 1. I haven=92t seen any particularly convincing evidence that CBOR would,=
 in
> production, achieve any meaningful reductions in serialization time or
> deserialization time or code footprint or memory footprint.
> 2. I think CBOR does too much; I=92d discard half the features and see wh=
o
> uses *that*.  Well, if it doesn=92t take off they can always try CBOR-lit=
e
> next year.
>
> But I do not see it as actively harmful, am not screaming or lying down i=
n
> the road; go ahead and give it an RFC number and see what happens.
>
> I=92d also like to compliment Barry on his restraint and courtesy in deal=
ing
> with Phillip here; far more than I would have been able to muster.
>

Tim, if you want to slam other people on the list, please have the courtesy
to do so directly. Are you really upset about what I said to Barry or what
I said about the defects in the XML specification you led?


The reason I directed those questions at Barry is that I had previously
asked them in private and received no response. I also want the answers to
be on the record. An applicability statement would be a good plan.

The issue here is not whether or not CBOR gets an RFC number but whether
issuing that RFC number means that those of us who made alternative
proposals for a binary encoding are being foreclosed on.

And it does seem rather odd that while I am being told that there are two
opportunities to challenge a Personal Submission, on the initial list and
the IETF list, that I then get criticized for raising the issues on the
IETF list.

For the record, I thought that there was a lot of skepticism about CBOR
from the start. There is certainly a consensus in support of CBOR among
supporters of CBOR but at least half the commenters were negative and the
fundamental question of why CBOR versus a binary version of JSON encoding
was never answered.


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

--001a11c2601604c2f804e38a3c78
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Aug 9, 2013 at 4:46 PM, Tim Bray <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textua=
lity.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"im">On Fri, A=
ug 9, 2013 at 11:52 AM, Barry Leiba <span dir=3D"ltr">&lt;<a href=3D"mailto=
:barryleiba@computer.org" target=3D"_blank">barryleiba@computer.org</a>&gt;=
</span> wrote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"i=
m">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">To the rest of the community: Does anyone el=
se think it is not<br>
appropriate to publish CBOR as a Proposed Standard, and see who uses<br>
it?<br></blockquote><div><br></div></div><div>I have two moderate concerns:=
<br><br>1. I haven=92t seen any particularly convincing evidence that CBOR =
would, in production, achieve any meaningful reductions in serialization ti=
me or deserialization time or code footprint or memory footprint.<br>

</div><div>2. I think CBOR does too much; I=92d discard half the features a=
nd see who uses *that*.=A0 Well, if it doesn=92t take off they can always t=
ry CBOR-lite next year.<br><br>But I do not see it as actively harmful, am =
not screaming or lying down in the road; go ahead and give it an RFC number=
 and see what happens.<br>

<br>I=92d also like to compliment Barry on his restraint and courtesy in de=
aling with Phillip here; far more than I would have been able to muster.</d=
iv></div></div></div></blockquote><div><br></div><div>Tim, if you want to s=
lam other people on the list, please have the courtesy to do so directly. A=
re you really upset about what I said to Barry or what I said about the def=
ects in the XML specification you led?</div>
<div><br></div><div><br></div><div>The reason I directed those questions at=
 Barry is that I had previously asked them in private and received no respo=
nse. I also want the answers to be on the record. An applicability statemen=
t would be a good plan.</div>
<div><br></div><div>The issue here is not whether or not CBOR gets an RFC n=
umber but whether issuing that RFC number means that those of us who made a=
lternative proposals for a binary encoding are being foreclosed on.=A0</div=
>
<div><br></div><div>And it does seem rather odd that while I am being told =
that there are two opportunities to challenge a Personal Submission, on the=
 initial list and the IETF list, that I then get criticized for raising the=
 issues on the IETF list.</div>
</div><br clear=3D"all"><div>For the record, I thought that there was a lot=
 of skepticism about CBOR from the start. There is certainly a consensus in=
 support of CBOR among supporters of CBOR but at least half the commenters =
were negative and the fundamental question of why CBOR versus a binary vers=
ion of JSON encoding was never answered.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2601604c2f804e38a3c78--

From cabo@tzi.org  Fri Aug  9 17:48:05 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA07C21F99B7; Fri,  9 Aug 2013 17:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[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 tTOy21im0pU6; Fri,  9 Aug 2013 17:48:00 -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 B3F861F0D61; Fri,  9 Aug 2013 17:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7A0gAEB026761; Sat, 10 Aug 2013 02:42:10 +0200 (CEST)
Received: from [192.168.217.105] (p54890C7C.dip0.t-ipconnect.de [84.137.12.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 774176CB; Sat, 10 Aug 2013 02:42:10 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com>
Date: Sat, 10 Aug 2013 02:42:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E30E660-C76A-4120-91CF-60C42B4DB41E@tzi.org>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1508)
Cc: iesg@ietf.org, 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, 10 Aug 2013 00:48:05 -0000

> 1. I haven=92t seen any particularly convincing evidence that CBOR =
would, in production, achieve any meaningful reductions in serialization =
time or deserialization time or code footprint or memory footprint.

I'm not sure relative to what you want to see that reduction.

But let me give you a real-world example.

Look at section 6.3.3 of the OMA Lightweight M2M Technical =
Specification.
This defines a TLV format for multiple-instance resources (whatever that =
means is not very relevant in this context).  This format is becoming a =
bit complicated because this is trying to be efficient (in the number of =
bytes needed).  Being designed from scratch, it also has certain =
functional deficiencies I don't want to go into here.

If you look closely behind the complexity created by the desire to be =
efficient, this is actually just a map of maps.  The CBOR representation =
of that is just as efficient (probably slightly more so) as the bespoke =
encoding specifically invented for this.  Apart from the direct gains in =
simplicity and efficiency, in an implementation, the CBOR code is likely =
to be shared and more polished than the bespoke code for this, so there =
are likely to be more gains in code size and performance.

Specialized binary formats like this TLV format are invented a dozen a =
day all over the industry.
Each of them has their own little set of unwarranted complexities, =
bizarre features, and little bugs waiting to explode in the face of =
their users.
Rationalizing some of them to a common base like CBOR will be a major =
win.
(Justifiably or not, JSON isn't even in the starting block for many of =
them.)

> 2. I think CBOR does too much; I=92d discard half the features and see =
who uses *that*.  Well, if it doesn=92t take off they can always try =
CBOR-lite next year.

In order to address use cases such as the above, CBOR has to have a =
certain amount of capabilities.
It is indeed a judgment call which capabilities should be included in =
the standard.
Feedback from people who want to use this in the IETF has led to a =
little bit of growth compared to the original proposal, but only =
moderately so.

Gr=FC=DFe, Carsten


From Ted.Lemon@nominum.com  Fri Aug  9 18:11:40 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2832511E810B for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 18:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.565
X-Spam-Level: 
X-Spam-Status: No, score=-106.565 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNH3ffeANwGW for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 18:11:33 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id B920621F9EFC for <ietf@ietf.org>; Fri,  9 Aug 2013 18:04:22 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUgWRlpTX1gx8LScRDk590Rw+EgsxNq20@postini.com; Fri, 09 Aug 2013 18:04:22 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D5DC71B828B for <ietf@ietf.org>; Fri,  9 Aug 2013 18:04:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8A476190060; Fri,  9 Aug 2013 18:04:20 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 9 Aug 2013 18:04:20 -0700
Content-Type: multipart/alternative; boundary="Apple-Mail=_3FBCBC46-447E-42B0-892E-2C1AC5194066"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAMm+Lwj2TuBTOB75bFaz+BwzwmZ49zeU7aDwKKH1SopkQ7YYzA@mail.gmail.com>
Date: Fri, 9 Aug 2013 21:04:17 -0400
Message-ID: <CCB7CF30-1FB7-47C7-A863-CA702D1C3D68@nominum.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <CAMm+Lwj2TuBTOB75bFaz+BwzwmZ49zeU7aDwKKH1SopkQ7YYzA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
Cc: Joe Hildebrand <hildjj@cursive.net>, Barry Leiba <barryleiba@computer.org>, IETF Discussion Mailing List <ietf@ietf.org>, "iesg@" <ietf.orgiesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Aug 2013 01:11:40 -0000

--Apple-Mail=_3FBCBC46-447E-42B0-892E-2C1AC5194066
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"

On Aug 9, 2013, at 4:56 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:
> Actually I just want it in writing because my past experience of a =
similar platform type spec was that it was just another option for =
developers right up to the point where it was published when I found =
myself in a BOF where the members were being told that they 'had' to use =
the IETF platform for their work because that is what had been =
'decided'.

People say that a lot.   It's true that code reuse is an argument in =
favor of doing one thing over another, but there are lots of other =
relevant arguments, not the least of which is "it doesn't work well."   =
This second argument carries just as much weight as the first.   The =
bottom line is that there is nothing the IESG can do to prevent people =
from making this claim, but working group chairs should understand that =
it is not binding=97it's just one thing to consider among many.

I recommend reading RFC 1958.


--Apple-Mail=_3FBCBC46-447E-42B0-892E-2C1AC5194066
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="windows-1252"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Aug =
9, 2013, at 4:56 PM, Phillip Hallam-Baker &lt;<a =
href=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt; =
wrote:<div><blockquote type=3D"cite"><div style=3D"font-family: =
Optima-Regular; font-size: 14px; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">Actually I just want it in writing =
because my past experience of a similar platform type spec was that it =
was just another option for developers right up to the point where it =
was published when I found myself in a BOF where the members were being =
told that they 'had' to use the IETF platform for their work because =
that is what had been 'decided'.</div></blockquote><br></div><div>People =
say that a lot. &nbsp; It's true that code reuse is an argument in favor =
of doing one thing over another, but there are lots of other relevant =
arguments, not the least of which is "it doesn't work well." &nbsp; This =
second argument carries just as much weight as the first. &nbsp; The =
bottom line is that there is nothing the IESG can do to prevent people =
from making this claim, but working group chairs should understand that =
it is not binding=97it's just one thing to consider among =
many.</div><div><br></div><div>I recommend reading RFC =
1958.</div><div><br></div></body></html>=

--Apple-Mail=_3FBCBC46-447E-42B0-892E-2C1AC5194066--

From stephen.farrell@cs.tcd.ie  Fri Aug  9 18:15:52 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52EE721F9C0E for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 18:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNgInQa7YaB9 for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 18:15:45 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id E2BB021F9D21 for <ietf@ietf.org>; Fri,  9 Aug 2013 18:09:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8DEA7BE3E; Sat, 10 Aug 2013 02:09:43 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m06Uzco+g37t; Sat, 10 Aug 2013 02:09:42 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.41.52.85]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 87858BE33; Sat, 10 Aug 2013 02:09:42 +0100 (IST)
Message-ID: <520592CC.3080701@cs.tcd.ie>
Date: Sat, 10 Aug 2013 02:09:32 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com> <6E30E660-C76A-4120-91CF-60C42B4DB41E@tzi.org>
In-Reply-To: <6E30E660-C76A-4120-91CF-60C42B4DB41E@tzi.org>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 10 Aug 2013 01:15:52 -0000

Hi Carsten,

As a no-hats, IETF-LC comment...

On 08/10/2013 01:42 AM, Carsten Bormann wrote:
> 
> Specialized binary formats like this TLV format are invented a dozen a day all over the industry.
> Each of them has their own little set of unwarranted complexities, bizarre features, and little bugs waiting to explode in the face of their users.
> Rationalizing some of them to a common base like CBOR will be a major win.

That, and some of the IETF LC discussion reminds me of BEEP. [1]
While CBOR also seems sensible, maybe being sensible isn't
sufficient for stuff like this.

So some kind of statement that CBOR is one point in a design
space (as opposed to an optimal solution for some set of
design objectives) would be worthwhile. (Or even to make it
EXP and not PS, but to be honest I don't care much about
that distinction here.)

S.

[1] http://tools.ietf.org/html/rfc3080

From dhc@dcrocker.net  Fri Aug  9 19:40:27 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78DBC11E812F for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 19:40: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 deCOiZ0tBdV6 for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 19:40:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 295FA11E8136 for <ietf@ietf.org>; Fri,  9 Aug 2013 19:34:12 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7A2XukS003048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 9 Aug 2013 19:34:00 -0700
Message-ID: <5205A68D.2020403@dcrocker.net>
Date: Fri, 09 Aug 2013 19:33:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com> <6E30E660-C76A-4120-91CF-60C42B4DB41E@tzi.org> <520592CC.3080701@cs.tcd.ie>
In-Reply-To: <520592CC.3080701@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 09 Aug 2013 19:34:00 -0700 (PDT)
Cc: Carsten Bormann <cabo@tzi.org>, IETF Discussion Mailing 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, 10 Aug 2013 02:40:27 -0000

On 8/9/2013 6:09 PM, Stephen Farrell wrote:
> So some kind of statement that CBOR is one point in a design
> space (as opposed to an optimal solution for some set of
> design objectives) would be worthwhile.


huh?  a statement beyond the opening sentence of the introduction and 
its third paragraph?

worthwhile to whom and for what?  it's a spec (or perhaps a meta-spec.) 
  it provides a capability.  it needs to specify the what and how well 
enough to be usable.

while ietf culture permits specifications to have quite a variety of 
commentary, historical or contextual discussion is not an essential part 
of the document, and certainly not discussion cast in a manner to 
denigrate the current spec.

Counter-marketing that has the current spec self-deprecatingly casting 
itself as  only one of many seems mostly worthwhile to get people to 
avoid using it.

exp makes sense if there is doubt that it is technically workable, not 
because its success in the market is questionable.  we give ps all the 
time to specs that have little clear market and go on gain small market use.

from what i've seen, this is a carefully researched and crafted 
mechanism and i haven't noted anyone challenging it on basic technical 
grounds.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From sustrik@250bpm.com  Fri Aug  9 22:48:01 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E234D21F9EDB for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 22:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ph-va5esfN2w for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 22:47:56 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8E5B921F9D9A for <ietf@ietf.org>; Fri,  9 Aug 2013 22:43:27 -0700 (PDT)
Received: from [192.168.0.102] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id A39DD180354D for <ietf@ietf.org>; Sat, 10 Aug 2013 07:43:23 +0200 (CEST)
Message-ID: <5205D2FB.8010205@250bpm.com>
Date: Sat, 10 Aug 2013 07:43:23 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: TCPMUX (RFC 1078) status
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Aug 2013 05:48:02 -0000

Hi all,

Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol used? 
Is it the case that there are inetd daemons in TCPMUX mode running 
everywhere, or can it be rather considered a dead protocol?

Specifically, if I implement a new TCPMUX daemon how likely I am to 
clash with an existing TCPMUX daemon listening on port 1?

Martin

From yaronf.ietf@gmail.com  Fri Aug  9 23:52:11 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF1D11E8145 for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 23:52: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 QBGJGjKouaWh for <ietf@ietfa.amsl.com>; Fri,  9 Aug 2013 23:52:10 -0700 (PDT)
Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5B10821F9CAF for <ietf@ietf.org>; Fri,  9 Aug 2013 23:47:04 -0700 (PDT)
Received: by mail-ee0-f44.google.com with SMTP id b47so2507537eek.3 for <ietf@ietf.org>; Fri, 09 Aug 2013 23:47:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wtSngYg+c5QtWrpJtXY76qHTp7E2o+0oUsHnH9DjNP0=; b=ju6eBIzXVLnx9UHkPiFidxQhwu7oZKJTxV0VFpWZjcY0WflTCwsncCwLq9tg10GOx3 dUfPdGVpOZcdZ8ckK87cQTUXTUDLreYA8kHbBsVhZyuSreiRk0IDNVZYO08adysu0wMd vE+gblH6ccVRLoDXR5wnM0/zgC/gBRW/MT5gAK6FJusquLvplatZP+JNafGDOD1VqmtN tzwkpZtUl0P+BuGMxVYD86Y991SYr0bqlD8VtBvFtMImxi0g1BRyb43aRexXPhneziBK 3COQ1rS+9R3JOIobbU4YXtvR/VdfUscVywhhD5VSOMfg3Bk9Oarxm0qRVQ1meOvrwOBG tDHw==
X-Received: by 10.15.63.142 with SMTP id m14mr16291043eex.106.1376117223472; Fri, 09 Aug 2013 23:47:03 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-180-208-107.red.bezeqint.net. [79.180.208.107]) by mx.google.com with ESMTPSA id r48sm28336750eev.14.2013.08.09.23.47.02 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 09 Aug 2013 23:47:02 -0700 (PDT)
Message-ID: <5205E1DB.5040903@gmail.com>
Date: Sat, 10 Aug 2013 09:46:51 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-bormann-cbor-04.txt (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <mailman.1781.1376113682.3376.ietf@ietf.org>
In-Reply-To: <mailman.1781.1376113682.3376.ietf@ietf.org>
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, 10 Aug 2013 06:52:11 -0000

Hi Dave,

I agree with you about the counter-marketing text that will only turn 
off potential implementers.

However I think this would be more appropriate as Experimental. Yes, we 
give PS to specs that may not ever be implemented. But at least working 
groups are (usually) good at avoiding publishing multiple specs to solve 
the same problem. Here we do not have that gating function. If we 
foresee multiple solutions being published for this problem space, which 
is what I'm hearing, then Experimental is the better choice.

Thanks,
	Yaron

> Date: Fri, 09 Aug 2013 19:33:49 -0700
> From: Dave Crocker<dhc@dcrocker.net>
> To: Stephen Farrell<stephen.farrell@cs.tcd.ie>
> Cc: Carsten Bormann<cabo@tzi.org>,	IETF Discussion Mailing List
> 	<ietf@ietf.org>
> Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary
> 	Object	Representation (CBOR)) to Proposed Standard
> Message-ID:<5205A68D.2020403@dcrocker.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 8/9/2013 6:09 PM, Stephen Farrell wrote:
>> >So some kind of statement that CBOR is one point in a design
>> >space (as opposed to an optimal solution for some set of
>> >design objectives) would be worthwhile.
>
> huh?  a statement beyond the opening sentence of the introduction and
> its third paragraph?
>
> worthwhile to whom and for what?  it's a spec (or perhaps a meta-spec.)
>    it provides a capability.  it needs to specify the what and how well
> enough to be usable.
>
> while ietf culture permits specifications to have quite a variety of
> commentary, historical or contextual discussion is not an essential part
> of the document, and certainly not discussion cast in a manner to
> denigrate the current spec.
>
> Counter-marketing that has the current spec self-deprecatingly casting
> itself as  only one of many seems mostly worthwhile to get people to
> avoid using it.
>
> exp makes sense if there is doubt that it is technically workable, not
> because its success in the market is questionable.  we give ps all the
> time to specs that have little clear market and go on gain small market use.
>
> from what i've seen, this is a carefully researched and crafted
> mechanism and i haven't noted anyone challenging it on basic technical
> grounds.
>
> d/
>
> -- Dave Crocker Brandenburg InternetWorking bbiw.net

From cabo@tzi.org  Sat Aug 10 00:13:58 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE5721F9C42 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 00:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GDOtp1DFRzTf for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 00:13:52 -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 D721821F9D71 for <ietf@ietf.org>; Sat, 10 Aug 2013 00:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7A7761G028825; Sat, 10 Aug 2013 09:07:06 +0200 (CEST)
Received: from [192.168.217.105] (p54890C7C.dip0.t-ipconnect.de [84.137.12.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id D7C686DC; Sat, 10 Aug 2013 09:07:05 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5205E1DB.5040903@gmail.com>
Date: Sat, 10 Aug 2013 09:07:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEA04780-503B-4F3B-B13B-6B0136A32A7E@tzi.org>
References: <mailman.1781.1376113682.3376.ietf@ietf.org> <5205E1DB.5040903@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Aug 2013 07:13:58 -0000

On Aug 10, 2013, at 08:46, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:

> If we foresee multiple solutions being published for this problem =
space, which is what I'm hearing, then Experimental is the better =
choice.

By that argument, TCP and UDP should be Experimental, too -- they are =
both in the transport protocol problem space.

There is nothing Experimental about CBOR.

Gr=FC=DFe, Carsten


From stephen.farrell@cs.tcd.ie  Sat Aug 10 04:17:34 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534D821F9E8B for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 04:17:34 -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 kQJ3HLMHInRe for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 04:17:28 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0570721F9D71 for <ietf@ietf.org>; Sat, 10 Aug 2013 04:13:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 240DABE33; Sat, 10 Aug 2013 12:13:12 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z999-96cBxHx; Sat, 10 Aug 2013 12:13:11 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.44.68.133]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 445FCBE20; Sat, 10 Aug 2013 12:13:11 +0100 (IST)
Message-ID: <5206203C.6070401@cs.tcd.ie>
Date: Sat, 10 Aug 2013 12:13:00 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <CAHBU6ivSy73s3c21ED8cF8miq+=mAX88pj=CcLaRSP25rdu67Q@mail.gmail.com> <6E30E660-C76A-4120-91CF-60C42B4DB41E@tzi.org> <520592CC.3080701@cs.tcd.ie> <5205A68D.2020403@dcrocker.net>
In-Reply-To: <5205A68D.2020403@dcrocker.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, 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, 10 Aug 2013 11:17:34 -0000

On 08/10/2013 03:33 AM, Dave Crocker wrote:
> On 8/9/2013 6:09 PM, Stephen Farrell wrote:
>> So some kind of statement that CBOR is one point in a design
>> space (as opposed to an optimal solution for some set of
>> design objectives) would be worthwhile.
> 
> 
> huh?  

That's fair. My suggestion above wasn't a model of clarity;-)

> a statement beyond the opening sentence of the introduction and
> its third paragraph?

And now that I read that again, yes, it does what I was
trying try to ask for well enough.

S.

> 
> worthwhile to whom and for what?  it's a spec (or perhaps a meta-spec.)
>  it provides a capability.  it needs to specify the what and how well
> enough to be usable.
> 
> while ietf culture permits specifications to have quite a variety of
> commentary, historical or contextual discussion is not an essential part
> of the document, and certainly not discussion cast in a manner to
> denigrate the current spec.
> 
> Counter-marketing that has the current spec self-deprecatingly casting
> itself as  only one of many seems mostly worthwhile to get people to
> avoid using it.
> 
> exp makes sense if there is doubt that it is technically workable, not
> because its success in the market is questionable.  we give ps all the
> time to specs that have little clear market and go on gain small market
> use.
> 
> from what i've seen, this is a carefully researched and crafted
> mechanism and i haven't noted anyone challenging it on basic technical
> grounds.
> 
> d/
> 

From hadriel.kaplan@oracle.com  Sat Aug 10 05:39:56 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0E5311E817A for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 05:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.219
X-Spam-Level: 
X-Spam-Status: No, score=-6.219 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O47g8ZhygXUi for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 05:39:50 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id DDED321F9B4C for <ietf@ietf.org>; Sat, 10 Aug 2013 05:32:30 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7ACWROZ013411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Aug 2013 12:32:28 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7ACWQHr018848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Aug 2013 12:32:27 GMT
Received: from abhmt116.oracle.com (abhmt116.oracle.com [141.146.116.68]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7ACWQnq008105; Sat, 10 Aug 2013 12:32:26 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 10 Aug 2013 05:32:26 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
Date: Sat, 10 Aug 2013 08:32:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
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, 10 Aug 2013 12:39:57 -0000

Howdy,
You asked for community input, so I'll pipe up from the peanut gallery.

I happen to be looking for a JSON-ish on-the-wire encoding with binary =
support, and I actually like what I see in CBOR.  (I'll probably end up =
using MessagePack anyway though... popularity has a quality all its own)

Comments inline...

On Aug 9, 2013, at 2:52 PM, Barry Leiba <barryleiba@computer.org> wrote:

> To the rest of the community: Does anyone else think it is not
> appropriate to publish CBOR as a Proposed Standard, and see who uses
> it?

If the intention is to just document an encoding format/mechanism and =
see who uses it, I think 'Informational' achieves that goal and is more =
appropriate.  If the intention is to base other standards-track work on =
this one in the near-term, and you've got some such use-case in mind for =
it, then 'Proposed Standard' seems reasonable to me if there're no =
strong objections.  Afaict it's always been easier to move Info to PS =
later, but it's been a lot harder to deprecate PS.  In the latter you =
have to prove something's broken/dangerous, while in the former you just =
have to prove people use it.

Also, while I take Ted's point that people shouldn't feel constrained to =
use it in other WGs, in practice I find that both WG participants and WG =
Chairs do in fact give a huge bias to re-using something that's =
published as a PS.  The burden of proof required to not re-use an =
existing PS RFC is very high.  They say: "It's a STANDARD!" and the =
implication is its something written on a stone tablet given to a guy =
named Moses.

I'm not saying that will happen in this case at all, but we shouldn't =
kid ourselves that it doesn't matter.  If it didn't matter, people =
wouldn't care about labeling their IDs Informational or Experimental.  =
People seem to *want* the PS label, and I don't think it's because =
people want to upgrade to an IS someday. [as an aside: that's what the =
2-level RFC experiment should teach us - that there is only 1 level that =
people care about, in practice]


> To the rest of the community: What is your view of Phill's technical
> arguments with CBOR?  Do you agree that CBOR is flawed?

No, it doesn't appear to contain technical errors nor fail to meet its =
self-stated design objectives.  I think Phillip probably has different =
design objectives.  But I'm not an expert in the field of object =
encoding theory. :)


> To the rest of the community: Do you agree with that concern?  Do you
> think such an analysis and selection of common goals, leading to one
> (or perhaps two) new binary encodings being proposed is what we should
> be doing?  Or is it acceptable to have work such as CBOR proposed
> without that analysis?

I think it's fair to publish CBOR as Informational right now.  I think =
publishing it as Proposed Standard would be ok if there wasn't strong =
disagreement, but it appears there is strong disagreement, including on =
how it came to be.  I have no idea what the history of CBOR's =
development has been, but if it's truly the case that it's just a couple =
people's personal work, then that's cool but PS seems wrong to me if a =
third person says it's a bad design. [again, I have no idea if that's =
true/false] =20

We rarely get 100% agreement even in WGs, but at least in WGs you get =
focused concentration from many participants.  Usually I've only seen PS =
going the A-D route when there are no objections from anyone whatsoever. =
(but that could be a wrong impression)

-hadriel


From moore@network-heretics.com  Sat Aug 10 06:55:49 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0511221F9FD7 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 06:55:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qGGZ3Wjfc6j for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 06:55:44 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id B0E3911E8102 for <ietf@ietf.org>; Sat, 10 Aug 2013 06:51:19 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8E62920E9B; Sat, 10 Aug 2013 09:51:18 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 10 Aug 2013 09:51:18 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=glrhbaKpHkriqjvKq8Amyx ClGO8=; b=NVHpH721wTow7usn3iP8MujrONLcxs/0NsUclMkmaDxTVHKu0Pgr2V ry5wbpKxsaWhpBUMFOk++JJier61baK/VqzyRdcKZGk/CDLvK37yfZ5jDyQcdmiM lc3miowzv5ByG0CdA6xZ9IEt5VM6LMv+f946crnZHiS3nAz7mNAf4=
X-Sasl-enc: 7m0fy/6atUXdVcAud4soMJFZUfQowUofrLv7Wm6NqDSz 1376142677
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AE3D8C00E8D; Sat, 10 Aug 2013 09:51:16 -0400 (EDT)
Message-ID: <52064543.4050504@network-heretics.com>
Date: Sat, 10 Aug 2013 09:50:59 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Faraday cages...
References: <20130807043255.39248.qmail@joyce.lan> <CAPv4CP8ZVPz_ob3hLTADQJyha_cpRRRJmEsbTiwe3c0No5n9Kw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524962E@mbx-01.win.nominum.com> <alpine.OSX.2.01.1308071327190.19348@173-11-110-132-sfba.hfc.comcastbusiness.net> <8D23D4052ABE7A4490E77B1A012B630775249BC7@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152D1543@tk5ex14mbxc272.redmond.corp.microsoft.com> <CAMm+LwgvD--A0GALM+eZ+MRswupA8sOhzV=dCUaEfM9hpxQqpw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63077524BD96@mbx-01.win.nominum.com> <C91E67751B1EFF41B857DE2FE1F68ABA152E659B@TK5EX14MBXC273.redmond.corp.microsoft.com> <CAMm+Lwh8TaKq3TvALkULS_xLhnGq=_Yq0HZBc+KyNwY+YjdQPQ@mail.gmail.com> <5204364E.7080905@network-heretics.com> <CAKr6gn3qR-oaegi0XjGLhOCmVF7x7eex6akiBB5OYS0RizoP2w@mail.gmail.com> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com> <52044054.7020205@network-heretics. com> <3F97BF72-62A7-4A69-908B-A4C01D75A8ED@nominum.com>
In-Reply-To: <3F97BF72-62A7-4A69-908B-A4C01D75A8ED@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 10 Aug 2013 13:55:49 -0000

On 08/09/2013 09:39 AM, Ted Lemon wrote:
> On Aug 8, 2013, at 9:05 PM, Keith Moore <moore@network-heretics.com> wrote:
>> Would being able to reliably know exactly who said everything that was said in a WG meeting visibly improve the quality of our standards?   If the answer is not a clear "yes" (and I don't think it is) then I suggest that this topic is a distraction.
> If you mean will it improve what is written on the page, probably not.   Will it decrease the likelihood of someone participating without identifying themself, and then violating the IPR rules?   Possibly.
>
> AFAIK that's why we do it.   Not so much because it is an iron-clad preventative, but because it to some degree removes the illusion of anonymity that might tempt someone to do something like that, or just be careless about it.

If it's that important to catch people violating the IPR rules, perhaps 
we need to hire a court reporter for every WG meeting, and not rely on 
volunteer Jabber scribes to accurately capture what is said and who said it.

Keith


From Ted.Lemon@nominum.com  Sat Aug 10 07:28:32 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759B811E8112 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 07:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.566
X-Spam-Level: 
X-Spam-Status: No, score=-106.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 ik20Hj5V62Mn for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 07:28:26 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 73A8711E80ED for <ietf@ietf.org>; Sat, 10 Aug 2013 07:21:23 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUgZMYdq2Jtkvsw8OsQDptIWXURaiMD03@postini.com; Sat, 10 Aug 2013 07:21:23 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7D6891B8271 for <ietf@ietf.org>; Sat, 10 Aug 2013 07:21:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 74796190060; Sat, 10 Aug 2013 07:21:21 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 10 Aug 2013 07:21:14 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com>
Date: Sat, 10 Aug 2013 10:21:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 14:28:32 -0000

On Aug 10, 2013, at 8:32 AM, Hadriel Kaplan <hadriel.kaplan@oracle.com> =
wrote:
> I'm not saying that will happen in this case at all, but we shouldn't =
kid ourselves that it doesn't matter.  If it didn't matter, people =
wouldn't care about labeling their IDs Informational or Experimental.  =
People seem to *want* the PS label, and I don't think it's because =
people want to upgrade to an IS someday. [as an aside: that's what the =
2-level RFC experiment should teach us - that there is only 1 level that =
people care about, in practice]

It almost certainly will happen.   But "we shouldn't do this because =
someone might later on draw an incorrect conclusion about what we did" =
is just not a valid argument against advancing the document to proposed =
standard.   What it is is an argument for understanding the IETF process =
so that when people make assertions about this sort of thing, you can =
have a meaningful debate with them and point at RFCs.   Otherwise your =
working group can get sidetracked by the ownership assertion problem, =
which as you are already aware can be very damaging.

The reason we call things "proposed standard" is because we expect =
interoperability.   A thing that can't have or affect interoperability =
probably isn't a "proposed standard."   In this case, what we have is =
definitely a proposed standard and not an informational document; the =
question is whether it's a standard that will get IETF consensus.

I should point out that a lot of arguments have been raised here that =
don't really affect consensus.   The arguments to raise if you think a =
proposed standard is a bad idea are technical arguments: "this won't =
work because of X" or architectural arguments: "we shouldn't do this =
because there is a better way to do it that fits better with the =
Internet architecture" or "this is needlessly complicated for the use =
case we are trying to address."

Importantly, "we shouldn't do this because there's a proposed standard =
that does something similar" is _not_ a valid argument; if the proposed =
standard is technically or architecturally better, _that_ is the =
argument to raise.   The mere existence of the RFC is not an argument in =
itself.

Seriously, RFC 1958 is a good document to read if you are interested in =
this issue.   You might also want to read RFC 5218.

(Dave Thaler will know why I know to reference these two documents... :)


From scott@kitterman.com  Sat Aug 10 07:59:18 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 915A421F9D65 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 07:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YFFPrfOfzR8M for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 07:59:13 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2A97B21F9946 for <ietf@ietf.org>; Sat, 10 Aug 2013 07:52:38 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 55B4D20E40EA; Sat, 10 Aug 2013 10:52:37 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376146357; bh=pwlvfw+EmNU9BEOU4AdPhVTBtVIqTjiq6FF4SsR6fUI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KYqmpEOgqTBEOaJ+B9p7YCUYAMXMfkYT3zuYrGZ+JdNJLwRGxzOMuK/gCcs50uMmM RYcbUPIDyxwSHBK6tUlxMPZhkstPQ8cuhVdY2aB2GnfYzVlruhmwVTE1/BskR6nDjP CXCO8YK1pDPeI49YcnGH5vS/qhWro/tWwEInkDmM=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 3EDB020E40CB;  Sat, 10 Aug 2013 10:52:36 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Faraday cages...
Date: Sat, 10 Aug 2013 10:52:35 -0400
Message-ID: <3765257.KlB4bF3Fne@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <3F97BF72-62A7-4A69-908B-A4C01D75A8ED@nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com> <3F97BF72-62A7-4A69-908B-A4C01D75A8ED@nominum.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Aug 2013 14:59:18 -0000

On Friday, August 09, 2013 09:39:12 Ted Lemon wrote:
> On Aug 8, 2013, at 9:05 PM, Keith Moore <moore@network-heretics.com> wrote:
> > Would being able to reliably know exactly who said everything that was
> > said in a WG meeting visibly improve the quality of our standards?   If
> > the answer is not a clear "yes" (and I don't think it is) then I suggest
> > that this topic is a distraction.
> If you mean will it improve what is written on the page, probably not.  
> Will it decrease the likelihood of someone participating without
> identifying themself, and then violating the IPR rules?   Possibly.
> 
> AFAIK that's why we do it.   Not so much because it is an iron-clad
> preventative, but because it to some degree removes the illusion of
> anonymity that might tempt someone to do something like that, or just be
> careless about it.

Unless you're checking identification provided by sources all agree are 
trustworthy, you've done nothing of the sort.  You may be able to attach an 
unverified identifier to a group of statements, but there's still no firm 
connection to identity (I'm not arguing in favor of one, but it seems a bit 
silly to expend resources to protect against something you aren't actually 
protecting against).

Scott K

From dhc@dcrocker.net  Sat Aug 10 08:08:31 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D15121E804E for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:08:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KyAUQjqWdLO5 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:08:26 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4421B21F99DE for <ietf@ietf.org>; Sat, 10 Aug 2013 08:00:31 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7AF0RfD013956 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sat, 10 Aug 2013 08:00:30 -0700
Message-ID: <52065582.8000906@dcrocker.net>
Date: Sat, 10 Aug 2013 08:00:18 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-bormann-cbor-04.txt (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <mailman.1781.1376113682.3376.ietf@ietf.org> <5205E1DB.5040903@gmail.com> <DEA04780-503B-4F3B-B13B-6B0136A32A7E@tzi.org>
In-Reply-To: <DEA04780-503B-4F3B-B13B-6B0136A32A7E@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.66]); Sat, 10 Aug 2013 08:00:30 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Aug 2013 15:08:31 -0000

On 8/10/2013 12:07 AM, Carsten Bormann wrote:
> On Aug 10, 2013, at 08:46, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
>
>> If we foresee multiple solutions being published for this problem space, which is what I'm hearing, then Experimental is the better choice.
>
> By that argument, TCP and UDP should be Experimental, too -- they are both in the transport protocol problem space.
>
> There is nothing Experimental about CBOR.


One of the reasons we find groups choosing to avoid the IETF's standards 
process is its unpredictability.  Folks here -- both on open discussion 
lists and often in the IESG -- think it's acceptable to invoke 
spontaneous, personal criteria, rather than pay attention to the rules 
we've put into place.  We have criteria for the standards labels. 
They've gone through IETF consensus and they are supposed to have 
something akin to the force of (IETF) law.

If someone feels that this specification does not qualify for Proposed 
Standard, they ought to feel obligated to begin with a citation of the 
portion of RFC 2026, Section 4.1.1 -- specifying the criteria for 
Proposed Standard -- that this specification fails to satisfy.

In particular, they should draw carefully from the second paragraph of 
that section.,

By my own reading, this specification looks to be a pretty classic 
example of what we say we want for Proposed Standard.

Most of this thread has ignored the IETF's own rules and criteria.  As 
such, it's wasteful, at best, though I think it's actually destructive, 
since it provides fuel to the view that the IETF is a questionable venue 
for standards work.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Sat Aug 10 08:20:16 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1683011E80FE for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.566
X-Spam-Level: 
X-Spam-Status: No, score=-106.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 qRv3Ijc+8f0l for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:20:09 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 122AB11E80FF for <ietf@ietf.org>; Sat, 10 Aug 2013 08:13:43 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUgZYpcgM0q1H9kBbmItbLI+8+DN182b9@postini.com; Sat, 10 Aug 2013 08:13:43 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 87F691B827C for <ietf@ietf.org>; Sat, 10 Aug 2013 08:13:41 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 68D9A190060; Sat, 10 Aug 2013 08:13:41 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 10 Aug 2013 08:13:41 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Faraday cages...
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <3765257.KlB4bF3Fne@scott-latitude-e6320>
Date: Sat, 10 Aug 2013 11:13:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <2F50CDA5-8EF1-4173-ABE1-E3F699B69717@nominum.com>
References: <20130807043255.39248.qmail@joyce.lan> <CAMm+LwgHMy20vPtQKwsnJR1VkOTCpvwU6CScBf66qAGAZix4Yg@mail.gmail.com> <3F97BF72-62A7-4A69-908B-A4C01D75A8ED@nominum.com> <3765257.KlB4bF3Fne@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
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, 10 Aug 2013 15:20:16 -0000

On Aug 10, 2013, at 10:52 AM, Scott Kitterman <scott@kitterman.com> =
wrote:
> Unless you're checking identification provided by sources all agree =
are=20
> trustworthy, you've done nothing of the sort.  You may be able to =
attach an=20
> unverified identifier to a group of statements, but there's still no =
firm=20
> connection to identity (I'm not arguing in favor of one, but it seems =
a bit=20
> silly to expend resources to protect against something you aren't =
actually=20
> protecting against).

I think you misunderstand the threat model.


From Ted.Lemon@nominum.com  Sat Aug 10 08:21:45 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168C121E804B for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:21:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.566
X-Spam-Level: 
X-Spam-Status: No, score=-106.566 tagged_above=-999 required=5 tests=[AWL=0.033, 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 5DB5uCnV0q-k for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:21:33 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1A821F9F3D for <ietf@ietf.org>; Sat, 10 Aug 2013 08:14:33 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUgZY2M9tg4GU0rvc7CPhuG1SCO8SsqVM@postini.com; Sat, 10 Aug 2013 08:14:33 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 627BF1B8271 for <ietf@ietf.org>; Sat, 10 Aug 2013 08:14:32 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 5BE93190060; Sat, 10 Aug 2013 08:14:32 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 10 Aug 2013 08:14:32 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52065582.8000906@dcrocker.net>
Date: Sat, 10 Aug 2013 11:14:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <52FC8141-984F-4A99-A0F7-4B3B4563B418@nominum.com>
References: <mailman.1781.1376113682.3376.ietf@ietf.org> <5205E1DB.5040903@gmail.com> <DEA04780-503B-4F3B-B13B-6B0136A32A7E@tzi.org> <52065582.8000906@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
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, 10 Aug 2013 15:21:45 -0000

On Aug 10, 2013, at 11:00 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> Most of this thread has ignored the IETF's own rules and criteria.  As =
such, it's wasteful, at best, though I think it's actually destructive, =
since it provides fuel to the view that the IETF is a questionable venue =
for standards work.

+1


From hadriel.kaplan@oracle.com  Sat Aug 10 08:38:21 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A239C11E8136 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.517
X-Spam-Level: 
X-Spam-Status: No, score=-6.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfqKMq6fE59F for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:38:15 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 6E84021F9CA9 for <ietf@ietf.org>; Sat, 10 Aug 2013 08:30:52 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7AFUkMp004107 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Aug 2013 15:30:47 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7AFUjgO028061 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Aug 2013 15:30:46 GMT
Received: from abhmt108.oracle.com (abhmt108.oracle.com [141.146.116.60]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7AFUjq6028058; Sat, 10 Aug 2013 15:30:45 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 10 Aug 2013 08:30:44 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com>
Date: Sat, 10 Aug 2013 11:30:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 15:38:21 -0000

On Aug 10, 2013, at 10:21 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> The reason we call things "proposed standard" is because we expect =
interoperability.   A thing that can't have or affect interoperability =
probably isn't a "proposed standard."   In this case, what we have is =
definitely a proposed standard and not an informational document; the =
question is whether it's a standard that will get IETF consensus.

I'm not sure if you intended to, but you're implying non-standards-track =
docs are only for things we don't expect interoperability for, or cannot =
have or affect interoperability.   I've read RFC 2026, and afaict =
non-standards-track docs can still be things that have or affect =
interoperability.  That's not to say it ought not to be PS, obviously, =
but more that a statement of "what we have is definitely a proposed =
standard" seems like jumping the gun to me.


> I should point out that a lot of arguments have been raised here that =
don't really affect consensus.   The arguments to raise if you think a =
proposed standard is a bad idea are technical arguments: "this won't =
work because of X" or architectural arguments: "we shouldn't do this =
because there is a better way to do it that fits better with the =
Internet architecture" or "this is needlessly complicated for the use =
case we are trying to address."

That's fair, and I should have been clearer.  I think 'Informatonal' is =
more appropriate for now, because I don't think we know what the "it" is =
in your above statements - i.e., I don't know what Internet use-cases =
and/or IETF protocols CBOR was intended to be used for.  For example, is =
the purpose of it to be JSONv2 for Javascript uses, vs. a new encoding =
for DNS AXFR/IXFR, vs. an encoding for a NoSQL inter-DB synch protocol, =
vs. a new encoding for MIME bodies in SMTP.  I don't see how we can know =
whether an encoding mechanism is sound or broken without knowing what =
its intended/motivating use-case is.

But, if the IESG feels an encoding mechanism doesn't need any targeted =
use-case to be published as a PS, then please ignore my email for =
purposes of consensus.  I'm not strongly for/against - just answering =
Barry's original question, from the peanut gallery as I said in my =
original email.  And as I said in my original email: "[the draft] =
doesn't appear to contain technical errors nor fail to meet its =
self-stated design objectives."


> Importantly, "we shouldn't do this because there's a proposed standard =
that does something similar" is _not_ a valid argument; if the proposed =
standard is technically or architecturally better, _that_ is the =
argument to raise.   The mere existence of the RFC is not an argument in =
itself.
> Seriously, RFC 1958 is a good document to read if you are interested =
in this issue.   You might also want to read RFC 5218.

I read RFC 1958 yesterday when I saw your previous email, and I read it =
again this morning when I saw your comment above.  But I still don't =
grok which part of it let's me tell a WG Chair: "No, just because =
there's a PS RFC doing something similar, doesn't mean we can't do =
something better and more appropriate for this particular application".  =
I mean I can tell them that now, but it doesn't carry much weight.  What =
part of RFC 1958 would help me making such a statement?

-hadriel


From john-ietf@jck.com  Sat Aug 10 08:41:04 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E45A21F9F98 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DKwhslc2owq2 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 08:40:58 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 09EE511E80AD for <ietf@ietf.org>; Sat, 10 Aug 2013 08:33:33 -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 1V8BAX-000IoW-Bs; Sat, 10 Aug 2013 11:33:29 -0400
Date: Sat, 10 Aug 2013 11:33:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <ted.lemon@nominum.com>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt (Concise Binary Object	Representation (CBOR)) to Proposed Standard
Message-ID: <D39F308341AB81895B352C7E@JcK-HP8200.jck.com>
In-Reply-To: <52FC8141-984F-4A99-A0F7-4B3B4563B418@nominum.com>
References: <mailman.1781.1376113682.3376.ietf@ietf.org> <5205E1DB.5040903@gmail.com> <DEA04780-503B-4F3B-B13B-6B0136A32A7E@tzi.org> <52065582.8000906@dcrocker.net> <52FC8141-984F-4A99-A0F7-4B3B4563B418@nominum.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 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, 10 Aug 2013 15:41:04 -0000

--On Saturday, August 10, 2013 11:14 -0400 Ted Lemon
<ted.lemon@nominum.com> wrote:

> On Aug 10, 2013, at 11:00 AM, Dave Crocker <dhc@dcrocker.net>
> wrote:
>> Most of this thread has ignored the IETF's own rules and
>> criteria.  As such, it's wasteful, at best, though I think
>> it's actually destructive, since it provides fuel to the view
>> that the IETF is a questionable venue for standards work.
> 
> +1

+1 more.  Not doing this sort of thing to ourselves is probably
far more important, in the long run, than trying to slightly
re-tune the language of 2026 in that hope that will impress
someone.  The latter might still be worthwhile, but it is, IMO,
far more important to stop shooting ourselves in the foot.

   john






From Ted.Lemon@nominum.com  Sat Aug 10 09:31:46 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEE021E804D for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 09:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.567
X-Spam-Level: 
X-Spam-Status: No, score=-106.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEJSAjDNAHQG for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 09:31:39 -0700 (PDT)
Received: from exprod7og129.obsmtp.com (exprod7og129.obsmtp.com [64.18.2.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6287921F9CC7 for <ietf@ietf.org>; Sat, 10 Aug 2013 09:25:49 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob129.postini.com ([64.18.6.12]) with SMTP ID DSNKUgZpjNjOdSgYHa/cQBqv2vovlNulGbQx@postini.com; Sat, 10 Aug 2013 09:25:49 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CEC251B825D for <ietf@ietf.org>; Sat, 10 Aug 2013 09:25:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4C15F190060; Sat, 10 Aug 2013 09:25:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 10 Aug 2013 09:25:39 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com>
Date: Sat, 10 Aug 2013 12:25:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 16:31:46 -0000

On Aug 10, 2013, at 11:30 AM, Hadriel Kaplan <hadriel.kaplan@oracle.com> =
wrote:
> I'm not sure if you intended to, but you're implying =
non-standards-track docs are only for things we don't expect =
interoperability for, or cannot have or affect interoperability.   I've =
read RFC 2026, and afaict non-standards-track docs can still be things =
that have or affect interoperability.  That's not to say it ought not to =
be PS, obviously, but more that a statement of "what we have is =
definitely a proposed standard" seems like jumping the gun to me.

Fair point.   RFC2026 does not in fact make the distinction I made.

Here is what RFC 2026 says about proposed standards:

   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.  However, further experience
   might result in a change or even retraction of the specification
   before it advances.

Here is what it says about Informational documents:

   An "Informational" specification is published for the general
   information of the Internet community, and does not represent an
   Internet community consensus or recommendation.  The Informational
   designation is intended to provide for the timely publication of a
   very broad range of responsible informational documents from many
   sources, subject only to editorial considerations and to verification
   that there has been adequate coordination with the standards process
   (see section 4.2.3).

In practice, the qualifications for Informational generally don't give =
us any reasonable expectation of interoperability, nor do they require =
it.   There is one exception:

   Specifications that have been prepared outside of the Internet
   community and are not incorporated into the Internet Standards
   Process by any of the provisions of section 10 may be published as
   Informational RFCs, with the permission of the owner and the
   concurrence of the RFC Editor.

As a practice, we also do sometimes publish informational documents that =
were produced by working groups and that were intended to be standards, =
but that were not selected by the working group to be standards, but =
that nevertheless are considered to be useful to the community for =
informational purposes.   But the most common examples of informational =
documents are operational practices documents that do not qualify as =
BCP, reports, architecture documents, requirements documents, gap =
analyses and other analyses.   It is on this basis that I made the claim =
that informational documents generally aren't intended to interoperate.

> That's fair, and I should have been clearer.  I think 'Informatonal' =
is more appropriate for now, because I don't think we know what the "it" =
is in your above statements - i.e., I don't know what Internet use-cases =
and/or IETF protocols CBOR was intended to be used for.  For example, is =
the purpose of it to be JSONv2 for Javascript uses, vs. a new encoding =
for DNS AXFR/IXFR, vs. an encoding for a NoSQL inter-DB synch protocol, =
vs. a new encoding for MIME bodies in SMTP.  I don't see how we can know =
whether an encoding mechanism is sound or broken without knowing what =
its intended/motivating use-case is.

Section 1.1 goes on at some length about the intended use for the =
document is.   If you believe it is unclear or incomplete, some pointed =
questions about it would be entirely appropriate.

> But, if the IESG feels an encoding mechanism doesn't need any targeted =
use-case to be published as a PS, then please ignore my email for =
purposes of consensus.  I'm not strongly for/against - just answering =
Barry's original question, from the peanut gallery as I said in my =
original email.  And as I said in my original email: "[the draft] =
doesn't appear to contain technical errors nor fail to meet its =
self-stated design objectives."

I can't speak for the IESG.   You already know what my opinion as an =
individual AD is=97I am not strongly in favor of publishing this =
document, because it's out of my area, but I haven't seen any argument =
raised against publishing it that I find convincing; in particular I do =
think it's appropriate to publish it as a standards-track document if =
it's found to have consensus.

> I read RFC 1958 yesterday when I saw your previous email, and I read =
it again this morning when I saw your comment above.  But I still don't =
grok which part of it let's me tell a WG Chair: "No, just because =
there's a PS RFC doing something similar, doesn't mean we can't do =
something better and more appropriate for this particular application".  =
I mean I can tell them that now, but it doesn't carry much weight.  What =
part of RFC 1958 would help me making such a statement?

Section 3.   If you only read section 3.2, and don't read the last =
clause of the last sentence in that section, then you might come to the =
conclusion that once an RFC is published that solves a specific problem, =
no other RFC can ever be published that addresses a similar problem.

Section 3.2 definitely does argue that if you have a good solution to a =
problem, you shouldn't invent a new solution to the problem.   If you =
were to apply section 3.2 strictly without all the caveats, you could =
argue that this document shouldn't be published because ASN.1 solves the =
same problem.   But that's not a correct reading of the document, =
because of all the other caveats that are listed in subsequent sections.=

From Ted.Lemon@nominum.com  Sat Aug 10 09:48:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C336B11E8108 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 09:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.567
X-Spam-Level: 
X-Spam-Status: No, score=-106.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHqW3lHaGqm0 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 09:48:42 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 18AB421F9E9D for <ietf@ietf.org>; Sat, 10 Aug 2013 09:41:56 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUgZtU6wBwIlzOsq+f1pwH0ViJjY9SREK@postini.com; Sat, 10 Aug 2013 09:41:56 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BFD561B827C for <ietf@ietf.org>; Sat, 10 Aug 2013 09:41:55 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B326D190060; Sat, 10 Aug 2013 09:41:55 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 10 Aug 2013 09:41:49 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
Date: Sat, 10 Aug 2013 12:41:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <0C246504-2D2B-4755-B35A-37EFB08FE553@nominum.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com> <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 16:48:48 -0000

On Aug 10, 2013, at 12:25 PM, Ted Lemon <ted.lemon@nominum.com> wrote:
> Section 1.1 goes on at some length about the intended use for the =
document is.   If you believe it is unclear or incomplete, some pointed =
questions about it would be entirely appropriate.

To expand on this slightly, the point is that if you say "it's not clear =
to me what the use case for this document is," that's a valid objection, =
and the authors ought to address it, either by explaining to the =
satisfaction of the consensus-caller and, more generally, the reviewers, =
why it's not relevant, or by fixing the document to be clearer about =
what the current intended use cases are.   But if you want that to =
happen, you should really raise your objection in a way that makes it =
clearly actionable, so that the authors know you are asking them to do =
something.


From ynir@checkpoint.com  Sat Aug 10 11:19:10 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B232711E80F3 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 11:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.522
X-Spam-Level: 
X-Spam-Status: No, score=-10.522 tagged_above=-999 required=5 tests=[AWL=0.077, 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 3h8B-3E49S7X for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 11:19:04 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id AF50521F9E9D for <ietf@ietf.org>; Sat, 10 Aug 2013 11:13:07 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r7AICvj7019233; Sat, 10 Aug 2013 21:12:58 +0300
X-CheckPoint: {520682A9-4-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Sat, 10 Aug 2013 21:12:56 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Index: AQHOjAb1l79Be4a5KUSX2quaKf0s1ZmILHaAgAAfkICAAPL0gIACR24AgAGSi4CAASgKgIAAHmaAgAATa4CAAC1aAA==
Date: Sat, 10 Aug 2013 18:12:56 +0000
Message-ID: <274F24F8-BD78-4839-91C2-E873CD897DA1@checkpoint.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com>
In-Reply-To: <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.172]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1194048faeb067582e0772535a700b6e88fff0faad
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <7C702065E85A994BA5D772CB4199B755@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 18:19:10 -0000

On Aug 10, 2013, at 6:30 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com> wro=
te:
>=20
>=20
> But, if the IESG feels an encoding mechanism doesn't need any targeted us=
e-case to be published as a PS, then please ignore my email for purposes of=
 consensus.  I'm not strongly for/against - just answering Barry's original=
 question, from the peanut gallery as I said in my original email.  And as =
I said in my original email: "[the draft] doesn't appear to contain technic=
al errors nor fail to meet its self-stated design objectives."

I don't know about the IESG, but I don't think an encoding mechanism or for=
 that matter any format needs to have a targeted use case. WebSec is curren=
tly debating ([1] whether to put the key pinning data in an HTTP header or =
in a resource. If we choose the latter, there will be the question of encod=
ing, and we will probably consider things like XML, JSON, ASN.1, and CBOR, =
or roll our own new one-time format. If someone in the group wants to do th=
e one-off format, we will ask why not use XML, JSON, or CBOR (nobody's goin=
g to ask about ASN.1, because those that care enough to suggest it also kno=
w to call it BER), and of course you'll need a good reason not to use a doc=
umented format, whether it's "standard" or not.

Those will be the obvious choices regardless of whether CBOR is Information=
al, Experimental, PS, or still a draft-bormann. Nobody's proposing technica=
l changes, so we might as well stick an RFC number on it. IMO the only time=
 you stick the "INFORMATIONAL" label on a protocol or an encoding, is when =
you are just documenting a protocol or an encoding that exists outside the =
IETF, and the IETF is not given change control. See draft-ietf-websec-x-fra=
me-options for an example. Experimental is for things where we don't know i=
f they work in general or if they scale. IOW, we're not sure they're approp=
riate for their stated goal. That is not the case with CBOR.

Yes, we can reference CBOR as normative from draft-ietf-websec-key-pinning =
(intended to be PS) with a downref. But just because downrefs exist does no=
t mean we should aim for them. PS is the right choice IMO.

Yoav


From lear@cisco.com  Sat Aug 10 11:53:24 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4639D21F9D5C for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 11:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.087
X-Spam-Level: 
X-Spam-Status: No, score=-110.087 tagged_above=-999 required=5 tests=[AWL=0.512, 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 c1HX4ib1tCdO for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 11:53:19 -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 B89C421F9263 for <ietf@ietf.org>; Sat, 10 Aug 2013 11:46:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1517; q=dns/txt; s=iport; t=1376160394; x=1377369994; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=M9M6qNWw1hvi3WdUtOsnXha0nOhL9zLTR7vi3GP31y4=; b=QRMEYT+MBuoxiDzHtpdio+6aHcAA94XoUH/oo/pMz4i79y0rNN+dtHv5 O8Ue7tpyclEhO1ZUxdZiPhY6nPYahdnsSRRirD5aZSjJS8BmvRSjqm2KG SRE+FUQQT59XKvX+V5WJGMqb1MidanD/uD6dsg7pkEtumj69sDMJZotbj g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAAuKBlKQ/khM/2dsb2JhbABZgwaEGLtOgRkWdIIkAQEBBCNVARALGAICBRYEBwICCQMCAQIBKxoTAQcBAYgMpn6QcIEpjxIHFoJSgSkDl2SRUYFhgTw6
X-IronPort-AV: E=Sophos;i="4.89,852,1367971200"; d="scan'208";a="17008246"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-4.cisco.com with ESMTP; 10 Aug 2013 18:46:31 +0000
Received: from mctiny.local ([10.61.195.60]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7AIkTXJ027234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Aug 2013 18:46:29 GMT
Message-ID: <52068A85.8080408@cisco.com>
Date: Sat, 10 Aug 2013 20:46:29 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Last Call: <draft-bormann-cbor-04.txt (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <mailman.1781.1376113682.3376.ietf@ietf.org> <5205E1DB.5040903@gmail.com> <DEA04780-503B-4F3B-B13B-6B0136A32A7E@tzi.org> <52065582.8000906@dcrocker.net>
In-Reply-To: <52065582.8000906@dcrocker.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Aug 2013 18:53:24 -0000

On 8/10/13 5:00 PM, Dave Crocker wrote:
>
> One of the reasons we find groups choosing to avoid the IETF's
> standards process is its unpredictability.

Our processes must be stable, but people have different reasons for
articulating concern.  2026 is not meant to be the singular criteria. 
In fact we have for a long time accepted the additional questions that
form a working group, as well.  And unpredictability is part and parcel
of standards activity: you can't buy a standard at the IETF, which is
what predictability implies, if taken to extremes.  And people not
familiar with the IETF often take it to extremes.  A perfect example was
Tim Berners-Lee who wanted to standardize HTML, but didn't want to give
up control of the specification.  It just doesn't work that way.

Now that we're done with generalities, I'll just chime in and say that
the spec in question seems perfectly fine to advance as a Proposed
Standard.  I do wonder whether CBOR is better than compressed JSON, but
I understand that in this context CPU may be a limiting factor.

There is an architectural question hiding here: when we use CBOR in
various protocols, we may be optimizing for the wrong set of devices
overall.  Conversely, we may be optimizing for just the right devices
since the so-called Internet of Things that are low end devices will
outnumber other devices.  Which is it?  Either way, it seems to me we
can't answer without CBOR or something like it, so...  let's have it, then.

Eliot

From wes@mti-systems.com  Sat Aug 10 12:36:21 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7909811E81A6 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 12:36: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 FHMlnBhUStLm for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 12:36:15 -0700 (PDT)
Received: from atl4mhob08.myregisteredsite.com (atl4mhob08.myregisteredsite.com [209.17.115.46]) by ietfa.amsl.com (Postfix) with ESMTP id EAD1311E8140 for <ietf@ietf.org>; Sat, 10 Aug 2013 12:29:59 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob08.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r7AJTxu7032185 for <ietf@ietf.org>; Sat, 10 Aug 2013 15:29:59 -0400
Received: (qmail 32258 invoked by uid 0); 10 Aug 2013 19:29:59 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.122?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 10 Aug 2013 19:29:59 -0000
Message-ID: <52069498.1000604@mti-systems.com>
Date: Sat, 10 Aug 2013 15:29:28 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com>
In-Reply-To: <5205D2FB.8010205@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Aug 2013 19:36:21 -0000

On 8/10/2013 1:43 AM, Martin Sustrik wrote:
> Hi all,
> 
> Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol used?
> Is it the case that there are inetd daemons in TCPMUX mode running
> everywhere, or can it be rather considered a dead protocol?
> 
> Specifically, if I implement a new TCPMUX daemon how likely I am to
> clash with an existing TCPMUX daemon listening on port 1?
> 


It's in the FreeBSD inetd, among others, but to to my
knowledge, nobody actually turns it on.  There are
probably security issues.

-- 
Wes Eddy
MTI Systems

From sustrik@250bpm.com  Sat Aug 10 12:41:10 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E967311E81C7 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 12:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNLJaLA9rFGg for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 12:41:05 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id E47A311E8189 for <ietf@ietf.org>; Sat, 10 Aug 2013 12:33:33 -0700 (PDT)
Received: from [192.168.0.102] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 86C66180354D; Sat, 10 Aug 2013 21:33:30 +0200 (CEST)
Message-ID: <52069589.3010403@250bpm.com>
Date: Sat, 10 Aug 2013 21:33:29 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com>
In-Reply-To: <52069498.1000604@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Aug 2013 19:41:11 -0000

On 10/08/13 21:29, Wesley Eddy wrote:
> On 8/10/2013 1:43 AM, Martin Sustrik wrote:
>> Hi all,
>>
>> Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol used?
>> Is it the case that there are inetd daemons in TCPMUX mode running
>> everywhere, or can it be rather considered a dead protocol?
>>
>> Specifically, if I implement a new TCPMUX daemon how likely I am to
>> clash with an existing TCPMUX daemon listening on port 1?
>>
>
>
> It's in the FreeBSD inetd, among others, but to to my
> knowledge, nobody actually turns it on.  There are
> probably security issues.

I am aware of inetd and alternatives. I was more interested whether 
there's some significant deployment base of systems with TCPMUX turned on.

So far, the only relevant info I've found is that TCPMUX was turned on 
by default on SGI Irix systems, but given that these had end of life in 
2006, I guess there's not much of them left out there.

Martin


From hallam@gmail.com  Sat Aug 10 12:52:56 2013
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 846A421F8EB3 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 12:52:56 -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, 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 Vf9AcKuTICtv for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 12:52:55 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A06EB21F9F9E for <ietf@ietf.org>; Sat, 10 Aug 2013 12:45:56 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id x55so4426294wes.18 for <ietf@ietf.org>; Sat, 10 Aug 2013 12:45:55 -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=v+Pn143PJYxnQYfOyvDLKjarX/39/1L4KkfMT2x/pPA=; b=GhaPuYHRsTruHKTE3W6Qb1BO/ZeHL65WGYtQumXnQjS0N9VnpK6XmGvrTLP7gpub1N TmquFcPWFaJTa2o//TTHdIVdvAxS+wb3uQi2vMyMOLaGvm+yGzDwLucoHqIZWirwz0da 4WEYD0LSFJixqmjOGXIyjZjN0h6ca14xrEsCTNCqB2LdvZp+WCe7BEvzxNn1cRFkvAum kkMJBQB7olxZvwvRoxIUu8nN53K5WPDZ234phlPjvoOuKUwfIW9+1lNg6TbpkLEUyxHE 4IfXudL8mxnpJUsHRvJp4wERRGIqJUry5b0zeyx4hHYUmk1ZAC+f4MmJOUAQUpyvsZx9 sc3A==
MIME-Version: 1.0
X-Received: by 10.194.219.233 with SMTP id pr9mr3186842wjc.8.1376163955699; Sat, 10 Aug 2013 12:45:55 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Sat, 10 Aug 2013 12:45:55 -0700 (PDT)
In-Reply-To: <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com>
Date: Sat, 10 Aug 2013 20:45:55 +0100
Message-ID: <CAMm+LwjvxXv+kr9z5OVXaYipYF9eLo-00+uZUuVaPQh5b=rZAg@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c1b7e6bb773e04e39d2346
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 19:52:56 -0000

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

On Sat, Aug 10, 2013 at 3:21 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Aug 10, 2013, at 8:32 AM, Hadriel Kaplan <hadriel.kaplan@oracle.com>
> wrote:
> > I'm not saying that will happen in this case at all, but we shouldn't
> kid ourselves that it doesn't matter.  If it didn't matter, people wouldn't
> care about labeling their IDs Informational or Experimental.  People seem
> to *want* the PS label, and I don't think it's because people want to
> upgrade to an IS someday. [as an aside: that's what the 2-level RFC
> experiment should teach us - that there is only 1 level that people care
> about, in practice]
>
> It almost certainly will happen.   But "we shouldn't do this because
> someone might later on draw an incorrect conclusion about what we did" is
> just not a valid argument against advancing the document to proposed
> standard.   What it is is an argument for understanding the IETF process so
> that when people make assertions about this sort of thing, you can have a
> meaningful debate with them and point at RFCs.   Otherwise your working
> group can get sidetracked by the ownership assertion problem, which as you
> are already aware can be very damaging
>

You seem to think that the IETF process is a model of clarity and purpose.
For over a decade the vast majority of IETF standards were not STANDARDs.

It seems rather odd to be referring to 2026 as holly writ here when we have
since changed the process so that there are two steps instead of three.
This being largely to recognize the fact that the contemporary criteria for
PS were far in excess of what the criteria had been twenty years ago.

Standards are what people interpret them as, no more, not less. If the IETF
calls something a cat then people are going to expect it to be a feline
even if RFC 3141.56 says that a 'cat' is actually an umbrella.


The obvious reading of 2026 is that Proposed Standard is a document that
describes something that the IETF is proposing should be a standard and
that the part that David cites states the minimum criteria for documents
that are to be endorsed by the IETF as standards proposals.

Like it or not, the endorsement of the IETF is what the various people who
hire consultants to work on IETF specifications are seeking.


The reason we call things "proposed standard" is because we expect
> interoperability.   A thing that can't have or affect interoperability
> probably isn't a "proposed standard."   In this case, what we have is
> definitely a proposed standard and not an informational document; the
> question is whether it's a standard that will get IETF consensus.
>

It really is neither, it is an experiment, the experiment being to see
whether anyone will use it.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Aug 10, 2013 at 3:21 PM, Ted Lemon <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.=
com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Aug 10, 2013, at 8:32 A=
M, Hadriel Kaplan &lt;<a href=3D"mailto:hadriel.kaplan@oracle.com">hadriel.=
kaplan@oracle.com</a>&gt; wrote:<br>

&gt; I&#39;m not saying that will happen in this case at all, but we should=
n&#39;t kid ourselves that it doesn&#39;t matter. =A0If it didn&#39;t matte=
r, people wouldn&#39;t care about labeling their IDs Informational or Exper=
imental. =A0People seem to *want* the PS label, and I don&#39;t think it&#3=
9;s because people want to upgrade to an IS someday. [as an aside: that&#39=
;s what the 2-level RFC experiment should teach us - that there is only 1 l=
evel that people care about, in practice]<br>

<br>
</div>It almost certainly will happen. =A0 But &quot;we shouldn&#39;t do th=
is because someone might later on draw an incorrect conclusion about what w=
e did&quot; is just not a valid argument against advancing the document to =
proposed standard. =A0 What it is is an argument for understanding the IETF=
 process so that when people make assertions about this sort of thing, you =
can have a meaningful debate with them and point at RFCs. =A0 Otherwise you=
r working group can get sidetracked by the ownership assertion problem, whi=
ch as you are already aware can be very damaging<br>
</blockquote><div><br></div><div>You seem to think that the IETF process is=
 a model of clarity and purpose. For over a decade the vast majority of IET=
F standards were not STANDARDs.=A0</div><div><br></div><div>It seems rather=
 odd to be referring to 2026 as holly writ here when we have since changed =
the process so that there are two steps instead of three. This being largel=
y to recognize the fact that the contemporary criteria for PS were far in e=
xcess of what the criteria had been twenty years ago.=A0</div>
<div><br></div><div>Standards are what people interpret them as, no more, n=
ot less. If the IETF calls something a cat then people are going to expect =
it to be a feline even if RFC 3141.56 says that a &#39;cat&#39; is actually=
 an umbrella.</div>
<div><br></div><div><br></div><div>The obvious reading of 2026 is that Prop=
osed Standard is a document that describes something that the IETF is propo=
sing should be a standard and that the part that David cites states the min=
imum criteria for documents that are to be endorsed by the IETF as standard=
s proposals.</div>
<div><br></div><div>Like it or not, the endorsement of the IETF is what the=
 various people who hire consultants to work on IETF specifications are see=
king.</div><div><br></div><div><br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

The reason we call things &quot;proposed standard&quot; is because we expec=
t interoperability. =A0 A thing that can&#39;t have or affect interoperabil=
ity probably isn&#39;t a &quot;proposed standard.&quot; =A0 In this case, w=
hat we have is definitely a proposed standard and not an informational docu=
ment; the question is whether it&#39;s a standard that will get IETF consen=
sus.<br>
</blockquote><div><br></div><div>It really is neither, it is an experiment,=
 the experiment being to see whether anyone will use it.</div><div>=A0<br><=
/div></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com=
/">http://hallambaker.com/</a><br>

</div></div>

--001a11c1b7e6bb773e04e39d2346--

From hallam@gmail.com  Sat Aug 10 13:01:20 2013
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 2BAC021F9EA2 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 13:01:20 -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, 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 h7SQa7dBNr4E for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 13:01:19 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id D51B421F9E94 for <ietf@ietf.org>; Sat, 10 Aug 2013 12:55:24 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id y10so4337917wgg.4 for <ietf@ietf.org>; Sat, 10 Aug 2013 12:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0GJUo7+WzdNRVUI90L0FEgFZ8M5CKKMfs+D5T1l+VYE=; b=Mkw/NqETxSOOzi+7y2cH17x+b2p7A1YJx54Yb1m32x9NzWEVMCZyyHPTcMrudZEZ8I zHaiXcAaN6r86KWoJCaGzhviw2olUpUMuFith0zhDWIY6Pa5qnR3Ip9y30IuTf44CDFX 1uaU19p0c6Ln6BSsNct3aZjHQwuYSHXYE0uCPveKh4WYhE3p4WJtA6ZIHNCcE5M7IpVN Ibm2VoFrfS1lWgHG1m3ljSVyRxyt8QqiSrhXJLyT839+6ifN5sSBjPDQGmAO+8mmvPjz qnIasgxIR4ZRazGbp08oP7ugRBcI/dIl7WXiiGQApsKGYIKpbsnGkwicZe857lTKUyyj mzyg==
MIME-Version: 1.0
X-Received: by 10.180.184.84 with SMTP id es20mr3183017wic.37.1376164523936; Sat, 10 Aug 2013 12:55:23 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Sat, 10 Aug 2013 12:55:23 -0700 (PDT)
In-Reply-To: <274F24F8-BD78-4839-91C2-E873CD897DA1@checkpoint.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com> <274F24F8-BD78-4839-91C2-E873CD897DA1@checkpoint.com>
Date: Sat, 10 Aug 2013 20:55:23 +0100
Message-ID: <CAMm+LwjNqDuWLsX6ixVjU3u9TZ7jUaCPGOFv+V8yT9+ydruBXw@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=001a11c2259c9a112304e39d457e
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 20:01:20 -0000

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

On Sat, Aug 10, 2013 at 7:12 PM, Yoav Nir <ynir@checkpoint.com> wrote:

>
> On Aug 10, 2013, at 6:30 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com>
> wrote:
> >
> >
> > But, if the IESG feels an encoding mechanism doesn't need any targeted
> use-case to be published as a PS, then please ignore my email for purposes
> of consensus.  I'm not strongly for/against - just answering Barry's
> original question, from the peanut gallery as I said in my original email.
>  And as I said in my original email: "[the draft] doesn't appear to contain
> technical errors nor fail to meet its self-stated design objectives."
>
> I don't know about the IESG, but I don't think an encoding mechanism or
> for that matter any format needs to have a targeted use case. WebSec is
> currently debating ([1] whether to put the key pinning data in an HTTP
> header or in a resource. If we choose the latter, there will be the
> question of encoding, and we will probably consider things like XML, JSON,
> ASN.1, and CBOR, or roll our own new one-time format. If someone in the
> group wants to do the one-off format, we will ask why not use XML, JSON, or
> CBOR (nobody's going to ask about ASN.1, because those that care enough to
> suggest it also know to call it BER), and of course you'll need a good
> reason not to use a documented format, whether it's "standard" or not.
>
> Those will be the obvious choices regardless of whether CBOR is
> Informational, Experimental, PS, or still a draft-bormann. Nobody's
> proposing technical changes, so we might as well stick an RFC number on it.
> IMO the only time you stick the "INFORMATIONAL" label on a protocol or an
> encoding, is when you are just documenting a protocol or an encoding that
> exists outside the IETF, and the IETF is not given change control. See
> draft-ietf-websec-x-frame-options for an example. Experimental is for
> things where we don't know if they work in general or if they scale. IOW,
> we're not sure they're appropriate for their stated goal. That is not the
> case with CBOR.
>
> Yes, we can reference CBOR as normative from draft-ietf-websec-key-pinning
> (intended to be PS) with a downref. But just because downrefs exist does
> not mean we should aim for them. PS is the right choice IMO.
>

If key pinning was to use CBOR rather than JSON or ASN.1, I think you are
going to be laughed at.

Since pins are to ASN.1 encoded certificates, I think you are obliged to
choose ASN.1 if you want the browser people to implement.


But lets consider the case that you did decide on CBOR. The Working Group
would then be obliged to look at the specification and persuade key
stakeholders to implement the code. And that might result in changes of the
'remove this half of the specification before we will accept it' variety or
the 'we won't implement unless the encoding is ASN.1'.

At the very least it means that the 'design goals' would get a work out.


But why would CBOR be on the table and not BJSON or JSON-B or any of the
other potential choices?


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Aug 10, 2013 at 7:12 PM, Yoav Nir <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ynir@checkpoint.com" target=3D"_blank">ynir@checkpoint.com</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
On Aug 10, 2013, at 6:30 PM, Hadriel Kaplan &lt;<a href=3D"mailto:hadriel.k=
aplan@oracle.com">hadriel.kaplan@oracle.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; But, if the IESG feels an encoding mechanism doesn&#39;t need any targ=
eted use-case to be published as a PS, then please ignore my email for purp=
oses of consensus. =A0I&#39;m not strongly for/against - just answering Bar=
ry&#39;s original question, from the peanut gallery as I said in my origina=
l email. =A0And as I said in my original email: &quot;[the draft] doesn&#39=
;t appear to contain technical errors nor fail to meet its self-stated desi=
gn objectives.&quot;<br>

<br>
</div>I don&#39;t know about the IESG, but I don&#39;t think an encoding me=
chanism or for that matter any format needs to have a targeted use case. We=
bSec is currently debating ([1] whether to put the key pinning data in an H=
TTP header or in a resource. If we choose the latter, there will be the que=
stion of encoding, and we will probably consider things like XML, JSON, ASN=
.1, and CBOR, or roll our own new one-time format. If someone in the group =
wants to do the one-off format, we will ask why not use XML, JSON, or CBOR =
(nobody&#39;s going to ask about ASN.1, because those that care enough to s=
uggest it also know to call it BER), and of course you&#39;ll need a good r=
eason not to use a documented format, whether it&#39;s &quot;standard&quot;=
 or not.<br>

<br>
Those will be the obvious choices regardless of whether CBOR is Information=
al, Experimental, PS, or still a draft-bormann. Nobody&#39;s proposing tech=
nical changes, so we might as well stick an RFC number on it. IMO the only =
time you stick the &quot;INFORMATIONAL&quot; label on a protocol or an enco=
ding, is when you are just documenting a protocol or an encoding that exist=
s outside the IETF, and the IETF is not given change control. See draft-iet=
f-websec-x-frame-options for an example. Experimental is for things where w=
e don&#39;t know if they work in general or if they scale. IOW, we&#39;re n=
ot sure they&#39;re appropriate for their stated goal. That is not the case=
 with CBOR.<br>

<br>
Yes, we can reference CBOR as normative from draft-ietf-websec-key-pinning =
(intended to be PS) with a downref. But just because downrefs exist does no=
t mean we should aim for them. PS is the right choice IMO.<br></blockquote>
<div><br></div><div>If key pinning was to use CBOR rather than JSON or ASN.=
1, I think you are going to be laughed at.</div><div><br></div><div>Since p=
ins are to ASN.1 encoded certificates, I think you are obliged to choose AS=
N.1 if you want the browser people to implement.=A0</div>
<div><br></div><div><br></div><div>But lets consider the case that you did =
decide on CBOR. The Working Group would then be obliged to look at the spec=
ification and persuade key stakeholders to implement the code. And that mig=
ht result in changes of the &#39;remove this half of the specification befo=
re we will accept it&#39; variety or the &#39;we won&#39;t implement unless=
 the encoding is ASN.1&#39;.=A0</div>
<div><br></div><div>At the very least it means that the &#39;design goals&#=
39; would get a work out.</div><div><br></div><div><br></div><div>But why w=
ould CBOR be on the table and not BJSON or JSON-B or any of the other poten=
tial choices?</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2259c9a112304e39d457e--

From ynir@checkpoint.com  Sat Aug 10 13:54:16 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6432811E8105 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 13:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.523
X-Spam-Level: 
X-Spam-Status: No, score=-10.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TgQ7Iz09YTGP for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 13:54:10 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E9A0C21F8F4D for <ietf@ietf.org>; Sat, 10 Aug 2013 13:47:11 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r7AKl2Qe029895; Sat, 10 Aug 2013 23:47:02 +0300
X-CheckPoint: {5206A6C6-11-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.105]) by DAG-EX10.ad.checkpoint.com ([169.254.3.223]) with mapi id 14.02.0342.003; Sat, 10 Aug 2013 23:47:01 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Index: AQHOlgORJCDbf0KFxEW8MAge3jC8T5mOtzmA
Date: Sat, 10 Aug 2013 20:47:00 +0000
Message-ID: <44E85291-6C18-4727-A918-6984B095A4C7@checkpoint.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com> <274F24F8-BD78-4839-91C2-E873CD897DA1@checkpoint.com> <CAMm+LwjNqDuWLsX6ixVjU3u9TZ7jUaCPGOFv+V8yT9+ydruBXw@mail.gmail.com>
In-Reply-To: <CAMm+LwjNqDuWLsX6ixVjU3u9TZ7jUaCPGOFv+V8yT9+ydruBXw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.172]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 116c46dc8dbe65d82a4583c8e075f2f9526f6ee969
Content-Type: multipart/alternative; boundary="_000_44E852916C184727A9186984B095A4C7checkpointcom_"
MIME-Version: 1.0
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 20:54:16 -0000

--_000_44E852916C184727A9186984B095A4C7checkpointcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


On Aug 10, 2013, at 10:55 PM, Phillip Hallam-Baker <hallam@gmail.com<mailto=
:hallam@gmail.com>> wrote:




On Sat, Aug 10, 2013 at 7:12 PM, Yoav Nir <ynir@checkpoint.com<mailto:ynir@=
checkpoint.com>> wrote:

On Aug 10, 2013, at 6:30 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com<mail=
to:hadriel.kaplan@oracle.com>> wrote:
>
>
> But, if the IESG feels an encoding mechanism doesn't need any targeted us=
e-case to be published as a PS, then please ignore my email for purposes of=
 consensus.  I'm not strongly for/against - just answering Barry's original=
 question, from the peanut gallery as I said in my original email.  And as =
I said in my original email: "[the draft] doesn't appear to contain technic=
al errors nor fail to meet its self-stated design objectives."

I don't know about the IESG, but I don't think an encoding mechanism or for=
 that matter any format needs to have a targeted use case. WebSec is curren=
tly debating ([1] whether to put the key pinning data in an HTTP header or =
in a resource. If we choose the latter, there will be the question of encod=
ing, and we will probably consider things like XML, JSON, ASN.1, and CBOR, =
or roll our own new one-time format. If someone in the group wants to do th=
e one-off format, we will ask why not use XML, JSON, or CBOR (nobody's goin=
g to ask about ASN.1, because those that care enough to suggest it also kno=
w to call it BER), and of course you'll need a good reason not to use a doc=
umented format, whether it's "standard" or not.

Those will be the obvious choices regardless of whether CBOR is Information=
al, Experimental, PS, or still a draft-bormann. Nobody's proposing technica=
l changes, so we might as well stick an RFC number on it. IMO the only time=
 you stick the "INFORMATIONAL" label on a protocol or an encoding, is when =
you are just documenting a protocol or an encoding that exists outside the =
IETF, and the IETF is not given change control. See draft-ietf-websec-x-fra=
me-options for an example. Experimental is for things where we don't know i=
f they work in general or if they scale. IOW, we're not sure they're approp=
riate for their stated goal. That is not the case with CBOR.

Yes, we can reference CBOR as normative from draft-ietf-websec-key-pinning =
(intended to be PS) with a downref. But just because downrefs exist does no=
t mean we should aim for them. PS is the right choice IMO.

If key pinning was to use CBOR rather than JSON or ASN.1, I think you are g=
oing to be laughed at.

Since pins are to ASN.1 encoded certificates, I think you are obliged to ch=
oose ASN.1 if you want the browser people to implement.

I think the browser people also have a JSON parser lying around somewhere. =
But I agree that CBOR would increase the cost of implementation, and that's=
 a good argument against choosing CBOR. It's also a good argument against c=
hoosing any new encoding anybody might propose.

But lets consider the case that you did decide on CBOR. The Working Group w=
ould then be obliged to look at the specification and persuade key stakehol=
ders to implement the code. And that might result in changes of the 'remove=
 this half of the specification before we will accept it' variety or the 'w=
e won't implement unless the encoding is ASN.1'.

At the very least it means that the 'design goals' would get a work out.


But why would CBOR be on the table and not BJSON or JSON-B or any of the ot=
her potential choices?

I don't see why any of them would be off the table.

Yoav



--_000_44E852916C184727A9186984B095A4C7checkpointcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <9734E4BAEB136640BDA72F5515ABF153@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On Aug 10, 2013, at 10:55 PM, Phillip Hallam-Baker &lt;<a href=3D"mail=
to:hallam@gmail.com">hallam@gmail.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Sat, Aug 10, 2013 at 7:12 PM, Yoav Nir <span =
dir=3D"ltr">
&lt;<a href=3D"mailto:ynir@checkpoint.com" target=3D"_blank">ynir@checkpoin=
t.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
On Aug 10, 2013, at 6:30 PM, Hadriel Kaplan &lt;<a href=3D"mailto:hadriel.k=
aplan@oracle.com">hadriel.kaplan@oracle.com</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; But, if the IESG feels an encoding mechanism doesn't need any targeted=
 use-case to be published as a PS, then please ignore my email for purposes=
 of consensus. &nbsp;I'm not strongly for/against - just answering Barry's =
original question, from the peanut gallery
 as I said in my original email. &nbsp;And as I said in my original email: =
&quot;[the draft] doesn't appear to contain technical errors nor fail to me=
et its self-stated design objectives.&quot;<br>
<br>
</div>
I don't know about the IESG, but I don't think an encoding mechanism or for=
 that matter any format needs to have a targeted use case. WebSec is curren=
tly debating ([1] whether to put the key pinning data in an HTTP header or =
in a resource. If we choose the
 latter, there will be the question of encoding, and we will probably consi=
der things like XML, JSON, ASN.1, and CBOR, or roll our own new one-time fo=
rmat. If someone in the group wants to do the one-off format, we will ask w=
hy not use XML, JSON, or CBOR (nobody's
 going to ask about ASN.1, because those that care enough to suggest it als=
o know to call it BER), and of course you'll need a good reason not to use =
a documented format, whether it's &quot;standard&quot; or not.<br>
<br>
Those will be the obvious choices regardless of whether CBOR is Information=
al, Experimental, PS, or still a draft-bormann. Nobody's proposing technica=
l changes, so we might as well stick an RFC number on it. IMO the only time=
 you stick the &quot;INFORMATIONAL&quot; label
 on a protocol or an encoding, is when you are just documenting a protocol =
or an encoding that exists outside the IETF, and the IETF is not given chan=
ge control. See draft-ietf-websec-x-frame-options for an example. Experimen=
tal is for things where we don't
 know if they work in general or if they scale. IOW, we're not sure they're=
 appropriate for their stated goal. That is not the case with CBOR.<br>
<br>
Yes, we can reference CBOR as normative from draft-ietf-websec-key-pinning =
(intended to be PS) with a downref. But just because downrefs exist does no=
t mean we should aim for them. PS is the right choice IMO.<br>
</blockquote>
<div><br>
</div>
<div>If key pinning was to use CBOR rather than JSON or ASN.1, I think you =
are going to be laughed at.</div>
<div><br>
</div>
<div>Since pins are to ASN.1 encoded certificates, I think you are obliged =
to choose ASN.1 if you want the browser people to implement.&nbsp;</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
I think the browser people also have a JSON parser lying around somewhere. =
But I agree that CBOR would increase the cost of implementation, and that's=
 a good argument against choosing CBOR. It's also a good argument against c=
hoosing any new encoding anybody
 might propose.</div>
<div><br>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>But lets consider the case that you did decide on CBOR. The Working Gr=
oup would then be obliged to look at the specification and persuade key sta=
keholders to implement the code. And that might result in changes of the 'r=
emove this half of the specification
 before we will accept it' variety or the 'we won't implement unless the en=
coding is ASN.1'.&nbsp;</div>
<div><br>
</div>
<div>At the very least it means that the 'design goals' would get a work ou=
t.</div>
<div><br>
</div>
<div><br>
</div>
<div>But why would CBOR be on the table and not BJSON or JSON-B or any of t=
he other potential choices?</div>
</div>
</div>
</div>
</blockquote>
<br>
</div>
<div>I don't see why any of them would be off the table.</div>
<div><br>
</div>
<div>Yoav</div>
<div><br>
</div>
<br>
</body>
</html>

--_000_44E852916C184727A9186984B095A4C7checkpointcom_--

From hadriel.kaplan@oracle.com  Sat Aug 10 13:57:17 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61C5421F9B94 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 13:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.082,  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 cSwiqLwOfdzg for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 13:57:10 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4C611E81A5 for <ietf@ietf.org>; Sat, 10 Aug 2013 13:50:51 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7AKof4t022998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Aug 2013 20:50:42 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7AKoep0029322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 10 Aug 2013 20:50:41 GMT
Received: from abhmt105.oracle.com (abhmt105.oracle.com [141.146.116.57]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7AKoexO029317; Sat, 10 Aug 2013 20:50:40 GMT
Received: from [192.168.2.10] (/184.61.127.93) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 10 Aug 2013 13:50:40 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
Date: Sat, 10 Aug 2013 16:50:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <86467F8D-A309-458C-B80F-C1890BB3F32F@oracle.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com> <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: Barry Leiba <barryleiba@computer.org>, 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, 10 Aug 2013 20:57:17 -0000

On Aug 10, 2013, at 12:25 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 10, 2013, at 11:30 AM, Hadriel Kaplan =
<hadriel.kaplan@oracle.com> wrote:
>> That's fair, and I should have been clearer.  I think 'Informatonal' =
is more appropriate for now, because I don't think we know what the "it" =
is in your above statements - i.e., I don't know what Internet use-cases =
and/or IETF protocols CBOR was intended to be used for.  For example, is =
the purpose of it to be JSONv2 for Javascript uses, vs. a new encoding =
for DNS AXFR/IXFR, vs. an encoding for a NoSQL inter-DB synch protocol, =
vs. a new encoding for MIME bodies in SMTP.  I don't see how we can know =
whether an encoding mechanism is sound or broken without knowing what =
its intended/motivating use-case is.
>=20
> Section 1.1 goes on at some length about the intended use for the =
document is.   If you believe it is unclear or incomplete, some pointed =
questions about it would be entirely appropriate.

OK... I read that section previously, and I just re-read it now, and I =
think that section is quite clear on the *design* goals.  And I think it =
meets those goals.  That's why I said, if that's all that's needed for =
PS, then I'm cool.  I literally don't know whether or not a PS for an =
encoding mechanism needs any more than that - I deal mostly with =
protocol docs, not encoding docs.  And I don't know whether the same =
considerations make sense or not for an encoding doc.  I'm quite =
sensitive to not blocking people from progress, as I've been in similar =
situations myself.  So I'm just giving my 2 cents, because I happen to =
have looked at it for using it as a binary JSON alternative for a =
non-IETF application.

What I'm curious about is the intended IETF protocol use-case(s).  I =
don't think a use-case even needs to be stated in the doc, because this =
doc is really about a generic object encoding mechanism; it has =
properties X, and if you want properties X then you should use it.  I'm =
more just asking what the authors were targeting, if anything.  For =
example, if it's intended for a new encoding mechanism for IPFIX I'd =
have strong opinions one way; whereas if it's a new encoding mechanism =
for DNS zone transfers I'd probably have a different opinion.  But if =
the use-case is just "anything that needs our properties X", that's fine =
too.

=46rom reading the doc, it feels like it's intended to be the successor =
for MessagePack.  Afaik, MessagePack is used by a broad community as a =
drop-in replacement for JSON. (I could be wrong on that, it's just my =
impression and how I plan to use it)  If that's the goal of CBOR, then I =
think it will have a tough time of it but I've got no objection to =
letting it try.


>> I read RFC 1958 yesterday when I saw your previous email, and I read =
it again this morning when I saw your comment above.  But I still don't =
grok which part of it let's me tell a WG Chair: "No, just because =
there's a PS RFC doing something similar, doesn't mean we can't do =
something better and more appropriate for this particular application".  =
I mean I can tell them that now, but it doesn't carry much weight.  What =
part of RFC 1958 would help me making such a statement?
>=20
> Section 3.   If you only read section 3.2, and don't read the last =
clause of the last sentence in that section, then you might come to the =
conclusion that once an RFC is published that solves a specific problem, =
no other RFC can ever be published that addresses a similar problem.
> Section 3.2 definitely does argue that if you have a good solution to =
a problem, you shouldn't invent a new solution to the problem.   If you =
were to apply section 3.2 strictly without all the caveats, you could =
argue that this document shouldn't be published because ASN.1 solves the =
same problem.   But that's not a correct reading of the document, =
because of all the other caveats that are listed in subsequent sections.

Ahh, I see.  I did read that sentence but it felt more like an =
afterthought escape clause. :)
That's good to know though.

-hadriel


From masinter@adobe.com  Sat Aug 10 15:45:10 2013
Return-Path: <masinter@adobe.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D78921F9B53 for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 15:45:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.529
X-Spam-Level: 
X-Spam-Status: No, score=-5.529 tagged_above=-999 required=5 tests=[AWL=-0.419, BAYES_05=-1.11, 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 Fz6cimi1VM-D for <ietf@ietfa.amsl.com>; Sat, 10 Aug 2013 15:45:04 -0700 (PDT)
Received: from exprod6og105.obsmtp.com (exprod6og105.obsmtp.com [64.18.1.189]) by ietfa.amsl.com (Postfix) with ESMTP id A15A621F9B92 for <ietf@ietf.org>; Sat, 10 Aug 2013 15:37:58 -0700 (PDT)
Received: from outbound-smtp-1.corp.adobe.com ([192.150.11.134]) by exprod6ob105.postini.com ([64.18.5.12]) with SMTP ID DSNKUgbAwpoZg23cqXP5c3fCr72KJpm0zuFL@postini.com; Sat, 10 Aug 2013 15:37:59 PDT
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52]) by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r7AMYOD8006820; Sat, 10 Aug 2013 15:34:24 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r7AMbrw7024682; Sat, 10 Aug 2013 15:37:53 -0700 (PDT)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Sat, 10 Aug 2013 15:37:53 -0700
From: Larry Masinter <masinter@adobe.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Date: Sat, 10 Aug 2013 15:37:34 -0700
Subject: RE: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Index: Ac6WGNtb8dfZg5HgT1++SEfYniOWww==
Message-ID: <C68CB012D9182D408CED7B884F441D4D34728C1386@nambxv01a.corp.adobe.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: "Hollenbeck, Scott" <shollenbeck@verisign.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, 10 Aug 2013 22:45:10 -0000

BCP 70 " Guidelines for the Use of Extensible Markup Language (XML)  within=
 IETF Protocols"
attempted to outline some of the design considerations for data representat=
ion using XML.
In 2003, it represented the consensus and also the disagreements about what
was "best current practice" at the time.

Section 3 of BCP 70, "Alternatives", lists some of the alternatives and pro=
vides
a comparison.

I think what might be missing is an update to BCP 70 or a companion which m=
ore
explicitly compares XML, JSON, CBOR and other alternatives in use in IETF p=
rotocols.

If you're interested in this work, perhaps you might review BCP 70 and sugg=
est
updates.

Larry
--
http://larry.masinter.net





From peter@akayla.com  Sat Aug 10 21:57:00 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D207811E80D7; Sat, 10 Aug 2013 21:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0mIgiuRhOm+I; Sat, 10 Aug 2013 21:56:52 -0700 (PDT)
Received: from p3plsmtpa07-10.prod.phx3.secureserver.net (p3plsmtpa07-10.prod.phx3.secureserver.net [173.201.192.239]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE5D21F9A71; Sat, 10 Aug 2013 21:52:25 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-10.prod.phx3.secureserver.net with  id BGsN1m00A1huGat01GsNgf; Sat, 10 Aug 2013 21:52:24 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-jabley-dnsext-eui48-eui64-rrtypes.all@tools.ietf.org>
Subject: Gen-ART Telechat review of draft-jabley-dnsext-eui48-eui64-rrtypes-05
Date: Sat, 10 Aug 2013 21:52:55 -0700
Message-ID: <08c101ce964e$a618c620$f24a5260$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6WTjVLeQ4X/0nrTsSskAoejQ+VSw==
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: Sun, 11 Aug 2013 04:57:01 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please wait for direction from your document shepherd or AD before posting a
new version of the draft.

Document: draft-jabley-dnsext-eui48-eui64-rrtypes-05
Reviewer: Peter Yee
Review Date: July-07-2013
IETF LC End Date: July-17-2013
IESG Telechat date: August-15-2013

Summary: This draft is basically ready for publication as an Informational
RFC, but has nits that should be fixed before publication. [Ready with nits]

This review is the same as the IETF LC review of this draft, which remain
unchanged for the telechat.  This draft defines DNS Resources Record Types
for encoding IEEE 802 EUI-48 and EUI-64 addresses.  Potential privacy issues
with this scheme have been soundly beaten to death with extreme prejudice.

Major issues:

Minor issues:

Nits:

Page 1, Abstract, 1st paragraph: After "e.g.", append a comma and delete an
extraneous space before "Ethernet".

Page 3, Introduction, 1st paragraph, 2nd sentence: change "This" to "These"
and change "specification defines" to "specifications define". 

Page 3, Introduction, 2nd paragraph: append a comma after "e.g.".

		-Peter Yee




From hallam@gmail.com  Sun Aug 11 06:26:21 2013
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 5395521E8051 for <ietf@ietfa.amsl.com>; Sun, 11 Aug 2013 06:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[AWL=-1.157, BAYES_00=-2.599, FRT_ADOBE2=2.455, 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 OkbTwsIbGIeC for <ietf@ietfa.amsl.com>; Sun, 11 Aug 2013 06:26:20 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8B64421F853A for <ietf@ietf.org>; Sun, 11 Aug 2013 06:19:23 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id hq12so900791wib.14 for <ietf@ietf.org>; Sun, 11 Aug 2013 06:19: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:date:message-id:subject:from:to :cc:content-type; bh=l1ykFVNmWeh2uNxaohE+cCCu6yTzJA7j/xp12f7Ppy0=; b=AUrzQyHWIGBeHfckDKK4w9L4IeJeonmgweAm3sGsjC6b5MLmG9tcrrZdjzZxIYbhE4 jT04BztlVhmfwR/AgNdsd4xAAqH0pngcHHhwvHGOG6p0dqWEMoXAfOkbrmnT/beTgxRM il31ecWvR+sub4hNCAaZ3qlQWgpMgeJ3M+pcJLq7KIs4c9F08I6iin9hHv0t0AIZrunT sl1tS3Bpu5k/fxFjvktmTvoaXeU9nuYYb2X9DfsiDXiQpgTjPNoA2MtnLHI0DqtpcVFj 4CLm9uk6zbcWYYOuVb6HSxUloN9Ro2Tvjnizao5KcJvCuuvqjb14+7N9M/OxWeWrHnAm 1dyw==
MIME-Version: 1.0
X-Received: by 10.180.184.84 with SMTP id es20mr4401809wic.37.1376227161408; Sun, 11 Aug 2013 06:19:21 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Sun, 11 Aug 2013 06:19:20 -0700 (PDT)
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D34728C1386@nambxv01a.corp.adobe.com>
References: <C68CB012D9182D408CED7B884F441D4D34728C1386@nambxv01a.corp.adobe.com>
Date: Sun, 11 Aug 2013 14:19:20 +0100
Message-ID: <CAMm+Lwii-4iWsEDzvfhBY7XxvmbgbOkbDVrdbr25Eoq-ZMmqYw@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Larry Masinter <masinter@adobe.com>
Content-Type: multipart/alternative; boundary=001a11c2259c160e1d04e3abdb0c
Cc: "Hollenbeck, Scott" <shollenbeck@verisign.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Aug 2013 13:26:21 -0000

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

On Sat, Aug 10, 2013 at 11:37 PM, Larry Masinter <masinter@adobe.com> wrote:

> BCP 70 " Guidelines for the Use of Extensible Markup Language (XML)
>  within IETF Protocols"
> attempted to outline some of the design considerations for data
> representation using XML.
> In 2003, it represented the consensus and also the disagreements about what
> was "best current practice" at the time.
>
> Section 3 of BCP 70, "Alternatives", lists some of the alternatives and
> provides
> a comparison.
>
> I think what might be missing is an update to BCP 70 or a companion which
> more
> explicitly compares XML, JSON, CBOR and other alternatives in use in IETF
> protocols.
>
> If you're interested in this work, perhaps you might review BCP 70 and
> suggest
> updates.
>

Independently of CBOR, it would be worth revisiting this and writing best
practices for using JSON.

One of the areas that XML thought it had handled was extensibility. In
retrospect, I don't think extensibility was handled anywhere near as well
as people imagined at that time. We had to rewrite the SAML schema despite
having the input of one of the XML main authors leading the work. What we
thought would be a good extensibility mechanism turned out not to be in
practice.

At this point JSON has a reasonable extensibility story but not one that I
have seen committed to paper...


I think that we could learn something from XML Schema as well. XML Scema
and DTDs are really tools for validating documents and they are useful
there because they allow the validator to tell the user which line and
column an error occurred.

XML schema can be used as a tool for validating input to a Web Service but
much of the effort is counterproductive. Who cares which order the elements
are presented? I am not aware of any widely used programming language that
would, the order of definition of elements in a structure is only visible
at all in LISP like languages.


I see a value of using some sort of tool to define what elements do and do
not have specified semantics in a protocol and to describe the structure,
i.e. a 'schema' but we need something with a tenth the features of XML
Schema and we need to address extensibility.



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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Aug 10, 2013 at 11:37 PM, Larry Masinter <span dir=3D"ltr">=
&lt;<a href=3D"mailto:masinter@adobe.com" target=3D"_blank">masinter@adobe.=
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">BCP 70 &quot; Guidelines for the Use of Exte=
nsible Markup Language (XML) =A0within IETF Protocols&quot;<br>
attempted to outline some of the design considerations for data representat=
ion using XML.<br>
In 2003, it represented the consensus and also the disagreements about what=
<br>
was &quot;best current practice&quot; at the time.<br>
<br>
Section 3 of BCP 70, &quot;Alternatives&quot;, lists some of the alternativ=
es and provides<br>
a comparison.<br>
<br>
I think what might be missing is an update to BCP 70 or a companion which m=
ore<br>
explicitly compares XML, JSON, CBOR and other alternatives in use in IETF p=
rotocols.<br>
<br>
If you&#39;re interested in this work, perhaps you might review BCP 70 and =
suggest<br>
updates.<br>
</blockquote></div><br>Independently of CBOR, it would be worth revisiting =
this and writing best practices for using JSON.</div><div class=3D"gmail_ex=
tra"><br></div><div class=3D"gmail_extra">One of the areas that XML thought=
 it had handled was extensibility. In retrospect, I don&#39;t think extensi=
bility was handled anywhere near as well as people imagined at that time. W=
e had to rewrite the SAML schema despite having the input of one of the XML=
 main authors leading the work. What we thought would be a good extensibili=
ty mechanism turned out not to be in practice.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">At this poi=
nt JSON has a reasonable extensibility story but not one that I have seen c=
ommitted to paper...</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">I think that we could learn something =
from XML Schema as well. XML Scema and DTDs are really tools for validating=
 documents and they are useful there because they allow the validator to te=
ll the user which line and column an error occurred.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">XML schema =
can be used as a tool for validating input to a Web Service but much of the=
 effort is counterproductive. Who cares which order the elements are presen=
ted? I am not aware of any widely used programming language that would, the=
 order of definition of elements in a structure is only visible at all in L=
ISP like languages.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">I see a value of using some sort of tool to defin=
e what elements do and do not have specified semantics in a protocol and to=
 describe the structure, i.e. a &#39;schema&#39; but we need something with=
 a tenth the features of XML Schema and we need to address extensibility.</=
div>
<div class=3D"gmail_extra"><br><br clear=3D"all"><div><br></div>-- <br>Webs=
ite: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2259c160e1d04e3abdb0c--

From vinayakh@gmail.com  Mon Aug 12 06:18:45 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABF721F9B10 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 06:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level: 
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[AWL=-0.732, 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 GLa0UbpQPj4U for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 06:18:44 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1673121F86B2 for <ietf@ietf.org>; Mon, 12 Aug 2013 06:09:34 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo5so6815355pbc.9 for <ietf@ietf.org>; Mon, 12 Aug 2013 06:09:33 -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=r/B68aryIXR8JjNrwcFoPItxw5xDl15M6am+xNVAtYc=; b=jGBsu/5+T0SC5ElUKmmgGRXYQxA2eHtsVBmZS5Nz+EwhZ8oZSMGPGaJVymtDYyBebW 2Wnb111kTZx7DyiASjAhQhLSpwkAsk+a0AVwm1HWdhCNfIG42dEMlk/i3ZKll3SCyPTH WKebk7kLlcMsrAitGG05yHkSHFhw8QhEJJuTMhPBEvoVpUHeFzQfJB8qnEJzVimg10Z2 HZtnsUU+yqDqUobssoahruwvQDoeulHtZEHnMh43ekZ3LNLcn/kGAN6tX69bCJYe3Bjx RdVAtz5HDGVGtFGRkpeY+70dZdsb3W0XqgD2cPIqw+jUsSXjZraZ4uge8S0s9OqSQdCw 5AvA==
MIME-Version: 1.0
X-Received: by 10.68.234.102 with SMTP id ud6mr24513556pbc.50.1376312973465; Mon, 12 Aug 2013 06:09:33 -0700 (PDT)
Received: by 10.66.100.226 with HTTP; Mon, 12 Aug 2013 06:09:32 -0700 (PDT)
Date: Mon, 12 Aug 2013 18:39:32 +0530
Message-ID: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>
Subject: Data collection for remote participation
From: Vinayak Hegde <vinayakh@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: Mon, 12 Aug 2013 13:18:45 -0000

Hi,

There has been a lot of discussion on the IETF mailing list regarding
improving remote participation and improving diversity on the mailing
lists and in the working groups. I think the two are related. I think
everyone broadly agrees that remote participation can be better. If
nothing else, it will tell about who the remote participants are. I
had proposed a few steps in this direction by improving the data
collection for remote participation in the IAOC Sunday meeting.
Posting them below again for discussion on the mailing lists.

It can be a simple form that asks the following questions (Can be
refined - this is just a start)
1. Name:
2. Country:
3. Duration of participation in IETF (either in number of years or
number of meetings)
4. Employer ?
5. Working groups interested in.

This can be voluntary and can be done pre-IETF meeting. As of now
there is no structured way to know how many people wre active in the
jabber room or listening on the audio stream.

I can see that this has multiple benefits.
1. If the number of participants in a certain WG is more, it would
push the WG chair to request for the slides/agenda available earlier.

2. If there are consistently more participation from around the world,
the the WG chair can request for a meetecho recording so people can
follow the group even if they cannot attend the meeting live. This
could be useful for people who have clashing schedules as well.

3. Over a longer period of time, it can help IETF plan and encourage
remote participation. Currently there is no hard data on number of
remote participants. There is however a lot of hand waving so this
will get some useful data into the system.

-- Vinayak

From alejandroacostaalamo@gmail.com  Mon Aug 12 08:58:08 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25E8B21E817A for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 08:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.150,  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 cWwuijMzZEtK for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 08:57:57 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 354DB21E81C9 for <ietf@ietf.org>; Mon, 12 Aug 2013 08:05:04 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id hq12so1819884wib.8 for <ietf@ietf.org>; Mon, 12 Aug 2013 08:05:03 -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=Vr1IqYyaXaFCk3yAnzzh3STC/muujdpq+SfJrtpCLzA=; b=Oh8NMjtVA37x4pZ+7mel6CfgNPLpHi14S8u2Atq6G4xecO/I2cNydat4QZ7/wdARvn giB7ErTi/Dq1UYWmtmUS59xwS0kStqLN4EhNwwR9Bf5fxZlhpeNSrWumrT93jl4/SsnU WDKkRF+O0UIvd8QByxMS91rlCDLpXZjKUtunc+Y8akboDkpAheLuuyjLXDNkj0Ye359U Zfc+kN8jYGC/hkiNRK3mpmdJFqvGTB4LtY7mzYT11jKkCRha9UWdCLhKCqYIdXE7wyI8 dQvrePO/WfKsgKJM9+I0qZclg6N7Z/Zvek4oXILAEBG/jNeIZOtQNm7mvAI5WSkYQ3cv Lbgg==
MIME-Version: 1.0
X-Received: by 10.194.80.168 with SMTP id s8mr7078522wjx.86.1376319903297; Mon, 12 Aug 2013 08:05:03 -0700 (PDT)
Received: by 10.217.143.196 with HTTP; Mon, 12 Aug 2013 08:05:03 -0700 (PDT)
In-Reply-To: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>
Date: Mon, 12 Aug 2013 10:35:03 -0430
Message-ID: <CAOmxzdxTftsbyCghsGyfBrhuiKrti3mwRfNNzFCiUoTddpeFyQ@mail.gmail.com>
Subject: Re: Data collection for remote participation
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Vinayak Hegde <vinayakh@gmail.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: Mon, 12 Aug 2013 15:58:09 -0000

Hi Vinayak,
  First, well done, I fully agree with your email. I have two
questions for you/the group:

1)  I wonder if in your proposal you are considering some sort of
charge for remote participation. IMHO I do not think we are yet
prepare to charge.
2) When you mention that filling the responses (pre-IETF) is
voluntary, so, I guess it's not mandatory, am I right?. We should also
define what pre-IETF is..., it sounds obvious but it can be read as
the pre-WG session.

  I would add to your proposal some kind of activities from local ISOC chapters.

Thanks,

Alejandro,




On 8/12/13, Vinayak Hegde <vinayakh@gmail.com> wrote:
> Hi,
>
> There has been a lot of discussion on the IETF mailing list regarding
> improving remote participation and improving diversity on the mailing
> lists and in the working groups. I think the two are related. I think
> everyone broadly agrees that remote participation can be better. If
> nothing else, it will tell about who the remote participants are. I
> had proposed a few steps in this direction by improving the data
> collection for remote participation in the IAOC Sunday meeting.
> Posting them below again for discussion on the mailing lists.
>
> It can be a simple form that asks the following questions (Can be
> refined - this is just a start)
> 1. Name:
> 2. Country:
> 3. Duration of participation in IETF (either in number of years or
> number of meetings)
> 4. Employer ?
> 5. Working groups interested in.
>
> This can be voluntary and can be done pre-IETF meeting. As of now
> there is no structured way to know how many people wre active in the
> jabber room or listening on the audio stream.
>
> I can see that this has multiple benefits.
> 1. If the number of participants in a certain WG is more, it would
> push the WG chair to request for the slides/agenda available earlier.
>
> 2. If there are consistently more participation from around the world,
> the the WG chair can request for a meetecho recording so people can
> follow the group even if they cannot attend the meeting live. This
> could be useful for people who have clashing schedules as well.
>
> 3. Over a longer period of time, it can help IETF plan and encourage
> remote participation. Currently there is no hard data on number of
> remote participants. There is however a lot of hand waving so this
> will get some useful data into the system.
>
> -- Vinayak
>


-- 
=====
^A.......o$

From jgunn6@csc.com  Mon Aug 12 09:00:13 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8901921E81C7; Mon, 12 Aug 2013 09:00:12 -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.006,  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 TSKYqTTHH417; Mon, 12 Aug 2013 09:00:05 -0700 (PDT)
Received: from mail170.messagelabs.com (mail170.messagelabs.com [216.82.253.227]) by ietfa.amsl.com (Postfix) with ESMTP id 1F88221E8203; Mon, 12 Aug 2013 08:14:42 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-6.tower-170.messagelabs.com!1376320477!4667787!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24233 invoked from network); 12 Aug 2013 15:14:37 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-6.tower-170.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Aug 2013 15:14:37 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r7CFAF5x030455; Mon, 12 Aug 2013 11:10:16 -0400
In-Reply-To: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>
To: Vinayak Hegde <vinayakh@gmail.com>
MIME-Version: 1.0
Subject: Re: Data collection for remote participation
X-KeepSent: F816F7EA:E9F0330D-85257BC5:0051D5AD; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com>
Date: Mon, 12 Aug 2013 11:14:35 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/12/2013 11:07:58 AM, Serialize complete at 08/12/2013 11:07:58 AM
Content-Type: multipart/alternative; boundary="=_alternative 0053BC3085257BC5_="
Cc: ietf-bounces@ietf.org, 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: Mon, 12 Aug 2013 16:00:14 -0000

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

As someone who has done it both ways (in person and remotely) I have a 
couple of comments.

Having the slides available early is an advantage to BOTH in-person and 
remote participants.

As a remote participant I "need" the slides available about 30 min before 
the session.
As a participant (in-person or remote) it is VERY helpful to have the 
slides available much earlier.
So I do not think "how many remote participants for this session" is a 
useful parameter for "how important is it to get the slides out early"

On the other hand, I DO think  that the number of remote participants for 
a particular session IS a useful parameter for "how important is it to 
have an active jabber scribe" and "how important is it to make sure the 
audio streaming is working well."


As a remote participant the list of "working groups I am interested in" is 
different from the list of "working groups I plan to participate in 
remotely".
There is a SMALL list of working groups I am willing to get up at 2:30 AM 
(my time) to participate in (otherwise I MIGHT look at the slides and read 
the minutes when they come out)
There is a much LARGER list of working groups I  will participate in 
remotely if they are in (my time) "normal working hours".

There is nothing you can do about this a priori, but if the records show 
that, for instance -  whenever IETF is in North America, WG abc 
consistently has a large number of remote participants from Europe, and WG 
xyz consistently has a large number of remote participants from Asia - 
that could be factored into the agenda scheduling process.

In-person participants are not asked to list the WG they are interested 
in.  That is accomplished by the blue sheets.  I wonder if there is a way 
to do something analogous to the blue sheets for remote participants, 
whether  through jabber, email, doodle-poll, wiki, whatever. 

I agree with your points 2 and 3.

Janet


ietf-bounces@ietf.org wrote on 08/12/2013 09:09:32 AM:

> From: Vinayak Hegde <vinayakh@gmail.com>
> To: IETF Discussion Mailing List <ietf@ietf.org>
> Date: 08/12/2013 09:19 AM
> Subject: Data collection for remote participation
> Sent by: ietf-bounces@ietf.org
> 
> Hi,
> 
> There has been a lot of discussion on the IETF mailing list regarding
> improving remote participation and improving diversity on the mailing
> lists and in the working groups. I think the two are related. I think
> everyone broadly agrees that remote participation can be better. If
> nothing else, it will tell about who the remote participants are. I
> had proposed a few steps in this direction by improving the data
> collection for remote participation in the IAOC Sunday meeting.
> Posting them below again for discussion on the mailing lists.
> 
> It can be a simple form that asks the following questions (Can be
> refined - this is just a start)
> 1. Name:
> 2. Country:
> 3. Duration of participation in IETF (either in number of years or
> number of meetings)
> 4. Employer ?
> 5. Working groups interested in.
> 
> This can be voluntary and can be done pre-IETF meeting. As of now
> there is no structured way to know how many people wre active in the
> jabber room or listening on the audio stream.
> 
> I can see that this has multiple benefits.
> 1. If the number of participants in a certain WG is more, it would
> push the WG chair to request for the slides/agenda available earlier.
> 
> 2. If there are consistently more participation from around the world,
> the the WG chair can request for a meetecho recording so people can
> follow the group even if they cannot attend the meeting live. This
> could be useful for people who have clashing schedules as well.
> 
> 3. Over a longer period of time, it can help IETF plan and encourage
> remote participation. Currently there is no hard data on number of
> remote participants. There is however a lot of hand waving so this
> will get some useful data into the system.
> 
> -- Vinayak

--=_alternative 0053BC3085257BC5_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">As someone who has done it both ways (in
person and remotely) I have a couple of comments.</font>
<br>
<br><font size=2 face="sans-serif">Having the slides available early is
an advantage to BOTH in-person and remote participants.</font>
<br>
<br><font size=2 face="sans-serif">As a remote participant I &quot;need&quot;
the slides available about 30 min before the session.</font>
<br><font size=2 face="sans-serif">As a participant (in-person or remote)
it is VERY helpful to have the slides available much earlier.</font>
<br><font size=2 face="sans-serif">So I do not think &quot;how many remote
participants for this session&quot; is a useful parameter for &quot;how
important is it to get the slides out early&quot;</font>
<br>
<br><font size=2 face="sans-serif">On the other hand, I DO think &nbsp;that
the number of remote participants for a particular session IS a useful
parameter for &quot;how important is it to have an active jabber scribe&quot;
and &quot;how important is it to make sure the audio streaming is working
well.&quot;</font>
<br>
<br>
<br><font size=2 face="sans-serif">As a remote participant the list of
&quot;working groups I am interested in&quot; is different from the list
of &quot;working groups I plan to participate in remotely&quot;.</font>
<br><font size=2 face="sans-serif">There is a SMALL list of working groups
I am willing to get up at 2:30 AM (my time) to participate in (otherwise
I MIGHT look at the slides and read the minutes when they come out)</font>
<br><font size=2 face="sans-serif">There is a much LARGER list of working
groups I &nbsp;will participate in remotely if they are in (my time) &quot;normal
working hours&quot;.</font>
<br>
<br><font size=2 face="sans-serif">There is nothing you can do about this
a priori, but if the records show that, for instance - &nbsp;whenever IETF
is in North America, WG abc consistently has a large number of remote participants
from Europe, and WG xyz consistently has a large number of remote participants
from Asia - &nbsp;that could be factored into the agenda scheduling process.</font>
<br>
<br><font size=2 face="sans-serif">In-person participants are not asked
to list the WG they are interested in. &nbsp;That is accomplished by the
blue sheets. &nbsp;I wonder if there is a way to do something analogous
to the blue sheets for remote participants, whether &nbsp;through jabber,
email, doodle-poll, wiki, whatever. </font>
<br>
<br><font size=2 face="sans-serif">I agree with your points 2 and 3.</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 08/12/2013 09:09:32
AM:<br>
<br>
&gt; From: Vinayak Hegde &lt;vinayakh@gmail.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: IETF Discussion Mailing List &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 08/12/2013 09:19 AM</font></tt>
<br><tt><font size=2>&gt; Subject: Data collection for remote participation</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Hi,<br>
&gt; <br>
&gt; There has been a lot of discussion on the IETF mailing list regarding<br>
&gt; improving remote participation and improving diversity on the mailing<br>
&gt; lists and in the working groups. I think the two are related. I think<br>
&gt; everyone broadly agrees that remote participation can be better. If<br>
&gt; nothing else, it will tell about who the remote participants are.
I<br>
&gt; had proposed a few steps in this direction by improving the data<br>
&gt; collection for remote participation in the IAOC Sunday meeting.<br>
&gt; Posting them below again for discussion on the mailing lists.<br>
&gt; <br>
&gt; It can be a simple form that asks the following questions (Can be<br>
&gt; refined - this is just a start)<br>
&gt; 1. Name:<br>
&gt; 2. Country:<br>
&gt; 3. Duration of participation in IETF (either in number of years or<br>
&gt; number of meetings)<br>
&gt; 4. Employer ?<br>
&gt; 5. Working groups interested in.<br>
&gt; <br>
&gt; This can be voluntary and can be done pre-IETF meeting. As of now<br>
&gt; there is no structured way to know how many people wre active in the<br>
&gt; jabber room or listening on the audio stream.<br>
&gt; <br>
&gt; I can see that this has multiple benefits.<br>
&gt; 1. If the number of participants in a certain WG is more, it would<br>
&gt; push the WG chair to request for the slides/agenda available earlier.<br>
&gt; <br>
&gt; 2. If there are consistently more participation from around the world,<br>
&gt; the the WG chair can request for a meetecho recording so people can<br>
&gt; follow the group even if they cannot attend the meeting live. This<br>
&gt; could be useful for people who have clashing schedules as well.<br>
&gt; <br>
&gt; 3. Over a longer period of time, it can help IETF plan and encourage<br>
&gt; remote participation. Currently there is no hard data on number of<br>
&gt; remote participants. There is however a lot of hand waving so this<br>
&gt; will get some useful data into the system.<br>
&gt; <br>
&gt; -- Vinayak<br>
</font></tt>
--=_alternative 0053BC3085257BC5_=--

From vinayakh@gmail.com  Mon Aug 12 09:07:49 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E1321F9D68; Mon, 12 Aug 2013 09:07:49 -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.074,  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 T6ou0LHyqJaF; Mon, 12 Aug 2013 09:07:46 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4701921F9E44; Mon, 12 Aug 2013 08:27:47 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up15so6828933pbc.40 for <multiple recipients>; Mon, 12 Aug 2013 08:27: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=NeAVRJe82SgEJoVo361QjaAVtsgPt0zTmHBBSMB5VPA=; b=f55tgzWBkosb9ZfAF4aqt+AMk6WTiipjr37ww1XgCjsTlTRINdUuBK1B3mYTRX5fwY QP64fxb0WBU5euazWUr0oDoavGBvlfPyF6f5pr/aaQypjL28wfGagPkU6OVvPrlcF7RD XxnY1F9DP8Ewt7GEllUiXfXX7Resam0j6KmAbqFPZ8IqYzy3x7kR0l6MY+znDDlTogdB hcTcvdNA7AHFEmH0EKQ218lElJnUFzwvEU/db6oRA2JrxKGUQypr06ib1b5RigdYPQZG MvHLzAbyo3Se/od5oTfjtpH366IA87KfJhZA/KmqED38VIUh8FXh5ZkswAkIcoWPEvRf a+Zg==
MIME-Version: 1.0
X-Received: by 10.68.239.168 with SMTP id vt8mr14310930pbc.125.1376321255406;  Mon, 12 Aug 2013 08:27:35 -0700 (PDT)
Received: by 10.66.100.226 with HTTP; Mon, 12 Aug 2013 08:27:35 -0700 (PDT)
In-Reply-To: <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com>
Date: Mon, 12 Aug 2013 20:57:35 +0530
Message-ID: <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>
Subject: Re: Data collection for remote participation
From: Vinayak Hegde <vinayakh@gmail.com>
To: Janet P Gunn <jgunn6@csc.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf-bounces@ietf.org, 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: Mon, 12 Aug 2013 16:07:49 -0000

On Mon, Aug 12, 2013 at 8:44 PM, Janet P Gunn <jgunn6@csc.com> wrote:
> As someone who has done it both ways (in person and remotely) I have a
> couple of comments.
>
> Having the slides available early is an advantage to BOTH in-person and
> remote participants.
>
> As a remote participant I "need" the slides available about 30 min before
> the session.
> As a participant (in-person or remote) it is VERY helpful to have the slides
> available much earlier.
> So I do not think "how many remote participants for this session" is a
> useful parameter for "how important is it to get the slides out early"

Agreed. What I meant was it strengthens the case to make slides
available before hand.

> On the other hand, I DO think  that the number of remote participants for a
> particular session IS a useful parameter for "how important is it to have an
> active jabber scribe" and "how important is it to make sure the audio
> streaming is working well."

Agreed. Again,  it strengthens the case to get it done right. This
part has been working well though.

> As a remote participant the list of "working groups I am interested in" is
> different from the list of "working groups I plan to participate in
> remotely".
> There is a SMALL list of working groups I am willing to get up at 2:30 AM
> (my time) to participate in (otherwise I MIGHT look at the slides and read
> the minutes when they come out)
> There is a much LARGER list of working groups I  will participate in
> remotely if they are in (my time) "normal working hours".

Agreed. there are a couple of nuances here. There is a list of groups
I would wake up in the middle of the night so that I can follow the
discussion realtime. The other is a list of groups for which I would
like to have meetecho recording so that I can follow more closely
later.

> There is nothing you can do about this a priori, but if the records show
> that, for instance -  whenever IETF is in North America, WG abc consistently
> has a large number of remote participants from Europe, and WG xyz
> consistently has a large number of remote participants from Asia -  that
> could be factored into the agenda scheduling process.

Yes exactly. Great point. I forgot to mention this. Right now we
cannot see patterns as we do not have enough data. Just moving around
the WG scheduling can help a lot more people participate.

> In-person participants are not asked to list the WG they are interested in.
> That is accomplished by the blue sheets.  I wonder if there is a way to do
> something analogous to the blue sheets for remote participants, whether
> through jabber, email, doodle-poll, wiki, whatever.

Yeah. I had in mind something like doodle. Simple, lightweight works
and gets data.

Also we can start this on a WG-by-WG groups though an IETF wide tool
would be useful.

> I agree with your points 2 and 3.
>
> Janet

From jgunn6@csc.com  Mon Aug 12 09:34:10 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F58621F8617; Mon, 12 Aug 2013 09:34: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.006,  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 g3oFSbF1VDdG; Mon, 12 Aug 2013 09:34:03 -0700 (PDT)
Received: from mail171.messagelabs.com (mail171.messagelabs.com [216.82.253.243]) by ietfa.amsl.com (Postfix) with ESMTP id DD93B21F967F; Mon, 12 Aug 2013 08:49:34 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-14.tower-171.messagelabs.com!1376322572!21143306!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16791 invoked from network); 12 Aug 2013 15:49:32 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-14.tower-171.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 12 Aug 2013 15:49:32 -0000
Received: from amer-gw09.amer.csc.com (cscmail.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r7CFj9TW004632; Mon, 12 Aug 2013 11:45:11 -0400
In-Reply-To: <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>
To: Vinayak Hegde <vinayakh@gmail.com>
MIME-Version: 1.0
Subject: Re: Data collection for remote participation
X-KeepSent: 2FB45330:E1DCDB32-85257BC5:0056B5ED; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com>
Date: Mon, 12 Aug 2013 11:49:30 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/12/2013 11:42:53 AM, Serialize complete at 08/12/2013 11:42:53 AM
Content-Type: multipart/alternative; boundary="=_alternative 0056EE9185257BC5_="
Cc: ietf-bounces@ietf.org, 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: Mon, 12 Aug 2013 16:34:10 -0000

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

> > On the other hand, I DO think  that the number of remote participants 
for a
> > particular session IS a useful parameter for "how important is it to 
have an
> > active jabber scribe" and "how important is it to make sure the audio
> > streaming is working well."
> 
> Agreed. Again,  it strengthens the case to get it done right. This
> part has been working well though.

Not necessarily.  There was one WG where I had to send an email to the WG 
mailing list asking for someone to provide slide numbers on jabber.

Janet
--=_alternative 0056EE9185257BC5_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
</font><tt><font size=2>&gt; &gt; On the other hand, I DO think &nbsp;that
the number of remote participants for a<br>
&gt; &gt; particular session IS a useful parameter for &quot;how important
is it to have an<br>
&gt; &gt; active jabber scribe&quot; and &quot;how important is it to make
sure the audio<br>
&gt; &gt; streaming is working well.&quot;<br>
&gt; <br>
&gt; Agreed. Again, &nbsp;it strengthens the case to get it done right.
This<br>
&gt; part has been working well though.</font></tt>
<br><tt><font size=2><br>
Not necessarily. &nbsp;There was one WG where I had to send an email to
the WG mailing list asking for someone to provide slide numbers on jabber.</font></tt>
<br>
<br><tt><font size=2>Janet</font></tt>
--=_alternative 0056EE9185257BC5_=--

From vinayakh@gmail.com  Mon Aug 12 09:37:37 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 173AE21F9BB6 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 09:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.068,  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 cBBBXzSukcf0 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 09:37:35 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 76A6D21E814F for <ietf@ietf.org>; Mon, 12 Aug 2013 08:56:30 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id fb10so7616967pad.23 for <ietf@ietf.org>; Mon, 12 Aug 2013 08:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zpQ7NKjE5uuFoDmZ1FGQ8KRApuat9bUo2FF3mUsln3I=; b=O7R2QAmoITYj0wi44jRhTD7N9bicyMwe7oWQhs7pfZvLurqBePgu+gGrAXiGODcmQD 2cQMvIguTkSCpAuw0wefi3rF7dvrBVr7jrOHuEoC1vXkIbnNkkDnV+XKnpyce/VsE3Ie wVWXBm0h5Sr37SgNB2VJrc5nGlHOBEc4GVh1LAkrhUU7sHRCgKRH13dmjROt4c/at8h+ SRrzU4+VwEhESwxfaUtmCRKxk8+elTE1F+8KmdEJeW11yRQFGzQziCDcPFb5F9rnyJOe hYeB5dwDtANFizXyyCap9CJhmF+4wUAkGUSXNb1AxYA6unj2h2RYSHSrULXO5WZBGJsd vpBw==
MIME-Version: 1.0
X-Received: by 10.68.234.33 with SMTP id ub1mr24947138pbc.98.1376322990195; Mon, 12 Aug 2013 08:56:30 -0700 (PDT)
Received: by 10.66.100.226 with HTTP; Mon, 12 Aug 2013 08:56:30 -0700 (PDT)
In-Reply-To: <CAOmxzdxTftsbyCghsGyfBrhuiKrti3mwRfNNzFCiUoTddpeFyQ@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <CAOmxzdxTftsbyCghsGyfBrhuiKrti3mwRfNNzFCiUoTddpeFyQ@mail.gmail.com>
Date: Mon, 12 Aug 2013 21:26:30 +0530
Message-ID: <CAKe6YvMFcceT_bHsvfK2eNvSXBGzw5oSuV2r7RUJLRaHBLDtCw@mail.gmail.com>
Subject: Re: Data collection for remote participation
From: Vinayak Hegde <vinayakh@gmail.com>
To: Alejandro Acosta <alejandroacostaalamo@gmail.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: Mon, 12 Aug 2013 16:37:37 -0000

On Mon, Aug 12, 2013 at 8:35 PM, Alejandro Acosta
<alejandroacostaalamo@gmail.com> wrote:
> Hi Vinayak,
>   First, well done, I fully agree with your email. I have two
> questions for you/the group:
>
> 1)  I wonder if in your proposal you are considering some sort of
> charge for remote participation. IMHO I do not think we are yet
> prepare to charge.

This was a suggestion but I don't think it will work well. OTOH an
argument can be made that money gathered from charging remote
participants can be used to fund better tools for remote
participation.

> 2) When you mention that filling the responses (pre-IETF) is
> voluntary, so, I guess it's not mandatory, am I right?. We should also
> define what pre-IETF is..., it sounds obvious but it can be read as
> the pre-WG session.

I am proposing it not be mandatory but I am sure many people will be
happy to help. It should be unobtrusive and be the equivalent of
signing the blue sheets.

>   I would add to your proposal some kind of activities from local ISOC chapters.

Did not understand. Can you elaborate ?

-- Vinayak

From hadriel.kaplan@oracle.com  Mon Aug 12 09:56:30 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A353821E80FC for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 09:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.521
X-Spam-Level: 
X-Spam-Status: No, score=-4.521 tagged_above=-999 required=5 tests=[AWL=-1.918, BAYES_50=0.001, MIME_QP_LONG_LINE=1.396, 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 oOJxfMtpQVUK for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 09:56:12 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 1CFA121F9C37 for <ietf@ietf.org>; Mon, 12 Aug 2013 09:35:35 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7CGZYZ7009648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Aug 2013 16:35:34 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7CGZX61012999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Aug 2013 16:35:33 GMT
Received: from abhmt112.oracle.com (abhmt112.oracle.com [141.146.116.64]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7CGZWgR003563; Mon, 12 Aug 2013 16:35:32 GMT
Received: from [10.244.206.128] (/174.236.78.252) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Aug 2013 09:35:31 -0700
To: John C Klensin <john-ietf@jck.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com> <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
X-Universally-Unique-Identifier: 68d24994-1fd7-4099-8814-a6fdb663f2db
In-Reply-To: <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=us-ascii
X-Apple-Mail-Signature: 
Message-Id: <A9F21378-1F90-46AC-9B62-6A725E295FBA@oracle.com>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (10B329)
X-Apple-Windows-Friendly: 1
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
X-Apple-Mail-Remote-Attachments: YES
X-Apple-Base-Url: x-msg://4516/
X-Uniform-Type-Identifier: com.apple.mail-draft
Subject: Re: procedural question with remote participation
Date: Mon, 12 Aug 2013 12:35:26 -0400
X-Apple-Mail-Plain-Text-Draft: yes
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 16:56:31 -0000

[personal disclaimer: I have participated remotely, a few times, and I agree=
 that it's not the same as being there, and I agree that it could be improve=
d.  But I think we need to balance the needs of remote participants, vs. the=
 goals of physical meetings: to get work done that can only get done with di=
rect human interaction, with real-time interactive discussion, and hallway c=
o-mingling, etc.  In my opinion being remote will *never* be the same as bei=
ng there, and that's why we have physical meetings to begin with, instead of=
 just virtual ones - ultimately I want you to come to the meeting *physicall=
y*... but I want to do as much as possible and *practical* to accommodate re=
mote participants, because I know not everyone has the luxury to come, and I=
 want their input regardless.]


I think one challenge with this discussion, at least for me, is that it feel=
s like the solutions being proposed are completely out of whack with the sev=
erity and nature of the problems at hand, and the people they apply to.  Add=
ing more rules and processes is about the surest way I know to annoy enginee=
rs, let alone volunteer ones.  And if your right hand is sore, you don't cut=
 it off and replace with a mechanical one, or go build a billion-dollar robo=
t to be controlled by brain-waves.

People on this list are saying things like "we don't know who's at the mic",=
 and "we can't see the slides well enough", and "presenters are hard to foll=
ow".  ISTM there are practical and low-tech means of fixing those problems.

Here're some ideas of possible solutions - but most of these boil down to ei=
ther "have WG Chairs do their job", or "get over it":

Problem-1: we don't know who's at the mic, because people forget to say thei=
r names.
Solution: (a) train WG Chairs to remind people at mic, and interrupt them if=
 they haven't said their names, (b) have jabber scribes sit next to mics, to=
 do the same as WG chairs, (c) if chairs and scribes forget, send a chat mes=
sage in jabber to remind them.  Is it annoying?  Sure.  Will it sometimes fa=
il to work?  Sure.  But every other solution will also be annoying and not a=
lways work, and this solution is very low-tech and simple.  This is what hap=
pens in RAI area WG meetings, and appears to work afaict.  If it doesn't wor=
k, then we go to a Plan-B in the future.

Problem-2: we can't see the slides well enough, in video.  Meetecho is ok, b=
ut they don't cover all meetings.
Solution: we pay Meetecho to cover all WG meetings.  Last time I checked, we=
 weren't paying them anything; but if we really want that type of technology=
 in all meetings, then it's only fair to pay them. (frankly we should be pay=
ing them now already)  We also need to remind people to use reasonable font s=
ize.  10pt is bad mojo even in the physical room.  That type of thing is wha=
t a WG chair should be telling people, though - we don't need slide police.

Problem-3: presenters are hard to hear/follow/understand.
Solution: that's life.  We're a volunteer organization, not trained professi=
onal thespians.  We have drafts written in plain ascii available in advance,=
 and audio, and video, and jabber, and (hopefully) Meetecho-type service, an=
d that's about as good as it can reasonably be.

Problem-4: we want slides 7 days in advance to translate to our native langu=
age
Solution: You're doing it wrong - or rather, the presenters are doing it wro=
ng.  The slides aren't a replacement for drafts, or a copy-paste of draft te=
xt.  WG Chairs know this, and should remind presenters of it.  As an aside, i=
f you really need a week to translate them, it's highly unlikely you'll be a=
ble to truly *participate* interactively during the meeting - and you don't n=
eed to be real-time if all you're going to do is listen/watch - we record th=
e whole thing for your later viewing pleasure.

Problem-5: we want slides 48 hours in advance to translate to our native lan=
guage, download it, etc.
Solution: sounds reasonable.  Have WG chairs use 48 hours as their guideline=
, but not as a strictly enforced rule a la I-D submission deadlines.  WG cha=
irs can figure out when exceptions need to be made, how to deal with it, etc=
.  We don't need this in an RFC.

Problem-6: if you change slides, I don't know which slides you changed
Solution: it happens, and that's life.  You've got to follow the speaker's w=
ords, not a published script.  The point of these meetings is for real-time d=
iscussion on relevant matters that can only be handled live.

Problem-7:=20

-hadriel


On Aug 8, 2013, at 10:43 AM, John C Klensin <john-ietf@jck.com> wrote:

> --On Tuesday, August 06, 2013 11:06 -0400 Andrew Feren
> <andrewf@plixer.com> wrote:
>=20
>> ...
>> I think this sort of misses the point.  At least for me as a
>> remote participant.
>>=20
>> I'm not interested in arguing about whether slides are good or
>> bad. I am interested in following (and being involved) in the
>> WG meeting.  When there are slides I want to be able to see
>> them clearly from my remote location.  Having them integrated
>> with Meetecho works fine.  Having slides and other materials
>> ...
>=20
> Let me say part of this differently, with the understanding I
> may be more fussy (or older and less tolerant) than Andrew is...
>=20
> If the IETF is going to claim that remote participation (rather
> than remote passive listening/ observation with mailing list
> follow up) is feasible, then it has to work.  If, as a remote
> participant, I could be guaranteed zero-delay transmission and
> receipt of audio and visual materials (including high enough
> resolution of slides to be able to read all of them) and that
> speakers (in front of the room and at the mic) would identify
> themselves clearly and then speak clearly and at reasonable
> speed, enunciating every word, I wouldn't care whether slides
> were posted in advance or not. =20
>=20
> Realistically, that doesn't happen.  In some cases (e.g.,
> lag-free audio) it is beyond the state of the art or a serious
> technical challenge (e.g., video that is high enough resolution
> that I can slides that have been prepared with 12 point type).
> In others, we haven't done nearly enough speaker training or it
> hasn't been effective (e.g., people mumbling, speaking very
> quickly, swallowing words, or wandering out of microphone or
> camera range).   And sometimes there are just problems (e.g.,
> intermittent audio or video, servers crashing, noisy audio
> cables or other audio or video problems in the room).  =20
>=20
> In those cases, as a remote participant, I need all the help I
> can get.  I'd rather than no one ever use a slide that has
> information on it in a type size that would be smaller than 20
> pt on A4 paper.  But 14 pt and even 12 pt happen, especially if
> the slides were prepared with a tool that quietly shrinks things
> to fit in the image area.  If I'm in the room and such a slide
> is projected, I can walk to the front to see if if I'm not
> already in front and can't deduce what I need from context.  If
> I'm remote and have such a slide in advance, I can zoom in on it
> or otherwise get to the information I need (assuming high enough
> resolution).  If I'm remote and reading the slide off video,
> especially low resolution video, is hopeless. =20
>=20
> More generally, being able to see an outline of what the speaker
> is talking about is of huge help when the audio isn't completely
> clear.  Others have mentioned this, but, if I couldn't read and
> understand slides in English easily in real time, it would be of
> even more help if I had the slides far enough in advance to be
> able to read through them at my own pace before the WG session
> and even make notes abut what they are about in my most-familiar
> language ... and that is true whether I'm remote or in the room.
>=20
> And, yes, for my purposes, 48 hours ahead of the WG meeting
> would be plenty.  But I can read and understand English in real
> time.  If the IETF cares about diversity as well as about remote
> participation and someone whose English is worse than mine is
> trying to follow several WGs, 48 hours may not be enough without
> requiring a lot of extra effort.
>=20
> That is not, however, the key reason I said "a week".  The more
> important part of the reason is that a one-week cutoff gives the
> WG Chair (or IETF or IAB Chairs for the plenaries) the time to
> make adjustments.  If there is a nominal one week deadline, then
> the WG Chair has lots of warning when things don't show up.  She
> can respond by getting on someone's case, by accepting a firm
> promise and a closer deadline, by finding someone else to take
> charge of the presentation or discussion-leading, or by
> rearranging the agenda.  And exceptions can be explained to the
> WG on the mailing list.  With a 48 hour deadline, reasonable
> ways to compensate are much less likely, the Chair is likely to
> have only the choice that was presented this time (accepting
> late slides or hurting the WG's ability to consider important
> issues) and one needs to start talking about sanctions for bad
> behavior.   I would never suggest a firm "one week or no agenda
> time" rule.  I am suggesting something much more like a "one
> week or the WG Chair needs to make an exception, explain it to
> the WG, and be accountable if the late slides cause too much of
> a problem".  There is some similarity between this and the
> current I-D cutoff rule and its provision for AD-authorized
> exceptions.  That similarity is intentional.
>=20
>=20
> --On Monday, August 05, 2013 13:36 -0500 James Polk
> <jmpolk@cisco.com> wrote:
>=20
>> At 12:38 PM 8/5/2013, John C Klensin wrote:
>>> Hi.
>>>=20
>>> I seem to have missed a lot of traffic since getting a few
>>> responses yesterday.  I think the reasons why slides should be
>>> available well in advance of the meeting have been covered
>>> well by others.  And, as others have suggested, I'm willing
>>> to see updates to those slides if things change in the hours
>>> leading up to the meeting, but strongly prefer that those
>>> updates come as new alides with update-type "numbers" or other
>>> identification rather than new decks.  In other words, if a
>>> deck is posted in advance with four slides numbered 1, 2, 3,
>>> and 4, and additional information is needed for 3, I'd prefer
>>> to see the updated deck consist of slides 1, 2, 3, 3a, 3b, 4
>>> or 1, 2, 3a, 3b, 3c, 4, rather than 1, 2, 3, 4, 5, 6.
>>=20
>> How exactly do you do this in pptx? Numbering slides is a
>> linear operation AFAICT, and it's binary (it's either on or
>> off). Please educate me if I'm wrong; lord knows I don't know
>> don't know how to do everything flag/setting in powerpoint...
>=20
> Hmm.  First, I missed the IESG Statement requiring the people
> use pptx or any other particular piece of
> presentation-preparation software, much less the IETF consensus
> for that statement.  If the tools you choose to use don't meet
> the needs of the IETF, that doesn't seem to me to be an IETF
> problem.
>=20
> Second and more important, while having slide preparation
> software number pages, I'm not aware of anything that prevents
> you from typing in numbers, especially with something that is as
> inherently page (slide)-oriented as presentation-preparation
> software.  Yes, it is an annoyance, but having the need to
> update slides within a short interval before the meeting/
> presentation/ discussion is an annoyance to participants who
> depend on the ability to access those slides and who might want
> to prepare reference or discussion notes in advance.
>=20
>> And, in my 8 years as TSVWG chair, I've rarely had completely
>> new individual slides sprinkled throughout an existing deck.
>> Rather, I've received updated slides - each with part of their
>> content altered. Does this fall into your desire for a "3a",
>> or is that just "3" (because 3a means an entirely new slide
>> from scratch)?
>=20
> 3a. =20
>=20
>> BTW - I'm very much *not* in favor of stipulating to my WG
>> that slides must be turned in 7 days in advance of a TSVWG
>> meeting. I personally think no more than a 48 hour advanced
>> window should ever be considered.
>=20
> See above.
>=20
>   best,
>   john


From jari.arkko@piuha.net  Mon Aug 12 10:20:00 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D255821F9D70; Mon, 12 Aug 2013 10:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.207
X-Spam-Level: 
X-Spam-Status: No, score=-102.207 tagged_above=-999 required=5 tests=[AWL=-0.208, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GVJ9toRXm5Xb; Mon, 12 Aug 2013 10:19:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id ACFB821F9A0C; Mon, 12 Aug 2013 10:11:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 180C72CC48; Mon, 12 Aug 2013 20:11:54 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lSibXQxwopJw; Mon, 12 Aug 2013 20:11:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id F2E522F63C; Mon, 12 Aug 2013 20:11:51 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-framework-06
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712984AD61D@MX15A.corp.emc.com>
Date: Mon, 12 Aug 2013 20:11:51 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <617E3D65-CFF1-4006-BAAA-336728231284@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE712984AD61D@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "trill@ietf.org" <trill@ietf.org>, "igor@yahoo-inc.com" <igor@yahoo-inc.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, 12 Aug 2013 17:20:01 -0000

David: Thank you. I have placed a no-objection ballot for this draft.

Jari

On Jul 29, 2013, at 2:20 PM, "Black, David" <david.black@emc.com> wrote:

> The -06 version of this draft resolves all of the concerns raised by =
the Gen-ART
> review of the -05 version - the -06 version is ready for publication =
as an
> Informational RFC.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Black, David
>> Sent: Wednesday, July 17, 2013 7:54 PM
>> To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; =
igor@yahoo-
>> inc.com; General Area Review Team
>> Cc: trill@ietf.org; ietf@ietf.org; Black, David; Ted Lemon
>> Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
>>=20
>> Document: draft-ietf-trill-directory-framework-05
>> Reviewer: David L. Black
>> Review Date: July 17, 2013
>> IETF LC End Date: July 18, 2013
>>=20
>> Summary:
>> This draft is on the right track but has open issues, described in =
the review.
>>=20
>> This draft describes a framework for using directory servers to =
provide
>> address mappings (address -> destination RBridge) to TRILL Rbridges =
as an
>> alternative to data plane learning and use of the TRILL ESADI =
protocol.
>>=20
>> The draft's generally well written and clear.  I found a couple of =
minor
>> issues.
>>=20
>> Major issues: None.
>>=20
>> Minor issues:
>>=20
>> [1] The last bullet in Section 3.1 says:
>>=20
>>       - In an environment where VMs migrate, there is a higher chance
>>         of cached information becoming invalid, causing traffic to be
>>         black-holed by the ingress RBridge, that is, persistently =
sent
>>         to the wrong egress RBridge. If VMs do not flood gratuitous
>>         ARP/ND or VDP [802.1Qbg] messages upon arriving at new
>>         locations, the ingress nodes might not have MAC entries for =
the
>>         MAC of the newly arrived VMs, causing unknown address =
flooding.
>>=20
>> This is incorrect in multiple ways and should just be removed:
>>=20
>> - Persistent black-holing is rare in practice because all common
>> 	VM migration implementations issue the gratuitous messages.
>> - VMs don't send the gratuitous messages, hypervisors do.
>> - VDP is not flooded.  The receiver's always a bridge.
>> - At least one common VM migration implementation actually uses a =
gratuitous
>> 	RARP, not ARP.
>> - Flooding is done by the bridges and Rbridges, not the VMs.
>>=20
>> [2] There are some unfortunate notation problems in Section 5.1 that =
carry
>> into the following sections, based on the logical data structure:
>>=20
>>   [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
>>   interested RBridges}]
>>=20
>> - The first open curly brace ('{') is unmatched.
>> - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
>> 	none of which appear in that structure.
>>=20
>> Nits/editorial comments:
>>=20
>> Section 1 - item 1 in the numbered list does not explain why it makes
>> a directory approach attractive.  This should be added, as it is
>> present for the other three items .
>>=20
>> Section 2 - Say that IS-IS is a routing protocol.
>> The definition of Station should say that the node or virtual node
>> is on a network.  Also, please define or explain "virtual node".
>>=20
>> Section 3.2 - Add the number of entries to be learned to scenario #1
>> in order to parallel the scenario # 2 discussion.
>>=20
>> Section 4 - remove "(distributed model)" from first paragraph,
>> as it's not explained.
>>=20
>> Section 5.3, top of p.13:
>>=20
>>   therefore, there needs to be some mechanism by which RBridges that
>>   have pulled information that has not expired can be informed when
>>   that information changes or the like.
>>=20
>> "or the like" is vague.  I suggest "or becomes invalid for other
>> reasons".
>>=20
>> idnits 2.12.17 didn't find any nits that need attention.
>>=20
>> 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        Mobile: +1 (978) 394-7754
>> ----------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From tnadeau@lucidvision.com  Mon Aug 12 10:27:21 2013
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2850F21F84D9 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 10:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level: 
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x62hRE3L+LaG for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 10:27:13 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id B5D1521F944C for <ietf@ietf.org>; Mon, 12 Aug 2013 10:24:38 -0700 (PDT)
Received: from wgao-sslvpn-nc.jnpr.net (westford-nat.juniper.net [66.129.232.2]) by lucidvision.com (Postfix) with ESMTP id 6C859252E79F for <ietf@ietf.org>; Mon, 12 Aug 2013 13:24:37 -0400 (EDT)
From: Thomas Nadeau <tnadeau@lucidvision.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: NOMS 2014 Call for Papers
Message-Id: <C5CED97E-F5B4-445B-964C-DED30E662D3E@lucidvision.com>
Date: Mon, 12 Aug 2013 13:24:34 -0400
To: "discussion ietf@ietf.org" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:27:21 -0000

http://noms2014.ieee-noms.org/content/call-experience-session-papers

http://www.ieee-noms.org/

NOMS 2014 will be next year's IEEE flagship conference in the area of =
management of networked systems and services. The symposium will include =
an Experience Session program. Experience Sessions complement the =
Technical Sessions with contributions that emphasize practical =
experiences and lessons learnt in applying, implementing, and deploying =
management technology. They will focus on aspects such as real-world =
deployment scenarios, experiences with the management of new services =
and technology, industrial applications of management technology, =
implementation experiences, and organizational considerations. =
Experience sessions are particularly aimed at decision makers and =
experts from industry.
New this year and for the first time at NOMS, the best Experience Paper =
will be recognized with an award.
=20
Topics of interest=20
NOMS 2014's theme is "Management in a Software Defined World". NOMS 2014 =
will place particular emphasis on Software Defined Networking and =
related technologies; submissions in those areas are particularly =
encouraged. Specific topics include but are not limited to the ones =
listed below. Please refer also to the general Call for Papers.
	=95 Management case studies and best practices
	=95 Issues and experiences with practical deployments
	=95 Software Defined Networks and enabling technologies
	=95 Open source SDN frameworks, Open Daylight
	=95 Experiences with OpenFlow deployments
	=95 Orchestration and SDN controllers
	=95 Network Function Virtualization implementations
	=95 Data center automation
	=95 Management of cloud
	=95 Cloud service assurance
	=95 Big Data analytics in management
	=95 Management of virtualized environments
	=95 OSS/BSS development
	=95 Virtualization of operation centers and help desks
	=95 Organizational aspects of IT service management
	=95 IT governance
	=95 Service engineering and operational challenges
	=95 Management of emerging networks and services
	=95 Green management and managing energy efficiency
	=95 Smart buildings, industrial automation and management
	=95 Experiences with autonomic networking and self-management
	=95 Application of machine learning and data mining to =
management
	=95 Advances in standardization
	=95 Management information models
	=95 Event correlation, diagnostics, fault, performance =
management
	=95 Billing and accounting models and service level management
	=95 Business alignment of IT service management
	=95 Experiences with Call Home frameworks
	=95 Managed service provider issues
	=95 Service delivery and service assurance
	=95 Experiences with process engineering and frameworks (ITIL, =
eTOM)
	=95 Other topics in network and service operations and =
management



From hadriel.kaplan@oracle.com  Mon Aug 12 10:55:38 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA7A421F9D07 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 10:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.502
X-Spam-Level: 
X-Spam-Status: No, score=-6.502 tagged_above=-999 required=5 tests=[AWL=0.097,  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 BklAphs+rRDZ for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 10:55:31 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id E3E7021F9D2B for <ietf@ietf.org>; Mon, 12 Aug 2013 10:55:26 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7CHtMZN019573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Aug 2013 17:55:26 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7CHtL41028319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Aug 2013 17:55:21 GMT
Received: from abhmt115.oracle.com (abhmt115.oracle.com [141.146.116.67]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7CHtK8x001823; Mon, 12 Aug 2013 17:55:20 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 12 Aug 2013 10:55:20 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: procedural question with remote participation
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <A9F21378-1F90-46AC-9B62-6A725E295FBA@oracle.com>
Date: Mon, 12 Aug 2013 13:55:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C821E5D6-C05A-4994-835F-D5986449A1EA@oracle.com>
References: <CE218890.17010%york@isoc.org> <8FA47708-C3A1-4E59-A65B-6ABACE46DB92@edvina.net> <ECF4A733EFD13FA1753C063B@[192.168.1.128]> <32634.1375615620@sandelman.ca> <057CBC2970E7A4BE8F50AA90@[192.168.1.128]> <8D23D4052ABE7A4490E77B1A012B63077524332A@mbx-01.win.nominum.com> <5200F53A.6020408@network-heretics.com> <520110F0.5030100@plixer.com> <85FC528D5A7B2D875CCB0CA0@JcK-HP8200.jck.com> <A9F21378-1F90-46AC-9B62-6A725E295FBA@oracle.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 17:55:38 -0000

Ugh.  Ignore that email below - I had sent it a few days ago but somehow =
it got stuck in the outbox and never got sent, and the discussion is =
past that point now so it doesn't matter.

-hadriel


On Aug 12, 2013, at 12:35 PM, Hadriel Kaplan <hadriel.kaplan@oracle.com> =
wrote:

>=20
> [personal disclaimer: I have participated remotely, a few times, and I =
agree that it's not the same as being there, and I agree that it could =
be improved.  But I think we need to balance the needs of remote =
participants, vs. the goals of physical meetings: to get work done that =
can only get done with direct human interaction, with real-time =
interactive discussion, and hallway co-mingling, etc.  In my opinion =
being remote will *never* be the same as being there, and that's why we =
have physical meetings to begin with, instead of just virtual ones - =
ultimately I want you to come to the meeting *physically*... but I want =
to do as much as possible and *practical* to accommodate remote =
participants, because I know not everyone has the luxury to come, and I =
want their input regardless.]
>=20
>=20
> I think one challenge with this discussion, at least for me, is that =
it feels like the solutions being proposed are completely out of whack =
with the severity and nature of the problems at hand, and the people =
they apply to.  Adding more rules and processes is about the surest way =
I know to annoy engineers, let alone volunteer ones.  And if your right =
hand is sore, you don't cut it off and replace with a mechanical one, or =
go build a billion-dollar robot to be controlled by brain-waves.
>=20
> People on this list are saying things like "we don't know who's at the =
mic", and "we can't see the slides well enough", and "presenters are =
hard to follow".  ISTM there are practical and low-tech means of fixing =
those problems.
>=20
> Here're some ideas of possible solutions - but most of these boil down =
to either "have WG Chairs do their job", or "get over it":
>=20
> Problem-1: we don't know who's at the mic, because people forget to =
say their names.
> Solution: (a) train WG Chairs to remind people at mic, and interrupt =
them if they haven't said their names, (b) have jabber scribes sit next =
to mics, to do the same as WG chairs, (c) if chairs and scribes forget, =
send a chat message in jabber to remind them.  Is it annoying?  Sure.  =
Will it sometimes fail to work?  Sure.  But every other solution will =
also be annoying and not always work, and this solution is very low-tech =
and simple.  This is what happens in RAI area WG meetings, and appears =
to work afaict.  If it doesn't work, then we go to a Plan-B in the =
future.
>=20
> Problem-2: we can't see the slides well enough, in video.  Meetecho is =
ok, but they don't cover all meetings.
> Solution: we pay Meetecho to cover all WG meetings.  Last time I =
checked, we weren't paying them anything; but if we really want that =
type of technology in all meetings, then it's only fair to pay them. =
(frankly we should be paying them now already)  We also need to remind =
people to use reasonable font size.  10pt is bad mojo even in the =
physical room.  That type of thing is what a WG chair should be telling =
people, though - we don't need slide police.
>=20
> Problem-3: presenters are hard to hear/follow/understand.
> Solution: that's life.  We're a volunteer organization, not trained =
professional thespians.  We have drafts written in plain ascii available =
in advance, and audio, and video, and jabber, and (hopefully) =
Meetecho-type service, and that's about as good as it can reasonably be.
>=20
> Problem-4: we want slides 7 days in advance to translate to our native =
language
> Solution: You're doing it wrong - or rather, the presenters are doing =
it wrong.  The slides aren't a replacement for drafts, or a copy-paste =
of draft text.  WG Chairs know this, and should remind presenters of it. =
 As an aside, if you really need a week to translate them, it's highly =
unlikely you'll be able to truly *participate* interactively during the =
meeting - and you don't need to be real-time if all you're going to do =
is listen/watch - we record the whole thing for your later viewing =
pleasure.
>=20
> Problem-5: we want slides 48 hours in advance to translate to our =
native language, download it, etc.
> Solution: sounds reasonable.  Have WG chairs use 48 hours as their =
guideline, but not as a strictly enforced rule a la I-D submission =
deadlines.  WG chairs can figure out when exceptions need to be made, =
how to deal with it, etc.  We don't need this in an RFC.
>=20
> Problem-6: if you change slides, I don't know which slides you changed
> Solution: it happens, and that's life.  You've got to follow the =
speaker's words, not a published script.  The point of these meetings is =
for real-time discussion on relevant matters that can only be handled =
live.
>=20
> Problem-7:=20
>=20
> -hadriel
>=20
>=20
> On Aug 8, 2013, at 10:43 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
>> --On Tuesday, August 06, 2013 11:06 -0400 Andrew Feren
>> <andrewf@plixer.com> wrote:
>>=20
>>> ...
>>> I think this sort of misses the point.  At least for me as a
>>> remote participant.
>>>=20
>>> I'm not interested in arguing about whether slides are good or
>>> bad. I am interested in following (and being involved) in the
>>> WG meeting.  When there are slides I want to be able to see
>>> them clearly from my remote location.  Having them integrated
>>> with Meetecho works fine.  Having slides and other materials
>>> ...
>>=20
>> Let me say part of this differently, with the understanding I
>> may be more fussy (or older and less tolerant) than Andrew is...
>>=20
>> If the IETF is going to claim that remote participation (rather
>> than remote passive listening/ observation with mailing list
>> follow up) is feasible, then it has to work.  If, as a remote
>> participant, I could be guaranteed zero-delay transmission and
>> receipt of audio and visual materials (including high enough
>> resolution of slides to be able to read all of them) and that
>> speakers (in front of the room and at the mic) would identify
>> themselves clearly and then speak clearly and at reasonable
>> speed, enunciating every word, I wouldn't care whether slides
>> were posted in advance or not. =20
>>=20
>> Realistically, that doesn't happen.  In some cases (e.g.,
>> lag-free audio) it is beyond the state of the art or a serious
>> technical challenge (e.g., video that is high enough resolution
>> that I can slides that have been prepared with 12 point type).
>> In others, we haven't done nearly enough speaker training or it
>> hasn't been effective (e.g., people mumbling, speaking very
>> quickly, swallowing words, or wandering out of microphone or
>> camera range).   And sometimes there are just problems (e.g.,
>> intermittent audio or video, servers crashing, noisy audio
>> cables or other audio or video problems in the room).  =20
>>=20
>> In those cases, as a remote participant, I need all the help I
>> can get.  I'd rather than no one ever use a slide that has
>> information on it in a type size that would be smaller than 20
>> pt on A4 paper.  But 14 pt and even 12 pt happen, especially if
>> the slides were prepared with a tool that quietly shrinks things
>> to fit in the image area.  If I'm in the room and such a slide
>> is projected, I can walk to the front to see if if I'm not
>> already in front and can't deduce what I need from context.  If
>> I'm remote and have such a slide in advance, I can zoom in on it
>> or otherwise get to the information I need (assuming high enough
>> resolution).  If I'm remote and reading the slide off video,
>> especially low resolution video, is hopeless. =20
>>=20
>> More generally, being able to see an outline of what the speaker
>> is talking about is of huge help when the audio isn't completely
>> clear.  Others have mentioned this, but, if I couldn't read and
>> understand slides in English easily in real time, it would be of
>> even more help if I had the slides far enough in advance to be
>> able to read through them at my own pace before the WG session
>> and even make notes abut what they are about in my most-familiar
>> language ... and that is true whether I'm remote or in the room.
>>=20
>> And, yes, for my purposes, 48 hours ahead of the WG meeting
>> would be plenty.  But I can read and understand English in real
>> time.  If the IETF cares about diversity as well as about remote
>> participation and someone whose English is worse than mine is
>> trying to follow several WGs, 48 hours may not be enough without
>> requiring a lot of extra effort.
>>=20
>> That is not, however, the key reason I said "a week".  The more
>> important part of the reason is that a one-week cutoff gives the
>> WG Chair (or IETF or IAB Chairs for the plenaries) the time to
>> make adjustments.  If there is a nominal one week deadline, then
>> the WG Chair has lots of warning when things don't show up.  She
>> can respond by getting on someone's case, by accepting a firm
>> promise and a closer deadline, by finding someone else to take
>> charge of the presentation or discussion-leading, or by
>> rearranging the agenda.  And exceptions can be explained to the
>> WG on the mailing list.  With a 48 hour deadline, reasonable
>> ways to compensate are much less likely, the Chair is likely to
>> have only the choice that was presented this time (accepting
>> late slides or hurting the WG's ability to consider important
>> issues) and one needs to start talking about sanctions for bad
>> behavior.   I would never suggest a firm "one week or no agenda
>> time" rule.  I am suggesting something much more like a "one
>> week or the WG Chair needs to make an exception, explain it to
>> the WG, and be accountable if the late slides cause too much of
>> a problem".  There is some similarity between this and the
>> current I-D cutoff rule and its provision for AD-authorized
>> exceptions.  That similarity is intentional.
>>=20
>>=20
>> --On Monday, August 05, 2013 13:36 -0500 James Polk
>> <jmpolk@cisco.com> wrote:
>>=20
>>> At 12:38 PM 8/5/2013, John C Klensin wrote:
>>>> Hi.
>>>>=20
>>>> I seem to have missed a lot of traffic since getting a few
>>>> responses yesterday.  I think the reasons why slides should be
>>>> available well in advance of the meeting have been covered
>>>> well by others.  And, as others have suggested, I'm willing
>>>> to see updates to those slides if things change in the hours
>>>> leading up to the meeting, but strongly prefer that those
>>>> updates come as new alides with update-type "numbers" or other
>>>> identification rather than new decks.  In other words, if a
>>>> deck is posted in advance with four slides numbered 1, 2, 3,
>>>> and 4, and additional information is needed for 3, I'd prefer
>>>> to see the updated deck consist of slides 1, 2, 3, 3a, 3b, 4
>>>> or 1, 2, 3a, 3b, 3c, 4, rather than 1, 2, 3, 4, 5, 6.
>>>=20
>>> How exactly do you do this in pptx? Numbering slides is a
>>> linear operation AFAICT, and it's binary (it's either on or
>>> off). Please educate me if I'm wrong; lord knows I don't know
>>> don't know how to do everything flag/setting in powerpoint...
>>=20
>> Hmm.  First, I missed the IESG Statement requiring the people
>> use pptx or any other particular piece of
>> presentation-preparation software, much less the IETF consensus
>> for that statement.  If the tools you choose to use don't meet
>> the needs of the IETF, that doesn't seem to me to be an IETF
>> problem.
>>=20
>> Second and more important, while having slide preparation
>> software number pages, I'm not aware of anything that prevents
>> you from typing in numbers, especially with something that is as
>> inherently page (slide)-oriented as presentation-preparation
>> software.  Yes, it is an annoyance, but having the need to
>> update slides within a short interval before the meeting/
>> presentation/ discussion is an annoyance to participants who
>> depend on the ability to access those slides and who might want
>> to prepare reference or discussion notes in advance.
>>=20
>>> And, in my 8 years as TSVWG chair, I've rarely had completely
>>> new individual slides sprinkled throughout an existing deck.
>>> Rather, I've received updated slides - each with part of their
>>> content altered. Does this fall into your desire for a "3a",
>>> or is that just "3" (because 3a means an entirely new slide
>>> from scratch)?
>>=20
>> 3a. =20
>>=20
>>> BTW - I'm very much *not* in favor of stipulating to my WG
>>> that slides must be turned in 7 days in advance of a TSVWG
>>> meeting. I personally think no more than a 48 hour advanced
>>> window should ever be considered.
>>=20
>> See above.
>>=20
>>  best,
>>  john
>=20


From john@jlc.net  Mon Aug 12 13:06:27 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3510521F9ED2 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 13:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level: 
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3yXilvWkJKS for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 13:06:22 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 17D2F21F9EC4 for <ietf@ietf.org>; Mon, 12 Aug 2013 13:06:22 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 05D4B33C20; Mon, 12 Aug 2013 16:06:22 -0400 (EDT)
Date: Mon, 12 Aug 2013 16:06:21 -0400
From: John Leslie <john@jlc.net>
To: Janet P Gunn <jgunn6@csc.com>
Subject: Re: Data collection for remote participation
Message-ID: <20130812200621.GB68553@verdi>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com>
User-Agent: Mutt/1.4.1i
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: Mon, 12 Aug 2013 20:06:27 -0000

Janet P Gunn <jgunn6@csc.com> wrote:
>  
>> Again, it strengthens the case to get it done right. This part has been
>> working well though.
> 
> Not necessarily.  There was one WG where I had to send an email to the WG 
> mailing list asking for someone to provide slide numbers on jabber.

   ... and Janet was merely the one who _did_ so. Others did their best
to guess at the slide numbers.

   At least one-third of the sessions I listened to failed to provide
all we are told to expect in the way of jabber support. :^(

   OTOH, we _do_ get what we pay for; so I don't mean to complain.

--
John Leslie <john@jlc.net>

From iad@ietf.org  Mon Aug 12 14:54:37 2013
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 8D48A21F9F44; Mon, 12 Aug 2013 14:54:36 -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 H-FRk2fXGBff; Mon, 12 Aug 2013 14:54:36 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9DD21F9F2B; Mon, 12 Aug 2013 14:54:35 -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: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
Date: Mon, 12 Aug 2013 14:54:35 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 21:54:38 -0000

The RFC Series Editor (RSE) is proposing changes to the Statements of Work =
(SOW) for the RFC =

Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive c=
ommunity input prior to =

negotiating the proposed changes with the contractor.  Community input will=
 be discussed with the RSE =

prior to negotiations and reviewed by the IAOC.

In forwarding the proposed Statements of Work the RSE said:  "The changes s=
eek to make the SoWs =

more current [implementing RFC 6635] and specific, correcting the issues of=
 "multiple masters" =

directing the RPC and Publisher, as well as preparing the way for a more si=
gnificant revision to the SoWs
when the RFC Format changes are operationalized.  The SoWs have also been r=
eviewed and supported =

by the RSOC [RFC Series Oversight Committee].  We consider the changes with=
in the SoWs critical to the =

clear function of the RPC and Publisher, but suggest that the changes do no=
t imply a significant change =

in responsibility for the RPC or Publisher."

The proposed SOWs, the current SOWs and a diff file for each can be found h=
ere under Community =

Review: <http://iaoc.ietf.org/rfps.html>

We appreciate the community's input and look forward to hearing from you.  =


Thanks

Ray Pelletier
IAD

From alejandroacostaalamo@gmail.com  Mon Aug 12 16:43:56 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E74B21F8FD8 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 16:43:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8OpY9-5fG-jM for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 16:43:55 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6B92521F864D for <ietf@ietf.org>; Mon, 12 Aug 2013 16:43:52 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w60so6139048wes.1 for <ietf@ietf.org>; Mon, 12 Aug 2013 16:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=283c+2PPpJozNwRUfqfv/Li+r2B+aG95hOUpEe6EK4s=; b=aYgMevYxAt8T5bhHVIey4bW7yFD+xI2HFYBn4P2rtYa3B+9KDXflB2AohnlNpM73Nq rqFU4r5oRTWFYQUDopYcwHFKTMXjELSRKGKdxt2eY4axLFGpMGICAKT9xpcmUVKTS77a yTGA04jb0GAjlrNMAppThJ//xKoF/3UynpobylCcb3C0nfOVv3iWwpAPEHuhu8Sn3d8R l6umgikE0te5JDtNFJy+DveOuA1Oj7I/9/7M4Pzf6Ywo5iKEdnoFvNznfUJBteiwGNPH wKtry8JyqihPKjBXd/2f3gVtQb4xJBGPdtAwZPoRjMbWtGVx0hLVnJdCnNYIQXfWEYQ1 vVMA==
MIME-Version: 1.0
X-Received: by 10.180.182.67 with SMTP id ec3mr1129939wic.1.1376351031806; Mon, 12 Aug 2013 16:43:51 -0700 (PDT)
Received: by 10.217.143.196 with HTTP; Mon, 12 Aug 2013 16:43:51 -0700 (PDT)
In-Reply-To: <CAKe6YvMFcceT_bHsvfK2eNvSXBGzw5oSuV2r7RUJLRaHBLDtCw@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <CAOmxzdxTftsbyCghsGyfBrhuiKrti3mwRfNNzFCiUoTddpeFyQ@mail.gmail.com> <CAKe6YvMFcceT_bHsvfK2eNvSXBGzw5oSuV2r7RUJLRaHBLDtCw@mail.gmail.com>
Date: Mon, 12 Aug 2013 19:13:51 -0430
Message-ID: <CAOmxzdzP-MxtdJq3Sgh=wJo6dGZwKiamFNQPDKQ8EGpd6foC1Q@mail.gmail.com>
Subject: Re: Data collection for remote participation
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Vinayak Hegde <vinayakh@gmail.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: Mon, 12 Aug 2013 23:43:56 -0000

On 8/12/13, Vinayak Hegde <vinayakh@gmail.com> wrote:
> On Mon, Aug 12, 2013 at 8:35 PM, Alejandro Acosta
> <alejandroacostaalamo@gmail.com> wrote:
>> Hi Vinayak,
>>   First, well done, I fully agree with your email. I have two
>> questions for you/the group:

>>   I would add to your proposal some kind of activities from local ISOC
>> chapters.
>
> Did not understand. Can you elaborate ?

  Well, what I said is not directly related with your proposal, but
it's something like this: As you know ISOC has several chapters around
the world, all of them with many member, I have always believed it's a
good idea to organize local meetings to follow the IETF or at least
some WG sessions remotely. Of course ISOC has some kind of information
of their member (not much but they have something)


>
> -- Vinayak
>


-- 
=====
^A.......o$

From doug.mtview@gmail.com  Mon Aug 12 18:00:28 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B36ED21E8098 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 18:00: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=[BAD_CREDIT=0.001, 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 iirUZYxkkwD8 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 18:00:27 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8A511E80E9 for <ietf@ietf.org>; Mon, 12 Aug 2013 18:00:06 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w10so4121888pde.23 for <ietf@ietf.org>; Mon, 12 Aug 2013 18:00:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7RogKvB2kprEixkAiRn2uYqeCtjE4hE5Dt/ph1kz/c4=; b=eO7EZD9mf7XIia25KLPaX2oFOOEdWpWnSTsJm5l2TSECxturr/03chHrTj0JpTgG7u xtfu+eBiq61nBd1jVqml+hk26FSYtOpJs+i0jk8ZTJ3O+AJgpr9ENQwptPKhpRRX2Avm +HR68YeXXQYhDdMd1MNbst0XirIRDxQXDUlceZaYV89nw5XCQ3Y9DMK/hcdvIJaE7R3b lDw0pc3wp+lsz11WdBNE8TJDof0l4Bjx08CEE+18zkEhoiHAM8NWpA98bdM1hQ6u8iMY u1KwlKKZbXJGgxQZIALpohAanFH/71ihp58Zdhgf/1X4tIG+MJZUHdd3y22PVuF61bwP aXuw==
X-Received: by 10.67.14.67 with SMTP id fe3mr1729381pad.134.1376355605457; Mon, 12 Aug 2013 18:00:05 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:b098:107:26f1:1ff0? ([2601:9:3180:3e:b098:107:26f1:1ff0]) by mx.google.com with ESMTPSA id pu5sm42954241pac.21.2013.08.12.18.00.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 12 Aug 2013 18:00:04 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Radical Solution for remote participants
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <20130812200621.GB68553@verdi>
Date: Mon, 12 Aug 2013 18:00:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1508)
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: Tue, 13 Aug 2013 01:00:29 -0000

On Aug 12, 2013, at 1:06 PM, John Leslie <john@jlc.net> wrote:

> Janet P Gunn <jgunn6@csc.com> wrote:
>>=20
>>> Again, it strengthens the case to get it done right. This part has =
been
>>> working well though.
>>=20
>> Not necessarily.  There was one WG where I had to send an email to =
the WG=20
>> mailing list asking for someone to provide slide numbers on jabber.
>=20
>   ... and Janet was merely the one who _did_ so. Others did their best
> to guess at the slide numbers.
>=20
>   At least one-third of the sessions I listened to failed to provide
> all we are told to expect in the way of jabber support. :^(
>=20
>   OTOH, we _do_ get what we pay for; so I don't mean to complain.

Dear John,

You are right about getting your money's worth.  In the case of remote =
participants, they are charged nothing and receive no credit for having =
done so.  Often their input is ignored as well.=20

A radical solution for meaningful remote participation is to change how =
A/V in meeting rooms operate.  This change will require a small amount =
of additional equipment and slightly different room configurations.

1) Ensure exact digital interfaces driving projectors are fully =
available remotely. =20

2) Ensure Audio access requires an identified request via XMPP prior to =
enabling either a remote or local audio feed.

3) RFI tags could facilitate enabling local audio feed instead of an =
identified request via XMPP.

4) In the event of the local venue loosing Internet access, the device =
regulating A/V presentations must be able to operate in a virtual mode =
where only remote participants are permitted to continue the meeting =
proceedings.

5) Important participants should plan for alternative modes of Internet =
access to remain part of the proceedings.

6) Develop a simple syntax used on XMPP sessions to:
 1) signify a request to speak on X=20
 2) withdraw a request to speak on X
 3) signify support of Y
 4) signify non-support of Y
 5) signal when a request has been granted or revoked.  For local =
participants this could be in the form of a red or green light at their =
microphone.=20

7) Develop a control panel managed by chairs or their proxies that =
consolidate and sequence requests and log support and nonsupport =
indications and the granting of requests.

8) Chairs should be able to act as proxies for local participants =
lacking access to XMPP.=20

9) Chairs should have alternative Internet access independent of that of =
the venue's.
=20
10) Establish a reasonable fee to facilitate remote participants who =
receive credit for their participation equal to that of being local.

11) The device regulating A/V presentations must drive both the video =
and audio portions of the presentations.  A web camera in a room is a =
very poor replacement.

12) All video information in the form of slides and text must be =
available from the Internet prior to the beginning of the meeting.

Regards,
Douglas Otis


From framefritti@gmail.com  Tue Aug 13 00:36:16 2013
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67FEC21E80B9; Tue, 13 Aug 2013 00:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_50=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 SERZDn8X7wLP; Tue, 13 Aug 2013 00:36:16 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB7321F99B8; Tue, 13 Aug 2013 00:36:13 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so7608978pbb.20 for <multiple recipients>; Tue, 13 Aug 2013 00:36: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=0C9gdWz36drHvd10IpsuZ9sSGryjmplDrEMb7oK5fmg=; b=JFYy+PSZdUyhHrzdLgSDo13NNjxNy0jg6KobffwQ/cJudCgYzCHuYJeQm18Hxf4Soy yQnSLIqPqcgpFdy+PKaqYXM0be6rOLBoHXRWuFxy+2ud5XWcsT4NVltj+Aja3/0LLf7C +M35IVabkc4c4drVU6A4HdVPFM5OF7VKm0bVQVGIqy2aJSVJGdcJw92F0iF96xySftPu 5QvuM7oZjvwJTezuW6MXhq2fohh5ssNNQQMlEtzxhB3meAJ8p8gKMbIRc+yvTus8n7CT RFV8eWVP50mUuWFYCC5jIOnofngo4PCXo0QCKta+lbiuFOC3FzWcBY9XB+nbVBsNco3f ZzJQ==
MIME-Version: 1.0
X-Received: by 10.68.242.105 with SMTP id wp9mr3113037pbc.153.1376379372824; Tue, 13 Aug 2013 00:36:12 -0700 (PDT)
Received: by 10.70.27.97 with HTTP; Tue, 13 Aug 2013 00:36:12 -0700 (PDT)
In-Reply-To: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
Date: Tue, 13 Aug 2013 09:36:12 +0200
Message-ID: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: wgchairs@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>, iab@iab.org, iesg@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 07:36:16 -0000

Is this the document with the proposed SOW?

   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc

I know that I should not this, but... I am a bit surprised
(disappointed) in seeing a proprietary format used here.  I am not
saying that you should not use the Office suite to write it, but you
could convert it to PDF (better, PDF/A) before publishing it.

Anyway, I use Linux, so I guess I will not be able to give my input about it.

Best regards,

Riccardo


On Mon, Aug 12, 2013 at 11:54 PM, IETF Administrative Director
<iad@ietf.org> wrote:
> The RFC Series Editor (RSE) is proposing changes to the Statements of Work (SOW) for the RFC
> Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive community input prior to
> negotiating the proposed changes with the contractor.  Community input will be discussed with the RSE
> prior to negotiations and reviewed by the IAOC.
>
> In forwarding the proposed Statements of Work the RSE said:  "The changes seek to make the SoWs
> more current [implementing RFC 6635] and specific, correcting the issues of "multiple masters"
> directing the RPC and Publisher, as well as preparing the way for a more significant revision to the SoWs
> when the RFC Format changes are operationalized.  The SoWs have also been reviewed and supported
> by the RSOC [RFC Series Oversight Committee].  We consider the changes within the SoWs critical to the
> clear function of the RPC and Publisher, but suggest that the changes do not imply a significant change
> in responsibility for the RPC or Publisher."
>
> The proposed SOWs, the current SOWs and a diff file for each can be found here under Community
> Review: <http://iaoc.ietf.org/rfps.html>
>
> We appreciate the community's input and look forward to hearing from you.
>
> Thanks
>
> Ray Pelletier
> IAD

From dave@cridland.net  Tue Aug 13 00:40:15 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9130121E80DC for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 00:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.118
X-Spam-Level: 
X-Spam-Status: No, score=-0.118 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QR2nCohQfvA3 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 00:40:15 -0700 (PDT)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 85E5B21E80D9 for <ietf@ietf.org>; Tue, 13 Aug 2013 00:40:12 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i18so11081945oag.29 for <ietf@ietf.org>; Tue, 13 Aug 2013 00:40:12 -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=7jLB8sMay3i5n26Hf8o0OtQHEQEclQvYlZm91BAb44U=; b=Xs1ZiMKUMz6lmAl+JccTShEPh7gt5NPP8GVBMAlJl2quom+QNDdrVxBGZVCh7qc0WV olN5tjbg6YYiwSUVLO2/lRAkPxh/060lpBVB3fkl3tvydj7gsQAO1n6idq7yPk+vNDJO 7gOnlQsuep1b/PRqxXKpZwN9gBfM5PmMCBXw8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7jLB8sMay3i5n26Hf8o0OtQHEQEclQvYlZm91BAb44U=; b=nhYZjaXtFZeGFvTV7VrRvmELhxkSR7ll2+o0bcc9it3Mg9cSI3CBW9I+DwOYOQROCZ te2/WYQiqMLU49H5vJEGt7uR8tI87JB6Nn4Ds63fcJWfPC20S+JfXXx+N6RkKt+jysDa U+O9OV0BJwbJVdXa/LeKyGDCPe4/xRzb95kILfiGM/XCm/bctrE6oxKjbk4KrKob4aRt wDp3NYih/wGcA+0/tTlw678/1Cp2tcKJXQjKPgSxT2MP216qYBkiQOA6QfV0Rt8H3Frj n3KfhDR56QhQBHcdtzsPXOhCJ6uT+1xYcHm0uNRX68F/jPTRFYt6XwP6t/DUYZb/pHCx YHVg==
X-Gm-Message-State: ALoCoQmv2kWZOOh9II02gP+7yaonxd22NhJu0ws0v38sG9QZ0HiA7bjR2bzg1vAH6R4W/0zDUhuX
MIME-Version: 1.0
X-Received: by 10.60.52.101 with SMTP id s5mr350203oeo.56.1376379612099; Tue, 13 Aug 2013 00:40:12 -0700 (PDT)
Received: by 10.60.38.131 with HTTP; Tue, 13 Aug 2013 00:40:12 -0700 (PDT)
In-Reply-To: <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
Date: Tue, 13 Aug 2013 08:40:12 +0100
Message-ID: <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com>
Subject: Re: Radical Solution for remote participants
From: Dave Cridland <dave@cridland.net>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=001a11330d54db0b3104e3cf5903
Cc: John Leslie <john@jlc.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: Tue, 13 Aug 2013 07:40:15 -0000

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

On Tue, Aug 13, 2013 at 2:00 AM, Douglas Otis <doug.mtview@gmail.com> wrote:

> 10) Establish a reasonable fee to facilitate remote participants who
> receive credit for their participation equal to that of being local.
>

I understand the rationale here, but I'm nervous about any movement toward
a kind of "pay-to-play standardization". The idea of "buying credit" I find
slightly weird, too - if I spend enough, can I get credit for other
people's ideas, too? How much is TCP?

I'd be happy to pay for good quality remote participation, but I'd be
unhappy if this blocked participation in any significant way. One option
might be to give chairs some heavy influence on remote burserships.

Dave.

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

<div dir=3D"ltr">On Tue, Aug 13, 2013 at 2:00 AM, Douglas Otis <span dir=3D=
"ltr">&lt;<a href=3D"mailto:doug.mtview@gmail.com" target=3D"_blank">doug.m=
tview@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">10) Establish a reasonable fee to facilitate=
 remote participants who receive credit for their participation equal to th=
at of being local.<br>
</blockquote><div><br></div><div>I understand the rationale here, but I&#39=
;m nervous about any movement toward a kind of &quot;pay-to-play standardiz=
ation&quot;. The idea of &quot;buying credit&quot; I find slightly weird, t=
oo - if I spend enough, can I get credit for other people&#39;s ideas, too?=
 How much is TCP?</div>
<div><br></div><div>I&#39;d be happy to pay for good quality remote partici=
pation, but I&#39;d be unhappy if this blocked participation in any signifi=
cant way. One option might be to give chairs some heavy influence on remote=
 burserships.</div>
<div><br></div><div>Dave.=A0</div></div></div></div>

--001a11330d54db0b3104e3cf5903--

From melinda.shore@gmail.com  Tue Aug 13 00:49:50 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39E0821E80BC for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 00:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1NkQxaZd5Se for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 00:49:49 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id D5FA721E80B8 for <ietf@ietf.org>; Tue, 13 Aug 2013 00:49:49 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id y13so4515865pdi.5 for <ietf@ietf.org>; Tue, 13 Aug 2013 00:49:49 -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=FuS5ZwmeSd+T2tA0uv0a2YUuuhpEkNqdFnqQIxpTPhE=; b=v1qQwTvG7e5s+OKOYfWJd0FBTv1AJbkVRKN8RHgNW6s1btp/m0ygDg+RJ1u9MpeCSg koRzGRDdW68cgFYMScu9I5MM5R45v6wQQ79frVGvJkKZeZCql/qQ+RSfIiB+8+CudUzM MxxUdZ9PiNjuDbS1HDY6pEQOGSL1iDE9sNhf0hd7nH6jUxJfRJjKUTz9Ywt35jRuiw7R OgkIfoEBYvCm7m760LBO/2FgU1fY2xnY4qVXLHzdBIPy0RbUhtbdtRLtO9HlVLJwb+zy rjqMlW9Z4Wha8rIUL/LmDEqaqYN9a2a1eiUAloU7ZGGGRjrGYGpzM7DDikhBOanKz4K/ K0VA==
X-Received: by 10.68.163.131 with SMTP id yi3mr3205264pbb.55.1376380189626; Tue, 13 Aug 2013 00:49:49 -0700 (PDT)
Received: from spandex.local (66-230-112-160-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.160]) by mx.google.com with ESMTPSA id py4sm42157826pbc.14.2013.08.13.00.49.47 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 13 Aug 2013 00:49:48 -0700 (PDT)
Message-ID: <5209E519.6080809@gmail.com>
Date: Mon, 12 Aug 2013 23:49:45 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
In-Reply-To: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 07:49:50 -0000

On 8/12/13 11:36 PM, Riccardo Bernardini wrote:
> Anyway, I use Linux, so I guess I will not be able to give my input about it.

I agree in principle (MS document formats are not a suitable document
exchange format for an open standards body) but in truth, it's been
awhile since Open Office hasn't been able to read .doc files correctly.
I'd rather not see any .doc, .ppt, etc. files in the future but I
don't think it's correct to say that their use excludes people on
different platforms or with different software.

Melinda



From john@jlc.net  Tue Aug 13 03:25:05 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B64B221E80EE for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 03:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6UeejfJw7Cy for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 03:25:00 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 9649321E80E1 for <ietf@ietf.org>; Tue, 13 Aug 2013 03:25:00 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id E838133C27; Tue, 13 Aug 2013 06:24:59 -0400 (EDT)
Date: Tue, 13 Aug 2013 06:24:59 -0400
From: John Leslie <john@jlc.net>
To: Dave Cridland <dave@cridland.net>
Subject: Re: Radical Solution for remote participants
Message-ID: <20130813102459.GC68553@verdi>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com>
User-Agent: Mutt/1.4.1i
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: Tue, 13 Aug 2013 10:25:05 -0000

Dave Cridland <dave@cridland.net> wrote:
> On Tue, Aug 13, 2013 at 2:00 AM, Douglas Otis <doug.mtview@gmail.com> wrote:
> 
>> 10) Establish a reasonable fee to facilitate remote participants who
>>     receive credit for their participation equal to that of being local.
> >
> 
> I understand the rationale here, but I'm nervous about any movement toward
> a kind of "pay-to-play standardization".

   Alas, that is what we have now. :^(

   There are a certain number of Working Groups where it's standard
operating practice to ignore any single voice who doesn't attend an
IETF week to defend his/her postings.

   I don't always understand what Doug is asking for; but I suspect
he is proposing to define a remote-participation where you get full
opportunity to defend your ideas. This simply doesn't happen today.

> I'd be happy to pay for good quality remote participation, but I'd
> be unhappy if this blocked participation in any significant way.

   The fact remains that full remote participation has costs. These
costs only become greater if we pretend that we can expect current
WGCs to do the additional work.

> One option might be to give chairs some heavy influence on remote
> burserships.

   Do you mean
" 
" bursarship: noun
"   a grant or payment made to support a student's education.

   That seems premature at this point: the likely costs aren't neatly
correlated to number of remote participants; so it's not clear there's
any reason to "support" an individual, rather than support the tools.

   Today, requests for IETF-week sessions include checkoffs for
"WebEx required" and "MeetEcho" required. AFAIK these simply generate
requests to cisco and meetecho to subsidize the tool for that session.
Cisco seems to automatically approve using the fully-automated tool,
while meetecho seems to need to allocate staff for setup.

   But of course these checkoffs happen long before the WGC knows of
individuals desiring to participate remotely. :^(

   Conceivably what we need is an automated tool to receive offers
to (partially) subsidize the cost of a tool for a particular session.

--
John Leslie <john@jlc.net> 

From fanf2@hermes.cam.ac.uk  Tue Aug 13 04:15:21 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4263721F9EE1; Tue, 13 Aug 2013 04:15: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 S6ukHyXTHJkM; Tue, 13 Aug 2013 04:15:20 -0700 (PDT)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 8875E21F86DD; Tue, 13 Aug 2013 04:14:30 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:45907) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1V9CYO-000824-81 (Exim 4.80_167-5a66dd3) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 13 Aug 2013 12:14:20 +0100
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1V9CYO-0006Af-Do (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 13 Aug 2013 12:14:20 +0100
Date: Tue, 13 Aug 2013 12:14:20 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
In-Reply-To: <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
Message-ID: <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 11:15:21 -0000

Carsten Bormann <cabo@tzi.org> wrote:
>
>    The Concise Binary Object Representation (CBOR) is a data format
>    whose design goals include the possibility of extremely small code
>    size, fairly small message size, and extensibility without the need
>    for version negotiation.  These design goals make it different from
>    earlier binary serializations such as ASN.1 and MessagePack, or other
>    binary serializations that may be created in the future.

I have a small problem with this abstract: the three goals that it picks
out are satisfied by MessagePack better than CBOR, since MessagePack is
simpler so will need even less code. As far as I can tell what makes CBOR
different from MessagePack is support for richer types, especially
strings. Streaming support is useful but it wasn't one of the original
goals.

Regarding PHB's criticisms of complexity: Type tags don't really need to
be part of the serialization format: they can be encoded in a simpler
format by the application. The advantage of doing so would be a more
direct translation into typical dynamic language data structures, and
better interop with JSON. The disadvantage is slightly more verbosity. You
would need a clear tagging convention to replace the syntactic framework.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From sm@resistor.net  Tue Aug 13 05:07:12 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F2011E8152; Tue, 13 Aug 2013 05:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.444
X-Spam-Level: 
X-Spam-Status: No, score=-99.444 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, SARE_FWDLOOK=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 57T3CVE11O2G; Tue, 13 Aug 2013 05:07: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 E735811E814D; Tue, 13 Aug 2013 05:07:10 -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 r7DC6ota022208; Tue, 13 Aug 2013 05:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376395617; bh=Vw+jDurUtXj1aJ/vnLsQ6o0o6LYRFJAPZo7rANrqtm4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Hkyy+35cLeIerIO4d9cUB+iKBmIDvW5qZAgKE5ZrLXEV/ElC0kWWw6iZ1YwnKxtRv /rCj/xp3rWrvSBibOotETMWGU0SFwHkELSEFyYJbUj4hQoJb72uIFwwaKMJI8ZIOCr xyQkHlZPLNHHRHcK6Duj1Xjab4Pp/19A4qWq20Eg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376395617; i=@resistor.net; bh=Vw+jDurUtXj1aJ/vnLsQ6o0o6LYRFJAPZo7rANrqtm4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KmJUzywz2QuqYhMo2Bzu86ScLa3u+YVvaGax8wx0tTrAaEWObHeTrPvyshmi73NF+ JJx6Vk0r3r3G8k5z8z7V8VLrjisEPpjyhjoBzHkNVAr985UOg9d9iEnex9SleCE0uJ hDzNCLsZPjnhgVxIlK/6dkUXYzi17NNUN3jP1UtQ=
Message-Id: <6.2.5.6.2.20130813042024.0b65b518@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 13 Aug 2013 05:06:22 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-weirds-rdap-sec-04.txt> (Security Services for the Registration Data Access Protocol) to Proposed Standard
In-Reply-To: <CAL0qLwZuNLE6qSksxa7z83WxEUWO1OYsBORWfsMA2naJaNx0NQ@mail.g mail.com>
References: <20130715230614.25146.34230.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130724111528.0d2bf428@resistor.net> <CAL0qLwZuNLE6qSksxa7z83WxEUWO1OYsBORWfsMA2naJaNx0NQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, weirds@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 12:07:12 -0000

Hi Murray,
At 10:36 AM 8/5/2013, Murray S. Kucherawy wrote:
>RDAP is far from the first protocol specification to exist across 
>multiple RFCs, so this approach isn't uncommon.  That said, I take 
>it you believe the material here should be rolled into one of the 
>other documents?

Yes.

>Correct, that's what it says.
>
>   "RDAP SHOULD be capable of supporting future authentication methods
>    defined for use with HTTP."
>
>That sounds like a "SHOULD CONSIDER".  Given how ill-defined the 
>protocol is I doubt that the above is actionable.
>
>
>You said two important things here:
>
>1) Can you please elaborate on why you think this is "ill-defined" 
>and, if possible, how this could be remedied?

It's difficult to understand what RDAP is as it is not clearly 
defined.  That is what I meant by "ill-defined".  In the above 
example, the "SHOULD" does not specify anything.  It  looks like a 
"forward-looking statement" as the "future authentication methods" are unknown.

I would look at the specification in terms of what is required to 
achieve interoperability now instead of trying to define future 
needs.  In terms of protocol it would be what the two sides have to 
do to talk to each other.  One of the issues in MILE what that there 
wasn't a clear separation of the HTTP aspect and the MILE aspect.  In 
simple terms it is better not to redefine how HTTP works; i.e. a 404 
is a 404 instead of a contextual meaning of that code.

>2) Insofar as this draft amounts to a requirements document, I take 
>"SHOULD be capable" to mean the actual implementation needs to have 
>hooks for the stated capability, or have a very good reason for not 
>providing those hooks (e.g., the same capability is available some other way).

The draft is intended as a proposed standard.  In my opinion that is 
different from a requirements document.   The usage of SHOULD does 
not make it implementable.  It is like using SHOULD to beat people up 
if they do not implement some future capability. :-)

>More precisely, the draft takes the stance that federated 
>authentication is an option.  The working group doesn't feel the 
>need to elevate this to SHOULD or MUST, likely because operators 
>might not be compelled to federate themselves with anyone for 
>whatever local security or privacy reasons apply.

I mean that the draft does not contain any security feature which is 
mandatory to implement.

>Right, and the benefits it provides in the context of RDAP.  Is that 
>a criticism or an observation?  What do you suggest?

I don't think that the executive summary provides much value.  I 
suggest dropping the tutorial material. :-)

>The next sentence (which you omitted) provides the 
>context.  Operators are advised to be aware of denial-of-service 
>considerations, and there's a document referenced that provides 
>useful information.  Depending on the uptake of RDAP and the other 
>services that begin to depend upon it, it might become a DoS 
>target.  Hardening against such attacks will be important to begin 
>with, but might become critical later.  I think this is not a waste of space.

Ok.

>It is a web service, in as much as it uses web protocols.  Is there 
>some improvement you'd like to suggest?

The approach taken can create interoperability issues.  I would look 
at this in terms of what the codes has to do.

>Non-repudiation (which is the context of the paragraph from which 
>that sentence was taken) is one of the classic properties of 
>security, so I don't agree.  It's useful to point out to the reader 
>that non-repudiation is not provided by any of the capabilities 
>discussed here, and its absence might be conspicuous.

This draft looks like a tutorial for the not-well-informed. 
:-)  There is likely some BCP which already discusses about non-repudiation.

>It's true that the specific things called out in that paragraph are 
>not specific to RDAP, but rather to anything built atop HTTP.  Do 
>you suggest something else, perhaps something more general like a 
>statement that any known HTTP-based attack might also affect an RDAP service?

I would use that as the starting point and then discuss attacks which 
are specific to the service.

>SecDir often scratches its head when a document says very little, so 
>what you're saying is often the case.  However, sometimes it's 
>enough to say "This is built on top of HTTP, so all the security 
>issues known about HTTP and HTTPS also apply here."  Do you have a 
>specific suggestion?

It would be better to point to the relevant sections if the objective 
is to help the reader identify relevant issues.

>That seems a little sharp.

The comments were strong. :-(

>This draft is manifestly not a technical specification insofar as it 
>does not define a new protocol.  I would say it's partly a 
>requirements document and partly an applicability statement, and the 
>latter at least is normally a standards track document.

I personally think that there is a lack of understanding of what an 
applicability statement is.  I commented on the draft from a 
technical specification angle.

>I don't know what "thinking about security" we are expected to do 
>beyond making use of the security services that have already been 
>made available to applications built atop HTTP.  Do you have any 
>specific suggestions?

It is a lot of work to explain or suggest text.  It's not worth 
putting in the effort if the working group believes that the draft is okay.

Regards,
-sm


>-MSK


From sm@elandsys.com  Tue Aug 13 05:07:37 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAED11E817A for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 05:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.748
X-Spam-Level: 
X-Spam-Status: No, score=-99.748 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VTI+Lrt0Ixun for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 05:07:35 -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 8289E11E8173 for <ietf@ietf.org>; Tue, 13 Aug 2013 05:07:27 -0700 (PDT)
Received: from sm-THINK.elandsys.com ([197.224.133.219]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7DC7BoW012433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Aug 2013 05:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376395644; bh=M3vQHh+0ctM+i0rsZ11Izz5JYRkoglm9GaVRyAo3WSs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rdG6kbKJQ1NPX6716FPR/o1GWSytmuEfZLka7yw+SzX6aGjos8GqJfMTem9DnvC+O O7kya6KniT6SAhBeWJxgHhz9oTtJvMQw05GwMjV5/CL4z8+xSqQ9rAS6n+Vq1QGqyd l4vGIJl2rVbOCCnN4dNpgTcgAkcpCoYdRTVZ6kRQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1376395644; i=@elandsys.com; bh=M3vQHh+0ctM+i0rsZ11Izz5JYRkoglm9GaVRyAo3WSs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eHgKLrrbm2upkHKqXi7JqxIIXPs0LqlK34ltHSxW0ZUl4bINzoLer0xL/bxit88hn aNMwT6dhhUhvDCAmyhdN0ezzDcjk1OW0JFh6iAx4vBxW99z1gdplb0lR6xQSQoLquV 0Qrncv05dtR4gZ9osBOzhSwudnym8Z0SVeDBniuM=
Message-Id: <6.2.5.6.2.20130812091129.08d9bd38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 12 Aug 2013 09:28:12 -0700
To: Vinayak Hegde <vinayakh@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Data collection for remote participation
In-Reply-To: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.g mail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 12:07:37 -0000

Hi Vinayak,
At 06:09 AM 8/12/2013, Vinayak Hegde wrote:
>There has been a lot of discussion on the IETF mailing list regarding
>improving remote participation and improving diversity on the mailing
>lists and in the working groups. I think the two are related. I think
>everyone broadly agrees that remote participation can be better. If
>nothing else, it will tell about who the remote participants are. I
>had proposed a few steps in this direction by improving the data
>collection for remote participation in the IAOC Sunday meeting.
>Posting them below again for discussion on the mailing lists.
>
>It can be a simple form that asks the following questions (Can be
>refined - this is just a start)
>1. Name:
>2. Country:
>3. Duration of participation in IETF (either in number of years or
>number of meetings)
>4. Employer ?
>5. Working groups interested in.
>
>This can be voluntary and can be done pre-IETF meeting. As of now
>there is no structured way to know how many people wre active in the
>jabber room or listening on the audio stream.

As the data collection is voluntary it should not be a problem to ask 
for the information mentioned above.

>I can see that this has multiple benefits.
>1. If the number of participants in a certain WG is more, it would
>push the WG chair to request for the slides/agenda available earlier.

I suggest asking the working group for the agenda if it is not available.

>2. If there are consistently more participation from around the world,
>the the WG chair can request for a meetecho recording so people can
>follow the group even if they cannot attend the meeting live. This
>could be useful for people who have clashing schedules as well.

Yes.

>3. Over a longer period of time, it can help IETF plan and encourage
>remote participation. Currently there is no hard data on number of
>remote participants. There is however a lot of hand waving so this
>will get some useful data into the system.

There is the usual hand waving. :-)  It is a good start.  The 
information available over a period of time might provide a view of 
whether there is any improvement in remote participation.

At 08:56 AM 8/12/2013, Vinayak Hegde wrote:
>This was a suggestion but I don't think it will work well. OTOH an
>argument can be made that money gathered from charging remote
>participants can be used to fund better tools for remote
>participation.

After reading about the remote participation issues which have been 
discussed on this mailing list I don't think that the problem is the tools.

Regards,
S. Moonesamy  


From Ted.Lemon@nominum.com  Tue Aug 13 06:53:53 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65DFA21E8127 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 06:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4n5J69uDsN5 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 06:53:46 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id E8C2F21E811D for <ietf@ietf.org>; Tue, 13 Aug 2013 06:53:44 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUgo6aEAcWfyScLWA0LCh2QqW8uY8H5Wn@postini.com; Tue, 13 Aug 2013 06:53:44 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9620A1B8116 for <ietf@ietf.org>; Tue, 13 Aug 2013 06:53:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8D30A19006C; Tue, 13 Aug 2013 06:53:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 13 Aug 2013 06:53:44 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5209E519.6080809@gmail.com>
Date: Tue, 13 Aug 2013 09:53:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <A92B1BA6-735C-4FCB-BE3F-315E5AAC30CE@nominum.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com> <5209E519.6080809@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
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: Tue, 13 Aug 2013 13:53:53 -0000

On Aug 13, 2013, at 3:49 AM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
> I agree in principle (MS document formats are not a suitable document
> exchange format for an open standards body) but in truth, it's been
> awhile since Open Office hasn't been able to read .doc files =
correctly.

I wonder, though, if this document might have contained change bars that =
nobody but people who use MS Word would see.   Opening the document up =
in Preview on the Mac, it's just four or five pages of text, with no way =
to evaluate what changed.


From johnl@iecc.com  Tue Aug 13 06:58:08 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02A821E80D8 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 06:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdBpmTOG4ixX for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 06:58: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 9790221E8125 for <ietf@ietf.org>; Tue, 13 Aug 2013 06:58:02 -0700 (PDT)
Received: (qmail 14729 invoked from network); 13 Aug 2013 13:51:22 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 13 Aug 2013 13:51:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520a39da.xn--3zv.k1308; i=johnl@user.iecc.com; bh=rgaS73f1YZ+bhv4nfqorLsIyb6tjdFJ4si+CHdpwOZo=; b=Nb47lP4EQWHgiUcCs8jiyYGeFv8lIFRM6Wrt4j5xa1z6Ctd4X5MGxLk/10ZsK6hzHmhLrrA1Cqp/fXdGsvDogrt2jk3wUCG2LhxHPPxYYeSpsJodOOdtLl03SAU7cEFLUkgxN0XTXcMetIuZfqWWdlq9KUToGFPPIFoHpzg39/VMJmyiEhX6UaJLELlHQsj1qs+OLCDUKcRYYbWajBDxMP9OySvjWEJPhovTibAvYuamdp2w6V2GMJQXDqTgDU1F
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520a39da.xn--3zv.k1308; olt=johnl@user.iecc.com; bh=rgaS73f1YZ+bhv4nfqorLsIyb6tjdFJ4si+CHdpwOZo=; b=c7NgVDYa5DaHRj/j+TyDctI1OhSQ9P601RaZ089Encujo8KGJ9qjJGjFAcA5T94hTjA4RxG1GIIjQEPzGPIECi6gQLqR+2XYPETUheG0WYP1wsi/5/kBrYXEPRgsHNxQTl5PnfwhsKVxSLEyORIEmV9rrqrPYUVkWyq+HAcmHdrJpaD0lnwZHngTFb+YNZotQUlojkpbHZMdQaCzv+U89iqzFDEbNlW0WsoPBTfGc+9QEKz8NtYRtUYgQYDh7/Qi
Date: 13 Aug 2013 13:51:00 -0000
Message-ID: <20130813135100.2250.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
In-Reply-To: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 13:58:08 -0000

>   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc
>
>I know that I should not this, but... I am a bit surprised
>(disappointed) in seeing a proprietary format used here.  I am not
>saying that you should not use the Office suite to write it, but you
>could convert it to PDF (better, PDF/A) before publishing it.
>
>Anyway, I use Linux, so I guess I will not be able to give my input about it.

Hmmn.  Is there some reason you are unable to install OpenOffice?  It
opens and displays the SoW including the redline just fine.

I suppose she could have sent it out in OpenOffice's .odt format which
is nominally more open, but then the people who use MS Word (I hear
there are still a few of them) couldn't read it.  There's no great way
to send around a redlined document and I'd say that Word formats are
currently the least bad.  I presume you know that the more recent
.docx file format is ISO/IEC 29500, so that should make everyone
happy, modulo the detail that it's so complicated that in practice the
older nominally un-open .doc interoperates a lot more reliably.

R's,
John

From framefritti@gmail.com  Tue Aug 13 07:13:01 2013
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBB021E811D for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 07:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[AWL=1.300, 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 ilqgAKAzhoYk for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 07:13:01 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 669AA21E810A for <ietf@ietf.org>; Tue, 13 Aug 2013 07:13:01 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id q10so4947175pdj.35 for <ietf@ietf.org>; Tue, 13 Aug 2013 07:13: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=iS7JL9hLBJcS7OI0OhC0+E6Y9HvwN/UUHW2bKfhH3rY=; b=al3yIPPVj4EuOyxI7E6xPEA8BdiCqJ47QWJPZBt8ESULjJ7pRWsTmmXS2FLNjIBxIt gwyiokmzuzNOJ7uNT18+bSOcmy7zZg8398gXeBXqZ7cLxgSFjxQyirWngd2OKOhBPOw5 UjKQIDkWJg3wE7PJiItW6e38hJvnDa3fEYIwX03j4usbRHeBX9VLgYNRaSr/YCuPsqnn 5kCeDf6UZkxbNwjx8iQ5s8Qkv/rL3GGvGfFRDghe1zOIusCtBD/qKwuk2XD3EoeDrh6K yZOa4mKXGEJkysbBfOpjE6zjSFEgZq/mL00DwRJ/8Ls4zr8/rXwmrAm/4hbyYCh3iA52 +kTA==
MIME-Version: 1.0
X-Received: by 10.66.231.42 with SMTP id td10mr4679242pac.144.1376403181109; Tue, 13 Aug 2013 07:13:01 -0700 (PDT)
Received: by 10.70.27.97 with HTTP; Tue, 13 Aug 2013 07:13:01 -0700 (PDT)
In-Reply-To: <20130813135100.2250.qmail@joyce.lan>
References: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com> <20130813135100.2250.qmail@joyce.lan>
Date: Tue, 13 Aug 2013 16:13:01 +0200
Message-ID: <CABSMSPWyx5q-pqUa48RyfydT_C+b5t70TVLdxSchV=-uWYh0Kg@mail.gmail.com>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Riccardo Bernardini <framefritti@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 14:13:02 -0000

On Tue, Aug 13, 2013 at 3:51 PM, John Levine <johnl@taugh.com> wrote:
>>   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc
>>
>>I know that I should not this, but... I am a bit surprised
>>(disappointed) in seeing a proprietary format used here.  I am not
>>saying that you should not use the Office suite to write it, but you
>>could convert it to PDF (better, PDF/A) before publishing it.
>>
>>Anyway, I use Linux, so I guess I will not be able to give my input about it.
>
> Hmmn.  Is there some reason you are unable to install OpenOffice?  It
> opens and displays the SoW including the redline just fine.

OK, I admit I was over-polemicizing (stretching the language a bit..)

To be honest, my experience with opening .doc files with OO is a mixed
bag: often the rendering is good enough, but sometimes, with fancy
documents, funny things happen.

>
> I suppose she could have sent it out in OpenOffice's .odt format which
> is nominally more open, but then the people who use MS Word (I hear
> there are still a few of them) couldn't read it.   There's no great way
> to send around a redlined document and I'd say that Word formats are
> currently the least bad.  I presume you know that the more recent
> .docx file format is ISO/IEC 29500

No I did not know that and I must say that I like it. I can imagine
that is quite complex, but at least it is open.  A doubt remains:
which fundamental features were missing from odt (an ISO/IEC standard
too, as far as I know) to grant for the definition of a new complex
object like a document format?  Anyway, I do not want to start a
discussion about this (which BTW is becoming a bit OT with respect to
the main thread).

>, so that should make everyone
> happy, modulo the detail that it's so complicated that in practice the
> older nominally un-open .doc interoperates a lot more reliably.
>
> R's,
> John

From cabo@tzi.org  Tue Aug 13 07:29:06 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43DC021E816C; Tue, 13 Aug 2013 07:29:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4LUUbz5AcDU; Tue, 13 Aug 2013 07:29:00 -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 637C521E811A; Tue, 13 Aug 2013 07:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7DESIAN000411; Tue, 13 Aug 2013 16:28:18 +0200 (CEST)
Received: from [192.168.217.105] (p5489267F.dip0.t-ipconnect.de [84.137.38.127]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 75E1F4CC; Tue, 13 Aug 2013 16:28:18 +0200 (CEST)
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
Date: Tue, 13 Aug 2013 16:28:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA3B1C2C-DF2A-4DC8-8F9D-9E915BAB1BF4@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org> <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 14:29:06 -0000

On Aug 13, 2013, at 13:14, Tony Finch <dot@dotat.at> wrote:

> Type tags don't really need to
> be part of the serialization format: they can be encoded in a simpler
> format by the application.=20

Yes, and we also can get rid of maps {"a": 1, "b": 2}.

Just represent them as arrays of two-element arrays [["a", 1], ["b", =
2]].
Or, actually, as arrays where the even-indexed elements are the keys =
["a", 1, "b", 2].
(This is, in the end, close to what happens in the encoder anyway.)

There is a reason why we provide some type tagging (here: distinguish =
arrays and maps) in the encoding: The decoder may be able to factor out =
some common handling that otherwise would need to be done on the =
application.

In other words, removing maps in the name of simplicity just moves the =
complexity elsewhere, in this case to the application.

Now, the application may already be prepared to handle the complexity, =
and if you come from a JSON world, you are probably *used* to having it =
handle the equivalent of CBOR's tags in the application: JSON doesn't =
have tags.  Supporting applications that do that is a reason why the use =
of tags is optional.

Gr=FC=DFe, Carsten


From GK@ninebynine.org  Mon Aug 12 15:30:21 2013
Return-Path: <GK@ninebynine.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 3373121F9FA4 for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 15:30:21 -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 5yMW-zzVKDsf for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 15:30:15 -0700 (PDT)
Received: from relay14.mail.ox.ac.uk (relay14.mail.ox.ac.uk [163.1.2.162]) by ietfa.amsl.com (Postfix) with ESMTP id 44E2E21F9A35 for <ietf@ietf.org>; Mon, 12 Aug 2013 15:30:15 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay14.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1V90cv-0008Jc-jC for ietf@ietf.org; Mon, 12 Aug 2013 23:30:13 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1V90cu-0001u3-8M for ietf@ietf.org; Mon, 12 Aug 2013 23:30:12 +0100
Message-ID: <52095E5D.5070802@ninebynine.org>
Date: Mon, 12 Aug 2013 23:14:53 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Tue, 13 Aug 2013 08:02:12 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 22:30:21 -0000

> From: The IESG <iesg-secretary@ietf.org>
> To: IETF-Announce <ietf-announce@ietf.org>
> Reply-To: ietf@ietf.org
> Sender: <iesg-secretary@ietf.org>
> Subject: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
>
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol'
>   <draft-nandakumar-rtcweb-stun-uri-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 2013-08-16. 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 is the specification of the syntax and semantics of the
>   Uniform Resource Identifier (URI) scheme for the Session Traversal
>   Utilities for NAT (STUN) protocol.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-nandakumar-rtcweb-stun-uri/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-nandakumar-rtcweb-stun-uri/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.

As IANA designated expert for reviewing URI scheme registrations, I've been 
asked to approve this scheme for registration.  If there is IETF consensus to 
publish this document, it is clear to me that the scheme should be registered.

But, in a personal capacity, not as designated reviewer, I have to ask *why* 
this needs to be a URI.  As far as I can tell, it is intended for use only in 
very constrained environments, where there seems to be little value in having an 
identifier that can appear in all the contexts where a URI may be recognized.

The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 include:

"New URI schemes SHOULD have clear utility to the broad Internet community, 
beyond that available with already registered URI schemes."
-- http://tools.ietf.org/html/rfc4395#section-2.1

This "utility to the broader community" is not clear to me, but I don't fully 
understand the intended scope of this protocol, so I could be missing something. 
  So, in declaring consensus for this specification, I would request that this 
aspect at least be considered.

...

Further, according to http://tools.ietf.org/html/rfc5389 it appears that there 
are security considerations with regard to the STUN protocol that it should not 
be used in isolation:
[[
    Classic STUN also had a security vulnerability -- attackers could
    provide the client with incorrect mapped addresses under certain
    topologies and constraints, and this was fundamentally not solvable
    through any cryptographic means.  Though this problem remains with
    this specification, those attacks are now mitigated through the use
    of more complete solutions that make use of STUN.

    For these reasons, this specification obsoletes RFC 3489, and instead
    describes STUN as a tool that is utilized as part of a complete NAT
    traversal solution.
]]
-- http://tools.ietf.org/html/rfc5389#section-2

It seems to me that creating a URI for STUN could encourage its use in 
environments outside the "more complete solutions that make use of STUN".  This 
seems to be further reason that STUN[S] should not be a URI scheme.

I have also suggested that, if registered, the URI scheme registration should 
carries a "health warning" to this effect, and that it is not suitable for 
general use that is not part of a "complete NAT traversal solution".  But I also 
recognize that I do not fully grasp the security implications, and that if those 
that do know better can agree that there is no potential for creating security 
risks here, this suggestion may be unnecessary.

#g
--

From GK@ninebynine.org  Mon Aug 12 15:30:42 2013
Return-Path: <GK@ninebynine.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 9A29321F9AED for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 15:30:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ts1bm2G77Zsv for <ietf@ietfa.amsl.com>; Mon, 12 Aug 2013 15:30:31 -0700 (PDT)
Received: from relay16.mail.ox.ac.uk (relay16.mail.ox.ac.uk [163.1.2.166]) by ietfa.amsl.com (Postfix) with ESMTP id 4FED821F99CF for <ietf@ietf.org>; Mon, 12 Aug 2013 15:30:31 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay16.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1V90cw-0006gU-qT for ietf@ietf.org; Mon, 12 Aug 2013 23:30:14 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1V90cv-0001u6-99 for ietf@ietf.org; Mon, 12 Aug 2013 23:30:14 +0100
Message-ID: <52095E77.3000908@ninebynine.org>
Date: Mon, 12 Aug 2013 23:15:19 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Last Call: <draft-petithuguenin-behave-turn-uris-05.txt> (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Tue, 13 Aug 2013 08:02:12 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Aug 2013 22:30:42 -0000

> From: The IESG <iesg-secretary@ietf.org>
> To: IETF-Announce <ietf-announce@ietf.org>
> Reply-to: iesg-secretary@ietf.org
> Subject: Last Call: <draft-petithuguenin-behave-turn-uris-05.txt> (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed
> X-C5I-RSN: 1/0/934/11413/12177
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers'
> <draft-petithuguenin-behave-turn-uris-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 2013-08-16. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
> This document specifies the syntax of Uniform Resource Identifier
> (URI) schemes for the Traversal Using Relays around NAT (TURN)
> protocol. It defines two URI schemes to provision the TURN
> Resolution Mechanism [RFC5928].
>

As IANA designated expert for reviewing URI scheme registrations, I've been 
asked to approve this scheme for registration.  If there is IETF consensus to 
publish this document, it is clear to me that the scheme should be registered.

But, in a personal capacity, not as designated reviewer, I have to ask *why* 
this needs to be a URI.  As far as I can tell, it is intended for use only in 
very constrained environments, where there seems to be little value in having an 
identifier that can appear in all the contexts where a URI may be recognized.

The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 include:

"New URI schemes SHOULD have clear utility to the broad Internet community, 
beyond that available with already registered URI schemes."
-- http://tools.ietf.org/html/rfc4395#section-2.1

This "utility to the broader community" is not clear to me, but I don't fully 
understand the intended scope of this protocol, so I could be missing something. 
  So, in declaring consensus for this specification, I would request that this 
aspect at least be considered.
  be considered.

#g
--


From Ted.Lemon@nominum.com  Tue Aug 13 08:03:28 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B19021E811E for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 08:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Nop1U2KorIf for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 08:03:22 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id E036311E80AD for <ietf@ietf.org>; Tue, 13 Aug 2013 08:03:21 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUgpKuaEGcOYQlm0RoYqkuWS8slRStj56@postini.com; Tue, 13 Aug 2013 08:03:21 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 90E4D1B82A5 for <ietf@ietf.org>; Tue, 13 Aug 2013 08:03:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8AFCC19006C; Tue, 13 Aug 2013 08:03:21 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 13 Aug 2013 08:03:15 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1793.4\))
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20130813135100.2250.qmail@joyce.lan>
Date: Tue, 13 Aug 2013 11:03:13 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <5ECCE03E-BD02-437C-B021-72DC0C459385@nominum.com>
References: <20130813135100.2250.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1793.4)
X-Originating-IP: [192.168.1.10]
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: Tue, 13 Aug 2013 15:03:28 -0000

On Aug 13, 2013, at 9:51 AM, John Levine <johnl@taugh.com> wrote:
> There's no great way
> to send around a redlined document and I'd say that Word formats are
> currently the least bad.

rfcdiff does really nicely, actually.


From paul.hoffman@vpnc.org  Tue Aug 13 08:12:50 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0206721E818D; Tue, 13 Aug 2013 08:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zuY3yYpdXQzw; Tue, 13 Aug 2013 08:12:49 -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 5479A21E818A; Tue, 13 Aug 2013 08:12:48 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-185.dsl.dynamic.sonic.net [50.1.98.185]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r7DFCH3J081236 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Aug 2013 08:12:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-185.dsl.dynamic.sonic.net [50.1.98.185] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
Date: Tue, 13 Aug 2013 08:12:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8BC71C0-DFD5-4D34-81DB-CE4539B4EAEF@vpnc.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org> <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org list" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 15:12:50 -0000

On Aug 13, 2013, at 4:14 AM, Tony Finch <dot@dotat.at> wrote:

> Carsten Bormann <cabo@tzi.org> wrote:
>>=20
>>   The Concise Binary Object Representation (CBOR) is a data format
>>   whose design goals include the possibility of extremely small code
>>   size, fairly small message size, and extensibility without the need
>>   for version negotiation.  These design goals make it different from
>>   earlier binary serializations such as ASN.1 and MessagePack, or =
other
>>   binary serializations that may be created in the future.
>=20
> I have a small problem with this abstract: the three goals that it =
picks
> out are satisfied by MessagePack better than CBOR, since MessagePack =
is
> simpler so will need even less code.

MsgPack is not extensible. If it was, we might have been able to avoid =
all of this.

> As far as I can tell what makes CBOR
> different from MessagePack is support for richer types, especially
> strings. Streaming support is useful but it wasn't one of the original
> goals.

It *was* part of the original goals; it wasn't part of the original =
format. Some people on the AppsAWG list pointed out to us that our =
format was not meeting its goals by not supporting streaming, so we =
added it. Yes, this added a bit of complexity for decoders, but we =
handled that as best we could.

--Paul Hoffman


From john-ietf@jck.com  Tue Aug 13 08:36:40 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5DB11E814B for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 08:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.099
X-Spam-Level: 
X-Spam-Status: No, score=-102.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_PAYLESS=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zE7Alp67xsYr for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 08:36:34 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE5A11E8138 for <ietf@ietf.org>; Tue, 13 Aug 2013 08:36:34 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1V9Ge8-0002YH-1J; Tue, 13 Aug 2013 11:36:32 -0400
Date: Tue, 13 Aug 2013 11:36:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Leslie <john@jlc.net>, Dave Cridland <dave@cridland.net>
Subject: Re: Radical Solution for remote participants
Message-ID: <94BEA62A2E38325A5729EE49@JcK-HP8200.jck.com>
In-Reply-To: <20130813102459.GC68553@verdi>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com> <20130813102459.GC68553@verdi>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion 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: Tue, 13 Aug 2013 15:36:40 -0000

--On Tuesday, August 13, 2013 06:24 -0400 John Leslie
<john@jlc.net> wrote:

> Dave Cridland <dave@cridland.net> wrote:
>> On Tue, Aug 13, 2013 at 2:00 AM, Douglas Otis
>> <doug.mtview@gmail.com> wrote:
>> 
>>> 10) Establish a reasonable fee to facilitate remote
>>> participants who receive credit for their participation
>>>     equal to that of being local.
>> > 
>> 
>> I understand the rationale here, but I'm nervous about any
>> movement toward a kind of "pay-to-play standardization".
> 
>    Alas, that is what we have now. :^(
> 
>    There are a certain number of Working Groups where it's
> standard operating practice to ignore any single voice who
> doesn't attend an IETF week to defend his/her postings.

Thee is also a matter of equity even if one were to ignore the
costs to the community of enabling remote participation.   Some
fraction of the registration fee goes to support IETF overhead
activities that are not strictly associated with the costs of
particular meetings.  Although it would be a pity to turn us
into a community of hair-splitting amateur accountants [1], it
is inappropriate to expect those who participate in f2f meetings
to fully subsidize those who participate remotely.
 
>...
>   I don't always understand what Doug is asking for; but I
> suspect he is proposing to define a remote-participation where
> you get full opportunity to defend your ideas. This simply
> doesn't happen today.
 
>...
>> One option might be to give chairs some heavy influence on
>> remote burserships.
>...
>    That seems premature at this point: the likely costs aren't
> neatly correlated to number of remote participants; so it's
> not clear there's any reason to "support" an individual,
> rather than support the tools.

Worse, enabling WG Chairs to made de facto decisions about who
participates or not would have the appearance of enabling the
worst types of abuse.  It would be worse than figuring out how
to call on advocates of only one  position to speak.  Even if
those abuses never occurred, the optics and risk would be bad
news.[1[  

>...
>    Conceivably what we need is an automated tool to receive
> offers to (partially) subsidize the cost of a tool for a
> particular session.

Seems to me to be the wrong way to go.  I wouldn't want to
discourage Cisco's generosity.  And I think it is time to
declare the "Meetecho experiment" to have been concluded
successfully.  It can use some improvements and I hope it
continues to evolve (I could say the same thing about WebEx but
I'm less optimistic about evolution).  But it works well.  If we
want to use it, it is probably time to take it seriously.
Certainly that means having a available for all relevant
sessions, rather than constrained by the size of the current
team and their resources.  If that means training for operators
other than the core team, having to put in-room operators on a
non-volunteer basis, and/or IETF assumption of equipment
expenses, that would, IMO, be completely appropriate (of course,
that interacts with your comment about remote participation
having costs).

Similarly, "everyone pays but some pay less or zero and we set
up a procedure and/or bureaucracy to figure out who the latter
are" seems like a bad idea.

Simpler suggestion (this interacts with the "data collection"
thread):

(1) Remote participants are required [3] to register (remote
lurkers should continue to get a free ride for multiple reasons).

(2) The IAOC sets and announces a remote registrant fee based on
overhead expenses (those not associated with physical presence
at meetings).  Marginal costs of remote participation are
treated as overhead, not direct meeting expenses, because they
benefit the whole community.

(3) Remote participants pay that fee, or part of it, on a good
faith and conscience "what you can afford" basis with
information about what any particular person pays kept
confidential by the secretariat.  Again, we depend on good
faith. Financially, whatever we collect is better than what we
collect today.  Collecting some fee is better than none and
either too high a fee or the necessity to beg would discourage
registration or, worse, participation.

(4) If the IAOC or ISOC decide to conduct a diversity campaign
to help keep those fees low, more power to them, but such a
campaign (or its success) are not requirements for the above
model working.

best,
    john


[1] Possibly an improvement on a community of amateur lawyers,
perhaps not.

[2] Incidentally, one of the advantages of the otherwise clumsy
and efficient "mic lines" is that they make the queue clear to
everyone.

[3] We should recognize that we have no realistic enforcement
ability, at least unless non-registration is used to subvert IPR
rules. Any mechanism we might devise would not stop the truly
malicious.  This has to be a good faith requirement.



From rpelletier@isoc.org  Tue Aug 13 09:04:37 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C6121E8179; Tue, 13 Aug 2013 09:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Psk2Q-fn2b0; Tue, 13 Aug 2013 09:04:33 -0700 (PDT)
Received: from smtp78.ord1c.emailsrvr.com (smtp78.ord1c.emailsrvr.com [108.166.43.78]) by ietfa.amsl.com (Postfix) with ESMTP id 266E821F9ED4; Tue, 13 Aug 2013 09:04:32 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id A37FA1E81AB; Tue, 13 Aug 2013 12:04:30 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 1C73F1E829E;  Tue, 13 Aug 2013 12:04:30 -0400 (EDT)
Subject: Re: [rfc-i] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
Date: Tue, 13 Aug 2013 12:04:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DCE46403-65AC-4405-B8FB-14D378E4AFF6@isoc.org>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <CABSMSPWqR0OJbnzRZyONR==ScTqV=xV87DMvNbJ1Lg=7xf6TxA@mail.gmail.com>
To: Riccardo Bernardini <framefritti@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org, IETF Discussion <ietf@ietf.org>, iaoc@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 16:04:37 -0000

Riccardo

All of the DOC files are in the process of being replaced with PDF =
files.

I apologize for the inconvenience and angst this caused.

Ray


On Aug 13, 2013, at 3:36 AM, Riccardo Bernardini wrote:

> Is this the document with the proposed SOW?
>=20
>   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.doc
>=20
> I know that I should not this, but... I am a bit surprised
> (disappointed) in seeing a proprietary format used here.  I am not
> saying that you should not use the Office suite to write it, but you
> could convert it to PDF (better, PDF/A) before publishing it.
>=20
> Anyway, I use Linux, so I guess I will not be able to give my input =
about it.
>=20
> Best regards,
>=20
> Riccardo
>=20
>=20
> On Mon, Aug 12, 2013 at 11:54 PM, IETF Administrative Director
> <iad@ietf.org> wrote:
>> The RFC Series Editor (RSE) is proposing changes to the Statements of =
Work (SOW) for the RFC
>> Production Center (RPC) and the RFC Publisher.  The IAOC wants to =
receive community input prior to
>> negotiating the proposed changes with the contractor.  Community =
input will be discussed with the RSE
>> prior to negotiations and reviewed by the IAOC.
>>=20
>> In forwarding the proposed Statements of Work the RSE said:  "The =
changes seek to make the SoWs
>> more current [implementing RFC 6635] and specific, correcting the =
issues of "multiple masters"
>> directing the RPC and Publisher, as well as preparing the way for a =
more significant revision to the SoWs
>> when the RFC Format changes are operationalized.  The SoWs have also =
been reviewed and supported
>> by the RSOC [RFC Series Oversight Committee].  We consider the =
changes within the SoWs critical to the
>> clear function of the RPC and Publisher, but suggest that the changes =
do not imply a significant change
>> in responsibility for the RPC or Publisher."
>>=20
>> The proposed SOWs, the current SOWs and a diff file for each can be =
found here under Community
>> Review: <http://iaoc.ietf.org/rfps.html>
>>=20
>> We appreciate the community's input and look forward to hearing from =
you.
>>=20
>> Thanks
>>=20
>> Ray Pelletier
>> IAD
> _______________________________________________
> rfc-interest mailing list
> rfc-interest@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest


From johnl@iecc.com  Tue Aug 13 09:23:01 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D638511E8191 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 09:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kCpYvX+uk04 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 09:22: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 3C58E11E8184 for <ietf@ietf.org>; Tue, 13 Aug 2013 09:22:48 -0700 (PDT)
Received: (qmail 47021 invoked from network); 13 Aug 2013 16:22:47 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 13 Aug 2013 16:22:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520a5d57.xn--9vv.k1308; i=johnl@user.iecc.com; bh=mptXfuc8C4LYTjsNUube6IX//k5JMoNuWRQQRPyw/O0=; b=qKyJi2BfIxgp3pcBkq/4WeWq4q4PHM0p95H/DfseCWrAap6ZANKKd+K+IMB8TjhZcUnodk35TjCi0dPB28hggG49CBRNOsBx0bKxmeTSrPDf9eQuC+IR+yROIjbmzOH0BjagWwjauYxTKhPCaMV2F73/euW7OOFVpOKRAn+bgt+2obBMoIdCbXGsyLnbSTI9SRP87VgYBpKYr2p2dkMJ6f9qkha4DcRXFWNfP4hXxbHQpG+BW9tb53sIkcq4dMEX
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=520a5d57.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=mptXfuc8C4LYTjsNUube6IX//k5JMoNuWRQQRPyw/O0=; b=BHskfIyC3SmbCfqbTZU+FrlLTehs4AmSYPWgATKAxUnWPkqc6H7gZkn1N7qXRBSC1fCp1l9Cia+yD6dNbDEhXgh0zgURKZ+2hE0n3m49C6gFogwItOYukSVrguw04mMK1QrTKYRZrne7XXK3Gd5WR0ScB5Eh6YVW8veOLr+8BmFelJpbrKQaG0I+6yBvH0lBBcOg9aPmwNnRScXMDMzwKdpspDWTqt2ZENYu5dTqR0gRDkE27Tzyi7cO1mJZ09Ym
Date: 13 Aug 2013 16:22:25 -0000
Message-ID: <20130813162225.3087.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
In-Reply-To: <A92B1BA6-735C-4FCB-BE3F-315E5AAC30CE@nominum.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 16:23:02 -0000

>I wonder, though, if this document might have contained change bars that nobody but people who use MS
>Word would see.   Opening the document up in Preview on the Mac, it's just four or five pages of
>text, with no way to evaluate what changed.

It looks fine in OpenOffice.  Really.

I agree with your suggestion that rfcdiff would be nice, too.





From jari.arkko@piuha.net  Tue Aug 13 12:06:59 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8297121E819B; Tue, 13 Aug 2013 12:06: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 VCSG0zwi-Gpp; Tue, 13 Aug 2013 12:06:54 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id F0A6321E8182; Tue, 13 Aug 2013 12:06:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5474D2CC48; Tue, 13 Aug 2013 22:06:52 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNMQpgcndOya; Tue, 13 Aug 2013 22:06:51 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 56AE62CC5B; Tue, 13 Aug 2013 22:06:46 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-karp-crypto-key-table-08
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Date: Wed, 14 Aug 2013 03:06:45 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D641C7D-768F-4FB0-8DFC-D2C247E0F63A@piuha.net>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "Sam Hartman \(hartmans@painless-security.com\)" <hartmans@painless-security.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "stbryant@cisco.com" <stbryant@cisco.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 19:06:59 -0000

Thank you for your review, David. The Gen-ART reviews are important =
feedback for me to understand where I should look more closely.=20

In this case your review caused me to read the draft in detail, and I =
now have similar question as you did. I have raised a Discuss in my IESG =
ballot so that we can talk about those issues with the authors. In =
particular, it would be useful to discuss whether FCFS or some other =
assignment policy is most appropriate for the algorithm ID and KDF =
registries. I too thought Expert Review would have been a more natural =
fit. But I do not mind another policy, as long as we have a good reason =
for picking it. Secondly, I too was wondering what the relationship of =
this database is to the PAD.

Jari


From sm@elandsys.com  Tue Aug 13 12:08:59 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6AF421E819D for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 12:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.243
X-Spam-Level: 
X-Spam-Status: No, score=-102.243 tagged_above=-999 required=5 tests=[AWL=0.356, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwFywFIhZIfX for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 12:08: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 11AFA21E819C for <ietf@ietf.org>; Tue, 13 Aug 2013 12:08:59 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.133.219]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7DJ8kY1017984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Aug 2013 12:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376420937; bh=DnGMyrN0dLevErssngNo4BD9kQ4XPeO2JwERZme/+AE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TMtekIWaJbU7Ph4FZpjBTQ73dQEvdSjkqNAFH7z35g0rcyWJ5UjVVHjLJoj7Q+Tef 2leD0FaWGvqeAViSmS65S67ZVJGNinsONBOmQXe+0v9VQr6mkNlDJfuCRoa7eIn8cn 7JWcJ6+9WM1eUYY30DRMOvoAYw2iD2ael4dZKwoQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1376420937; i=@elandsys.com; bh=DnGMyrN0dLevErssngNo4BD9kQ4XPeO2JwERZme/+AE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gv+zXCGYZvzCf4R/L/vMdzInS4itoUivwFxTPc/4g78zS5u5BlIEec9HgoMoDUXGU z6NVP2IPVpEKM/v+EHF4b0ZEssMUZWV3Do/1xMBe17H8Mn++JcOiStbafCRmDeAOyr 52WltqhfZWdJGYNeXBW5CDza26CAdiQn2kJwjHxI=
Message-Id: <6.2.5.6.2.20130813113033.0b7632c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 13 Aug 2013 12:03:49 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
In-Reply-To: <52095E5D.5070802@ninebynine.org>
References: <52095E5D.5070802@ninebynine.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Graham Klyne <GK@ninebynine.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 19:08:59 -0000

At 15:14 12-08-2013, Graham Klyne wrote:
>But, in a personal capacity, not as designated reviewer, I have to 
>ask *why* this needs to be a URI.  As far as I can tell, it is 
>intended for use only in very constrained environments, where there 
>seems to be little value in having an identifier that can appear in 
>all the contexts where a URI may be recognized.

This is an individual comment.  I reviewed 
draft-petithuguenin-behave-turn-uris-05.  I wondered why a URI was 
needed given the limited use.  The same argument is applicable for 
draft-nandakumar-rtcweb-stun-uri-05.  There is running code for both 
drafts.  Both draft qualify for "DNP".  I would describe the 
proposals as trying to fit the solution within a URI instead of 
designing a URI scheme.  Both proposals sound like UNSAF.

Regards,
S. Moonesamy 


From sm@resistor.net  Tue Aug 13 13:13:41 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F9F11E81B7 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 13:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.81
X-Spam-Level: 
X-Spam-Status: No, score=-101.81 tagged_above=-999 required=5 tests=[AWL=0.789, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 934PwIUXxla9 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 13:13:39 -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 CA0FD11E81B4 for <ietf@ietf.org>; Tue, 13 Aug 2013 13:13:39 -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 r7DKDTlK023537; Tue, 13 Aug 2013 13:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376424816; bh=BcO3ukz7qh25tFbTnPc1YZUnOLOaS8v67UbiP3u8m7k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vKlj8Pgfo7oULq4QvLj5ZidKns6B1uCJy9fXC4oEKreBV9ZBadfAw1/I05tJ7MC+j qNAaXEX38OOSqjcvfdYBZbiCLkq7PsjPNLOZj66D1KbwN7n1Si0odXUJ0P7eBv7JgN WSuyGdYWG22McK67EWWgN0F/XSEWq/2Z9BbW7Dyw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376424816; i=@resistor.net; bh=BcO3ukz7qh25tFbTnPc1YZUnOLOaS8v67UbiP3u8m7k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3PllT0mejxY3J/ndcVlRgXk3Enge4gIXouQis3x7In9SKyJtemBsKhsMKFklzG0hj FvhJs3WOWYHgKw3BBWCf8uOShkc3Hmy9hoh5nBHFcNyhorI4+rzumstxV1OzC6Nh9M JxIIfMAGei3Y6jZXbGAZoQXC432zQ5J2mjHy5H6Y=
Message-Id: <6.2.5.6.2.20130813120911.0c59eca0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 13 Aug 2013 12:40:36 -0700
To: Ted Lemon <ted.lemon@nominum.com>, Hadriel Kaplan <hadriel.kaplan@oracle.com>, Eliot Lear <lear@cisco.com>
From: SM <sm@resistor.net>
Subject: What RFC 2026 says (was: Last Call: <draft-bormann-cbor-04.txt)
In-Reply-To: <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com> <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 20:13:41 -0000

At 09:25 10-08-2013, Ted Lemon wrote:
>Fair point.   RFC2026 does not in fact make the distinction I made.
>
>Here is what RFC 2026 says about proposed standards:
>
>    A Proposed Standard specification is generally stable, has resolved
>    known design choices, is believed to be well-understood, has received
>    significant community review, and appears to enjoy enough community
>    interest to be considered valuable.  However, further experience
>    might result in a change or even retraction of the specification
>    before it advances.

RFC 2026 also says that "Implementors should treat Proposed Standards 
as immature specifications".  Specifications are rarely 
retracted.  The community would not agree to retract an Experimental 
document.  Trying to do that with a Proposed Standard is madness. :-)

>Here is what it says about Informational documents:
>
>    An "Informational" specification is published for the general
>    information of the Internet community, and does not represent an
>    Internet community consensus or recommendation.  The Informational
>    designation is intended to provide for the timely publication of a
>    very broad range of responsible informational documents from many
>    sources, subject only to editorial considerations and to verification
>    that there has been adequate coordination with the standards process
>    (see section 4.2.3).

There is a bug in the above.  I prefer to avoid quoting RFC 2026 
nowadays as nobody really knows what RFC 2026; or to say it 
differently, the consensus is that there isn't any consensus about RFC 2026.

At 11:46 10-08-2013, Eliot Lear wrote:
>There is an architectural question hiding here: when we use CBOR in

Note that I did selective quoting.

There is a belief that someone would have thought about the 
architectural question.  After seeing such questions being ignored or 
seeing the blank stares in response to an architectural question I 
prefer not to even ask about that.  It is difficult to find the right 
answer to architectural questions.  One can only wonder how many 
people read RFC 1958 before writing a draft.

Padlipsky's Law states that:

   To The Technologically Naive, Change Equals Progress;
   To Vendors, Change Equals Profit.

I would read The Relevant Literature instead of RFC 2026.

Regards,
-sm 


From dhc@dcrocker.net  Tue Aug 13 13:35:10 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4667A21F9B5F for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 13:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LiGwo21o15ct for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 13:35:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC3721F9B5B for <ietf@ietf.org>; Tue, 13 Aug 2013 13:35:05 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7DKYx9g027891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Aug 2013 13:35:03 -0700
Message-ID: <520A9867.50206@dcrocker.net>
Date: Tue, 13 Aug 2013 13:34:47 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: What RFC 2026 says
References: <CAMm+Lwh2N+WhwWL599xjtES_jQQaubL4vGRJBt=L-2Nq8jd0mg@mail.gmail.com> <CE26746A.13BA5%joe@cursive.net> <CAMm+LwhX=h18vZvG4z_VUcSDVgfwavwEmY_FzDQigHrewa7Mew@mail.gmail.com> <CAC4RtVCCHHsOuqDCLMimp0Xvrbu9j8SA7rmojjHEyf0-E1OC9w@mail.gmail.com> <CAMm+LwhQD3G8cp=G+bO8SA0znhOA4esAaUx7O=Ln46L-FSDOwA@mail.gmail.com> <CALaySJJp1H=pNpN5-OppqSh0aV2fFkZexAeLa9ygh9uhSyMCmg@mail.gmail.com> <04FAF6EB-6184-4BEC-9872-B351D8DE2D0A@oracle.com> <C2D6F8A0-61FC-4688-9E94-D4F61305C258@nominum.com> <5DF42F1C-DDDB-41E5-A94F-3E18E6CCBB18@oracle.com> <3AAC80C8-1D73-4FC4-AF36-14E863304411@nominum.com> <6.2.5.6.2.20130813120911.0c59eca0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130813120911.0c59eca0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 13 Aug 2013 13:35:03 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 20:35:10 -0000

On 8/13/2013 12:40 PM, SM wrote:
>
> There is a bug in the above.  I prefer to avoid quoting RFC 2026
> nowadays as nobody really knows what RFC 2026; or to say it differently,
> the consensus is that there isn't any consensus about RFC 2026.


Either you are wrong or we have no stable, written criteria that 
determine assignment of our standards labels and our process really is 
quite ad hoc and therefore unreliable.

I hope you are wrong.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From yaronf.ietf@gmail.com  Tue Aug 13 14:14:05 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7ED521F9E22 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 14:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f+tWLqoWcmud for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 14:14:05 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0711721F9DBA for <ietf@ietf.org>; Tue, 13 Aug 2013 14:14:04 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id x12so7166677wgg.24 for <ietf@ietf.org>; Tue, 13 Aug 2013 14:14:04 -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=+lrVLOYj80XZcn0c1iDGIUBd0uijeWtDGSOeM/geweg=; b=hD5c7pjnSFmM10efZvZnRprp8RKHGbKuf5/+btukkO/xtVZ7Hjup6G8ioD6xIJUDZ9 J3HorIokTJ6hlYJyqC5DXmVrNNkeEeeI/WW+e/IHlx0nImfvQMR7ZMAapicshJzjgXgE CzwkKuAEPZAiewL9xZsmO/DePkOOsF65ZwOH0V+klzMoqvjlaQ3047nr5ImqXhxghOC4 6FpTtHPwr/qJ6drK5lGxgBkVOpNA0KSGONd+fRMk8RaMzkSdAfvkVm7sYgUeWRtTOl5w d30Dc+iMkTHthB9Uxc8cJtC66orj1AIKVaYdInlCMCXBlwlB6B+JLxJ21BoTH/SOErJY BZTQ==
X-Received: by 10.181.13.209 with SMTP id fa17mr3989453wid.12.1376428444113; Tue, 13 Aug 2013 14:14:04 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-180-208-107.red.bezeqint.net. [79.180.208.107]) by mx.google.com with ESMTPSA id jf2sm5717847wic.2.2013.08.13.14.14.02 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 13 Aug 2013 14:14:03 -0700 (PDT)
Message-ID: <520AA111.6080809@gmail.com>
Date: Wed, 14 Aug 2013 00:11:45 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 21:14:06 -0000

Dear authors,

sorry I'm submitting these comments after the end of the LC period. I 
hope they can still be of use.

- The document is well written and very clearly explained.
- I am still of the opinion that this document should better be 
published as Experimental RFC. Unlike TCP and UDP. But the comments 
below are unrelated to this discussion.
- The "diagnostic notation" can be used very effectively for things like 
configuration files, e.g. if an application already uses CBOR on the 
wire. Therefore I would suggest to formalize it a bit more, so that we 
also have interoperability at this level.
- And since this notation is not meant as a JSON extension, this is a 
good time to introduce comments (e.g. with an initial '#') into the 
notation.
- The positive vs. negative encoding means that the parser actually 
deals with 9-, 17-, 33- and 65-bit integers. I don't think this makes it 
easier to write parsers.
- Arrays are prefixed by the number of elements but not by their length 
in bytes. And elements need not be all of the same size. So you cannot 
skip the array without fully parsing every last element. IIRC this is a 
major disadvantage compared to ASN.1 encodings.
- A puzzling change from JSON, and one that probably complicates 
implementations quite a bit, is that a map's index can be of any type, 
not just a string. And this includes mixed index types for the same map.
- And similarly to arrays, you cannot skip a map element without deep 
parsing of the element.
- I think many of the tag values are too specific, and are best left to 
applications. For example, why should the format care if the app encodes 
a UTF-8 string in base64? OTOH, I would reserve a part of the tag space 
for "private" application-specific allocations.
- One tag value you may want to consider adding is "critical" in the 
security sense of the word, i.e., an application is required to fail if 
it does not understand the value (probably best applied to map keys).
- In the "diagnostic notation", I suggest to use symbolic values rather 
than integers for tags, e.g. TAG_URI.
- Sec. 3: because of the need for deep parsing mentioned above, a wire 
protocol cannot be extended by adding an element that uses a new data 
type (e.g. double precision FP) unless all potential recipients 
understand the type, even though they might not need to use the data 
element.
- Type restrictions for tags should be spelled out more clearly. E.g. in 
2.4.4.2, please clarify that when this tag applies to an array or map, 
*all* the items (and potentially items of nested arrays/maps?) MUST be 
byte strings. IMHO this just adds complexity and it's best to only tag 
the atomic item.
- Text such as this (for unknown simple types): "might issue a warning, 
might stop processing altogether, might handle the error by making the 
unknown value available to the application as such, or take some other 
type of action." is a security disaster waiting to happen. Also, it does 
not allow extensibility. Even though the encoding format is nominally 
extensible, in reality you cannot add stuff because the behavior of 
existing implementations when faced with it is unpredictable.
- Similarly for unknown tags (which IMHO should be ignored). Note that 
"unknown" includes currently specified tags, because implementations are 
not required to implement all current tags.
- Another security issue, for incomplete arrays: "a parser may 
completely fail the decoding, or substitute the missing data and data 
items using an decoder-specific convention. " This is a buffer overflow 
vulnerability by a different name.
- And by the way the entire Sec. 3 is non-normative. I suggest to use 
normative language for parser behavior, to ensure it is deterministic.

Thanks,
     Yaron


From hildjj@cursive.net  Tue Aug 13 15:21:02 2013
Return-Path: <hildjj@cursive.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 222E821F9BF1 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 15:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76UNudlqjjuy for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 15:21:01 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 85D9321F9BCA for <ietf@ietf.org>; Tue, 13 Aug 2013 15:20:58 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so8453874pbb.24 for <ietf@ietf.org>; Tue, 13 Aug 2013 15:20:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=user-agent:date:subject:from:to:message-id:thread-topic:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=8REi/6lrvOvQXUzBLHfdT+1HN4IDbefErHPxx4+q0cg=; b=lwVlPiAY+Ea+OJlT3UVUpPWnuohcMrxWlHcuvZxktdlXlj+LDJXh1yHRPkPzkzMQyU BlyrTvUcxA2WKO84k/7vFEhsOXk84H4E3vyQkJgAKzjix5asYG3pdKwYenN23RtFGi2P 0i7dC+YLfsh+JQVuf0JcWa6rR/2YeWOuA/0aY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=8REi/6lrvOvQXUzBLHfdT+1HN4IDbefErHPxx4+q0cg=; b=XLaKbrYw39G2PpHcBVwyLzQfhUCWk2QKvweP60+IpCsdzBTy+17qPITrwgjBY4CwxX otm8wK2+LE3AVm0SpG2TVKG+uSBEq4fZvU6rUEZrd4LkQglTZqJZiCsjNuXOIX93uzUL lqqZ5IfZcSwt9Y7oEhobtGhZOrSLXlMpbVLbYTeVUD5YVnHuMjBA+60SvWLEYSC3RLH3 spGCqQmTcfZ7sTt60guRUhECMcEp9jUelS5dFl/uZyFhRmtqy/ACFYNJt8zUnmzM3zSk qnaH8jhYoYZQLwf/pan3VzzGkDbN0Y70U49BbjQVEoAGBpw4dFmVoFk+z2V0NHgPsxSO Dgpw==
X-Gm-Message-State: ALoCoQmkmI4wQMemU8xUKrNDtZFcEAd9JkDmO+sznoCC8dCouByoWa7dX+/U+8RfBmAp0xsqdOxE
X-Received: by 10.68.98.1 with SMTP id ee1mr6573178pbb.65.1376432457041; Tue, 13 Aug 2013 15:20:57 -0700 (PDT)
Received: from [10.21.68.145] (128-107-239-234.cisco.com. [128.107.239.234]) by mx.google.com with ESMTPSA id oj6sm49146415pab.9.2013.08.13.15.20.52 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 13 Aug 2013 15:20:56 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 13 Aug 2013 16:20:45 -0600
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Joe Hildebrand <hildjj@cursive.net>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <CE300BA7.15704%joe@cursive.net>
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
In-Reply-To: <520AA111.6080809@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Aug 2013 22:21:02 -0000

(leaving a full response to the authors, and responding to a couple of
points I found interesting)

On 8/13/13 3:11 PM, "Yaron Sheffer" <yaronf.ietf@gmail.com> wrote:

>- Arrays are prefixed by the number of elements but not by their length
>in bytes. And elements need not be all of the same size. So you cannot
>skip the array without fully parsing every last element. IIRC this is a
>major disadvantage compared to ASN.1 encodings.

>- And similarly to arrays, you cannot skip a map element without deep
>parsing of the element.

One of the reasons why I like the CBOR tag applied to a byte stream is
that 
it can be used to skip parsing on entire sections (no matter their
underlying types) in processors that don't need to understand that section.

>I would reserve a part of the tag space
>for "private" application-specific allocations.

I like that.

>- One tag value you may want to consider adding is "critical" in the
>security sense of the word, i.e., an application is required to fail if
>it does not understand the value (probably best applied to map keys).

That's also an interesting idea.  If included, it would be best to add
this as soon as possible, and ensure that it gets added to the test
vectors, to avoid problems we've had in the past with inadequate
implementations of criticality.

>- In the "diagnostic notation", I suggest to use symbolic values rather
>than integers for tags, e.g. TAG_URI.

How would you deal with tags that your implementation doesn't understand,
then?

-- 
Joe Hildebrand





From stephen.nadas@ericsson.com  Tue Aug 13 15:28:19 2013
Return-Path: <stephen.nadas@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 D09F411E80D2; Tue, 13 Aug 2013 15:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cIe4-Kv+ZyJZ; Tue, 13 Aug 2013 15:28:11 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 8228621E816E; Tue, 13 Aug 2013 15:28:08 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-81-520ab2f716b9
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 13.E5.31362.7F2BA025; Wed, 14 Aug 2013 00:28:07 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Tue, 13 Aug 2013 18:28:06 -0400
From: Stephen Nadas <stephen.nadas@ericsson.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "rfc-dist@rfc-editor.org" <rfc-dist@rfc-editor.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6	Neighbor Discovery
Thread-Topic: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6	Neighbor Discovery
Thread-Index: AQHOmHMLv+csr4kx2UygNsGxX3IOGpmTt9wF
Date: Tue, 13 Aug 2013 22:28:05 +0000
Message-ID: <0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046A@eusaamb101.ericsson.se>
References: <20130813221321.AEA1AB1E003@rfc-editor.org>
In-Reply-To: <20130813221321.AEA1AB1E003@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046Aeusaamb101erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPlO73TVxBBvc61Sxu/Whkt7h3Zjqb xbON81ksXp59z2SxYuJRNoum/V/ZHNg8euQ9liz5yeTR0HaMNYA5issmJTUnsyy1SN8ugStj /rmb7AW9jhXnWm8yNjC2WnQxcnJICJhI9K/qZIewxSQu3FvP1sXIxSEkcJRRov/iZ2YIZzmj xJHuG4wgVWwCBhL/e5awgNgiAv2MEn03uEGKmAVmMkrM+/6QDSQhLJAs8W33KkaIohSJjUcO QjUYSSzr2c4EYrMIqEr0Hp3EDGLzCvhKbL99GcwWEjCXOLXlJFgvp4CFxJfDG1lBbEag876f WgPWyywgLnHryXwmiLMFJJbsOc8MYYtKvHz8jxWiJl9i/62PjBDzBSVOznzCMoFRZBaS9llI ymYhKYOI60ncmDqFDcLWlli28DUzhK0rMePfIRZk8QWM7KsYOUqLU8ty040MNzEC4+2YBJvj DsYFnywPMUpzsCiJ827QOxMoJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgXHpbPfz0cfDqw4e 0j4icf7L7qoAjw3brlwVXzMnVCFu57SjbWGXXryLZmVgq1Jdcm7Cd8+Lt3Jlleoufq/L4T9f aBT9b/O7aZfjratKNRcJvSzj/MSqezXu9tFmwWvmYRP38Z/i47pUa/r4wJqCjHVKsQZrTpvc XmBzw8Z4h/mnCQ63uwPPKf1VYinOSDTUYi4qTgQA9jWvgoUCAAA=
Cc: "drafts-update-ref@iana.org" <drafts-update-ref@iana.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "rfc-editor@rfc-editor.org" <rfc-editor@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: Tue, 13 Aug 2013 22:28:19 -0000

--_000_0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046Aeusaamb101erics_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ok. I assume this should be for FT? Or just something to get started?
Steve

-----Original Message-----
From: rfc-editor@rfc-editor.org [rfc-editor@rfc-editor.org]
Received: Tuesday, 13 Aug 2013, 18:18
To: ietf-announce@ietf.org [ietf-announce@ietf.org]; rfc-dist@rfc-editor.or=
g [rfc-dist@rfc-editor.org]
CC: drafts-update-ref@iana.org [drafts-update-ref@iana.org]; ipv6@ietf.org =
[ipv6@ietf.org]; rfc-editor@rfc-editor.org [rfc-editor@rfc-editor.org]
Subject: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 =
Neighbor Discovery

A new Request for Comments is now available in online RFC libraries.


        RFC 6980

        Title:      Security Implications of IPv6 Fragmentation
                    with IPv6 Neighbor Discovery
        Author:     F. Gont
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2013
        Mailbox:    fgont@si6networks.com
        Pages:      10
        Characters: 20850
        Updates:    RFC 3971, RFC 4861

        I-D Tag:    draft-ietf-6man-nd-extension-headers-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6980.txt

This document analyzes the security implications of employing IPv6
fragmentation with Neighbor Discovery (ND) messages.  It updates RFC
4861 such that use of the IPv6 Fragmentation Header is forbidden in
all Neighbor Discovery messages, thus allowing for simple and
effective countermeasures for Neighbor Discovery attacks.  Finally,
it discusses the security implications of using IPv6 fragmentation
with SEcure Neighbor Discovery (SEND) and formally updates RFC 3971
to provide advice regarding how the aforementioned security
implications can be mitigated.

This document is a product of the IPv6 Maintenance Working Group of the IET=
F.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_sear=
ch.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

--_000_0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046Aeusaamb101erics_
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 Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11p=
t; color:black">
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11=
pt; color:black">Ok. I assume this should be for FT? Or just something to g=
et started?
<br>
Steve<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> rfc-editor@rfc-editor.org [rfc-editor@rfc-editor.org]<br>
<b>Received:</b> Tuesday, 13 Aug 2013, 18:18<br>
<b>To:</b> ietf-announce@ietf.org [ietf-announce@ietf.org]; rfc-dist@rfc-ed=
itor.org [rfc-dist@rfc-editor.org]<br>
<b>CC:</b> drafts-update-ref@iana.org [drafts-update-ref@iana.org]; ipv6@ie=
tf.org [ipv6@ietf.org]; rfc-editor@rfc-editor.org [rfc-editor@rfc-editor.or=
g]<br>
<b>Subject:</b> RFC 6980 on Security Implications of IPv6 Fragmentation wit=
h IPv6 Neighbor Discovery<br>
<br>
</span></span></div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">A new Request for Comments is now available in onl=
ine RFC libraries.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RFC 6980<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title:&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Security Implications of IPv6 Fragmentation <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with IPv6 Neighbor Discovery <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author:&nbsp;&nbsp;&nbsp;&nbsp; =
F. Gont<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Status:&nbsp;&nbsp;&nbsp;&nbsp; =
Standards Track<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Stream:&nbsp;&nbsp;&nbsp;&nbsp; =
IETF<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date:&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; August 2013<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mailbox:&nbsp;&nbsp;&nbsp; fgont=
@si6networks.com<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages:&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; 10<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Characters: 20850<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Updates:&nbsp;&nbsp;&nbsp; RFC 3=
971, RFC 4861<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I-D Tag:&nbsp;&nbsp;&nbsp; draft=
-ietf-6man-nd-extension-headers-05.txt<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; URL:&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; <a href=3D"http://www.rfc-editor.org/rfc/rfc6980.txt">http:/=
/www.rfc-editor.org/rfc/rfc6980.txt</a><br>
<br>
This document analyzes the security implications of employing IPv6<br>
fragmentation with Neighbor Discovery (ND) messages.&nbsp; It updates RFC<b=
r>
4861 such that use of the IPv6 Fragmentation Header is forbidden in<br>
all Neighbor Discovery messages, thus allowing for simple and<br>
effective countermeasures for Neighbor Discovery attacks.&nbsp; Finally,<br=
>
it discusses the security implications of using IPv6 fragmentation<br>
with SEcure Neighbor Discovery (SEND) and formally updates RFC 3971<br>
to provide advice regarding how the aforementioned security<br>
implications can be mitigated.<br>
<br>
This document is a product of the IPv6 Maintenance Working Group of the IET=
F.<br>
<br>
This is now a Proposed Standard.<br>
<br>
STANDARDS TRACK: This document specifies an Internet standards track<br>
protocol for the Internet community,and requests discussion and suggestions=
<br>
for improvements.&nbsp; Please refer to the current edition of the Internet=
<br>
Official Protocol Standards (STD 1) for the standardization state and<br>
status of this protocol.&nbsp; Distribution of this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
&nbsp; <a href=3D"http://www.ietf.org/mailman/listinfo/ietf-announce">http:=
//www.ietf.org/mailman/listinfo/ietf-announce</a><br>
&nbsp; <a href=3D"http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist">=
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href=3D"http://www.rfc-editor.org/sear=
ch/rfc_search.php">
http://www.rfc-editor.org/search/rfc_search.php</a><br>
For downloading RFCs, see <a href=3D"http://www.rfc-editor.org/rfc.html">ht=
tp://www.rfc-editor.org/rfc.html</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to rfc-editor@rfc-editor.org.&nbsp; Unles=
s<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
</div>
</span></font>
</body>
</html>

--_000_0BDF8C6F58AEFA45A013C71E4ADEB4AF02F2046Aeusaamb101erics_--

From paul.hoffman@vpnc.org  Tue Aug 13 16:12:34 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE22621E805A for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 16:12:34 -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 f4Ug+y-p0ELo for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 16:12:33 -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 BEA7F21E8186 for <ietf@ietf.org>; Tue, 13 Aug 2013 16:12:33 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r7DNCTpK097449 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Aug 2013 16:12:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <520AA111.6080809@gmail.com>
Date: Tue, 13 Aug 2013 16:12:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E8CFF40-7B40-4F4B-868D-28F7490CDA3B@vpnc.org>
References: <520AA111.6080809@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
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: Tue, 13 Aug 2013 23:12:34 -0000

On Aug 13, 2013, at 2:11 PM, Yaron Sheffer <yaronf.ietf@gmail.com> =
wrote:

> sorry I'm submitting these comments after the end of the LC period. I =
hope they can still be of use.

No problem, and the are. Some answers below.

> - The "diagnostic notation" can be used very effectively for things =
like configuration files, e.g. if an application already uses CBOR on =
the wire. Therefore I would suggest to formalize it a bit more, so that =
we also have interoperability at this level.

Based on other things we heard, we went sort of in the other direction =
in the next draft: saying that an implementer might consider a different =
notation for config files, such as YAML.

> - And since this notation is not meant as a JSON extension, this is a =
good time to introduce comments (e.g. with an initial '#') into the =
notation.

Comments are not needed in diagnostics. :-)

> - The positive vs. negative encoding means that the parser actually =
deals with 9-, 17-, 33- and 65-bit integers. I don't think this makes it =
easier to write parsers.

If you primarily think about signed integers, that may be one way of =
viewing it.  CBOR is primarily addressing unsigned integers.  Negative =
integers are clearly separated out, and indeed do require watching the =
sign bit.  There is no way to handle this that is painless for all =
applications.

Multiple people have implemented parsers in multiple languages =
(JavaScript, Python, Ruby, ...), and we found it was pretty easy, and =
very little code.

> - Arrays are prefixed by the number of elements but not by their =
length in bytes. And elements need not be all of the same size. So you =
cannot skip the array without fully parsing every last element. IIRC =
this is a major disadvantage compared to ASN.1 encodings.

Correct. Counting items and not bytes is indeed a fundamental design =
decision in CBOR that has advantages and disadvantages. We believe the =
advantages outweigh the disadvantages.

In specific here, we are not assuming that "skip over an array/map" is a =
common desire for a decoder. Forcing an encoder to marshall all the =
bytes before it could start emitting an array/map causes overhead for =
the encoder that is avoided if it just knows the number of elements it =
will emit.

> - A puzzling change from JSON, and one that probably complicates =
implementations quite a bit, is that a map's index can be of any type, =
not just a string. And this includes mixed index types for the same map.

We have looked at this, and do not think that it complicates many =
implementations. It does not complicate encoders at all. It does not =
complicate decoders, even those that are looking for duplicate keys =
(which will be an error). It only complicates decoders that are also =
sorting the keys. We assume that the latter does not need to happen in =
the parser, but in the application that needs the keys sorted by =
semantics it knows about.

> - And similarly to arrays, you cannot skip a map element without deep =
parsing of the element.

Ditto from above.

> - I think many of the tag values are too specific, and are best left =
to applications. For example, why should the format care if the app =
encodes a UTF-8 string in base64?

Because a generic parser could then do the Base64 decoding. This will =
always be an iffy space: CBOR will either force too much knowledge on =
the application, or it will do too much. We picked somewhere on that =
continuum, knowing that it will make no one happy. FWIW, Carsten and I =
disagreed with each other on this to varying degrees during the =
different drafts, and different people proposed different places on the =
continuum where CBOR "should" be.

> OTOH, I would reserve a part of the tag space for "private" =
application-specific allocations.

One of the always-repeating IETF rat-hole. We didn't go there, nor will =
we say you're wrong for wanting to go there. The first-come-first-served =
space should enable such allocations. If you just want to play around in =
the lab, the range up to 18446744073709551615 should allow reliably =
avoiding collisions.

> - One tag value you may want to consider adding is "critical" in the =
security sense of the word, i.e., an application is required to fail if =
it does not understand the value (probably best applied to map keys).

That is a lovely proposal for an extension from a developer who is using =
CBOR in such an environment so that they can write the three or four =
paragraphs that would be needed to explain that in detail.

> - In the "diagnostic notation", I suggest to use symbolic values =
rather than integers for tags, e.g. TAG_URI.

You seem to like the diagnostic notation more than we do. :-) If CBOR =
becomes at all popular, having a second, more thought-out diagnostic =
notation seems like a reasonable project.

> - Sec. 3: because of the need for deep parsing mentioned above, a wire =
protocol cannot be extended by adding an element that uses a new data =
type (e.g. double precision FP) unless all potential recipients =
understand the type, even though they might not need to use the data =
element.

Correct. We are adding more text to make that clear.

> - Type restrictions for tags should be spelled out more clearly. E.g. =
in 2.4.4.2, please clarify that when this tag applies to an array or =
map, *all* the items (and potentially items of nested arrays/maps?) MUST =
be byte strings.

A CBOR protocol can choose to do just that.

> IMHO this just adds complexity and it's best to only tag the atomic =
item.

Noted. Some of the tags imply more restrictions that we would have =
hoped, but if it isn't specified in the tag, the complexity just gets =
pushed to all the applications.

> - Text such as this (for unknown simple types): "might issue a =
warning, might stop processing altogether, might handle the error by =
making the unknown value available to the application as such, or take =
some other type of action." is a security disaster waiting to happen. =
Also, it does not allow extensibility. Even though the encoding format =
is nominally extensible, in reality you cannot add stuff because the =
behavior of existing implementations when faced with it is =
unpredictable.

You (and the other folks who made similar comments about the looseness =
in this section) should be much happier with the next draft.

> - Similarly for unknown tags (which IMHO should be ignored). Note that =
"unknown" includes currently specified tags, because implementations are =
not required to implement all current tags.

Not sure what you mean here.

> - Another security issue, for incomplete arrays: "a parser may =
completely fail the decoding, or substitute the missing data and data =
items using an decoder-specific convention. " This is a buffer overflow =
vulnerability by a different name.

How is that different than, say JSON, where the decoder might never see =
the final "}" or "]"?

> - And by the way the entire Sec. 3 is non-normative. I suggest to use =
normative language for parser behavior, to ensure it is deterministic.

We think we have done so in the next version.

--Paul Hoffman


From randy_presuhn@mindspring.com  Tue Aug 13 18:53:52 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4675921E8098 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 18:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJ7yHZISRUZ6 for <ietf@ietfa.amsl.com>; Tue, 13 Aug 2013 18:53:46 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 208B721E8087 for <ietf@ietf.org>; Tue, 13 Aug 2013 18:53:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=e2u8RdPnXFK+Sx6nbCHyiylglWa/AzT/NZJfCXqV/Vv8aCotPhCtHI7tcqp9fKTw; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.48] (helo=elwamui-rustique.atl.sa.earthlink.net) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1V9QHJ-0007Fq-U7; Tue, 13 Aug 2013 21:53:37 -0400
Received: from 99.23.160.142 by webmail.earthlink.net with HTTP; Tue, 13 Aug 2013 21:53:37 -0400
Message-ID: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net>
Date: Tue, 13 Aug 2013 18:53:37 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Subject: re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888ba196d48fc2e3f08daee38461ca3a98075288fdf15b5a816350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.48
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 01:53:52 -0000

Hi -

>From: Yaron Sheffer <yaronf.ietf@gmail.com>
>Sent: Aug 13, 2013 2:11 PM
>To: IETF Discussion Mailing List <ietf@ietf.org>
>Subject: re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object	Representation (CBOR)) to Proposed Standard
...
>- The "diagnostic notation" can be used very effectively for things like 
>configuration files, e.g. if an application already uses CBOR on the 
>wire. Therefore I would suggest to formalize it a bit more, so that we 
>also have interoperability at this level.

Do you envision it as an encoding for Netconf?

Randy

From cabo@tzi.org  Wed Aug 14 00:12:59 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F34FD11E8127; Wed, 14 Aug 2013 00:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYsmpFnLSeDA; Wed, 14 Aug 2013 00:12:54 -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 01C0711E80C5; Wed, 14 Aug 2013 00:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7E7CpNC011437; Wed, 14 Aug 2013 09:12:51 +0200 (CEST)
Received: from [192.168.217.105] (p54890CE5.dip0.t-ipconnect.de [84.137.12.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id B698D752; Wed, 14 Aug 2013 09:12:50 +0200 (CEST)
Subject: cbor-05 (was: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard)
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20130716195803.9658.64560.idtracker@ietfa.amsl.com>
Date: Wed, 14 Aug 2013 09:12:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB7E2042-9C40-48DB-8D9C-FAE41931361D@tzi.org>
References: <20130716195803.9658.64560.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1508)
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 07:12:59 -0000

This was a rather productive IETF Last Call!
Thank you all for the many comments.

Paul and I have taken your comments and believe that we have
incorporated the ones that we said we would.

The -05 has just been published:

    http://tools.ietf.org/html/draft-bormann-cbor-05

... and there are lots of diffs; see

    http://tools.ietf.org/rfcdiff?url2=3Ddraft-bormann-cbor-05

We would particularly like review of the changes we made in section 3,
where we tightened up a lot of the "might" language for parsers. We
also clarified that what we were too-loosely calling a "parser" was
actually a "decoder" that has two sub-parts: a parser (grammar only)
and semantic processor (checking for validity). We hope that this
major edit alleviates most concerns, but further comments are
certainly appreciated.

Gr=FC=DFe, Carsten


From yaronf.ietf@gmail.com  Wed Aug 14 00:31:19 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F5B611E8133 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 00:31: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 rJg0Ela-V9dU for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 00:31:18 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF5611E8127 for <ietf@ietf.org>; Wed, 14 Aug 2013 00:31:13 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id j13so3387106wgh.3 for <ietf@ietf.org>; Wed, 14 Aug 2013 00:31:13 -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=pE/awfqSMIj1+95oQVpr+6zb7YMl8wjbStsi3hjqTWQ=; b=SGOOgMT8j9DtHLI8arhIr9SZPfF2UBQ5KIlgEy0R1cGBhm141pl9Dj4t6pTfkLn55f CHhi//h8goSrP5dfGwRDy+jmzd5eIknCNz83i3VTGl+30huNARJWltTlLa/sWY3/kv+4 MlfO6BMaCDMh4kb38hD15i+3XiFPeHZO687ca3Ch8/8aTK10CbUVNPciNio2x02OL7/B yg0HCRLYltCBplsUzYgXuFcEiMcyUjOGyOkXs8o0rAB+UIX0P7VHYvTL/zEOr4OcPLRv C0mBCRCHJr8/vMaSdZ2HKH6b0P1czQryBcO+Xr6AyD3Gabo6bWyMA49IZlpxcFJBLYqH OXZQ==
X-Received: by 10.180.84.196 with SMTP id b4mr5315283wiz.19.1376465472086; Wed, 14 Aug 2013 00:31:12 -0700 (PDT)
Received: from [10.0.0.142] (46-116-127-98.bb.netvision.net.il. [46.116.127.98]) by mx.google.com with ESMTPSA id e7sm1061573wiy.4.2013.08.14.00.31.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 14 Aug 2013 00:31:11 -0700 (PDT)
Message-ID: <520B323D.7090702@gmail.com>
Date: Wed, 14 Aug 2013 10:31:09 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net>
In-Reply-To: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 14 Aug 2013 07:31:19 -0000

Hi Randy,

I prefer to leave this question to people who know something about 
Netconf, i.e. not me.

But let me just say that, based on my thoroughly extensive 5-min. 
research, YANG seems to be incompatible with CBOR.

Thanks,
	Yaron

On 2013-08-14 04:53, Randy Presuhn wrote:
> Hi -
>
>> From: Yaron Sheffer <yaronf.ietf@gmail.com>
>> Sent: Aug 13, 2013 2:11 PM
>> To: IETF Discussion Mailing List <ietf@ietf.org>
>> Subject: re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object	Representation (CBOR)) to Proposed Standard
> ...
>> - The "diagnostic notation" can be used very effectively for things like
>> configuration files, e.g. if an application already uses CBOR on the
>> wire. Therefore I would suggest to formalize it a bit more, so that we
>> also have interoperability at this level.
>
> Do you envision it as an encoding for Netconf?
>
> Randy
>

From daedulus@btconnect.com  Wed Aug 14 01:17:00 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CED421E809A for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 01:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mypWFKj+KSs7 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 01:16:48 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe003.messaging.microsoft.com [216.32.180.186]) by ietfa.amsl.com (Postfix) with ESMTP id 0468921E808D for <ietf@ietf.org>; Wed, 14 Aug 2013 01:16:46 -0700 (PDT)
Received: from mail16-co1-R.bigfish.com (10.243.78.247) by CO1EHSOBE031.bigfish.com (10.243.66.96) with Microsoft SMTP Server id 14.1.225.22; Wed, 14 Aug 2013 08:16:46 +0000
Received: from mail16-co1 (localhost [127.0.0.1])	by mail16-co1-R.bigfish.com (Postfix) with ESMTP id 562C36C0250; Wed, 14 Aug 2013 08:16:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.69; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -15
X-BigFish: PS-15(zz98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail16-co1 (localhost.localdomain [127.0.0.1]) by mail16-co1 (MessageSwitch) id 1376468203685253_10673; Wed, 14 Aug 2013 08:16:43 +0000 (UTC)
Received: from CO1EHSMHS027.bigfish.com (unknown [10.243.78.225])	by mail16-co1.bigfish.com (Postfix) with ESMTP id A3171AC0047; Wed, 14 Aug 2013 08:16:43 +0000 (UTC)
Received: from AMXPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.69) by CO1EHSMHS027.bigfish.com (10.243.66.37) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 14 Aug 2013 08:16:43 +0000
Received: from DBXPRD0210HT002.eurprd02.prod.outlook.com (157.56.253.181) by pod51017.outlook.com (10.242.9.162) with Microsoft SMTP Server (TLS) id 14.16.347.3; Wed, 14 Aug 2013 08:16:40 +0000
Message-ID: <003f01ce98c6$8835d920$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Ted Lemon <ted.lemon@nominum.com>, John Levine <johnl@taugh.com>
References: <20130813135100.2250.qmail@joyce.lan> <5ECCE03E-BD02-437C-B021-72DC0C459385@nominum.com>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFCPublisher
Date: Wed, 14 Aug 2013 09:16:02 +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.253.181]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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: Wed, 14 Aug 2013 08:17:01 -0000

----- Original Message -----
From: "Ted Lemon" <ted.lemon@nominum.com>
To: "John Levine" <johnl@taugh.com>
Cc: "IETF Discussion Mailing List" <ietf@ietf.org>
Sent: Tuesday, August 13, 2013 4:03 PM
> On Aug 13, 2013, at 9:51 AM, John Levine <johnl@taugh.com> wrote:
> > There's no great way
> > to send around a redlined document and I'd say that Word formats are
> > currently the least bad.
>
> rfcdiff does really nicely, actually.

And HTML can also be used to produce a genuine red-lined document (but I
expect that you know that:-)

Sharon Chisholm used to do it for Netconf as with
draft-ietf-netconf-notification-09.txt.prerelease2

<strike><font color='red'>January</font></strike>
is the operative tag.

Tom Petch




From randy@psg.com  Wed Aug 14 04:40:11 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9259211E8131 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 04:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level: 
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[AWL=0.229,  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 8fXL0wcWnWUl for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 04:40:06 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) by ietfa.amsl.com (Postfix) with ESMTP id A648411E8155 for <ietf@ietf.org>; Wed, 14 Aug 2013 04:40:03 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1V9ZQn-0006mP-TM; Wed, 14 Aug 2013 11:40:02 +0000
Date: Wed, 14 Aug 2013 20:40:00 +0900
Message-ID: <m2mwoko60f.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object	Representation (CBOR)) to Proposed Standard
In-Reply-To: <520B323D.7090702@gmail.com>
References: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net> <520B323D.7090702@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: Wed, 14 Aug 2013 11:40:11 -0000

> YANG seems to be incompatible with CBOR.

so what does that say about yang, yang's suitability for netconf, cbor,
and cbor's suitability?

randy

From cabo@tzi.org  Wed Aug 14 06:07:30 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E706521F8F67 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 06:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DThR2uY8bzRB for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 06:07: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 0E24B11E80EE for <ietf@ietf.org>; Wed, 14 Aug 2013 06:07:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7ED7ENp002140; Wed, 14 Aug 2013 15:07:14 +0200 (CEST)
Received: from [192.168.217.105] (p54890CE5.dip0.t-ipconnect.de [84.137.12.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8585FA80; Wed, 14 Aug 2013 15:07:14 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object	Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <m2mwoko60f.wl%randy@psg.com>
Date: Wed, 14 Aug 2013 15:07:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D52BE231-28E3-4DE6-BE66-8D0E85691FC6@tzi.org>
References: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net> <520B323D.7090702@gmail.com> <m2mwoko60f.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1508)
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 13:07:31 -0000

On Aug 14, 2013, at 13:40, Randy Bush <randy@psg.com> wrote:

>> YANG seems to be incompatible with CBOR.
>=20
> so what does that say about yang, yang's suitability for netconf, =
cbor,
> and cbor's suitability?

Good question.  I'm not sure the jury is even out on that yet.

Yaron reminded me that netconf is using XPath for various purposes, so a =
CBOR rendition of netconf would need to do the same that you would need =
for doing netconf with JSON: either replace XPath with something else =
(indeed causing some incompatibility), or explain how to use XPath with =
the CBOR/JSON translation of the YANG model (which might be =
interesting).

CBOR certainly has no trouble carrying around the data described by a =
YANG model.
(Indeed, CBOR's decimal fractions were inspired by YANG's.)
But then, I don't have an opinion whether adding a binary object =
representation to the netconf ecosystem is on the agenda.

Gr=FC=DFe, Carsten


From andy@yumaworks.com  Wed Aug 14 08:18:31 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7AA811E8175 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 08:18:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level: 
X-Spam-Status: No, score=-2.077 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M93HaISTnZWO for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 08:18:26 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3790221E80C6 for <ietf@ietf.org>; Wed, 14 Aug 2013 08:18:21 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so6484420pdj.31 for <ietf@ietf.org>; Wed, 14 Aug 2013 08:18:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QLsX4453s+n0L/pLAdQs1WFQJLXYhzEm6gCH0fr9MGI=; b=fWIjvWptLr2ViZDvyVEA5Rz48KZEHPcqFEFCZnIIQPcezSFV1EAQFHvzqmlwFS6Ra9 6ebj/1vKbWOPdFdXi5K/N72eCikTboWIKTD4I/ZcQY1dnsjlA/bc1U4kwTAkgE1PwIqE pHwgQf0vCD0xopnZmgCbl0EjW+mXSdAoMg8Jmj2MKyq7D1EuVyvU5aMeEFcGpMhspMLS HjLPmwsOWUFlPLsJP3N7KmWEie0d7osQl4Xg/R+ulQ/CZBRU/MhU2ftx7yQc3oOVOnW7 3UGDNmbnvZSJAghAKQfyiHzcCubWphodLfNr4EyPw+gScvvNW73VUmsfpVMkk1k/XPU4 6Veg==
X-Gm-Message-State: ALoCoQmW0M7eGtwG4//WB00xNU2RDsFoXLMCXGvnG9Mujcy0ZHhma5dInFM3ixy8a2eifUo7UjP6
MIME-Version: 1.0
X-Received: by 10.67.4.136 with SMTP id ce8mr1848460pad.158.1376493501636; Wed, 14 Aug 2013 08:18:21 -0700 (PDT)
Received: by 10.70.41.162 with HTTP; Wed, 14 Aug 2013 08:18:21 -0700 (PDT)
In-Reply-To: <520B323D.7090702@gmail.com>
References: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net> <520B323D.7090702@gmail.com>
Date: Wed, 14 Aug 2013 08:18:21 -0700
Message-ID: <CABCOCHT4dEaX+ZnLd-WX9_J61GXxMfkpDjkwD_P97-aZGtUWDA@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Andy Bierman <andy@yumaworks.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, 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: Wed, 14 Aug 2013 15:18:32 -0000

On Wed, Aug 14, 2013 at 12:31 AM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
> Hi Randy,
>
> I prefer to leave this question to people who know something about Netconf,
> i.e. not me.
>
> But let me just say that, based on my thoroughly extensive 5-min. research,
> YANG seems to be incompatible with CBOR.
>

Can you be more specific?
What is incompatible about YANG?

> Thanks,
>         Yaron
>

Andy


> On 2013-08-14 04:53, Randy Presuhn wrote:
>>
>> Hi -
>>
>>> From: Yaron Sheffer <yaronf.ietf@gmail.com>
>>> Sent: Aug 13, 2013 2:11 PM
>>> To: IETF Discussion Mailing List <ietf@ietf.org>
>>> Subject: re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary
>>> Object      Representation (CBOR)) to Proposed Standard
>>
>> ...
>>>
>>> - The "diagnostic notation" can be used very effectively for things like
>>> configuration files, e.g. if an application already uses CBOR on the
>>> wire. Therefore I would suggest to formalize it a bit more, so that we
>>> also have interoperability at this level.
>>
>>
>> Do you envision it as an encoding for Netconf?
>>
>> Randy
>>
>

From dhc@dcrocker.net  Wed Aug 14 08:24:11 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5E0011E81DD for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 08:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 AbQEaCerkxZB for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 08:23:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4584F11E8186 for <ietf@ietf.org>; Wed, 14 Aug 2013 08:23:57 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7EFNpgW016410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Aug 2013 08:23:54 -0700
Message-ID: <520BA0FA.6000406@dcrocker.net>
Date: Wed, 14 Aug 2013 08:23:38 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Hildebrand <hildjj@cursive.net>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <CE300BA7.15704%joe@cursive.net>
In-Reply-To: <CE300BA7.15704%joe@cursive.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 14 Aug 2013 08:23:54 -0700 (PDT)
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 15:24:15 -0000

On 8/13/2013 3:20 PM, Joe Hildebrand wrote:
> One of the reasons why I like the CBOR tag applied to a byte stream is
> that
> it can be used to skip parsing on entire sections (no matter their
> underlying types) in processors that don't need to understand that section.


This is an example of the core reason that having a "one true standard" 
is not appropriate for many topics:  design choices optimize along 
particular axes, giving particular optimizations, typically at the 
expense of others.  Different operating context benefit from different 
optimizations.

It makes sense for a specification to document its tradeoffs; it often 
does not make sense to choose only one such specification for use in all 
scenarios.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From yaronf.ietf@gmail.com  Wed Aug 14 08:45:09 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9432521F9BAB for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 08:45:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4fmPuJbFwC9 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 08:45:08 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 6C88721F9DB2 for <ietf@ietf.org>; Wed, 14 Aug 2013 08:44:55 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so7791883wes.5 for <ietf@ietf.org>; Wed, 14 Aug 2013 08:44: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=45EGumCQG7T3qYS7YspHVe5NXPGIzJ0a/t8lFuTzuzA=; b=x/UbXJLm7/+UJVQs279gu64qs+VdmPZKg1BtKSdaYhDpzlhJ6g16Jdjfzorlr+Sb44 AR2AzJ+78POSLuqfGzRwlX73y1JMbpfq1ZpSXb+qRqMNDJo0Yr0IXwPZtrorlW8uhdWr N7arTqz/Lr7VwMcmrakUknQHcbiZtBFU9A5/rYS7I6WiFf0v0VKeLRYXUVwBneWWKs/4 d3QzoRsn6Gu/YC9nw2LvV0VRMcxuAj0v5tiysavIihCbmqtZLZnXJBGz5WIqH/62y33C Hf4aD3Tq96bgCuJUbTgk1H13fYJC9YQcNJ9Tz0ENP53krfWhhXor2d7w9MQKUOH9yWrW /qug==
X-Received: by 10.194.220.103 with SMTP id pv7mr7145338wjc.14.1376495094428; Wed, 14 Aug 2013 08:44:54 -0700 (PDT)
Received: from [10.0.0.140] (46-116-127-98.bb.netvision.net.il. [46.116.127.98]) by mx.google.com with ESMTPSA id a4sm3771671wik.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 14 Aug 2013 08:44:53 -0700 (PDT)
Message-ID: <520BA5F3.3020200@gmail.com>
Date: Wed, 14 Aug 2013 18:44:51 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net> <520B323D.7090702@gmail.com> <CABCOCHT4dEaX+ZnLd-WX9_J61GXxMfkpDjkwD_P97-aZGtUWDA@mail.gmail.com>
In-Reply-To: <CABCOCHT4dEaX+ZnLd-WX9_J61GXxMfkpDjkwD_P97-aZGtUWDA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, 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: Wed, 14 Aug 2013 15:45:10 -0000

Hi Andy,

Please see Carsten's mail on this subject.

Thanks,
	Yaron

On 2013-08-14 18:18, Andy Bierman wrote:
> On Wed, Aug 14, 2013 at 12:31 AM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
>> Hi Randy,
>>
>> I prefer to leave this question to people who know something about Netconf,
>> i.e. not me.
>>
>> But let me just say that, based on my thoroughly extensive 5-min. research,
>> YANG seems to be incompatible with CBOR.
>>
>
> Can you be more specific?
> What is incompatible about YANG?
>
>> Thanks,
>>          Yaron
>>
>
> Andy
>
>
>> On 2013-08-14 04:53, Randy Presuhn wrote:
>>>
>>> Hi -
>>>
>>>> From: Yaron Sheffer <yaronf.ietf@gmail.com>
>>>> Sent: Aug 13, 2013 2:11 PM
>>>> To: IETF Discussion Mailing List <ietf@ietf.org>
>>>> Subject: re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary
>>>> Object      Representation (CBOR)) to Proposed Standard
>>>
>>> ...
>>>>
>>>> - The "diagnostic notation" can be used very effectively for things like
>>>> configuration files, e.g. if an application already uses CBOR on the
>>>> wire. Therefore I would suggest to formalize it a bit more, so that we
>>>> also have interoperability at this level.
>>>
>>>
>>> Do you envision it as an encoding for Netconf?
>>>
>>> Randy
>>>
>>

From andy@yumaworks.com  Wed Aug 14 10:57:31 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1B721E80C6 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 10:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.433,  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 DNDHpYtFwP1T for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 10:57:26 -0700 (PDT)
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD7B21E80BA for <ietf@ietf.org>; Wed, 14 Aug 2013 10:57:26 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id ma3so9518812pbc.7 for <ietf@ietf.org>; Wed, 14 Aug 2013 10:57:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jvpiP1i6P2IyFLHAkLP19SQxwk9c76R//SLGbLIvlnM=; b=CTg/aII/YBpDkmx5SVyvsOzJofJPx413hlXFh3InxV7mWLyaqn2aYoHA88CTRYBSlx dB/wo62un7C5SAsD6k6ezLpfHx+TZk29kp5kjNK/wYDFo4kGPenuKw30tVT32rH7pxEo U8DnhjayOqMl6JzRDTKeWbEn7LtEaxJ11CVs6+8uB8QDcdvO5+TKzLgw3oiWejUIun1H GB+qXN2cf2l0CcVaJwnAM0gCfAE73mm2n/JT57Qan/ZgoYDnuPSHqzcOdojzevDgShXV xqJMf/K8uGfoDh2PmsRwEJsiImb4kkV6r3amAxOwZ7PPp797Ly8Yj8a1UWKO0G+DaeR7 DgTw==
X-Gm-Message-State: ALoCoQl9PK0SMTV0ScXTnMDxgwsgn9McY2FrsLIWJfJSpmrM82pZ0ajUjcXe4ePMpkJ9Mj3W/+Im
MIME-Version: 1.0
X-Received: by 10.66.219.38 with SMTP id pl6mr11396955pac.59.1376503042783; Wed, 14 Aug 2013 10:57:22 -0700 (PDT)
Received: by 10.70.41.162 with HTTP; Wed, 14 Aug 2013 10:57:22 -0700 (PDT)
In-Reply-To: <D52BE231-28E3-4DE6-BE66-8D0E85691FC6@tzi.org>
References: <15222127.1376445217946.JavaMail.root@elwamui-rustique.atl.sa.earthlink.net> <520B323D.7090702@gmail.com> <m2mwoko60f.wl%randy@psg.com> <D52BE231-28E3-4DE6-BE66-8D0E85691FC6@tzi.org>
Date: Wed, 14 Aug 2013 10:57:22 -0700
Message-ID: <CABCOCHRNczb0RJ-w6hfE6d2hv_yTE0f46LBjAmOfCgQVkY=VaA@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Andy Bierman <andy@yumaworks.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 17:57:31 -0000

On Wed, Aug 14, 2013 at 6:07 AM, Carsten Bormann <cabo@tzi.org> wrote:
> On Aug 14, 2013, at 13:40, Randy Bush <randy@psg.com> wrote:
>
>>> YANG seems to be incompatible with CBOR.
>>
>> so what does that say about yang, yang's suitability for netconf, cbor,
>> and cbor's suitability?
>
> Good question.  I'm not sure the jury is even out on that yet.
>
> Yaron reminded me that netconf is using XPath for various purposes, so a =
CBOR rendition of netconf would need to do the same that you would need for=
 doing netconf with JSON: either replace XPath with something else (indeed =
causing some incompatibility), or explain how to use XPath with the CBOR/JS=
ON translation of the YANG model (which might be interesting).
>
> CBOR certainly has no trouble carrying around the data described by a YAN=
G model.
> (Indeed, CBOR's decimal fractions were inspired by YANG's.)
> But then, I don't have an opinion whether adding a binary object represen=
tation to the netconf ecosystem is on the agenda.
>

I am not sure this is an actual problem.
NETCONF uses full XPath only if the :xpath capability
is supported.  The "select" expression represents
the data to be returned from the conceptual datastore
and possibly the state/statistics within the device.
The select expression is not related to the message on the wire.

There is also an "error-path" field that is returned in errors
that contains the absolute path of the message or data node
that caused the error.

Neither of these message fields should cause an encoding problem.
They are just strings at the message layer.



> Gr=FC=DFe, Carsten
>

Andy

From iab-chair@iab.org  Wed Aug 14 11:48:49 2013
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8182421E80DD; Wed, 14 Aug 2013 11:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7TSq2M8rye0; Wed, 14 Aug 2013 11:48:49 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id EEE0421E80D6; Wed, 14 Aug 2013 11:48:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id C8458A608C; Wed, 14 Aug 2013 11:47:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dcv9IyttXQlF; Wed, 14 Aug 2013 11:47:32 -0700 (PDT)
Received: from [192.168.0.48] (75-139-113-21.dhcp.mant.nc.charter.com [75.139.113.21]) by c9a.amsl.com (Postfix) with ESMTPSA id 4753CA608B; Wed, 14 Aug 2013 11:47:32 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: multipart/alternative; boundary=Apple-Mail-39-914447108
Subject: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
Date: Wed, 14 Aug 2013 14:48:41 -0400
Message-Id: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 18:48:49 -0000

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

This is a call for review of "List of Internet Official Protocol =
Standards: Replaced by an Online Database" prior to potential approval =
as an IAB stream RFC.

The document is available for inspection here: =
https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/

The Call for Review will last until 11 September 2013.  Please send =
comments to iab@iab.org.=20

On behalf of the IAB,
  Russ Housley
  IAB Chair


--Apple-Mail-39-914447108
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">This is a call for review of "List of Internet Official Protocol Standards:&nbsp;Replaced by an Online Database"&nbsp;prior to potential approval as an IAB stream RFC.<div><br>The document is available for inspection here:&nbsp;<font class="Apple-style-span" color="#144fae"><u><a href="https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/">https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/</a></u></font></div><div><font class="Apple-style-span" color="#144fae"><u><br></u></font>The Call for Review will last until 11 September 2013. &nbsp;Please send comments to <a href="mailto:iab@iab.org">iab@iab.org</a>.&nbsp;</div><div><br></div><div>On behalf of the IAB,</div><div>&nbsp; Russ Housley</div><div>&nbsp; IAB Chair</div><div><br></div></body></html>
--Apple-Mail-39-914447108--

From harald@alvestrand.no  Wed Aug 14 11:50:02 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBF3A21F9BD0 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 11:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.435
X-Spam-Level: 
X-Spam-Status: No, score=-110.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 bIqyxslyJFBZ for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 11:49:57 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 3F49F21F9A4B for <ietf@ietf.org>; Wed, 14 Aug 2013 11:49:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 7C10039E1BD; Wed, 14 Aug 2013 20:49:45 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V6NzKSg36h+q; Wed, 14 Aug 2013 20:49:44 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 3354139E1BB; Wed, 14 Aug 2013 20:49:44 +0200 (CEST)
Message-ID: <520BD147.1040505@alvestrand.no>
Date: Wed, 14 Aug 2013 20:49:43 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org>
In-Reply-To: <52095E5D.5070802@ninebynine.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 18:50:02 -0000

On 08/13/2013 12:14 AM, Graham Klyne wrote:
>> From: The IESG <iesg-secretary@ietf.org>
>> To: IETF-Announce <ietf-announce@ietf.org>
>> Reply-To: ietf@ietf.org
>> Sender: <iesg-secretary@ietf.org>
>> Subject: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI 
>> Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to 
>> Proposed Standard
>>
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol'
>>   <draft-nandakumar-rtcweb-stun-uri-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 2013-08-16. 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 is the specification of the syntax and semantics of the
>>   Uniform Resource Identifier (URI) scheme for the Session Traversal
>>   Utilities for NAT (STUN) protocol.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-nandakumar-rtcweb-stun-uri/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-nandakumar-rtcweb-stun-uri/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>
> As IANA designated expert for reviewing URI scheme registrations, I've 
> been asked to approve this scheme for registration.  If there is IETF 
> consensus to publish this document, it is clear to me that the scheme 
> should be registered.
>
> But, in a personal capacity, not as designated reviewer, I have to ask 
> *why* this needs to be a URI.  As far as I can tell, it is intended 
> for use only in very constrained environments, where there seems to be 
> little value in having an identifier that can appear in all the 
> contexts where a URI may be recognized.
>
> The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 
> include:
>
> "New URI schemes SHOULD have clear utility to the broad Internet 
> community, beyond that available with already registered URI schemes."
> -- http://tools.ietf.org/html/rfc4395#section-2.1
>
> This "utility to the broader community" is not clear to me, but I 
> don't fully understand the intended scope of this protocol, so I could 
> be missing something.  So, in declaring consensus for this 
> specification, I would request that this aspect at least be considered.

I can only give  my personal opinion....

1) This is a format for a piece of data. This data cannot be expressed 
using any existing URI scheme - indeed, I don't think there exists 
another well-defined textual representation of this piece of data.

1) This is defining an identifier that will be used in W3C-defined APIs. 
W3C tends to use URIs every time they want a self-defining piece of data 
with a clearly defined structure.
In the particular API where this is wanted, one wants to have STUN URIs, 
TURNS URIs and TURN URIs passed over the same interface. Thus, keeping 
with the W3C tradition of URIs seems reasonable.

I think this answers the question about "utility to the broader 
community" to my satisfaction - your mileage may differ, of course.


>
> ...
>
> Further, according to http://tools.ietf.org/html/rfc5389 it appears 
> that there are security considerations with regard to the STUN 
> protocol that it should not be used in isolation:
> [[
>    Classic STUN also had a security vulnerability -- attackers could
>    provide the client with incorrect mapped addresses under certain
>    topologies and constraints, and this was fundamentally not solvable
>    through any cryptographic means.  Though this problem remains with
>    this specification, those attacks are now mitigated through the use
>    of more complete solutions that make use of STUN.
>
>    For these reasons, this specification obsoletes RFC 3489, and instead
>    describes STUN as a tool that is utilized as part of a complete NAT
>    traversal solution.
> ]]
> -- http://tools.ietf.org/html/rfc5389#section-2
>
> It seems to me that creating a URI for STUN could encourage its use in 
> environments outside the "more complete solutions that make use of 
> STUN".  This seems to be further reason that STUN[S] should not be a 
> URI scheme.
>
> I have also suggested that, if registered, the URI scheme registration 
> should carries a "health warning" to this effect, and that it is not 
> suitable for general use that is not part of a "complete NAT traversal 
> solution".  But I also recognize that I do not fully grasp the 
> security implications, and that if those that do know better can agree 
> that there is no potential for creating security risks here, this 
> suggestion may be unnecessary.

This URI scheme does not represent STUN. It represents configuration 
data that is used to initialize a protocol machine that utilizes STUN.

This configuration data has to be passed no matter what the format of 
the data is - whether it be URI or not.

Thus, I do not think the argument raised is really relevant to the 
context. The data will be passed, and registering an URI scheme will 
cause no more and no less data to be passed.

Again, my opinion.

From harald@alvestrand.no  Wed Aug 14 11:51:59 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7ACA21F9C16 for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 11:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.455
X-Spam-Level: 
X-Spam-Status: No, score=-110.455 tagged_above=-999 required=5 tests=[AWL=0.144, 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 I4mckhiyaoWF for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 11:51:52 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 01CA021F9D1C for <ietf@ietf.org>; Wed, 14 Aug 2013 11:51:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 40FA139E1C8 for <ietf@ietf.org>; Wed, 14 Aug 2013 20:51:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-Mad0lHhOWz for <ietf@ietf.org>; Wed, 14 Aug 2013 20:51:46 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 6583A39E1BB for <ietf@ietf.org>; Wed, 14 Aug 2013 20:51:46 +0200 (CEST)
Message-ID: <520BD1C1.2090002@alvestrand.no>
Date: Wed, 14 Aug 2013 20:51:45 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <6.2.5.6.2.20130813113033.0b7632c0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130813113033.0b7632c0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 18:51:59 -0000

On 08/13/2013 09:03 PM, S Moonesamy wrote:
> At 15:14 12-08-2013, Graham Klyne wrote:
>> But, in a personal capacity, not as designated reviewer, I have to 
>> ask *why* this needs to be a URI.  As far as I can tell, it is 
>> intended for use only in very constrained environments, where there 
>> seems to be little value in having an identifier that can appear in 
>> all the contexts where a URI may be recognized.
>
> This is an individual comment.  I reviewed 
> draft-petithuguenin-behave-turn-uris-05.  I wondered why a URI was 
> needed given the limited use.  The same argument is applicable for 
> draft-nandakumar-rtcweb-stun-uri-05.  There is running code for both 
> drafts.  Both draft qualify for "DNP".  I would describe the proposals 
> as trying to fit the solution within a URI instead of designing a URI 
> scheme.  Both proposals sound like UNSAF.

FWIW, UNSAF = Unilateral Self Address Fixing, or "figuring out what my 
address is on the Internet", and is exactly what STUN is useful for.

In a world of NATs, UNSAF is, unfortunately, a necessary thing to do. 
These URI schemes allow us to pass configuration data for performing 
these operations in a standardized form.



From hartmans@mit.edu  Wed Aug 14 12:19:21 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43AE911E81F0; Wed, 14 Aug 2013 12:19: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 ZCuz8wprUAt7; Wed, 14 Aug 2013 12:19:15 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D417411E81D3; Wed, 14 Aug 2013 12:19:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 5681420288; Wed, 14 Aug 2013 15:17:58 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ad05Q-xHOkXP; Wed, 14 Aug 2013 15:17:57 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 14 Aug 2013 15:17:57 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 0E4688051A; Wed, 14 Aug 2013 15:19:06 -0400 (EDT)
From: Sam Hartman <hartmans-ietfc@mit.edu>
Newsgroups: 
To: "Black\, David" <david.black@emc.com>
Subject: Re: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Date: Wed, 14 Aug 2013 15:19:06 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> (David Black's message of "Fri, 9 Aug 2013 10:47:05 -0400")
Message-ID: <tslvc38cc7p.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 19:19:21 -0000

David, as we mentioned in the IESG thread, we seem to have dropped the
response to your comments about IANA actions.

WG:
>From the genart review:

[9] I suggest Expert Review for the new IANA registries, not just 
First Come First Served, so that someone with a security "clue" can
check that the proposed registrations are reasonable.


Stephen has filed a related DISCUSS position.  He's confused why we need
a registry for  KDFs or algorithms.
He argues that the protocols should already have such a registry.  He
argues that it would be non-sensical to register a value in this
registry but not the protocol registry.

In a somewhat related discussion, multiple people have asked what the
scope of this document is.  Are we defining something for routing
protocols?  Any security protocol in the world?  Something in-between?


IU'm going to make two responses:

1)
I think FCFS is not harmful for these registries.

David's main concern is that bad security will get registered.

I'll point out that these registries are not about what security you can
use with a routing protocol, but about what security you can configure
from a management standpoint.
Registering rot13 or similarly questionable security here wouldn't mean
I could use it with a routing protocol, only that I could ask a system
to do so.  If ROT13 was not actually in the security-specific registries
for the protocols in question there'd be no way to send a
rot13-transformed message.

I think people wanting to use bad security in routing protocols will
focus on specifying how to use the security for the protocols, and
that's the appropriate place to do any gateway review.
Yeah, I guess with FCFS it's possible someone could register here and
then later realize they cannot get their md4 security approved in the
actual protocol registry document.

That might be confusing but doesn't seem very harmful.

Also, some routing protocols are protected by cleartext passwords sent
over the network.  We want to be able to manage that, so we will be
registering plaintext password in these registries.
I don't think anyone will come up with anything worse than that.

Finally, I think a lot of us have begun to question the value in
security review for codepoint assignment.  Some security WGs care a lot;
some don't seem to care much at all.

2)  Why I prefer FCFS or at least would object strongly to expert
review.

If we're going to say we want expert review I want us to give  expert
instructions at least good enough that I believe I could answer the
question of what registrations to approve if I were appointed the
expert.

I don't think we could come to consensus on those instructions very
easily.
In particular, I think it would be challenging for us to describe what
security protocols the protocol registry applies to and which ones it
does not.

I'm totally fine publishing this document knowing it will be used for
routing protocols but not knowing what beyond routing protocols it will
be used for.
If we do that FCFS makes a lot of sense.

So, my recommendation is that we keep our current registration policy.

From hartmans@mit.edu  Wed Aug 14 12:31:58 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF3221E808C; Wed, 14 Aug 2013 12:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VZudT0fEjn7; Wed, 14 Aug 2013 12:31:53 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id DFCE921F99D0; Wed, 14 Aug 2013 12:31:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 9212A20280; Wed, 14 Aug 2013 15:30:41 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLmALA9OwzD7; Wed, 14 Aug 2013 15:30:41 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 14 Aug 2013 15:30:41 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3D9D48051A; Wed, 14 Aug 2013 15:31:50 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
Subject: Re: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com>
Date: Wed, 14 Aug 2013 15:31:50 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> (David Black's message of "Fri, 9 Aug 2013 10:47:05 -0400")
Message-ID: <tslr4dwcbmh.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 19:31:59 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:


    Black,> [A] Overall - I would like to see a paragraph added on how
    Black,> this database conceptually relates to the IPsec Peer
    Black,> Authorization Database (PAD) - see RFC 4301, section 4.4.3.

It doesn't.
not even a little bit.
It's not IPsec; it's not about what key management peers to interact
with.

It's conceptually similar to the Security Association Database (SAD).
In a discussion with Jari I agreed to propose text for a paragraph
describing how this interacts with IPsec.

If this conceptual database is used to manage to keys for a security
    protocol that uses IPsec [RFC4301] security services, then  the
    interactions between this conceptual database and the IPsec
    databases needs to be described by the protocol specification.
    Typically such a protocol would insert entries into the Security
    Association Database (SAD) when rows are inserted into the key table
    and remove SAD entries when key table rows are removed.  The
    protocol specification needs to describe how the SAD entries are
    constructed along with any other IPsec database entries that are
    needed, including a description of how these entries are ordered
    along with other IPsec database entries.  The question of whether it
    is desirable to use this conceptual database to manage protocols
    that use IPsec security services is open and has not been evaluated.

    Black,> [C] (Section 3) Where does key selection occur?  I would
    Black,> suggest that the database return all possible keys and let
    Black,> the protocol figure out what to use.  This is particularly
    Black,> important for inbound traffic for obvious reasons.

I think we've discussed key selection in the WG and come to a different
conclusion.  The key table selects the key.  We expect peer, key ID,
protocol and interface to identify a unique key for an inbound packet.

So, I think the concern you raise is not a problem.
While there was not a specific thread discussing key selection or this
issue, there were multiple reviewers who provided comments on key
selection over the development of the document, and making a major
change at this point without a technical problem seems undesirable.
If I'm missing something and the inbound packet issue is a problem then
we need to discuss it.

From hallam@gmail.com  Wed Aug 14 13:15:17 2013
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 6819211E817E for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 13:15: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, 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 bCsOx7LAEMwg for <ietf@ietfa.amsl.com>; Wed, 14 Aug 2013 13:15:16 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E299611E8118 for <ietf@ietf.org>; Wed, 14 Aug 2013 13:15:15 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w60so8331813wes.1 for <ietf@ietf.org>; Wed, 14 Aug 2013 13:15:15 -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=M8uzWRrAc9vrs4PAFd5xfXW7kTjmKrIdh20+2ff5KC8=; b=vg1U+sAt02ETrmPFsrNJYpOYkn3gdpk7shDOXwSQhdL//lLp4LxUG8XzHNTLMf3wKB U1P45Bgcej2RtvhAZ7VcfC7isDKyJD0GcMhWzjM1lLvuIFM/UXdyLfwihzBY0hbxUBPQ ylOV4lDPPjm2x4CURZPK4JsCXqVNDMluzociaI7uY82oP94xwJ+SWQ5wvDrIAXp2leh+ Lp+9MJ9FmQE08cACo7KBoWfUDVrOmeigaMkU2QEQ5KpdcqjvrAN+wnPW9oTaseXOgIG6 m8bhsy7YbpNCx8c06pWAnTQs43B8ytQ+AZF18/jyLzek+KPQHSellEnRUO40Wzey5alR +bxw==
MIME-Version: 1.0
X-Received: by 10.180.36.208 with SMTP id s16mr2981472wij.33.1376511315038; Wed, 14 Aug 2013 13:15:15 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Wed, 14 Aug 2013 13:15:14 -0700 (PDT)
In-Reply-To: <520BA0FA.6000406@dcrocker.net>
References: <CE300BA7.15704%joe@cursive.net> <520BA0FA.6000406@dcrocker.net>
Date: Wed, 14 Aug 2013 21:15:14 +0100
Message-ID: <CAMm+Lwggw6EvYpLw=0cV=i-uPQc60CWbLbaF0abcQpXC5cioiw@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=e89a8f6466f5f65a4104e3ee03ab
Cc: Joe Hildebrand <hildjj@cursive.net>, IETF Discussion Mailing List <ietf@ietf.org>, Yaron Sheffer <yaronf.ietf@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 20:15:17 -0000

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

On Wed, Aug 14, 2013 at 4:23 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/13/2013 3:20 PM, Joe Hildebrand wrote:
>
>> One of the reasons why I like the CBOR tag applied to a byte stream is
>> that
>> it can be used to skip parsing on entire sections (no matter their
>> underlying types) in processors that don't need to understand that
>> section.
>>
>
>
> This is an example of the core reason that having a "one true standard" is
> not appropriate for many topics:  design choices optimize along particular
> axes, giving particular optimizations, typically at the expense of others.
>  Different operating context benefit from different optimizations.
>
> It makes sense for a specification to document its tradeoffs; it often
> does not make sense to choose only one such specification for use in all
> scenarios.


Maybe, but should the standards process at least uncover what the potential
design axes might be?

I think that we could actually dispense with design options for application
protocols entirely Remember that standards are all about making design
choices that don't matter.

It does not matter how the bits are encoded on the wire, all that actually
matters is the complexity of decoding them. And CBOR is not a good encoding
by that measure. It has a lot of options and is designed to offer even
more. CBOR is retrograde to MessagePack, a step backwards.


90% of Application protocols are simple API function calls. The other 10%
are API function callbacks. Thats it.

We have a complete set of intrinsic types that are recognized by modern
programming languages. There are some programming languages that don't
recognize all the intrinsic types of C/C#/Java but at this point the
intrinsic types that are not supported those languages are pretty few and
tending to decrease rather than increase over time.


The approach I took in JSON-BCD was to start with the assumption that the
JSON data model was sufficiently complete to be considered definitive
(after adding binary arrays) and then propose three extensions to the JSON
encoding model to provide what I believe to be 100% coverage of all
reasonable use cases.

It is possible that I did not succeed but there are two ways that I might
have slipped up. Dave does not distinguish between these.

1) An application might need a richer data model than JSON affords.
2) An application might need a more efficient bit packing than JSON-BCD
provides or a canonical encoding.

I can't address the first since the starting point for my design is to not
change the JSON data model. If someone did find JSON insufficient then they
should probably be looking at XML or ASN.1 anyway.

The second is easy enough to address, just add another encoding like I did.

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

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

<div dir=3D"ltr">On Wed, Aug 14, 2013 at 4:23 PM, Dave Crocker <span dir=3D=
"ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocke=
r.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 8/13/2013 3:20 PM, Joe =
Hildebrand wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
One of the reasons why I like the CBOR tag applied to a byte stream is<br>
that<br>
it can be used to skip parsing on entire sections (no matter their<br>
underlying types) in processors that don&#39;t need to understand that sect=
ion.<br>
</blockquote>
<br>
<br></div>
This is an example of the core reason that having a &quot;one true standard=
&quot; is not appropriate for many topics: =A0design choices optimize along=
 particular axes, giving particular optimizations, typically at the expense=
 of others. =A0Different operating context benefit from different optimizat=
ions.<br>

<br>
It makes sense for a specification to document its tradeoffs; it often does=
 not make sense to choose only one such specification for use in all scenar=
ios.</blockquote><div><br></div><div>Maybe, but should the standards proces=
s at least uncover what the potential design axes might be?</div>
<div><br></div><div>I think that we could actually dispense with design opt=
ions for application protocols entirely Remember that standards are all abo=
ut making design choices that don&#39;t matter.</div><div><br></div><div>
It does not matter how the bits are encoded on the wire, all that actually =
matters is the complexity of decoding them. And CBOR is not a good encoding=
 by that measure. It has a lot of options and is designed to offer even mor=
e. CBOR is retrograde to MessagePack, a step backwards.</div>
<div><br></div><div><br></div><div>90% of Application protocols are simple =
API function calls. The other 10% are API function callbacks. Thats it.</di=
v><div><br></div><div>We have a complete set of intrinsic types that are re=
cognized by modern programming languages. There are some programming langua=
ges that don&#39;t recognize all the intrinsic types of C/C#/Java but at th=
is point the intrinsic types that are not supported those languages are pre=
tty few and tending to decrease rather than increase over time.</div>
<div><br></div><div><br></div><div>The approach I took in JSON-BCD was to s=
tart with the assumption that the JSON data model was sufficiently complete=
 to be considered definitive (after adding binary arrays) and then propose =
three extensions to the JSON encoding model to provide what I believe to be=
 100% coverage of all reasonable use cases.</div>
<div><br></div><div>It is possible that I did not succeed but there are two=
 ways that I might have slipped up. Dave does not distinguish between these=
.</div><div><br></div><div>1) An application might need a richer data model=
 than JSON affords.</div>
<div>2) An application might need a more efficient bit packing than JSON-BC=
D provides or a canonical encoding.</div><div><br></div><div>I can&#39;t ad=
dress the first since the starting point for my design is to not change the=
 JSON data model. If someone did find JSON insufficient then they should pr=
obably be looking at XML or ASN.1 anyway.</div>
<div><br></div><div>The second is easy enough to address, just add another =
encoding like I did.</div><div><br></div></div>-- <br>Website: <a href=3D"h=
ttp://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--e89a8f6466f5f65a4104e3ee03ab--

From cabo@tzi.org  Wed Aug 14 13:47:00 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C4511E8187; Wed, 14 Aug 2013 13:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C93vMKWag9eG; Wed, 14 Aug 2013 13:46:54 -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 4960411E8118; Wed, 14 Aug 2013 13:46:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7EKkLTL010851; Wed, 14 Aug 2013 22:46:22 +0200 (CEST)
Received: from [192.168.217.105] (p54890CE5.dip0.t-ipconnect.de [84.137.12.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8A17FB0;  Wed, 14 Aug 2013 22:46:21 +0200 (CEST)
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
Date: Wed, 14 Aug 2013 22:46:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B9ACBC6-7552-4A55-9C3F-A773A373C0DE@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org> <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1508)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2013 20:47:00 -0000

On Aug 13, 2013, at 13:14, Tony Finch <dot@dotat.at> wrote:

> MessagePack is simpler so will need even less code

FWIW, earlier today I had a nice afternoon with the msgpack-ruby C code, =
converting it to encoding and decoding CBOR instead.

Saved ~ 250 lines of C code.

Of course, I'm filling in that gap now by implementing some of the =
optional tags of CBOR.
In the end, the implementation of a generic CBOR encoder/decoder with a =
sizable collection of optional tags will probably indeed be slightly =
larger.
But if you just need the features of MessagePack, I now have one data =
point where CBOR measurably wins on the implementation complexity =
metric.

Gr=FC=DFe, Carsten


From hallam@gmail.com  Thu Aug 15 00:41:48 2013
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 379FA21E80A3; Thu, 15 Aug 2013 00:41: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=[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 P9NPrXZTMt-k; Thu, 15 Aug 2013 00:41:47 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D9C6521F9F74; Thu, 15 Aug 2013 00:41:46 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id r10so402322lbi.1 for <multiple recipients>; Thu, 15 Aug 2013 00:41: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=c5SLoSXtuzm2isTALKxxEK1MVD9O/xsJrYWgbQ8RmFs=; b=XMyk5731a9WEKLnb8Zcab6Ag3nQRXe7he8zQJxFLiV0KIr5ML/lv4dqU7f4ZAmmElt vkGLsGtHpnVAbhRtVowGHQ2Bc3xRRqtgixsCRBGmN0REoUwFQvHE0Ny9ae2ZUOwLhJWk Hx8f1gw9WP7wYRD9L0Lo0mCpNicqdKs5QNQCalkl1RQEtizDxFhidZSjJhSSPVJBXJ8R d5nnWAAJeSFC8SbGi09/E/WmdIRo9lsLKIVjRNxeQHUy9TsxyNuCh2Pt2dk4oX9OXy8R gGOJIKg7h+g8/AHZCNiOSPlkQHoVCYiHRG2zKN0NsCPjNgVnTEfDQn0bGQupFiw74CjP 7fig==
MIME-Version: 1.0
X-Received: by 10.112.136.38 with SMTP id px6mr11493103lbb.29.1376552504259; Thu, 15 Aug 2013 00:41:44 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Thu, 15 Aug 2013 00:41:44 -0700 (PDT)
In-Reply-To: <6B9ACBC6-7552-4A55-9C3F-A773A373C0DE@tzi.org>
References: <CABkgnnXtCBHnOpY_=t7yWD-+7rSFHKdUi0VGUSVJqXq+xV-G2g@mail.gmail.com> <D16097AF-5DFB-4F6A-A6E7-2582C1CF25CD@tzi.org> <alpine.LSU.2.00.1308131200210.6019@hermes-2.csi.cam.ac.uk> <6B9ACBC6-7552-4A55-9C3F-A773A373C0DE@tzi.org>
Date: Thu, 15 Aug 2013 08:41:44 +0100
Message-ID: <CAMm+LwgHkcgej4U3G+ZgCKuy8nnQpX7hYZX7frdG3X3r8NqJHw@mail.gmail.com>
Subject: Re: [apps-discuss] Gen-ART review of draft-bormann-cbor-04
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=089e0112cc6a07f87f04e3f79b47
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 07:41:48 -0000

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

On Wed, Aug 14, 2013 at 9:46 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On Aug 13, 2013, at 13:14, Tony Finch <dot@dotat.at> wrote:
>
> > MessagePack is simpler so will need even less code
>
> FWIW, earlier today I had a nice afternoon with the msgpack-ruby C code,
> converting it to encoding and decoding CBOR instead.
>
> Saved ~ 250 lines of C code.
>
> Of course, I'm filling in that gap now by implementing some of the
> optional tags of CBOR.
> In the end, the implementation of a generic CBOR encoder/decoder with a
> sizable collection of optional tags will probably indeed be slightly larg=
er.
> But if you just need the features of MessagePack, I now have one data
> point where CBOR measurably wins on the implementation complexity metric.
>
> Gr=FC=DFe, Carsten
>
>
How does it compare to JSON-B which is considerably simpler than CBOR?

Getting Proposed Standard this way is not going to count for anything
because your proposal that you named after yourself was never in
competition with anything else. No other competitors were allowed.


And, no, no apologies for complaining about this farce.

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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Aug 14, 2013 at 9:46 PM, Carsten Bormann <span dir=3D"ltr">=
&lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org</a>&gt;<=
/span> wrote:<br>
<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 13, 2013, at 13:14,=
 Tony Finch &lt;<a href=3D"mailto:dot@dotat.at">dot@dotat.at</a>&gt; wrote:=
<br>

<br>
</div><div class=3D"im">&gt; MessagePack is simpler so will need even less =
code<br>
<br>
</div>FWIW, earlier today I had a nice afternoon with the msgpack-ruby C co=
de, converting it to encoding and decoding CBOR instead.<br>
<br>
Saved ~ 250 lines of C code.<br>
<br>
Of course, I&#39;m filling in that gap now by implementing some of the opti=
onal tags of CBOR.<br>
In the end, the implementation of a generic CBOR encoder/decoder with a siz=
able collection of optional tags will probably indeed be slightly larger.<b=
r>
But if you just need the features of MessagePack, I now have one data point=
 where CBOR measurably wins on the implementation complexity metric.<br>
<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br>How does it compare to JSON-B which is considerably =
simpler than CBOR?</div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">Getting Proposed Standard this way is not going to count for a=
nything because your proposal that you named after yourself was never in co=
mpetition with anything else. No other competitors were allowed.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">And, no, no apologies for complaining about this =
farce.<br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://ha=
llambaker.com/">http://hallambaker.com/</a><br>

</div></div>

--089e0112cc6a07f87f04e3f79b47--

From harald@alvestrand.no  Thu Aug 15 03:05:05 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C524811E80E4 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 03:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QuEkeOKFh89 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 03:04:56 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id D0ED521F9958 for <ietf@ietf.org>; Thu, 15 Aug 2013 03:04:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 0DC3E39EA41; Thu, 15 Aug 2013 12:04:54 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCLsx5fMJp-4; Thu, 15 Aug 2013 12:04:50 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [74.125.57.89]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 3807939E0E1; Thu, 15 Aug 2013 12:04:50 +0200 (CEST)
Message-ID: <520CA7C1.6080404@alvestrand.no>
Date: Thu, 15 Aug 2013 12:04:49 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org>
In-Reply-To: <520C9997.2010601@ninebynine.org>
Content-Type: multipart/alternative; boundary="------------040107030203070203080100"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 10:05:06 -0000

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

On 08/15/2013 11:04 AM, Graham Klyne wrote:
> Hi Harald,
>
> On 14/08/2013 19:49, Harald Alvestrand wrote:
>> On 08/13/2013 12:14 AM, Graham Klyne wrote:
> [...]
>>> But, in a personal capacity, not as designated reviewer, I have to 
>>> ask *why*
>>> this needs to be a URI.  As far as I can tell, it is intended for 
>>> use only in
>>> very constrained environments, where there seems to be little value 
>>> in having
>>> an identifier that can appear in all the contexts where a URI may be 
>>> recognized.
>>>
>>> The criteria for new URI schemes in 
>>> http://tools.ietf.org/html/rfc4395 include:
>>>
>>> "New URI schemes SHOULD have clear utility to the broad Internet 
>>> community,
>>> beyond that available with already registered URI schemes."
>>> -- http://tools.ietf.org/html/rfc4395#section-2.1
>>>
>>> This "utility to the broader community" is not clear to me, but I 
>>> don't fully
>>> understand the intended scope of this protocol, so I could be missing
>>> something.  So, in declaring consensus for this specification, I 
>>> would request
>>> that this aspect at least be considered.
>>
>> I can only give  my personal opinion....
>>
>> 1) This is a format for a piece of data. This data cannot be 
>> expressed using any
>> existing URI scheme - indeed, I don't think there exists another 
>> well-defined
>> textual representation of this piece of data.
>>
>> 1) This is defining an identifier that will be used in W3C-defined 
>> APIs. W3C
>> tends to use URIs every time they want a self-defining piece of data 
>> with a
>> clearly defined structure.
>> In the particular API where this is wanted, one wants to have STUN 
>> URIs, TURNS
>> URIs and TURN URIs passed over the same interface. Thus, keeping with 
>> the W3C
>> tradition of URIs seems reasonable.
>>
>> I think this answers the question about "utility to the broader 
>> community" to my
>> satisfaction - your mileage may differ, of course.
>
> Some thoughts occur to me:
>
> 1. My reading was that this is a generic NAT traversal protocol, so 
> the requirement here is not Web/W3C specific.  But you do say "used in 
> W3C-defined APIs"...

Truth in advertising: One W3C-defined API.
The specific reference:

http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-members

>
> 2. If this is being driven by W3C activities, this should probably be 
> flagged with W3C TAG.  I'll raise it there.
>
> 3. URIs are not generally used as *data* formats, but rather as 
> identifiers for resources.  Web architecture and REST principles tend 
> to discourage information encoded in URIs in favour of data 
> representation formats.  Cf. 
> http://www.w3.org/TR/webarch/#uri-opacity, 
> http://www.w3.org/2001/tag/doc/metaDataInURI-31.html

Well, it is. The data encoded is the identification of a STUN server, 
which is a resource.

>
> 4. If the purpose here is simply to encode data, then there does 
> already exist a suitable URI scheme, viz data:.  A new content type 
> can be defined to actually encode the required data, and the whole be 
> wrapped in a data: URI.  This approach has the advantage that 
> alternative mechanisms (other than URIs) can be used to transfer the 
> traversal data if required (though that may be moot in the very 
> restricted intended scope of deployment for stun:, etc.)

Yes, but why?

>
>>>
>>> ...
>>>
>>> Further, according to http://tools.ietf.org/html/rfc5389 it appears 
>>> that there
>>> are security considerations with regard to the STUN protocol that it 
>>> should
>>> not be used in isolation:
>>> [[
>>>    Classic STUN also had a security vulnerability -- attackers could
>>>    provide the client with incorrect mapped addresses under certain
>>>    topologies and constraints, and this was fundamentally not solvable
>>>    through any cryptographic means.  Though this problem remains with
>>>    this specification, those attacks are now mitigated through the use
>>>    of more complete solutions that make use of STUN.
>>>
>>>    For these reasons, this specification obsoletes RFC 3489, and 
>>> instead
>>>    describes STUN as a tool that is utilized as part of a complete NAT
>>>    traversal solution.
>>> ]]
>>> -- http://tools.ietf.org/html/rfc5389#section-2
>>>
>>> It seems to me that creating a URI for STUN could encourage its use in
>>> environments outside the "more complete solutions that make use of 
>>> STUN".
>>> This seems to be further reason that STUN[S] should not be a URI 
>>> scheme.
>>>
>>> I have also suggested that, if registered, the URI scheme 
>>> registration should
>>> carries a "health warning" to this effect, and that it is not 
>>> suitable for
>>> general use that is not part of a "complete NAT traversal 
>>> solution".  But I
>>> also recognize that I do not fully grasp the security implications, 
>>> and that
>>> if those that do know better can agree that there is no potential 
>>> for creating
>>> security risks here, this suggestion may be unnecessary.
>>
>> This URI scheme does not represent STUN. It represents configuration 
>> data that
>> is used to initialize a protocol machine that utilizes STUN.
>>
>> This configuration data has to be passed no matter what the format of 
>> the data
>> is - whether it be URI or not.
>>
>> Thus, I do not think the argument raised is really relevant to the 
>> context. The
>> data will be passed, and registering an URI scheme will cause no more 
>> and no
>> less data to be passed.
>>
>> Again, my opinion.
>>
>
> If the URI is used only in very constrained contexts, then I agree.
>
> But the whole point of using a URI is that, due to URI opacity, it can 
> be used a a range of contexts where URIs are used.  If it cannot 
> properly be used in those other contexts, I have to question if it 
> really is a URI, as opposed to a string that happens to look like a URI.

The subject of "if it really is an URI" has plagued the whole URI space 
since day one. My current opinion is that if it looks like an URI, and 
parses according to the URI spec, it should probably be called an URI.

So far, we know of one context where we need this (RTCWEB). It's the 
first context I know of where the Web and STUN intersect. It's not 
certain that it'll be the last one.

>
> I also note that this looks as if it may fall foul of the 
> "confidential metadata" practice noted in the W3C TAG finding about 
> metadata in URIs 
> (http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity)

That's why we took the "credentials" part out of the URI scheme.

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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 08/15/2013 11:04 AM, Graham Klyne
      wrote:<br>
    </div>
    <blockquote cite="mid:520C9997.2010601@ninebynine.org" type="cite">Hi
      Harald,
      <br>
      <br>
      On 14/08/2013 19:49, Harald Alvestrand wrote:
      <br>
      <blockquote type="cite">On 08/13/2013 12:14 AM, Graham Klyne
        wrote:
        <br>
      </blockquote>
      [...]
      <br>
      <blockquote type="cite">
        <blockquote type="cite">But, in a personal capacity, not as
          designated reviewer, I have to ask *why*
          <br>
          this needs to be a URI.&nbsp; As far as I can tell, it is intended
          for use only in
          <br>
          very constrained environments, where there seems to be little
          value in having
          <br>
          an identifier that can appear in all the contexts where a URI
          may be recognized.
          <br>
          <br>
          The criteria for new URI schemes in
          <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc4395">http://tools.ietf.org/html/rfc4395</a> include:
          <br>
          <br>
          "New URI schemes SHOULD have clear utility to the broad
          Internet community,
          <br>
          beyond that available with already registered URI schemes."
          <br>
          -- <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc4395#section-2.1">http://tools.ietf.org/html/rfc4395#section-2.1</a>
          <br>
          <br>
          This "utility to the broader community" is not clear to me,
          but I don't fully
          <br>
          understand the intended scope of this protocol, so I could be
          missing
          <br>
          something.&nbsp; So, in declaring consensus for this specification,
          I would request
          <br>
          that this aspect at least be considered.
          <br>
        </blockquote>
        <br>
        I can only give&nbsp; my personal opinion....
        <br>
        <br>
        1) This is a format for a piece of data. This data cannot be
        expressed using any
        <br>
        existing URI scheme - indeed, I don't think there exists another
        well-defined
        <br>
        textual representation of this piece of data.
        <br>
        <br>
        1) This is defining an identifier that will be used in
        W3C-defined APIs. W3C
        <br>
        tends to use URIs every time they want a self-defining piece of
        data with a
        <br>
        clearly defined structure.
        <br>
        In the particular API where this is wanted, one wants to have
        STUN URIs, TURNS
        <br>
        URIs and TURN URIs passed over the same interface. Thus, keeping
        with the W3C
        <br>
        tradition of URIs seems reasonable.
        <br>
        <br>
        I think this answers the question about "utility to the broader
        community" to my
        <br>
        satisfaction - your mileage may differ, of course.
        <br>
      </blockquote>
      <br>
      Some thoughts occur to me:
      <br>
      <br>
      1. My reading was that this is a generic NAT traversal protocol,
      so the requirement here is not Web/W3C specific.&nbsp; But you do say
      "used in W3C-defined APIs"...
      <br>
    </blockquote>
    <br>
    Truth in advertising: One W3C-defined API.<br>
    The specific reference:<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a
href="http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-members">http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-members</a><br>
    <br>
    <blockquote cite="mid:520C9997.2010601@ninebynine.org" type="cite">
      <br>
      2. If this is being driven by W3C activities, this should probably
      be flagged with W3C TAG.&nbsp; I'll raise it there.
      <br>
      <br>
      3. URIs are not generally used as *data* formats, but rather as
      identifiers for resources.&nbsp; Web architecture and REST principles
      tend to discourage information encoded in URIs in favour of data
      representation formats.&nbsp; Cf.
      <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/webarch/#uri-opacity">http://www.w3.org/TR/webarch/#uri-opacity</a>,
      <a class="moz-txt-link-freetext" href="http://www.w3.org/2001/tag/doc/metaDataInURI-31.html">http://www.w3.org/2001/tag/doc/metaDataInURI-31.html</a>
      <br>
    </blockquote>
    <br>
    Well, it is. The data encoded is the identification of a STUN
    server, which is a resource.<br>
    <br>
    <blockquote cite="mid:520C9997.2010601@ninebynine.org" type="cite">
      <br>
      4. If the purpose here is simply to encode data, then there does
      already exist a suitable URI scheme, viz data:.&nbsp; A new content
      type can be defined to actually encode the required data, and the
      whole be wrapped in a data: URI.&nbsp; This approach has the advantage
      that alternative mechanisms (other than URIs) can be used to
      transfer the traversal data if required (though that may be moot
      in the very restricted intended scope of deployment for stun:,
      etc.)
      <br>
    </blockquote>
    <br>
    Yes, but why?<br>
    <br>
    <blockquote cite="mid:520C9997.2010601@ninebynine.org" type="cite">
      <br>
      <blockquote type="cite">
        <blockquote type="cite">
          <br>
          ...
          <br>
          <br>
          Further, according to <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc5389">http://tools.ietf.org/html/rfc5389</a> it
          appears that there
          <br>
          are security considerations with regard to the STUN protocol
          that it should
          <br>
          not be used in isolation:
          <br>
          [[
          <br>
          &nbsp;&nbsp; Classic STUN also had a security vulnerability -- attackers
          could
          <br>
          &nbsp;&nbsp; provide the client with incorrect mapped addresses under
          certain
          <br>
          &nbsp;&nbsp; topologies and constraints, and this was fundamentally not
          solvable
          <br>
          &nbsp;&nbsp; through any cryptographic means.&nbsp; Though this problem
          remains with
          <br>
          &nbsp;&nbsp; this specification, those attacks are now mitigated through
          the use
          <br>
          &nbsp;&nbsp; of more complete solutions that make use of STUN.
          <br>
          <br>
          &nbsp;&nbsp; For these reasons, this specification obsoletes RFC 3489,
          and instead
          <br>
          &nbsp;&nbsp; describes STUN as a tool that is utilized as part of a
          complete NAT
          <br>
          &nbsp;&nbsp; traversal solution.
          <br>
          ]]
          <br>
          -- <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc5389#section-2">http://tools.ietf.org/html/rfc5389#section-2</a>
          <br>
          <br>
          It seems to me that creating a URI for STUN could encourage
          its use in
          <br>
          environments outside the "more complete solutions that make
          use of STUN".
          <br>
          This seems to be further reason that STUN[S] should not be a
          URI scheme.
          <br>
          <br>
          I have also suggested that, if registered, the URI scheme
          registration should
          <br>
          carries a "health warning" to this effect, and that it is not
          suitable for
          <br>
          general use that is not part of a "complete NAT traversal
          solution".&nbsp; But I
          <br>
          also recognize that I do not fully grasp the security
          implications, and that
          <br>
          if those that do know better can agree that there is no
          potential for creating
          <br>
          security risks here, this suggestion may be unnecessary.
          <br>
        </blockquote>
        <br>
        This URI scheme does not represent STUN. It represents
        configuration data that
        <br>
        is used to initialize a protocol machine that utilizes STUN.
        <br>
        <br>
        This configuration data has to be passed no matter what the
        format of the data
        <br>
        is - whether it be URI or not.
        <br>
        <br>
        Thus, I do not think the argument raised is really relevant to
        the context. The
        <br>
        data will be passed, and registering an URI scheme will cause no
        more and no
        <br>
        less data to be passed.
        <br>
        <br>
        Again, my opinion.
        <br>
        <br>
      </blockquote>
      <br>
      If the URI is used only in very constrained contexts, then I
      agree.
      <br>
      <br>
      But the whole point of using a URI is that, due to URI opacity, it
      can be used a a range of contexts where URIs are used.&nbsp; If it
      cannot properly be used in those other contexts, I have to
      question if it really is a URI, as opposed to a string that
      happens to look like a URI.
      <br>
    </blockquote>
    <br>
    The subject of "if it really is an URI" has plagued the whole URI
    space since day one. My current opinion is that if it looks like an
    URI, and parses according to the URI spec, it should probably be
    called an URI.<br>
    <br>
    So far, we know of one context where we need this (RTCWEB). It's the
    first context I know of where the Web and STUN intersect. It's not
    certain that it'll be the last one.<br>
    <br>
    <blockquote cite="mid:520C9997.2010601@ninebynine.org" type="cite">
      <br>
      I also note that this looks as if it may fall foul of the
      "confidential metadata" practice noted in the W3C TAG finding
      about metadata in URIs
      (<a class="moz-txt-link-freetext" href="http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity">http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity</a>)
      <br>
    </blockquote>
    <br>
    That's why we took the "credentials" part out of the URI scheme.<br>
  </body>
</html>

--------------040107030203070203080100--

From hadriel.kaplan@oracle.com  Thu Aug 15 06:16:50 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A842521E813A for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 06:16:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqFUlUAQBO6H for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 06:16:43 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 2355F21E811F for <ietf@ietf.org>; Thu, 15 Aug 2013 06:16:39 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7FDG4Mq016705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Aug 2013 13:16:06 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7FDG2uE003746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Aug 2013 13:16:03 GMT
Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7FDG28S009764; Thu, 15 Aug 2013 13:16:02 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 15 Aug 2013 06:16:01 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <520CA7C1.6080404@alvestrand.no>
Date: Thu, 15 Aug 2013 09:16:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6899EEB-F0F2-4F99-9E88-3677002104B2@oracle.com>
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org> <520CA7C1.6080404@alvestrand.no>
To: Graham Klyne <GK@ninebynine.org>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: Harald Alvestrand <harald@alvestrand.no>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 13:16:50 -0000

I agree with Harald.

Both the STUN and TURN URIs really do represent what we traditionally =
use URIs for: they identify a physical resource, a protocol for =
accessing the resource, etc.  Unlike a data URL, the STUN/TURN URI is =
not locally/directly self-contained data - it's a resource identifier, =
only meaningful when resolved and accessed using the scheme's protocol =
and host address, with whatever attributes are encoded in the URI.

Today only W3C has an immediate need for it, for the Javascript API for =
WebRTC, but one can envision this might be used by others as well in the =
future:

1) SIP might use this in a UA-config profile to tell a SIP client what =
STUN/TURN resources to use, or even in a REGISTER response someday.

2) XMPP might use this someday to indicate to clients what STUN/TURN =
servers to use for Jingle/etc.  Today it's done with a 'services' =
element I think, but it could be changed in the future.

3) BEHAVE WG might define a new DHCP option to tell DHCP clients a =
STUN/TURN server to use, in which case they could use this URI for that. =
(I don't know if BEHAVE's already done that, or decided not to do such a =
thing, but just sayin' it's another potential use-case)

It's possible other protocols might use this as well someday, for =
example RTSP or H.323.  I'm not saying any of them *will*, but it's =
possible.

-hadriel



On Aug 15, 2013, at 6:04 AM, Harald Alvestrand <harald@alvestrand.no> =
wrote:

> On 08/15/2013 11:04 AM, Graham Klyne wrote:
>> Hi Harald,=20
>>=20
>> On 14/08/2013 19:49, Harald Alvestrand wrote:=20
>>> On 08/13/2013 12:14 AM, Graham Klyne wrote:=20
>> [...]=20
>>>> But, in a personal capacity, not as designated reviewer, I have to =
ask *why*=20
>>>> this needs to be a URI.  As far as I can tell, it is intended for =
use only in=20
>>>> very constrained environments, where there seems to be little value =
in having=20
>>>> an identifier that can appear in all the contexts where a URI may =
be recognized.=20
>>>>=20
>>>> The criteria for new URI schemes in =
http://tools.ietf.org/html/rfc4395 include:=20
>>>>=20
>>>> "New URI schemes SHOULD have clear utility to the broad Internet =
community,=20
>>>> beyond that available with already registered URI schemes."=20
>>>> -- http://tools.ietf.org/html/rfc4395#section-2.1=20
>>>>=20
>>>> This "utility to the broader community" is not clear to me, but I =
don't fully=20
>>>> understand the intended scope of this protocol, so I could be =
missing=20
>>>> something.  So, in declaring consensus for this specification, I =
would request=20
>>>> that this aspect at least be considered.=20
>>>=20
>>> I can only give  my personal opinion....=20
>>>=20
>>> 1) This is a format for a piece of data. This data cannot be =
expressed using any=20
>>> existing URI scheme - indeed, I don't think there exists another =
well-defined=20
>>> textual representation of this piece of data.=20
>>>=20
>>> 1) This is defining an identifier that will be used in W3C-defined =
APIs. W3C=20
>>> tends to use URIs every time they want a self-defining piece of data =
with a=20
>>> clearly defined structure.=20
>>> In the particular API where this is wanted, one wants to have STUN =
URIs, TURNS=20
>>> URIs and TURN URIs passed over the same interface. Thus, keeping =
with the W3C=20
>>> tradition of URIs seems reasonable.=20
>>>=20
>>> I think this answers the question about "utility to the broader =
community" to my=20
>>> satisfaction - your mileage may differ, of course.=20
>>=20
>> Some thoughts occur to me:=20
>>=20
>> 1. My reading was that this is a generic NAT traversal protocol, so =
the requirement here is not Web/W3C specific.  But you do say "used in =
W3C-defined APIs"...=20
>=20
> Truth in advertising: One W3C-defined API.
> The specific reference:
>=20
> =
http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-m=
embers
>=20
>>=20
>> 2. If this is being driven by W3C activities, this should probably be =
flagged with W3C TAG.  I'll raise it there.=20
>>=20
>> 3. URIs are not generally used as *data* formats, but rather as =
identifiers for resources.  Web architecture and REST principles tend to =
discourage information encoded in URIs in favour of data representation =
formats.  Cf. http://www.w3.org/TR/webarch/#uri-opacity, =
http://www.w3.org/2001/tag/doc/metaDataInURI-31.html=20
>=20
> Well, it is. The data encoded is the identification of a STUN server, =
which is a resource.
>=20
>>=20
>> 4. If the purpose here is simply to encode data, then there does =
already exist a suitable URI scheme, viz data:.  A new content type can =
be defined to actually encode the required data, and the whole be =
wrapped in a data: URI.  This approach has the advantage that =
alternative mechanisms (other than URIs) can be used to transfer the =
traversal data if required (though that may be moot in the very =
restricted intended scope of deployment for stun:, etc.)=20
>=20
> Yes, but why?
>=20
>>=20
>>>>=20
>>>> ...=20
>>>>=20
>>>> Further, according to http://tools.ietf.org/html/rfc5389 it appears =
that there=20
>>>> are security considerations with regard to the STUN protocol that =
it should=20
>>>> not be used in isolation:=20
>>>> [[=20
>>>>    Classic STUN also had a security vulnerability -- attackers =
could=20
>>>>    provide the client with incorrect mapped addresses under certain=20=

>>>>    topologies and constraints, and this was fundamentally not =
solvable=20
>>>>    through any cryptographic means.  Though this problem remains =
with=20
>>>>    this specification, those attacks are now mitigated through the =
use=20
>>>>    of more complete solutions that make use of STUN.=20
>>>>=20
>>>>    For these reasons, this specification obsoletes RFC 3489, and =
instead=20
>>>>    describes STUN as a tool that is utilized as part of a complete =
NAT=20
>>>>    traversal solution.=20
>>>> ]]=20
>>>> -- http://tools.ietf.org/html/rfc5389#section-2=20
>>>>=20
>>>> It seems to me that creating a URI for STUN could encourage its use =
in=20
>>>> environments outside the "more complete solutions that make use of =
STUN".=20
>>>> This seems to be further reason that STUN[S] should not be a URI =
scheme.=20
>>>>=20
>>>> I have also suggested that, if registered, the URI scheme =
registration should=20
>>>> carries a "health warning" to this effect, and that it is not =
suitable for=20
>>>> general use that is not part of a "complete NAT traversal =
solution".  But I=20
>>>> also recognize that I do not fully grasp the security implications, =
and that=20
>>>> if those that do know better can agree that there is no potential =
for creating=20
>>>> security risks here, this suggestion may be unnecessary.=20
>>>=20
>>> This URI scheme does not represent STUN. It represents configuration =
data that=20
>>> is used to initialize a protocol machine that utilizes STUN.=20
>>>=20
>>> This configuration data has to be passed no matter what the format =
of the data=20
>>> is - whether it be URI or not.=20
>>>=20
>>> Thus, I do not think the argument raised is really relevant to the =
context. The=20
>>> data will be passed, and registering an URI scheme will cause no =
more and no=20
>>> less data to be passed.=20
>>>=20
>>> Again, my opinion.=20
>>>=20
>>=20
>> If the URI is used only in very constrained contexts, then I agree.=20=

>>=20
>> But the whole point of using a URI is that, due to URI opacity, it =
can be used a a range of contexts where URIs are used.  If it cannot =
properly be used in those other contexts, I have to question if it =
really is a URI, as opposed to a string that happens to look like a URI.=20=

>=20
> The subject of "if it really is an URI" has plagued the whole URI =
space since day one. My current opinion is that if it looks like an URI, =
and parses according to the URI spec, it should probably be called an =
URI.
>=20
> So far, we know of one context where we need this (RTCWEB). It's the =
first context I know of where the Web and STUN intersect. It's not =
certain that it'll be the last one.
>=20
>>=20
>> I also note that this looks as if it may fall foul of the =
"confidential metadata" practice noted in the W3C TAG finding about =
metadata in URIs =
(http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity)=20=

>=20
> That's why we took the "credentials" part out of the URI scheme.


From hadriel.kaplan@oracle.com  Thu Aug 15 07:01:32 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E572421E8143 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:01:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.326
X-Spam-Level: 
X-Spam-Status: No, score=-6.326 tagged_above=-999 required=5 tests=[AWL=0.273,  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 GyNNp3KS1bs8 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:01:21 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 0DC4C21F99A8 for <ietf@ietf.org>; Thu, 15 Aug 2013 07:01:19 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7FE1FqQ032168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Aug 2013 14:01:15 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7FE1D6V019766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Aug 2013 14:01:14 GMT
Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7FE1DvW007653; Thu, 15 Aug 2013 14:01:13 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 15 Aug 2013 07:01:13 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <52095E5D.5070802@ninebynine.org>
Date: Thu, 15 Aug 2013 10:01:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BAF41B4A-D434-4974-AEB6-538288A957C1@oracle.com>
References: <52095E5D.5070802@ninebynine.org>
To: draft-nandakumar-rtcweb-stun-uri@tools.ietf.org, draft-petithuguenin-behave-turn-uris@tools.ietf.org
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: Graham Klyne <GK@ninebynine.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 14:01:33 -0000

Some comments on this STUN draft and the TURN one:

1) The ABNF in these drafts leaves no room for future extension such as =
adding parameters.  Was that intentional?

2) Why do both of these docs repeat a lot of ABNF from RFC 3986, instead =
of just referencing it?  It says in the appendix some ABNF was repeated =
because RFC 3986 "are for hierarchical URIs".  I'm not exactly sure what =
that means other than you don't have a path component, but as far as I =
can tell the copied ABNF components in these STUN/TRUN drafts are =
verbatim copies of RFC 3986, all the way down to their final expansion. =20=


For example, 'IP-literal' and all of its sub-defined parts =
('IPv6address', 'IPvFuture', 'h16', 'ls32') appear identical to those in =
RFC 3986.  In fact, so is 'stun-host' and 'turn-host' - it's just RFC =
3986 'host' by another name.  Am I missing something?

Why not just have this:
   stunURI       =3D scheme ":" stun-host [ ":" stun-port ]
   scheme        =3D "stun" / "stuns"
   stun-host     =3D host      ;see section 3.2.2 of [RFC3986]
   stun-port     =3D port      ;see section 3.2.3 of [RFC3986]

Not a big deal, but it just seems simpler and cleaner to me to not =
repeat ABNF from other RFCs, especially when the RFC in question is the =
one for general URI syntax and you're defining a specific URI syntax =
based on it.

-hadriel



On Aug 12, 2013, at 6:14 PM, Graham Klyne <GK@ninebynine.org> wrote:

>> From: The IESG <iesg-secretary@ietf.org>
>> To: IETF-Announce <ietf-announce@ietf.org>
>> Reply-To: ietf@ietf.org
>> Sender: <iesg-secretary@ietf.org>
>> Subject: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI =
Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to =
Proposed Standard
>>=20
>>=20
>> The IESG has received a request from an individual submitter to =
consider
>> the following document:
>> - 'URI Scheme for Session Traversal Utilities for NAT (STUN) =
Protocol'
>>  <draft-nandakumar-rtcweb-stun-uri-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 2013-08-16. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>  This document is the specification of the syntax and semantics of =
the
>>  Uniform Resource Identifier (URI) scheme for the Session Traversal
>>  Utilities for NAT (STUN) protocol.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-nandakumar-rtcweb-stun-uri/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-nandakumar-rtcweb-stun-uri/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>=20
> As IANA designated expert for reviewing URI scheme registrations, I've =
been asked to approve this scheme for registration.  If there is IETF =
consensus to publish this document, it is clear to me that the scheme =
should be registered.
>=20
> But, in a personal capacity, not as designated reviewer, I have to ask =
*why* this needs to be a URI.  As far as I can tell, it is intended for =
use only in very constrained environments, where there seems to be =
little value in having an identifier that can appear in all the contexts =
where a URI may be recognized.
>=20
> The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 =
include:
>=20
> "New URI schemes SHOULD have clear utility to the broad Internet =
community, beyond that available with already registered URI schemes."
> -- http://tools.ietf.org/html/rfc4395#section-2.1
>=20
> This "utility to the broader community" is not clear to me, but I =
don't fully understand the intended scope of this protocol, so I could =
be missing something.  So, in declaring consensus for this =
specification, I would request that this aspect at least be considered.
>=20
> ...
>=20
> Further, according to http://tools.ietf.org/html/rfc5389 it appears =
that there are security considerations with regard to the STUN protocol =
that it should not be used in isolation:
> [[
>   Classic STUN also had a security vulnerability -- attackers could
>   provide the client with incorrect mapped addresses under certain
>   topologies and constraints, and this was fundamentally not solvable
>   through any cryptographic means.  Though this problem remains with
>   this specification, those attacks are now mitigated through the use
>   of more complete solutions that make use of STUN.
>=20
>   For these reasons, this specification obsoletes RFC 3489, and =
instead
>   describes STUN as a tool that is utilized as part of a complete NAT
>   traversal solution.
> ]]
> -- http://tools.ietf.org/html/rfc5389#section-2
>=20
> It seems to me that creating a URI for STUN could encourage its use in =
environments outside the "more complete solutions that make use of =
STUN".  This seems to be further reason that STUN[S] should not be a URI =
scheme.
>=20
> I have also suggested that, if registered, the URI scheme registration =
should carries a "health warning" to this effect, and that it is not =
suitable for general use that is not part of a "complete NAT traversal =
solution".  But I also recognize that I do not fully grasp the security =
implications, and that if those that do know better can agree that there =
is no potential for creating security risks here, this suggestion may be =
unnecessary.
>=20
> #g
> --


From harald@alvestrand.no  Thu Aug 15 07:10:35 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99F8221E8146 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:10:35 -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 LHQcdw+4-0Zj for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:10:27 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id C6FC511E8152 for <ietf@ietf.org>; Thu, 15 Aug 2013 07:10:25 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id B55BD39E0E1; Thu, 15 Aug 2013 16:10:23 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QOrySXqPovMP; Thu, 15 Aug 2013 16:10:22 +0200 (CEST)
Received: from [172.28.249.38] (unknown [74.125.57.89]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id E0C1E39EA62; Thu, 15 Aug 2013 16:10:21 +0200 (CEST)
Message-ID: <520CE14D.6070505@alvestrand.no>
Date: Thu, 15 Aug 2013 16:10:21 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Graham Klyne <GK@ninebynine.org>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org> <520CA7C1.6080404@alvestrand.no> <520CE029.3070405@ninebynine.org>
In-Reply-To: <520CE029.3070405@ninebynine.org>
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, 15 Aug 2013 14:10:35 -0000

On 08/15/2013 04:05 PM, Graham Klyne wrote:
> Harald,
>
> Briefly:
>
> 1. Thanks for the reference,
>
> and
>
> 2. I misunderstood what you meant by "This is a format for a piece of
> data".  In light of your clarification, I withdraw my comments 3 & 4. 
> Identification of the STUN service would appear to be a perfectly
> reasonable use.
>
> ...
>
> So the remaining issues from my questions are whether the intended
> highly constrained use of these services justifies allocating a URI
> scheme.
>
> If the community consensus is that it is of sufficient value, I might
> suggest an annotation to the scheme registration along the lines of:
>
> "This URI scheme is intended for use in very specific NAT traversal
> environments, and should not be used otherwise on the open Web or
> Internet."
>
> Would such a comment run contrary to your expectations for its use?

I would prefer to run the comment as "This scheme is intended for use in
specific environments that involve NAT traversal. Users of the scheme
need to carefully consider the security properties of the context in
which they are using it."

Echoing the warning in the STUN scheme - "use this when you know what
you're doing only".

Frankly, like Hadriel indicated, I have no idea whether it will be
useful in other contexts or not, and I'm hesitant to put language that
seems to claim that we've evaluated all possible contexts and say that
there aren't other contexts in which it can be useful.


>
> #g
> -- 
>
>
> On 15/08/2013 11:04, Harald Alvestrand wrote:
>> On 08/15/2013 11:04 AM, Graham Klyne wrote:
>>> Hi Harald,
>>>
>>> On 14/08/2013 19:49, Harald Alvestrand wrote:
>>>> On 08/13/2013 12:14 AM, Graham Klyne wrote:
>>> [...]
>>>>> But, in a personal capacity, not as designated reviewer, I have to
>>>>> ask *why*
>>>>> this needs to be a URI.  As far as I can tell, it is intended for
>>>>> use only in
>>>>> very constrained environments, where there seems to be little
>>>>> value in having
>>>>> an identifier that can appear in all the contexts where a URI may be
>>>>> recognized.
>>>>>
>>>>> The criteria for new URI schemes in
>>>>> http://tools.ietf.org/html/rfc4395 include:
>>>>>
>>>>> "New URI schemes SHOULD have clear utility to the broad Internet
>>>>> community,
>>>>> beyond that available with already registered URI schemes."
>>>>> -- http://tools.ietf.org/html/rfc4395#section-2.1
>>>>>
>>>>> This "utility to the broader community" is not clear to me, but I
>>>>> don't fully
>>>>> understand the intended scope of this protocol, so I could be missing
>>>>> something.  So, in declaring consensus for this specification, I
>>>>> would request
>>>>> that this aspect at least be considered.
>>>>
>>>> I can only give  my personal opinion....
>>>>
>>>> 1) This is a format for a piece of data. This data cannot be
>>>> expressed using any
>>>> existing URI scheme - indeed, I don't think there exists another
>>>> well-defined
>>>> textual representation of this piece of data.
>>>>
>>>> 1) This is defining an identifier that will be used in W3C-defined
>>>> APIs. W3C
>>>> tends to use URIs every time they want a self-defining piece of
>>>> data with a
>>>> clearly defined structure.
>>>> In the particular API where this is wanted, one wants to have STUN
>>>> URIs, TURNS
>>>> URIs and TURN URIs passed over the same interface. Thus, keeping
>>>> with the W3C
>>>> tradition of URIs seems reasonable.
>>>>
>>>> I think this answers the question about "utility to the broader
>>>> community" to my
>>>> satisfaction - your mileage may differ, of course.
>>>
>>> Some thoughts occur to me:
>>>
>>> 1. My reading was that this is a generic NAT traversal protocol, so the
>>> requirement here is not Web/W3C specific.  But you do say "used in
>>> W3C-defined
>>> APIs"...
>>
>> Truth in advertising: One W3C-defined API.
>> The specific reference:
>>
>> http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-members
>>
>>
>>>
>>> 2. If this is being driven by W3C activities, this should probably
>>> be flagged
>>> with W3C TAG.  I'll raise it there.
>>>
>>> 3. URIs are not generally used as *data* formats, but rather as
>>> identifiers
>>> for resources.  Web architecture and REST principles tend to discourage
>>> information encoded in URIs in favour of data representation
>>> formats.  Cf.
>>> http://www.w3.org/TR/webarch/#uri-opacity,
>>> http://www.w3.org/2001/tag/doc/metaDataInURI-31.html
>>
>> Well, it is. The data encoded is the identification of a STUN server,
>> which is a
>> resource.
>>
>>>
>>> 4. If the purpose here is simply to encode data, then there does
>>> already exist
>>> a suitable URI scheme, viz data:.  A new content type can be defined to
>>> actually encode the required data, and the whole be wrapped in a
>>> data: URI.
>>> This approach has the advantage that alternative mechanisms (other
>>> than URIs)
>>> can be used to transfer the traversal data if required (though that
>>> may be
>>> moot in the very restricted intended scope of deployment for stun:,
>>> etc.)
>>
>> Yes, but why?
>>
>>>
>>>>>
>>>>> ...
>>>>>
>>>>> Further, according to http://tools.ietf.org/html/rfc5389 it
>>>>> appears that there
>>>>> are security considerations with regard to the STUN protocol that
>>>>> it should
>>>>> not be used in isolation:
>>>>> [[
>>>>>    Classic STUN also had a security vulnerability -- attackers could
>>>>>    provide the client with incorrect mapped addresses under certain
>>>>>    topologies and constraints, and this was fundamentally not
>>>>> solvable
>>>>>    through any cryptographic means.  Though this problem remains with
>>>>>    this specification, those attacks are now mitigated through the
>>>>> use
>>>>>    of more complete solutions that make use of STUN.
>>>>>
>>>>>    For these reasons, this specification obsoletes RFC 3489, and
>>>>> instead
>>>>>    describes STUN as a tool that is utilized as part of a complete
>>>>> NAT
>>>>>    traversal solution.
>>>>> ]]
>>>>> -- http://tools.ietf.org/html/rfc5389#section-2
>>>>>
>>>>> It seems to me that creating a URI for STUN could encourage its
>>>>> use in
>>>>> environments outside the "more complete solutions that make use of
>>>>> STUN".
>>>>> This seems to be further reason that STUN[S] should not be a URI
>>>>> scheme.
>>>>>
>>>>> I have also suggested that, if registered, the URI scheme
>>>>> registration should
>>>>> carries a "health warning" to this effect, and that it is not
>>>>> suitable for
>>>>> general use that is not part of a "complete NAT traversal
>>>>> solution".  But I
>>>>> also recognize that I do not fully grasp the security
>>>>> implications, and that
>>>>> if those that do know better can agree that there is no potential
>>>>> for creating
>>>>> security risks here, this suggestion may be unnecessary.
>>>>
>>>> This URI scheme does not represent STUN. It represents
>>>> configuration data that
>>>> is used to initialize a protocol machine that utilizes STUN.
>>>>
>>>> This configuration data has to be passed no matter what the format
>>>> of the data
>>>> is - whether it be URI or not.
>>>>
>>>> Thus, I do not think the argument raised is really relevant to the
>>>> context. The
>>>> data will be passed, and registering an URI scheme will cause no
>>>> more and no
>>>> less data to be passed.
>>>>
>>>> Again, my opinion.
>>>>
>>>
>>> If the URI is used only in very constrained contexts, then I agree.
>>>
>>> But the whole point of using a URI is that, due to URI opacity, it
>>> can be used
>>> a a range of contexts where URIs are used.  If it cannot properly be
>>> used in
>>> those other contexts, I have to question if it really is a URI, as
>>> opposed to
>>> a string that happens to look like a URI.
>>
>> The subject of "if it really is an URI" has plagued the whole URI
>> space since
>> day one. My current opinion is that if it looks like an URI, and parses
>> according to the URI spec, it should probably be called an URI.
>>
>> So far, we know of one context where we need this (RTCWEB). It's the
>> first
>> context I know of where the Web and STUN intersect. It's not certain
>> that it'll
>> be the last one.
>>
>>>
>>> I also note that this looks as if it may fall foul of the "confidential
>>> metadata" practice noted in the W3C TAG finding about metadata in URIs
>>> (http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity)
>>
>> That's why we took the "credentials" part out of the URI scheme.
>>


From stpeter@stpeter.im  Thu Aug 15 07:20:47 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D3921F9A78 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z+oxnxLF2urV for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:20:42 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BB98E21E8156 for <ietf@ietf.org>; Thu, 15 Aug 2013 07:20:42 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 54AD3E834E; Thu, 15 Aug 2013 08:23:44 -0600 (MDT)
Message-ID: <520CE3BA.6070706@stpeter.im>
Date: Thu, 15 Aug 2013 08:20:42 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org> <520CA7C1.6080404@alvestrand.no> <520CE029.3070405@ninebynine.org> <520CE14D.6070505@alvestrand.no>
In-Reply-To: <520CE14D.6070505@alvestrand.no>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 14:20:47 -0000

On 8/15/13 8:10 AM, Harald Alvestrand wrote:
> On 08/15/2013 04:05 PM, Graham Klyne wrote:
>> Harald,
>>
>> Briefly:
>>
>> 1. Thanks for the reference,
>>
>> and
>>
>> 2. I misunderstood what you meant by "This is a format for a piece of
>> data".  In light of your clarification, I withdraw my comments 3 & 4. 
>> Identification of the STUN service would appear to be a perfectly
>> reasonable use.
>>
>> ...
>>
>> So the remaining issues from my questions are whether the intended
>> highly constrained use of these services justifies allocating a URI
>> scheme.
>>
>> If the community consensus is that it is of sufficient value, I might
>> suggest an annotation to the scheme registration along the lines of:
>>
>> "This URI scheme is intended for use in very specific NAT traversal
>> environments, and should not be used otherwise on the open Web or
>> Internet."
>>
>> Would such a comment run contrary to your expectations for its use?
> 
> I would prefer to run the comment as "This scheme is intended for use in
> specific environments that involve NAT traversal. Users of the scheme
> need to carefully consider the security properties of the context in
> which they are using it."
> 
> Echoing the warning in the STUN scheme - "use this when you know what
> you're doing only".
> 
> Frankly, like Hadriel indicated, I have no idea whether it will be
> useful in other contexts or not, 

I tend to think not.

> and I'm hesitant to put language that
> seems to claim that we've evaluated all possible contexts 

Agreed.

> and say that
> there aren't other contexts in which it can be useful.

Too many negatives. :-) You are hesitant to say that it won't be useful
in other contexts, or you would prefer to say that it was designed for a
specific contexts and probably wouldn't be useful outside that context?

Peter

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



From harald@alvestrand.no  Thu Aug 15 07:25:16 2013
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 777F021F9B1B for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 IbIr7sjbxSv2 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:24:59 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id D1E3F21F9A2D for <ietf@ietf.org>; Thu, 15 Aug 2013 07:24:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C1C3E39EA6F; Thu, 15 Aug 2013 16:24:47 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dVvjVbY7acM0; Thu, 15 Aug 2013 16:24:47 +0200 (CEST)
Received: from [172.28.249.38] (unknown [74.125.57.89]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id DD5B639E0E1; Thu, 15 Aug 2013 16:24:46 +0200 (CEST)
Message-ID: <520CE4AE.6000403@alvestrand.no>
Date: Thu, 15 Aug 2013 16:24:46 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org> <520CA7C1.6080404@alvestrand.no> <520CE029.3070405@ninebynine.org> <520CE14D.6070505@alvestrand.no> <520CE3BA.6070706@stpeter.im>
In-Reply-To: <520CE3BA.6070706@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Graham Klyne <GK@ninebynine.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 14:25:16 -0000

On 08/15/2013 04:20 PM, Peter Saint-Andre wrote:
> On 8/15/13 8:10 AM, Harald Alvestrand wrote:
>> On 08/15/2013 04:05 PM, Graham Klyne wrote:
>>> Harald,
>>>
>>> Briefly:
>>>
>>> 1. Thanks for the reference,
>>>
>>> and
>>>
>>> 2. I misunderstood what you meant by "This is a format for a piece of
>>> data".  In light of your clarification, I withdraw my comments 3 & 4. 
>>> Identification of the STUN service would appear to be a perfectly
>>> reasonable use.
>>>
>>> ...
>>>
>>> So the remaining issues from my questions are whether the intended
>>> highly constrained use of these services justifies allocating a URI
>>> scheme.
>>>
>>> If the community consensus is that it is of sufficient value, I might
>>> suggest an annotation to the scheme registration along the lines of:
>>>
>>> "This URI scheme is intended for use in very specific NAT traversal
>>> environments, and should not be used otherwise on the open Web or
>>> Internet."
>>>
>>> Would such a comment run contrary to your expectations for its use?
>> I would prefer to run the comment as "This scheme is intended for use in
>> specific environments that involve NAT traversal. Users of the scheme
>> need to carefully consider the security properties of the context in
>> which they are using it."
>>
>> Echoing the warning in the STUN scheme - "use this when you know what
>> you're doing only".
>>
>> Frankly, like Hadriel indicated, I have no idea whether it will be
>> useful in other contexts or not, 
> I tend to think not.
>
>> and I'm hesitant to put language that
>> seems to claim that we've evaluated all possible contexts 
> Agreed.
>
>> and say that
>> there aren't other contexts in which it can be useful.
> Too many negatives. :-) You are hesitant to say that it won't be useful
> in other contexts, or you would prefer to say that it was designed for a
> specific contexts and probably wouldn't be useful outside that context?

I'm hesitant to say that it won't be useful in other contexts - that is,
I'd prefer to say nothing about whether it will be useful elsewhere or not.


Others understand other contexts better than I do; if they come forward
(as Hadriel just did) and say "This is useful to me", I don't want the
draft to say "Sorry, but we decided you can't use it".

>
> Peter
>


From GK@ninebynine.org  Thu Aug 15 02:05:11 2013
Return-Path: <GK@ninebynine.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 1A3DB11E80DE for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 02:05: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyKrkEf-5qVr for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 02:05:06 -0700 (PDT)
Received: from relay13.mail.ox.ac.uk (relay13.mail.ox.ac.uk [129.67.1.166]) by ietfa.amsl.com (Postfix) with ESMTP id A8C4D11E8106 for <ietf@ietf.org>; Thu, 15 Aug 2013 02:05:05 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay13.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1V9tUM-0002Ok-hp; Thu, 15 Aug 2013 10:05:02 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1V9tUM-0005cN-6o; Thu, 15 Aug 2013 10:05:02 +0100
Message-ID: <520C9997.2010601@ninebynine.org>
Date: Thu, 15 Aug 2013 10:04:23 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no>
In-Reply-To: <520BD147.1040505@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Thu, 15 Aug 2013 08:19:05 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 09:05:11 -0000

Hi Harald,

On 14/08/2013 19:49, Harald Alvestrand wrote:
> On 08/13/2013 12:14 AM, Graham Klyne wrote:
[...]
>> But, in a personal capacity, not as designated reviewer, I have to ask *why*
>> this needs to be a URI.  As far as I can tell, it is intended for use only in
>> very constrained environments, where there seems to be little value in having
>> an identifier that can appear in all the contexts where a URI may be recognized.
>>
>> The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 include:
>>
>> "New URI schemes SHOULD have clear utility to the broad Internet community,
>> beyond that available with already registered URI schemes."
>> -- http://tools.ietf.org/html/rfc4395#section-2.1
>>
>> This "utility to the broader community" is not clear to me, but I don't fully
>> understand the intended scope of this protocol, so I could be missing
>> something.  So, in declaring consensus for this specification, I would request
>> that this aspect at least be considered.
>
> I can only give  my personal opinion....
>
> 1) This is a format for a piece of data. This data cannot be expressed using any
> existing URI scheme - indeed, I don't think there exists another well-defined
> textual representation of this piece of data.
>
> 1) This is defining an identifier that will be used in W3C-defined APIs. W3C
> tends to use URIs every time they want a self-defining piece of data with a
> clearly defined structure.
> In the particular API where this is wanted, one wants to have STUN URIs, TURNS
> URIs and TURN URIs passed over the same interface. Thus, keeping with the W3C
> tradition of URIs seems reasonable.
>
> I think this answers the question about "utility to the broader community" to my
> satisfaction - your mileage may differ, of course.

Some thoughts occur to me:

1. My reading was that this is a generic NAT traversal protocol, so the 
requirement here is not Web/W3C specific.  But you do say "used in W3C-defined 
APIs"...

2. If this is being driven by W3C activities, this should probably be flagged 
with W3C TAG.  I'll raise it there.

3. URIs are not generally used as *data* formats, but rather as identifiers for 
resources.  Web architecture and REST principles tend to discourage information 
encoded in URIs in favour of data representation formats.  Cf. 
http://www.w3.org/TR/webarch/#uri-opacity, 
http://www.w3.org/2001/tag/doc/metaDataInURI-31.html

4. If the purpose here is simply to encode data, then there does already exist a 
suitable URI scheme, viz data:.  A new content type can be defined to actually 
encode the required data, and the whole be wrapped in a data: URI.  This 
approach has the advantage that alternative mechanisms (other than URIs) can be 
used to transfer the traversal data if required (though that may be moot in the 
very restricted intended scope of deployment for stun:, etc.)

>>
>> ...
>>
>> Further, according to http://tools.ietf.org/html/rfc5389 it appears that there
>> are security considerations with regard to the STUN protocol that it should
>> not be used in isolation:
>> [[
>>    Classic STUN also had a security vulnerability -- attackers could
>>    provide the client with incorrect mapped addresses under certain
>>    topologies and constraints, and this was fundamentally not solvable
>>    through any cryptographic means.  Though this problem remains with
>>    this specification, those attacks are now mitigated through the use
>>    of more complete solutions that make use of STUN.
>>
>>    For these reasons, this specification obsoletes RFC 3489, and instead
>>    describes STUN as a tool that is utilized as part of a complete NAT
>>    traversal solution.
>> ]]
>> -- http://tools.ietf.org/html/rfc5389#section-2
>>
>> It seems to me that creating a URI for STUN could encourage its use in
>> environments outside the "more complete solutions that make use of STUN".
>> This seems to be further reason that STUN[S] should not be a URI scheme.
>>
>> I have also suggested that, if registered, the URI scheme registration should
>> carries a "health warning" to this effect, and that it is not suitable for
>> general use that is not part of a "complete NAT traversal solution".  But I
>> also recognize that I do not fully grasp the security implications, and that
>> if those that do know better can agree that there is no potential for creating
>> security risks here, this suggestion may be unnecessary.
>
> This URI scheme does not represent STUN. It represents configuration data that
> is used to initialize a protocol machine that utilizes STUN.
>
> This configuration data has to be passed no matter what the format of the data
> is - whether it be URI or not.
>
> Thus, I do not think the argument raised is really relevant to the context. The
> data will be passed, and registering an URI scheme will cause no more and no
> less data to be passed.
>
> Again, my opinion.
>

If the URI is used only in very constrained contexts, then I agree.

But the whole point of using a URI is that, due to URI opacity, it can be used a 
a range of contexts where URIs are used.  If it cannot properly be used in those 
other contexts, I have to question if it really is a URI, as opposed to a string 
that happens to look like a URI.

I also note that this looks as if it may fall foul of the "confidential 
metadata" practice noted in the W3C TAG finding about metadata in URIs 
(http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity)

#g
--

From GK@ninebynine.org  Thu Aug 15 07:05:58 2013
Return-Path: <GK@ninebynine.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 4D5F321F9A57 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:05:55 -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 zbogBdVaP6Yz for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 07:05:50 -0700 (PDT)
Received: from relay11.mail.ox.ac.uk (relay11.mail.ox.ac.uk [129.67.1.162]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC3721E8145 for <ietf@ietf.org>; Thu, 15 Aug 2013 07:05:45 -0700 (PDT)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay11.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1V9yBK-0006bm-cY; Thu, 15 Aug 2013 15:05:42 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1V9yBK-0006f6-4T; Thu, 15 Aug 2013 15:05:42 +0100
Message-ID: <520CE029.3070405@ninebynine.org>
Date: Thu, 15 Aug 2013 15:05:29 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org> <520CA7C1.6080404@alvestrand.no>
In-Reply-To: <520CA7C1.6080404@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Thu, 15 Aug 2013 08:19:16 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 14:06:01 -0000

Harald,

Briefly:

1. Thanks for the reference,

and

2. I misunderstood what you meant by "This is a format for a piece of data".  In 
light of your clarification, I withdraw my comments 3 & 4.  Identification of 
the STUN service would appear to be a perfectly reasonable use.

...

So the remaining issues from my questions are whether the intended highly 
constrained use of these services justifies allocating a URI scheme.

If the community consensus is that it is of sufficient value, I might suggest an 
annotation to the scheme registration along the lines of:

"This URI scheme is intended for use in very specific NAT traversal 
environments, and should not be used otherwise on the open Web or Internet."

Would such a comment run contrary to your expectations for its use?

#g
--


On 15/08/2013 11:04, Harald Alvestrand wrote:
> On 08/15/2013 11:04 AM, Graham Klyne wrote:
>> Hi Harald,
>>
>> On 14/08/2013 19:49, Harald Alvestrand wrote:
>>> On 08/13/2013 12:14 AM, Graham Klyne wrote:
>> [...]
>>>> But, in a personal capacity, not as designated reviewer, I have to ask *why*
>>>> this needs to be a URI.  As far as I can tell, it is intended for use only in
>>>> very constrained environments, where there seems to be little value in having
>>>> an identifier that can appear in all the contexts where a URI may be
>>>> recognized.
>>>>
>>>> The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 include:
>>>>
>>>> "New URI schemes SHOULD have clear utility to the broad Internet community,
>>>> beyond that available with already registered URI schemes."
>>>> -- http://tools.ietf.org/html/rfc4395#section-2.1
>>>>
>>>> This "utility to the broader community" is not clear to me, but I don't fully
>>>> understand the intended scope of this protocol, so I could be missing
>>>> something.  So, in declaring consensus for this specification, I would request
>>>> that this aspect at least be considered.
>>>
>>> I can only give  my personal opinion....
>>>
>>> 1) This is a format for a piece of data. This data cannot be expressed using any
>>> existing URI scheme - indeed, I don't think there exists another well-defined
>>> textual representation of this piece of data.
>>>
>>> 1) This is defining an identifier that will be used in W3C-defined APIs. W3C
>>> tends to use URIs every time they want a self-defining piece of data with a
>>> clearly defined structure.
>>> In the particular API where this is wanted, one wants to have STUN URIs, TURNS
>>> URIs and TURN URIs passed over the same interface. Thus, keeping with the W3C
>>> tradition of URIs seems reasonable.
>>>
>>> I think this answers the question about "utility to the broader community" to my
>>> satisfaction - your mileage may differ, of course.
>>
>> Some thoughts occur to me:
>>
>> 1. My reading was that this is a generic NAT traversal protocol, so the
>> requirement here is not Web/W3C specific.  But you do say "used in W3C-defined
>> APIs"...
>
> Truth in advertising: One W3C-defined API.
> The specific reference:
>
> http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-members
>
>>
>> 2. If this is being driven by W3C activities, this should probably be flagged
>> with W3C TAG.  I'll raise it there.
>>
>> 3. URIs are not generally used as *data* formats, but rather as identifiers
>> for resources.  Web architecture and REST principles tend to discourage
>> information encoded in URIs in favour of data representation formats.  Cf.
>> http://www.w3.org/TR/webarch/#uri-opacity,
>> http://www.w3.org/2001/tag/doc/metaDataInURI-31.html
>
> Well, it is. The data encoded is the identification of a STUN server, which is a
> resource.
>
>>
>> 4. If the purpose here is simply to encode data, then there does already exist
>> a suitable URI scheme, viz data:.  A new content type can be defined to
>> actually encode the required data, and the whole be wrapped in a data: URI.
>> This approach has the advantage that alternative mechanisms (other than URIs)
>> can be used to transfer the traversal data if required (though that may be
>> moot in the very restricted intended scope of deployment for stun:, etc.)
>
> Yes, but why?
>
>>
>>>>
>>>> ...
>>>>
>>>> Further, according to http://tools.ietf.org/html/rfc5389 it appears that there
>>>> are security considerations with regard to the STUN protocol that it should
>>>> not be used in isolation:
>>>> [[
>>>>    Classic STUN also had a security vulnerability -- attackers could
>>>>    provide the client with incorrect mapped addresses under certain
>>>>    topologies and constraints, and this was fundamentally not solvable
>>>>    through any cryptographic means.  Though this problem remains with
>>>>    this specification, those attacks are now mitigated through the use
>>>>    of more complete solutions that make use of STUN.
>>>>
>>>>    For these reasons, this specification obsoletes RFC 3489, and instead
>>>>    describes STUN as a tool that is utilized as part of a complete NAT
>>>>    traversal solution.
>>>> ]]
>>>> -- http://tools.ietf.org/html/rfc5389#section-2
>>>>
>>>> It seems to me that creating a URI for STUN could encourage its use in
>>>> environments outside the "more complete solutions that make use of STUN".
>>>> This seems to be further reason that STUN[S] should not be a URI scheme.
>>>>
>>>> I have also suggested that, if registered, the URI scheme registration should
>>>> carries a "health warning" to this effect, and that it is not suitable for
>>>> general use that is not part of a "complete NAT traversal solution".  But I
>>>> also recognize that I do not fully grasp the security implications, and that
>>>> if those that do know better can agree that there is no potential for creating
>>>> security risks here, this suggestion may be unnecessary.
>>>
>>> This URI scheme does not represent STUN. It represents configuration data that
>>> is used to initialize a protocol machine that utilizes STUN.
>>>
>>> This configuration data has to be passed no matter what the format of the data
>>> is - whether it be URI or not.
>>>
>>> Thus, I do not think the argument raised is really relevant to the context. The
>>> data will be passed, and registering an URI scheme will cause no more and no
>>> less data to be passed.
>>>
>>> Again, my opinion.
>>>
>>
>> If the URI is used only in very constrained contexts, then I agree.
>>
>> But the whole point of using a URI is that, due to URI opacity, it can be used
>> a a range of contexts where URIs are used.  If it cannot properly be used in
>> those other contexts, I have to question if it really is a URI, as opposed to
>> a string that happens to look like a URI.
>
> The subject of "if it really is an URI" has plagued the whole URI space since
> day one. My current opinion is that if it looks like an URI, and parses
> according to the URI spec, it should probably be called an URI.
>
> So far, we know of one context where we need this (RTCWEB). It's the first
> context I know of where the Web and STUN intersect. It's not certain that it'll
> be the last one.
>
>>
>> I also note that this looks as if it may fall foul of the "confidential
>> metadata" practice noted in the W3C TAG finding about metadata in URIs
>> (http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity)
>
> That's why we took the "credentials" part out of the URI scheme.
>

From sm@resistor.net  Thu Aug 15 10:41:51 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5927911E81FB for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 10:41:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.258
X-Spam-Level: 
X-Spam-Status: No, score=-102.258 tagged_above=-999 required=5 tests=[AWL=0.341, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z0baVJ-YYSt5 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 10:41:49 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 570BF11E8200 for <ietf@ietf.org>; Thu, 15 Aug 2013 10:41:49 -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 r7FHfhAK023304 for <ietf@ietf.org>; Thu, 15 Aug 2013 10:41:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376588508; bh=GnCD2B5K/NDa7bJWQFmEtJEnoT1gY5xeafSnAxA8TGM=; h=Date:To:From:Subject:In-Reply-To:References; b=Y/wfpHaF4dxiJoK6vyC28vmZzdrvVrGomWgA7rMt0FCIMgu2f00yHjpA6v+Y5hHwv ciFnzF0m9Ysbzglim8RG0NcWe6mhb7pf1S+OZcJ7Fl19JXxXmZ0i2LdrXJVmHdW03F CIItzbodUTyBIpVfTPDpROJPHAQszEDINCj4GwCA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376588508; i=@resistor.net; bh=GnCD2B5K/NDa7bJWQFmEtJEnoT1gY5xeafSnAxA8TGM=; h=Date:To:From:Subject:In-Reply-To:References; b=nsD5C7s17VKbkZOb7GZzKjciHYNnp5nbc3pA+yUdf8qGcDgUnsog1Z07bYY0jg342 gPrTbGGOIszKQYhR82ry/cZl/HnYCNMjhYL7A9rvKYbxr6XAGaeggMU+hkanUI0Qgl TgwCuEKkL9vbX8zf5/Bu+pG1lk5gZRCzBCn8Yi6Q=
Message-Id: <6.2.5.6.2.20130815092301.0b86a398@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Aug 2013 10:13:36 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
In-Reply-To: <20130815144121.15477.78141.idtracker@ietfa.amsl.com>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 17:41:51 -0000

At 07:41 15-08-2013, The IESG wrote:
>The IESG has received a request from the Reputation Services WG (repute)
>to consider the following document:
>- 'A Reputation Query Protocol'
>   <draft-ietf-repute-query-http-09.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-08-29. Exceptionally, comments may be

The draft-iet-repute-model reference is a down-ref.

   "A server receiving a query about an application it does not
    recognize or explicitly support support (e.g., by virtue of
    private agreements or experimental extensions) MUST return a
    404 error code."

There is a typo: "support support".

Are there other cases where a 404 is appropriate?  I am asking the 
question as there is a string of proposals built upon RFC 2616 which 
attempt to use HTTP status codes to communicate errors for the 
layered protocol.

In Section 3.2:

   "and SHOULD include an Expires field (see Section 14.21 of [HTTP])
    indicating a duration for which the template is to be considered
    valid by clients and not re-queried."

Why is this a RFC 2119 SHOULD?  There is a "SHOULD NOT" following 
that paragraph with a "don't query for a day if there isn't an 
Expires field".  Wouldn't it be easier to have "MUST include the 
Expires field"?


   "The template file might contain more than one template.  Such a file
    MUST have each template separated by a newline (ASCII 0x0D)
    character."

As this is line oriented it may be better to have CRLF.

In Section 3.3:

   "A server SHOULD include support for providing service over HTTP"

Is there a case where the service with work if the server does not 
support HTTP?

In Section 5:

   "The reputation service itself will use HTTP or other transport
    methods to issue queries and receive replies.  Those protocols have
    registered URI schemes and, as such, presumably have documented
    security considerations."

This is odd.  What other protocols are there to retrieve the URI template?

If I understood the draft, the Proposed Standard angle is:

   http://{service}/{application}/{subject}/{assertion}

with a "application/reputon+json" response.  Why should that be a 
Proposed Standard?

Regards,
-sm 


From sm@resistor.net  Thu Aug 15 10:41:55 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD2111E8205 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 10:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.296
X-Spam-Level: 
X-Spam-Status: No, score=-102.296 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czGmihl08a6U for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 10:41:55 -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 5B52C11E8203 for <ietf@ietf.org>; Thu, 15 Aug 2013 10:41:55 -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 r7FHfhAM023304 for <ietf@ietf.org>; Thu, 15 Aug 2013 10:41:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376588513; bh=UlrqaeJbFeUWzoxcun9jOaElqU5LXL/7t9wqBwiE47s=; h=Date:To:From:Subject:In-Reply-To:References; b=qAT7n856rQ/NmkyEdj0IXLBTu5jslwfntLEI7hC2TUeKNoywnTw6l1+LFYkybeBX3 Z+wkWDp6ptd7iSjWxWIk3jy3/g8kivv7dTDVzjGRk28VnZQOJ9tT/KrKdzvsmMot1e SYdZDog32L0EIsrEOo3ztU2/PUpok71Ky0ifHfh0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376588513; i=@resistor.net; bh=UlrqaeJbFeUWzoxcun9jOaElqU5LXL/7t9wqBwiE47s=; h=Date:To:From:Subject:In-Reply-To:References; b=Yb0qXPiuNwOR/vix0ksiebRawOUHDrCROP3rKwjEyw70C+mUZXt/DTd4hUoowMmIj 4+D40WrnJtWv6a0+m3NImJMh63KvuEJ/V4SfaLwYKz27YA3Fu8x7vQHmD9weSQRACx yQOeyWGqyTvh7+8H2CABJG+/J2R824DBlXpasijM=
Message-Id: <6.2.5.6.2.20130815101412.0b86a108@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Aug 2013 10:24:27 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-email-identifiers-08.txt> (A Reputation Response Set for Email Identifiers) to Proposed Standard
In-Reply-To: <20130815144348.25999.91573.idtracker@ietfa.amsl.com>
References: <20130815144348.25999.91573.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 17:41:55 -0000

At 07:43 15-08-2013, The IESG wrote:
>The IESG has received a request from the Reputation Services WG (repute)
>to consider the following document:
>- 'A Reputation Response Set for Email Identifiers'
>   <draft-ietf-repute-email-identifiers-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 2013-08-29. Exceptionally, comments may be

draft-ietf-repute-model is a down-ref.  I suggest referencing the 
updated SPF specification as that specification is said to fix some 
issues in RFC 4408.

Why is DKIM and SPF normatively referenced while SMTP is an 
informative reference?

Section 5 states that the draft "is primarily an IANA action and 
doesn't describe any protocols or protocol elements".  Why is the 
intended status "Proposed Standard"?

Regards,
-sm 


From sm@resistor.net  Thu Aug 15 10:42:02 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F8E11E820E for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 10:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.326
X-Spam-Level: 
X-Spam-Status: No, score=-102.326 tagged_above=-999 required=5 tests=[AWL=0.273, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NpRv-OHtOfM for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 10:42:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 596DD11E820B for <ietf@ietf.org>; Thu, 15 Aug 2013 10:42:00 -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 r7FHfhAO023304 for <ietf@ietf.org>; Thu, 15 Aug 2013 10:41:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376588518; bh=Pue+zj7rvNAzsTZ8jIhxh+4wIcPzwYq7izVfWTc8Tq0=; h=Date:To:From:Subject:In-Reply-To:References; b=vigjUEpa8MwFEXpF89yb9dV3Asn4Lk8wigoTyVBSTUcuTXbJvhMHNhFQxEhEWJqDC pMIJEqAV0hUIHEZ5G6eAIiTRtZF4eIbIoDJQjHNg9qVgiIaiXwi8+Um3Gew5TpOiRn myNkEVzGM2D1sEKas6a+MP20keq6rxNK3IAVI8CM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376588518; i=@resistor.net; bh=Pue+zj7rvNAzsTZ8jIhxh+4wIcPzwYq7izVfWTc8Tq0=; h=Date:To:From:Subject:In-Reply-To:References; b=RVnPFk79VlJoUJtEY27oCI6t6H5HWTYQ61QlHqbQ6mRugTe3l73tSvc2v21yH3INf jZsY0G8E4zY1B5oS2l7vtDcB6FLU8ScjQcykRMIjeCbxVQ686YzRgH1glQEjQyKB5C Zrf+720H6kNAHOxVSnGjsRYrzs1YGm+7bl/3wTCQ=
Message-Id: <6.2.5.6.2.20130815102618.0b86a4e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Aug 2013 10:40:58 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-media-type-10.txt> (A Media Type for Reputation Interchange) to Proposed Standard
In-Reply-To: <20130815144419.712.35650.idtracker@ietfa.amsl.com>
References: <20130815144419.712.35650.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 17:42:03 -0000

At 07:44 15-08-2013, The IESG wrote:
>The IESG has received a request from the Reputation Services WG (repute)
>to consider the following document:
>- 'A Media Type for Reputation Interchange'
>   <draft-ietf-repute-media-type-10.txt> as Proposed Standard
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-08-29. Exceptionally, comments may be

 From Section 3.1:

    "expires:  A timestamp indicating a time beyond which the score
       reported is likely not to be valid.  Expressed as the number of
       seconds since January 1, 1970 00:00 UTC.  See Section 5 for
       discussion."

And Section 5:

   'A reputon can contain an "expires" field indicating a timestamp after
    which the client SHOULD NOT use the rating it contains, and SHOULD'

The "expires" field uses "HTTP-date".  It is easier to code for one 
timestamp format instead of two (see Unix timestamp in Section 3.1).

In Section 3.1:

   "An application service provider might operate with an enhanced form
    of common services, which might in turn prompt development and
    reporting of specialized reputation information."

I don't see anything actionable in the above.

Why was "specification required" chosen for the Reputation 
Applications Registry?

Regards,
-sm






From sm@resistor.net  Thu Aug 15 11:25:20 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52ED321F9EEB for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 11:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.351
X-Spam-Level: 
X-Spam-Status: No, score=-102.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-LNy+lI4v7W for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 11:25:19 -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 B5BAA21F9C68 for <ietf@ietf.org>; Thu, 15 Aug 2013 11:25:18 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7FIPCQE003777 for <ietf@ietf.org>; Thu, 15 Aug 2013 11:25:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376591117; bh=Li7CeCkODgwHwZ8gqEehtAneaoQCtlOampTY74N2GJQ=; h=Date:To:From:Subject:In-Reply-To:References; b=oGp2S3qhXFFWIQLsrisvGFVh3sGuL0vsdff9M2dX+6IetzNldNFYEYDTZVVWCtzLx 6LZSxhbRoC5CrNEsiE3cOIYnBtvOTY8pMMT3qnKJK5MQA26UfW2YSC15r6eQzdNCrc OK2659NbaGLIWtQw+gwGVdU1dN0z53o6+rDxOsxc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376591117; i=@resistor.net; bh=Li7CeCkODgwHwZ8gqEehtAneaoQCtlOampTY74N2GJQ=; h=Date:To:From:Subject:In-Reply-To:References; b=aNrf0SHCP43PqrFnixIFoiwmWlfj+zjefHaLquSLiBIn2PVmaO5D1xya2WkqdVxwA E+lnpNTedD6L0dkfrj8WcLsUatGdCkF+NZR6QDLPSLaijmCcdv3mOrJ2sSBx6w8EQC ZKdb113ZSLoxyk8vBohryopiMyyKIrIMCMxPliw4=
Message-Id: <6.2.5.6.2.20130815104802.0b87f9b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Aug 2013 11:24:51 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-model-07.txt> (A Model for Reputation Reporting) to Informational RFC
In-Reply-To: <20130815144507.22504.36661.idtracker@ietfa.amsl.com>
References: <20130815144507.22504.36661.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 18:25:20 -0000

At 07:45 15-08-2013, The IESG wrote:
>The IESG has received a request from the Reputation Services WG (repute)
>to consider the following document:
>- 'A Model for Reputation Reporting'
>   <draft-ietf-repute-model-07.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-08-29. Exceptionally, comments may be

The Privacy Considerations Section focuses on data in transit and 
collection of data only.  Section 8.1 mentions protecting the data 
from "unauthorized access and viewing".  That would only be 
unauthorized viewing while the data is in transit.

I don't know whether people overlook this; the queries leak out 
information.  Information which the user might consider as private is 
sent out without the person's knowledge.  I suggest pushing that 
discussion to the specification which defines the identity (e.g. 
draft-ietf-repute-email-identifiers-08).

As a general comment I would say that the issue is less about privacy 
and more about reputation.  There is a saying: Tell me what you read 
and I will tell you who you are.

Regards,
-sm 


From sm@resistor.net  Thu Aug 15 12:15:02 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55F0521F9A3B; Thu, 15 Aug 2013 12:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[AWL=0.227, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q766sThODitZ; Thu, 15 Aug 2013 12:15: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 B7BDA21F9017; Thu, 15 Aug 2013 12:15:01 -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 r7FJEt50005247; Thu, 15 Aug 2013 12:14:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376594101; bh=ksZmZyR6PXWKJd5svNlf7n7kpl0EadS0qf3EtiptbHg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UWyvdMpbUrZcTTJZxKHI4VderIe2QyoUmJXUUL8lAwSTSw4fADsL/Nmx+iDuNjQ3Z JhaixO7lN7SRPy0aJ3j4IHBVdUNP3ufsRBO3SsYD3AWyJCyLg31KjemNkVA5gAbTIx Bb2iQzlXTcfRPCoNSChod/MgKs6AuMcvn0VbIdeE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376594101; i=@resistor.net; bh=ksZmZyR6PXWKJd5svNlf7n7kpl0EadS0qf3EtiptbHg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=P/8qA7TmJjuCxIbHvs5BhhUqpSH6tdAK9ruM6JxELwEv642FECMEcGnl1mJFEIbm7 JtWut/zh0WzJ1hZLiozs18r/EPdehlD3YtGBVpqX5W4rQI2fwgFMyqs7V0yQN6HnnJ IhzDjSG9P07IgtPcnO+21MgrJyTWNnYUJIpvo33A=
Message-Id: <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Aug 2013 12:06:12 -0700
To: iab@iab.org
From: SM <sm@resistor.net>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
In-Reply-To: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.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, 15 Aug 2013 19:15:02 -0000

At 11:48 14-08-2013, IAB Chair wrote:
This is a call for review of "List of Internet Official Protocol 
Standards: Replaced by an Online Database" prior to potential 
approval as an IAB stream RFC.

The document is available for inspection here: 
https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/

 From Section 2.1 of RFC 2026:

   'The status of Internet protocol and service specifications is
    summarized periodically in an RFC entitled "Internet Official
    Protocol Standards".'

My guess is that draft-rfced-rfcxx00-retired cannot update RFC 
2026.  Does the IAB have any objection if I do something about that?

 From Section 3:

   "This document formally retires STD 1.  Identifier STD 1 will not be
    re-used unless there is a future need to publish periodic snapshots
    of the Standards Track documents (i.e., unless the documentation is
    resumed)."

The document argues that STD 1 is historic as there is an online list 
now.  The above reserves an option to restart periodic snapshots if 
there is a future need.  I suggest removing that option as I presume 
that the IAB has thought carefully about the long term evolution of 
the Series before taking the decision to retire STD 1.

Regards,
-sm


From yaronf.ietf@gmail.com  Thu Aug 15 12:26:30 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CB921F9D2E for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 12:26: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 d7ya1Jx9isyy for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 12:26:29 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4A56111E815E for <ietf@ietf.org>; Thu, 15 Aug 2013 12:26:28 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b13so888187wgh.7 for <ietf@ietf.org>; Thu, 15 Aug 2013 12:26:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=t/Zu7YfFgyrcc6Kw+QfxTIT8Ob/2dnsIpW0Umf+azdY=; b=Cmi6yAsQnyu/5y8KCFJNyTHzM12obdgXmh2DTrkorJTUeng4X75VnygPtqt4Ph23QX ONIz8pZSmZP8BfR54hYhYY6yhQQkQUGs5nZHzBDzkv4pQTl7Z9ERt0xdgA/Fy5S6OC/3 DiIRmlLNpWEhBXZe28MyzFi243292+WvIziJigBpzgTbpGnIn7Ntbsjr7zm2Rke0+dei TyDnJPmkvq+x7R+1FTcoXmlHYGRgxcUjGA+W+DcmaTAPmS0zHjWHIuHKpjWUyEaj3wYj XDzf487nuWi6/70cSC3yLyyE3aROSMc0Yw55Yvx5BFXhEfu+Pjb/rRqdalnecq3aMwm6 Jgbw==
X-Received: by 10.180.211.206 with SMTP id ne14mr2795996wic.30.1376594787475;  Thu, 15 Aug 2013 12:26:27 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-181-180-40.red.bezeqint.net. [79.181.180.40]) by mx.google.com with ESMTPSA id a4sm4493905wik.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 Aug 2013 12:26:27 -0700 (PDT)
Message-ID: <520D2B60.3000301@gmail.com>
Date: Thu, 15 Aug 2013 22:26:24 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Hildebrand <hildjj@cursive.net>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <CE300BA7.15704%joe@cursive.net>
In-Reply-To: <CE300BA7.15704%joe@cursive.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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, 15 Aug 2013 19:26:30 -0000

Hi Joe,

please see below.

Thanks,
	Yaron

On 2013-08-14 01:20, Joe Hildebrand wrote:
> (leaving a full response to the authors, and responding to a couple of
> points I found interesting)
>
> On 8/13/13 3:11 PM, "Yaron Sheffer" <yaronf.ietf@gmail.com> wrote:
>
>> - Arrays are prefixed by the number of elements but not by their length
>> in bytes. And elements need not be all of the same size. So you cannot
>> skip the array without fully parsing every last element. IIRC this is a
>> major disadvantage compared to ASN.1 encodings.
>
>> - And similarly to arrays, you cannot skip a map element without deep
>> parsing of the element.
>
> One of the reasons why I like the CBOR tag applied to a byte stream is
> that
> it can be used to skip parsing on entire sections (no matter their
> underlying types) in processors that don't need to understand that section.
>

I suppose you mean you don't understand the section at a semantic level 
(e.g. you don't understand the map "section-7") but you do need to parse 
every last data item in the section before you know its byte length. So 
at a syntactic level you don't skip anything.

>> I would reserve a part of the tag space
>> for "private" application-specific allocations.
>
> I like that.
>
>> - One tag value you may want to consider adding is "critical" in the
>> security sense of the word, i.e., an application is required to fail if
>> it does not understand the value (probably best applied to map keys).
>
> That's also an interesting idea.  If included, it would be best to add
> this as soon as possible, and ensure that it gets added to the test
> vectors, to avoid problems we've had in the past with inadequate
> implementations of criticality.

I agree this needs to go into the base spec ASAP, so that it really is 
treated correctly. And it certainly cannot be a later extension, as Paul 
suggested in another message.

Also note that "critical" can be applied to all sorts of data, including 
data items that are already tagged! I think this is not allowed for 
according to the spec. But the new "self-describing" tag that appeared 
in -05 suffers from the very same problem. It can be applied to things 
that need other tags. So supporting multiple tags may be a good idea 
after all.

>
>> - In the "diagnostic notation", I suggest to use symbolic values rather
>> than integers for tags, e.g. TAG_URI.
>
> How would you deal with tags that your implementation doesn't understand,
> then?
>

That's simple, especially if the diagnostic notation is really "write 
only" as Paul suggests. Just use the integer in this case.

From paul.hoffman@vpnc.org  Thu Aug 15 12:57:19 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B026011E80F5 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 12:57: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 iGts8A21OSjN for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 12:57:19 -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 1E95D21F96B1 for <ietf@ietf.org>; Thu, 15 Aug 2013 12:57:19 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r7FJvDMC016868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 15 Aug 2013 12:57:14 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: CBOR and a tag for "critical"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <520D2B60.3000301@gmail.com>
Date: Thu, 15 Aug 2013 12:57:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1F240A5-C02F-4E45-862B-4A12376A85FF@vpnc.org>
References: <CE300BA7.15704%joe@cursive.net> <520D2B60.3000301@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
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, 15 Aug 2013 19:57:19 -0000

On Aug 15, 2013, at 12:26 PM, Yaron Sheffer <yaronf.ietf@gmail.com> =
wrote:

>>> - One tag value you may want to consider adding is "critical" in the
>>> security sense of the word, i.e., an application is required to fail =
if
>>> it does not understand the value (probably best applied to map =
keys).
>>=20
>> That's also an interesting idea.  If included, it would be best to =
add
>> this as soon as possible, and ensure that it gets added to the test
>> vectors, to avoid problems we've had in the past with inadequate
>> implementations of criticality.
>=20
> I agree this needs to go into the base spec ASAP, so that it really is =
treated correctly. And it certainly cannot be a later extension, as Paul =
suggested in another message.

You and I have been in IETF security WGs together for over a decade, and =
we have seen how often implementers have gotten "critical" wrong =
regardless of the wording in the various specs. They disagree about what =
it means to "understand" an extension, to "be able to process" an =
extension, and so on. They are completely sure that people who disagree =
with them are obviously wrong, even in the face of multiple examples by =
seasoned programmers.

Someone joked at the mic in some WG years ago that the critical bit was =
called that because we should be criticized for how poorly it is =
understood.

Instead of thinking "this time I'm sure we'll get everyone to understand =
this", it might be better to have an extended discussion which possibly =
ends in multiple tags with varying descriptions.

> Also note that "critical" can be applied to all sorts of data, =
including data items that are already tagged! I think this is not =
allowed for according to the spec.

That is incorrect. Please point to the area where you think it says that =
so we can make it clearer.

--Paul Hoffman=

From kent@bbn.com  Thu Aug 15 13:05:05 2013
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD4121F994C; Thu, 15 Aug 2013 13:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.518
X-Spam-Level: 
X-Spam-Status: No, score=-106.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MR3E+1z9E4C4; Thu, 15 Aug 2013 13:04:57 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id A2AF421F9798; Thu, 15 Aug 2013 13:04:57 -0700 (PDT)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:53876) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1VA3my-0007db-3Y; Thu, 15 Aug 2013 16:04:56 -0400
Message-ID: <520D3467.1080107@bbn.com>
Date: Thu, 15 Aug 2013 16:04:55 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslr4dwcbmh.fsf@mit.edu>
In-Reply-To: <tslr4dwcbmh.fsf@mit.edu>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 20:05:06 -0000

David,

I agree with Sam here. The key table is analogous to the SPD in 4301, 
but not
the PAD.

Another doc being developed in the KARP WG does have a "Routing 
Authentication Policy
Database" (RAPD) that incorporates aspects of the PAD from 4301, as well 
as some
SPD fields.

Steve

From touch@isi.edu  Thu Aug 15 13:18:30 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B50611E8196 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:18:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WgSfLcJ2MLqd for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:18:23 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 38C3C11E80FF for <ietf@ietf.org>; Thu, 15 Aug 2013 13:18:23 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r7FKI1Jf026547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Aug 2013 13:18:01 -0700 (PDT)
Message-ID: <520D3779.4050106@isi.edu>
Date: Thu, 15 Aug 2013 13:18:01 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com>
In-Reply-To: <52069498.1000604@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 20:18:30 -0000

On 8/10/2013 12:29 PM, Wesley Eddy wrote:
> On 8/10/2013 1:43 AM, Martin Sustrik wrote:
>> Hi all,
>>
>> Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol used?
>> Is it the case that there are inetd daemons in TCPMUX mode running
>> everywhere, or can it be rather considered a dead protocol?
>>
>> Specifically, if I implement a new TCPMUX daemon how likely I am to
>> clash with an existing TCPMUX daemon listening on port 1?
>>
>
>
> It's in the FreeBSD inetd, among others, but to to my
> knowledge, nobody actually turns it on.  There are
> probably security issues.

There are semantics issues to; see draft-touch-tcp-portnames-00 for 
information (this is being revised for resubmission shortly, FWIW).

Joe

From yaronf.ietf@gmail.com  Thu Aug 15 13:19:27 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD19211E81B5 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id immrmpdo6OVt for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:19:27 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D98AF11E8177 for <ietf@ietf.org>; Thu, 15 Aug 2013 13:19:26 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id q58so954888wes.20 for <ietf@ietf.org>; Thu, 15 Aug 2013 13:19:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=RCA5Yx+syHeeRb6jFsf1xGsz7hkftJin0rks06q3hro=; b=mltqzcB669lVke/4F0spfbXAyG4E+K8rlRQqkYu18WuLzN/hD9k8mS1tIVZSQ/D3iz WsyvniYQUgW8o9ML/YaJd6zw6rtSo9OK9IoM7T9U2O7MVrIcPke0giBuFjz/ztBtcicy Y6T2g34LIr+i7QeVteyRDq0wvXLBe03boYZqwVVfL2lENkYC1wCXKR1i4sFUUZV/WFL4 GGp2ovGoHnTb7YpmyoToy+qFml29S8zo4ySOKbRKHVubGEUj6hc+0vZnSiuRHUC/uQEk yzng7msA/MFCtqg6q6/EtAfFr7WROCsXDQ+F/c+DjQ5u4D3nkjdi2jU5KPKN9ebnsbir GCkQ==
X-Received: by 10.180.75.164 with SMTP id d4mr2818126wiw.58.1376597966055; Thu, 15 Aug 2013 13:19:26 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-181-180-40.red.bezeqint.net. [79.181.180.40]) by mx.google.com with ESMTPSA id li9sm4715980wic.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 Aug 2013 13:19:25 -0700 (PDT)
Message-ID: <520D37CB.8040305@gmail.com>
Date: Thu, 15 Aug 2013 23:19:23 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: CBOR and a tag for "critical"
References: <CE300BA7.15704%joe@cursive.net> <520D2B60.3000301@gmail.com> <A1F240A5-C02F-4E45-862B-4A12376A85FF@vpnc.org>
In-Reply-To: <A1F240A5-C02F-4E45-862B-4A12376A85FF@vpnc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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, 15 Aug 2013 20:19:27 -0000

Hi Paul,

I am quite sure that I fully understand the semantics of "critical" 
(probably erroneously), so I'm not the right person to clarify the 
various meanings of the word. I would appreciate a proposal.

Just for the record, my "critical" means: the reader must be able to 
process the data item according to its specification, not just 
syntactically but also semantically, and must fail otherwise. There may 
still be contained non-critical data items that are NOT understood by 
the reader.

Sec. 2.4 consistently mentions "tag" in the singular. For example, the 
first sentence could be "a data item can optionally be preceded by one 
or more tags" - but it isn't.

Thanks,
	Yaron


On 2013-08-15 22:57, Paul Hoffman wrote:
> On Aug 15, 2013, at 12:26 PM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
>
>>>> - One tag value you may want to consider adding is "critical" in the
>>>> security sense of the word, i.e., an application is required to fail if
>>>> it does not understand the value (probably best applied to map keys).
>>>
>>> That's also an interesting idea.  If included, it would be best to add
>>> this as soon as possible, and ensure that it gets added to the test
>>> vectors, to avoid problems we've had in the past with inadequate
>>> implementations of criticality.
>>
>> I agree this needs to go into the base spec ASAP, so that it really is treated correctly. And it certainly cannot be a later extension, as Paul suggested in another message.
>
> You and I have been in IETF security WGs together for over a decade, and we have seen how often implementers have gotten "critical" wrong regardless of the wording in the various specs. They disagree about what it means to "understand" an extension, to "be able to process" an extension, and so on. They are completely sure that people who disagree with them are obviously wrong, even in the face of multiple examples by seasoned programmers.
>
> Someone joked at the mic in some WG years ago that the critical bit was called that because we should be criticized for how poorly it is understood.
>
> Instead of thinking "this time I'm sure we'll get everyone to understand this", it might be better to have an extended discussion which possibly ends in multiple tags with varying descriptions.
>
>> Also note that "critical" can be applied to all sorts of data, including data items that are already tagged! I think this is not allowed for according to the spec.
>
> That is incorrect. Please point to the area where you think it says that so we can make it clearer.
>
> --Paul Hoffman
>

From paul.hoffman@vpnc.org  Thu Aug 15 13:36:07 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7A211E81D5 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjUrm04eJdu2 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:36:06 -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 E944B11E8181 for <ietf@ietf.org>; Thu, 15 Aug 2013 13:36:05 -0700 (PDT)
Received: from [165.227.249.247] (sn80.proper.com [75.101.18.80]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r7FKZtvI018163 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 15 Aug 2013 13:35:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host sn80.proper.com [75.101.18.80] claimed to be [165.227.249.247]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: CBOR and a tag for "critical"
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <520D37CB.8040305@gmail.com>
Date: Thu, 15 Aug 2013 13:35:55 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <72AF328E-541A-4619-A31C-7D941FAFFD80@vpnc.org>
References: <CE300BA7.15704%joe@cursive.net> <520D2B60.3000301@gmail.com> <A1F240A5-C02F-4E45-862B-4A12376A85FF@vpnc.org> <520D37CB.8040305@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
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, 15 Aug 2013 20:36:07 -0000

On Aug 15, 2013, at 1:19 PM, Yaron Sheffer <yaronf.ietf@gmail.com> =
wrote:

> I am quite sure that I fully understand the semantics of "critical" =
(probably erroneously), so I'm not the right person to clarify the =
various meanings of the word. I would appreciate a proposal.
>=20
> Just for the record, my "critical" means: the reader must be able to =
process the data item according to its specification, not just =
syntactically but also semantically, and must fail otherwise. There may =
still be contained non-critical data items that are NOT understood by =
the reader.

And what you say should happen if a decoder saw the One True Critical =
tag before an array item, and then the decoder soon thereafter finds a =
tag it does not know about? The "critical" tag was on the array, not on =
the unknown item.

And so on. We've been there, and we haven't done that so well.

> Sec. 2.4 consistently mentions "tag" in the singular. For example, the =
first sentence could be "a data item can optionally be preceded by one =
or more tags" - but it isn't.

A tag is also a data item. A tag refers to the next data item, even if =
that next data item is also a tag. We'll try to clarify this in the -06.

--Paul Hoffman=

From yaronf.ietf@gmail.com  Thu Aug 15 13:44:07 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C716E11E8205 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEe89ZFuAWFx for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:44:07 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 22B0711E81B7 for <ietf@ietf.org>; Thu, 15 Aug 2013 13:44:06 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id p61so1000953wes.11 for <ietf@ietf.org>; Thu, 15 Aug 2013 13:44:06 -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=uM2tGNm4hLPuX/QQWXjaBzUCiPU00AaRtQjwUcAiG9Q=; b=ou9T2J8Inwynffq7lmkcRWaeoZ3p8xw6/zF7u+6pM1PIYbK6YypneNh0fn7MFVr4G3 z7ARrutD1nXEuiM/QcFjIqz2FBc5uQ2o8Rnzf9cYXIlZaqdMxPmTWey+zGE2ry3/jw6a pn7dc5jNSsFYDRlbQJLeuxpB2UwLj5/UanREStYp4pv1Md7kMj2CNUWzPlo7MGt7SSxD ID6KwXZ4TMRQQYHrRo43qqlhF7IjcCNDmwpf+KV0d4uO7RRTbyfA8Yl9u1Ug2Y6hMWEE Avze/Bq3/E9VTNUZY6OIlTl1uZLTSPfV+kiIHpdlKJpUu/DUVsoz8pVgLXIPYz84RIUB S1xQ==
X-Received: by 10.180.182.15 with SMTP id ea15mr2969399wic.16.1376599445876; Thu, 15 Aug 2013 13:44:05 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-181-180-40.red.bezeqint.net. [79.181.180.40]) by mx.google.com with ESMTPSA id fu13sm1392469wic.7.2013.08.15.13.44.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 Aug 2013 13:44:05 -0700 (PDT)
Message-ID: <520D3D93.5090901@gmail.com>
Date: Thu, 15 Aug 2013 23:44:03 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: CBOR and a tag for "critical"
References: <CE300BA7.15704%joe@cursive.net> <520D2B60.3000301@gmail.com> <A1F240A5-C02F-4E45-862B-4A12376A85FF@vpnc.org> <520D37CB.8040305@gmail.com> <72AF328E-541A-4619-A31C-7D941FAFFD80@vpnc.org>
In-Reply-To: <72AF328E-541A-4619-A31C-7D941FAFFD80@vpnc.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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, 15 Aug 2013 20:44:07 -0000

In fact I answered your question precisely when I mentioned "contained" 
data items (i.e., contained in the critical one). So I may be wrong but 
at least I'm consistent...

I think the concept of criticality is powerful, even if in the past we 
messed it up.

Thanks,
	Yaron

On 2013-08-15 23:35, Paul Hoffman wrote:
> On Aug 15, 2013, at 1:19 PM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
>
>> I am quite sure that I fully understand the semantics of "critical" (probably erroneously), so I'm not the right person to clarify the various meanings of the word. I would appreciate a proposal.
>>
>> Just for the record, my "critical" means: the reader must be able to process the data item according to its specification, not just syntactically but also semantically, and must fail otherwise. There may still be contained non-critical data items that are NOT understood by the reader.
>
> And what you say should happen if a decoder saw the One True Critical tag before an array item, and then the decoder soon thereafter finds a tag it does not know about? The "critical" tag was on the array, not on the unknown item.
>
> And so on. We've been there, and we haven't done that so well.
>
>> Sec. 2.4 consistently mentions "tag" in the singular. For example, the first sentence could be "a data item can optionally be preceded by one or more tags" - but it isn't.
>
> A tag is also a data item. A tag refers to the next data item, even if that next data item is also a tag. We'll try to clarify this in the -06.
>
> --Paul Hoffman
>

From hallam@gmail.com  Thu Aug 15 13:48:58 2013
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 7749711E81CD for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:48:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 GmIJXS4QsmLe for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 13:48:57 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1926411E81AF for <ietf@ietf.org>; Thu, 15 Aug 2013 13:48:56 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id m46so947134wev.8 for <ietf@ietf.org>; Thu, 15 Aug 2013 13:48:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LCiLA6/UEh1af5/TaV57AR+yjfQlKb5CvGcVHV23ngY=; b=EIyd+LfruRP5FM74Lm6unQ+xuImwbIFdG2HyKr9TlJMBESB+OBQ0m39wI2fN58AJxk Pjn1DSNqKMrY1WZPH7erzvcBe9Js4oj2hv7p3pSR1TQSUKCZJ8mDcaKot4MP7q6aU9o6 9T+CO6jTlWsucI2OK3zMV76B62MwdBgMAD3d2kIS2uWd7MViu1ocOuOthbMiJo9XzoU/ azFj5WSsX0c0hixpU2FSpHwneXBRiyGwYGGeHvSP1rQUPj4dUx/RSqotplq+EppYK617 aLQt32psDAd+hx/8yeYN4XIEfhIvfOSb7zHFTl5LBYJD3eDm9MP7zvEMRMI2W6m1TK9v g/tA==
MIME-Version: 1.0
X-Received: by 10.194.174.36 with SMTP id bp4mr11080563wjc.7.1376599736215; Thu, 15 Aug 2013 13:48:56 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Thu, 15 Aug 2013 13:48:56 -0700 (PDT)
In-Reply-To: <520D37CB.8040305@gmail.com>
References: <CE300BA7.15704%joe@cursive.net> <520D2B60.3000301@gmail.com> <A1F240A5-C02F-4E45-862B-4A12376A85FF@vpnc.org> <520D37CB.8040305@gmail.com>
Date: Thu, 15 Aug 2013 21:48:56 +0100
Message-ID: <CAMm+Lwh14ThC8bkW5=EO-JooLqwfO53sgDDP2yCxCE6+6hq56Q@mail.gmail.com>
Subject: Re: CBOR and a tag for "critical"
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e0141a0ae466fc704e4029ab5
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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, 15 Aug 2013 20:48:58 -0000

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

On Thu, Aug 15, 2013 at 9:19 PM, Yaron Sheffer <yaronf.ietf@gmail.com>wrote:

> Hi Paul,
>
> I am quite sure that I fully understand the semantics of "critical"
> (probably erroneously), so I'm not the right person to clarify the various
> meanings of the word. I would appreciate a proposal.
>
> Just for the record, my "critical" means: the reader must be able to
> process the data item according to its specification, not just
> syntactically but also semantically, and must fail otherwise. There may
> still be contained non-critical data items that are NOT understood by the
> reader.
>
> Sec. 2.4 consistently mentions "tag" in the singular. For example, the
> first sentence could be "a data item can optionally be preceded by one or
> more tags" - but it isn't
>

+1

The semantics of critical have never been ambiguous. The problem has been
that some people have been misled into thinking 'critical' means
'important'. So we have certain PKIX extensions where the specification
says that they MUST be marked critical even though marking them critical is
stupid.


Marking an extension critical in a PKIX certificate means 'if you do not
understand this extension you cannot understand the semantics of the
certificate and so you MUST NOT rely on it'.

As such, this is an essential feature to have available if you have a
certificate that depends on some novel revocation mechanism. But it is
something that should only be used if the semantics are so important that
breaking backwards compatibility is desirable.


It is an essential semantic but I don't believe that semantics belong in
the encoding layer. The bit can only be processed at the application layer
so the encoding layer should not be dealing with it. Consider the situation
where you have one application moving bits for another. I might send along
a piece of data that has a critical bit set but it is presented in a
context where the piece of data is optional.

And it need not be a bit. The Critical bit in SAML is actually the
<Conditions/> element. It was necessary to disguise it as I knew that
having a criticality bit would lead to a lot of unproductive arguing and
possibly the same sort of misuse as in PKIX. Calling it Conditions was a
twofer.




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

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

<div dir=3D"ltr">On Thu, Aug 15, 2013 at 9:19 PM, Yaron Sheffer <span dir=
=3D"ltr">&lt;<a href=3D"mailto:yaronf.ietf@gmail.com" target=3D"_blank">yar=
onf.ietf@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Paul,<br>
<br>
I am quite sure that I fully understand the semantics of &quot;critical&quo=
t; (probably erroneously), so I&#39;m not the right person to clarify the v=
arious meanings of the word. I would appreciate a proposal.<br>
<br>
Just for the record, my &quot;critical&quot; means: the reader must be able=
 to process the data item according to its specification, not just syntacti=
cally but also semantically, and must fail otherwise. There may still be co=
ntained non-critical data items that are NOT understood by the reader.<br>

<br>
Sec. 2.4 consistently mentions &quot;tag&quot; in the singular. For example=
, the first sentence could be &quot;a data item can optionally be preceded =
by one or more tags&quot; - but it isn&#39;t<br></blockquote><div><br>
</div><div>+1</div><div><br></div><div>The semantics of critical have never=
 been ambiguous. The problem has been that some people have been misled int=
o thinking &#39;critical&#39; means &#39;important&#39;. So we have certain=
 PKIX extensions where the specification says that they MUST be marked crit=
ical even though marking them critical is stupid.</div>
<div><br></div><div><br></div><div>Marking an extension critical in a PKIX =
certificate means &#39;if you do not understand this extension you cannot u=
nderstand the semantics of the certificate and so you MUST NOT rely on it&#=
39;.=A0</div>
<div><br></div><div>As such, this is an essential feature to have available=
 if you have a certificate that depends on some novel revocation mechanism.=
 But it is something that should only be used if the semantics are so impor=
tant that breaking backwards compatibility is desirable.</div>
<div><br></div><div><br></div><div>It is an essential semantic but I don&#3=
9;t believe that semantics belong in the encoding layer. The bit can only b=
e processed at the application layer so the encoding layer should not be de=
aling with it. Consider the situation where you have one application moving=
 bits for another. I might send along a piece of data that has a critical b=
it set but it is presented in a context where the piece of data is optional=
.</div>
<div><br></div><div>And it need not be a bit. The Critical bit in SAML is a=
ctually the &lt;Conditions/&gt; element. It was necessary to disguise it as=
 I knew that having a criticality bit would lead to a lot of unproductive a=
rguing and possibly the same sort of misuse as in PKIX. Calling it Conditio=
ns was a twofer.</div>
<div><br></div><div><br></div><div>=A0</div></div><div><br></div>-- <br>Web=
site: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0141a0ae466fc704e4029ab5--

From yaronf.ietf@gmail.com  Thu Aug 15 15:11:32 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF7A521F9CF3 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 15:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.87
X-Spam-Level: 
X-Spam-Status: No, score=-101.87 tagged_above=-999 required=5 tests=[AWL=-0.729, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIA+8V26lqhh for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 15:11:31 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 788C321F9CC3 for <ietf@ietf.org>; Thu, 15 Aug 2013 15:11:31 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id b13so995087wgh.31 for <ietf@ietf.org>; Thu, 15 Aug 2013 15:11:30 -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 :content-type:content-transfer-encoding; bh=Q7AqrDq0LQT1m3uHfFwKFZ9w7Kj2L6HOywY2x3WG3xA=; b=CX/Aqd/+UzMsa7xFZ6cM7IVT9/Lt0Cy95oGBTaSgRbATj3DiS4Fj8wph6QN+wV1M8x nUPHg0WRyZd1qGAiDOEPUM3+TPeyoXvPxmvASK36020eruvEcgmt0zSXFgA3qABzweso k8cIQN4rybJA/Tlk9XL0pFdUhIB4YpGEaMj9m7pbNztRQbHTQ60UcFOTXnUifp1Spj8n j7WO2RGvHqox9R2R50jYs1W1/0lzqAGt+KPz5d6C3jRfu/yNlhX6Kz/oQ78CzhnplSkZ a6haz3bzY5T3IdeLcm9Rb/96R5X0eMvQHDgUn2MAfQloTlEObXZqm2/0ZclnbTQdugzG s0tQ==
X-Received: by 10.180.160.162 with SMTP id xl2mr3227240wib.2.1376604689507; Thu, 15 Aug 2013 15:11:29 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-181-180-40.red.bezeqint.net. [79.181.180.40]) by mx.google.com with ESMTPSA id eb3sm5041971wic.10.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 Aug 2013 15:11:28 -0700 (PDT)
Message-ID: <520D520F.8050104@gmail.com>
Date: Fri, 16 Aug 2013 01:11:27 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 15 Aug 2013 22:11:32 -0000

<html style="direction: ltr;">
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
    <style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
  </head>
  <body style="direction: ltr;"
    bidimailui-detected-decoding-type="latin-charset" text="#000000"
    bgcolor="#FFFFFF">
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre style="white-space: pre-wrap; word-wrap: break-word; width: 1199.6875px; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">Hi Paul,

Sorry for the top posting. IMAP ate your mail. Responding to several remaining points:

- A parser that looks for duplicates must be able to detect that {{"a":1, "b":2}:4, {"b":2, "a":1}:5} does in fact have a duplicate key, because the two internal maps (used as keys) are identical. So in general, parsers need to canonicalize maps to any depth in order to detect duplicates. This is "complex" by any definition of the word.

- Even for an unloved diagnostic notation, you want people to read it without resorting to little pieces of paper. So a symbolic representation (TAG_URI) is definitely better than numbers.

- I don't understand your reply re: tags when applied to arrays. Is it up to the application to decide whether the tag applies to all elements, to the first one, to the last 14?

- Regarding error handling and security, I am slightly happier with -05, but not by much. For some reason you avoid using 2119 language in places where I would expect: parsers SHOULD include a "strict mode". A strict mode parser MUST fail when the syntax is broken (sec. 3.3, 3.4, and also 3.5). And so forth.

- Unknown tags: you specifically allow decoders (Sec. 3.5) to not implement any tags they don't like, and then you specify the behavior of the decoder as "do whatever you feel like" (and this is in -05). So a sender cannot rely on *any* tag being implemented by the receiver, and cannot expect deterministic behavior if any are not. This is a security issue IMO, but also an interoperability thing.

Thanks,
	Yaron
&nbsp;
---

On Aug 13, 2013, at 2:11 PM, Yaron Sheffer &lt;yaronf.ietf at gmail.com&gt; wrote:

&gt; sorry I'm submitting these comments after the end of the LC period. I hope they can still be of use.

No problem, and the are. Some answers below.

&gt; - The "diagnostic notation" can be used very effectively for things like configuration files, e.g. if an application already uses CBOR on the wire. Therefore I would suggest to formalize it a bit more, so that we also have interoperability at this level.

Based on other things we heard, we went sort of in the other direction in the next draft: saying that an implementer might consider a different notation for config files, such as YAML.

&gt; - And since this notation is not meant as a JSON extension, this is a good time to introduce comments (e.g. with an initial '#') into the notation.

Comments are not needed in diagnostics. :-)

&gt; - The positive vs. negative encoding means that the parser actually deals with 9-, 17-, 33- and 65-bit integers. I don't think this makes it easier to write parsers.

If you primarily think about signed integers, that may be one way of viewing it.  CBOR is primarily addressing unsigned integers.  Negative integers are clearly separated out, and indeed do require watching the sign bit.  There is no way to handle this that is painless for all applications.

Multiple people have implemented parsers in multiple languages (JavaScript, Python, Ruby, ...), and we found it was pretty easy, and very little code.

&gt; - Arrays are prefixed by the number of elements but not by their length in bytes. And elements need not be all of the same size. So you cannot skip the array without fully parsing every last element. IIRC this is a major disadvantage compared to ASN.1 encodings.

Correct. Counting items and not bytes is indeed a fundamental design decision in CBOR that has advantages and disadvantages. We believe the advantages outweigh the disadvantages.

In specific here, we are not assuming that "skip over an array/map" is a common desire for a decoder. Forcing an encoder to marshall all the bytes before it could start emitting an array/map causes overhead for the encoder that is avoided if it just knows the number of elements it will emit.

&gt; - A puzzling change from JSON, and one that probably complicates implementations quite a bit, is that a map's index can be of any type, not just a string. And this includes mixed index types for the same map.

We have looked at this, and do not think that it complicates many implementations. It does not complicate encoders at all. It does not complicate decoders, even those that are looking for duplicate keys (which will be an error). It only complicates decoders that are also sorting the keys. We assume that the latter does not need to happen in the parser, but in the application that needs the keys sorted by semantics it knows about.

&gt; - And similarly to arrays, you cannot skip a map element without deep parsing of the element.

Ditto from above.

&gt; - I think many of the tag values are too specific, and are best left to applications. For example, why should the format care if the app encodes a UTF-8 string in base64?

Because a generic parser could then do the Base64 decoding. This will always be an iffy space: CBOR will either force too much knowledge on the application, or it will do too much. We picked somewhere on that continuum, knowing that it will make no one happy. FWIW, Carsten and I disagreed with each other on this to varying degrees during the different drafts, and different people proposed different places on the continuum where CBOR "should" be.

&gt; OTOH, I would reserve a part of the tag space for "private" application-specific allocations.

One of the always-repeating IETF rat-hole. We didn't go there, nor will we say you're wrong for wanting to go there. The first-come-first-served space should enable such allocations. If you just want to play around in the lab, the range up to 18446744073709551615 should allow reliably avoiding collisions.

&gt; - One tag value you may want to consider adding is "critical" in the security sense of the word, i.e., an application is required to fail if it does not understand the value (probably best applied to map keys).

That is a lovely proposal for an extension from a developer who is using CBOR in such an environment so that they can write the three or four paragraphs that would be needed to explain that in detail.

&gt; - In the "diagnostic notation", I suggest to use symbolic values rather than integers for tags, e.g. TAG_URI.

You seem to like the diagnostic notation more than we do. :-) If CBOR becomes at all popular, having a second, more thought-out diagnostic notation seems like a reasonable project.

&gt; - Sec. 3: because of the need for deep parsing mentioned above, a wire protocol cannot be extended by adding an element that uses a new data type (e.g. double precision FP) unless all potential recipients understand the type, even though they might not need to use the data element.

Correct. We are adding more text to make that clear.

&gt; - Type restrictions for tags should be spelled out more clearly. E.g. in 2.4.4.2, please clarify that when this tag applies to an array or map, *all* the items (and potentially items of nested arrays/maps?) MUST be byte strings.

A CBOR protocol can choose to do just that.

&gt; IMHO this just adds complexity and it's best to only tag the atomic item.

Noted. Some of the tags imply more restrictions that we would have hoped, but if it isn't specified in the tag, the complexity just gets pushed to all the applications.

&gt; - Text such as this (for unknown simple types): "might issue a warning, might stop processing altogether, might handle the error by making the unknown value available to the application as such, or take some other type of action." is a security disaster waiting to happen. Also, it does not allow extensibility. Even though the encoding format is nominally extensible, in reality you cannot add stuff because the behavior of existing implementations when faced with it is unpredictable.

You (and the other folks who made similar comments about the looseness in this section) should be much happier with the next draft.

&gt; - Similarly for unknown tags (which IMHO should be ignored). Note that "unknown" includes currently specified tags, because implementations are not required to implement all current tags.

Not sure what you mean here.

&gt; - Another security issue, for incomplete arrays: "a parser may completely fail the decoding, or substitute the missing data and data items using an decoder-specific convention. " This is a buffer overflow vulnerability by a different name.

How is that different than, say JSON, where the decoder might never see the final "}" or "]"?

&gt; - And by the way the entire Sec. 3 is non-normative. I suggest to use normative language for parser behavior, to ensure it is deterministic.

We think we have done so in the next version.

--Paul Hoffman</pre>
  </body>
</html>

From wes@mti-systems.com  Thu Aug 15 18:24:06 2013
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC01711E823E for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 18:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nCLaIlwCs-vQ for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 18:24:02 -0700 (PDT)
Received: from atl4mhob13.myregisteredsite.com (atl4mhob13.myregisteredsite.com [209.17.115.51]) by ietfa.amsl.com (Postfix) with ESMTP id 11C9D11E823D for <ietf@ietf.org>; Thu, 15 Aug 2013 18:24:02 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob13.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id r7G1O16g023023 for <ietf@ietf.org>; Thu, 15 Aug 2013 21:24:01 -0400
Received: (qmail 373 invoked by uid 0); 16 Aug 2013 01:24:01 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.122?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 16 Aug 2013 01:24:01 -0000
Message-ID: <520D7F0D.10905@mti-systems.com>
Date: Thu, 15 Aug 2013 21:23:25 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu>
In-Reply-To: <520D3779.4050106@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 01:24:07 -0000

On 8/15/2013 4:18 PM, Joe Touch wrote:
> 
> 
> On 8/10/2013 12:29 PM, Wesley Eddy wrote:
>> On 8/10/2013 1:43 AM, Martin Sustrik wrote:
>>> Hi all,
>>>
>>> Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol used?
>>> Is it the case that there are inetd daemons in TCPMUX mode running
>>> everywhere, or can it be rather considered a dead protocol?
>>>
>>> Specifically, if I implement a new TCPMUX daemon how likely I am to
>>> clash with an existing TCPMUX daemon listening on port 1?
>>>
>>
>>
>> It's in the FreeBSD inetd, among others, but to to my
>> knowledge, nobody actually turns it on.  There are
>> probably security issues.
> 
> There are semantics issues to; see draft-touch-tcp-portnames-00 for
> information (this is being revised for resubmission shortly, FWIW).
> 


I totally agree.  In fact, in the update to the TCP roadmap [1], we
added TCPMUX to the section on "Historic and Undeployed Extensions",
though it definitely bears further discussion than is currently in
the roadmap.  I think we should add a reference to your portnames doc
to explain why this should be Historic plus check a bit more to see if
the code that's out there is really being used or whether it's just
hanging out like a vestigal limb in the various inetd packages.

If it's fair to ask Martin ... I'm kind of curious why you might want
to be using it or think it sounds useful?  I think a lot of admins
would be concerned that it could be used to get around port-based
firewall rules, etc.

[1] http://tools.ietf.org/html/draft-ietf-tcpm-tcp-rfc4614bis-00

-- 
Wes Eddy
MTI Systems

From mnot@mnot.net  Thu Aug 15 18:48:32 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D2C11E80F9 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 18:48: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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8lPLjOsQmmy for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 18:48:26 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8B14E11E8235 for <ietf@ietf.org>; Thu, 15 Aug 2013 18:48:26 -0700 (PDT)
Received: from [192.168.1.62] (unknown [118.209.151.245]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1310522E1F3; Thu, 15 Aug 2013 21:48:18 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Radical Solution for remote participants
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
Date: Fri, 16 Aug 2013 11:48:15 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D60BC4FA-F146-466B-97FB-C0AEAC9E6FBA@mnot.net>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: John Leslie <john@jlc.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, 16 Aug 2013 01:48:32 -0000

On 13/08/2013, at 11:00 AM, Douglas Otis <doug.mtview@gmail.com> wrote:
>=20
> 1) Ensure exact digital interfaces driving projectors are fully =
available remotely. =20

That would be fantastic, if feasible. Much simpler than sharing through =
software.


> 2) Ensure Audio access requires an identified request via XMPP prior =
to enabling either a remote or local audio feed.

Hm.

>=20
> 3) RFI tags could facilitate enabling local audio feed instead of an =
identified request via XMPP.

Could be quite interesting; many conferences now provide attendees with =
RFID tags...

>=20
> 4) In the event of the local venue loosing Internet access, the device =
regulating A/V presentations must be able to operate in a virtual mode =
where only remote participants are permitted to continue the meeting =
proceedings.

That seems=85 extreme.

> 5) Important participants should plan for alternative modes of =
Internet access to remain part of the proceedings.

Not exactly practical.

>=20
> 6) Develop a simple syntax used on XMPP sessions to:
> 1) signify a request to speak on X=20
> 2) withdraw a request to speak on X
> 3) signify support of Y
> 4) signify non-support of Y
> 5) signal when a request has been granted or revoked.  For local =
participants this could be in the form of a red or green light at their =
microphone.=20

The W3C does much of this already with IRC bots, e.g.:
  http://www.w3.org/2001/12/zakim-irc-bot.html

(also can pick a scribe, track an agenda, etc.)


> 7) Develop a control panel managed by chairs or their proxies that =
consolidate and sequence requests and log support and nonsupport =
indications and the granting of requests.

See above (I think).

>=20
> 8) Chairs should be able to act as proxies for local participants =
lacking access to XMPP.=20

Not practical, unless they delegate.

>=20
> 9) Chairs should have alternative Internet access independent of that =
of the venue's.

Seems extreme.

>=20
> 10) Establish a reasonable fee to facilitate remote participants who =
receive credit for their participation equal to that of being local.
>=20
> 11) The device regulating A/V presentations must drive both the video =
and audio portions of the presentations.  A web camera in a room is a =
very poor replacement.
>=20
> 12) All video information in the form of slides and text must be =
available from the Internet prior to the beginning of the meeting.

Cheers,


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




From narten@us.ibm.com  Thu Aug 15 21:53:16 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2532311E8255 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.144
X-Spam-Level: 
X-Spam-Status: No, score=-108.144 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, 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 3aRtLimPlh3B for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 21:53:09 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 35DB811E8253 for <ietf@ietf.org>; Thu, 15 Aug 2013 21:53:08 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 16 Aug 2013 00:53:07 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 16 Aug 2013 00:53:06 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id D246F38C8027 for <ietf@ietf.org>; Fri, 16 Aug 2013 00:53:03 -0400 (EDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7G4r5e4206496 for <ietf@ietf.org>; Fri, 16 Aug 2013 00:53:05 -0400
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r7G4tq7d019064 for <ietf@ietf.org>; Thu, 15 Aug 2013 22:55:52 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7G4tqjt019059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 15 Aug 2013 22:55:52 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r7G4r3eU026816 for <ietf@ietf.org>; Fri, 16 Aug 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r7G4r3iE026769 for ietf@ietf.org; Fri, 16 Aug 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201308160453.r7G4r3iE026769@rotala.raleigh.ibm.com>
Date: Fri, 16 Aug 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13081604-7182-0000-0000-0000081C66A5
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 04:53:16 -0000

Total of 125 messages in the last 7 days.
 
script run at: Fri Aug 16 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.20% |    9 | 10.47% |   108804 | hallam@gmail.com
  5.60% |    7 |  8.58% |    89136 | hadriel.kaplan@oracle.com
  7.20% |    9 |  6.54% |    67899 | ted.lemon@nominum.com
  6.40% |    8 |  6.59% |    68454 | yaronf.ietf@gmail.com
  5.60% |    7 |  5.04% |    52375 | sm@resistor.net
  4.00% |    5 |  5.79% |    60106 | harald@alvestrand.no
  4.80% |    6 |  3.58% |    37229 | cabo@tzi.org
  3.20% |    4 |  3.71% |    38560 | gk@ninebynine.org
  3.20% |    4 |  2.97% |    30814 | paul.hoffman@vpnc.org
  3.20% |    4 |  2.40% |    24926 | dhc@dcrocker.net
  2.40% |    3 |  2.02% |    20970 | vinayakh@gmail.com
  1.60% |    2 |  2.16% |    22459 | ynir@checkpoint.com
  1.60% |    2 |  2.07% |    21464 | jgunn6@csc.com
  1.60% |    2 |  1.77% |    18417 | david.black@emc.com
  1.60% |    2 |  1.49% |    15442 | jari.arkko@piuha.net
  1.60% |    2 |  1.48% |    15334 | john-ietf@jck.com
  1.60% |    2 |  1.36% |    14092 | framefritti@gmail.com
  1.60% |    2 |  1.35% |    13994 | sm+ietf@elandsys.com
  1.60% |    2 |  1.32% |    13756 | alejandroacostaalamo@gmail.com
  1.60% |    2 |  1.32% |    13737 | andy@yumaworks.com
  1.60% |    2 |  1.28% |    13320 | stephen.farrell@cs.tcd.ie
  1.60% |    2 |  1.18% |    12275 | johnl@taugh.com
  1.60% |    2 |  1.17% |    12171 | john@jlc.net
  1.60% |    2 |  1.12% |    11671 | wes@mti-systems.com
  1.60% |    2 |  0.97% |    10051 | sustrik@250bpm.com
  0.80% |    1 |  1.36% |    14152 | stephen.nadas@ericsson.com
  0.80% |    1 |  1.15% |    11950 | narten@us.ibm.com
  0.80% |    1 |  1.10% |    11434 | tbray@textuality.com
  0.80% |    1 |  0.99% |    10320 | carlosm3011@gmail.com
  0.80% |    1 |  0.86% |     8963 | barryleiba@computer.org
  0.80% |    1 |  0.84% |     8692 | doug.mtview@gmail.com
  0.80% |    1 |  0.80% |     8285 | hartmans-ietfc@mit.edu
  0.80% |    1 |  0.78% |     8141 | dave@cridland.net
  0.80% |    1 |  0.76% |     7889 | superuser@gmail.com
  0.80% |    1 |  0.73% |     7623 | hartmans-ietf@mit.edu
  0.80% |    1 |  0.73% |     7609 | hildjj@cursive.net
  0.80% |    1 |  0.71% |     7373 | mnot@mnot.net
  0.80% |    1 |  0.70% |     7301 | martin.thomson@gmail.com
  0.80% |    1 |  0.70% |     7228 | rpelletier@isoc.org
  0.80% |    1 |  0.70% |     7223 | moore@network-heretics.com
  0.80% |    1 |  0.68% |     7094 | lear@cisco.com
  0.80% |    1 |  0.68% |     7084 | tnadeau@lucidvision.com
  0.80% |    1 |  0.66% |     6860 | daedulus@btconnect.com
  0.80% |    1 |  0.64% |     6680 | stpeter@stpeter.im
  0.80% |    1 |  0.63% |     6528 | scott@kitterman.com
  0.80% |    1 |  0.62% |     6404 | dot@dotat.at
  0.80% |    1 |  0.61% |     6287 | iab-chair@iab.org
  0.80% |    1 |  0.60% |     6262 | john@jck.com
  0.80% |    1 |  0.58% |     6073 | melinda.shore@gmail.com
  0.80% |    1 |  0.58% |     5999 | masinter@adobe.com
  0.80% |    1 |  0.55% |     5702 | randy_presuhn@mindspring.com
  0.80% |    1 |  0.53% |     5552 | iad@ietf.org
  0.80% |    1 |  0.53% |     5530 | peter@akayla.com
  0.80% |    1 |  0.52% |     5401 | touch@isi.edu
  0.80% |    1 |  0.48% |     4980 | kent@bbn.com
  0.80% |    1 |  0.45% |     4704 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |  125 |100.00% |  1038779 | Total


From sustrik@250bpm.com  Thu Aug 15 22:19:58 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED5A21F8C9D for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 22:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CA6LtjowuC97 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 22:19:52 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9834F11E811B for <ietf@ietf.org>; Thu, 15 Aug 2013 22:19:52 -0700 (PDT)
Received: from [192.168.1.134] (188-167-109-79.dynamic.chello.sk [188.167.109.79]) by mail.moloch.sk (Postfix) with ESMTPSA id E90101803553; Fri, 16 Aug 2013 07:19:49 +0200 (CEST)
Message-ID: <520DB675.2040206@250bpm.com>
Date: Fri, 16 Aug 2013 07:19:49 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu>
In-Reply-To: <520D3779.4050106@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 05:19:58 -0000

On 15/08/13 22:18, Joe Touch wrote:

>>> Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol used?
>>> Is it the case that there are inetd daemons in TCPMUX mode running
>>> everywhere, or can it be rather considered a dead protocol?
>>>
>>> Specifically, if I implement a new TCPMUX daemon how likely I am to
>>> clash with an existing TCPMUX daemon listening on port 1?
>>>
>>
>>
>> It's in the FreeBSD inetd, among others, but to to my
>> knowledge, nobody actually turns it on. There are
>> probably security issues.
>
> There are semantics issues to; see draft-touch-tcp-portnames-00 for
> information (this is being revised for resubmission shortly, FWIW).

Nice, however, it requires changes to TCP stack, so even if it succeeds 
it won't be a practical option for at least few years to come.

Martin

From sustrik@250bpm.com  Thu Aug 15 22:38:27 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02D0C11E8113 for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 22:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaFgQYNazsUi for <ietf@ietfa.amsl.com>; Thu, 15 Aug 2013 22:38:21 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7839111E811B for <ietf@ietf.org>; Thu, 15 Aug 2013 22:38:17 -0700 (PDT)
Received: from [192.168.1.134] (188-167-109-79.dynamic.chello.sk [188.167.109.79]) by mail.moloch.sk (Postfix) with ESMTPSA id 4E1B31803553; Fri, 16 Aug 2013 07:38:03 +0200 (CEST)
Message-ID: <520DBABA.2000506@250bpm.com>
Date: Fri, 16 Aug 2013 07:38:02 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com>
In-Reply-To: <520D7F0D.10905@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 05:38:27 -0000

On 16/08/13 03:23, Wesley Eddy wrote:

>> There are semantics issues to; see draft-touch-tcp-portnames-00 for
>> information (this is being revised for resubmission shortly, FWIW).
>>
> I totally agree.  In fact, in the update to the TCP roadmap [1], we
> added TCPMUX to the section on "Historic and Undeployed Extensions",
> though it definitely bears further discussion than is currently in
> the roadmap.  I think we should add a reference to your portnames doc
> to explain why this should be Historic plus check a bit more to see if
> the code that's out there is really being used or whether it's just
> hanging out like a vestigal limb in the various inetd packages.
>
> If it's fair to ask Martin ... I'm kind of curious why you might want
> to be using it or think it sounds useful?  I think a lot of admins
> would be concerned that it could be used to get around port-based
> firewall rules, etc.

Ok, let me explain.

I am coming from enterprise messaging world (think of IBM MQ series, 
JMS, ActiveMQ, RabbitMQ et c.)

Once I was participating on AMQP protocol development (now at OASIS). 
So, what AMQP and other enterprise messaging products do is exposing a 
"message broker" on a single TCP port, which then forwards messages to 
any connected services. As can be seen, single open firewall port can be 
used to access any internal service.

That being obviously the *wrong* way to do things, I've written ZeroMQ 
later which takes the strict approach: If you want to expose a new 
service, you have to use a separate TCP port number.

Since then it turned out that this as a limitation that people are most 
complaining about.

Now, the reason seems to be that ZeroMQ requires you to use different 
TCP connections for doing different kinds of stuff to avoid head-of-line 
blocking et c. (think of SCTP channels simulated via TCP)

What that means is that you have a lot of fine-grained services and as 
the development of your application proceeds you add more of them, 
remove them and so on.

That in turn requires admins (and the corporate approval process!) to 
get into the deployment cycle and open the TCP ports as appropriate. The 
result is that the development basically grinds to halt.

The solution IMO is to preserve the port-based services functionality 
for those that truly care about security and -- optionally -- support 
some kind of multiplexer such as TCPMUX for those that care more about 
short deployment cycle.

That being said, IIRC, there's such functionality in WebSockets as well. 
Open a connection to fixed pot (80) and particular URL (string), then 
after the initial negotiation, switch to raw TCP mode and hand the 
connection to whatever application is suppose to handle it. The reason I 
don't like that solution is that you have to have web server installed 
to work as a multiplexer, which is kind of strange.

Martin


From yaronf.ietf@gmail.com  Fri Aug 16 00:12:01 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B79211E8257 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 00:12:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.417
X-Spam-Level: 
X-Spam-Status: No, score=-102.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4lDr-Vxrl02 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 00:12:00 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id A272E11E811D for <ietf@ietf.org>; Fri, 16 Aug 2013 00:11:59 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id j17so487096wiw.17 for <ietf@ietf.org>; Fri, 16 Aug 2013 00:11: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:cc:subject :content-type:content-transfer-encoding; bh=IRJrk2ekOV/1I8kl2l6QlQVRWrNCnEmt9oHmOfff7JQ=; b=CQ4aH36uoLkVASSawRsbSScPAFRgSlQoe673RoaNFPaD9XZoBKPB0q7WCEusDWm+gg srKacnCjsGOpJka+QXIJMpJ3UQJC0C+rBxcTWX9SIMdzZaWUB5GvRpLav9uQKpvtWZ6D 4DGGJNEwJtCjHwcVQnwVzEMnSMDNP/E88ArTqf4CUn+3RbSZneyfXc8R0Quw4WxDYKbY Q5MiIm9xo1316eeLJlABfdEyousn2dX3E7C/B6IYPNrkKmynehfkeXhVV7x7YmYyUo+O dpd/TZPOaBVXQjhbLflWm9k9uO7paCDN1Hx/FouEU4/+nUjEgZ4QfQqccaM/QUa8Ggai sLCg==
X-Received: by 10.180.189.132 with SMTP id gi4mr4286635wic.19.1376637117506; Fri, 16 Aug 2013 00:11:57 -0700 (PDT)
Received: from [10.0.0.6] (bzq-79-181-180-40.red.bezeqint.net. [79.181.180.40]) by mx.google.com with ESMTPSA id e7sm189617wiy.4.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 Aug 2013 00:11:56 -0700 (PDT)
Message-ID: <520DD0BA.2090000@gmail.com>
Date: Fri, 16 Aug 2013 10:11:54 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 16 Aug 2013 07:12:01 -0000

[resending as non-HTML]

Hi Paul,

Sorry for the top posting. IMAP ate your mail. Responding to several remaining points:

- A parser that looks for duplicates must be able to detect that {{"a":1, "b":2}:4, {"b":2, "a":1}:5} does in fact have a duplicate key, because the two internal maps (used as keys) are identical. So in general, parsers need to canonicalize maps to any depth in order to detect duplicates. This is "complex" by any definition of the word.

- Even for an unloved diagnostic notation, you want people to read it without resorting to little pieces of paper. So a symbolic representation (TAG_URI) is definitely better than numbers.

- I don't understand your reply re: tags when applied to arrays. Is it up to the application to decide whether the tag applies to all elements, to the first one, to the last 14?

- Regarding error handling and security, I am slightly happier with -05, but not by much. For some reason you avoid using 2119 language in places where I would expect: parsers SHOULD include a "strict mode". A strict mode parser MUST fail when the syntax is broken (sec. 3.3, 3.4, and also 3.5). And so forth.

- Unknown tags: you specifically allow decoders (Sec. 3.5) to not implement any tags they don't like, and then you specify the behavior of the decoder as "do whatever you feel like" (and this is in -05). So a sender cannot rely on *any* tag being implemented by the receiver, and cannot expect deterministic behavior if any are not. This is a security issue IMO, but also an interoperability thing.

Thanks,
	Yaron
  
---

On Aug 13, 2013, at 2:11 PM, Yaron Sheffer <yaronf.ietf at gmail.com> wrote:

> sorry I'm submitting these comments after the end of the LC period. I hope they can still be of use.

No problem, and the are. Some answers below.

> - The "diagnostic notation" can be used very effectively for things like configuration files, e.g. if an application already uses CBOR on the wire. Therefore I would suggest to formalize it a bit more, so that we also have interoperability at this level.

Based on other things we heard, we went sort of in the other direction in the next draft: saying that an implementer might consider a different notation for config files, such as YAML.

> - And since this notation is not meant as a JSON extension, this is a good time to introduce comments (e.g. with an initial '#') into the notation.

Comments are not needed in diagnostics. :-)

> - The positive vs. negative encoding means that the parser actually deals with 9-, 17-, 33- and 65-bit integers. I don't think this makes it easier to write parsers.

If you primarily think about signed integers, that may be one way of viewing it.  CBOR is primarily addressing unsigned integers.  Negative integers are clearly separated out, and indeed do require watching the sign bit.  There is no way to handle this that is painless for all applications.

Multiple people have implemented parsers in multiple languages (JavaScript, Python, Ruby, ...), and we found it was pretty easy, and very little code.

> - Arrays are prefixed by the number of elements but not by their length in bytes. And elements need not be all of the same size. So you cannot skip the array without fully parsing every last element. IIRC this is a major disadvantage compared to ASN.1 encodings.

Correct. Counting items and not bytes is indeed a fundamental design decision in CBOR that has advantages and disadvantages. We believe the advantages outweigh the disadvantages.

In specific here, we are not assuming that "skip over an array/map" is a common desire for a decoder. Forcing an encoder to marshall all the bytes before it could start emitting an array/map causes overhead for the encoder that is avoided if it just knows the number of elements it will emit.

> - A puzzling change from JSON, and one that probably complicates implementations quite a bit, is that a map's index can be of any type, not just a string. And this includes mixed index types for the same map.

We have looked at this, and do not think that it complicates many implementations. It does not complicate encoders at all. It does not complicate decoders, even those that are looking for duplicate keys (which will be an error). It only complicates decoders that are also sorting the keys. We assume that the latter does not need to happen in the parser, but in the application that needs the keys sorted by semantics it knows about.

> - And similarly to arrays, you cannot skip a map element without deep parsing of the element.

Ditto from above.

> - I think many of the tag values are too specific, and are best left to applications. For example, why should the format care if the app encodes a UTF-8 string in base64?

Because a generic parser could then do the Base64 decoding. This will always be an iffy space: CBOR will either force too much knowledge on the application, or it will do too much. We picked somewhere on that continuum, knowing that it will make no one happy. FWIW, Carsten and I disagreed with each other on this to varying degrees during the different drafts, and different people proposed different places on the continuum where CBOR "should" be.

> OTOH, I would reserve a part of the tag space for "private" application-specific allocations.

One of the always-repeating IETF rat-hole. We didn't go there, nor will we say you're wrong for wanting to go there. The first-come-first-served space should enable such allocations. If you just want to play around in the lab, the range up to 18446744073709551615 should allow reliably avoiding collisions.

> - One tag value you may want to consider adding is "critical" in the security sense of the word, i.e., an application is required to fail if it does not understand the value (probably best applied to map keys).

That is a lovely proposal for an extension from a developer who is using CBOR in such an environment so that they can write the three or four paragraphs that would be needed to explain that in detail.

> - In the "diagnostic notation", I suggest to use symbolic values rather than integers for tags, e.g. TAG_URI.

You seem to like the diagnostic notation more than we do. :-) If CBOR becomes at all popular, having a second, more thought-out diagnostic notation seems like a reasonable project.

> - Sec. 3: because of the need for deep parsing mentioned above, a wire protocol cannot be extended by adding an element that uses a new data type (e.g. double precision FP) unless all potential recipients understand the type, even though they might not need to use the data element.

Correct. We are adding more text to make that clear.

> - Type restrictions for tags should be spelled out more clearly. E.g. in 2.4.4.2, please clarify that when this tag applies to an array or map, *all* the items (and potentially items of nested arrays/maps?) MUST be byte strings.

A CBOR protocol can choose to do just that.

> IMHO this just adds complexity and it's best to only tag the atomic item.

Noted. Some of the tags imply more restrictions that we would have hoped, but if it isn't specified in the tag, the complexity just gets pushed to all the applications.

> - Text such as this (for unknown simple types): "might issue a warning, might stop processing altogether, might handle the error by making the unknown value available to the application as such, or take some other type of action." is a security disaster waiting to happen. Also, it does not allow extensibility. Even though the encoding format is nominally extensible, in reality you cannot add stuff because the behavior of existing implementations when faced with it is unpredictable.

You (and the other folks who made similar comments about the looseness in this section) should be much happier with the next draft.

> - Similarly for unknown tags (which IMHO should be ignored). Note that "unknown" includes currently specified tags, because implementations are not required to implement all current tags.

Not sure what you mean here.

> - Another security issue, for incomplete arrays: "a parser may completely fail the decoding, or substitute the missing data and data items using an decoder-specific convention. " This is a buffer overflow vulnerability by a different name.

How is that different than, say JSON, where the decoder might never see the final "}" or "]"?

> - And by the way the entire Sec. 3 is non-normative. I suggest to use normative language for parser behavior, to ensure it is deterministic.

We think we have done so in the next version.

--Paul Hoffman


From jmh@joelhalpern.com  Fri Aug 16 01:59:29 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50B7311E8107 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 01:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRzETsKqSldm for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 01:59:24 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD4611E80D5 for <ietf@ietf.org>; Fri, 16 Aug 2013 01:59:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 2450A1C0541; Fri, 16 Aug 2013 01:59:24 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [192.165.183.201]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id A47121C0198; Fri, 16 Aug 2013 01:59:22 -0700 (PDT)
Message-ID: <520DE9E8.6030806@joelhalpern.com>
Date: Fri, 16 Aug 2013 04:59:20 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Radical Solution for remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <D60BC4FA-F146-466B-97FB-C0AEAC9E6FBA@mnot.net>
In-Reply-To: <D60BC4FA-F146-466B-97FB-C0AEAC9E6FBA@mnot.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>, John Leslie <john@jlc.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 08:59:29 -0000

Maybe I am missing something.
The reason we have face-to-face meetings is because there is value in 
such meetings that can not reasonably be achieved in other ways.
I would like remote participation to be as good as possible.  But if 
would could achieve "the same as being there" then we should seriously 
consider not meeting face-to-face.
Conversely, until the technology gets that good, we must not penalize 
the face-to-face meeting for failures of the technology.

Yours,
Joel

On 8/15/13 9:48 PM, Mark Nottingham wrote:
>
> On 13/08/2013, at 11:00 AM, Douglas Otis <doug.mtview@gmail.com> wrote:
>>
>> 1) Ensure exact digital interfaces driving projectors are fully available remotely.
>
> That would be fantastic, if feasible. Much simpler than sharing through software.
>
>
>> 2) Ensure Audio access requires an identified request via XMPP prior to enabling either a remote or local audio feed.
>
> Hm.
>
>>
>> 3) RFI tags could facilitate enabling local audio feed instead of an identified request via XMPP.
>
> Could be quite interesting; many conferences now provide attendees with RFID tags...
>
>>
>> 4) In the event of the local venue loosing Internet access, the device regulating A/V presentations must be able to operate in a virtual mode where only remote participants are permitted to continue the meeting proceedings.
>
> That seems… extreme.
>
>> 5) Important participants should plan for alternative modes of Internet access to remain part of the proceedings.
>
> Not exactly practical.
>
>>
>> 6) Develop a simple syntax used on XMPP sessions to:
>> 1) signify a request to speak on X
>> 2) withdraw a request to speak on X
>> 3) signify support of Y
>> 4) signify non-support of Y
>> 5) signal when a request has been granted or revoked.  For local participants this could be in the form of a red or green light at their microphone.
>
> The W3C does much of this already with IRC bots, e.g.:
>    http://www.w3.org/2001/12/zakim-irc-bot.html
>
> (also can pick a scribe, track an agenda, etc.)
>
>
>> 7) Develop a control panel managed by chairs or their proxies that consolidate and sequence requests and log support and nonsupport indications and the granting of requests.
>
> See above (I think).
>
>>
>> 8) Chairs should be able to act as proxies for local participants lacking access to XMPP.
>
> Not practical, unless they delegate.
>
>>
>> 9) Chairs should have alternative Internet access independent of that of the venue's.
>
> Seems extreme.
>
>>
>> 10) Establish a reasonable fee to facilitate remote participants who receive credit for their participation equal to that of being local.
>>
>> 11) The device regulating A/V presentations must drive both the video and audio portions of the presentations.  A web camera in a room is a very poor replacement.
>>
>> 12) All video information in the form of slides and text must be available from the Internet prior to the beginning of the meeting.
>
> Cheers,
>
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>

From john-ietf@jck.com  Fri Aug 16 04:26:09 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFF311E8110 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 04:26:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N1i+3RWylosS for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 04:26:03 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A6F8421F8A38 for <ietf@ietf.org>; Fri, 16 Aug 2013 04:26:03 -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 1VAIAH-0008GH-AU; Fri, 16 Aug 2013 07:25:57 -0400
Date: Fri, 16 Aug 2013 07:25:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Mark Nottingham <mnot@mnot.net>
Subject: Re: Radical Solution for remote participants
Message-ID: <0FC8035D77FAB0B571A347D3@JcK-HP8200.jck.com>
In-Reply-To: <520DE9E8.6030806@joelhalpern.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <D60BC4FA-F146-466B-97FB-C0AEAC9E6FBA@mnot.net> <520DE9E8.6030806@joelhalpern.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion Mailing List <ietf@ietf.org>, John Leslie <john@jlc.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 11:26:09 -0000

--On Friday, August 16, 2013 04:59 -0400 "Joel M. Halpern"
<jmh@joelhalpern.com> wrote:

> Maybe I am missing something.
> The reason we have face-to-face meetings is because there is
> value in such meetings that can not reasonably be achieved in
> other ways.
> I would like remote participation to be as good as possible.
> But if would could achieve "the same as being there" then we
> should seriously consider not meeting face-to-face.
> Conversely, until the technology gets that good, we must not
> penalize the face-to-face meeting for failures of the
> technology.

Joel,

I certainly agree with your conclusion.  While I hope the intent
wasn't to penalize the face-to-face meeting, there have been
several suggestions in this thread that I believe are
impractical and a few that are probably undesirable even if they
were practical.   Others, such as improved automation, are
practical if we want to make the effort, would probably help,
and, fwiw, have been suggested by multiple people in multiple
threads.

I do believe it would be helpful for everyone involved in the
discussion to be careful about their reactions and rhetoric.
While it is certainly possible to go too far in any given
direction, significant and effective remote participation will
almost certainly require some adjustments by the people in the
room.  We've already made some of those adjustments: for example
while it is inefficient and sometimes doesn't work well, using
Jabber as inbound channel with someone in the room reading
Jabber input at the Mic does help remote participants at some
cost to the efficient flow of the f2f discussions.  

Perhaps that penalizes the face to face participants.  I believe
it is worth it and that it would be worthwhile going somewhat
further in that direction, e.g., by treating remote participants
as a separate mic queue.  I also see it as very closely related
to some other tradeoffs: for example, going to extra effort to
be inclusive and diverse requires extra effort by existing f2f
participants and very carefully balancing costs -- higher costs
and even costs at current levels discourage broader participants
but many ways of increasing diversity also increase costs.

Wrt "not meeting face-to-face", I don't see it happening, even
with technology improvements.  On the other hand, the absolutely
most effective thing we could do to significantly decrease costs
for those who need the f2f meetings but are cost-sensitive would
be to reverse the trends toward WG substituting interim meetings
for work on mailing lists, toward extending the IETF meeting
week to include supplemental meetings, and even to move toward
two, rather than three, meetings a year.  Those changes,
especially the latter two, would probably require that remote
participation be much more efficient and effective than it is
today, but would not require nearly the level of perfection
required to eliminate f2f meetings entirely.  And any of the
three would "penalize" those who like going to extended f2f
meetings and/or prefer working that way and who have effectively
unlimited travel support and related resources.

best,
    john


From hadriel.kaplan@oracle.com  Fri Aug 16 05:08:10 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB8711E8110 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 05:08:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.319
X-Spam-Level: 
X-Spam-Status: No, score=-6.319 tagged_above=-999 required=5 tests=[AWL=0.280,  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 lbAZiV4c0Alp for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 05:08:04 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id BCD9011E8136 for <ietf@ietf.org>; Fri, 16 Aug 2013 05:08:03 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GC7xUs017813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Aug 2013 12:08:01 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GC7vf2023934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 12:07:58 GMT
Received: from abhmt118.oracle.com (abhmt118.oracle.com [141.146.116.70]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GC7vdY029297; Fri, 16 Aug 2013 12:07:57 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 05:07:57 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Radical Solution for remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <20130813102459.GC68553@verdi>
Date: Fri, 16 Aug 2013 08:07:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com> <20130813102459.GC68553@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
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, 16 Aug 2013 12:08:11 -0000

On Aug 13, 2013, at 6:24 AM, John Leslie <john@jlc.net> wrote:

>   There are a certain number of Working Groups where it's standard
> operating practice to ignore any single voice who doesn't attend an
> IETF week to defend his/her postings.

I don't see that happening in the WGs I attend - when remote =
participants post to jabber, the jabber scribes get mic time.  I think =
what you mean isn't really that physical participants "ignore" remote =
ones, but more that remote participants don't have as much impact/weight =
with their input/arguments than physical participants do.  Is that what =
you mean?


>   I don't always understand what Doug is asking for; but I suspect
> he is proposing to define a remote-participation where you get full
> opportunity to defend your ideas. This simply doesn't happen today.

Then fix that problem.

Which solution addresses that problem:
1) Make remote participants pay money.
2) Add a separate mic line.
3) Add remote controls for A/V equipment.
4) Add XMPP controls for mic-line and humming.
5) None of the above.

ISTM it's (5).  Working Groups don't ignore remote participant voices =
because they don't pay money.  They don't ignore them because they don't =
have a separate mic.  They don't ignore them because they don't have A/V =
control.  They don't ignore them because they don't have XMPP controls.

WG physical participants "ignore" remote ones because they're not =
physically present.  We're human beings.  Human beings have a =
subconscious connection/empathy with other human beings based on our =
senses, that does not exist when we only read their words or only hear =
them speaking... especially when it's hear them by-proxy as the current =
jabber model uses.  This isn't news to anyone - it's why people travel =
to meet other people, and why the telepresence market exists.

The next step up from our current jabber-scribe model is to have audio =
input - the ability for remote participants to speak using their own =
voice, when it's their turn at the 'mic'.  The next step up after that =
is video input, where remote participants can be seen as well as heard.  =
Both of those are technically achievable, and possibly even practical to =
implement - though that's something the folks who run and manage the =
meetings would have to decide, since they'd know a lot more than us =
about that.

-hadriel


From arturo.servin@gmail.com  Fri Aug 16 05:31:04 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0720C11E8102 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 05:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HncjUr5XGZXN for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 05:31:03 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id ACF0421F9815 for <ietf@ietf.org>; Fri, 16 Aug 2013 05:30:59 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id g17so1559032vbg.14 for <ietf@ietf.org>; Fri, 16 Aug 2013 05:30:59 -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=OzscKUq2f2QrqMBfD2xC/AfvvgHA5a+QgOTmCvpgi7U=; b=iJri3Md2wEr4SM0sDT8sKubvwGRJhOCauH9I//7z0Bg+4AwSLSKxhjppqkzEcePa+i 6R6NcwJOHMzSDvHjuWTIHzDSmgzgBLh+JA87rmakIi2HCV0KeQqiwFrGwFRXOrjW9jGP MxT/IQZ8SbuaH/X/dALQ9ZaINHu7vpdZvRcI2mh7M5tY+rPhMFVxQAjzNsqtvU2D4bp4 wHMW+/lBv+SMm2+2Qru8bhb0EqOcNbsC+i7wsFHekvOdvJVKTL//ooutxS+5R8c8HkO8 uopCbUu5GoaQ6I755p0diF6l0bOvV31PCeao1LSldNPL0j/jymdp50ZMTSd4MhT7hOY/ y7jA==
X-Received: by 10.52.120.114 with SMTP id lb18mr884555vdb.23.1376656259109; Fri, 16 Aug 2013 05:30:59 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:89fe:2017:540a:a2d5]) by mx.google.com with ESMTPSA id ev7sm189007vdc.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 Aug 2013 05:30:57 -0700 (PDT)
Message-ID: <520E1B7E.3010908@gmail.com>
Date: Fri, 16 Aug 2013 09:30:54 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Radical Solution for remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com> <20130813102459.GC68553@verdi> <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com>
In-Reply-To: <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 12:31:04 -0000

	Well, we just had a technical session about Real Time web.

	This seems to me like the perfect application to show and eat own dog food.

	
Regards,
as

On 8/16/13 9:07 AM, Hadriel Kaplan wrote:
> The next step up from our current jabber-scribe model is to have audio input - the ability for remote participants to speak using their own voice, when it's their turn at the 'mic'.  The next step up after that is video input, where remote participants can be seen as well as heard.  Both of those are technically achievable, and possibly even practical to implement - though that's something the folks who run and manage the meetings would have to decide, since they'd know a lot more than us about that.

From hadriel.kaplan@oracle.com  Fri Aug 16 06:11:04 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6676D21F96B1 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 06:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.337
X-Spam-Level: 
X-Spam-Status: No, score=-6.337 tagged_above=-999 required=5 tests=[AWL=0.262,  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 Ai3q2rNHLNNJ for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 06:10:57 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id B3FAF21F991F for <ietf@ietf.org>; Fri, 16 Aug 2013 06:10:57 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GDAuFs031391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Fri, 16 Aug 2013 13:10:57 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GDAt0I003821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 16 Aug 2013 13:10:56 GMT
Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GDAtvb021554 for <ietf@ietf.org>; Fri, 16 Aug 2013 13:10:55 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 06:10:55 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
Date: Fri, 16 Aug 2013 09:10:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 13:11:04 -0000

Since the topic keeps getting raised... I think that charging remote =
participants any fee is a really terrible idea.  One of the really great =
things about the IETF is its open and free (as in beer) participation =
policy.  The real work is supposed to be done on mailing lists, and =
there's no charge or restriction on who can send emails.  That policy is =
actually quite rare for standards bodies, and makes our output better =
not worse.

Obviously we discuss things and do real work at physical meetings too, =
and they're not simply social occasions.  At the end of the day we =
actually want people to come to the physical meetings, but the realities =
of life make that impossible for many.  But charging remote participants =
for better tools/experience isn't the answer.  At least for me, whenever =
I'm discussing a draft mechanism I actually *want* input from remote =
participants.  I don't want it to be only from folks who can afford to =
provide input.  I want it from people who can't get approval for even a =
$100 expense, from people who are between jobs, people from academia, =
and even from just plain ordinary users rather than just vendors or big =
corps.  At one time we worried that free remote participation would lead =
to too many random participants to get work done, but that hasn't become =
a problem afaict.  Please don't whittle it down further to only those =
who can afford it.

I would do anything whatsoever to avoid charging remote participants, =
even if it means raising the fee for f2f attendees to subsidize =
remote-participant tooling costs.

In that vein, I think a lot of the f2f attendees get our reg-fee paid by =
our employer and another $50 or even $100 isn't going to make a bit of =
difference for us - for those whom it would make a difference, I'd =
create another category of f2f registration fee like 'Self-paying =
Attendee' or some such.  Selecting the new category would drop your fee =
by the $50 or $100, but wouldn't change what gets displayed on your =
badge or anything.  It would be purely optional, with no guilt attached =
for not paying it and no visible difference to anyone else.  Just put =
some words on the registration form page saying something like "If you =
cannot expense your registration fee, please select the 'Self-paying =
Attendee' category" or something like that.  Or make it some checkbox =
thingy.  I believe the majority of folks who can expense it will not =
have difficulty expensing a 'Regular Attendee' charge so long as it =
doesn't say we opted to pay more.

-hadriel

p.s. Even from a purely practical standpoint, charging remote =
participants raises a lot of issues - we debate incessantly just about =
the f2f day-pass, and that's nothing compared to this.  For example: if =
things break during the meeting session, do we re-imburse them?  Do we =
pro-rate the re-imbursement based on how many of their meetings had =
technical issues with audio or video?  Do we charge a flat fee for the =
whole week of meetings, or just charge per meeting session, or depending =
on how long the session is?  Do we charge students a different rate, =
like we do f2f reg-fees?  Do we need to provide tech support with a =
specific SLA?  This while thing is a can of worms.  It's not worth it.


From hadriel.kaplan@oracle.com  Fri Aug 16 06:28:40 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD7211E8134 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 06:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.352
X-Spam-Level: 
X-Spam-Status: No, score=-6.352 tagged_above=-999 required=5 tests=[AWL=0.247,  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 0pFUn2nCRm1i for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 06:28:33 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 642D611E80EC for <ietf@ietf.org>; Fri, 16 Aug 2013 06:28:33 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GDSVF3003268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Aug 2013 13:28:32 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GDSVv4011542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 13:28:31 GMT
Received: from abhmt113.oracle.com (abhmt113.oracle.com [141.146.116.65]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GDSVS9011537; Fri, 16 Aug 2013 13:28:31 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 06:28:30 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Radical Solution for remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <520E1B7E.3010908@gmail.com>
Date: Fri, 16 Aug 2013 09:28:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <92D8F3ED-6940-4E60-AB40-925E749ACEF9@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com> <20130813102459.GC68553@verdi> <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com> <520E1B7E.3010908@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 13:28:40 -0000

Yes, that had also occurred to me. :)

It does cost money though... if even for just additional equipment, tech =
support and administration, and a separate presentation screen in the =
rooms.  And it's one more thing for the folks who run the meetings to =
worry about, plan for, deal with, etc. - and that's a real cost too.  As =
far as I can tell it's not the up-front capex costs of a technology that =
really matter much, it's the recurring opex costs.

-hadriel


On Aug 16, 2013, at 8:30 AM, Arturo Servin <arturo.servin@gmail.com> =
wrote:

>=20
> 	Well, we just had a technical session about Real Time web.
>=20
> 	This seems to me like the perfect application to show and eat =
own dog food.
>=20
> =09
> Regards,
> as
>=20
> On 8/16/13 9:07 AM, Hadriel Kaplan wrote:
>> The next step up from our current jabber-scribe model is to have =
audio input - the ability for remote participants to speak using their =
own voice, when it's their turn at the 'mic'.  The next step up after =
that is video input, where remote participants can be seen as well as =
heard.  Both of those are technically achievable, and possibly even =
practical to implement - though that's something the folks who run and =
manage the meetings would have to decide, since they'd know a lot more =
than us about that.


From jgunn6@csc.com  Fri Aug 16 06:38:16 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E8311E80EC; Fri, 16 Aug 2013 06:38:15 -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 34iDFkP-Mrv9; Fri, 16 Aug 2013 06:38:07 -0700 (PDT)
Received: from mail210.messagelabs.com (mail210.messagelabs.com [216.82.250.179]) by ietfa.amsl.com (Postfix) with ESMTP id 25D1D11E8134; Fri, 16 Aug 2013 06:38:07 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-15.tower-210.messagelabs.com!1376660284!13500210!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16628 invoked from network); 16 Aug 2013 13:38:05 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-15.tower-210.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Aug 2013 13:38:05 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (8.13.8/8.13.8) with ESMTP id r7GDYWY5010653; Fri, 16 Aug 2013 09:34:32 -0400
In-Reply-To: <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
MIME-Version: 1.0
Subject: Re: Charging remote participants
X-KeepSent: 7C8B5CF8:DD8CFB55-85257BC9:004A95C2; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com>
Date: Fri, 16 Aug 2013 09:38:02 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/16/2013 09:31:23 AM, Serialize complete at 08/16/2013 09:31:23 AM
Content-Type: multipart/alternative; boundary="=_alternative 004AE54E85257BC9_="
Cc: ietf-bounces@ietf.org, 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, 16 Aug 2013 13:38:16 -0000

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

 08/16/2013 09:10:54 AM:

> From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
>
...I want it from 
> people who can't get approval for even a $100 expense, from people 
> who are between jobs, people from academia, and even from just plain
> ordinary users rather than just vendors or big corps. 

I agree.

The realities of internal politics/funding being what they are, it is 
sometimes  going to be just as hard to get $100 "remote" fee approved as 
it as to  get the whole f2f trip approved.

Janet

--=_alternative 004AE54E85257BC9_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
<br>
</font>
<br><tt><font size=2>&nbsp;08/16/2013 09:10:54 AM:<br>
<br>
&gt; From: Hadriel Kaplan &lt;hadriel.kaplan@oracle.com&gt;</font></tt>
<br><tt><font size=2>&gt;</font></tt>
<br><tt><font size=2>...I want it from <br>
&gt; people who can't get approval for even a $100 expense, from people
<br>
&gt; who are between jobs, people from academia, and even from just plain<br>
&gt; ordinary users rather than just vendors or big corps. </font></tt>
<br>
<br><tt><font size=2>I agree.</font></tt>
<br>
<br><tt><font size=2>The realities of internal politics/funding being what
they are, it is sometimes &nbsp;going to be just as hard to get $100 &quot;remote&quot;
fee approved as it as to &nbsp;get the whole f2f trip approved.</font></tt>
<br>
<br><tt><font size=2>Janet<br>
</font></tt>
--=_alternative 004AE54E85257BC9_=--

From jgunn6@csc.com  Fri Aug 16 06:51:12 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC8D11E814E; Fri, 16 Aug 2013 06:51:12 -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 8Axt7fwwU046; Fri, 16 Aug 2013 06:51:06 -0700 (PDT)
Received: from mail87.messagelabs.com (mail87.messagelabs.com [216.82.250.19]) by ietfa.amsl.com (Postfix) with ESMTP id 0DAC211E8158; Fri, 16 Aug 2013 06:51:03 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-5.tower-87.messagelabs.com!1376661059!16972547!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28341 invoked from network); 16 Aug 2013 13:51:00 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-5.tower-87.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Aug 2013 13:51:00 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (8.13.8/8.13.8) with ESMTP id r7GDlRof001077; Fri, 16 Aug 2013 09:47:27 -0400
In-Reply-To: <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com>	<20130813102459.GC68553@verdi> <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
MIME-Version: 1.0
Subject: Re: Radical Solution for remote participants
X-KeepSent: 533FEC11:FE637A8C-85257BC9:004B2325; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF533FEC11.FE637A8C-ON85257BC9.004B2325-85257BC9.004C1485@csc.com>
Date: Fri, 16 Aug 2013 09:50:58 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/16/2013 09:44:18 AM, Serialize complete at 08/16/2013 09:44:18 AM
Content-Type: multipart/alternative; boundary="=_alternative 004C147985257BC9_="
Cc: ietf-bounces@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, John Leslie <john@jlc.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 13:51:12 -0000

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

I agree with Hadriel (probably because we attend a lot of the same WGs) 
that remote participants are not actively  ignored.

The problem is that, with the time lag, and the need to type in your 
comments in quickly, then relay them through the jabber scribe
A- the discussion has often moved on before your comment gets to the mic
B - your comment is necessarily short and, hopefully, to the point.  But 
if the audience doesn't "get" the point and misinterprets your comment, 
you really don't get an opportunity to clarify.
C- you can't participate in a back and forth "conversation"

Of the remedies listed, only 

> audio input - the ability for remote participants to speak using 
> their own voice, when it's their turn at the 'mic'.
addresses that.

(When I drag myself  out of bed at 2:30 AM for a remote meeting, even if I 
have changed into clothes, I don't think I want
video input, where remote participants can be seen 
> as well as heard. )

Janet


ietf-bounces@ietf.org wrote on 08/16/2013 08:07:56 AM:

> From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
> To: John Leslie <john@jlc.net>
> Cc: IETF Discussion Mailing List <ietf@ietf.org>
> Date: 08/16/2013 08:08 AM
> Subject: Re: Radical Solution for remote participants
> Sent by: ietf-bounces@ietf.org
> 
> 
> On Aug 13, 2013, at 6:24 AM, John Leslie <john@jlc.net> wrote:
> 
> >   There are a certain number of Working Groups where it's standard
> > operating practice to ignore any single voice who doesn't attend an
> > IETF week to defend his/her postings.
> 
> I don't see that happening in the WGs I attend - when remote 
> participants post to jabber, the jabber scribes get mic time.  I 
> think what you mean isn't really that physical participants "ignore"
> remote ones, but more that remote participants don't have as much 
> impact/weight with their input/arguments than physical participants 
> do.  Is that what you mean?
> 
> 
> >   I don't always understand what Doug is asking for; but I suspect
> > he is proposing to define a remote-participation where you get full
> > opportunity to defend your ideas. This simply doesn't happen today.
> 
> Then fix that problem.
> 
> Which solution addresses that problem:
> 1) Make remote participants pay money.
> 2) Add a separate mic line.
> 3) Add remote controls for A/V equipment.
> 4) Add XMPP controls for mic-line and humming.
> 5) None of the above.
> 
> ISTM it's (5).  Working Groups don't ignore remote participant 
> voices because they don't pay money.  They don't ignore them because
> they don't have a separate mic.  They don't ignore them because they
> don't have A/V control.  They don't ignore them because they don't 
> have XMPP controls.
> 
> WG physical participants "ignore" remote ones because they're not 
> physically present.  We're human beings.  Human beings have a 
> subconscious connection/empathy with other human beings based on our
> senses, that does not exist when we only read their words or only 
> hear them speaking... especially when it's hear them by-proxy as the
> current jabber model uses.  This isn't news to anyone - it's why 
> people travel to meet other people, and why the telepresence market 
exists.
> 
> The next step up from our current jabber-scribe model is to have 
> audio input - the ability for remote participants to speak using 
> their own voice, when it's their turn at the 'mic'.  The next step 
> up after that is video input, where remote participants can be seen 
> as well as heard.  Both of those are technically achievable, and 
> possibly even practical to implement - though that's something the 
> folks who run and manage the meetings would have to decide, since 
> they'd know a lot more than us about that.
> 
> -hadriel
> 

--=_alternative 004C147985257BC9_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
<br>
I agree with Hadriel (probably because we attend a lot of the same WGs)
that remote participants are not actively &nbsp;ignored.</font>
<br>
<br><font size=2 face="sans-serif">The problem is that, with the time lag,
and the need to type in your comments in quickly, then relay them through
the jabber scribe</font>
<br><font size=2 face="sans-serif">A- the discussion has often moved on
before your comment gets to the mic</font>
<br><font size=2 face="sans-serif">B - your comment is necessarily short
and, hopefully, to the point. &nbsp;But if the audience doesn't &quot;get&quot;
the point and misinterprets your comment, you really don't get an opportunity
to clarify.</font>
<br><font size=2 face="sans-serif">C- you can't participate in a back and
forth &quot;conversation&quot;</font>
<br>
<br><font size=2 face="sans-serif">Of the remedies listed, only </font>
<br>
<br><tt><font size=2>&gt; audio input - the ability for remote participants
to speak using <br>
&gt; their own voice, when it's their turn at the 'mic'.</font></tt>
<br><font size=2 face="sans-serif">addresses that.</font>
<br>
<br><font size=2 face="sans-serif">(When I drag myself &nbsp;out of bed
at 2:30 AM for a remote meeting, even if I have changed into clothes, I
don't think I want</font>
<br><tt><font size=2>video input, where remote participants can be seen
<br>
&gt; as well as heard. )</font></tt>
<br>
<br><tt><font size=2>Janet</font></tt>
<br>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 08/16/2013 08:07:56
AM:<br>
<br>
&gt; From: Hadriel Kaplan &lt;hadriel.kaplan@oracle.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: John Leslie &lt;john@jlc.net&gt;</font></tt>
<br><tt><font size=2>&gt; Cc: IETF Discussion Mailing List &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 08/16/2013 08:08 AM</font></tt>
<br><tt><font size=2>&gt; Subject: Re: Radical Solution for remote participants</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; On Aug 13, 2013, at 6:24 AM, John Leslie &lt;john@jlc.net&gt; wrote:<br>
&gt; <br>
&gt; &gt; &nbsp; There are a certain number of Working Groups where it's
standard<br>
&gt; &gt; operating practice to ignore any single voice who doesn't attend
an<br>
&gt; &gt; IETF week to defend his/her postings.<br>
&gt; <br>
&gt; I don't see that happening in the WGs I attend - when remote <br>
&gt; participants post to jabber, the jabber scribes get mic time. &nbsp;I
<br>
&gt; think what you mean isn't really that physical participants &quot;ignore&quot;<br>
&gt; remote ones, but more that remote participants don't have as much
<br>
&gt; impact/weight with their input/arguments than physical participants
<br>
&gt; do. &nbsp;Is that what you mean?<br>
&gt; <br>
&gt; <br>
&gt; &gt; &nbsp; I don't always understand what Doug is asking for; but
I suspect<br>
&gt; &gt; he is proposing to define a remote-participation where you get
full<br>
&gt; &gt; opportunity to defend your ideas. This simply doesn't happen
today.<br>
&gt; <br>
&gt; Then fix that problem.<br>
&gt; <br>
&gt; Which solution addresses that problem:<br>
&gt; 1) Make remote participants pay money.<br>
&gt; 2) Add a separate mic line.<br>
&gt; 3) Add remote controls for A/V equipment.<br>
&gt; 4) Add XMPP controls for mic-line and humming.<br>
&gt; 5) None of the above.<br>
&gt; <br>
&gt; ISTM it's (5). &nbsp;Working Groups don't ignore remote participant
<br>
&gt; voices because they don't pay money. &nbsp;They don't ignore them
because<br>
&gt; they don't have a separate mic. &nbsp;They don't ignore them because
they<br>
&gt; don't have A/V control. &nbsp;They don't ignore them because they
don't <br>
&gt; have XMPP controls.<br>
&gt; <br>
&gt; WG physical participants &quot;ignore&quot; remote ones because they're
not <br>
&gt; physically present. &nbsp;We're human beings. &nbsp;Human beings have
a <br>
&gt; subconscious connection/empathy with other human beings based on our<br>
&gt; senses, that does not exist when we only read their words or only
<br>
&gt; hear them speaking... especially when it's hear them by-proxy as the<br>
&gt; current jabber model uses. &nbsp;This isn't news to anyone - it's
why <br>
&gt; people travel to meet other people, and why the telepresence market
exists.<br>
&gt; <br>
&gt; The next step up from our current jabber-scribe model is to have <br>
&gt; audio input - the ability for remote participants to speak using <br>
&gt; their own voice, when it's their turn at the 'mic'. &nbsp;The next
step <br>
&gt; up after that is video input, where remote participants can be seen
<br>
&gt; as well as heard. &nbsp;Both of those are technically achievable,
and <br>
&gt; possibly even practical to implement - though that's something the
<br>
&gt; folks who run and manage the meetings would have to decide, since
<br>
&gt; they'd know a lot more than us about that.<br>
&gt; <br>
&gt; -hadriel<br>
&gt; <br>
</font></tt>
--=_alternative 004C147985257BC9_=--

From jgunn6@csc.com  Fri Aug 16 07:03:53 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860FC11E8258; Fri, 16 Aug 2013 07:03:53 -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 6z3Vh0+Lp573; Fri, 16 Aug 2013 07:03:47 -0700 (PDT)
Received: from mail87.messagelabs.com (mail87.messagelabs.com [216.82.250.19]) by ietfa.amsl.com (Postfix) with ESMTP id 4332611E8109; Fri, 16 Aug 2013 07:03:46 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-13.tower-87.messagelabs.com!1376661825!17939115!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10450 invoked from network); 16 Aug 2013 14:03:46 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-13.tower-87.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Aug 2013 14:03:46 -0000
Received: from amer-gw09.amer.csc.com (cscmail.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r7GDx1wm031061; Fri, 16 Aug 2013 09:59:01 -0400
In-Reply-To: <OF533FEC11.FE637A8C-ON85257BC9.004B2325-85257BC9.004C1485@csc.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <CAKHUCzy7d6v4S3uJ+gzcxWVoyvdACzJQ6+2uOUDZQ=LHmg5=0g@mail.gmail.com>	<20130813102459.GC68553@verdi> <77953E60-F822-4FA6-8573-509801ADE5C1@oracle.com> <OF533FEC11.FE637A8C-ON85257BC9.004B2325-85257BC9.004C1485@csc.com>
To: Janet P Gunn <jgunn6@csc.com>
MIME-Version: 1.0
Subject: Re: Radical Solution for remote participants
X-KeepSent: 16FAE7A8:A672F79D-85257BC9:004C9838; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF16FAE7A8.A672F79D-ON85257BC9.004C9838-85257BC9.004D3F98@csc.com>
Date: Fri, 16 Aug 2013 10:03:43 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/16/2013 09:57:03 AM, Serialize complete at 08/16/2013 09:57:03 AM
Content-Type: multipart/alternative; boundary="=_alternative 004D3F4E85257BC9_="
Cc: ietf-bounces@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>, John Leslie <john@jlc.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 14:03:53 -0000

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

Adding to my own comments - 

Beware of technological solutions that require software on the remote 
user's end, or network communications.
 
Many employers have strict policies about what is allowed to be installed 
on company computers.

Furthermore, some have draconian firewalls.  For instance, my employer's 
network blocks jabber. They used to block the streaming audio too.  They 
are likely to block anything "new" they have not officially approved. 

 I have to isolate myself from the company network, and use a separate 
connection, to use jabber from the office. 

Janet




ietf-bounces@ietf.org wrote on 08/16/2013 09:50:58 AM:

> From: Janet P Gunn/USA/CSC@CSC
> 
> 
> 
> 
> I agree with Hadriel (probably because we attend a lot of the same 
> WGs) that remote participants are not actively  ignored. 
> 
> The problem is that, with the time lag, and the need to type in your
> comments in quickly, then relay them through the jabber scribe 
> A- the discussion has often moved on before your comment gets to the mic 

> B - your comment is necessarily short and, hopefully, to the point. 
> But if the audience doesn't "get" the point and misinterprets your 
> comment, you really don't get an opportunity to clarify. 
> C- you can't participate in a back and forth "conversation" 
> 
> Of the remedies listed, only 
> 
> > audio input - the ability for remote participants to speak using 
> > their own voice, when it's their turn at the 'mic'. 
> addresses that. 
> 
> (When I drag myself  out of bed at 2:30 AM for a remote meeting, 
> even if I have changed into clothes, I don't think I want 
> video input, where remote participants can be seen 
> > as well as heard. ) 
> 
> Janet 
> 
--=_alternative 004D3F4E85257BC9_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Adding to my own comments - </font>
<br>
<br><font size=2 face="sans-serif">Beware of technological solutions that
require software on the remote user's end, or network communications.</font>
<br><font size=2 face="sans-serif">&nbsp; </font>
<br><font size=2 face="sans-serif">Many employers have strict policies
about what is allowed to be installed on company computers.</font>
<br>
<br><font size=2 face="sans-serif">Furthermore, some have draconian firewalls.
&nbsp;For instance, my employer's network blocks jabber. They used to block
the streaming audio too. &nbsp;They are likely to block anything &quot;new&quot;
they have not officially approved. </font>
<br>
<br><font size=2 face="sans-serif">&nbsp;I have to isolate myself from
the company network, and use a separate connection, to use jabber from
the office. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
</font>
<br><font size=2 face="sans-serif"><br>
</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 08/16/2013 09:50:58
AM:<br>
<br>
&gt; From: Janet P Gunn/USA/CSC@CSC</font></tt>
<br><tt><font size=2>&gt; </font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; <br>
&gt; I agree with Hadriel (probably because we attend a lot of the same
<br>
&gt; WGs) that remote participants are not actively &nbsp;ignored. <br>
&gt; <br>
&gt; The problem is that, with the time lag, and the need to type in your<br>
&gt; comments in quickly, then relay them through the jabber scribe <br>
&gt; A- the discussion has often moved on before your comment gets to the
mic <br>
&gt; B - your comment is necessarily short and, hopefully, to the point.
<br>
&gt; But if the audience doesn't &quot;get&quot; the point and misinterprets
your <br>
&gt; comment, you really don't get an opportunity to clarify. <br>
&gt; C- you can't participate in a back and forth &quot;conversation&quot;
<br>
&gt; <br>
&gt; Of the remedies listed, only <br>
&gt; <br>
&gt; &gt; audio input - the ability for remote participants to speak using
<br>
&gt; &gt; their own voice, when it's their turn at the 'mic'. <br>
&gt; addresses that. <br>
&gt; <br>
&gt; (When I drag myself &nbsp;out of bed at 2:30 AM for a remote meeting,
<br>
&gt; even if I have changed into clothes, I don't think I want <br>
&gt; video input, where remote participants can be seen <br>
&gt; &gt; as well as heard. ) <br>
&gt; <br>
&gt; Janet <br>
&gt; </font></tt>
--=_alternative 004D3F4E85257BC9_=--

From petithug@acm.org  Fri Aug 16 07:54:29 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7530111E8288 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 07:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6NOM3v8w9-H for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 07:54:26 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC5811E8286 for <ietf@ietf.org>; Fri, 16 Aug 2013 07:54:26 -0700 (PDT)
Received: from [IPv6:2601:9:4bc0:25:79d7:c76c:3194:4c] (unknown [IPv6:2601:9:4bc0:25:79d7:c76c:3194:4c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 2A53320388; Fri, 16 Aug 2013 16:54:19 +0200 (CEST)
Message-ID: <520E3D19.9040406@acm.org>
Date: Fri, 16 Aug 2013 07:54:17 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <BAF41B4A-D434-4974-AEB6-538288A957C1@oracle.com>
In-Reply-To: <BAF41B4A-D434-4974-AEB6-538288A957C1@oracle.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Graham Klyne <GK@ninebynine.org>, draft-petithuguenin-behave-turn-uris@tools.ietf.org, draft-nandakumar-rtcweb-stun-uri@tools.ietf.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 14:54:29 -0000

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

Hi Hadriel,

Note that the STUN URIs design is based on the TURN URI design, which was
discussed back in 2008-2009.  See my answers below.

On 08/15/2013 07:01 AM, Hadriel Kaplan wrote:
> 
> Some comments on this STUN draft and the TURN one:
> 
> 1) The ABNF in these drafts leaves no room for future extension such as 
> adding parameters.  Was that intentional?

Yes.  There is two very different kind of parameters in an URI:

1. Parameters that are used to guide the selection of the resource (basically
parameters that are input to RFC 5766 and RFC 5928).  The BEHAVE WG decided in
Dublin to not support this[1] (i.e. to not have either URI parameters or their
counterpart in the DNS).

2. Other parameters that are not used to guide the selection but that are used
by the protocol, e.g. "username",  "password", etc...  "password" was removed
for security reasons.  It was decided (although I cannot find exactly when)
that these non-guiding parameters should not be part of a TURN URI, so
"username" was removed too, as was the "auth" parameter proposed recently
(i.e. all these parameters should be part of the WebRTC RTCIceServer dictionary).

Not supporting extensibility (i.e. not being able to add these parameters
later) was agreed by default also in Dublin (see slide 5 of [2]).  IIRC,
extensibility for the first kind of parameters was found too difficult (how
implementation reacts to a new parameter?).  Extensibility for the second type
of parameters would create less issues, but as they were rejected anyway on
principle, there was no point of having a way to add them later.

For the record, I still disagree with the decision of not supporting the first
kind of parameters (RFC 5928 was even designed to support TWIST ;-) ), but
that was the consensus at the time.  I still agree with not supporting the
second kind of parameters.

Note that only the second type of parameters would apply to STUN URIs, but
they were not permitted in STUN for symmetry with the TURN URIs.


[1] https://www.ietf.org/proceedings/72/minutes/behave.txt
[2] https://www.ietf.org/proceedings/72/slides/behave-0.pdf

> 
> 2) Why do both of these docs repeat a lot of ABNF from RFC 3986, instead
> of just referencing it?  It says in the appendix some ABNF was repeated
> because RFC 3986 "are for hierarchical URIs".  I'm not exactly sure what
> that means other than you don't have a path component, but as far as I can
> tell the copied ABNF components in these STUN/TRUN drafts are verbatim
> copies of RFC 3986, all the way down to their final expansion.
> 
> For example, 'IP-literal' and all of its sub-defined parts ('IPv6address', 
> 'IPvFuture', 'h16', 'ls32') appear identical to those in RFC 3986.  In
> fact, so is 'stun-host' and 'turn-host' - it's just RFC 3986 'host' by
> another name.  Am I missing something?
> 
> Why not just have this: stunURI       = scheme ":" stun-host [ ":"
> stun-port ] scheme        = "stun" / "stuns" stun-host     = host      ;see
> section 3.2.2 of [RFC3986] stun-port     = port      ;see section 3.2.3 of
> [RFC3986]
> 
> Not a big deal, but it just seems simpler and cleaner to me to not repeat 
> ABNF from other RFCs, especially when the RFC in question is the one for 
> general URI syntax and you're defining a specific URI syntax based on it.

This was done back in 2009 during the first uri-review of the TURN URI,
following a comment by Ted Hardie.  The problem is that the TURN and STUN uris
are opaque URIs, but using these ABNF productions make them look like
hierarchical URIs, because these productions are defined in RFC 3986 only for
hierarchical URIs.  So the point was that developers may misinterpreting this
as meaning that TURN and STUN URIs can be parsed by a generic hierarchical
parser, which would be a very bad idea (as username and password would then be
parsed).

Version -06 will contain a more complete design note about this (we decided
that the design notes will stay in the RFC), here's the current version:

"o  The ABNF in this document duplicates the <IP-literal>,
    <IPv4address>, and <reg-name> productions and other dependent
    productions from [RFC3986], instead of referencing them.  This is
    because the definitions in RFC 3986 are for hierarchical URIs, so
    using these references in an opaque URI made reviewers think that
    a hierarchical URI parser could be used to parse the URIs defined
    in this document."

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBCAAGBQJSDj0WAAoJECnERZXWan7EbJwQAOIQJjxl2JtZM8oFcvSevFCG
aulKCWtmX9P067JvyeUHMBp5w3bP+piY6pKYVuBtbjhflKCW+k24cIK7vXyJ9w0N
0VjrubNIrtHYc8ORHGyASxx+92zoIHU8cssIPS/fXjho6u1tGJaJCghGlG5f9UiQ
JicqpdWagzL6KNmvpG3jOW+kXr+acSjGWJg/flwuK8SRiNlK4hWNAtzye8cPaSly
KkRrNS4ZJSDDDO7hWcKS7KgOXeyue5Vmh3OngIuOXOgpJeyITgI0F+EXnb0ius5z
i6TFrpa4HlUaaE59D9ho86fc1M9RTM81cxaj4onJeUTSpcvWSIxmOECmqPzlowzG
LlmW5qCljVG9+63j0q3ddEZXqujoL2V/5IwXg3MO6hj7/a4dcyiPLlZt0QRqO3F4
u27IyRAQBtboZzSDfpuVizIDJh4ied1RSNkJtJRI0liv3mPJYJVCUSWdLbLS9ptV
GKv9byvVYZVxLUerTfbvzGOnjogdb9jZb1FT5GDlv8jaHcqam/Z+y3t7d8piWIz2
NwOPeEftPro8UvsH2SiDOTGzEZfHH3n+V+ymvbaLJib2Z8G3VWtoWAyozt9/hj1v
YWC2QaiUHjKjHGWdldLh5h+EGI7SIILNW6GDsnfxvrkAD/Cksr6asGaXVdjus71C
Urdaqp5q7e9n5y6f+3J/
=zZ4a
-----END PGP SIGNATURE-----

From moore@network-heretics.com  Fri Aug 16 07:54:49 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB4B11E8299 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 07:54:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ozN40io9UUQf for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 07:54:42 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 24AB611E828E for <ietf@ietf.org>; Fri, 16 Aug 2013 07:54:40 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B0EAF20DEE for <ietf@ietf.org>; Fri, 16 Aug 2013 10:54:38 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Fri, 16 Aug 2013 10:54:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=FWVZo2A4P6498G9j65FLu0 l28Z4=; b=hojJyu512MUsP48k0aCE8QZ0kwq86J99MOpaBq5TnL70KiTsFvaIBJ eEJcmk+uZCqgYt1ymvEVav4trRohZOtbuzI2g0yd+lyIfeLuiOm3GCKUWvN2HNrD tR/t5CUkhApHIPb37MevqMeF2Wh6QQxnPCZWHtJlSQKsoHR9pT+yQ=
X-Sasl-enc: kXc3RVvQRqoWODFYsr/irr2Y7q1UBKfy+JdZ+/HMf/vP 1376664878
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1EA8D680119; Fri, 16 Aug 2013 10:54:38 -0400 (EDT)
Message-ID: <520E3D29.6030201@network-heretics.com>
Date: Fri, 16 Aug 2013 10:54:33 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Radical Solution for remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <D60BC4FA-F146-466B-97FB-C0AEAC9E6FBA@mnot.net> <520DE9E8.6030806@joelhalpern.com>
In-Reply-To: <520DE9E8.6030806@joelhalpern.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 14:54:49 -0000

On 08/16/2013 04:59 AM, Joel M. Halpern wrote:
> Conversely, until the technology gets that good, we must not penalize 
> the face-to-face meeting for failures of the technology.

Unfortunately, we've been doing that for many years, e.g. by forcing 
speakers to queue up at the microphones, and by arranging seating so 
that it's difficult to get to the microphones unless you're seated near 
an aisle.   If you actually think you might want to speak at a f2f 
meeting, you need to show up early (forgoing any potentially valuable 
hallway conversations) and get a seat near an aisle.

Keith


From moore@network-heretics.com  Fri Aug 16 07:56:52 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B544611E8149 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 07:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 jse8uYO8f12W for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 07:56:47 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 7DA8C21F8426 for <ietf@ietf.org>; Fri, 16 Aug 2013 07:56:32 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 35D99212CF for <ietf@ietf.org>; Fri, 16 Aug 2013 10:56:32 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 16 Aug 2013 10:56:32 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type; s=smtpout; bh=gQR4 POvEdPEo6/xznqvY4Bxa1O8=; b=cFIZ8jXyhEX1U+WL0OM9WDtPZicXQ9l1jIR9 0JMvHl5+ANSPwBcP2arWXXRuzWBWlRlhlxmUbqdeejr2pglKO8gml3ZxcygCfrzR lZ0EqZ+mG9CTkZEn9+NHxaGyaxBcroPtKm70WXn9lHYs9XojCiBZhSAMKPNgdJtm pEUMaOY=
X-Sasl-enc: 6noyglGsnjPoq8lD+2dbuPXdhqm4HigGZzpfiZWlGd59 1376664991
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 817D26800B9; Fri, 16 Aug 2013 10:56:31 -0400 (EDT)
Message-ID: <520E3D9B.5020901@network-heretics.com>
Date: Fri, 16 Aug 2013 10:56:27 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com>
In-Reply-To: <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com>
Content-Type: multipart/alternative; boundary="------------020107040106090203080701"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 14:56:52 -0000

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

On 08/16/2013 09:38 AM, Janet P Gunn wrote:
> >
> ...I want it from
> > people who can't get approval for even a $100 expense, from people
> > who are between jobs, people from academia, and even from just plain
> > ordinary users rather than just vendors or big corps.
>
> I agree.
>
> The realities of internal politics/funding being what they are, it is 
> sometimes  going to be just as hard to get $100 "remote" fee approved 
> as it as to  get the whole f2f trip approved.
As someone who just spent $3.5K out of pocket to show up in Berlin, I 
have a hard time being sympathetic to someone who won't participate 
because he has to spend $100 out of pocket.

Keith


--------------020107040106090203080701
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 08/16/2013 09:38 AM, Janet P Gunn
      wrote:<br>
    </div>
    <blockquote
cite="mid:OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com"
      type="cite"><tt><font size="2">&gt;</font></tt>
      <br>
      <tt><font size="2">...I want it from <br>
          &gt; people who can't get approval for even a $100 expense,
          from people
          <br>
          &gt; who are between jobs, people from academia, and even from
          just plain<br>
          &gt; ordinary users rather than just vendors or big corps. </font></tt>
      <br>
      <br>
      <tt><font size="2">I agree.</font></tt>
      <br>
      <br>
      <tt><font size="2">The realities of internal politics/funding
          being what
          they are, it is sometimes &nbsp;going to be just as hard to get
          $100 "remote"
          fee approved as it as to &nbsp;get the whole f2f trip approved.</font></tt>
      <br>
    </blockquote>
    As someone who just spent $3.5K out of pocket to show up in Berlin,
    I have a hard time being sympathetic to someone who won't
    participate because he has to spend $100 out of pocket.<br>
    <br>
    Keith<br>
    <br>
  </body>
</html>

--------------020107040106090203080701--

From GK@ninebynine.org  Fri Aug 16 04:19:44 2013
Return-Path: <GK@ninebynine.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 2B19A11E8136 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 04:19: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 wPYIKtjHXHn5 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 04:19:39 -0700 (PDT)
Received: from relay12.mail.ox.ac.uk (relay12.mail.ox.ac.uk [129.67.1.163]) by ietfa.amsl.com (Postfix) with ESMTP id AF7D811E80E4 for <ietf@ietf.org>; Fri, 16 Aug 2013 04:19:37 -0700 (PDT)
Received: from smtp1.mail.ox.ac.uk ([129.67.1.207]) by relay12.mail.ox.ac.uk with esmtp (Exim 4.80) (envelope-from <GK@ninebynine.org>) id 1VAI47-0000xB-dA; Fri, 16 Aug 2013 12:19:35 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=conina.local) by smtp1.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1VAI46-0001t6-4m; Fri, 16 Aug 2013 12:19:35 +0100
Message-ID: <520DFFA5.7020803@ninebynine.org>
Date: Fri, 16 Aug 2013 11:32:05 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Last Call: <draft-nandakumar-rtcweb-stun-uri-05.txt> (URI Scheme for Session Traversal Utilities for NAT (STUN) Protocol) to Proposed Standard
References: <52095E5D.5070802@ninebynine.org> <520BD147.1040505@alvestrand.no> <520C9997.2010601@ninebynine.org> <520CA7C1.6080404@alvestrand.no> <B6899EEB-F0F2-4F99-9E88-3677002104B2@oracle.com>
In-Reply-To: <B6899EEB-F0F2-4F99-9E88-3677002104B2@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Fri, 16 Aug 2013 08:02:21 -0700
Cc: Harald Alvestrand <harald@alvestrand.no>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 11:19:44 -0000

Hadriel,

I think you are making a fair case that this URI is more than just an internal 
string for use in a single protocol, which is the impression I got from the 
registration draft.

I think you're saying the URI schemes proposed provide ways for applications to 
be told about NAT-traversal resources they should use?  I can see that even if 
their in-use deployment is limited, the benefits can be relevant to a wider 
audience.

I think it would be useful if the URI scheme description could clarify that it 
is being used to identify a NAT traversal service (or something like that).

#g
--

On 15/08/2013 14:16, Hadriel Kaplan wrote:
> I agree with Harald.
>
> Both the STUN and TURN URIs really do represent what we traditionally use URIs for: they identify a physical resource, a protocol for accessing the resource, etc.  Unlike a data URL, the STUN/TURN URI is not locally/directly self-contained data - it's a resource identifier, only meaningful when resolved and accessed using the scheme's protocol and host address, with whatever attributes are encoded in the URI.
>
> Today only W3C has an immediate need for it, for the Javascript API for WebRTC, but one can envision this might be used by others as well in the future:
>
> 1) SIP might use this in a UA-config profile to tell a SIP client what STUN/TURN resources to use, or even in a REGISTER response someday.
>
> 2) XMPP might use this someday to indicate to clients what STUN/TURN servers to use for Jingle/etc.  Today it's done with a 'services' element I think, but it could be changed in the future.
>
> 3) BEHAVE WG might define a new DHCP option to tell DHCP clients a STUN/TURN server to use, in which case they could use this URI for that. (I don't know if BEHAVE's already done that, or decided not to do such a thing, but just sayin' it's another potential use-case)
>
> It's possible other protocols might use this as well someday, for example RTSP or H.323.  I'm not saying any of them *will*, but it's possible.
>
> -hadriel
>
>
>
> On Aug 15, 2013, at 6:04 AM, Harald Alvestrand <harald@alvestrand.no> wrote:
>
>> On 08/15/2013 11:04 AM, Graham Klyne wrote:
>>> Hi Harald,
>>>
>>> On 14/08/2013 19:49, Harald Alvestrand wrote:
>>>> On 08/13/2013 12:14 AM, Graham Klyne wrote:
>>> [...]
>>>>> But, in a personal capacity, not as designated reviewer, I have to ask *why*
>>>>> this needs to be a URI.  As far as I can tell, it is intended for use only in
>>>>> very constrained environments, where there seems to be little value in having
>>>>> an identifier that can appear in all the contexts where a URI may be recognized.
>>>>>
>>>>> The criteria for new URI schemes in http://tools.ietf.org/html/rfc4395 include:
>>>>>
>>>>> "New URI schemes SHOULD have clear utility to the broad Internet community,
>>>>> beyond that available with already registered URI schemes."
>>>>> -- http://tools.ietf.org/html/rfc4395#section-2.1
>>>>>
>>>>> This "utility to the broader community" is not clear to me, but I don't fully
>>>>> understand the intended scope of this protocol, so I could be missing
>>>>> something.  So, in declaring consensus for this specification, I would request
>>>>> that this aspect at least be considered.
>>>>
>>>> I can only give  my personal opinion....
>>>>
>>>> 1) This is a format for a piece of data. This data cannot be expressed using any
>>>> existing URI scheme - indeed, I don't think there exists another well-defined
>>>> textual representation of this piece of data.
>>>>
>>>> 1) This is defining an identifier that will be used in W3C-defined APIs. W3C
>>>> tends to use URIs every time they want a self-defining piece of data with a
>>>> clearly defined structure.
>>>> In the particular API where this is wanted, one wants to have STUN URIs, TURNS
>>>> URIs and TURN URIs passed over the same interface. Thus, keeping with the W3C
>>>> tradition of URIs seems reasonable.
>>>>
>>>> I think this answers the question about "utility to the broader community" to my
>>>> satisfaction - your mileage may differ, of course.
>>>
>>> Some thoughts occur to me:
>>>
>>> 1. My reading was that this is a generic NAT traversal protocol, so the requirement here is not Web/W3C specific.  But you do say "used in W3C-defined APIs"...
>>
>> Truth in advertising: One W3C-defined API.
>> The specific reference:
>>
>> http://dev.w3.org/2011/webrtc/editor/webrtc.html#dictionary-rtciceserver-members
>>
>>>
>>> 2. If this is being driven by W3C activities, this should probably be flagged with W3C TAG.  I'll raise it there.
>>>
>>> 3. URIs are not generally used as *data* formats, but rather as identifiers for resources.  Web architecture and REST principles tend to discourage information encoded in URIs in favour of data representation formats.  Cf. http://www.w3.org/TR/webarch/#uri-opacity, http://www.w3.org/2001/tag/doc/metaDataInURI-31.html
>>
>> Well, it is. The data encoded is the identification of a STUN server, which is a resource.
>>
>>>
>>> 4. If the purpose here is simply to encode data, then there does already exist a suitable URI scheme, viz data:.  A new content type can be defined to actually encode the required data, and the whole be wrapped in a data: URI.  This approach has the advantage that alternative mechanisms (other than URIs) can be used to transfer the traversal data if required (though that may be moot in the very restricted intended scope of deployment for stun:, etc.)
>>
>> Yes, but why?
>>
>>>
>>>>>
>>>>> ...
>>>>>
>>>>> Further, according to http://tools.ietf.org/html/rfc5389 it appears that there
>>>>> are security considerations with regard to the STUN protocol that it should
>>>>> not be used in isolation:
>>>>> [[
>>>>>     Classic STUN also had a security vulnerability -- attackers could
>>>>>     provide the client with incorrect mapped addresses under certain
>>>>>     topologies and constraints, and this was fundamentally not solvable
>>>>>     through any cryptographic means.  Though this problem remains with
>>>>>     this specification, those attacks are now mitigated through the use
>>>>>     of more complete solutions that make use of STUN.
>>>>>
>>>>>     For these reasons, this specification obsoletes RFC 3489, and instead
>>>>>     describes STUN as a tool that is utilized as part of a complete NAT
>>>>>     traversal solution.
>>>>> ]]
>>>>> -- http://tools.ietf.org/html/rfc5389#section-2
>>>>>
>>>>> It seems to me that creating a URI for STUN could encourage its use in
>>>>> environments outside the "more complete solutions that make use of STUN".
>>>>> This seems to be further reason that STUN[S] should not be a URI scheme.
>>>>>
>>>>> I have also suggested that, if registered, the URI scheme registration should
>>>>> carries a "health warning" to this effect, and that it is not suitable for
>>>>> general use that is not part of a "complete NAT traversal solution".  But I
>>>>> also recognize that I do not fully grasp the security implications, and that
>>>>> if those that do know better can agree that there is no potential for creating
>>>>> security risks here, this suggestion may be unnecessary.
>>>>
>>>> This URI scheme does not represent STUN. It represents configuration data that
>>>> is used to initialize a protocol machine that utilizes STUN.
>>>>
>>>> This configuration data has to be passed no matter what the format of the data
>>>> is - whether it be URI or not.
>>>>
>>>> Thus, I do not think the argument raised is really relevant to the context. The
>>>> data will be passed, and registering an URI scheme will cause no more and no
>>>> less data to be passed.
>>>>
>>>> Again, my opinion.
>>>>
>>>
>>> If the URI is used only in very constrained contexts, then I agree.
>>>
>>> But the whole point of using a URI is that, due to URI opacity, it can be used a a range of contexts where URIs are used.  If it cannot properly be used in those other contexts, I have to question if it really is a URI, as opposed to a string that happens to look like a URI.
>>
>> The subject of "if it really is an URI" has plagued the whole URI space since day one. My current opinion is that if it looks like an URI, and parses according to the URI spec, it should probably be called an URI.
>>
>> So far, we know of one context where we need this (RTCWEB). It's the first context I know of where the Web and STUN intersect. It's not certain that it'll be the last one.
>>
>>>
>>> I also note that this looks as if it may fall foul of the "confidential metadata" practice noted in the W3C TAG finding about metadata in URIs (http://www.w3.org/2001/tag/doc/metaDataInURI-31.html#hideforsecurity)
>>
>> That's why we took the "credentials" part out of the URI scheme.
>
>

From uma.chunduri@ericsson.com  Thu Aug 15 16:06:28 2013
Return-Path: <uma.chunduri@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 7FCD211E8219; Thu, 15 Aug 2013 16:06: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 ozKzQkLAR7SH; Thu, 15 Aug 2013 16:06:21 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id C6DB711E8138; Thu, 15 Aug 2013 16:06:20 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-5e-520d5eeb6002
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 1F.0F.09414.BEE5D025; Fri, 16 Aug 2013 01:06:19 +0200 (CEST)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Thu, 15 Aug 2013 19:06:18 -0400
From: Uma Chunduri <uma.chunduri@ericsson.com>
To: Stephen Kent <kent@bbn.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: RE: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Topic: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6VD0rmlAaf+56PTd+LLDqqvEOcAQEFcz9OADvJOYAAAi6WMA==
Date: Thu, 15 Aug 2013 23:06:18 +0000
Message-ID: <1B502206DFA0C544B7A60469152008631747F84B@eusaamb105.ericsson.se>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslr4dwcbmh.fsf@mit.edu> <520D3467.1080107@bbn.com>
In-Reply-To: <520D3467.1080107@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [155.53.74.98]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrELMWRmVeSWpSXmKPExsUyuXRPlO7rON4gg3t3JS22Hl7LbnH11WcW izlfV7NZPNs4n8Vi77c1jBYbZzNafFr1mMmB3WPq+VCPI0dms3gsWfKTyaPpzFFmj2sn/7IG sEZx2aSk5mSWpRbp2yVwZUxbGFpwl7Hi7/ZGpgbGZYxdjJwcEgImEs1PG9khbDGJC/fWs3Ux cnEICRxllNiz5iQ7hLOcUeLVu2msIFVsAnoSH6f+BOsQEXCR2PdsNSNIEbPATUaJI5u+MoEk hAU8JRa2rQYaxQFU5CXxq5cFwnSS+NKQB1LBIqAqsW/OQ2aQMK+Ar8Sas1CrGhgl/k7YD3Yc p4C6xJRNZ8DWMgId9/3UGrDpzALiEreezGeCOFpAYsme88wQtqjEy8f/WCFsBYkdi36xQNTr SCzY/YkNwtaWWLbwNVg9r4CgxMmZT1gmMIrNQjJ2FpKWWUhaZiFpWcDIsoqRo7Q4tSw33chg EyMw3o5JsOnuYNzz0vIQozQHi5I47yq9M4FCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGE2+ f+c7ynouv2y1oUl5ydP9O38+PmgYniD7KYVrudOOTU3TLrYcZph+7dmSRUqcVVb1Nb9+cbZI XH9pyMsn6tXzl+9Khb3KnF/l96VTGH5tc534Wsmr34bVsp2xdc+N+jBujisXb+r1hNyzaj+z dfnuFdkeLWFGXdFBXCK7XPOun2Nnzjt0XImlOCPRUIu5qDgRACJAkDGFAgAA
X-Mailman-Approved-At: Fri, 16 Aug 2013 08:02:30 -0700
Cc: "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2013 23:06:28 -0000

=20
>> The key table is analogous to the SPD in 4301, but not the PAD.


Close to SAD not SPD for some RPs as it have negotiation result including k=
eys.=20
But not definitely analogous to the PAD.

--
Uma C.=

From turchanyi.geza@gmail.com  Fri Aug 16 08:13:40 2013
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C74F611E8298 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GtjsbZwLCSiX for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:13:22 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2178121F9BD1 for <ietf@ietf.org>; Fri, 16 Aug 2013 08:13:19 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id u10so1565062lbi.0 for <ietf@ietf.org>; Fri, 16 Aug 2013 08:13: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=s3R4nQBA12gZ7nqRy3RMx1HURpB2GVrswcQ8dyV4VP8=; b=O1ylsmHdlTV8fssQ0NiJx9GhSzmAsxyZxfNzpRWKQqG5MHhZygL1bRiXbwEDXzdTx9 tJYCro2dodAcAqxuekQ3P0GOUmxPPkxf6aaK5tLaoYUvn/Ekl4e/wnKIqXyiUPfzGwOL Cf1+ZSWAdaeKJ8VUA/eTSkQYpqBatejmPuqTCKZwAuXaLL8AJcEBe/iQ2HC6TuQNJmfU Rj9BUk/U49TjHB8yurRn/8d2fiSS93MON5RTQVz73tsOvPvr++VsG8bwAq6HlcTLYGE3 eXEjsCfKsqZWTe12cvs18+/m+yPbnUgW61cZLIn6mF47NwvKLHqhpndF5cYnLvYtypKf 09vg==
MIME-Version: 1.0
X-Received: by 10.112.89.100 with SMTP id bn4mr2717670lbb.16.1376665997766; Fri, 16 Aug 2013 08:13:17 -0700 (PDT)
Received: by 10.114.81.231 with HTTP; Fri, 16 Aug 2013 08:13:17 -0700 (PDT)
In-Reply-To: <520E3D9B.5020901@network-heretics.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com>
Date: Fri, 16 Aug 2013 17:13:17 +0200
Message-ID: <CAJfR-+N0+Us4sEhP7BVPfc-P4uUvyFLcGgUM2EPZaf7yzLVrCA@mail.gmail.com>
Subject: Re: Charging remote participants
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=001a11c379ecc574b604e41207d5
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, 16 Aug 2013 15:13:40 -0000

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

Keith,

Fortunately sympathy is unidirectional, therefore I keep all my respect
towards you while totally disagree with your opinion...


On Fri, Aug 16, 2013 at 4:56 PM, Keith Moore <moore@network-heretics.com>wrote:

>  On 08/16/2013 09:38 AM, Janet P Gunn wrote:
>
> >
> ...I want it from
> > people who can't get approval for even a $100 expense, from people
> > who are between jobs, people from academia, and even from just plain
> > ordinary users rather than just vendors or big corps.
>
> I agree.
>
> The realities of internal politics/funding being what they are, it is
> sometimes  going to be just as hard to get $100 "remote" fee approved as it
> as to  get the whole f2f trip approved.
>
> As someone who just spent $3.5K out of pocket to show up in Berlin, I have
> a hard time being sympathetic to someone who won't participate because he
> has to spend $100 out of pocket.
>
> Keith
>
>

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

<div dir=3D"ltr">Keith,<br><br>Fortunately sympathy is unidirectional, ther=
efore I keep all my respect towards you while totally disagree with your op=
inion...<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">
On Fri, Aug 16, 2013 at 4:56 PM, Keith Moore <span dir=3D"ltr">&lt;<a href=
=3D"mailto:moore@network-heretics.com" target=3D"_blank">moore@network-here=
tics.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">

 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"im">
    <div>On 08/16/2013 09:38 AM, Janet P Gunn
      wrote:<br>
    </div>
    <blockquote type=3D"cite"><tt><font>&gt;</font></tt>
      <br>
      <tt><font>...I want it from <br>
          &gt; people who can&#39;t get approval for even a $100 expense,
          from people
          <br>
          &gt; who are between jobs, people from academia, and even from
          just plain<br>
          &gt; ordinary users rather than just vendors or big corps. </font=
></tt>
      <br>
      <br>
      <tt><font>I agree.</font></tt>
      <br>
      <br>
      <tt><font>The realities of internal politics/funding
          being what
          they are, it is sometimes =A0going to be just as hard to get
          $100 &quot;remote&quot;
          fee approved as it as to =A0get the whole f2f trip approved.</fon=
t></tt>
      <br>
    </blockquote></div>
    As someone who just spent $3.5K out of pocket to show up in Berlin,
    I have a hard time being sympathetic to someone who won&#39;t
    participate because he has to spend $100 out of pocket.<span class=3D"H=
OEnZb"><font color=3D"#888888"><br>
    <br>
    Keith<br>
    <br>
  </font></span></div>

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

--001a11c379ecc574b604e41207d5--

From aservin@lacnic.net  Fri Aug 16 08:26:06 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8FD11E828E for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGtObv16fXM3 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:26:05 -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 0731C11E8149 for <ietf@ietf.org>; Fri, 16 Aug 2013 08:26:05 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:7000:7196:4c0e:da83:95c1]) by mail.lacnic.net.uy (Postfix) with ESMTP id 8698030848D for <ietf@ietf.org>; Fri, 16 Aug 2013 12:25:35 -0300 (UYT)
Message-ID: <520E4484.7010404@lacnic.net>
Date: Fri, 16 Aug 2013 12:25:56 -0300
From: Arturo Servin <aservin@lacnic.net>
Organization: LACNIC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com>
In-Reply-To: <520E3D9B.5020901@network-heretics.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 15:26:06 -0000

	In some parts of the world there are good engineers that get $100 for a
week as salary.

	Charging remote participation will raise the bar even more for people
that cannot travel and their only way to participate is in mailing lists
and remotely.

	Providing good remote tools it expensive in capex and opex as stated
before, but charging remote participants it is not the way forward,
unless that payment were optional (I personally I would do it, but I
know people -students, researchers in public universities, badly paid
engineers whose employer is not convinced that the ietf is a good way to
expend money, etc.- )

Regards,
as

On 8/16/13 11:56 AM, Keith Moore wrote:
> On 08/16/2013 09:38 AM, Janet P Gunn wrote:
>> >
>> ...I want it from
>> > people who can't get approval for even a $100 expense, from people
>> > who are between jobs, people from academia, and even from just plain
>> > ordinary users rather than just vendors or big corps.
>>
>> I agree.
>>
>> The realities of internal politics/funding being what they are, it is
>> sometimes  going to be just as hard to get $100 "remote" fee approved
>> as it as to  get the whole f2f trip approved.
> As someone who just spent $3.5K out of pocket to show up in Berlin, I
> have a hard time being sympathetic to someone who won't participate
> because he has to spend $100 out of pocket.
> 
> Keith
> 

From hadriel.kaplan@oracle.com  Fri Aug 16 08:37:01 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B068E11E8155 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:37:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.389
X-Spam-Level: 
X-Spam-Status: No, score=-6.389 tagged_above=-999 required=5 tests=[AWL=0.210,  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 s2rhgmGvLx63 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:36:50 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 4190211E8119 for <ietf@ietf.org>; Fri, 16 Aug 2013 08:36:35 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GFaYQU022487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Aug 2013 15:36:35 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GFaWJJ009807 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 15:36:33 GMT
Received: from abhmt101.oracle.com (abhmt101.oracle.com [141.146.116.53]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GFaWnu028327; Fri, 16 Aug 2013 15:36:32 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 08:36:32 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <520E3D9B.5020901@network-heretics.com>
Date: Fri, 16 Aug 2013 11:36:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 15:37:01 -0000

On Aug 16, 2013, at 10:56 AM, Keith Moore <moore@network-heretics.com> =
wrote:

> As someone who just spent $3.5K out of pocket to show up in Berlin, I =
have a hard time being sympathetic to someone who won't participate =
because he has to spend $100 out of pocket.

This isn't about "fairness" or equal-pain-for-all.  It's about getting =
work done and producing good output.  Whether someone remote has to pay =
$0 or $1000 won't change your $3.5k out-of-pocket expense.  If you don't =
feel the $3.5k was worth it for you to go physically, don't go.

But let's say we go deploy some more tools for remote participants, and =
want to subsidize that additional cost.  Because making f2f folks pay =
out-of-pocket to subsidize remote participants reduces the incentive for =
them to come physically, I suggested we have a 'Self-paying Rate' =
category or check-box in the registration form page that removes any new =
additional remote-participant subsidy from the reg-fee cost.  Those of =
us who can expense the reg-fee won't select that, and can expense the =
new full amount.[1]  Nothing on the badges or attendee list or whatever =
would show any difference... it's purely a registration form/receipt =
thing.

[Fwiw, I think people still get their money's worth to go, though $3.5k =
is pushing it.  I assume it was that high for you because you're in the =
US and it was quite expensive to fly there - I find US-based f2f =
meetings are far cheaper for US folks, but I assume they're more =
expensive for non-US folks so in that sense it's good we rotate meeting =
locations.]

-hadriel
[1] Sure some people may claim Self-Paying status even when expensing =
their fee, but that's ok so long as many people pay the full amount.  =
Speaking just for myself, every employer I've worked at so far would =
have paid the full amount - it just can't be an opt-in to pay more, nor =
look like we're 'donating' or stuff like that.  It's got to be a =
'Regular Rate' or some such for our receipts, while the other type says =
'Self-Paying Rate' or some such on their receipts.  And it can't be like =
$1000 more, but $100 is reasonable.


From dhc@dcrocker.net  Fri Aug 16 08:56:07 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60FF421F9C4A for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:56:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.572
X-Spam-Level: 
X-Spam-Status: No, score=-6.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqrndCMJqIj6 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:55:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 176E711E8164 for <ietf@ietf.org>; Fri, 16 Aug 2013 08:55:59 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7GFtt2L002046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Aug 2013 08:55:58 -0700
Message-ID: <520E4B79.6040208@dcrocker.net>
Date: Fri, 16 Aug 2013 08:55:37 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
In-Reply-To: <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 16 Aug 2013 08:55:58 -0700 (PDT)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 15:56:07 -0000

On 8/16/2013 6:10 AM, Hadriel Kaplan wrote:
> Since the topic keeps getting raised... I think that charging remote
> participants any fee is a really terrible idea.  One of the really
> great things about the IETF is its open and free (as in beer)
> participation policy.  The real work is supposed to be done on
> mailing lists, and there's no charge or restriction on who can send
> emails.  That policy is actually quite rare for standards bodies, and
> makes our output better not worse.

The IETF has never been free.  Actually, it's quite expensive.

We've maintained the myth that it's free because we've had long-term 
funding support from the outside, originally dubbed "daddy pays".  First 
it was ARPA, then CNRI and now ISOC (and wealthy corporations).

Having a wealthy benefactor is definitely pleasant, but it is also 
fragile.  It does not take much for funding or political problems to 
develop.

Currently, primary IETF funding comes from 3 sources:

    1. ISOC

    2. Face-to-face meeting attendees

    3. Face-to-face sponsors

Each of these represents a sizable pool, although the sponsors require 
significant, on-going effort to recruit (the formal term is cost of sales).

ISOC is the main 'daddy' in the equation because it graciously and 
reliably gives the IETF whatever money is asked for.  There's a large 
annual budget that gets approved, but ISOC readily adds to that when 
asked. And one certainly cannot fault ISOC for this, of course. 
Nevermind that supporting the IETF is one of ISOC's main reasons for 
existence; it's still darn nice of them, and darn lucky that they have 
such a reliable and large base of their own funding.

Sponsors and the bulk of meeting attendee fees constitute another daddy, 
in this case an aggregate corporate daddy.  Wealthy organizations.

But the resulting financial model for the IETF isn't very business-like. 
  We regularly make expenditure choices on a well-intentioned whim.  We 
do it because, contrary to the real world, we don't suffer meaningful 
financial downsides for poor choices.  Daddy will keep paying.

Robust organizations make sure they have diverse revenue sources.  In 
the case of the IETF, we need to balance between easy, inclusive access 
by the widest possible range of possible participants, versus diverse 
funding to ensure both financial and political robustness.


>   But charging remote
> participants for better tools/experience isn't the answer.  At least
> for me, whenever I'm discussing a draft mechanism I actually *want*
> input from remote participants.  I don't want it to be only from
> folks who can afford to provide input.  I want it from people who
> can't get approval for even a $100 expense, from people who are
> between jobs, people from academia, and even from just plain ordinary
> users rather than just vendors or big corps.  At one time we worried
> that free remote participation would lead to too many random
> participants to get work done, but that hasn't become a problem
> afaict.  Please don't whittle it down further to only those who can
> afford it.

The diversity of participation /is/ a problem and always has been. 
However it also is a benefit, and always has been.  So, yes, we want to 
continue to make highly diverse participation easy.

But we still have bills to pay.  So it's not reasonable to argue against 
one source of revenue in the absence of a compensating argument in favor 
of another.

As remote participation tools get better, it is likely that we will have 
more remote attendees and fewer face-to-face ones.  This likely means 
significant reduction in attendee fees but also could challenge sponsor 
fees, since the marketing benefit of sponsorship for the f2f will likely 
go down.

The IETF already has a modest program for free or subsidized 
participation in the face-to-face meeting.  Attention to the diverse 
access you cite would recommend extending it to remote participation, 
should fees be imposed.


> I would do anything whatsoever to avoid charging remote participants,
> even if it means raising the fee for f2f attendees to subsidize
> remote-participant tooling costs.

So, you want to make the f2f meetings even more exclusionary than they 
already are?  The meetings are already dominated by well-funded 
corporate attendees.  Higher fees will screen out some additional 
percentage of the others who currently find a way to pay for attendance.


> In that vein, I think a lot of the f2f attendees get our reg-fee paid
> by our employer and another $50 or even $100 isn't going to make a
> bit of difference for us

For you.  For other well-funded corporate attendees.  But each increment 
makes a difference for anyone on a tight budget.

So yes:

> - for those whom it would make a difference,
> I'd create another category of f2f registration fee like 'Self-paying
> Attendee' or some such.  Selecting the new category would drop your
> fee by the $50 or $100, but wouldn't change what gets displayed on
> your badge or anything.  It would be purely optional, with no guilt
> attached for not paying it and no visible difference to anyone else.

Why cannot a model like this also apply to fees for remote participation?


> p.s. Even from a purely practical standpoint, charging remote
> participants raises a lot of issues - we debate incessantly just
> about the f2f day-pass, and that's nothing compared to this.  For
> example: if things break during the meeting session, do we re-imburse
> them?  Do we pro-rate the re-imbursement based on how many of their
> meetings had technical issues with audio or video?
...
> It's not worth it.

OK.  Let's not put effort into thinking through a robust revenue model. 
  Let's stay with daddy pays.

d/



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From andy@yumaworks.com  Fri Aug 16 08:56:52 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64DEF21F9C4A for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:56:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level: 
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=-0.283,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8z3hMnbbCWVC for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 08:56:48 -0700 (PDT)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by ietfa.amsl.com (Postfix) with ESMTP id 02EF311E828F for <ietf@ietf.org>; Fri, 16 Aug 2013 08:56:47 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id r10so2428576pdi.14 for <ietf@ietf.org>; Fri, 16 Aug 2013 08:56:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UOSsbIgaIE7cKca3ntWaz56qGeReZHzA9WrFoTciGgs=; b=WXYGw2FNBBXsstqvofTgAW6vsCdt9mcBRlfyLPhb42bZoFHbr30ej4fGmqAhYzfdkV 7qNE57NhiYBuGjrN4o0uyIgFweW61hbsh893PtWxl8sDWsgiYgkgs3nDX93BrgAcMlwg 8ozbJBFuQ1gDKObH4CHRvRTsr7nk69Rz0hy8ibafBQbKkPeOZexmEnRZewizHa5Ur2i+ rRbbysy4bUoBgcEBp3GUccLtWXHfvy3sDkDCgp9kVo6BNFgzgThkaKJd6gy5mZzx0sJX 5yQNiw0Zr9wIx3ZCoZ6/aKg7kvZWOB5xgNZQFu+v0Pmxky2nvHUHQdOL9XsPtgFK/rXc HwcA==
X-Gm-Message-State: ALoCoQkgphuH0zS2iCVl1HULxfYXgxs1y1ztU6tgzNWD3u6vG51wucJljXlVWPTw0yrnyfdmSwhi
MIME-Version: 1.0
X-Received: by 10.68.189.5 with SMTP id ge5mr112451pbc.42.1376668603419; Fri, 16 Aug 2013 08:56:43 -0700 (PDT)
Received: by 10.70.41.162 with HTTP; Fri, 16 Aug 2013 08:56:43 -0700 (PDT)
In-Reply-To: <520DE9E8.6030806@joelhalpern.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <D60BC4FA-F146-466B-97FB-C0AEAC9E6FBA@mnot.net> <520DE9E8.6030806@joelhalpern.com>
Date: Fri, 16 Aug 2013 08:56:43 -0700
Message-ID: <CABCOCHScnBXrTsJ0LFdyQQsg1MT28EodjbWUNRED0A-YamBcRg@mail.gmail.com>
Subject: Re: Radical Solution for remote participants
From: Andy Bierman <andy@yumaworks.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion Mailing List <ietf@ietf.org>, John Leslie <john@jlc.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 15:56:52 -0000

Hi,

+1

On Fri, Aug 16, 2013 at 1:59 AM, Joel M. Halpern <jmh@joelhalpern.com> wrot=
e:
> Maybe I am missing something.
> The reason we have face-to-face meetings is because there is value in suc=
h
> meetings that can not reasonably be achieved in other ways.
> I would like remote participation to be as good as possible.  But if woul=
d
> could achieve "the same as being there" then we should seriously consider
> not meeting face-to-face.

Being at the IETF for a week is never going to be the same experience
as participating remotely at a computer for a couple 2 hour meetings.
A lot of work gets done outside the official WG meetings because
the right people can all be in the same room at the same time.

IMO we should be using more virtual interim meetings,
not trying to turn our f2f meetings into remote meetings.
WGs should meet virtually at least once a month for 2 - 4 hours
to make progress on issues same as via the WG mailing list.
Everybody is a remote participant in a virtual interim so
the problems with interfacing to a live meeting go away.

> Conversely, until the technology gets that good, we must not penalize the
> face-to-face meeting for failures of the technology.
>
> Yours,
> Joel


Andy

>
> On 8/15/13 9:48 PM, Mark Nottingham wrote:
>>
>>
>> On 13/08/2013, at 11:00 AM, Douglas Otis <doug.mtview@gmail.com> wrote:
>>>
>>>
>>> 1) Ensure exact digital interfaces driving projectors are fully availab=
le
>>> remotely.
>>
>>
>> That would be fantastic, if feasible. Much simpler than sharing through
>> software.
>>
>>
>>> 2) Ensure Audio access requires an identified request via XMPP prior to
>>> enabling either a remote or local audio feed.
>>
>>
>> Hm.
>>
>>>
>>> 3) RFI tags could facilitate enabling local audio feed instead of an
>>> identified request via XMPP.
>>
>>
>> Could be quite interesting; many conferences now provide attendees with
>> RFID tags...
>>
>>>
>>> 4) In the event of the local venue loosing Internet access, the device
>>> regulating A/V presentations must be able to operate in a virtual mode =
where
>>> only remote participants are permitted to continue the meeting proceedi=
ngs.
>>
>>
>> That seems=85 extreme.
>>
>>> 5) Important participants should plan for alternative modes of Internet
>>> access to remain part of the proceedings.
>>
>>
>> Not exactly practical.
>>
>>>
>>> 6) Develop a simple syntax used on XMPP sessions to:
>>> 1) signify a request to speak on X
>>> 2) withdraw a request to speak on X
>>> 3) signify support of Y
>>> 4) signify non-support of Y
>>> 5) signal when a request has been granted or revoked.  For local
>>> participants this could be in the form of a red or green light at their
>>> microphone.
>>
>>
>> The W3C does much of this already with IRC bots, e.g.:
>>    http://www.w3.org/2001/12/zakim-irc-bot.html
>>
>> (also can pick a scribe, track an agenda, etc.)
>>
>>
>>> 7) Develop a control panel managed by chairs or their proxies that
>>> consolidate and sequence requests and log support and nonsupport indica=
tions
>>> and the granting of requests.
>>
>>
>> See above (I think).
>>
>>>
>>> 8) Chairs should be able to act as proxies for local participants lacki=
ng
>>> access to XMPP.
>>
>>
>> Not practical, unless they delegate.
>>
>>>
>>> 9) Chairs should have alternative Internet access independent of that o=
f
>>> the venue's.
>>
>>
>> Seems extreme.
>>
>>>
>>> 10) Establish a reasonable fee to facilitate remote participants who
>>> receive credit for their participation equal to that of being local.
>>>
>>> 11) The device regulating A/V presentations must drive both the video a=
nd
>>> audio portions of the presentations.  A web camera in a room is a very =
poor
>>> replacement.
>>>
>>> 12) All video information in the form of slides and text must be
>>> available from the Internet prior to the beginning of the meeting.
>>
>>
>> Cheers,
>>
>>
>> --
>> Mark Nottingham   http://www.mnot.net/
>>
>>
>>
>>
>

From carlosm3011@gmail.com  Fri Aug 16 09:07:27 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5535A11E8152 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 09:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPH6rAE4toVw for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 09:07:26 -0700 (PDT)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 1F2DA11E8149 for <ietf@ietf.org>; Fri, 16 Aug 2013 09:07:18 -0700 (PDT)
Received: by mail-vc0-f182.google.com with SMTP id hf12so1641138vcb.27 for <ietf@ietf.org>; Fri, 16 Aug 2013 09:07:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=LmzwvTNkZfd7Lj6Z+r07Lsr5ekEEcwa9Di2hPVAeWGw=; b=sfCw5hx2WzAUVDtaXxYQr2Pi4MWNp+s1JSDEe0nufbYFUkDjbASnMEij2YfNFERNeI fll2yBc+X+PfsT9HtAkf+VkvukCpdcQtIf4q9QJKsrOM78qA4wcLd4djlE9RtLzcJX8d fecLQxHgkvmk//3YvGI4tanyru50DI4bUQ8UAZNq5ZYaY7CzQraI3wuohbA+pZLukmmh yFplWS6sQQeyI6lXPXC0IWGGlDIpoHeHQOj6MAkWU7Tlz0qX2yfa42ZuUoW/8yTMqKP1 EksZB7BRfbAC8inRmnkezQZGJnJTUH+rlLR+LQoGM8HoHviM0Nsj5wx1VkL+2q9AP4qk RtVA==
X-Received: by 10.58.100.234 with SMTP id fb10mr1930193veb.5.1376669236568; Fri, 16 Aug 2013 09:07:16 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:5058:db84:6a58:a7cc]) by mx.google.com with ESMTPSA id hu9sm321107vdb.11.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 Aug 2013 09:07:15 -0700 (PDT)
Message-ID: <520E4E2E.2090708@gmail.com>
Date: Fri, 16 Aug 2013 13:07:10 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com>
In-Reply-To: <520E3D9B.5020901@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 16:07:27 -0000

Hello,

On 8/16/13 11:56 AM, Keith Moore wrote:

> As someone who just spent $3.5K out of pocket to show up in Berlin, I
> have a hard time being sympathetic to someone who won't participate
> because he has to spend $100 out of pocket.

Funny reading that under the light of the IETF worried about increasing
participation and diversity. There are places in the world where $100 is
all the disposable income an engineer *might* have. For months.

And, before the IETF would commit to take steps in that direction, it
would be interesting to see some numbers about how much money needs to
be invested in deploying and operating remote participation tools that
would actually make people feel they are getting value back for a $100
remote attendance fee.

I can already imagine the complain threads in the [XXattendees-remote]
list. Oh, the humanity!

~Carlos

From david.black@emc.com  Fri Aug 16 10:01:07 2013
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 D239421F9AEF; Fri, 16 Aug 2013 10:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SDlzf6VHIBZc; Fri, 16 Aug 2013 10:01:02 -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 088F521F9A2A; Fri, 16 Aug 2013 10:01:00 -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 r7GH0YWt004445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 13:00:36 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Fri, 16 Aug 2013 13:00:14 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7GH0Dvp023435; Fri, 16 Aug 2013 13:00:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Fri, 16 Aug 2013 13:00:12 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietfc@mit.edu>
Date: Fri, 16 Aug 2013 13:00:11 -0400
Subject: RE: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
Thread-Topic: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6ZIxPCrHP82d6uQRm+ncYL1wquCwBezKGg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489288@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslvc38cc7p.fsf@mit.edu>
In-Reply-To: <tslvc38cc7p.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "Black, David" <david.black@emc.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:01:08 -0000

Sam,

Thanks for picking this up.  Unlike my other two concerns with this draft,
I think we have a longer discussion ahead of us on this one.

Your summary of my concern is on the mark:

> David's main concern is that bad security will get registered.

I understand the response to be two-fold:

1) It doesn't matter; the controlling registry for crypto algorithm usage
is the protocol-specific registry, not the key table database registry.

2) The guidance for the Expert Reviewer will be very difficult to write.

I'm not convinced by either of these, sorry.

I'm concerned that the two-registry subtlety in 1) will be lost on
implementers, especially because (as mentioned in the IESG thread), this
key table database is likely to see use beyond routing protocols.  Among
other things, it's being proposed as a general mechanism for keying RSVP,
not just RSVP-TE (I'm one of the co-chairs of the tsvwg WG that's
responsible for RSVP).  That key table databases registry is also likely
to be a place that designers of new protocols look to figure out what to
use for security.

As for cleartext passwords:

> Also, some routing protocols are protected by cleartext passwords sent
> over the network.  We want to be able to manage that, so we will be
> registering plaintext password in these registries.
> I don't think anyone will come up with anything worse than that.

I read the first sentence in Section 2 of this draft as excluding
cleartext passwords:

   The database is characterized as a table, where each row represents
   a single long-lived symmetric cryptographic key.

If someone wants to argue that a cleartext password is a "long-lived
symmetric cryptographic key", I'll go break out the popcorn and watch
w/amusement :-).

Seriously, if the intention is to include cleartext passwords, then I
think some more rewriting is in order, and I would suggest checking
directly with the Security ADs before going there.

As for 2), the fact that it will be difficult (with which I agree)
doesn't imply that it isn't necessary or shouldn't be done.  IMHO, we
really should be setting a bar that says that this sort of IETF
imprimatur of approval of a crypto algorithm actually means something.

I appreciate that FCFS provides an easier path forward, however I'm
reminded by analogy of something I learned from my grad school
software engineering professor:

	I can make the code run arbitrarily fast ...
	...  if it doesn't have to be correct.

I'm rather uncomfortable with this use of process expediency as a
rationale for avoiding a technical concern.

This may ultimately be an issue that the IESG needs to sort out, as the
level of security for IETF protocols and concerns about "vanity crypto"=20
extend well beyond the karp WG, but discussion ought to start here.

Thanks,
--David


> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietfc@mit.edu]
> Sent: Wednesday, August 14, 2013 3:19 PM
> To: Black, David
> Cc: housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
> (zhangdacheng@huawei.com); General Area Review Team (gen-art@ietf.org);
> karp@ietf.org; ietf@ietf.org
> Subject: Re: [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
>=20
>=20
>=20
> David, as we mentioned in the IESG thread, we seem to have dropped the
> response to your comments about IANA actions.
>=20
> WG:
> From the genart review:
>=20
> [9] I suggest Expert Review for the new IANA registries, not just
> First Come First Served, so that someone with a security "clue" can
> check that the proposed registrations are reasonable.
>=20
>=20
> Stephen has filed a related DISCUSS position.  He's confused why we need
> a registry for  KDFs or algorithms.
> He argues that the protocols should already have such a registry.  He
> argues that it would be non-sensical to register a value in this
> registry but not the protocol registry.
>=20
> In a somewhat related discussion, multiple people have asked what the
> scope of this document is.  Are we defining something for routing
> protocols?  Any security protocol in the world?  Something in-between?
>=20
>=20
> IU'm going to make two responses:
>=20
> 1)
> I think FCFS is not harmful for these registries.
>=20
> David's main concern is that bad security will get registered.
>=20
> I'll point out that these registries are not about what security you can
> use with a routing protocol, but about what security you can configure
> from a management standpoint.
> Registering rot13 or similarly questionable security here wouldn't mean
> I could use it with a routing protocol, only that I could ask a system
> to do so.  If ROT13 was not actually in the security-specific registries
> for the protocols in question there'd be no way to send a
> rot13-transformed message.
>=20
> I think people wanting to use bad security in routing protocols will
> focus on specifying how to use the security for the protocols, and
> that's the appropriate place to do any gateway review.
> Yeah, I guess with FCFS it's possible someone could register here and
> then later realize they cannot get their md4 security approved in the
> actual protocol registry document.
>=20
> That might be confusing but doesn't seem very harmful.
>=20
> Also, some routing protocols are protected by cleartext passwords sent
> over the network.  We want to be able to manage that, so we will be
> registering plaintext password in these registries.
> I don't think anyone will come up with anything worse than that.
>=20
> Finally, I think a lot of us have begun to question the value in
> security review for codepoint assignment.  Some security WGs care a lot;
> some don't seem to care much at all.
>=20
> 2)  Why I prefer FCFS or at least would object strongly to expert
> review.
>=20
> If we're going to say we want expert review I want us to give  expert
> instructions at least good enough that I believe I could answer the
> question of what registrations to approve if I were appointed the
> expert.
>=20
> I don't think we could come to consensus on those instructions very
> easily.
> In particular, I think it would be challenging for us to describe what
> security protocols the protocol registry applies to and which ones it
> does not.
>=20
> I'm totally fine publishing this document knowing it will be used for
> routing protocols but not knowing what beyond routing protocols it will
> be used for.
> If we do that FCFS makes a lot of sense.
>=20
> So, my recommendation is that we keep our current registration policy.


From dwm@xpasc.com  Fri Aug 16 10:09:27 2013
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5B9A11E8174 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rdro+-5jVBCa for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:09:18 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 245E611E8281 for <ietf@ietf.org>; Fri, 16 Aug 2013 10:09:15 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 519CD3F8B4 for <ietf@ietf.org>; Fri, 16 Aug 2013 17:09:12 +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 r7GH9BgN021769 for <ietf@ietf.org>; Fri, 16 Aug 2013 10:09:11 -0700
Date: Fri, 16 Aug 2013 10:09:11 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Charging remote participants
In-Reply-To: <520E3D9B.5020901@network-heretics.com>
Message-ID: <alpine.LRH.2.01.1308161006250.21583@egate.xpasc.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:09:27 -0000

On Fri, 16 Aug 2013, Keith Moore wrote:

> On 08/16/2013 09:38 AM, Janet P Gunn wrote:
> > >
> > ...I want it from
> > > people who can't get approval for even a $100 expense, from people
> > > who are between jobs, people from academia, and even from just plain
> > > ordinary users rather than just vendors or big corps.
> > 
> > I agree.
> > 
> > The realities of internal politics/funding being what they are, it is
> > sometimes  going to be just as hard to get $100 "remote" fee approved as it
> > as to  get the whole f2f trip approved.
> As someone who just spent $3.5K out of pocket to show up in Berlin, I have a
> hard time being sympathetic to someone who won't participate because he has to
> spend $100 out of pocket.

As someone who couldn't justify the $3k+ to attend the meeting, and for 
whom attending a meeting implies substantial lost revenue opportunities,
the $100 (or more) fee for first class remote participation would be
awesome.

From david.black@emc.com  Fri Aug 16 10:50:04 2013
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 269D821F92B9; Fri, 16 Aug 2013 10:50: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=[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 ExS4MwCrFlK8; Fri, 16 Aug 2013 10:49:58 -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 626BC21F844D; Fri, 16 Aug 2013 10:49:57 -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 r7GGVjBB013274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 12:31:46 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 16 Aug 2013 12:31:23 -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 r7GGVMQ7020802; Fri, 16 Aug 2013 12:31:23 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub23.corp.emc.com ([128.222.70.135]) with mapi; Fri, 16 Aug 2013 12:31:22 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 16 Aug 2013 12:31:20 -0400
Subject: RE: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Topic: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6ZJNjZjowH+sHwRJSBvO6n+kH4QABddLkA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489279@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslr4dwcbmh.fsf@mit.edu>
In-Reply-To: <tslr4dwcbmh.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "Black, David" <david.black@emc.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:50:04 -0000

Sam,

Thanks for taking another look at this.  I think we're in good shape on
the IPsec relationship concern, but I think key selection responsibility
could use some more attention.

[A] The new text on the IPsec relationship looks good - I'd suggest also
adding a sentence to state that keys for IPsec pre-shared-key authenticatio=
n
are not appropriate for this key database.

[C] The key selection responsibility was not clear to me from the draft -
the intent/design stated in your message is fine (and having one key
be returned is simpler, and probably more robust than handing
multiple keys to different protocol implementations and hoping
that they do something consistent):

> I think we've discussed key selection in the WG and come to a different
> conclusion.  The key table selects the key.  We expect peer, key ID,
> protocol and interface to identify a unique key for an inbound packet.

My confusion stems from section 3 starting out by stating that the
key database is consulted "to find the key to use on an outgoing message"
followed by several sentences that indicate that the consultation may
result in multiple keys.  That leads to a suggestion and a question.

Suggestion:=20

Add a new paragraph at the start of Section 3 to make the functional
responsibility clear:

  Key selection is the responsibility of the key database functionality;
  in all cases, the protocol requests a key, and the database returns one
  key or an indication that there is no matching key.  When multiple keys
  match a protocol's request, the key database selects one as described
  further in this section.

Question:

What happens, when despite all the measures described in Section 3,
multiple keys match a protocol's request?  How does one ensure that the
key databases at both ends of the security association return the same
key?

Thanks,
--David

> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Wednesday, August 14, 2013 3:32 PM
> To: Black, David
> Cc: housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
> (zhangdacheng@huawei.com); General Area Review Team (gen-art@ietf.org);
> karp@ietf.org; ietf@ietf.org
> Subject: Re: [karp] Gen-ART review of draft-ietf-karp-crypto-key-table-08
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>=20
>     Black,> [A] Overall - I would like to see a paragraph added on how
>     Black,> this database conceptually relates to the IPsec Peer
>     Black,> Authorization Database (PAD) - see RFC 4301, section 4.4.3.
>=20
> It doesn't.
> not even a little bit.
> It's not IPsec; it's not about what key management peers to interact
> with.
>=20
> It's conceptually similar to the Security Association Database (SAD).
> In a discussion with Jari I agreed to propose text for a paragraph
> describing how this interacts with IPsec.
>=20
> If this conceptual database is used to manage to keys for a security
>     protocol that uses IPsec [RFC4301] security services, then  the
>     interactions between this conceptual database and the IPsec
>     databases needs to be described by the protocol specification.
>     Typically such a protocol would insert entries into the Security
>     Association Database (SAD) when rows are inserted into the key table
>     and remove SAD entries when key table rows are removed.  The
>     protocol specification needs to describe how the SAD entries are
>     constructed along with any other IPsec database entries that are
>     needed, including a description of how these entries are ordered
>     along with other IPsec database entries.  The question of whether it
>     is desirable to use this conceptual database to manage protocols
>     that use IPsec security services is open and has not been evaluated.
>=20
>     Black,> [C] (Section 3) Where does key selection occur?  I would
>     Black,> suggest that the database return all possible keys and let
>     Black,> the protocol figure out what to use.  This is particularly
>     Black,> important for inbound traffic for obvious reasons.
>=20
> I think we've discussed key selection in the WG and come to a different
> conclusion.  The key table selects the key.  We expect peer, key ID,
> protocol and interface to identify a unique key for an inbound packet.
>=20
> So, I think the concern you raise is not a problem.
> While there was not a specific thread discussing key selection or this
> issue, there were multiple reviewers who provided comments on key
> selection over the development of the document, and making a major
> change at this point without a technical problem seems undesirable.
> If I'm missing something and the inbound packet issue is a problem then
> we need to discuss it.


From jgunn6@csc.com  Fri Aug 16 10:51:35 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D150021F9B8F; Fri, 16 Aug 2013 10:51: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=[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 61T-KCRb6IcF; Fri, 16 Aug 2013 10:51:29 -0700 (PDT)
Received: from mail210.messagelabs.com (mail210.messagelabs.com [216.82.250.179]) by ietfa.amsl.com (Postfix) with ESMTP id CFC2E11E81D0; Fri, 16 Aug 2013 10:51:27 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-7.tower-210.messagelabs.com!1376675483!13548860!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11179 invoked from network); 16 Aug 2013 17:51:25 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-7.tower-210.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Aug 2013 17:51:25 -0000
Received: from amer-gw09.amer.csc.com (cscmail.csc.com [20.6.39.245]) by amer-mta102.csc.com (8.13.8/8.13.8) with ESMTP id r7GHlpGU012593; Fri, 16 Aug 2013 13:47:51 -0400
In-Reply-To: <520E3D9B.5020901@network-heretics.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>	<OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
MIME-Version: 1.0
Subject: Re: Charging remote participants
X-KeepSent: 3EF86F57:6F72305E-85257BC9:0061EDD1; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF3EF86F57.6F72305E-ON85257BC9.0061EDD1-85257BC9.006216D0@csc.com>
Date: Fri, 16 Aug 2013 13:51:21 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/16/2013 01:44:42 PM, Serialize complete at 08/16/2013 01:44:42 PM
Content-Type: multipart/alternative; boundary="=_alternative 0062167985257BC9_="
Cc: ietf-bounces@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:51:36 -0000

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

I expect _I_ would pay $100 out of my own pocket, if it came to that.

But not all remote participants would be able to.

Janet

ietf-bounces@ietf.org wrote on 08/16/2013 10:56:27 AM:

> From: Keith Moore <moore@network-heretics.com>
>
> 
> On 08/16/2013 09:38 AM, Janet P Gunn wrote:
> > 
> ...I want it from 
> > people who can't get approval for even a $100 expense, from people 
> > who are between jobs, people from academia, and even from just plain
> > ordinary users rather than just vendors or big corps. 
> 
> I agree. 
> 
> The realities of internal politics/funding being what they are, it 
> is sometimes  going to be just as hard to get $100 "remote" fee 
> approved as it as to  get the whole f2f trip approved. 
> As someone who just spent $3.5K out of pocket to show up in Berlin, 
> I have a hard time being sympathetic to someone who won't 
> participate because he has to spend $100 out of pocket.
> 
> Keith

--=_alternative 0062167985257BC9_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
I expect _I_ would pay $100 out of my own pocket, if it came to that.</font>
<br>
<br><font size=2 face="sans-serif">But not all remote participants would
be able to.<br>
</font>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 08/16/2013 10:56:27
AM:<br>
<br>
&gt; From: Keith Moore &lt;moore@network-heretics.com&gt;</font></tt>
<br><tt><font size=2>&gt;</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; On 08/16/2013 09:38 AM, Janet P Gunn wrote:</font></tt>
<br><tt><font size=2>&gt; &gt; <br>
&gt; ...I want it from <br>
&gt; &gt; people who can't get approval for even a $100 expense, from people
<br>
&gt; &gt; who are between jobs, people from academia, and even from just
plain<br>
&gt; &gt; ordinary users rather than just vendors or big corps. <br>
&gt; <br>
&gt; I agree. <br>
&gt; <br>
&gt; The realities of internal politics/funding being what they are, it
<br>
&gt; is sometimes &nbsp;going to be just as hard to get $100 &quot;remote&quot;
fee <br>
&gt; approved as it as to &nbsp;get the whole f2f trip approved. </font></tt>
<br><tt><font size=2>&gt; As someone who just spent $3.5K out of pocket
to show up in Berlin, <br>
&gt; I have a hard time being sympathetic to someone who won't <br>
&gt; participate because he has to spend $100 out of pocket.<br>
&gt; <br>
&gt; Keith<br>
</font></tt>
--=_alternative 0062167985257BC9_=--

From touch@isi.edu  Fri Aug 16 10:53:56 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747EF11E817B for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KOK1Q5thtCau for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:53:47 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7B68211E8163 for <ietf@ietf.org>; Fri, 16 Aug 2013 10:53:45 -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 r7GHqbCN005879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Aug 2013 10:52:37 -0700 (PDT)
Message-ID: <520E66E4.1040500@isi.edu>
Date: Fri, 16 Aug 2013 10:52:36 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520DB675.2040206@250bpm.com>
In-Reply-To: <520DB675.2040206@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:53:56 -0000

On 8/15/2013 10:19 PM, Martin Sustrik wrote:
> On 15/08/13 22:18, Joe Touch wrote:
>
>>>> Does anyone have any idea how widely is TCPMUX (RFC 1078) protocol
>>>> used?
>>>> Is it the case that there are inetd daemons in TCPMUX mode running
>>>> everywhere, or can it be rather considered a dead protocol?
>>>>
>>>> Specifically, if I implement a new TCPMUX daemon how likely I am to
>>>> clash with an existing TCPMUX daemon listening on port 1?
>>>>
>>>
>>>
>>> It's in the FreeBSD inetd, among others, but to to my
>>> knowledge, nobody actually turns it on. There are
>>> probably security issues.
>>
>> There are semantics issues to; see draft-touch-tcp-portnames-00 for
>> information (this is being revised for resubmission shortly, FWIW).
>
> Nice, however, it requires changes to TCP stack, so even if it succeeds
> it won't be a practical option for at least few years to come.

There have been other stack changes that have been deployed fairly quickly.

However, that's not relevant to the reason I cited the doc; the doc has 
a discussion of TCPMUX and its problems.

Joe

From john-ietf@jck.com  Fri Aug 16 10:54:03 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F39811E81DE for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1PdRLZZbogK for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:53:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 11B9211E8163 for <ietf@ietf.org>; Fri, 16 Aug 2013 10:53:57 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VAODj-0008lk-PP; Fri, 16 Aug 2013 13:53:55 -0400
X-Vipre-Scanned: 00AE4B43002C3100AE4C90-TDI
Date: Fri, 16 Aug 2013 13:53:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: carlos@lacnic.net
Subject: Re: Charging remote participants
Message-ID: <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]>
In-Reply-To: <520E4E2E.2090708@gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:54:03 -0000

--On Friday, August 16, 2013 13:07 -0300 "Carlos M. Martinez"
<carlosm3011@gmail.com> wrote:

>...
> And, before the IETF would commit to take steps in that
> direction, it would be interesting to see some numbers about
> how much money needs to be invested in deploying and operating
> remote participation tools that would actually make people
> feel they are getting value back for a $100 remote attendance
> fee.

Please Dave Crocker's note before my comment below -- I agree
with mose of it don't want to repeat what he has already said
well.

As someone who favors charging remote participants, who has paid
most or all of the travel and associated costs for every meeting
I've attended in the last ten plus years, and who doesn't share
in a view of "if I can, everyone can", let me make a few
observations.

(1) As Dave points out, this activity has never been free.  The
question is only about "who pays".  If any participants have to
pay 
(or convince their companies to pay) and others, as a matter of
categories, do not, that ultimately weakens the process even if,
most of the time, those who pay don't expect or get favored
treatment.  Having some participants get a "free ride" that
really comes at the expense of other participants (and
potentially competing organizations) is just not a healthy idea.

(2) Trying to figure out exactly what remote participation
(equipment, staffing, etc.) will cost the IETF and then trying
to assess those costs to the remote participants would be
madness for multiple reasons.  Not least of those is the fact
that, if new equipment or procedures are needed, there will be
significant startup costs with the base of remote participants
arriving only later.  One could try to offset that effect with
some accounting assumptions that would be either rather complex,
rather naive, or both, but, as a community, we aren't good at
those sorts of calculations nor at accepting them when the IAOC
does them in a way that doesn't feel transparent.

(3) Trying to establish a more or less elaborate system of
categories of participants with category-specific fees or to
scale the current system of subsidies and waivers to accommodate
the full range of potential in-person and remote participants is
almost equally insane.  While we might make such arrangements
work and keeping categories and status off badges helps, it gets
us entangled with requiring that the Secretariat and/or IAD
and/or some IAOC or other "leadership" members be privy to
information that is at least private and that might be formally
confidential.  We don't want to go there if we can help it.

(4) The current "registration fee" covers both some proportion
of meeting-specific expenses and some proportion of overhead
expenses that are not specific to the meetings or to meeting
attendance.  Breaking those proportions down specifically also
would require some accounting magic, especially given the
differences between meetings with greater or lesser degrees of
sponsorship.   But I believe that, if we can trust the IAOC to
set meeting registration fees for in-person attendees, we can
trust them to set target (see below) meeting registration fees
for remote participants.  Note that such a fee involves some
reasonable contribution to overhead expenses (including remote
participation costs, secretariat site visits, and the like) just
as the fee for in-person participants does -- it is not based on
the costs of facilities for remote participation.

So, to suggest this again in a different context:

Remote participants then pay between 0 and 100% of that target
fee, based on their consciences, resources, and whatever other
considerations apply.  No one asks how given remote participants
or their organizations arrive at the numbers they pick.  No one
is asked to put themselves into a category or explain their
personal finances.  The IETF does not need to offer promises
about the confidentiality of information that it doesn't
collect.  Any Euro we collect is one Euro more than we are
collecting now and, if a Euro or two is what a participant from
a developing area feels is equitable for him or her to pay, then
that is fine.

That "voluntary fee" model would be a terrible one except that I
think we can actually trust the vast majority of the community
to be reasonable.  Certainly some people will not be, but they
would probably figure out how to game a category system or any
more complex system we came up with.  Just as the price of
running a truly open standards process including tolerating a
certain number of non-constructive participants (and other
subspecies of trolls), it may require tolerating a certain
number of people who won't want to pay their fair share (or
whose judgments of "fair" might be at variance with what other
people with the same information would conclude).  Absent clear
indications that more complex process, or one that relied more
on leadership judgments about individual requests, would produce
more than enough additional revenue to compensate for the damage
and risks those approaches would cause, I think it strikes a
reasonable balance. It also addresses all of the issues about
the problems with charging remote participants that have been
raised in this thread except those based on the dubious
principle that anyone who doesn't attend an in-person meeting is
thereby entitled to be subsidized by the rest of the community.

best,
   john


    





From housley@vigilsec.com  Fri Aug 16 10:56:14 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7EB411E81DB for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:56:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xXYLOrzmCo4h for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 10:56:08 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id D819C21F9EE1 for <ietf@ietf.org>; Fri, 16 Aug 2013 10:55:43 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 6B637F24087; Fri, 16 Aug 2013 13:56:24 -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 B2--QQEJP7Ya; Fri, 16 Aug 2013 13:55:38 -0400 (EDT)
Received: from [192.168.0.8] (75-139-113-21.dhcp.mant.nc.charter.com [75.139.113.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 94C65F24032; Fri, 16 Aug 2013 13:56:21 -0400 (EDT)
Subject: Re: [IAB] Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
Date: Fri, 16 Aug 2013 13:55:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDF752FA-73CF-4944-B135-BF70B526ABAE@vigilsec.com>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>, Sandy Ginoza <sginoza@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: Fri, 16 Aug 2013 17:56:14 -0000

SM:

> This is a call for review of "List of Internet Official Protocol =
Standards: Replaced by an Online Database" prior to potential approval =
as an IAB stream RFC.
>=20
> The document is available for inspection here: =
https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/
>=20
> =46rom Section 2.1 of RFC 2026:
>=20
>  'The status of Internet protocol and service specifications is
>   summarized periodically in an RFC entitled "Internet Official
>   Protocol Standards".'
>=20
> My guess is that draft-rfced-rfcxx00-retired cannot update RFC 2026.  =
Does the IAB have any objection if I do something about that?

This seems to require coordination with the General Area Director.  I =
suggest that you ask Jari.

> =46rom Section 3:
>=20
>  "This document formally retires STD 1.  Identifier STD 1 will not be
>   re-used unless there is a future need to publish periodic snapshots
>   of the Standards Track documents (i.e., unless the documentation is
>   resumed)."
>=20
> The document argues that STD 1 is historic as there is an online list =
now.  The above reserves an option to restart periodic snapshots if =
there is a future need.  I suggest removing that option as I presume =
that the IAB has thought carefully about the long term evolution of the =
Series before taking the decision to retire STD 1.

I tend to agree.  I think the point is that STD 1 will not take on =
another meaning.

Russ=

From hartmans@mit.edu  Fri Aug 16 11:01:00 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36FA021F8C65; Fri, 16 Aug 2013 11:01:00 -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 Kpb-CSxpnfLn; Fri, 16 Aug 2013 11:00:54 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3955511E817A; Fri, 16 Aug 2013 11:00:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id E7FA72029E; Fri, 16 Aug 2013 13:59:33 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JS0HoaQLAGBV; Fri, 16 Aug 2013 13:59:32 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 16 Aug 2013 13:59:32 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3890B8052F; Fri, 16 Aug 2013 14:00:47 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
Subject: Re: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com>
Date: Fri, 16 Aug 2013 14:00:47 -0400
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> (David Black's message of "Fri, 16 Aug 2013 13:02:35 -0400")
Message-ID: <tslpptd348g.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, Sam Hartman <hartmans-ietfc@mit.edu>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:01:00 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> done.  IMHO, we really should be setting a bar that says
    Black,> that this sort of IETF imprimatur of approval of a crypto
    Black,> algorithm actually means something.



Something got manged there.
I agree that publishing a standards-track document  should endorce the
algorithm in question.

I'm somewhat uncomfortable with that sort of bar for IANA registries in
general, although I have supported it from time to time.  (My discomfort
with this has grown significantly since my time as an AD).  I do not
support that sort of bar for this registry.

I think we understand each other, but disagree.

The question now is whether you can gain sufficient support to show
rough consensus for a change in the document or to show that while there
was rough consensus behind the document in the KARP WG, there's a lack
of consensus on handling this issue between KARP and some other
significant segment of the IETF like the security area.

From hartmans@mit.edu  Fri Aug 16 11:02:35 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD5011E81FF; Fri, 16 Aug 2013 11:02:35 -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 2g8uESl0QDlu; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 13E4011E8165; Fri, 16 Aug 2013 11:02:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 5E8AA202AC; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQ7nmKCcgc0z; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 16 Aug 2013 14:01:19 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C99958052F; Fri, 16 Aug 2013 14:02:33 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: "Black\, David" <david.black@emc.com>
Subject: Re: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> (David Black's message of "Fri, 16 Aug 2013 13:02:35 -0400")
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Date: Fri, 16 Aug 2013 14:02:33 -0400
Message-ID: <tslob8x345i.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, Sam Hartman <hartmans-ietf@mit.edu>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:02:35 -0000

>>>>> "Black," == Black, David <david.black@emc.com> writes:

    Black,> done.  IMHO, we really should be setting a bar that says
    Black,> that this sort of IETF imprimatur of approval of a crypto
    Black,> algorithm actually means something.



Something got manged there.
I agree that publishing a standards-track document  should endorce the
algorithm in question.

I'm somewhat uncomfortable with that sort of bar for IANA registries in
general, although I have supported it from time to time.  (My discomfort
with this has grown significantly since my time as an AD).  I do not
support that sort of bar for this registry.

I think we understand each other, but disagree.

The question now is whether you can gain sufficient support to show
rough consensus for a change in the document or to show that while there
was rough consensus behind the document in the KARP WG, there's a lack
of consensus on handling this issue between KARP and some other
significant segment of the IETF like the security area.

From touch@isi.edu  Fri Aug 16 11:08:07 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D0011E8186 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 11:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJHyAxZSwZn4 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 11:08:01 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 14ACB11E81E3 for <ietf@ietf.org>; Fri, 16 Aug 2013 11:08:01 -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 r7GI7INO009052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Aug 2013 11:07:18 -0700 (PDT)
Message-ID: <520E6A55.6010802@isi.edu>
Date: Fri, 16 Aug 2013 11:07:17 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com>
In-Reply-To: <520DBABA.2000506@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:08:07 -0000

On 8/15/2013 10:38 PM, Martin Sustrik wrote:
> On 16/08/13 03:23, Wesley Eddy wrote:
>
>>> There are semantics issues to; see draft-touch-tcp-portnames-00 for
>>> information (this is being revised for resubmission shortly, FWIW).
>>>
>> I totally agree.  In fact, in the update to the TCP roadmap [1], we
>> added TCPMUX to the section on "Historic and Undeployed Extensions",
>> though it definitely bears further discussion than is currently in
>> the roadmap.  I think we should add a reference to your portnames doc
>> to explain why this should be Historic plus check a bit more to see if
>> the code that's out there is really being used or whether it's just
>> hanging out like a vestigal limb in the various inetd packages.
>>
>> If it's fair to ask Martin ... I'm kind of curious why you might want
>> to be using it or think it sounds useful?  I think a lot of admins
>> would be concerned that it could be used to get around port-based
>> firewall rules, etc.
>
> Ok, let me explain.
>
> I am coming from enterprise messaging world (think of IBM MQ series,
> JMS, ActiveMQ, RabbitMQ et c.)
>
> Once I was participating on AMQP protocol development (now at OASIS).
> So, what AMQP and other enterprise messaging products do is exposing a
> "message broker" on a single TCP port, which then forwards messages to
> any connected services. As can be seen, single open firewall port can be
> used to access any internal service.

I don't understand that statement.

Services are currently indicated by the destination port. If there is 
only one destination port available, there is only one service provided 
- because very few services can be identified solely by in-band information.

> That being obviously the *wrong* way to do things, I've written ZeroMQ
> later which takes the strict approach: If you want to expose a new
> service, you have to use a separate TCP port number.
>
> Since then it turned out that this as a limitation that people are most
> complaining about.

It would be useful if you could be more specific about the problem you 
are trying to solve.

So far I hear "people want one port that serves multiple services". I'd 
like a pony ;-) I.e., just because they want it, doesn't mean it either 
makes sense or should get it.

> Now, the reason seems to be that ZeroMQ requires you to use different
> TCP connections for doing different kinds of stuff to avoid head-of-line
> blocking et c. (think of SCTP channels simulated via TCP)

Different connections don't have anything to do with the use of a single 
port. A single port can serve multiple connections, and yes - that's a 
useful way to avoid HOL blocking.

> What that means is that you have a lot of fine-grained services and as
> the development of your application proceeds you add more of them,
> remove them and so on.
>
> That in turn requires admins (and the corporate approval process!) to
> get into the deployment cycle and open the TCP ports as appropriate. The
> result is that the development basically grinds to halt.

That sounds a lot like the desires of admins is in conflict with the 
desires of your users. I.e., an admin that wants to block anything they 
don't explicitly allow WANTS to block this sort of mechanism too.

> The solution IMO is to preserve the port-based services functionality
> for those that truly care about security and -- optionally -- support
> some kind of multiplexer such as TCPMUX for those that care more about
> short deployment cycle.

TCPMUX won't do what you're asking - if you're asking to block based on 
the service type. If it did, then the sysadmin would just block TCPMUX 
connections to services they didn't know, and you'd be right back where 
you are now (i.e., without TCPMUX).

Again, what is the goal?

(note: the goal of the portnames approach is NOT to provide a single 
multiplexing port; it's to decouple the dest port's two uses - demux 
info and service identifier. the primary reason for portnames is to 
allow more than 65K concurrent/timewait connections to a single service; 
FWIW, I cited it because of its description of the limitations of 
TCPMUX, not because the approach there was relevant here).

> That being said, IIRC, there's such functionality in WebSockets as well.
> Open a connection to fixed pot (80) and particular URL (string), then
> after the initial negotiation, switch to raw TCP mode and hand the
> connection to whatever application is suppose to handle it. The reason I
> don't like that solution is that you have to have web server installed
> to work as a multiplexer, which is kind of strange.

If you want a multiplexer to serve different connections from a single 
service port, you need a multiplexer server (tcpmux daemon, websockets, 
whatever you want to call it).

Joe

From hadriel.kaplan@oracle.com  Fri Aug 16 11:32:55 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B86811E817B for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 11:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvUN6DYJ6XYu for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 11:32:48 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id A7FCB11E811F for <ietf@ietf.org>; Fri, 16 Aug 2013 11:32:48 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GIWeh6017646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Aug 2013 18:32:41 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GIWaYW016343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 18:32:37 GMT
Received: from abhmt114.oracle.com (abhmt114.oracle.com [141.146.116.66]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GIWaWR029043; Fri, 16 Aug 2013 18:32:36 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 11:32:36 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <520E4B79.6040208@dcrocker.net>
Date: Fri, 16 Aug 2013 14:32:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <817AC110-D2A9-411B-814E-B27A2C1B1282@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <520E4B79.6040208@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
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, 16 Aug 2013 18:32:55 -0000

On Aug 16, 2013, at 11:55 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/16/2013 6:10 AM, Hadriel Kaplan wrote:
>> Since the topic keeps getting raised... I think that charging remote
>> participants any fee is a really terrible idea.  One of the really
>> great things about the IETF is its open and free (as in beer)
>> participation policy.  The real work is supposed to be done on
>> mailing lists, and there's no charge or restriction on who can send
>> emails.  That policy is actually quite rare for standards bodies, and
>> makes our output better not worse.
>=20
> The IETF has never been free.  Actually, it's quite expensive.
>=20
> We've maintained the myth that it's free because we've had long-term =
funding support from the outside, originally dubbed "daddy pays".  First =
it was ARPA, then CNRI and now ISOC (and wealthy corporations).

I didn't say it didn't cost someone money to run it - I said it's free =
to participate, and I like that policy and think we're better for it.  =
*Of course* someone has to pay something, and we could have a long =
debate about a better funding model for the IETF in general.  But that's =
not a problem I'm trying to fix.

Some people on the list have expressed a desire to have better remote =
participation.  I don't know if that's necessary or not, but I suggested =
a possible solution for that (i.e., audio input).  The solution will =
cost some money.  Not a lot, hopefully, but more than currently being =
spent.  The people who run the meetings will have to tell us how much =
more, per meeting.

Assuming it costs more than some trivial amount, we have to figure out a =
source of revenue for that.  We don't have to re-do the whole IETF =
funding model - just figure out where to get the money for this new =
thing.

So if that costs real money, I propose that instead of charging remote =
participants the cost, we charge f2f participants by burying it in the =
reg-fee, but discounting the reg-fee for those who can't expense the =
reg-fee.   That sounds whacky, I know.  It sounds radical too.  It's not =
a new idea though, and some other places do the same but using different =
words (like "Corporate Attendee" vs. "Individual Attendee", but those =
don't make sense here).

The good thing is it's something we can test and measure, without =
impacting attendee rates.  We can't measure how impactful a fee to =
remote participants is - the number who join rises and falls due to =
various reasons; and even if they don't join due to the fee we won't =
know it - they won't say so, and won't join remotely, and we won't know =
it.  Thus it's self-limiting and self-fulfilling.  We can't measure how =
impactful a mandatory increase across-the-board for f2f meeting reg-fee =
is either - the number of f2f attendees rises/falls based on too many =
factors, and again it's self-limiting and self-fulfilling.  With a =
selectable registration form check-box, and no laying of guilt or stigma =
on those who do/don't choose 'Self-Paying Rate' vs. 'Full Rate' and no =
external indicator of it, we can figure out if we get more money and how =
much, without directly impacting our f2f attendance rate.

We can even do it *before* we go and pay for anything.  We could, for =
example, have the check-box for the Vancouver IETF meeting form, with =
textual explanation of why to check it.  We could do the same for remote =
participants too, just to see how much we'd get that way instead.


> As remote participation tools get better, it is likely that we will =
have more remote attendees and fewer face-to-face ones.  This likely =
means significant reduction in attendee fees but also could challenge =
sponsor fees, since the marketing benefit of sponsorship for the f2f =
will likely go down.

I have a hard time believing that.  If anyone thinks they get as much =
out of remote participation as they do with f2f, then I think they're =
crazy... but you're right they shouldn't come.  If it turns out a lot of =
people stop coming, then maybe we really don't need f2f meetings or as =
many of them.  Or maybe it means we need to make cost the highest =
priority factor in meeting locations, instead of one among many =
must-have requirements.  Or maybe it means we need to restructure how we =
spend and get funding. =20

Regardless, the goal of the IETF isn't to have f2f meetings - it's a =
means to an end, not an end in itself.  I think it's super-valuable, for =
both physical attendees and the output the IETF produces; and I think =
it's worth having it 3 times year.  I *want* people to go physically.  =
But if it's not valuable to many people, don't have them; or not as =
frequently.

-hadriel


From john-ietf@jck.com  Fri Aug 16 11:44:43 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F9011E8186; Fri, 16 Aug 2013 11:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVENaWsUKVt5; Fri, 16 Aug 2013 11:44:38 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 380B011E820A; Fri, 16 Aug 2013 11:44:38 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VAP0m-0008rM-Ta; Fri, 16 Aug 2013 14:44:36 -0400
X-Vipre-Scanned: 00DCB2B7002C3100DCB404-TDI
Date: Fri, 16 Aug 2013 14:44:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>, iab@iab.org
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of	Internet Official Protocol Standards: Replaced by an Online Database"
Message-ID: <6E29F0AB625F4250CB35B273@[192.168.1.128]>
In-Reply-To: <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:44:43 -0000

--On Thursday, August 15, 2013 12:06 -0700 SM <sm@resistor.net>
wrote:

> At 11:48 14-08-2013, IAB Chair wrote:
> This is a call for review of "List of Internet Official
> Protocol Standards: Replaced by an Online Database" prior to
> potential approval as an IAB stream RFC.
> 
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/
> 
>  From Section 2.1 of RFC 2026:
> 
>    'The status of Internet protocol and service specifications
> is
>     summarized periodically in an RFC entitled "Internet
> Official
>     Protocol Standards".'
> 
> My guess is that draft-rfced-rfcxx00-retired cannot update RFC
> 2026.  Does the IAB have any objection if I do something about
> that?

SM, 

You have just identified another aspect of why I find this
document troubling.  I note that requirement of RFC 2026 has not
been satisfied for years unless one interprets "periodically" as
consistent with "whenever we get around to it, which, in today's
age, is likely to be never".  I note that the last version of
STD 1 was RFC 5000, published in May 2008 and that its
predecessor was RFC 3700 in July 2004, i.e., there was a four
year interval followed by at least a seven year one.  That is
well outside most normal interpretations of "periodic".  

I don't personally think it is worth it (or, more specifically,
think the resources could be better spent in other ways) but, if
one believed the "keep anything that might turn out to be
historically important" theme of the IETF 86 History BOF, then
there is value in maintaining the sort of comprehensive status
snapshot that STD 1 was supposed to provide (once its [other]
original purpose of being part of a report to the sponsor became
irrelevant) even if that snapshot is taken only once every few
years.  

That aside, I think this document is almost completely
unnecessary.  RFC 5000 already points to the HTML version of the
RFC index as the authority for contemporary information.  There
has, as far as I know, never been a requirement that STD 1 be
issued as RFCs numbered NN00,  nor that all such numbers be
reserved for that purpose, outside the internal conventions of
the RFC Editor function.  

At the same time, if the IAB and RSE believe that assembling and
publishing this statement formally and in the RFC Series is a
good use of their time and that of the community, I think it is
basically harmless, _unless_ it becomes an opportunity to
nit-pick such questions as its relationship to requirements or
statements in 2026 or elsewhere.


>  From Section 3:
> 
>    "This document formally retires STD 1.  Identifier STD 1
> will not be
>     re-used unless there is a future need to publish periodic
> snapshots
>     of the Standards Track documents (i.e., unless the
> documentation is
>     resumed)."
> 
> The document argues that STD 1 is historic as there is an
> online list now.  The above reserves an option to restart
> periodic snapshots if there is a future need.  I suggest
> removing that option as I presume that the IAB has thought
> carefully about the long term evolution of the Series before
> taking the decision to retire STD 1.

This is another form of the nit-picking (if there were protocols
involved, the historical term would involve the phrase "protocol
lawyer") that concerns me.  I don't remember where it is written
down (if at all), but the RFC Editor has had a firm rule ever
since I can remember that STD numbers are never reused for a
different topic.  Violating that prohibition against reuse would
be a really stupid move on the part of the RFC Editor and/or the
IAB.  If they were to be that stupid, we have much more serious
other problems.  If they are going to continue to avoid that
sort of stupidity, then that part of the statement above is
completely unnecessary - but still harmless.  

As far as removing the option is concerned, I think doing so
would be pointless if the rest of the statement remains.  For
better or worse, anything that is written into one RFC by the
IAB (or, under different circumstances, the IETF) can be amended
out of it by another RFC.  While I think it unlikely, I can
imagine at least one scenario, tied to the historical concern
above, under which we would resume publishing a snapshot.
Whether the IAB has considered it or not and whatever promises
this document does or does not make are irrelevant to whether or
not that would happen.

Summary: I think the RFC Series Editor should just make whatever
announcement she feels it is appropriate to make, recognizing
that we stopped regularly updating STD 1 long ago and have no
present intention of restarting.  I think this document and the
process and associated work it imposes on the IAB and the
community are a waste of time that could be better used in other
ways.    However, if they feel some desire to publish it in some
form, let's encourage them to just get it done and move on
rather than consuming even more time on issues that will make no
difference in the long term.

best,
    john




From rpelletier@isoc.org  Fri Aug 16 11:47:50 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 423B611E8217; Fri, 16 Aug 2013 11:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.435
X-Spam-Level: 
X-Spam-Status: No, score=-102.435 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 bhmAcQ0i0GTM; Fri, 16 Aug 2013 11:47:46 -0700 (PDT)
Received: from smtp102.ord1c.emailsrvr.com (smtp102.ord1c.emailsrvr.com [108.166.43.102]) by ietfa.amsl.com (Postfix) with ESMTP id 845AB11E8186; Fri, 16 Aug 2013 11:47:43 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id D2B121B0081; Fri, 16 Aug 2013 14:47:41 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 78CC91B0187;  Fri, 16 Aug 2013 14:47:41 -0400 (EDT)
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
Date: Fri, 16 Aug 2013 14:47:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.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: Fri, 16 Aug 2013 18:47:50 -0000

All;

Are there any more comments on the SOWs?

This item will be on the IAOC agenda for its call on 22 August.

Ray

On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:

> The RFC Series Editor (RSE) is proposing changes to the Statements of =
Work (SOW) for the RFC=20
> Production Center (RPC) and the RFC Publisher.  The IAOC wants to =
receive community input prior to=20
> negotiating the proposed changes with the contractor.  Community input =
will be discussed with the RSE=20
> prior to negotiations and reviewed by the IAOC.
>=20
> In forwarding the proposed Statements of Work the RSE said:  "The =
changes seek to make the SoWs=20
> more current [implementing RFC 6635] and specific, correcting the =
issues of "multiple masters"=20
> directing the RPC and Publisher, as well as preparing the way for a =
more significant revision to the SoWs
> when the RFC Format changes are operationalized.  The SoWs have also =
been reviewed and supported=20
> by the RSOC [RFC Series Oversight Committee].  We consider the changes =
within the SoWs critical to the=20
> clear function of the RPC and Publisher, but suggest that the changes =
do not imply a significant change=20
> in responsibility for the RPC or Publisher."
>=20
> The proposed SOWs, the current SOWs and a diff file for each can be =
found here under Community=20
> Review: <http://iaoc.ietf.org/rfps.html>
>=20
> We appreciate the community's input and look forward to hearing from =
you. =20
>=20
> Thanks
>=20
> Ray Pelletier
> IAD


From melinda.shore@gmail.com  Fri Aug 16 11:58:51 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3FB011E8200 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 11:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JiCPC59893MI for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 11:58:51 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4988E11E8184 for <ietf@ietf.org>; Fri, 16 Aug 2013 11:58:51 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id bg4so2203639pad.32 for <ietf@ietf.org>; Fri, 16 Aug 2013 11:58:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=8wrJlhGxndfThYCyxFgUh4nC1FksBk5OYfjJ6VWVlyw=; b=sm2AUOYJgmkeWYgp6l1QGrLthFsO4REmehOctrI21xZVm8oEQE8Us/CH0uQTzXBPtk GQbqeoR0QQyRjpgq4M0QpRp5Xauv5kAyheZt4PR4/cRjPdmn5uxsraUIE72S8MuDcn+3 rWg7OqkLRNsbLNYGeCAWZGaIN56DavMP1Pf6JSuHH3MW6GgrqmaZfInqmsvNk8lmyxBs jg1GDtN1unFR/i42uFGVFaroFTZbYUW3d8Lsk/p6gFTlAomijJM9dM5d53u0q/g3wcbr hq74wDLrJ7xvP0VcS3Q2x3LhWxmWREoobR8Rl7qcvp/Gqxm3+infbvTL9xbxJLQgskAF rKCg==
X-Received: by 10.68.240.72 with SMTP id vy8mr3020661pbc.161.1376679531053; Fri, 16 Aug 2013 11:58:51 -0700 (PDT)
Received: from spandex.local (66-230-112-160-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.112.160]) by mx.google.com with ESMTPSA id kd1sm4887331pab.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 Aug 2013 11:58:49 -0700 (PDT)
Message-ID: <520E7667.3040701@gmail.com>
Date: Fri, 16 Aug 2013 10:58:47 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]>
In-Reply-To: <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 18:58:51 -0000

On 8/16/13 9:53 AM, John C Klensin wrote:
> As someone who favors charging remote participants, who has paid
> most or all of the travel and associated costs for every meeting
> I've attended in the last ten plus years, and who doesn't share
> in a view of "if I can, everyone can", let me make a few
> observations.

I think these are good points, and I'd like to add: the extent to
which there's now an expectation that someone must participate in
a meeting in order to contribute to work is the extent to which
there's been a gradual shift in working methods in the organization,
and effectively reflect a loss (to whatever extent) of openness.

We can stay free and open if mailing lists remain the locus of
the IETF's work.  The costs associated with remote participation
have to be borne by someone; the marginal cost of someone joining
an existing mailing list is effectively zero.

Melinda


From moore@network-heretics.com  Fri Aug 16 12:11:11 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E39211E8179 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:11: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=[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 G385u0E3VB2Z for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:11:05 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 0C10811E810B for <ietf@ietf.org>; Fri, 16 Aug 2013 12:11:04 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 3D41821397; Fri, 16 Aug 2013 15:11:04 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 16 Aug 2013 15:11:04 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=ghkDUpsPtQ/TSp5DieGAU7 WaQlw=; b=lp6Tmc3mPcEvkTMlC1G7IfTV9ZYGkwWv/M7nfNt7uRrEgH69GiCz/L 52t3/v9gdwDbRfWbsZRvzTCPVeSMexLcCg+nxQdK7Xuqwjc6MiV6v44oMmL0ywF0 Nz7snPZCtsNYGTWUkPxYCoGREp/gOMONO2/hwc4mwjhZ3drP/FMig=
X-Sasl-enc: uF2j5LDgVzCu+02I4VdZqNzjUL/BVzDpCenfRbGSYSIQ 1376680263
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 341E9C00E8A; Fri, 16 Aug 2013 15:11:03 -0400 (EDT)
Message-ID: <520E7942.8060705@network-heretics.com>
Date: Fri, 16 Aug 2013 15:10:58 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com>
In-Reply-To: <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 19:11:11 -0000

On 08/16/2013 11:36 AM, Hadriel Kaplan wrote:
> On Aug 16, 2013, at 10:56 AM, Keith Moore <moore@network-heretics.com> wrote:
>
>> As someone who just spent $3.5K out of pocket to show up in Berlin, I have a hard time being sympathetic to someone who won't participate because he has to spend $100 out of pocket.
> This isn't about "fairness" or equal-pain-for-all.  It's about getting work done and producing good output.  Whether someone remote has to pay $0 or $1000 won't change your $3.5k out-of-pocket expense.  If you don't feel the $3.5k was worth it for you to go physically, don't go.

I'm all about having IETF get work done and produce good output. May I 
suggest that we start by trying to reduce IETF's longstanding bias in 
favor of large companies with large travel budgets that pay 
disproportionate attention to narrow and/or short-term interests, and 
against academics and others who take a wider and/or longer view?   The 
Internet has suffered tremendously due to a lack of a long-term view in 
IETF.

To that end, I'd like to see IETF do what it can to reduce meeting costs 
for those who attend face-to-face, rather than increase those costs even 
more in order to subsidize remote participation.

I have reached the difficult (i.e. expensive) conclusion that the only 
way to participate effectively in IETF (except perhaps in a narrow focus 
area) is to regularly attend face-to-face meetings. There are several 
reasons for this, just a few of which (off the top of my head) are:

(1)  It's really hard to understand where people are coming from 
unless/until you've met them in person.  I had been participating in 
IETF for about a year before I showed up at my first meeting, and I 
still remember how
(2) It's much easier to get a sense of how a group of people react to a 
proposal in person, than over email.
(3) For several reasons, people seem to react to ideas more favorably 
when discussed face-to-face.
(4) It's easier to get along well with people whom you see face-to-face 
on at least an occasional basis, so people whom you've met face-to-face 
are more likely to appreciate constructive suggestions and to interpret 
technical criticism as helpful input rather than personal attacks.
(5) Among the many things that hallway conversations are good for are 
quickly settling misunderstandings and resolving disputes.

I realize that a better remote participation experience might help with 
some or all of these, but I think we're decades away from being able to 
realize that quality of experience via remote participation, at least 
without developing new technology and spending a lot more money on 
equipment.   If someone wants to fund development of that technology and 
purchase of that equipment separately from the normal IETF revenue 
stream, more power to them.   But I do suspect that at some point it 
will cost money to maintain that technology and equipment, and again, I 
suspect it shouldn't primarily come from people who are paying to be 
there in person.

Or if we're really about trying to make IETF as open as possible, then 
we should be willing to publicly declare that people can participate in 
face-to-face meetings without paying the registration fee.  [*]  But I 
don't think that IETF's current funding model can support that.   So 
maybe IAOC should give serious thought to changing the model, but 
offhand I don't know what a better model would be.   Should IETF become 
a membership organization, and let some of the administrative costs be 
borne by membership fees, so that meeting costs can more accurately 
reflect the cost of hosting meetings?   How would the organization 
provide benefits to paying members without excluding participation from 
others?   I don't expect that there are any obviously right answers to 
questions like those - everything involves compromise - but it might be 
that there are far better answers to those questions than those that 
have been assumed for the past 20 years or so.

[*] I do realize that some people have, on occasion, shown up as 
"tourists" for the benefit of hallway and bar conversations, and avoided 
paying the meeting fee.


From brian.e.carpenter@gmail.com  Fri Aug 16 12:17:47 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C2011E820B for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BPYmT-zAQr1b for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:17:46 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3389E11E8179 for <ietf@ietf.org>; Fri, 16 Aug 2013 12:17:46 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc17so2332841pbc.4 for <ietf@ietf.org>; Fri, 16 Aug 2013 12:17: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=YAZ+obDI41hxIq4uh2mNBS1L5BVYhjnLUSlvRxqJnt0=; b=Ot9yORbnB4tCsJ1k28Ul7iR0Obl392beoZqK7z2HOZ1fIS9Oh2E2XX96cyXXXRmmCc Ktj4E13AhjeOOqIwAT/M2z2+VoE0LCKNo7UXaQBZzl/xoG8PfVZ+V6c7XInenhDC5od8 TvDarDKh7r/iGq/kk6YzNYenUb66hJ1Iq69a7/rP2iw57s2wtBeJlY3QxWahz/nKVSLw +HNt49FsCwRYkHN66vr5PYU7h2IX9jfd2MaN5i9auzet6tArTeOgWRR5OmTjwzbOr4d3 5malVnyQCcRWZ9TiB291N2HxY1CmXB7XHobFXQCD5faUCDKdFSybC/HUv6Y7Joa3f1vt o0sg==
X-Received: by 10.68.111.197 with SMTP id ik5mr3055622pbb.171.1376680665900; Fri, 16 Aug 2013 12:17:45 -0700 (PDT)
Received: from [10.1.9.168] ([203.167.141.74]) by mx.google.com with ESMTPSA id lm2sm4994983pab.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 16 Aug 2013 12:17:44 -0700 (PDT)
Message-ID: <520E7ADD.9060509@gmail.com>
Date: Sat, 17 Aug 2013 07:17:49 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org>	<6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <6E29F0AB625F4250CB35B273@[192.168.1.128]>
In-Reply-To: <6E29F0AB625F4250CB35B273@[192.168.1.128]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, 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: Fri, 16 Aug 2013 19:17:47 -0000

I think that if we worried about every minor deviation from RFC 2026,
we would be here for a long time and wasting most of it.

I have no particular objection to publishing the draft.

Regards

   Brian Carpenter

(who tried and failed - see draft-carpenter-rfc2026-critique,
draft-carpenter-rfc2026-practice, draft-carpenter-rfc2026-changes)

On 17/08/2013 06:44, John C Klensin wrote:
> 
> --On Thursday, August 15, 2013 12:06 -0700 SM <sm@resistor.net>
> wrote:
> 
>> At 11:48 14-08-2013, IAB Chair wrote:
>> This is a call for review of "List of Internet Official
>> Protocol Standards: Replaced by an Online Database" prior to
>> potential approval as an IAB stream RFC.
>>
>> The document is available for inspection here:
>> https://datatracker.ietf.org/doc/draft-rfced-rfcxx00-retired/
>>
>>  From Section 2.1 of RFC 2026:
>>
>>    'The status of Internet protocol and service specifications
>> is
>>     summarized periodically in an RFC entitled "Internet
>> Official
>>     Protocol Standards".'
>>
>> My guess is that draft-rfced-rfcxx00-retired cannot update RFC
>> 2026.  Does the IAB have any objection if I do something about
>> that?
> 
> SM, 
> 
> You have just identified another aspect of why I find this
> document troubling.  I note that requirement of RFC 2026 has not
> been satisfied for years unless one interprets "periodically" as
> consistent with "whenever we get around to it, which, in today's
> age, is likely to be never".  I note that the last version of
> STD 1 was RFC 5000, published in May 2008 and that its
> predecessor was RFC 3700 in July 2004, i.e., there was a four
> year interval followed by at least a seven year one.  That is
> well outside most normal interpretations of "periodic".  
> 
> I don't personally think it is worth it (or, more specifically,
> think the resources could be better spent in other ways) but, if
> one believed the "keep anything that might turn out to be
> historically important" theme of the IETF 86 History BOF, then
> there is value in maintaining the sort of comprehensive status
> snapshot that STD 1 was supposed to provide (once its [other]
> original purpose of being part of a report to the sponsor became
> irrelevant) even if that snapshot is taken only once every few
> years.  
> 
> That aside, I think this document is almost completely
> unnecessary.  RFC 5000 already points to the HTML version of the
> RFC index as the authority for contemporary information.  There
> has, as far as I know, never been a requirement that STD 1 be
> issued as RFCs numbered NN00,  nor that all such numbers be
> reserved for that purpose, outside the internal conventions of
> the RFC Editor function.  
> 
> At the same time, if the IAB and RSE believe that assembling and
> publishing this statement formally and in the RFC Series is a
> good use of their time and that of the community, I think it is
> basically harmless, _unless_ it becomes an opportunity to
> nit-pick such questions as its relationship to requirements or
> statements in 2026 or elsewhere.
> 
> 
>>  From Section 3:
>>
>>    "This document formally retires STD 1.  Identifier STD 1
>> will not be
>>     re-used unless there is a future need to publish periodic
>> snapshots
>>     of the Standards Track documents (i.e., unless the
>> documentation is
>>     resumed)."
>>
>> The document argues that STD 1 is historic as there is an
>> online list now.  The above reserves an option to restart
>> periodic snapshots if there is a future need.  I suggest
>> removing that option as I presume that the IAB has thought
>> carefully about the long term evolution of the Series before
>> taking the decision to retire STD 1.
> 
> This is another form of the nit-picking (if there were protocols
> involved, the historical term would involve the phrase "protocol
> lawyer") that concerns me.  I don't remember where it is written
> down (if at all), but the RFC Editor has had a firm rule ever
> since I can remember that STD numbers are never reused for a
> different topic.  Violating that prohibition against reuse would
> be a really stupid move on the part of the RFC Editor and/or the
> IAB.  If they were to be that stupid, we have much more serious
> other problems.  If they are going to continue to avoid that
> sort of stupidity, then that part of the statement above is
> completely unnecessary - but still harmless.  
> 
> As far as removing the option is concerned, I think doing so
> would be pointless if the rest of the statement remains.  For
> better or worse, anything that is written into one RFC by the
> IAB (or, under different circumstances, the IETF) can be amended
> out of it by another RFC.  While I think it unlikely, I can
> imagine at least one scenario, tied to the historical concern
> above, under which we would resume publishing a snapshot.
> Whether the IAB has considered it or not and whatever promises
> this document does or does not make are irrelevant to whether or
> not that would happen.
> 
> Summary: I think the RFC Series Editor should just make whatever
> announcement she feels it is appropriate to make, recognizing
> that we stopped regularly updating STD 1 long ago and have no
> present intention of restarting.  I think this document and the
> process and associated work it imposes on the IAB and the
> community are a waste of time that could be better used in other
> ways.    However, if they feel some desire to publish it in some
> form, let's encourage them to just get it done and move on
> rather than consuming even more time on issues that will make no
> difference in the long term.
> 
> best,
>     john
> 
> 
> 
> 

From hadriel.kaplan@oracle.com  Fri Aug 16 12:31:20 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02B721F9DB8 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.408
X-Spam-Level: 
X-Spam-Status: No, score=-6.408 tagged_above=-999 required=5 tests=[AWL=0.191,  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 XaF6KByE3dSS for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:31:14 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id F308D11E8118 for <ietf@ietf.org>; Fri, 16 Aug 2013 12:31:13 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GJV8m6011992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Aug 2013 19:31:09 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GJV5VC005647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 19:31:08 GMT
Received: from abhmt111.oracle.com (abhmt111.oracle.com [141.146.116.63]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GJV5t3000307; Fri, 16 Aug 2013 19:31:05 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 12:31:05 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <520E7942.8060705@network-heretics.com>
Date: Fri, 16 Aug 2013 15:31:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 19:31:20 -0000

I may be misunderstanding you, but I'm proposing we charge "large =
corporations with large travel budgets" slightly *more* than others.[1]  =
I'm not suggesting an overhaul of the system.  I'm not proposing they =
get more attention, or more weight, or any such thing.

Of course they *do* have more impact in subtle ways, because they can =
afford to send people and hire IETF "insiders" and pay salaries for =
people to be ADs and WG chairs and so on.  That's a separate issue, =
which we've long fretted about but can't truly address, nor am I =
proposing to fix it nor make it worse.

I'm just trying to fix the problem at hand. (well... it would only be a =
problem if people think we need better remote participation tools)

-hadriel
[1] "Large corporations" don't actually equate to large travel budgets; =
big corps have travel freezes all the time.  But if you can get expense =
approval for $695 reg-fee, you can likely get approval for $795; and the =
reg-fee is only a portion of the overall travel expense.  If you *can't* =
get approval for the $100 difference, that's ok - just select the =
"Self-Paying Rate".  There's no stigma associated with doing that. (at =
least that's the goal anyway)


On Aug 16, 2013, at 3:10 PM, Keith Moore <moore@network-heretics.com> =
wrote:

> On 08/16/2013 11:36 AM, Hadriel Kaplan wrote:
>> On Aug 16, 2013, at 10:56 AM, Keith Moore =
<moore@network-heretics.com> wrote:
>>=20
>>> As someone who just spent $3.5K out of pocket to show up in Berlin, =
I have a hard time being sympathetic to someone who won't participate =
because he has to spend $100 out of pocket.
>> This isn't about "fairness" or equal-pain-for-all.  It's about =
getting work done and producing good output.  Whether someone remote has =
to pay $0 or $1000 won't change your $3.5k out-of-pocket expense.  If =
you don't feel the $3.5k was worth it for you to go physically, don't =
go.
>=20
> I'm all about having IETF get work done and produce good output. May I =
suggest that we start by trying to reduce IETF's longstanding bias in =
favor of large companies with large travel budgets that pay =
disproportionate attention to narrow and/or short-term interests, and =
against academics and others who take a wider and/or longer view?   The =
Internet has suffered tremendously due to a lack of a long-term view in =
IETF.
>=20
> To that end, I'd like to see IETF do what it can to reduce meeting =
costs for those who attend face-to-face, rather than increase those =
costs even more in order to subsidize remote participation.
>=20
> I have reached the difficult (i.e. expensive) conclusion that the only =
way to participate effectively in IETF (except perhaps in a narrow focus =
area) is to regularly attend face-to-face meetings. There are several =
reasons for this, just a few of which (off the top of my head) are:
>=20
> (1)  It's really hard to understand where people are coming from =
unless/until you've met them in person.  I had been participating in =
IETF for about a year before I showed up at my first meeting, and I =
still remember how
> (2) It's much easier to get a sense of how a group of people react to =
a proposal in person, than over email.
> (3) For several reasons, people seem to react to ideas more favorably =
when discussed face-to-face.
> (4) It's easier to get along well with people whom you see =
face-to-face on at least an occasional basis, so people whom you've met =
face-to-face are more likely to appreciate constructive suggestions and =
to interpret technical criticism as helpful input rather than personal =
attacks.
> (5) Among the many things that hallway conversations are good for are =
quickly settling misunderstandings and resolving disputes.
>=20
> I realize that a better remote participation experience might help =
with some or all of these, but I think we're decades away from being =
able to realize that quality of experience via remote participation, at =
least without developing new technology and spending a lot more money on =
equipment.   If someone wants to fund development of that technology and =
purchase of that equipment separately from the normal IETF revenue =
stream, more power to them.   But I do suspect that at some point it =
will cost money to maintain that technology and equipment, and again, I =
suspect it shouldn't primarily come from people who are paying to be =
there in person.
>=20
> Or if we're really about trying to make IETF as open as possible, then =
we should be willing to publicly declare that people can participate in =
face-to-face meetings without paying the registration fee.  [*]  But I =
don't think that IETF's current funding model can support that.   So =
maybe IAOC should give serious thought to changing the model, but =
offhand I don't know what a better model would be.   Should IETF become =
a membership organization, and let some of the administrative costs be =
borne by membership fees, so that meeting costs can more accurately =
reflect the cost of hosting meetings?   How would the organization =
provide benefits to paying members without excluding participation from =
others?   I don't expect that there are any obviously right answers to =
questions like those - everything involves compromise - but it might be =
that there are far better answers to those questions than those that =
have been assumed for the past 20 years or so.
>=20
> [*] I do realize that some people have, on occasion, shown up as =
"tourists" for the benefit of hallway and bar conversations, and avoided =
paying the meeting fee.
>=20


From hadriel.kaplan@oracle.com  Fri Aug 16 12:46:44 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C4411E815F for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.416
X-Spam-Level: 
X-Spam-Status: No, score=-6.416 tagged_above=-999 required=5 tests=[AWL=0.183,  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 xpKq+nmb7oKp for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 12:46:37 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 85A9211E8162 for <ietf@ietf.org>; Fri, 16 Aug 2013 12:46:37 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7GJkZnk024347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 Aug 2013 19:46:36 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GJkXaI006416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 19:46:34 GMT
Received: from abhmt103.oracle.com (abhmt103.oracle.com [141.146.116.55]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7GJkXvh029017; Fri, 16 Aug 2013 19:46:33 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 12:46:33 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]>
Date: Fri, 16 Aug 2013 15:46:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: carlos@lacnic.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 19:46:44 -0000

On Aug 16, 2013, at 1:53 PM, John C Klensin <john-ietf@jck.com> wrote:

> (1) As Dave points out, this activity has never been free.  The
> question is only about "who pays".  If any participants have to
> pay=20
> (or convince their companies to pay) and others, as a matter of
> categories, do not, that ultimately weakens the process even if,
> most of the time, those who pay don't expect or get favored
> treatment.  Having some participants get a "free ride" that
> really comes at the expense of other participants (and
> potentially competing organizations) is just not a healthy idea.

Baloney.  People physically present still have an advantage over those =
remote, no matter how much technology we throw at this.  That's why =
corporations are willing to pay their employees to travel to these =
meetings.  And it's why people are willing to pay out-of-pocket for it =
too, ultimately.  It's why people want a day-pass type thing for only =
attending one meeting, instead of sitting at home attending remote.=20

Being there is important, and corporations and people know it.

An audio input model (ie, conference call model) still provides plenty =
of advantage to physical attendees, while also providing remote =
participants a chance to have their say in a more emphatic and real-time =
format.  We're not talking about building a telepresence system for all =
remote participants, or using robots as avatars.


>=20
> (2) Trying to figure out exactly what remote participation
> (equipment, staffing, etc.) will cost the IETF and then trying
> to assess those costs to the remote participants would be
> madness for multiple reasons.  [...snip...]

Yet you're proposing charging remote participants to bear the costs.  =
I'm confused.


> (3) Trying to establish a more or less elaborate system of
> categories of participants with category-specific fees or to
> scale the current system of subsidies and waivers to accommodate
> the full range of potential in-person and remote participants is
> almost equally insane.  While we might make such arrangements
> work and keeping categories and status off badges helps, it gets
> us entangled with requiring that the Secretariat and/or IAD
> and/or some IAOC or other "leadership" members be privy to
> information that is at least private and that might be formally
> confidential.  We don't want to go there if we can help it.

I'm not talking about posting this info on web, nor a "full range of =
potential".  We already have multiple reg-fee categories; I'm talking =
about adding *one* more.  I don't know who in the "leadership" can see a =
list of what rates people paid - if we need to constrain that, that's a =
solvable problem.  It's not the sky falling.

Regardless, the same argument can be made for charging remote =
participants to "donate" 0-100% or whatever.

-hadriel


From sginoza@amsl.com  Fri Aug 16 13:16:39 2013
Return-Path: <sginoza@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 9B51911E8151; Fri, 16 Aug 2013 13:16:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.699, BAYES_00=-2.599, 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 gW8zsMZm+4h4; Fri, 16 Aug 2013 13:16:37 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 8117011E8141; Fri, 16 Aug 2013 13:16:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 64365A60D2; Fri, 16 Aug 2013 13:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XYAfIepclAf; Fri, 16 Aug 2013 13:15:17 -0700 (PDT)
Received: from new-host-5.home (pool-108-0-223-143.lsanca.fios.verizon.net [108.0.223.143]) by c9a.amsl.com (Postfix) with ESMTPA id C3632A60D1; Fri, 16 Aug 2013 13:15:16 -0700 (PDT)
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-808--1054962467
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
Date: Fri, 16 Aug 2013 13:16:35 -0700
Message-Id: <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1085)
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.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: Fri, 16 Aug 2013 20:16:39 -0000

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

Greetings,

Since the publication of RFC 5620, the RFC Editor has been working to =
implement the RPC and Publisher split.  Based on our attempts to create =
two separable entities per RFC 5620 and later RFC 6635, our =
understanding of the motivations for splitting the RPC and Publisher =
into distinct functions, and our discussions with the RSE, the RSE has =
created a figure =
<http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpublisher&m=
edia=3Drfc-publisher-split-c.jpg> to describe where the split resides in =
practice.  We believe the figure accurately reflects the most practical =
split in terms of work allocation and portability. =20

The split described in the figure eliminates the need for the Publisher =
to have staff with detailed RFC-specific knowledge by placing the =
majority of staff-related responsibilities with the RPC. Our =
understanding is that it is important for the SoWs to be aligned with =
the split described in the figure, so many of our comments below are an =
attempt to align these documents.  We provide our comments below for =
consideration.=20

Thank you,
Sandy Ginoza=20
(for the RPC and Publisher)


Notes:=20
------

"Current" refers to text as provided in the Proposed SoWs:=20
  http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf
  http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf

"Figure" refers to the figure available at=20
  =
http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpublisher&me=
dia=3Drfc-publisher-split-c.jpg


RFC Production Center
---------------------

1) In the following, we suggest changing "reference IETF documents (RFCs =
and Internet Drafts)" to "referenced documents (RFCs and Internet =
Drafts)" because not all RFCs/I-Ds are IETF-stream documents.

Current:
1.2.  Validation of references

Ensure that references within specifications are available and that =
referenced IETF documents (RFCs and Internet Drafts) are latest versions =
available.  Also, match citations and references for consistency.  In =
the IETF standards stream, specific rules on the suitability and =
availability of references apply, as documented in RFC 2026 and =
successors, as interpreted by the IESG.  Editing of documents may be =
delayed waiting for normative references to become available.


2) In the following, we suggest that "ASN.1 (and particularly MIBs and =
MIB-related details)" be updated to reflect "MIBs".  Although MIB =
modules are written using a subset of ASN.1, the RPC does not check all =
ASN.1, we only check MIBs.  This change will reflect what is done in =
practice.  If the intent is to actually require the RPC to check all =
ASN.1, please let us know and we will discuss checking tools with the =
RSE and IAD.

Current:
1.3.  Validation of formal languages

The RPC should validate the syntax of sections of documents containing =
formal languages.  In particular ASN.1 (and particularly MIBs and =
MIB-related details), YANG, ABNF, and XML should be verified using one =
or more tools as approved by the RSE.     =20


3) Publication takes place in the "Electronic Signing & Announcements" =
box within the figure.  The following text does not seem to align with =
the figure:

Current:
2.     Documents forwarded to RFC Publisher

2.1.  The RPC will edit the documents from all streams consistent with =
the RFC Style Manual, the RFC Series, and the intent of the Authors.  =
Documents so edited will be placed in the ready-to-publish state and =
forwarded to the RFC Publisher.

In the figure, the publication-related actions occur on the RPC side =
because the RPC is responsible for posting RFCs in the public archive, =
sending out the RFC announcements, updating the various indexes, and =
digitally signing the RFCs.  This makes it possible for the RPC to =
respond to requests for legal verification of RFCs.  Therefore, we =
suggest the following update:=20

2. Documents forwarded to RFC Publisher

2.1. The RPC will edit the documents from all streams consistent with =
the RFC Style Manual, the RFC Series, and the intent of the Authors.  =
Documents so edited will be published on the RFC Editor website.=20

Alternately, Section 2.1 could be removed, as the documents will not be =
forwarded to the "Publisher" for publication and because how docs will =
be edited is discussed in Section 1.1.1. =20


For consistency with the above update, we suggest that item 2.2 be =
updated as follows:

Current:
2.2. Additionally, the RPC will forward records of all interaction and =
edits relative to the document, including dialogue with the document =
authors and stream representatives, to the RFC Publisher for archiving.

Suggested:
2.2. The RPC will post all relevant documents, including the related RFC =
files, records of all interaction and edits relative to the document, =
dialogue with the document authors and stream representatives, on the =
RFC Publisher server for archiving.


4) Because the Publisher is responsible for the website, =
webmaster@rfc-editor.org is a Publisher address (and the address in =
mentioned in the Publisher SoW). We suggest that =
"webmaster@rfc-editor.org" be removed from the text below.

Current:
6.2.  Response to general questions directed to =
rfc-editor@rfc-editor.org and webmaster@rfc-editor.org, coordinating as =
necessary with the RFC Publisher and RSE.


5) If item 3 (above) is accepted and Section 2.1 is updated or removed =
from the SoW, the Work Standards should be updated to refer to =
"publication" or "published" instead of "Forwarded Date" or "forwarded", =
for example:

Current:
A.2.1.1. A document is =93received=94 by the RPC on the date of the =
receipt of a request to publish by the each of the respective streams =
(Receipt Date).

A.2.1.2. A document is =93ready-to-publish=94 on the date it is =
forwarded to the RFC Publisher by the RPC (Forwarded Date).   =20

We suggest:
A.2.1.1. A document is =93received=94 by the RPC on the date of the =
receipt of a request to publish by the each of the respective streams =
(Receipt Date).

A.2.1.2. A document is "published" on the date the RFC is made available =
on the RFC Editor website and the RFC announcement is sent (Publication =
Date).

Note that the contractual definition of the "Publication Date" is not =
new; it is currently defined in =
http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012-5-24-11_000.=
pdf as=20

The date of announcement is defined as the date of publication.=20


If "Forwarded Date" is changed to "Publication Date", then these items =
should also be updated:

Current:
A.2.2.1. Processing times per document are from Receipt Date to =
Forwarded Date in total business days.

A.2.2.2. While the overall goal for document publication is 30 business =
days (6 weeks) from Receipt Date to Forwarded Date, the times measured =
in the defined Service Levels are times in RPC state.


6)  We suggest removing the first sentence of A.2.2.4 because it is =
redundant with earlier text and is not as clear as A.2.2.2, which can be =
summarized as:=20

- Overall goal: time in all states (RFC-Editor-controlled states + 3rd =
party states) < 6 weeks
- Actually measured for SLA: time in RFC-Editor-controlled states

Note that we also recommend changing "RPC state" to =
"RFC-Editor-controlled states" throughout for clarity.  Alternately, we =
suggest that "RPC State" be defined as special term.=20


Publisher
---------

7) In our understanding of the figure, the Publisher function provides =
access to the post-publication data, but the RPC would actually make any =
changes to post-publication data.  So, it seems inaccurate to include =
the Publisher is 'responsible for [...] post-publication data'.  =
Therefore, we suggest the following update:

Current:
The RFC Publisher function is described in RFC 6635 and is responsible =
for the storage and post-publication data for RFCs, access to the =
website, access to the errata reports, search tools and indexes, the =
archive of documents, and all backups and failover processes.

Suggested:
The RFC Publisher function is described in RFC 6635 and is responsible =
for the storage of and access to the website, errata reports, search =
tools and indexes, the archive of documents, and all backups and =
failover processes.


8) As mentioned in item 3 above, we believe that the action of =
publishing documents, and therefore the publication processes, are the =
responsibility of the RPC.  With that in mind, we suggest the following =
update to the Overview:

Current:
The Publisher will accept, store and publish documents from the RFC =
Production Center and
other material as determined by the RSE.  The RSE may authorize other =
entities to submit
documents directly for publication, but those documents are published on =
the authority of the
RSE.  Changes to the publication process and public-facing tools will be =
made under the advice
and approval of the RSE.

Suggested:
The Publisher will accept and store documents from the RFC Production =
Center and other material as determined by the RSE. =20

We suggest that the remainder of the text be removed.  While the =
Publisher houses the tools used by the various RFC Editor components, it =
is the various components that have the staff to suggest and implement =
changes to the publication process and tools.

Also, it is not clear to us what is meant by "other entities to submit =
documents directly for publication".  Does this refer to web content or =
perhaps I-Ds that are to be published without being edited?  Both of =
these cases seem to fall into the RPC SoW, as the RPC is responsible for =
content on the website, and even if an I-D is to be published without =
changes, it would need to be updated to conform with current format and =
boilerplate standards.  Are there other cases in which this "directly =
for publication" may apply?


9) To make it clear that the RPC updates various data, and the Publisher =
simply makes it available on a server, we suggest changing these =
instances of "publish" and "post" to "make available" as follows:

Current:
RFCs are published on the Publisher=92s website. This site includes one =
or more indexes with hyperlinked access to published documents as well =
as a convenient search engine.

Suggested:
RFCs are made available on the Publisher=92s website. This site includes =
one or more indexes with hyperlinked access to published documents as =
well as a convenient search engine.

(Note: SM also suggested making "Publisher's website" be "RFC Editor =
website")


Current:
1.2.5.     post Web content as provided by the RSE, ISE, and/or the RFC =
Production Center,

We suggest deleting Section 1.2.5 from the Publisher SoW or updating it =
to read:
      1.2.5.     make available Web content as provided by the RSE, ISE, =
and/or the RFC Production Center,


Current:=20
3.1.1.  Publish state information for each document in the publication =
process.

Suggested:=20
3.1.1.  State information for each document in the publication process.


10) With the understanding that the RPC is responsible for creating and =
maintaining the web content (which presumably includes organizing the =
web content), and the Publisher for serving the content, we suggest this =
item be altered as follows. (Also: second sentence deleted because =
already covered in 1.2.6.)

Current:
1.2.7.     provide continual incremental improvements, including =
regularly redesigning web page trees to respond to common usage =
patterns.  However, stable identifiers must be maintained for the RFCs, =
archives, Errata, indices and other items.

Suggested:
1.2.7.  provide data about the website usage patterns so that the =
maintainers of the web content can organize it accordingly.


11) We believe the following item should be updated because an address =
should be provided to reach the Publisher (and this same address is used =
numerous times in Appendix 1 for items for which the Publisher is =
responsible) and because the RPC should not be a middleman in cases of =
server failure, etc.=20

Current:=20
1.4. Customer Support Services. Messages sent to certain conventional =
addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall =
automatically be delivered to the RFC Production Center

Suggested:=20
1.4. Customer Support Services. Messages sent to certain conventional =
addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall =
be coordinated with the RPC as appropriate.


12) We question whether integration is really a publisher task.  The RPC =
has a programmer, so it seems the RPC would be responsible for the =
programming aspects and the Publisher would be responsible for ensuring =
the right access/security for integration.=20

Current:
3.1.2.     Integrate Production Center state information with the IETF =
tools or such other tool sets as directed by the RSE to provide =
end-to-end status tracking of documents=20

Perhaps Section 3.1.2 should be deleted, as Section 2.3.2 indicates that =
the Publisher should provide appropriate access for integration.


13) We suggest removing item 3.1.3, because it seems to be covered by =
providing state information, as described in Section 3.1.1.

Current:
3.1.3.     Provide external visibility regarding when a document is in =
an extended waiting period, the token-holder and circumstances of the =
wait.


14) While the Publisher may participate in discussions about the =
technical support systems required to address policy changes, we do not =
believe the Publisher needs to be involved in discussion regarding all =
publication policy changes.  Therefore, we suggest the following update:

Current:
6.1.  Participate in the discussions of the technical publication =
process with the RSE for policy changes.

Suggested:
6.1.  Participate in policy discussions about technical support of the =
publication process.=20


15) It is not clear to us that the Publisher enforces RFC Series =
consistency, as the Publisher is responsible for making the files =
available and maintaining the archives.

Current:=20
7.  Accountability

The Publisher is primarily responsible to the RSE as regards to RFC =
Series consistency.

Perhaps this should be updated as:
7.  Accountability

The Publisher is primarily responsible to the RSE regarding technical =
support and hosting of the RFC Series.=20


15) The Work Standards are listed in "Exhibit B", but there is no =
"Exhibit A" - is some text missing, or should Exhibit B be Exhibit A?


On Aug 16, 2013, at 11:47 AM, Ray Pelletier wrote:

> All;
>=20
> Are there any more comments on the SOWs?
>=20
> This item will be on the IAOC agenda for its call on 22 August.
>=20
> Ray
>=20
> On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:
>=20
>> The RFC Series Editor (RSE) is proposing changes to the Statements of =
Work (SOW) for the RFC=20
>> Production Center (RPC) and the RFC Publisher.  The IAOC wants to =
receive community input prior to=20
>> negotiating the proposed changes with the contractor.  Community =
input will be discussed with the RSE=20
>> prior to negotiations and reviewed by the IAOC.
>>=20
>> In forwarding the proposed Statements of Work the RSE said:  "The =
changes seek to make the SoWs=20
>> more current [implementing RFC 6635] and specific, correcting the =
issues of "multiple masters"=20
>> directing the RPC and Publisher, as well as preparing the way for a =
more significant revision to the SoWs
>> when the RFC Format changes are operationalized.  The SoWs have also =
been reviewed and supported=20
>> by the RSOC [RFC Series Oversight Committee].  We consider the =
changes within the SoWs critical to the=20
>> clear function of the RPC and Publisher, but suggest that the changes =
do not imply a significant change=20
>> in responsibility for the RPC or Publisher."
>>=20
>> The proposed SOWs, the current SOWs and a diff file for each can be =
found here under Community=20
>> Review: <http://iaoc.ietf.org/rfps.html>
>>=20
>> We appreciate the community's input and look forward to hearing from =
you. =20
>>=20
>> Thanks
>>=20
>> Ray Pelletier
>> IAD
>=20


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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>Greetings,</div><div><br><div><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Since the publication of RFC 5620, the RFC Editor has been =
working to implement the RPC and Publisher split. &nbsp;Based on our =
attempts to create two separable entities per RFC 5620 and later RFC =
6635, our understanding&nbsp;of the motivations for splitting the RPC =
and Publisher into distinct functions, and our discussions with the RSE, =
the&nbsp;RSE has created a&nbsp;figure &lt;<a =
href=3D"http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpubl=
isher&amp;media=3Drfc-publisher-">http://www.rfc-editor.org/rse/wiki/lib/e=
xe/detail.php?id=3Drfcpublisher&amp;media=3Drfc-publisher-</a>split-c.jpg&=
gt; to describe where the split resides in practice. &nbsp;We believe =
the figure&nbsp;accurately reflects the most&nbsp;practical split in =
terms of work allocation&nbsp;and portability. =
&nbsp;</div></div></div></div><br><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>The split described in the =
figure eliminates the need&nbsp;for the Publisher to have staff with =
detailed RFC-specific knowledge by placing the majority of =
staff-related&nbsp;responsibilities with the RPC.&nbsp;Our understanding =
is that it is important for the SoWs to be aligned with the =
split&nbsp;described in the figure, so many of our comments below are an =
attempt to align these documents. &nbsp;We provide our comments below =
for =
consideration.&nbsp;</div></div></div></div></div></div><div><br>Thank =
you,<br>Sandy Ginoza&nbsp;</div><div>(for the RPC and =
Publisher)<br><br><br>Notes:&nbsp;<br>------<div><br>"Current" refers to =
text as provided in the Proposed SoWs:&nbsp;<br>&nbsp;&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf">ht=
tp://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf</a><br>&nbsp;=
&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf=
">http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf</a><b=
r><br>"Figure" refers to the figure available at&nbsp;<br>&nbsp;&nbsp;<a =
href=3D"http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=3Drfcpubl=
isher&amp;media=3Drfc-publisher-split-c.jpg">http://www.rfc-editor.org/rse=
/wiki/lib/exe/detail.php?id=3Drfcpublisher&amp;media=3Drfc-publisher-split=
-c.jpg</a><br><br><br>RFC Production =
Center<br>---------------------<br><br>1) In the following, we suggest =
changing "reference IETF documents (RFCs and Internet Drafts)" to =
"referenced&nbsp;documents (RFCs and Internet Drafts)" because not all =
RFCs/I-Ds are IETF-stream documents.<br><br>Current:<br><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; ">1.2.&nbsp;&nbsp;Validation&nbsp;of =
references<br><br></blockquote><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; ">Ensure that references within&nbsp;specifications =
are available and that referenced IETF documents (RFCs and&nbsp;Internet =
Drafts) are latest versions available.&nbsp;&nbsp;Also, match citations =
and references for consistency.&nbsp;&nbsp;In the&nbsp;IETF standards =
stream, specific&nbsp;rules on the suitability and availability of =
references apply, as documented&nbsp;in&nbsp;RFC 2026 and successors, as =
interpreted by the IESG.&nbsp;&nbsp;Editing of documents may be delayed =
waiting for&nbsp;normative&nbsp;references to become =
available.</blockquote><br><br>2)&nbsp;In the following, we suggest that =
"ASN.1 (and particularly MIBs and MIB-related details)" be updated to =
reflect "MIBs".&nbsp;&nbsp;Although MIB modules are written using a =
subset of ASN.1, the RPC does not check all ASN.1, we only check MIBs. =
&nbsp;This change will reflect what is done in practice. &nbsp;If the =
intent is to actually require the RPC to check all ASN.1, please let us =
know and we will&nbsp;discuss checking tools with the RSE and =
IAD.<br><br>Current:<br><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; =
">1.3.&nbsp;&nbsp;Validation&nbsp;of formal =
languages</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; "><br>The RPC should validate =
the syntax of&nbsp;sections of documents containing formal =
languages.&nbsp;&nbsp;In particular ASN.1&nbsp;(and particularly MIBs =
and MIB-related&nbsp;details), YANG, ABNF, and XML should be verified =
using one or more tools&nbsp;as&nbsp;approved by the =
RSE.&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;</blockquote><br><br>3) Publication =
takes&nbsp;place in the "Electronic Signing &amp; Announcements" box =
within the figure. &nbsp;The following text does not seem to align with =
the figure:<br><br>Current:<br><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; ">2.&nbsp; &nbsp;&nbsp;&nbsp;Documents forwarded to =
RFC Publisher</blockquote><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; =
"><br>2.1.&nbsp;&nbsp;The&nbsp;RPC will edit the documents from all =
streams consistent with the RFC Style&nbsp;Manual, the RFC Series, =
and&nbsp;the intent of the Authors.&nbsp;&nbsp;Documents so edited will =
be placed in&nbsp;the ready-to-publish state and forwarded to&nbsp;the =
RFC Publisher.</blockquote><br>In the figure, the publication-related =
actions occur on the RPC side because the RPC is responsible for posting =
RFCs in the public archive, sending out the RFC announcements, updating =
the various indexes, and digitally signing the RFCs. &nbsp;This makes it =
possible for the RPC to respond to requests for legal verification of =
RFCs. &nbsp;Therefore, we suggest the following =
update:&nbsp;<div><br></div><blockquote class=3D"webkit-indent-blockquote"=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; "><div>2.&nbsp;Documents =
forwarded to RFC Publisher</div><div><br></div><div>2.1.&nbsp;The RPC =
will edit the documents from all streams consistent with the RFC Style =
Manual, the RFC Series,&nbsp;and the intent of the =
Authors.&nbsp;&nbsp;Documents so edited will be published on the RFC =
Editor website.&nbsp;</div></blockquote><div><br>Alternately, Section =
2.1 could be removed, as the documents will not be forwarded to the =
"Publisher" for publication&nbsp;and because how docs will be edited is =
discussed in Section 1.1.1.&nbsp;&nbsp;<br><br><br>For consistency with =
the above update, we suggest that item 2.2 be updated as =
follows:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>2.2. Additionally, the RPC will forward =
records of all interaction and edits relative to the =
document,&nbsp;including dialogue with the document authors and stream =
representatives, to the RFC Publisher for =
archiving.</div></blockquote><div><br>Suggested:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>2.2. The RPC will post all relevant documents, =
including the related RFC files, records of all interaction =
and&nbsp;edits relative to the document, dialogue with the document =
authors and stream representatives, on the RFC&nbsp;Publisher server for =
archiving.</div></blockquote><div><br><br>4)&nbsp;Because the Publisher =
is responsible for the website,&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>&nbsp=
;is a Publisher address (and the address in mentioned in the Publisher =
SoW). We suggest that "<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>" =
be removed from the text =
below.</div><div><br></div><div>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>6.2.&nbsp;&nbsp;Response&nbsp;to general =
questions directed to&nbsp;<a =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>&nb=
sp;and&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>,&nbs=
p;coordinating as necessary with the RFC Publisher&nbsp;and =
RSE.</div><div><br></div></blockquote><div><br>5) If item 3 (above) is =
accepted and Section 2.1 is updated or removed from the SoW, the Work =
Standards should be updated to&nbsp;refer to "publication" or =
"published" instead of "Forwarded Date" or "forwarded", for =
example:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal 'Times New Roman'; "><font class=3D"Apple-style-span" =
face=3D"Courier">A.2.1.1. A document is =93received=94 by the RPC on the =
date of the receipt of a request to publish by the each of the =
respective streams (Receipt =
Date).</font></div></div></blockquote><div><br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>A.2.1.2. A document is&nbsp;=93ready-to-publish=94=
 on the date it is forwarded to the RFC Publisher by the =
RPC&nbsp;(Forwarded Date).&nbsp; =
&nbsp;&nbsp;</div></blockquote><div><br>We suggest:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>A.2.1.1. A document is =93received=94 by the =
RPC on the date of the receipt of a request to publish by the each of =
the respective streams (Receipt Date).</div><div><br></div><div>A.2.1.2. =
A document is "published" on the date the RFC is made available on the =
RFC Editor website and the RFC announcement is sent (Publication =
Date).</div></blockquote><div><br>Note that the contractual definition =
of the "Publication Date" is not new; it is currently defined in&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012-5-24=
-11_000.pdf">http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012=
-5-24-11_000.pdf</a>&nbsp;as&nbsp;</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div><div dir=3D"ltr" data-font-name=3D"g_font_p0_19"=
 data-canvas-width=3D"627.8356633680341" style=3D"left: 96.1602px; top: =
667.2px; "><br></div></div><div><div dir=3D"ltr" =
data-font-name=3D"g_font_p0_19" data-canvas-width=3D"627.8356633680341" =
style=3D"left: 96.1602px; top: 667.2px; ">The date of&nbsp;announcement =
is defined as the&nbsp;<span class=3D"highlight selected">date of =
publication</span>.&nbsp;</div></div></blockquote><div><br><br></div><div>=
If "Forwarded Date" is changed to "Publication Date", then these items =
should also be =
updated:</div><div><br></div><div>Current:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>A.2.2.1. Processing times per document are =
from Receipt Date to Forwarded Date in total business =
days.</div><div><br></div><div>A.2.2.2. While the overall goal for =
document publication is 30 business days (6 weeks) from Receipt Date to =
Forwarded Date, the times measured in the defined Service Levels are =
times in RPC =
state.</div></blockquote><div><br></div><div><br></div><div>6) &nbsp;We =
suggest removing the first sentence of A.2.2.4 because it is redundant =
with earlier text and is not as clear as A.2.2.2, which can be =
summarized as:&nbsp;</div><div><br></div><div>- Overall goal: time in =
all states (RFC-Editor-controlled states + 3rd party states) &lt; 6 =
weeks</div><div>- Actually measured for SLA: time in =
RFC-Editor-controlled states<br></div><div><br></div><div>Note that we =
also recommend changing "RPC state" to "RFC-Editor-controlled states" =
throughout for clarity. &nbsp;Alternately, we suggest that "RPC State" =
be defined as special =
term.&nbsp;<br><br><br>Publisher</div><div>---------<br><br>7)&nbsp;In =
our understanding of the figure, the Publisher function provides access =
to the post-publication data, but the RPC would actually make any =
changes to post-publication data. &nbsp;So, it seems inaccurate to =
include the Publisher is 'responsible for [...] post-publication data'. =
&nbsp;Therefore, we suggest the following =
update:</div><div><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>The RFC Publisher function&nbsp;is described =
in RFC 6635 and is responsible for the storage =
and&nbsp;post-publication&nbsp;data for RFCs, access to the website, =
access to&nbsp;the errata reports, search tools and indexes, the archive =
of&nbsp;documents, and all&nbsp;backups and failover =
processes.</div></blockquote><div><br>Suggested:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>The RFC Publisher function is described in RFC =
6635 and is responsible for the storage of and access to =
the&nbsp;website, errata reports, search tools and indexes, the archive =
of documents, and all backups and =
failover&nbsp;processes.</div></blockquote><div><br><br>8) As mentioned =
in item 3 above, we believe that the action of publishing documents, and =
therefore the publication&nbsp;processes, are the responsibility of the =
RPC. &nbsp;With that in mind, we suggest the following update to the =
Overview:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div><div>The Publisher will accept, store and =
publish documents from the RFC Production Center =
and</div></div><div><div>other material as determined by the RSE. =
&nbsp;The RSE may authorize other entities to =
submit</div></div><div><div>documents directly for publication, but =
those documents are published on the authority of =
the</div></div><div><div>RSE. &nbsp;Changes to the publication process =
and public-facing tools will be made under the =
advice</div></div><div><div>and approval of the =
RSE.</div></div></blockquote><div><br>Suggested:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>The Publisher will accept and store documents =
from the RFC Production Center and other material as determined&nbsp;by =
the RSE.&nbsp;&nbsp;</div></blockquote><div><br>We suggest that the =
remainder of the text be removed. &nbsp;While the Publisher houses the =
tools used by the various RFC Editor&nbsp;components, it is the various =
components that have the staff to suggest and implement changes to the =
publication&nbsp;process and tools.<br><br>Also, it is not clear to us =
what is meant by "other entities to submit documents directly for =
publication". &nbsp;Does&nbsp;this refer to web content or perhaps I-Ds =
that are to be published without being edited? &nbsp;Both of these cases =
seem to&nbsp;fall into the RPC SoW, as the RPC is responsible for =
content on the website, and even if an I-D is to be =
published&nbsp;without changes, it would need to be updated to conform =
with current format and boilerplate standards. &nbsp;Are =
there&nbsp;other cases in which this "directly for publication" may =
apply?<br><br><br>9)&nbsp;To make it clear that the RPC updates various =
data, and the Publisher simply makes it available on a server, we =
suggest changing these instances of "publish" and "post" to "make =
available" as follows:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>RFCs are published on the Publisher=92s =
website. This site&nbsp;includes one or more indexes with hyperlinked =
access&nbsp;to published documents as&nbsp;well as a convenient search =
engine.</div></blockquote><div><br></div><div>Suggested:<br></div><blockqu=
ote class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>RFCs are made available on the Publisher=92s =
website. This site includes one or more indexes with =
hyperlinked&nbsp;access to published documents as well as a convenient =
search engine.</div></blockquote><div><br>(Note: SM also suggested =
making "Publisher's website" be "RFC Editor =
website")<br><br><br></div><div>Current:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.2.5. &nbsp; &nbsp; post Web content as =
provided by the RSE, ISE, and/or the RFC Production =
Center,</div></blockquote><div><br>We suggest deleting Section 1.2.5 =
from the Publisher SoW or updating it to read:<br>&nbsp; &nbsp; =
&nbsp;&nbsp;1.2.5. &nbsp; &nbsp; make available Web content as provided =
by the RSE, ISE, and/or the RFC Production =
Center,<br><br></div><div><br></div><div><div>Current:&nbsp;<br></div><blo=
ckquote class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.1. &nbsp;Publish state information for =
each document in the&nbsp;publication =
process.</div></blockquote><div><br>Suggested:&nbsp;<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.1. &nbsp;State information for each =
document in the publication =
process.</div></blockquote></div><div><br></div><div><br>10)&nbsp;With =
the understanding that the RPC is responsible for creating and =
maintaining the web content (which presumably includes organizing the =
web content), and the Publisher for serving the content, we suggest this =
item be altered as follows. (Also: second sentence deleted because =
already covered in 1.2.6.)<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.2.7.&nbsp; &nbsp;&nbsp;&nbsp;provide =
continual&nbsp;incremental improvements, including regularly redesigning =
web page trees to&nbsp;respond&nbsp;to common usage =
patterns.&nbsp;&nbsp;However, stable identifiers must be maintained for =
the RFCs, archives,&nbsp;Errata,&nbsp;indices and other =
items.</div></blockquote><div><br></div><div>Suggested:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.2.7. &nbsp;provide data about the website =
usage patterns so that the maintainers of the web content can organize =
it accordingly.</div></blockquote><div><br><br>11) We believe the =
following item should be updated because an address should be provided =
to reach the Publisher (and&nbsp;this same address is used numerous =
times in Appendix 1 for items for which the Publisher is responsible) =
and because&nbsp;the RPC should not be a middleman in cases of server =
failure, etc.&nbsp;<br><br>Current:&nbsp;<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.4. Customer Support Services.&nbsp;Messages =
sent to certain conventional addresses as defined by the RSE, such =
as&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>,&nbs=
p;shall automatically be delivered to the RFC Production =
Center</div></blockquote><div><br>Suggested:&nbsp;<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>1.4. Customer Support Services. Messages sent =
to certain conventional addresses as defined by the RSE, such as&nbsp;<a =
href=3D"mailto:webmaster@rfc-editor.org">webmaster@rfc-editor.org</a>, =
shall be coordinated with the RPC as =
appropriate.</div></blockquote><div><br><br>12) We question whether =
integration is really a publisher task. &nbsp;The RPC has a programmer, =
so it seems the RPC would&nbsp;be responsible for the programming =
aspects and the Publisher would be responsible for ensuring the right =
access/security for =
integration.&nbsp;<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.2.&nbsp; &nbsp; &nbsp;Integrate Production =
Center state information with the&nbsp;IETF tools&nbsp;or such other =
tool sets as directed&nbsp;by the RSE&nbsp;to provide end-to-end status =
tracking of documents&nbsp;</div></blockquote><div><br>Perhaps Section =
3.1.2 should be deleted, as Section 2.3.2 indicates that the Publisher =
should provide appropriate access =
for&nbsp;integration.<br><br><br></div><div>13) We suggest removing item =
3.1.3, because it seems to be covered by providing state information, as =
described in&nbsp;Section =
3.1.1.<br><br></div><div>Current:</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>3.1.3.&nbsp; &nbsp;&nbsp;&nbsp;Provide =
external&nbsp;visibility regarding when a document is in an extended =
waiting period, the&nbsp;token-holder and circumstances of the =
wait.</div></blockquote><div><br><br>14) While the Publisher may =
participate in discussions about the technical support systems required =
to address policy&nbsp;changes, we do not believe the Publisher needs to =
be involved in discussion regarding all publication policy =
changes.&nbsp;&nbsp;Therefore, we suggest the following =
update:<br><br>Current:<br></div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>6.1.&nbsp;&nbsp;Participate in&nbsp;the =
discussions of the technical publication process with the RSE for =
policy&nbsp;changes.</div></blockquote><div><br>Suggested:<br></div><block=
quote class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>6.1. &nbsp;Participate in policy discussions =
about technical support of the publication =
process.&nbsp;</div></blockquote><div><br><br></div><div>15) It is not =
clear to us that the Publisher enforces RFC Series consistency, as the =
Publisher is responsible for making the&nbsp;files available and =
maintaining the =
archives.<br><br></div><div>Current:&nbsp;</div><blockquote =
class=3D"webkit-indent-blockquote" style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 40px; =
border-top-style: none; border-right-style: none; border-bottom-style: =
none; border-left-style: none; border-width: initial; border-color: =
initial; padding-top: 0px; padding-right: 0px; padding-bottom: 0px; =
padding-left: 0px; "><div>7. =
&nbsp;Accountability</div><div><br></div><div>The Publisher is primarily =
responsible to the RSE as&nbsp;regards to RFC Series =
consistency.</div></blockquote><div><br>Perhaps this should be updated =
as:<br></div><blockquote class=3D"webkit-indent-blockquote" =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 40px; border-top-style: none; border-right-style: none; =
border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; padding-top: 0px; padding-right: 0px; =
padding-bottom: 0px; padding-left: 0px; "><div>7. =
&nbsp;Accountability</div><div><br></div><div>The Publisher is primarily =
responsible to the RSE regarding technical support and hosting of the =
RFC&nbsp;Series.&nbsp;</div></blockquote><div><br><br>15) The Work =
Standards are listed in "Exhibit B", but there is no "Exhibit A" - is =
some text missing, or should&nbsp;Exhibit B be Exhibit =
A?<br><br></div></div></div></div><br><div><div>On Aug 16, 2013, at =
11:47 AM, Ray Pelletier wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>All;<br><br>Are there any more comments on the =
SOWs?<br><br>This item will be on the IAOC agenda for its call on 22 =
August.<br><br>Ray<br><br>On Aug 12, 2013, at 5:54 PM, IETF =
Administrative Director wrote:<br><br><blockquote type=3D"cite">The RFC =
Series Editor (RSE) is proposing changes to the Statements of Work (SOW) =
for the RFC <br></blockquote><blockquote type=3D"cite">Production Center =
(RPC) and the RFC Publisher. &nbsp;The IAOC wants to receive community =
input prior to <br></blockquote><blockquote type=3D"cite">negotiating =
the proposed changes with the contractor. &nbsp;Community input will be =
discussed with the RSE <br></blockquote><blockquote type=3D"cite">prior =
to negotiations and reviewed by the IAOC.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In forwarding =
the proposed Statements of Work the RSE said: &nbsp;"The changes seek to =
make the SoWs <br></blockquote><blockquote type=3D"cite">more current =
[implementing RFC 6635] and specific, correcting the issues of "multiple =
masters" <br></blockquote><blockquote type=3D"cite">directing the RPC =
and Publisher, as well as preparing the way for a more significant =
revision to the SoWs<br></blockquote><blockquote type=3D"cite">when the =
RFC Format changes are operationalized. &nbsp;The SoWs have also been =
reviewed and supported <br></blockquote><blockquote type=3D"cite">by the =
RSOC [RFC Series Oversight Committee]. &nbsp;We consider the changes =
within the SoWs critical to the <br></blockquote><blockquote =
type=3D"cite">clear function of the RPC and Publisher, but suggest that =
the changes do not imply a significant change =
<br></blockquote><blockquote type=3D"cite">in responsibility for the RPC =
or Publisher."<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The proposed =
SOWs, the current SOWs and a diff file for each can be found here under =
Community <br></blockquote><blockquote type=3D"cite">Review: &lt;<a =
href=3D"http://iaoc.ietf.org/rfps.html">http://iaoc.ietf.org/rfps.html</a>=
&gt;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">We appreciate =
the community's input and look forward to hearing from you. =
&nbsp;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote =
type=3D"cite">Thanks<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Ray =
Pelletier<br></blockquote><blockquote =
type=3D"cite">IAD<br></blockquote><br></div></blockquote></div><br></body>=
</html>=

--Apple-Mail-808--1054962467--

From stephen.farrell@cs.tcd.ie  Fri Aug 16 13:30:11 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B9F21F9C91; Fri, 16 Aug 2013 13:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JYXt7hGY5AOi; Fri, 16 Aug 2013 13:29:57 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1372C11E822A; Fri, 16 Aug 2013 13:29:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B275ABE58; Fri, 16 Aug 2013 21:29:54 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zvpx0YpaqBtM; Fri, 16 Aug 2013 21:29:53 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.46.31.41]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C78B1BE53; Fri, 16 Aug 2013 21:29:52 +0100 (IST)
Message-ID: <520E8BBB.9050507@cs.tcd.ie>
Date: Fri, 16 Aug 2013 21:29:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Sandy Ginoza <sginoza@amsl.com>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
In-Reply-To: <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, 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: Fri, 16 Aug 2013 20:30:12 -0000

Hi Sandy,

I'm not sure how or if it plays into the SoW but your diagram
shows errata handling in the publisher part.

Many people find the current errata process not that great, but
we've collectively not gotten around to figuring out something
better.

I think the possible consequence is that it might be good to
have some flexibility in terms of how errata are processed in
future, e.g. if we all do get around to figuring out something
better it might be good for that not to be precluded by this
SOW being overly prescriptive in that respect. (I don't know
that the SOW is prescriptive about this btw, I did read it a
few days ago but didn't consider this aspect and am about to
head out for the evening... and going out wins:-)

As I said, I'm not sure if that might result in some change
here, but be good if the folks thinking about this SOW keep that
in mind.

Ta,
S.

On 08/16/2013 09:16 PM, Sandy Ginoza wrote:
> Greetings,
> 
> Since the publication of RFC 5620, the RFC Editor has been working to implement the RPC and Publisher split.  Based on our attempts to create two separable entities per RFC 5620 and later RFC 6635, our understanding of the motivations for splitting the RPC and Publisher into distinct functions, and our discussions with the RSE, the RSE has created a figure <http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=rfcpublisher&media=rfc-publisher-split-c.jpg> to describe where the split resides in practice.  We believe the figure accurately reflects the most practical split in terms of work allocation and portability.  
> 
> The split described in the figure eliminates the need for the Publisher to have staff with detailed RFC-specific knowledge by placing the majority of staff-related responsibilities with the RPC. Our understanding is that it is important for the SoWs to be aligned with the split described in the figure, so many of our comments below are an attempt to align these documents.  We provide our comments below for consideration. 
> 
> Thank you,
> Sandy Ginoza 
> (for the RPC and Publisher)
> 
> 
> Notes: 
> ------
> 
> "Current" refers to text as provided in the Proposed SoWs: 
>   http://iaoc.ietf.org/documents/RPC-Proposed-SoW-2013-final.pdf
>   http://iaoc.ietf.org/documents/PUB-Proposed-SoW-2013-final_000.pdf
> 
> "Figure" refers to the figure available at 
>   http://www.rfc-editor.org/rse/wiki/lib/exe/detail.php?id=rfcpublisher&media=rfc-publisher-split-c.jpg
> 
> 
> RFC Production Center
> ---------------------
> 
> 1) In the following, we suggest changing "reference IETF documents (RFCs and Internet Drafts)" to "referenced documents (RFCs and Internet Drafts)" because not all RFCs/I-Ds are IETF-stream documents.
> 
> Current:
> 1.2.  Validation of references
> 
> Ensure that references within specifications are available and that referenced IETF documents (RFCs and Internet Drafts) are latest versions available.  Also, match citations and references for consistency.  In the IETF standards stream, specific rules on the suitability and availability of references apply, as documented in RFC 2026 and successors, as interpreted by the IESG.  Editing of documents may be delayed waiting for normative references to become available.
> 
> 
> 2) In the following, we suggest that "ASN.1 (and particularly MIBs and MIB-related details)" be updated to reflect "MIBs".  Although MIB modules are written using a subset of ASN.1, the RPC does not check all ASN.1, we only check MIBs.  This change will reflect what is done in practice.  If the intent is to actually require the RPC to check all ASN.1, please let us know and we will discuss checking tools with the RSE and IAD.
> 
> Current:
> 1.3.  Validation of formal languages
> 
> The RPC should validate the syntax of sections of documents containing formal languages.  In particular ASN.1 (and particularly MIBs and MIB-related details), YANG, ABNF, and XML should be verified using one or more tools as approved by the RSE.      
> 
> 
> 3) Publication takes place in the "Electronic Signing & Announcements" box within the figure.  The following text does not seem to align with the figure:
> 
> Current:
> 2.     Documents forwarded to RFC Publisher
> 
> 2.1.  The RPC will edit the documents from all streams consistent with the RFC Style Manual, the RFC Series, and the intent of the Authors.  Documents so edited will be placed in the ready-to-publish state and forwarded to the RFC Publisher.
> 
> In the figure, the publication-related actions occur on the RPC side because the RPC is responsible for posting RFCs in the public archive, sending out the RFC announcements, updating the various indexes, and digitally signing the RFCs.  This makes it possible for the RPC to respond to requests for legal verification of RFCs.  Therefore, we suggest the following update: 
> 
> 2. Documents forwarded to RFC Publisher
> 
> 2.1. The RPC will edit the documents from all streams consistent with the RFC Style Manual, the RFC Series, and the intent of the Authors.  Documents so edited will be published on the RFC Editor website. 
> 
> Alternately, Section 2.1 could be removed, as the documents will not be forwarded to the "Publisher" for publication and because how docs will be edited is discussed in Section 1.1.1.  
> 
> 
> For consistency with the above update, we suggest that item 2.2 be updated as follows:
> 
> Current:
> 2.2. Additionally, the RPC will forward records of all interaction and edits relative to the document, including dialogue with the document authors and stream representatives, to the RFC Publisher for archiving.
> 
> Suggested:
> 2.2. The RPC will post all relevant documents, including the related RFC files, records of all interaction and edits relative to the document, dialogue with the document authors and stream representatives, on the RFC Publisher server for archiving.
> 
> 
> 4) Because the Publisher is responsible for the website, webmaster@rfc-editor.org is a Publisher address (and the address in mentioned in the Publisher SoW). We suggest that "webmaster@rfc-editor.org" be removed from the text below.
> 
> Current:
> 6.2.  Response to general questions directed to rfc-editor@rfc-editor.org and webmaster@rfc-editor.org, coordinating as necessary with the RFC Publisher and RSE.
> 
> 
> 5) If item 3 (above) is accepted and Section 2.1 is updated or removed from the SoW, the Work Standards should be updated to refer to "publication" or "published" instead of "Forwarded Date" or "forwarded", for example:
> 
> Current:
> A.2.1.1. A document is “received” by the RPC on the date of the receipt of a request to publish by the each of the respective streams (Receipt Date).
> 
> A.2.1.2. A document is “ready-to-publish” on the date it is forwarded to the RFC Publisher by the RPC (Forwarded Date).    
> 
> We suggest:
> A.2.1.1. A document is “received” by the RPC on the date of the receipt of a request to publish by the each of the respective streams (Receipt Date).
> 
> A.2.1.2. A document is "published" on the date the RFC is made available on the RFC Editor website and the RFC announcement is sent (Publication Date).
> 
> Note that the contractual definition of the "Publication Date" is not new; it is currently defined in http://iaoc.ietf.org/documents/RFC-Publisher-Current-SOW-2012-5-24-11_000.pdf as 
> 
> The date of announcement is defined as the date of publication. 
> 
> 
> If "Forwarded Date" is changed to "Publication Date", then these items should also be updated:
> 
> Current:
> A.2.2.1. Processing times per document are from Receipt Date to Forwarded Date in total business days.
> 
> A.2.2.2. While the overall goal for document publication is 30 business days (6 weeks) from Receipt Date to Forwarded Date, the times measured in the defined Service Levels are times in RPC state.
> 
> 
> 6)  We suggest removing the first sentence of A.2.2.4 because it is redundant with earlier text and is not as clear as A.2.2.2, which can be summarized as: 
> 
> - Overall goal: time in all states (RFC-Editor-controlled states + 3rd party states) < 6 weeks
> - Actually measured for SLA: time in RFC-Editor-controlled states
> 
> Note that we also recommend changing "RPC state" to "RFC-Editor-controlled states" throughout for clarity.  Alternately, we suggest that "RPC State" be defined as special term. 
> 
> 
> Publisher
> ---------
> 
> 7) In our understanding of the figure, the Publisher function provides access to the post-publication data, but the RPC would actually make any changes to post-publication data.  So, it seems inaccurate to include the Publisher is 'responsible for [...] post-publication data'.  Therefore, we suggest the following update:
> 
> Current:
> The RFC Publisher function is described in RFC 6635 and is responsible for the storage and post-publication data for RFCs, access to the website, access to the errata reports, search tools and indexes, the archive of documents, and all backups and failover processes.
> 
> Suggested:
> The RFC Publisher function is described in RFC 6635 and is responsible for the storage of and access to the website, errata reports, search tools and indexes, the archive of documents, and all backups and failover processes.
> 
> 
> 8) As mentioned in item 3 above, we believe that the action of publishing documents, and therefore the publication processes, are the responsibility of the RPC.  With that in mind, we suggest the following update to the Overview:
> 
> Current:
> The Publisher will accept, store and publish documents from the RFC Production Center and
> other material as determined by the RSE.  The RSE may authorize other entities to submit
> documents directly for publication, but those documents are published on the authority of the
> RSE.  Changes to the publication process and public-facing tools will be made under the advice
> and approval of the RSE.
> 
> Suggested:
> The Publisher will accept and store documents from the RFC Production Center and other material as determined by the RSE.  
> 
> We suggest that the remainder of the text be removed.  While the Publisher houses the tools used by the various RFC Editor components, it is the various components that have the staff to suggest and implement changes to the publication process and tools.
> 
> Also, it is not clear to us what is meant by "other entities to submit documents directly for publication".  Does this refer to web content or perhaps I-Ds that are to be published without being edited?  Both of these cases seem to fall into the RPC SoW, as the RPC is responsible for content on the website, and even if an I-D is to be published without changes, it would need to be updated to conform with current format and boilerplate standards.  Are there other cases in which this "directly for publication" may apply?
> 
> 
> 9) To make it clear that the RPC updates various data, and the Publisher simply makes it available on a server, we suggest changing these instances of "publish" and "post" to "make available" as follows:
> 
> Current:
> RFCs are published on the Publisher’s website. This site includes one or more indexes with hyperlinked access to published documents as well as a convenient search engine.
> 
> Suggested:
> RFCs are made available on the Publisher’s website. This site includes one or more indexes with hyperlinked access to published documents as well as a convenient search engine.
> 
> (Note: SM also suggested making "Publisher's website" be "RFC Editor website")
> 
> 
> Current:
> 1.2.5.     post Web content as provided by the RSE, ISE, and/or the RFC Production Center,
> 
> We suggest deleting Section 1.2.5 from the Publisher SoW or updating it to read:
>       1.2.5.     make available Web content as provided by the RSE, ISE, and/or the RFC Production Center,
> 
> 
> Current: 
> 3.1.1.  Publish state information for each document in the publication process.
> 
> Suggested: 
> 3.1.1.  State information for each document in the publication process.
> 
> 
> 10) With the understanding that the RPC is responsible for creating and maintaining the web content (which presumably includes organizing the web content), and the Publisher for serving the content, we suggest this item be altered as follows. (Also: second sentence deleted because already covered in 1.2.6.)
> 
> Current:
> 1.2.7.     provide continual incremental improvements, including regularly redesigning web page trees to respond to common usage patterns.  However, stable identifiers must be maintained for the RFCs, archives, Errata, indices and other items.
> 
> Suggested:
> 1.2.7.  provide data about the website usage patterns so that the maintainers of the web content can organize it accordingly.
> 
> 
> 11) We believe the following item should be updated because an address should be provided to reach the Publisher (and this same address is used numerous times in Appendix 1 for items for which the Publisher is responsible) and because the RPC should not be a middleman in cases of server failure, etc. 
> 
> Current: 
> 1.4. Customer Support Services. Messages sent to certain conventional addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall automatically be delivered to the RFC Production Center
> 
> Suggested: 
> 1.4. Customer Support Services. Messages sent to certain conventional addresses as defined by the RSE, such as webmaster@rfc-editor.org, shall be coordinated with the RPC as appropriate.
> 
> 
> 12) We question whether integration is really a publisher task.  The RPC has a programmer, so it seems the RPC would be responsible for the programming aspects and the Publisher would be responsible for ensuring the right access/security for integration. 
> 
> Current:
> 3.1.2.     Integrate Production Center state information with the IETF tools or such other tool sets as directed by the RSE to provide end-to-end status tracking of documents 
> 
> Perhaps Section 3.1.2 should be deleted, as Section 2.3.2 indicates that the Publisher should provide appropriate access for integration.
> 
> 
> 13) We suggest removing item 3.1.3, because it seems to be covered by providing state information, as described in Section 3.1.1.
> 
> Current:
> 3.1.3.     Provide external visibility regarding when a document is in an extended waiting period, the token-holder and circumstances of the wait.
> 
> 
> 14) While the Publisher may participate in discussions about the technical support systems required to address policy changes, we do not believe the Publisher needs to be involved in discussion regarding all publication policy changes.  Therefore, we suggest the following update:
> 
> Current:
> 6.1.  Participate in the discussions of the technical publication process with the RSE for policy changes.
> 
> Suggested:
> 6.1.  Participate in policy discussions about technical support of the publication process. 
> 
> 
> 15) It is not clear to us that the Publisher enforces RFC Series consistency, as the Publisher is responsible for making the files available and maintaining the archives.
> 
> Current: 
> 7.  Accountability
> 
> The Publisher is primarily responsible to the RSE as regards to RFC Series consistency.
> 
> Perhaps this should be updated as:
> 7.  Accountability
> 
> The Publisher is primarily responsible to the RSE regarding technical support and hosting of the RFC Series. 
> 
> 
> 15) The Work Standards are listed in "Exhibit B", but there is no "Exhibit A" - is some text missing, or should Exhibit B be Exhibit A?
> 
> 
> On Aug 16, 2013, at 11:47 AM, Ray Pelletier wrote:
> 
>> All;
>>
>> Are there any more comments on the SOWs?
>>
>> This item will be on the IAOC agenda for its call on 22 August.
>>
>> Ray
>>
>> On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:
>>
>>> The RFC Series Editor (RSE) is proposing changes to the Statements of Work (SOW) for the RFC 
>>> Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive community input prior to 
>>> negotiating the proposed changes with the contractor.  Community input will be discussed with the RSE 
>>> prior to negotiations and reviewed by the IAOC.
>>>
>>> In forwarding the proposed Statements of Work the RSE said:  "The changes seek to make the SoWs 
>>> more current [implementing RFC 6635] and specific, correcting the issues of "multiple masters" 
>>> directing the RPC and Publisher, as well as preparing the way for a more significant revision to the SoWs
>>> when the RFC Format changes are operationalized.  The SoWs have also been reviewed and supported 
>>> by the RSOC [RFC Series Oversight Committee].  We consider the changes within the SoWs critical to the 
>>> clear function of the RPC and Publisher, but suggest that the changes do not imply a significant change 
>>> in responsibility for the RPC or Publisher."
>>>
>>> The proposed SOWs, the current SOWs and a diff file for each can be found here under Community 
>>> Review: <http://iaoc.ietf.org/rfps.html>
>>>
>>> We appreciate the community's input and look forward to hearing from you.  
>>>
>>> Thanks
>>>
>>> Ray Pelletier
>>> IAD
>>
> 
> 

From hgs@cs.columbia.edu  Fri Aug 16 13:42:32 2013
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF4611E822A for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 13:42:32 -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 aR3WN5xQiIEZ for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 13:42:26 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id 700C711E8212 for <ietf@ietf.org>; Fri, 16 Aug 2013 13:42:26 -0700 (PDT)
Received: from ice.cs.columbia.edu (ice.cs.columbia.edu [128.59.18.177]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r7GKgOfe010446 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 16 Aug 2013 16:42:24 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com>
Date: Fri, 16 Aug 2013 16:42:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A319344-395C-46E3-8F39-8052992A3F17@cs.columbia.edu>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
X-Mailer: Apple Mail (2.1508)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: John C Klensin <john-ietf@jck.com>, carlos@lacnic.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 20:42:32 -0000

We already have a version of "self-pay", namely the very low student =
rate. For that rate, you are supposed to show student ID (not sure how =
and whether this is enforced), so it's not quite the same, but it's a =
"means-based" test, as well as an attempt to increase the diversity of =
participants. Nearly every scientific conference has versions of =
differentiated pricing - special rates for authors, attendees from =
low-income countries, students, society members (i.e., likely repeat =
attendees), ... In those venues, the general rule of thumb for =
organizers is that even the lowest priced category pays for the variable =
costs, and the fixed costs are borne by those more able to pay.

We also have the early-registration rate - thus, late and on-site =
registrations "subsidize" the early bird moochers.

We presumably want to encourage building a community, and that includes =
making it possible for people to attend who might not otherwise be able =
to. Our objective is not one-time revenue optimization. Many individuals =
switch back-and-forth between traveling on their own dime and on =
corporate tabs, and we want to encourage continued engagement, if only =
to increase our supply of Nomcom-eligibles.

Thus, I think this is worth exploring, as an experiment, just like we =
started the day-pass experiment a number of years ago.

Henning

> I'm not talking about posting this info on web, nor a "full range of =
potential".  We already have multiple reg-fee categories; I'm talking =
about adding *one* more.  I don't know who in the "leadership" can see a =
list of what rates people paid - if we need to constrain that, that's a =
solvable problem.  It's not the sky falling.
>=20
> Regardless, the same argument can be made for charging remote =
participants to "donate" 0-100% or whatever.
>=20
> -hadriel
>=20
>=20


From ben@nostrum.com  Fri Aug 16 14:13:46 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC65B11E8159; Fri, 16 Aug 2013 14:13: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, 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 7ZLx2AYDsc0F; Fri, 16 Aug 2013 14:13:46 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF2311E8158; Fri, 16 Aug 2013 14:13:46 -0700 (PDT)
Received: from [172.20.10.7] (mobile-166-147-071-199.mycingular.net [166.147.71.199]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7GLDbB9039117 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Aug 2013 16:13:38 -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-karp-ops-model-07
Date: Fri, 16 Aug 2013 16:13:32 -0500
Message-Id: <F0728D4E-4DEA-47B4-BA75-CCDB9C562924@nostrum.com>
To: draft-ietf-karp-ops-model.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 166.147.71.199 is authenticated by a trusted mechanism)
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 21:13:47 -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-karp-ops-model-07.txt
Reviewer: Ben Campbell
Review Date: 2013-08-16
IETF LC End Date: 2013-08-18
IESG Telechat date:=20

Summary: This draft is almost ready for publication as an informational =
RFC. I have a few clarity related comments that might be worth =
considering prior to publication.

Major issues:

None.


Minor issues:

-- This abstract claims that this draft is a discussion of issues. =46rom =
that perspective, I don't think the use of 2119 language is appropriate. =
There are some specific areas (mentioned below) where 2119 language is =
used in imprecise ways, and may do harm to the reader's understanding. =
There are other uses that may be more reasonable. But I think the draft =
would be better off dispensing with 2119 language altogether.

-- Section 3, paragraph 4:

This seems like a place where descriptive language would be better than =
2119 language. In particular, "and so on" leaves things too open ended =
and imprecise. Also, the use of 2119 language in an example seems a bit =
off.

-- section 3.1, last paragraph:

I'm not sure what guidance is intended in this paragraph. It offers an =
example, then refutes it. Are there better examples to offer? Is the =
point that one shouldn't make such checks?

-- section 3.2, paragraph 2:

What distinguishes SHOULD from "desirable" in this context? That is, why =
use 2119 language for one and not the other?

-- section 3.2, last paragraph: "Implementations SHOULD permit a =
configuration in which if no unexpired key is available, existing =
security associations continue using the expired key with which they =
were established."

This may need further guidance. For example, it seems risky to do this =
silently.

-- section 3.3, last paragraph: "... then there is complexity in key =
management protocols."

Can you elaborate? Too much complexity? Are there key management systems =
that are not complex?

-- section 4, 2nd to last paragraph:

Seems like other disadvantages are worth mentioning. For example, the =
potential impact of a compromised CA.

-- 4.1:

I understand why one might choose not to include a real-world example =
here, but is there something that can be referenced?

-- 4.4, 2nd paragraph: "... it will be critical to make sure that they =
are not required during routine operation or a cold-start of a network."

Can you elaborate on why?


Nits/editorial comments:

Abstract: Might be worth mentioning KARP and how this draft fits with =
others.

-- Section 1, paragraph 1: Please expand KARP on first mention.

-- Section 1, paragraph 3: Missing punctuation.

-- section 3:=20
The text seems to rather abruptly start talking about key considered =
actions with little background. A quick summary of how these keys re =
used would be helpful.

-- section 3, paragraph 2: "Each OSPF link needs to use the same =
authentication configuration, ..."

Same configuration as what? The sentence appears to say keys must be the =
same among links but can be different.

-- section 3.2, first 2 paragraphs:

I'm not sure how a configuration management system and a configuration =
interface differ for the purposes of this discussion.

-- 4.1, paragraph 4: "Preshared keys that are used via automatic key =
management have not been specified for KARP."

I'm not sure what's intended here--if they are not specified why does =
the paragraph go on to talk about them?

-- 4.4, 1st paragraph: "... like RADIUS or directories."

Is there a word missing?=20

-- 5, bullet list of management objects:

There may be management objects implied by the second and third bullets, =
but they are not mentioned as such. Can you explicitly state them? For =
example, in bullet 2 is the "peer" the object being discussed? Or is it =
the "name or key". In bullet 3, is "group" the managed object, rather =
than "routing protocol"?

-- 5, paragraphs 7 and 8:

s/what/which  (two occurrences)
=20


From kaduk@mit.edu  Fri Aug 16 14:35:19 2013
Return-Path: <kaduk@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 B283621F9A1E for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 14:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[AWL=1.610,  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 vZYLU2uykDEy for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 14:35:13 -0700 (PDT)
Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) by ietfa.amsl.com (Postfix) with ESMTP id 29EA121F99EF for <ietf@ietf.org>; Fri, 16 Aug 2013 14:35:12 -0700 (PDT)
X-AuditID: 12074423-b7f168e00000095a-96-520e9b1013a0
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 9E.F5.02394.01B9E025; Fri, 16 Aug 2013 17:35:12 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r7GLZAIF025836 for <ietf@ietf.org>; Fri, 16 Aug 2013 17:35:11 -0400
Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r7GLZ6HD031228 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 16 Aug 2013 17:35:10 -0400
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r7GLZ6HI018076; Fri, 16 Aug 2013 17:35:06 -0400 (EDT)
Date: Fri, 16 Aug 2013 17:35:05 -0400 (EDT)
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: ietf@ietf.org
Subject: Anyone having trouble submitting I-Ds?
Message-ID: <alpine.GSO.1.10.1308161726500.24720@multics.mit.edu>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHIsWRmVeSWpSXmKPExsUixCmqrSswmy/I4MQuQYtnG+ezODB6LFny kymAMYrLJiU1J7MstUjfLoErY97UiewFd5gq9m56xtLAOI2pi5GDQ0LAROL2HvEuRk4gU0zi wr31bF2MXBxCAvsYJRb09DJBOEcZJbr3XodyrjFJ9D16BeU0MEo0rjjADNLPIqAtMb9zORuI zSagIjHzzUY2kBUiAoISBx9bgoSFBfQlNs/5xQRi8wo4Srx494odxBYV0JFYvX8KC0RcUOLk zCdgNrOApcS/tb9YJzDyzUKSmoUktYCRaRWjbEpulW5uYmZOcWqybnFyYl5eapGumV5uZole akrpJkZQMLG7KO9g/HNQ6RCjAAejEg+vRQRfkBBrYllxZe4hRkkOJiVR3q9TgUJ8SfkplRmJ xRnxRaU5qcWHGCU4mJVEeP27gHK8KYmVValF+TApaQ4WJXHeZ0/PBgoJpCeWpGanphakFsFk ZTg4lCR4j80EahQsSk1PrUjLzClBSDNxcIIM5wEaPgGkhre4IDG3ODMdIn+KUVFKnPcSSEIA JJFRmgfXC4v2V4ziQK8I884AqeIBJgq47ldAg5mABk86wwsyuCQRISXVwMgRopedaR2SatST POPWjoUZj+McVi1f9/VL6eqkKb2VSgvPnr66ZMXklbe2sao3yZWHnJp70GapQFrY6118bsvO f9A2t++VVPz4nX+5Ungco/exopMlmzX+B+vZRK15r/uuuur573qlo6wnH/YIqzxpkLdQ2Mqy 6LycGdMX3oOZ13Xtjvtw9iixFGckGmoxFxUnAgBn0aXd0QIAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 21:35:19 -0000

My web submission told me "Your submission is pending email 
authentication. An email has been sent you with instructions." more than 
an hour ago, but I haven't seen such a mail.

I sent a note to internet-drafts@ mentioning my experience, but wanted to 
check if anyone else was seeing this behavior.

-Ben Kaduk
MIT Kerberos Consortium

From adrian@olddog.co.uk  Fri Aug 16 14:47:41 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D0011E8194; Fri, 16 Aug 2013 14:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level: 
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=-0.049, 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 4jW3ph-d2P3y; Fri, 16 Aug 2013 14:47:36 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 403A811E818F; Fri, 16 Aug 2013 14:47:34 -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 r7GLlXk8008036;  Fri, 16 Aug 2013 22:47:33 +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 r7GLlSdR007999 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Aug 2013 22:47:30 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ray Pelletier'" <rpelletier@isoc.org>, <ietf@ietf.org>
Subject: RE: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Date: Fri, 16 Aug 2013 22:47:25 +0100
Message-ID: <02df01ce9aca$35452bc0$9fcf8340$@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: Ac6ayYuJxnYNgDfoSgmm0qJczoXasw==
Content-Language: en-gb
Cc: wgchairs@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org, iaoc@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, 16 Aug 2013 21:47:41 -0000

Hi Ray,

Thanks for the reminder.

Meta-nit
The document seems unsure whether to say "Internet Draft" or "Internet-Draft".

---

Nits:
Para 2 
> The RPC is one of the distinct components of the RFC Editor. The primary
> responsibility for the RPC is to edit approved Internet Drafts to a consistent
> high level of quality as described by the RFC Style Manual.

1. I don't believe the RPC edits Internet Drafts. The purpose, it seems to me,
is to edit the text of Internet Drafts to create RFCs.
It would be correct to say "edits RFCs", but I can see people's toes curling. 
So say "exit the text of approved Internet Drafts".

2. s/consistent/consistently/

---

Nit:
1.1.1
What is "formal grammar" and how does it differ from "grammar"?

---

1.1.1

> Editing
> shall be accomplished in accordance with the current 'RFC Style Manual'
> maintained by the RSE . The Style Manual specification now in use will be
> used by the RPC until replaced.

I can see what is being attempted here, but it hasn't achieved it!
I think you want

The RSE maintains the 'RFC Style Manual'. The RPC shall edit in accordance with
the version of the RFC Style Manual current at the time of editing.

---

1.1.2

> Maintain a tracking system for edits, and ensure that changes are signed
> off by all authors and that any technical changes are approved by an
> authorized stream representative, except when exceptions are requested by
> the relevant stream and approved by the RSE.

"except where exceptions" is clumsy, but there is a bigger problem in that there
is an implication in the way that this is written that technical changes can be
made without sign-off by a representative of the stream if somehow requested by
the stream. I think that what was being attempted was the ability to handle
absent authors (e.g. during AUTH-48).  I suggest...

Maintain a tracking system for edits, and ensure that changes are signed-off by
all authors except when the need for sign-off is waived by an authorized
representative of the relevant stream and approved by the RSE. Also ensure that
that any technical changes are approved by an authorized representative of the
relevant stream.

---

1.2
What is the "IETF standards stream"?
Text should maybe read:
For standards track documents in the IETF stream

---

Nits
1.3
> The RPC should validate the syntax of sections of documents containing formal
> languages. In particular ASN.1 (and particularly MIBs and MIB-related
details),

s/languages/language/
s/particular/particular,/
s/MIBs/MIB modules/

---

1.5
While it is much tidier, the text "the relevant individuals" provides no clear
guidance to the RPC. How is the RPC supposed to know who constitutes a relevant
individual in order to allow or disallow their requested change?

---

1.10
I can see why "At the discretion of the RSE" would apply to 1.10.2.
It seems a bit harsh to apply it to 1.10.1. Can the RSE really tell the RPC to
not participate in these discussions?

---

Isn't 6.1.1 now in the Style Guide and covered by 9.3?

---

Nit
9.1 appears to have too many "when requested"

---

9.2
"when requested" and "regular" seem to be in conflict.

---

9.3.1

Do you mean "RFC Publisher web site" or "RFC Editor website"
cf. section 5 and 10.3

---

Nit
"authors" appears in 10.4.1.2 and 10.4.1.3

---

10.5.1
"continuously" or "continually"?

---

10.6
IANAL
This text appears to say that the RPC must take direction from the IAOC if it
receives a subpoena.
I am surprised that this can be placed in a SOW that will form the basis of a
contract.

---

Cheers,
Adrian



> -----Original Message-----
> From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of Ray
> Pelletier
> Sent: 16 August 2013 19:48
> To: ietf@ietf.org
> Cc: wgchairs@ietf.org; iaoc@ietf.org; rfc-interest@rfc-editor.org;
iab@iab.org;
> iesg@ietf.org; IETF Announcement List
> Subject: Re: Community Input Sought on SOWs for RFC Production Center and
> RFC Publisher
> 
> All;
> 
> Are there any more comments on the SOWs?
> 
> This item will be on the IAOC agenda for its call on 22 August.
> 
> Ray
> 
> On Aug 12, 2013, at 5:54 PM, IETF Administrative Director wrote:
> 
> > The RFC Series Editor (RSE) is proposing changes to the Statements of Work
> (SOW) for the RFC
> > Production Center (RPC) and the RFC Publisher.  The IAOC wants to receive
> community input prior to
> > negotiating the proposed changes with the contractor.  Community input will
> be discussed with the RSE
> > prior to negotiations and reviewed by the IAOC.
> >
> > In forwarding the proposed Statements of Work the RSE said:  "The changes
> seek to make the SoWs
> > more current [implementing RFC 6635] and specific, correcting the issues of
> "multiple masters"
> > directing the RPC and Publisher, as well as preparing the way for a more
> significant revision to the SoWs
> > when the RFC Format changes are operationalized.  The SoWs have also been
> reviewed and supported
> > by the RSOC [RFC Series Oversight Committee].  We consider the changes
> within the SoWs critical to the
> > clear function of the RPC and Publisher, but suggest that the changes do not
> imply a significant change
> > in responsibility for the RPC or Publisher."
> >
> > The proposed SOWs, the current SOWs and a diff file for each can be found
> here under Community
> > Review: <http://iaoc.ietf.org/rfps.html>
> >
> > We appreciate the community's input and look forward to hearing from you.
> >
> > Thanks
> >
> > Ray Pelletier
> > IAD


From hildjj@cursive.net  Fri Aug 16 14:58:47 2013
Return-Path: <hildjj@cursive.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B545811E80EA for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 14:58:46 -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 barowS6-uz6T for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 14:58:45 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id A2C6421F9DCE for <ietf@ietf.org>; Fri, 16 Aug 2013 14:58:45 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up15so2459811pbc.40 for <ietf@ietf.org>; Fri, 16 Aug 2013 14:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :in-reply-to:mime-version:content-type:content-transfer-encoding; bh=IvaWfML1CmM+5TEjkLDAAfDyuyGS3+8MZP08qyNKTY0=; b=ia9c0Jt5vOGISvCRdpO1eUoUVLOcakxSNv7C9JyEbLC2ANjaW90LxC25XRZfro1E3i EniQcClc+INaoCXofM6E2gblGdvbflwWBAtPEx6DSr6TMFlcdWtLhl8XfoQ3UFvB6Np8 ie6608/pTGTsU1iqskG+HPyUT7DBctzwXSgk8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=IvaWfML1CmM+5TEjkLDAAfDyuyGS3+8MZP08qyNKTY0=; b=jOMiwJdeCZcSFRdkLpockY2g9/Uxes+iGsjdyI9OJaGXVnrJCKmM8hl1PXFxyWOpAi FB8Pyku8rhm4cIKVeNv90nMg+zMKpnXdF5ea2VU+bdIdp/tnYKmLwd2czP38AgSentww RWjWL4UF0R9hAPkCs0RM2jUoHDvMmRGLvXsrE7p6MYipaGTOnE8rZBSgSRl/OP7RAtZ7 RivoNGITkMPtmYcdbMs+ZpBfbEZKkAHpxNtG65iuXrvuDU/MWxkhV9+IDWhE/5JjvysO rZDn9LWZTOsmd/zTGuLdMdYAB6kmudHFl8HBGkWPvltPqH+qdNGNPwa9grb/rUIA3tIH vnJg==
X-Gm-Message-State: ALoCoQnE81guK3rWpRzP478Z9ApsZY/Be61iQpco4/NhTvqpH+RNnBC5FYwRHh2Ca2pPrLl9ECkc
X-Received: by 10.68.196.167 with SMTP id in7mr3625125pbc.127.1376690325372; Fri, 16 Aug 2013 14:58:45 -0700 (PDT)
Received: from [10.129.24.242] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPSA id w8sm5512391paj.4.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 16 Aug 2013 14:58:43 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Fri, 16 Aug 2013 15:58:32 -0600
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Joe Hildebrand <hildjj@cursive.net>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <CE33F83A.15E0E%joe@cursive.net>
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
In-Reply-To: <520D2B60.3000301@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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, 16 Aug 2013 21:58:47 -0000

On 8/15/13 1:26 PM, "Yaron Sheffer" <yaronf.ietf@gmail.com> wrote:

>> One of the reasons why I like the CBOR tag applied to a byte stream is
>> that
>> it can be used to skip parsing on entire sections (no matter their
>> underlying types) in processors that don't need to understand that
>>section.
>>
>
>I suppose you mean you don't understand the section at a semantic level
>(e.g. you don't understand the map "section-7") but you do need to parse
>every last data item in the section before you know its byte length. So
>at a syntactic level you don't skip anything.

Example:

{"to": "you", "from": "me", "content": 24(h'a26161016162820203')}

If I'm just routing this based on the "to" address, I don't need to parse
the
"content" value.  If I'm the end recipient, I can either put my parser
into a 
mode that parses into CBOR (tag 24) blocks, or I can feed the byte string
I 
get for "content" from a generic parser back into that same parser.
Either 
way, I find out that the "content" is:

{"a": 1, "b": [2, 3]}


-- 
Joe Hildebrand





From mbaugher@cisco.com  Fri Aug 16 14:59:26 2013
Return-Path: <mbaugher@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 C533311E817E for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 14:59:26 -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 m4Bg-Daz6fQn for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 14:59:21 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 459C411E81A3 for <ietf@ietf.org>; Fri, 16 Aug 2013 14:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2132; q=dns/txt; s=iport; t=1376690359; x=1377899959; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=wG+TCXOoalgSfpWfOFZaRzyZu46ETCD4GYN9M4Hjcfc=; b=iT9QosHKq8ZqS3aK2JH5w1ZYsR6dOAoRNiSijWxhh77OfTRawykaEwkR bSBP9AwNE5ML3FYLumS5OkYBkpE2389X/EUItDaSiCrR6jeYGQ0s9Eckf Gt52k7S2yh5D6tmJuosYEibcxL2EgidI9qNzpsG5o2zPY3PAAdAuNA3Po 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFADigDlKtJXG//2dsb2JhbABbDoJ4gQa/IIErFnSCJAEBAQMBOi4RBQsCAQgOFBQQMiUCBA4FCAyHdga5Q5AdAjEHgxt3A6k5gl0/gio
X-IronPort-AV: E=Sophos;i="4.89,897,1367971200"; d="scan'208";a="248307682"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 16 Aug 2013 21:59:11 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r7GLxBbW007574 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 16 Aug 2013 21:59:11 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.191]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Fri, 16 Aug 2013 16:59:11 -0500
From: "Mark Baugher (mbaugher)" <mbaugher@cisco.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: Charging remote participants
Thread-Topic: Charging remote participants
Thread-Index: AQHOmoIdra+hzITndUa0dQzskTy4RZmYKnUAgAAV6YCAABPCAIAAHdOAgAAfdoCAAA+bAIAAFXUA
Date: Fri, 16 Aug 2013 21:59:10 +0000
Message-ID: <9C2FF8548CD17F4AB32FC8B311470DFA152D7285@xmb-rcd-x10.cisco.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com> <8A319344-395C-46E3-8F39-8052992A3F17@cs.columbia.edu>
In-Reply-To: <8A319344-395C-46E3-8F39-8052992A3F17@cs.columbia.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.24.22]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EB4ED45A967B1C439E3CBA8E96B5A1D0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John C Klensin <john-ietf@jck.com>, "<carlos@lacnic.net>" <carlos@lacnic.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 21:59:26 -0000

On Aug 16, 2013, at 1:42 PM, Henning Schulzrinne <hgs@cs.columbia.edu>
 wrote:

> We already have a version of "self-pay", namely the very low student rate=
. For that rate, you are supposed to show student ID (not sure how and whet=
her this is enforced), so it's not quite the same, but it's a "means-based"=
 test, as well as an attempt to increase the diversity of participants. Nea=
rly every scientific conference has versions of differentiated pricing - sp=
ecial rates for authors, attendees from low-income countries, students, soc=
iety members (i.e., likely repeat attendees), ... In those venues, the gene=
ral rule of thumb for organizers is that even the lowest priced category pa=
ys for the variable costs, and the fixed costs are borne by those more able=
 to pay.
>=20
> We also have the early-registration rate - thus, late and on-site registr=
ations "subsidize" the early bird moochers.
>=20
> We presumably want to encourage building a community, and that includes m=
aking it possible for people to attend who might not otherwise be able to. =
Our objective is not one-time revenue optimization. Many individuals switch=
 back-and-forth between traveling on their own dime and on corporate tabs, =
and we want to encourage continued engagement, if only to increase our supp=
ly of Nomcom-eligibles.
>=20
> Thus, I think this is worth exploring, as an experiment, just like we sta=
rted the day-pass experiment a number of years ago.

I don't know what "this" refers to in the above sentence, but I agree with =
everything else in your note.

Mark
>=20
> Henning
>=20
>> I'm not talking about posting this info on web, nor a "full range of pot=
ential".  We already have multiple reg-fee categories; I'm talking about ad=
ding *one* more.  I don't know who in the "leadership" can see a list of wh=
at rates people paid - if we need to constrain that, that's a solvable prob=
lem.  It's not the sky falling.
>>=20
>> Regardless, the same argument can be made for charging remote participan=
ts to "donate" 0-100% or whatever.
>>=20
>> -hadriel
>>=20
>>=20
>=20


From ietfdbh@comcast.net  Fri Aug 16 15:33:48 2013
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 1BDCC11E81AC for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 15:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  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 EeZrHQAChXqP for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 15:33:42 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 1D80A11E81A7 for <ietf@ietf.org>; Fri, 16 Aug 2013 15:33:41 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta05.westchester.pa.mail.comcast.net with comcast id DWk81m00517dt5G55aZhjc; Fri, 16 Aug 2013 22:33:41 +0000
Received: from [10.59.1.23] ([67.189.237.137]) by omta13.westchester.pa.mail.comcast.net with comcast id DaZa1m0012yZEBF3ZaZaUB; Fri, 16 Aug 2013 22:33:41 +0000
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Fri, 16 Aug 2013 18:33:32 -0400
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: David Harrington <ietfdbh@comcast.net>
To: <ietf@ietf.org>, Ray Pelletier <rpelletier@isoc.org>
Message-ID: <CE341C01.2FDEA%ietfdbh@comcast.net>
Thread-Topic: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
In-Reply-To: <3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1376692421; bh=toBYXwCb7Q4JnT3QiY0eN8ItNvgh6emjwXp6aFkrmn8=; h=Received:Received:Date:Subject:From:To:Message-ID:Mime-version: Content-type; b=GR96n1dmQByuEFUy1HVPBEp4+uO0GeedF/JTDROn4ibpuII2RrXAZ01TcTQkjn54Z XJI/rxZCakdnJP8FJT3/4r0n/C0bd28ak7RpbwE/uHg/aGUjxj6JJq21/QhLFkeSGg feTI9bvsoS0gJ8UrJR7UPI60MU+Um6nVxckcMnuuEh3BxyMS/g2myBP/anRL3pGJ+T DtcgJbulNgRGuZjN7InXwr7VcvMLomNx84KLi2D4OvRfzVZ1MRv/AqhiE8IqxLzhUX xOeIfe6O0cLfkbFAuD1GS/SH/e8IyZWbgI9jcT4rT25QGLBg9xpsJhkN++MCGNMT1b +roRz9LMyTe0A==
Cc: wgchairs@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 22:33:48 -0000

Hi,

A few nits regrading MIB module checking...



On 8/16/13 4:16 PM, "Sandy Ginoza" <sginoza@amsl.com> wrote:
>
>
>
>2) In the following, we suggest that "ASN.1 (and particularly MIBs and
>MIB-related details)" be updated to reflect "MIBs".  Although MIB modules
>are written using a subset of ASN.1, the RPC does not check all ASN.1, we
>only check MIBs.  This change will reflect what is done in practice.  If
>the intent is to actually require the RPC to check all ASN.1, please let
>us know and we will discuss checking tools with the RSE and IAD.
>
>Current:
>
>1.3.  Validation of formal languages
>
>The RPC should validate the syntax of sections of documents containing
>formal languages.  In particular ASN.1 (and particularly MIBs and
>MIB-related details), YANG, ABNF, and XML should be verified using one or
>more tools as approved by the RSE.
>
S/MIBs/MIB modules/

MIB Modules are written using version 2 of the SMI standard, a formal
language which is an IETF-standardized "adapted subset" of ASN.1-1988.
So MIB validation might be more accurately called SMI validation or SMIv2
validation (but SMIv3 could be done at some future date.)
So s/ASN.1/SMI/ or s/ASN.1/SMIv2/

ASN.1 has moved on since the 1988 subset used for SMI.

There are tools to validate against the more current ASN.1 standard.
I'm not sure how much current ASN.1 is used in IETF documents, but if it
is, then you might want to validate it.
I think there is very little current ASN.1 usage in IETF documents.

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



From john-ietf@jck.com  Fri Aug 16 15:39:40 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C7A11E81AF for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 15:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czhWCYE2mNAM for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 15:39:35 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BB4EA21F9FF9 for <ietf@ietf.org>; Fri, 16 Aug 2013 15:39:08 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VASfh-0009FX-OY; Fri, 16 Aug 2013 18:39:05 -0400
X-Vipre-Scanned: 01B35F52002C3101B3609F-TDI
Date: Fri, 16 Aug 2013 18:39:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Charging remote participants
Message-ID: <81BB6FC23C57D1FFAD7C8AF0@[192.168.1.128]>
In-Reply-To: <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.co m> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.co m> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.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: carlos@lacnic.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 22:39:40 -0000

--On Friday, August 16, 2013 15:46 -0400 Hadriel Kaplan
<hadriel.kaplan@oracle.com> wrote:

> 
> On Aug 16, 2013, at 1:53 PM, John C Klensin
> <john-ietf@jck.com> wrote:
> 
>> (1) As Dave points out, this activity has never been free.
>> The question is only about "who pays".  If any participants
>> have to pay 
>> (or convince their companies to pay) and others, as a matter
>> of categories, do not, that ultimately weakens the process
>> even if, most of the time, those who pay don't expect or get
>> favored treatment.  Having some participants get a "free
>> ride" that really comes at the expense of other participants
>> (and potentially competing organizations) is just not a
>> healthy idea.
> 
> Baloney.  People physically present still have an advantage
> over those remote, no matter how much technology we throw at
> this.  That's why corporations are willing to pay their
> employees to travel to these meetings.  And it's why people
> are willing to pay out-of-pocket for it too, ultimately.  It's
> why people want a day-pass type thing for only attending one
> meeting, instead of sitting at home attending remote. 
> 
> Being there is important, and corporations and people know it.

Sure.  And it is an entirely separate issue, one which I don't
know how to solve (if it can be solved at all).  It is
unsolvable in part because corporations --especially the larger
and more successful ones-- make their decisions about what to
participate in, at what levels, and with whatever choices of
people, for whatever presumably-good business reasons they do
so.  I can, for example, remember one such corporation refusing
to participate in a standards committee that was working on
something that many of us thought was key to their primary
product.  None us knew, then or now, why they made that decision
although their was wide speculation at the time that they
intended to deliberately violate the standard that emerged and
wanted plausible deniability about participation.  Lots of
reasons; lots of circumstances. 

> An audio input model (ie, conference call model) still
> provides plenty of advantage to physical attendees, while also
> providing remote participants a chance to have their say in a
> more emphatic and real-time format.  We're not talking about
> building a telepresence system for all remote participants, or
> using robots as avatars.

IIR, we've tried audio input.  It works really well for
conference-sized meetings (e.g., a dozen or two dozen people
around a table) with a few remote participants.  It works really
well for a larger group (50 or 100 or more) and one or two
remote participants.  I've even co-chaired IETF WG meetings
remotely that way (with a lot of help and sympathy from the
other co-chair or someone else taking an in-room leadership
role).  

But, try it for several remote participants and a large room
full of people, allow for audio delays in both directions, and
about the last thing one needs is a bunch of disembodied voices
coming out of the in-room audio system at times that are not
really coordinated with what is going on in the room.  Now it
can all certainly be made to work: it takes a bit of
coordination on a chat (or equivalent) channel, requests to get
in or out of the queue that are monitored from within the room,
and someone managing those queues along with the mic lines.
But, by that point, many of the disadvantage of audio input
relative to someone reading from Jabber have disappeared and the
other potential problems with audio input -- noise, level
setting, people who are hard to understand even if they are in
the room, and so on-- start to dominate.   Would I prefer audio
input to typing into Jabber under the right conditions?  Sure,
in part because, while I type faster than average it still isn't
fast enough to compensate for the various delays.  But it really
isn't a panacea for any of the significant problems.

>> (2) Trying to figure out exactly what remote participation
>> (equipment, staffing, etc.) will cost the IETF and then trying
>> to assess those costs to the remote participants would be
>> madness for multiple reasons.  [...snip...]
> 
> Yet you're proposing charging remote participants to bear the
> costs.  I'm confused.

I am proposing charging remote participants a portion of the
overhead costs of operating the IETF, _not_ a fee based on the
costs of supporting remote participation.  And, again, I want
them to have the option of deciding how much of it they can
reasonably afford to pay.

>...

best,
   john


From scott@kitterman.com  Fri Aug 16 15:44:10 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C018811E81AF for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 15:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1qlV15qfYIOp for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 15:44:05 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id A13C211E8192 for <ietf@ietf.org>; Fri, 16 Aug 2013 15:44:05 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 82A3D20E40D2; Fri, 16 Aug 2013 18:44:03 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376693043; bh=YHCwtBA4A0SqnfO/Wqmqt0fXNjeY5QWg8E5OYO5x0ek=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eMU+tItIcV+JE6RU4kSWh+/NV860SBt6DunJ0h8tBKo70XDy4fpm5yL4laYnTz0JK /ntfRKdzz9H5XFGIbfZP55ZCyfuekfkZBlchTJjn6rOz67YWYhwxiiOBBLFbMnSfKa FMJIrQGZ5z8cucqfgnvLOR7Tj5uKwhMJqyozYRs8=
Received: from scott-latitude-e6320.localnet (unknown [209.144.63.76]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 39C0820E40A4;  Fri, 16 Aug 2013 18:44:02 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Charging remote participants
Date: Fri, 16 Aug 2013 18:44:02 -0400
Message-ID: <3497332.mkpYaj5s7x@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <81BB6FC23C57D1FFAD7C8AF0@192.168.1.128>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <81BB6FC23C57D1FFAD7C8AF0@192.168.1.128>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 22:44:10 -0000

On Friday, August 16, 2013 18:39:04 John C Klensin wrote:
> --On Friday, August 16, 2013 15:46 -0400 Hadriel Kaplan
> 
> <hadriel.kaplan@oracle.com> wrote:
> > On Aug 16, 2013, at 1:53 PM, John C Klensin
> > 
> > <john-ietf@jck.com> wrote:
> >> (1) As Dave points out, this activity has never been free.
> >> The question is only about "who pays".  If any participants
> >> have to pay
> >> (or convince their companies to pay) and others, as a matter
> >> of categories, do not, that ultimately weakens the process
> >> even if, most of the time, those who pay don't expect or get
> >> favored treatment.  Having some participants get a "free
> >> ride" that really comes at the expense of other participants
> >> (and potentially competing organizations) is just not a
> >> healthy idea.
> > 
> > Baloney.  People physically present still have an advantage
> > over those remote, no matter how much technology we throw at
> > this.  That's why corporations are willing to pay their
> > employees to travel to these meetings.  And it's why people
> > are willing to pay out-of-pocket for it too, ultimately.  It's
> > why people want a day-pass type thing for only attending one
> > meeting, instead of sitting at home attending remote.
> > 
> > Being there is important, and corporations and people know it.
> 
> Sure.  And it is an entirely separate issue, one which I don't
> know how to solve (if it can be solved at all).  It is
> unsolvable in part because corporations --especially the larger
> and more successful ones-- make their decisions about what to
> participate in, at what levels, and with whatever choices of
> people, for whatever presumably-good business reasons they do
> so.  I can, for example, remember one such corporation refusing
> to participate in a standards committee that was working on
> something that many of us thought was key to their primary
> product.  None us knew, then or now, why they made that decision
> although their was wide speculation at the time that they
> intended to deliberately violate the standard that emerged and
> wanted plausible deniability about participation.  Lots of
> reasons; lots of circumstances.
> 
> > An audio input model (ie, conference call model) still
> > provides plenty of advantage to physical attendees, while also
> > providing remote participants a chance to have their say in a
> > more emphatic and real-time format.  We're not talking about
> > building a telepresence system for all remote participants, or
> > using robots as avatars.
> 
> IIR, we've tried audio input.  It works really well for
> conference-sized meetings (e.g., a dozen or two dozen people
> around a table) with a few remote participants.  It works really
> well for a larger group (50 or 100 or more) and one or two
> remote participants.  I've even co-chaired IETF WG meetings
> remotely that way (with a lot of help and sympathy from the
> other co-chair or someone else taking an in-room leadership
> role).
> 
> But, try it for several remote participants and a large room
> full of people, allow for audio delays in both directions, and
> about the last thing one needs is a bunch of disembodied voices
> coming out of the in-room audio system at times that are not
> really coordinated with what is going on in the room.  Now it
> can all certainly be made to work: it takes a bit of
> coordination on a chat (or equivalent) channel, requests to get
> in or out of the queue that are monitored from within the room,
> and someone managing those queues along with the mic lines.
> But, by that point, many of the disadvantage of audio input
> relative to someone reading from Jabber have disappeared and the
> other potential problems with audio input -- noise, level
> setting, people who are hard to understand even if they are in
> the room, and so on-- start to dominate.   Would I prefer audio
> input to typing into Jabber under the right conditions?  Sure,
> in part because, while I type faster than average it still isn't
> fast enough to compensate for the various delays.  But it really
> isn't a panacea for any of the significant problems.
> 
> >> (2) Trying to figure out exactly what remote participation
> >> (equipment, staffing, etc.) will cost the IETF and then trying
> >> to assess those costs to the remote participants would be
> >> madness for multiple reasons.  [...snip...]
> > 
> > Yet you're proposing charging remote participants to bear the
> > costs.  I'm confused.
> 
> I am proposing charging remote participants a portion of the
> overhead costs of operating the IETF, _not_ a fee based on the
> costs of supporting remote participation.  And, again, I want
> them to have the option of deciding how much of it they can
> reasonably afford to pay.

Maybe the IETF should charge for mailing list subscriptions too?

Scott K

From kaduk@mit.edu  Fri Aug 16 16:27:41 2013
Return-Path: <kaduk@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 0C54A11E8150 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 16:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.177
X-Spam-Level: 
X-Spam-Status: No, score=-3.177 tagged_above=-999 required=5 tests=[AWL=0.422,  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 22h21xPtXCQR for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 16:27:29 -0700 (PDT)
Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) by ietfa.amsl.com (Postfix) with ESMTP id 4048911E8138 for <ietf@ietf.org>; Fri, 16 Aug 2013 16:27:29 -0700 (PDT)
X-AuditID: 12074424-b7f228e00000096b-09-520eb5603459
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id EA.5E.02411.065BE025; Fri, 16 Aug 2013 19:27:28 -0400 (EDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r7GNRRs9010200 for <ietf@ietf.org>; Fri, 16 Aug 2013 19:27:28 -0400
Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r7GNRPed032549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 16 Aug 2013 19:27:27 -0400
Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r7GNRPOM004548; Fri, 16 Aug 2013 19:27:25 -0400 (EDT)
Date: Fri, 16 Aug 2013 19:27:24 -0400 (EDT)
From: Benjamin Kaduk <kaduk@MIT.EDU>
To: ietf@ietf.org
Subject: Re: Anyone having trouble submitting I-Ds?
In-Reply-To: <alpine.GSO.1.10.1308161726500.24720@multics.mit.edu>
Message-ID: <alpine.GSO.1.10.1308161925270.24720@multics.mit.edu>
References: <alpine.GSO.1.10.1308161726500.24720@multics.mit.edu>
User-Agent: Alpine 1.10 (GSO 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGIsWRmVeSWpSXmKPExsUixG6nrpuwlS/I4MoUdYtnG+ezODB6LFny kymAMYrLJiU1J7MstUjfLoEr482x5ewFT1krNh+cz9rAeIyli5GTQ0LARKL9yFJGCFtM4sK9 9WxdjFwcQgL7GCV2XG1khXCOMkp8mNHOBOFcY5I4/6gTqqyBUWJ+43dWkH4WAW2Jedd6wOay CahIzHyzEaiIg0NEQFDi4GNLkLCwgLHE95v9YOs4BZwk7u5YzAxSwivgKLHgHFinEJD5bep9 NhBbVEBHYvX+KWBxXqApJ2c+AbOZBSwlzv25zjaBUWAWktQsJKkFjEyrGGVTcqt0cxMzc4pT k3WLkxPz8lKLdM31cjNL9FJTSjcxgoPPRWUHY/MhpUOMAhyMSjy8FhF8QUKsiWXFlbmHGCU5 mJREeU+uBwrxJeWnVGYkFmfEF5XmpBYfYpTgYFYS4Z20BSjHm5JYWZValA+TkuZgURLnffb0 bKCQQHpiSWp2ampBahFMVoaDQ0mCNxikUbAoNT21Ii0zpwQhzcTBCTKcB2h4D9jw4oLE3OLM dIj8KUZFKXHeTJCEAEgiozQPrheWHF4xigO9Isw7B6SKB5hY4LpfAQ1mArn6DC/I4JJEhJRU A6NDKA/D0ScmzC6Xd+eGXk+7dstq8fd1S4QnrMp3FnrMfivwutoSvuPf+XYaVk9om2j25sp6 70kH9i273+bUueIc/z2uLwGb7k1ILLodyX/H8+v88h0uIVGVl74vlZ+or6+2a+4NW/ttt4N4 9myPP/dlrlvsvTf2t+5N051quarfM+bJ6gkT+LatU2Ipzkg01GIuKk4EAFySo9LpAgAA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 23:27:41 -0000

On Fri, 16 Aug 2013, Benjamin Kaduk wrote:

> My web submission told me "Your submission is pending email authentication. 
> An email has been sent you with instructions." more than an hour ago, but I 
> haven't seen such a mail.
>
> I sent a note to internet-drafts@ mentioning my experience, but wanted to 
> check if anyone else was seeing this behavior.

It turns out this was user error -- I was not listed as an author on the 
previous version of the document, even though I did the actual upload for 
that version.  The anti-hijacking feature causes the confirmation email to 
only go to the authors listed on the previous version of the document, so 
mail was not sent to me and things are working as expected.

-Ben

From hadriel.kaplan@oracle.com  Fri Aug 16 17:16:46 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD8411E80FF for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 17:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.124
X-Spam-Level: 
X-Spam-Status: No, score=-6.124 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XdB8XjU3hbdn for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 17:16:40 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 070AB11E80D7 for <ietf@ietf.org>; Fri, 16 Aug 2013 17:16:39 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7H0GcTI024089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 17 Aug 2013 00:16:39 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7H0GZhl023809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 00:16:36 GMT
Received: from abhmt106.oracle.com (abhmt106.oracle.com [141.146.116.58]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7H0GZZN009740; Sat, 17 Aug 2013 00:16:35 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 16 Aug 2013 17:16:35 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <81BB6FC23C57D1FFAD7C8AF0@[192.168.1.128]>
Date: Fri, 16 Aug 2013 20:16:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B2490E8-2B14-45FC-8C6A-7FBB725CFFC8@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.co m> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.co m> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com> <81BB6FC23C57D1FFAD7C8AF0@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 00:16:46 -0000

On Aug 16, 2013, at 6:39 PM, John C Klensin <john-ietf@jck.com> wrote:

> IIR, we've tried audio input.  It works really well for
> conference-sized meetings (e.g., a dozen or two dozen people
> around a table) with a few remote participants.  It works really
> well for a larger group (50 or 100 or more) and one or two
> remote participants.  I've even co-chaired IETF WG meetings
> remotely that way (with a lot of help and sympathy from the
> other co-chair or someone else taking an in-room leadership
> role). =20
>=20
> But, try it for several remote participants and a large room
> full of people, allow for audio delays in both directions, and
> about the last thing one needs is a bunch of disembodied voices
> coming out of the in-room audio system at times that are not
> really coordinated with what is going on in the room.  Now it
> can all certainly be made to work: it takes a bit of
> coordination on a chat (or equivalent) channel, requests to get
> in or out of the queue that are monitored from within the room,
> and someone managing those queues along with the mic lines.

Yup, it definitely takes those things.  Been there, done that, got the =
IETF t-shirt. :)

I think we might be able to do it, using the jabber scribes for those =
"coordination" actions.  Maybe.  It depends on the number of remote =
active participants and quality of scribes.  The jabber scribes would =
have to act like the operator-assisting person in big conferences with =
remote participants. (the old "we've got a question from Jane Doe, go =
ahead Jane" type thing)

For the WGs I go to (RAI area mostly), we have good scribes and not a =
large number of remote people who actually participate (as opposed to =
monitor).  We've had some exceptions, but my impression is the things =
the remote people wanted to say in those cases were usually said by =
someone locally anyway so they're more of a +1 thing.  I.e., if there =
are lots of local attendees, you usually get someone saying what you =
were going to say anyway.  Not that someone remote shouldn't say it as =
well, because it does matter if you hear the same thing being repeated.  =
But at least it's not so much "interaction" needed for hearing that.

But yes if there are a dozen remote active participants, and a 100 =
people locally in the room, it's chaos.  It's not chaos because the =
remote participants don't get mic time - it's chaos because they *do* =
get mic time.  The delay in letting them know it's their turn at the =
mic, delay in real-time interaction, the mental switch to "remote mode" =
for local participants, etc., all cause the meeting to slow down... a =
lot.

It's like multiple processes running on one CPU - context switching is =
painful.  We can try to pile up the remote participants to go all at =
once, so that there're fewer context switches.  That's what folks do in =
big conferences: the remote participants are queued up until the local =
ones have finished, and then the remote ones go all at once.  =
Unfortunately that turns it into a Q&A type thing at the end, and not a =
discussion, but with that big an active audience that's probably all it =
could be anyway.



> But, by that point, many of the disadvantage of audio input
> relative to someone reading from Jabber have disappeared and the
> other potential problems with audio input -- noise, level
> setting, people who are hard to understand even if they are in
> the room, and so on-- start to dominate.  =20

Yes, audio quality and volume control and a bunch of related things are =
very important for this to work.  IANAE on that - there are =
professionals who do that stuff for a living.


> Would I prefer audio
> input to typing into Jabber under the right conditions?  Sure,
> in part because, while I type faster than average it still isn't
> fast enough to compensate for the various delays.  But it really
> isn't a panacea for any of the significant problems.

OK, so what are the significant problems?  What have the WGs you've been =
participating in not been doing, that makes you feel like you don't get =
to participate remotely?

-hadriel


From bob.hinden@gmail.com  Fri Aug 16 18:28:44 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F199711E81D7; Fri, 16 Aug 2013 18:28:43 -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 jF7+zhbjVJcT; Fri, 16 Aug 2013 18:28:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3D411E81C5; Fri, 16 Aug 2013 18:28:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: The IAOC <bob.hinden@gmail.com>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IAOC Chair
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130817012843.22517.34222.idtracker@ietfa.amsl.com>
Date: Fri, 16 Aug 2013 18:28:43 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 01:28:44 -0000

I was recently elected as the chair of the Internet Society Board of Truste=
es.   While I plan to complete my current term on the IAOC, I am stepping d=
own as its chair.  I have served on the IAOC since 2007 and was chair since=
 2009.

I am pleased to report that the IAOC has elected Chris Griffiths as the new=
 IAOC chair.  I think Chris will be an excellent chair and that he has my c=
omplete support.

Congratulations to Chris!

The change in IAOC chairs is effective with this email.

Bob Hinden

From hgs@cs.columbia.edu  Fri Aug 16 18:43:48 2013
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8626111E81C5 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 18:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mKkz4JkLKzSP for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 18:43:42 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by ietfa.amsl.com (Postfix) with ESMTP id A2CAC11E81D3 for <ietf@ietf.org>; Fri, 16 Aug 2013 18:43:42 -0700 (PDT)
Received: from upstairs-3.home (pool-96-242-116-6.nwrknj.fios.verizon.net [96.242.116.6]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r7H1hb1C028597 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 16 Aug 2013 21:43:38 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <9C2FF8548CD17F4AB32FC8B311470DFA152D7285@xmb-rcd-x10.cisco.com>
Date: Fri, 16 Aug 2013 21:43:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <58B7ABEC-3648-4873-BB9A-CDA311981E63@cs.columbia.edu>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com> <8A319344-395C-46E3-8F39-8052992A3F17@cs.columbia.edu> <9C2FF8548CD17F4AB32FC8B311470DFA152D7285@xmb-rcd-x10.cisco.com>
To: Mark Baugher (mbaugher) <mbaugher@cisco.com>
X-Mailer: Apple Mail (2.1508)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.7
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 01:43:48 -0000

>>=20
>> Thus, I think this is worth exploring, as an experiment, just like we =
started the day-pass experiment a number of years ago.
>=20
> I don't know what "this" refers to in the above sentence, but I agree =
with everything else in your note.

Offer a "self-pay" rate, as suggested by Hadriel. See how many people =
take it and ask them whether that made a difference in their attendance.

Henning



From paul.hoffman@vpnc.org  Fri Aug 16 18:48:37 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2518611E81D7 for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 18:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.21
X-Spam-Level: 
X-Spam-Status: No, score=-102.21 tagged_above=-999 required=5 tests=[AWL=0.390, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aOiAGdjSktvL for <ietf@ietfa.amsl.com>; Fri, 16 Aug 2013 18:48:36 -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 9409511E81C5 for <ietf@ietf.org>; Fri, 16 Aug 2013 18:48:36 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-185.dsl.dynamic.sonic.net [50.1.98.185]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.5) with ESMTP id r7H1mVui061300 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Aug 2013 18:48:31 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-185.dsl.dynamic.sonic.net [50.1.98.185] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <520D520F.8050104@gmail.com>
Date: Fri, 16 Aug 2013 18:48:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <85C56F28-353C-48F3-82EA-3A3C058A2B4B@vpnc.org>
References: <520D520F.8050104@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
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, 17 Aug 2013 01:48:37 -0000

On Aug 15, 2013, at 3:11 PM, Yaron Sheffer <yaronf.ietf@gmail.com> =
wrote:

> - A parser that looks for duplicates must be able to detect that =
{{"a":1, "b":2}:4, {"b":2, "a":1}:5} does in fact have a duplicate key, =
because the two internal maps (used as keys) are identical. So in =
general, parsers need to canonicalize maps to any depth in order to =
detect duplicates. This is "complex" by any definition of the word.

It does not need to canonicalize, but it does need to reify (or some =
word that means "know what each name means"). This is not additional =
code: the decoder already has that in the semantic processor. It is only =
additional runtime during decoding, and only in protocols/applications =
that use maps as keys.

We could say "you cannot use maps as keys in maps because it is too =
hard", but then the question is where do we draw the line on "too hard". =
Is it "too hard" to use arrays? They might be arrays with arrays in =
them; is that too hard? Instead of the CBOR spec saying "this is too =
hard for you to do", we at some point have to trust the =
protocol/application developer to understand the tradeoffs.

> - Even for an unloved diagnostic notation, you want people to read it =
without resorting to little pieces of paper. So a symbolic =
representation (TAG_URI) is definitely better than numbers.

You keep trying to elevate the diagnostic notation; we keep resisting.

> - I don't understand your reply re: tags when applied to arrays. Is it =
up to the application to decide whether the tag applies to all elements, =
to the first one, to the last 14?

My reply may have been unclear, but the text in -05 should be clearer:

A tag always applies to the item that is directly followed by it. Thus, =
if tag A is followed by tag B which is followed by data item C, tag A =
applies to the result of applying tag B on data item C. That is, a =
tagged item is a data item consisting of a tag and a value. The content =
of the tagged item is the data item (the value) that is being tagged.

> - Regarding error handling and security, I am slightly happier with =
-05, but not by much. For some reason you avoid using 2119 language in =
places where I would expect: parsers SHOULD include a "strict mode". A =
strict mode parser MUST fail when the syntax is broken (sec. 3.3, 3.4, =
and also 3.5). And so forth.

This feels like creep to me, but Carsten wants to add more about strict =
mode in the -06.

> - Unknown tags: you specifically allow decoders (Sec. 3.5) to not =
implement any tags they don't like, and then you specify the behavior of =
the decoder as "do whatever you feel like" (and this is in -05). So a =
sender cannot rely on *any* tag being implemented by the receiver, and =
cannot expect deterministic behavior if any are not. This is a security =
issue IMO, but also an interoperability thing.

In his new wording for strict mode, the decoder will not be able to =
ignore any tag.

--Paul Hoffman=

From yaronf.ietf@gmail.com  Sat Aug 17 01:19:44 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32BF721F9BD5 for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 01:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FudNyzBKDYl7 for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 01:19:42 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 9C1FE21F9BEF for <ietf@ietf.org>; Sat, 17 Aug 2013 01:19:39 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so2340846wes.19 for <ietf@ietf.org>; Sat, 17 Aug 2013 01:19:38 -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=NUykyPrX0z5FUnKvqAPYSNG5LEZ3iuOKVoWUa5OyqYQ=; b=cRc6CROPfZsZzdMD1TI3wZ8xpxyWKiIId/vDyJP9Gt+jqzfYGdrS+KLRKW+Buj14QB mo9kOtOhymOB+EzzNbzj+kAjjKrhfgVWTnJmxBdSsF4ctVb6qHk5DYvIThZLkTrA00WL Y4+tnp9sxSy7+Yaq9L0BL6P21Xtej7WwC1c75CFM4MVZHQ7ccafR0TYJpTSfntuViN/6 U++G1j/tcrU4vggAWtvBx7Gha6VCBYgij4KNzV4qUAXzIwhqsSbtiiwFOMGy0XuT67UQ oQNyUZOAR/PL9xtPtbR+Et6Mkia2xGJU4WyUW70uAy9Nb1vWr+wWLk5CZVJegyFKG8R4 JKEQ==
X-Received: by 10.180.208.45 with SMTP id mb13mr1172771wic.27.1376727578796; Sat, 17 Aug 2013 01:19:38 -0700 (PDT)
Received: from [10.0.0.3] ([109.67.206.7]) by mx.google.com with ESMTPSA id i5sm2149798wiw.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 Aug 2013 01:19:38 -0700 (PDT)
Message-ID: <520F3217.1080909@gmail.com>
Date: Sat, 17 Aug 2013 11:19:35 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <520D520F.8050104@gmail.com> <85C56F28-353C-48F3-82EA-3A3C058A2B4B@vpnc.org>
In-Reply-To: <85C56F28-353C-48F3-82EA-3A3C058A2B4B@vpnc.org>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 17 Aug 2013 08:19:44 -0000

Hi Paul,

please see below.

Thanks,
	Yaron

On 2013-08-17 04:48, Paul Hoffman wrote:
> On Aug 15, 2013, at 3:11 PM, Yaron Sheffer <yaronf.ietf@gmail.com>
> wrote:
>
>> - A parser that looks for duplicates must be able to detect that
>> {{"a":1, "b":2}:4, {"b":2, "a":1}:5} does in fact have a duplicate
>> key, because the two internal maps (used as keys) are identical. So
>> in general, parsers need to canonicalize maps to any depth in order
>> to detect duplicates. This is "complex" by any definition of the
>> word.
>
> It does not need to canonicalize, but it does need to reify (or some
> word that means "know what each name means"). This is not additional
> code: the decoder already has that in the semantic processor. It is
> only additional runtime during decoding, and only in
> protocols/applications that use maps as keys.
>
> We could say "you cannot use maps as keys in maps because it is too
> hard", but then the question is where do we draw the line on "too
> hard". Is it "too hard" to use arrays? They might be arrays with
> arrays in them; is that too hard? Instead of the CBOR spec saying
> "this is too hard for you to do", we at some point have to trust the
> protocol/application developer to understand the tradeoffs.

I don't understand why you think you are shifting the complexity to the
application/protocol. Detecting duplicates is the responsibility of a 
generic decoder (parser?), and any complexity will fall there. As will 
any resultant security vulnerabilities.

In fact you do NOT need to understand "what each name means", you need
precisely a canonical order. Even if we don't like the C word for
historical reasons.

Since it's trivial to emulate complex keys with arrays, I would 
recommend to avoid this whole thing and only allow keys that are simple 
values. And even then you need to define how data items are compared, 
i.e. whether there are duplicates in {1:"a", 1.0:"a", "1":"a"}.

>
>> - Even for an unloved diagnostic notation, you want people to read
>> it without resorting to little pieces of paper. So a symbolic
>> representation (TAG_URI) is definitely better than numbers.
>
> You keep trying to elevate the diagnostic notation; we keep
> resisting.

If it's a diagnostic notation, we want people (not machines) to read it.
People can read symbolic values ("TAG_MIME") much better than numbers
("36").

>
>> - I don't understand your reply re: tags when applied to arrays. Is
>> it up to the application to decide whether the tag applies to all
>> elements, to the first one, to the last 14?
>
> My reply may have been unclear, but the text in -05 should be
> clearer:
>
> A tag always applies to the item that is directly followed by it.
> Thus, if tag A is followed by tag B which is followed by data item C,
> tag A applies to the result of applying tag B on data item C. That
> is, a tagged item is a data item consisting of a tag and a value. The
> content of the tagged item is the data item (the value) that is being
> tagged.

This is indeed good text. I suggest to also add: "A tag followed by an
aggregate data item (map or array) applies to all members of the data item."

[snip]

> --Paul Hoffman
>

From yaronf.ietf@gmail.com  Sat Aug 17 03:58:44 2013
Return-Path: <yaronf.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 863E211E80E6 for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 03:58: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 YY33I1F6uPPG for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 03:58:44 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD8211E80F0 for <ietf@ietf.org>; Sat, 17 Aug 2013 03:58:42 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id hi8so1599999wib.3 for <ietf@ietf.org>; Sat, 17 Aug 2013 03:58:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=5rn2i01r9wMyN5oZ++1byfSZbUlzZpmKmTwZmusTf0M=; b=bObPsq8aaHAgLRkA06iZDoRYOk/JvYF+BE5NRVHxAbq6N5KqhZ2CY+YvdDDz6+G/nm BkkE06EaTc484V+2rmzM8m/8BrKq53AAzqAmnwc3iOCt9P8OqMSK7VBLTV2cDvxfT7Tu VSFAq2XgaVOdgDKuEBngDqZoIQ5RHve7+1mt6ITPHcM4TronT4aIZOm5n/sOFYFJ/iLK qTK+d2uMnxiloJi8jXAkvpY8gJ7lpOIDqzbrAUJbst4Jaq/HcYLHKLe7BfdHbLsTZIuI xt40kpDKgbNJAlbnibZj9Z9hdqSyy5yAdftlLUR+FAZjMOFEcBqAGKAh+WgMttTxV85x 5WmA==
X-Received: by 10.194.201.131 with SMTP id ka3mr1593473wjc.22.1376737119693; Sat, 17 Aug 2013 03:58:39 -0700 (PDT)
Received: from [10.0.0.3] ([109.67.206.7]) by mx.google.com with ESMTPSA id a8sm2521617wie.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 17 Aug 2013 03:58:39 -0700 (PDT)
Message-ID: <520F575D.5070902@gmail.com>
Date: Sat, 17 Aug 2013 13:58:37 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Hildebrand <hildjj@cursive.net>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
References: <CE33F83A.15E0E%joe@cursive.net>
In-Reply-To: <CE33F83A.15E0E%joe@cursive.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
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, 17 Aug 2013 10:58:44 -0000

Got it, thanks for the example.

But tag 24 makes it harder for pedantic security devices to validate 
CBOR, somewhat like an "eval" statement.

Is a "strict mode" decoder required to decode/validate the contents of 
this tag?

And security aside, this usage means that endpoints (sender and 
receiver) work a bit harder, in order to make the life of middleboxes 
easier. This may or may not be the right trade-off, depending on your 
architecture.

Thanks,
	Yaron

On 2013-08-17 00:58, Joe Hildebrand wrote:
> On 8/15/13 1:26 PM, "Yaron Sheffer" <yaronf.ietf@gmail.com> wrote:
>
>>> One of the reasons why I like the CBOR tag applied to a byte stream is
>>> that
>>> it can be used to skip parsing on entire sections (no matter their
>>> underlying types) in processors that don't need to understand that
>>> section.
>>>
>>
>> I suppose you mean you don't understand the section at a semantic level
>> (e.g. you don't understand the map "section-7") but you do need to parse
>> every last data item in the section before you know its byte length. So
>> at a syntactic level you don't skip anything.
>
> Example:
>
> {"to": "you", "from": "me", "content": 24(h'a26161016162820203')}
>
> If I'm just routing this based on the "to" address, I don't need to parse
> the
> "content" value.  If I'm the end recipient, I can either put my parser
> into a
> mode that parses into CBOR (tag 24) blocks, or I can feed the byte string
> I
> get for "content" from a generic parser back into that same parser.
> Either
> way, I find out that the "content" is:
>
> {"a": 1, "b": [2, 3]}
>
>

From stephen.farrell@cs.tcd.ie  Sat Aug 17 04:06:01 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 706CF11E80E6 for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 04:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 gnyuCtqHvNFB for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 04:05:55 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB6A21F9B08 for <ietf@ietf.org>; Sat, 17 Aug 2013 04:05:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 11055BE24; Sat, 17 Aug 2013 12:05:54 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EwbxQfds8HQj; Sat, 17 Aug 2013 12:05:53 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.44.67.197]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5658DBE29; Sat, 17 Aug 2013 12:05:53 +0100 (IST)
Message-ID: <520F5911.3020701@cs.tcd.ie>
Date: Sat, 17 Aug 2013 12:05:53 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com> <8A319344-395C-46E3-8F39-8052992A3F17@cs.columbia.edu> <9C2FF8548CD17F4AB32FC8B311470DFA152D7285@xmb-rcd-x10.cisco.com> <58B7ABEC-3648-4873-BB9A-CDA311981E63@cs.columbia.edu>
In-Reply-To: <58B7ABEC-3648-4873-BB9A-CDA311981E63@cs.columbia.edu>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=windows-1252
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: Sat, 17 Aug 2013 11:06:01 -0000

On 08/17/2013 02:43 AM, Henning Schulzrinne wrote:
>>> 
>>> Thus, I think this is worth exploring, as an experiment, just
>>> like we started the day-pass experiment a number of years ago.
>> 
>> I don't know what "this" refers to in the above sentence, but I
>> agree with everything else in your note.
> 
> Offer a "self-pay" rate, as suggested by Hadriel. See how many people
> take it and ask them whether that made a difference in their
> attendance.

Just my 0.00 €

I don't agree with charging remote attendees until after
it works for them and after successful remote participation
becomes somewhat disruptive to the f2f participants. We have
so far to go before we get there, that discussion of how, what,
who or why to charge is mostly silly distraction.

I also believe its valuable that we can truthfully say that anyone
can participate with just an email address and IMO we should not
damage that. (And yes, I recognise that you can participate much
more fully if you go to f2f or virtual voice meetings.) So IMO
discussion of details of charging remote participants is also
slightly damaging.

S.

From jhutz@cmu.edu  Sat Aug 17 05:10:05 2013
Return-Path: <jhutz@cmu.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 35BC811E8108; Sat, 17 Aug 2013 05:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kyb63orb82bf; Sat, 17 Aug 2013 05:09:59 -0700 (PDT)
Received: from smtp01.srv.cs.cmu.edu (SMTP01.SRV.CS.CMU.EDU [128.2.217.196]) by ietfa.amsl.com (Postfix) with ESMTP id 4699D11E80F1; Sat, 17 Aug 2013 05:09:59 -0700 (PDT)
Received: from [10.59.1.80] ([209.118.26.194]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id r7HC9pcu028417 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 08:09:57 -0400 (EDT)
Message-ID: <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: ietf@ietf.org
Date: Sat, 17 Aug 2013 08:09:49 -0400
In-Reply-To: <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.6.2-0ubuntu0.1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.196
Cc: wgchairs@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, IETF Announcement List <ietf-announce@ietf.org>, jhutz@cmu.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, 17 Aug 2013 12:10:05 -0000

On Fri, 2013-08-16 at 13:16 -0700, Sandy Ginoza wrote:

> 2) In the following, we suggest that "ASN.1 (and particularly MIBs and
> MIB-related details)" be updated to reflect "MIBs".  Although MIB
> modules are written using a subset of ASN.1, the RPC does not check all
> ASN.1, we only check MIBs.  This change will reflect what is done in
> practice.  If the intent is to actually require the RPC to check all
> ASN.1, please let us know and we will discuss checking tools with the
> RSE and IAD.
> 
> Current:
> 1.3.  Validation of formal languages
> 
> The RPC should validate the syntax of sections of documents containing
> formal languages.  In particular ASN.1 (and particularly MIBs and
> MIB-related details), YANG, ABNF, and XML should be verified using one
> or more tools as approved by the RSE.      

I was a participant in and co-chair of a WG (Kerberos) which produced a
lot of documents containing ASN.1 other than in MIBs.  Before
considering a document ready for publication, we generally required
verification that its ASN.1 module compiles.  Usually this was done by
one or more implementors, who already had handy the tools and
dependencies required to perform such a check.

While I have no objection in principle to the RPC doing this check, it
seems likely that the burden of doing so would be significant and, at
least for IETF-stream documents, not worthwhile for the relatively small
gains realized.  This sort of check should be done before a document is
ever submitted to the IESG, let alone the RPC.

-- Jeff


From cabo@tzi.org  Sat Aug 17 06:02:27 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB98411E8104 for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 06:02:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SjHo-LfIJYJ for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 06:02:22 -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 D17BE11E8106 for <ietf@ietf.org>; Sat, 17 Aug 2013 06:02: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.4/8.14.4) with ESMTP id r7HD2IBN028241; Sat, 17 Aug 2013 15:02:18 +0200 (CEST)
Received: from [192.168.217.105] (p54893BD1.dip0.t-ipconnect.de [84.137.59.209]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 70C74C69; Sat, 17 Aug 2013 15:02:18 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <520F575D.5070902@gmail.com>
Date: Sat, 17 Aug 2013 15:02:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EAD5DAE9-4904-46FC-A6CC-DD3662CAADEC@tzi.org>
References: <CE33F83A.15E0E%joe@cursive.net> <520F575D.5070902@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1508)
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, 17 Aug 2013 13:02:28 -0000

> But tag 24 makes it harder for pedantic security devices to validate =
CBOR, somewhat like an "eval" statement.

Well, eval is Turing-equivalent, while tag 24 has quite narrow =
semantics.
So the added onus should be much more limited.

> Is a "strict mode" decoder required to decode/validate the contents of =
this tag?

Good question.
In my mental model, the "CBOR data"-tagged byte string is handed to the =
application, and this would then have to explicitly call the decoder =
again if needed (usually in strict mode again).
If the application does task the decoder to decode it as well, the =
strict mode should transfer to that (unless the application has =
explicitly said otherwise).

> And security aside, this usage means that endpoints (sender and =
receiver) work a bit harder, in order to make the life of middleboxes =
easier. This may or may not be the right trade-off, depending on your =
architecture.

There may be other reasons for a sending application to facilitate =
deferring decoding a part of the structure.

I'm not as sure about the continued importance of the premise here.
The premise seems to be "you are only middlebox-friendly if you provide =
a highly efficient way to skip large swaths of coded data the middlebox =
happens not to be interested in".
Unless the application knows precisely what the middlebox is trying to =
do (like in Joe's routing example), this may be hard to achieve.
With the move to architectures where every byte needs to be touched =
anyway (say, for encryption, or with transports like Minion), this also =
becomes less relevant.

I'm pretty sure the encoder-friendliness of item-counting (as opposed to =
byte-counting) approach trumps any middlebox-friendliness aspect here.

... switching messages here:

> This is indeed good text. I suggest to also add: "A tag followed by an
> aggregate data item (map or array) applies to all members of the data =
item."

This is not a property of tags in general.  A tag tags just the one item =
it contains.
(This sentence could be used to describe a specific property of the =
"expected conversion" tags, but saying it this way might be confusing.  =
For these three tags, the additional onus of inheriting the "expected =
conversion" to byte strings embedded in the tagged data item is only =
paid by JSON converters.)

Gr=FC=DFe, Carsten


From hadriel.kaplan@oracle.com  Sat Aug 17 07:21:48 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1037D11E8124 for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 07:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.438
X-Spam-Level: 
X-Spam-Status: No, score=-6.438 tagged_above=-999 required=5 tests=[AWL=0.161,  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 X7xC3kvUfiDC for <ietf@ietfa.amsl.com>; Sat, 17 Aug 2013 07:21:28 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id D115811E8122 for <ietf@ietf.org>; Sat, 17 Aug 2013 07:21:28 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7HELH4t017863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 17 Aug 2013 14:21:18 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7HELE7k027126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 14:21:15 GMT
Received: from abhmt119.oracle.com (abhmt119.oracle.com [141.146.116.71]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7HELEX7028783; Sat, 17 Aug 2013 14:21:14 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 17 Aug 2013 07:21:14 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <520F5911.3020701@cs.tcd.ie>
Date: Sat, 17 Aug 2013 10:20:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <435569FD-4EED-4B29-BD59-A6658ECD8527@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <520E4E2E.2090708@gmail.com> <5D8AE550A0E17E4B4CAAFD9E@[192.168.1.128]> <A97E4D71-BB8D-4161-98D8-F9AC269E0ABC@oracle.com> <8A319344-395C-46E3-8F39-8052992A3F17@cs.columbia.edu> <9C2FF8548CD17F4AB32FC8B311470DFA152D7285@xmb-rcd-x10.cisco.com> <58B7ABEC-3648-4873-BB9A-CDA311981E63@cs.columbia.edu> <520F5911.3020701@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 14:21:48 -0000

On Aug 17, 2013, at 7:05 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:

> I don't agree with charging remote attendees until after
> it works for them and after successful remote participation
> becomes somewhat disruptive to the f2f participants. We have
> so far to go before we get there, that discussion of how, what,
> who or why to charge is mostly silly distraction.

I agree.  My proposal for how/what/where to get more revenue (and not =
from remote participants) was only in case we actually need it to pay =
for enhancing remote participation.  It's not clear we have such a need =
any time soon, but I was only trying to provide an alternative model to =
charging remote participants.

-hadriel


From david.black@emc.com  Sat Aug 17 08:23:35 2013
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 010D911E8160; Sat, 17 Aug 2013 08:23:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9I8LUnnJ425G; Sat, 17 Aug 2013 08:23:30 -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 ED3DE11E815A; Sat, 17 Aug 2013 08:23:29 -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 r7HEJEVs019625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 10:19:14 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Sat, 17 Aug 2013 10:19:03 -0400
Received: from mxhub05.corp.emc.com (mxhub05.corp.emc.com [128.222.70.202]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7HEJ22i011575; Sat, 17 Aug 2013 10:19:02 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub05.corp.emc.com ([128.222.70.202]) with mapi; Sat, 17 Aug 2013 10:19:01 -0400
From: "Black, David" <david.black@emc.com>
To: "emcmurry@computer.org" <emcmurry@computer.org>, "ben@nostrum.com" <ben@nostrum.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 17 Aug 2013 10:18:59 -0400
Subject: Gen-ART review of draft-ietf-dime-overload-reqs-10
Thread-Topic: Gen-ART review of draft-ietf-dime-overload-reqs-10
Thread-Index: Ac6bVLdI1RcyJR65QjGW3iUjaKrpUQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489319@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
Cc: "Black, David" <david.black@emc.com>, "dime@ietf.org" <dime@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 15:23:35 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-dime-overload-reqs-10
Reviewer: David L. Black
Review Date: August 17, 2013
IETF LC End Date: August 16, 2013
IESG Telechat date: (if known)

Summary:
This draft is basically ready for publication, but has nits that should be
fixed before publication.

This draft describes scenarios in which Diameter overload can occur and pro=
vides
requirements for development of new overload control functionality in Diame=
ter.
It is well written, and the inclusion of scenarios in which overload can oc=
cur,
both in terms of the relationships among types of Diameter nodes and actual=
 mobile
network experience is very helpful.

I apologize for this review being a day late, as I've been on vacation for =
most
of this draft's IETF Last Call period.

Major issues: (none)

Minor issues: (none)

Nits/editorial comments:

The following two comments could be minor issues, but I'm going to treat th=
em
as editorial, as I expect that they will be addressed in development of the
actual overload functionality:

a) I assume that overload control development work will derive more specifi=
c
security requirements - e.g., as REQ 27 is stated at a rather high level.
The discussion in security considerations section seems reasonable.

b) The draft, and especially its requirements in Section 7 are strongly
focused on individual Diameter node overload.  That's necessary, but overlo=
ad
conditions can be broader, affecting an entire service or application, or
multiple instances of either/both, even if not every individual Diameter no=
de
involved is overloaded.  A number of the requirements, starting with REQ 22
could be generalized to cover broader overload conditions.

This (b) has implications for other requirements, e.g., REQ 13 should also =
be
generalized beyond a single node to avoid increased traffic in an overload
situation, even from a node that is not overloaded by itself.  There are li=
mits
on what is reasonable here, as the desired overload functionality is TCP/SC=
TP-
like reaction to congestion where individual actions taken by nodes based o=
n
the information they have (which is not the complete state of the network)
results in an overall reduction of load.

Section 1.2, 2nd paragraph:

   as network congestion, network congestion can reduce a Diameter nodes

"nodes" -> "node's"

Section 5, 1st paragraph:

 This inadequacy may, in turn, contribute to broader congestion collapse=20

"collapse" is not the right word here - I suggest "issues", "impacts",
"effects" or "problems".

Section 7

The long enumerated list of requirements is not an easy read.  It would be
better if these could somehow be grouped by functional category, e.g.,
security, transport interactions, operational/administrative, etc.

idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this is fine=
,
as the boilerplate has been appropriately modified for this draft that
expresses requirements (as opposed to a draft that specifies a protocol).

idnits 2.12.17 got confused by the 3GPP and GSMA Informative References.
I assume that they're all sufficiently stable to be informative references.
However, [TR23.843] is a work in progress, and should be noted as such in
its reference - is this needed for any of the other 3GPP or GSMA references=
?

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 lear@cisco.com  Sat Aug 17 09:27:32 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BB611E8168; Sat, 17 Aug 2013 09:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.939
X-Spam-Level: 
X-Spam-Status: No, score=-109.939 tagged_above=-999 required=5 tests=[AWL=0.659, 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 yoqbyYeN5-Xz; Sat, 17 Aug 2013 09:27:27 -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 DDEAD11E8170; Sat, 17 Aug 2013 09:27:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1982; q=dns/txt; s=iport; t=1376756847; x=1377966447; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=mjaNhN1XRSPSrRf299lmgE/HRN/tBfcfQPj3jFWnBto=; b=KUeSR2Q/WCbUDhZkOsEU34pPsy/AcupBitUmuqLwggfBu1IIbv0B8t2A Lh6vo7IpQ8ze+FgM4slpNGvwuhPtTlfzCclb/K0RhIAszSnE38zuw5wy+ L+Lyo9AdbnbEm2R38Y2pZ7lZ5+rZ/w9SBH0iItX1gTfnIifdXWRu5A4X7 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAC+jD1KtJV2a/2dsb2JhbABbgkJEhCCFXbY2gSEWdIIkAQEBAwEjVQEFCwsEAQkTFgsCAgkDAgECAUUGDQEHAQEQh3YGpwaQf5BgB4JogSoDl2SRVYFhgVcg
X-IronPort-AV: E=Sophos;i="4.89,901,1367971200";  d="scan'208,217";a="248307020"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 17 Aug 2013 16:27:20 +0000
Received: from rtp-vpn4-28.cisco.com (rtp-vpn4-28.cisco.com [10.82.208.28]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7HGRCdZ027479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Aug 2013 16:27:19 GMT
Message-ID: <520FA460.2060504@cisco.com>
Date: Sat, 17 Aug 2013 12:27:12 -0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: [IAB] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
In-Reply-To: <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------040705010106070101080504"
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 16:27:32 -0000

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

Hi Ray,

I have one question regarding 3:

> 3.Accountability
> The RPC is responsible to the RSE as regards to RFC Series consistency.


This is the entirety of a section called "accountability".  Can this be
clarified?  What about other than RFC Series consistency?  What is
example of how this statement might be relevant or operative?

Thanks,

Eliot

--------------040705010106070101080504
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 Ray,<br>
    <br>
    I have one question regarding 3:<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr" style="font-size: 16px; font-family: sans-serif;
        left: 144.16px; top: 554.88px; transform: scale(0.964316, 1);
        transform-origin: 0% 0% 0px;" data-font-name="g_font_p0_1"
        data-canvas-width="95.08160000000001">3.Accountability</div>
      <div dir="ltr" style="font-size: 16px; font-family: sans-serif;
        left: 500.16px; top: 573.44px; transform: scale(0.896831, 1);
        transform-origin: 0% 0% 0px;" data-font-name="g_font_p0_1"
        data-canvas-width="120.84800000000001">The RPC is responsible to
        the RSE as regards to RFC Series consistency. </div>
    </blockquote>
    <br>
    <br>
    This is the entirety of a section called "accountability".Â  Can this
    be clarified?Â  What about other than RFC Series consistency?Â  What
    is example of how this statement might be relevant or operative?<br>
    <br>
    Thanks,<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------040705010106070101080504--

From housley@vigilsec.com  Sat Aug 17 11:22:29 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5049221F9B01; Sat, 17 Aug 2013 11:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kJ9h2mwNqJWv; Sat, 17 Aug 2013 11:22:21 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id DFAD921F9D21; Sat, 17 Aug 2013 11:22:20 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D62ECF24038; Sat, 17 Aug 2013 14:22:26 -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 KfinaKwKYM+b; Sat, 17 Aug 2013 14:22:17 -0400 (EDT)
Received: from [192.168.0.8] (75-139-113-21.dhcp.mant.nc.charter.com [75.139.113.21]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 06177F24032; Sat, 17 Aug 2013 14:22:19 -0400 (EDT)
Subject: Re: [IAOC] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
Date: Sat, 17 Aug 2013 14:22:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1A67BD7-9E24-4A5F-A923-37504E1B1C23@vigilsec.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com> <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
To: Jeffrey Hutzelman <jhutz@cmu.edu>
X-Mailer: Apple Mail (2.1085)
Cc: IETF WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>, IETF <ietf@ietf.org>, IAOC <iaoc@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 18:22:30 -0000

In my experience, the RFC Editor relies on authors to compile non-MIB =
ASN.1 modules.

Russ


On Aug 17, 2013, at 8:09 AM, Jeffrey Hutzelman wrote:

> On Fri, 2013-08-16 at 13:16 -0700, Sandy Ginoza wrote:
>=20
>> 2) In the following, we suggest that "ASN.1 (and particularly MIBs =
and
>> MIB-related details)" be updated to reflect "MIBs".  Although MIB
>> modules are written using a subset of ASN.1, the RPC does not check =
all
>> ASN.1, we only check MIBs.  This change will reflect what is done in
>> practice.  If the intent is to actually require the RPC to check all
>> ASN.1, please let us know and we will discuss checking tools with the
>> RSE and IAD.
>>=20
>> Current:
>> 1.3.  Validation of formal languages
>>=20
>> The RPC should validate the syntax of sections of documents =
containing
>> formal languages.  In particular ASN.1 (and particularly MIBs and
>> MIB-related details), YANG, ABNF, and XML should be verified using =
one
>> or more tools as approved by the RSE.     =20
>=20
> I was a participant in and co-chair of a WG (Kerberos) which produced =
a
> lot of documents containing ASN.1 other than in MIBs.  Before
> considering a document ready for publication, we generally required
> verification that its ASN.1 module compiles.  Usually this was done by
> one or more implementors, who already had handy the tools and
> dependencies required to perform such a check.
>=20
> While I have no objection in principle to the RPC doing this check, it
> seems likely that the burden of doing so would be significant and, at
> least for IETF-stream documents, not worthwhile for the relatively =
small
> gains realized.  This sort of check should be done before a document =
is
> ever submitted to the IESG, let alone the RPC.
>=20
> -- Jeff
>=20


From bertietf@bwijnen.net  Sun Aug 18 00:22:55 2013
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 E575D11E825F; Sun, 18 Aug 2013 00:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.392
X-Spam-Level: 
X-Spam-Status: No, score=-101.392 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 462FzigkZk0r; Sun, 18 Aug 2013 00:22:48 -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 54ED511E8252; Sun, 18 Aug 2013 00:22:47 -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 <bertietf@bwijnen.net>) id 1VAxJv-0002gd-11; Sun, 18 Aug 2013 09:22:41 +0200
Received: from kitten.ripe.net ([193.0.1.240] helo=[IPv6:::1]) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1VAxJu-0005B5-Or; Sun, 18 Aug 2013 09:22:38 +0200
Message-ID: <52107646.1040002@bwijnen.net>
Date: Sun, 18 Aug 2013 09:22:46 +0200
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Community Input Sought on SOWs for RFC Production Center and RFC Publisher
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com> <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
In-Reply-To: <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20130818 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 -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd486a40e7d93e7704ffa0aa80312fc652c
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.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: Sun, 18 Aug 2013 07:22:55 -0000

The point w.r.t. MIB module checking was that
during editing phase, even a small typo in a
double quote or some such would render the MIB
module invalid/non-compilable (i.e. invalid SYNTAX).

So if RPC does not touch the text at all, then there
is no need for them to check. But if they DO touch
it (even for pagination or some such) I would
recommend doing the check. For MIB modules that
should be pretty easy, simple and not cause much
extra work. Of course the MIB module needs to be
checked (SYNTAX that is) BEFORE it gets submitted
to AD/IESG even.

Bert
On 8/17/13 2:09 PM, Jeffrey Hutzelman wrote:
> While I have no objection in principle to the RPC doing this check, it
> seems likely that the burden of doing so would be significant and, at
> least for IETF-stream documents, not worthwhile for the relatively small
> gains realized.  This sort of check should be done before a document is
> ever submitted to the IESG, let alone the RPC.

From sm@resistor.net  Sun Aug 18 02:26:40 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F3A11E8273 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 02:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.48
X-Spam-Level: 
X-Spam-Status: No, score=-102.48 tagged_above=-999 required=5 tests=[AWL=0.119, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3but8cQrhuo for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 02:26:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A2CF811E8272 for <ietf@ietf.org>; Sun, 18 Aug 2013 02:26:39 -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 r7I9QXci028208; Sun, 18 Aug 2013 02:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376817998; bh=RPM6gcGCqUCvqYgSxfm6Ihej4BDaUUGXaHmkvHOYVE8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=v0tE9Gic2a89u+490sFxcBuN3735hpzG97uHF/4VNQ5t1g4moz8RbQ+qKLd9QARBJ abjBPGUdOl30aMlAbxOc8Ebyfve4CZJEQDwv8OizrKZTfR2BjqWpyO4+1asBE+y9Rv Zp9keDjsa8DC1MUZv0DcmwqwRN3lsotFzojkB2ks=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376817998; i=@resistor.net; bh=RPM6gcGCqUCvqYgSxfm6Ihej4BDaUUGXaHmkvHOYVE8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hcrFac2+1GvRNd7561b9CW+DToZ8ZAPfR9IVbGZviQoG+wLWqsZ0xJLed6t1IxCdP NK1vMHA0vMU7FmWPWwW6Brkf4FHuxnz+DTDBJiBEbpqu0Hl+FJ5jWAe8so7gyw2pOq vwa+45UgjzIljhs2dYzBT+d4JUQBqxlL8VodzFHs=
Message-Id: <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 18 Aug 2013 02:21:55 -0700
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
From: SM <sm@resistor.net>
Subject: Academic and open source rate (was: Charging remote participants)
In-Reply-To: <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 09:26:41 -0000

Hi Hadriel,
At 12:31 16-08-2013, Hadriel Kaplan wrote:
>I may be misunderstanding you, but I'm proposing we charge "large 
>corporations with large travel budgets" slightly *more* than 
>others.[1]  I'm not suggesting an overhaul of the system.  I'm not 
>proposing they get more attention, or more weight, or any such thing.

That sounds like the ability to pay.  It might be worth considering 
changing the student rate to an academic and open source rate and 
doubling the rate.  I am not getting into a definition of "academic" 
or "open source" [1].  It is left to the organization to determine 
whether it is a good idea to be honest or try the weasel words [2] approach.

Regards,
-sm

1. If the IETF is serious about running code (see RFC 6982) it would 
try to encourage open source developers to participate more 
effectively in the IETF.

2. weasel words give the impression of taking a firm position while 
avoiding commitment to any specific claim.  


From vinayakh@gmail.com  Sun Aug 18 02:49:37 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8F611E8272 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 02:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 uvRYiqOQ9hf5 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 02:49:36 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BBE9021F9D07 for <ietf@ietf.org>; Sun, 18 Aug 2013 02:49:36 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so3755966pbb.33 for <ietf@ietf.org>; Sun, 18 Aug 2013 02:49: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=x9RfgItPLNJrFACWEaRcRzzRYQhzxYnQO2rFc+DlbBc=; b=yLzbkPSvBO91h0bKax8gZwoTsxbGPs4mgo2ZijL784kZTubMWhgReUrfhy2SrjgcvS 76sPSc/8A7SmKFYKPb02jzxqDd9FN6NKk0ZAZ9UlUw5zsvHW+vH8x+BB9T0HO5mfNDUJ rXEVzX5APFYHuNBayYaQN9sNF/OTAnCTIzcx2TgfeytJ3yRYCzIH1AhE9jAF2VG+L/ok byjo0MY/FHlXV1HazVlA24nFAss71QUvwaJspES73PkDg8lIHo87qt6K6tctTDDzq6AU jyvyx6rNnRQQHEj8bzyy2QFpx829f9RQ46lBrNYCYv9g4pF0vrJ7orwItHCiR2MXiZYp j6Uw==
MIME-Version: 1.0
X-Received: by 10.68.58.97 with SMTP id p1mr982604pbq.144.1376819376455; Sun, 18 Aug 2013 02:49:36 -0700 (PDT)
Received: by 10.66.100.226 with HTTP; Sun, 18 Aug 2013 02:49:36 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
Date: Sun, 18 Aug 2013 15:19:36 +0530
Message-ID: <CAKe6YvPu4=2iroGiyanvpQ2HsFG_P4K-5zOT3ngYi4Z=ECNM5w@mail.gmail.com>
Subject: Re: Academic and open source rate (was: Charging remote participants)
From: Vinayak Hegde <vinayakh@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=bcaec544eac6db6c0004e435bd6a
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 09:49:37 -0000

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

On Sun, Aug 18, 2013 at 2:51 PM, SM <sm@resistor.net> wrote:

> Hi Hadriel,
> At 12:31 16-08-2013, Hadriel Kaplan wrote:
>
>> I may be misunderstanding you, but I'm proposing we charge "large
>> corporations with large travel budgets" slightly *more* than others.[1]
>>  I'm not suggesting an overhaul of the system.  I'm not proposing they get
>> more attention, or more weight, or any such thing.
>>
>
> That sounds like the ability to pay.  It might be worth considering
> changing the student rate to an academic and open source rate and doubling
> the rate.  I am not getting into a definition of "academic" or "open
> source" [1].  It is left to the organization to determine whether it is a
> good idea to be honest or try the weasel words [2] approach.
>
> Regards,
> -sm
>
> 1. If the IETF is serious about running code (see RFC 6982) it would try
> to encourage open source developers to participate more effectively in the
> IETF.
>
> 2. weasel words give the impression of taking a firm position while
> avoiding commitment to any specific claim.
>

+1 on opensource. Especially in the application / RAI area space. There are
several implementers who could benefit from the interaction as well as
contribute to making standards better. Standards can be written in ways
that can make implementation easier. I have seen several instances where
RFCs have unnecessary complex and larger / longer than they should be.
Having more implementers in the WG session room is always welcome as it
will lead to better implementations and adoptions.

Also since so many opensource contributors work on their own time and money
(though not all of them), it would be welcome to give them a concessional
rate. So much of the daily software we use / write depends on open source
libraries and apps, I think will be useful to have them be a bigger part of
the standards process.

A guarded +1 on academics as well. The IRTF has been doing a good job of
involving academics. Would love to hear more on their experiences before
commenting.

-- Vinayak

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
un, Aug 18, 2013 at 2:51 PM, SM <span dir=3D"ltr">&lt;<a href=3D"mailto:sm@=
resistor.net" target=3D"_blank">sm@resistor.net</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
Hi Hadriel,<br>
At 12:31 16-08-2013, Hadriel Kaplan wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I may be misunderstanding you, but I&#39;m proposing we charge &quot;large =
corporations with large travel budgets&quot; slightly *more* than others.[1=
] =A0I&#39;m not suggesting an overhaul of the system. =A0I&#39;m not propo=
sing they get more attention, or more weight, or any such thing.<br>

</blockquote>
<br>
That sounds like the ability to pay. =A0It might be worth considering chang=
ing the student rate to an academic and open source rate and doubling the r=
ate. =A0I am not getting into a definition of &quot;academic&quot; or &quot=
;open source&quot; [1]. =A0It is left to the organization to determine whet=
her it is a good idea to be honest or try the weasel words [2] approach.<br=
>

<br>
Regards,<br>
-sm<br>
<br>
1. If the IETF is serious about running code (see RFC 6982) it would try to=
 encourage open source developers to participate more effectively in the IE=
TF.<br>
<br>
2. weasel words give the impression of taking a firm position while avoidin=
g commitment to any specific claim. =A0<br>
</blockquote></div><br></div><div class=3D"gmail_extra">+1 on opensource. E=
specially in the application / RAI area space. There are several implemente=
rs who could benefit from the interaction as well as contribute to making s=
tandards better. Standards can be written in ways that can make implementat=
ion easier. I have seen several instances where RFCs have unnecessary compl=
ex and larger / longer than they should be. Having more implementers in the=
 WG session room is always welcome as it will lead to better implementation=
s and adoptions.<br>
<br></div><div class=3D"gmail_extra">Also since so many opensource contribu=
tors work on their own time and money (though not all of them), it would be=
 welcome to give them a concessional rate. So much of the daily software we=
 use / write depends on open source libraries and apps, I think will be use=
ful to have them be a bigger part of the standards process.<br>
<br></div><div class=3D"gmail_extra">A guarded +1 on academics as well. The=
 IRTF has been doing a good job of involving academics. Would love to hear =
more on their experiences before commenting.<br></div><div class=3D"gmail_e=
xtra">
<br></div><div class=3D"gmail_extra">-- Vinayak<br></div></div>

--bcaec544eac6db6c0004e435bd6a--

From hadriel.kaplan@oracle.com  Sun Aug 18 05:33:54 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C7711E828A for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 05:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3g-S9jabGaYh for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 05:33:47 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 8C07111E8297 for <ietf@ietf.org>; Sun, 18 Aug 2013 05:33:29 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7ICXRAt022236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 18 Aug 2013 12:33:28 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7ICXPbk009046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Aug 2013 12:33:26 GMT
Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7ICXPva002276; Sun, 18 Aug 2013 12:33:25 GMT
Received: from [192.168.2.19] (/184.61.127.93) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 18 Aug 2013 05:33:25 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Academic and open source rate (was: Charging remote participants)
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
Date: Sun, 18 Aug 2013 08:33:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 12:33:54 -0000

On Aug 18, 2013, at 5:21 AM, SM <sm@resistor.net> wrote:

> 1. If the IETF is serious about running code (see RFC 6982) it would =
try to encourage open source developers to participate more effectively =
in the IETF.


Define "open source developers".  Technically quite a lot of developers =
at my employer develop "open source", as do many at many of the =
corporations which send people to the IETF.  Heck, even I personally =
submit code to Wireshark now and then.  Distinguishing between =
"Self-paying" vs. "Expensing" is pretty easy.  "Open source" vs. "Closed =
source" is a big can of worms.

I'd love to get more developers in general to participate - whether =
they're open or closed source doesn't matter.  But I don't know how to =
do that, beyond what we do now.  The email lists are free and open.  The =
physical meetings are remotely accessible for free and open.

To attend the physical meetings in person takes real money, but the =
registration fee is dwarfed by the travel+food+lodging costs.  The most =
successful open-source conferences I've seen are ones that only last a =
couple days, and located where many of them live. (which in the US would =
be silicon valley area, in terms of largest concentration)  But you =
can't just have it there once every few years - you have to have it =
there repeatedly to really succeed at that.

And it does cost the IETF lots of money to host the physical meetings, =
and that cost is directly proportional to the number of physical =
attendees.  More attendees =3D more cost.  Remote participation cost =
isn't nearly as linear nor as high, afaik.

-hadriel


From john-ietf@jck.com  Sun Aug 18 07:01:17 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE61C11E8291 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 07:01:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Akgn43OAAYJe for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 07:01:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C613E11E8111 for <ietf@ietf.org>; Sun, 18 Aug 2013 07:01:12 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VB3XX-000Cgl-EL; Sun, 18 Aug 2013 10:01:07 -0400
X-Vipre-Scanned: 0031C843002C310031C990-TDI
Date: Sun, 18 Aug 2013 10:01:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Subject: Re: Academic and open source rate (was: Charging remote participants)
Message-ID: <B8BA51FC63A70E70F70E1269@[192.168.1.128]>
In-Reply-To: <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.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: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 14:01:18 -0000

--On Sunday, 18 August, 2013 08:33 -0400 Hadriel Kaplan
<hadriel.kaplan@oracle.com> wrote:

>...
> And it does cost the IETF lots of money to host the physical
> meetings, and that cost is directly proportional to the number
> of physical attendees.  More attendees = more cost.

I had promised myself I was finished with this thread, but I
can't let this one pass.

(1) If IETF pays separately for the number of meeting rooms, the
cost is proportionate to the number of parallel sessions, not
the number of attendees.

(2) If IETF gets the meeting rooms (small and/or large) for
"free", the costs are borne by the room rates of those who stay
in the hotel and are not proportionate to much of anything
(other than favoring meetings that will draw the negotiated
minimum number of attendees who stay in that hotel).

(3) Equipment costs are also proportional to the number of
meetings we run in parallel.  Since IASA owns some of the
relevant equipment and has to ship it to meetings, there are
some amortization issues with those costs and shipping costs are
dependent on distance and handling charges from wherever things
are stored between meetings (I assume somewhere around Fremont,
California, USA).  If that location was correct and we wanted to
minimize those charges, we would hold all meetings in the San
Francisco area or at least in the western part of the USA.  In
any event the costs are in no way proportionate to the number of
attendees.

(4) The costs of the Secretariat and RFC Editor contracts and
other associated contracts and staff are relatively fixed.  A
smaller organization, with fewer working groups and less output,
might permit reducing the size of those contracts somewhat, but
that has only the most indirect and low-sensitively relationship
to the number of attendees, nothing near "proportional".

(5) If we have to pay people in addition to Secretariat staff
to, e.g., sit at registration desks, that bears some monotonic
relationship to the number of attendees.  But the step
increments in that participate function are quite large, nothing
like "directly proportional".  

(6) The cost of cookies and other refreshments may indeed be
proportional to the number of attendees but, in most facilities,
that proportionality will come in large step functions.  In
addition, in some places, costs will rise with the number of
"unusual" dietary requirements.  The number of those
requirements might increase with the number of attendees, but
nowhere near proportionately.  "Unusual" is entirely in the
perception of the supplier/facility but, from a purely economic
and cost of meetings standpoint, the IETF might be better off if
people with those needs stayed home or kept their requirements
to themselves.

So, meeting "cost directly proportional to the number of
physical attendees"?  Nope.   

    best,
       john

p.s. You should be a little cautious about a "charge the big
companies more" policy.  I've seen people who make the financial
decisions as to who comes say things like "we pay more by virtue
of sending more people, if they expect us to spend more per
person, we will make a point by cutting back on those we send
(or requiring much stronger justifications for each one who
wants to go)".  I've also seen reactions that amount to "We are
already making a big voluntary donation that is much higher than
the aggregate of the registration fees we are paying, one that
small organizations don't make.  If they want to charge us more
because we are big, we will reduce or eliminate the size of that
donation."  Specific company examples on request (but not
on-list), but be careful what you wish for.






From hadriel.kaplan@oracle.com  Sun Aug 18 08:50:52 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8277021F9406 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 08:50:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.458
X-Spam-Level: 
X-Spam-Status: No, score=-6.458 tagged_above=-999 required=5 tests=[AWL=0.141,  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 fRahd6ZzQqGB for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 08:50:46 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 9154D21F92CD for <ietf@ietf.org>; Sun, 18 Aug 2013 08:50:45 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7IFod5q030425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 18 Aug 2013 15:50:40 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7IFobKa002044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 18 Aug 2013 15:50:38 GMT
Received: from abhmt103.oracle.com (abhmt103.oracle.com [141.146.116.55]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7IFoahv017897; Sun, 18 Aug 2013 15:50:37 GMT
Received: from [192.168.2.19] (/184.61.127.93) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 18 Aug 2013 08:50:36 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Academic and open source rate (was: Charging remote participants)
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <B8BA51FC63A70E70F70E1269@[192.168.1.128]>
Date: Sun, 18 Aug 2013 11:50:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <01672754-1C4F-465B-B737-7E82DC5B3775@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com> <B8BA51FC63A70E70F70E1269@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 15:50:52 -0000

I've been told, though obviously I don't know, that the costs are =
proportional.  I assume it's not literally a "if we get one additional =
person, it costs an additional $500".  But I assume SM wasn't proposing =
to get just one or a few more "open source developer" attendees.  If =
we're talking about just a few people it's not worth arguing about... or =
doing anything about.  It would only be useful if we got a lot of such =
attendees.

-hadriel


On Aug 18, 2013, at 10:01 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Sunday, 18 August, 2013 08:33 -0400 Hadriel Kaplan
> <hadriel.kaplan@oracle.com> wrote:
>=20
>> ...
>> And it does cost the IETF lots of money to host the physical
>> meetings, and that cost is directly proportional to the number
>> of physical attendees.  More attendees =3D more cost.
>=20
> I had promised myself I was finished with this thread, but I
> can't let this one pass.
>=20
> (1) If IETF pays separately for the number of meeting rooms, the
> cost is proportionate to the number of parallel sessions, not
> the number of attendees.
>=20
> (2) If IETF gets the meeting rooms (small and/or large) for
> "free", the costs are borne by the room rates of those who stay
> in the hotel and are not proportionate to much of anything
> (other than favoring meetings that will draw the negotiated
> minimum number of attendees who stay in that hotel).
>=20
> (3) Equipment costs are also proportional to the number of
> meetings we run in parallel.  Since IASA owns some of the
> relevant equipment and has to ship it to meetings, there are
> some amortization issues with those costs and shipping costs are
> dependent on distance and handling charges from wherever things
> are stored between meetings (I assume somewhere around Fremont,
> California, USA).  If that location was correct and we wanted to
> minimize those charges, we would hold all meetings in the San
> Francisco area or at least in the western part of the USA.  In
> any event the costs are in no way proportionate to the number of
> attendees.
>=20
> (4) The costs of the Secretariat and RFC Editor contracts and
> other associated contracts and staff are relatively fixed.  A
> smaller organization, with fewer working groups and less output,
> might permit reducing the size of those contracts somewhat, but
> that has only the most indirect and low-sensitively relationship
> to the number of attendees, nothing near "proportional".
>=20
> (5) If we have to pay people in addition to Secretariat staff
> to, e.g., sit at registration desks, that bears some monotonic
> relationship to the number of attendees.  But the step
> increments in that participate function are quite large, nothing
> like "directly proportional". =20
>=20
> (6) The cost of cookies and other refreshments may indeed be
> proportional to the number of attendees but, in most facilities,
> that proportionality will come in large step functions.  In
> addition, in some places, costs will rise with the number of
> "unusual" dietary requirements.  The number of those
> requirements might increase with the number of attendees, but
> nowhere near proportionately.  "Unusual" is entirely in the
> perception of the supplier/facility but, from a purely economic
> and cost of meetings standpoint, the IETF might be better off if
> people with those needs stayed home or kept their requirements
> to themselves.
>=20
> So, meeting "cost directly proportional to the number of
> physical attendees"?  Nope.  =20
>=20
>    best,
>       john
>=20
> p.s. You should be a little cautious about a "charge the big
> companies more" policy.  I've seen people who make the financial
> decisions as to who comes say things like "we pay more by virtue
> of sending more people, if they expect us to spend more per
> person, we will make a point by cutting back on those we send
> (or requiring much stronger justifications for each one who
> wants to go)".  I've also seen reactions that amount to "We are
> already making a big voluntary donation that is much higher than
> the aggregate of the registration fees we are paying, one that
> small organizations don't make.  If they want to charge us more
> because we are big, we will reduce or eliminate the size of that
> donation."  Specific company examples on request (but not
> on-list), but be careful what you wish for.
>=20
>=20
>=20
>=20
>=20


From hallam@gmail.com  Sun Aug 18 11:24:41 2013
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 0B82811E8152 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 11:24: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=[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 cK5-zJmT7Ok3 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 11:24:40 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id A98EB21F99C0 for <ietf@ietf.org>; Sun, 18 Aug 2013 11:24:39 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id n5so3161172wev.0 for <ietf@ietf.org>; Sun, 18 Aug 2013 11:24: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=f183Rn3u99qcLcGRYrsZvR3ItgKg1agpVgkwI07N1Hg=; b=yU97ZjcWejHAZH2UDV7wsZlDOo6tmuwI45BgTSEOwu8Bg9EPmA28GDvA8nsb1/G5ea ihotGse14A0xI/aJUuA79y3tF6pQ0furyj1nxPQY3h5EK/pZkcRSDSfn5eVQObRfQ7gM s8ux6+zRYkxIwXzGLCOwzLAKATHORdQExy8Vp8BiABlE53pnpP3v0rIgfLT7DjGg1vuT DcWBekiPGZYqmMaYySHG09MRNPQa10Eac+8G0YBWnP+TGoDt3xQgzRv05lrfBxIjlU// J7Oy7uM7amLZB3BJPlSuY4Uv+g6AHq30dqF5zSEix1XB5KvXg73+rov5l/lt834RVv3W /64Q==
MIME-Version: 1.0
X-Received: by 10.180.72.104 with SMTP id c8mr5334220wiv.63.1376850278796; Sun, 18 Aug 2013 11:24:38 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Sun, 18 Aug 2013 11:24:38 -0700 (PDT)
In-Reply-To: <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com>
Date: Sun, 18 Aug 2013 14:24:38 -0400
Message-ID: <CAMm+Lwiwy6-+qiyxmtcF2Q6bcPtzrxOqHOhkDziEFCyhZoAOCg@mail.gmail.com>
Subject: Re: Academic and open source rate (was: Charging remote participants)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Content-Type: multipart/alternative; boundary=001a11c2b5b2c6d33004e43cef3d
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: Sun, 18 Aug 2013 18:24:41 -0000

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

On Sun, Aug 18, 2013 at 8:33 AM, Hadriel Kaplan
<hadriel.kaplan@oracle.com>wrote:

>
> On Aug 18, 2013, at 5:21 AM, SM <sm@resistor.net> wrote:
>
> > 1. If the IETF is serious about running code (see RFC 6982) it would try
> to encourage open source developers to participate more effectively in the
> IETF.
>
>
> Define "open source developers".  Technically quite a lot of developers at
> my employer develop "open source", as do many at many of the corporations
> which send people to the IETF.  Heck, even I personally submit code to
> Wireshark now and then.  Distinguishing between "Self-paying" vs.
> "Expensing" is pretty easy.  "Open source" vs. "Closed source" is a big can
> of worms.
>

+1

I suspect we have all done the open source thing at some point. Whether
open source makes sense as a business strategy depends on your position in
the ecosystem. Folk like the 10gen (MongoDB) people can't compete against
Oracle for the closed source DB market so an open source plus proprietary
service strategy is completely logical for them.

Following the most a logical business model for your product is hardly a
point of moral superiority. I am currently putting a large amount of my
private code onto SourceForge as open source, should my employer get a
discount for this? Should my employer pay a premium rate to allow discounts
to others? Should the fact that my employer provides open source products
that facilitate consuming a proprietary product count?


I really don't think this makes any sense at all. Open Source is not Free
Software though some people conflate the two.


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

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

<div dir=3D"ltr">On Sun, Aug 18, 2013 at 8:33 AM, Hadriel Kaplan <span dir=
=3D"ltr">&lt;<a href=3D"mailto:hadriel.kaplan@oracle.com" target=3D"_blank"=
>hadriel.kaplan@oracle.com</a>&gt;</span> wrote:<br><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
On Aug 18, 2013, at 5:21 AM, SM &lt;<a href=3D"mailto:sm@resistor.net">sm@r=
esistor.net</a>&gt; wrote:<br>
<br>
&gt; 1. If the IETF is serious about running code (see RFC 6982) it would t=
ry to encourage open source developers to participate more effectively in t=
he IETF.<br>
<br>
<br>
</div>Define &quot;open source developers&quot;. =A0Technically quite a lot=
 of developers at my employer develop &quot;open source&quot;, as do many a=
t many of the corporations which send people to the IETF. =A0Heck, even I p=
ersonally submit code to Wireshark now and then. =A0Distinguishing between =
&quot;Self-paying&quot; vs. &quot;Expensing&quot; is pretty easy. =A0&quot;=
Open source&quot; vs. &quot;Closed source&quot; is a big can of worms.<br>
</blockquote><div><br></div><div>+1=A0</div><div><br></div><div>I suspect w=
e have all done the open source thing at some point. Whether open source ma=
kes sense as a business strategy depends on your position in the ecosystem.=
 Folk like the 10gen (MongoDB) people can&#39;t compete against Oracle for =
the closed source DB market so an open source plus proprietary service stra=
tegy is completely logical for them.</div>
<div><br></div><div>Following the most a logical business model for your pr=
oduct is hardly a point of moral superiority. I am currently putting a larg=
e amount of my private code onto SourceForge as open source, should my empl=
oyer get a discount for this? Should my employer pay a premium rate to allo=
w discounts to others? Should the fact that my employer provides open sourc=
e products that facilitate consuming a proprietary product count?</div>
<div><br></div><div><br></div><div>I really don&#39;t think this makes any =
sense at all. Open Source is not Free Software though some people conflate =
the two.=A0</div><div>=A0</div></div><div><br></div>-- <br>Website: <a href=
=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>

</div></div>

--001a11c2b5b2c6d33004e43cef3d--

From hallam@gmail.com  Sun Aug 18 11:26:52 2013
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 74CA311E8153 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 11:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 gm5-GP7h6o1n for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 11:26:52 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A84BE21F995A for <ietf@ietf.org>; Sun, 18 Aug 2013 11:26:51 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id q58so3164556wes.34 for <ietf@ietf.org>; Sun, 18 Aug 2013 11:26: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=hEvRhbHQFzoYVvoI+3mPFfoKVssVB/XKBQ6+cvpYtyQ=; b=cnlm7iR0PFqEiylQpkxOXjEf03nDLQWE7scSzWUoJ9CY77RYHZqF7+Wz9j8yK0DTIc UJd90SDOG/yT6f1KYSOMl29m4gn4iNwo8dmSQBpI+zN05A+Qqj6dagUgORdj6LGs84te y054bNanTKCgPGNFoVGSqEIsCgJCrnOpr3QSMlP/ceSoUKTzaL9yiMS6Eus3MKIHur2B WIjIhBjwvCPMo/hGMxtALJfkGGxb0bPNt+6j6VnsREJWC9m9o4O/r2kds6Fwu3vOAZ2R alm+5xX1xAufc+vVt3hhKFvpTjKXOPXCVBQuoMfFzgZqLl/zaSJMCzEEtNgfAPU5dTvn HFEQ==
MIME-Version: 1.0
X-Received: by 10.180.38.73 with SMTP id e9mr5379009wik.37.1376850410828; Sun, 18 Aug 2013 11:26:50 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Sun, 18 Aug 2013 11:26:50 -0700 (PDT)
In-Reply-To: <alpine.GSO.1.10.1308161925270.24720@multics.mit.edu>
References: <alpine.GSO.1.10.1308161726500.24720@multics.mit.edu> <alpine.GSO.1.10.1308161925270.24720@multics.mit.edu>
Date: Sun, 18 Aug 2013 14:26:50 -0400
Message-ID: <CAMm+LwiiRBYrucjjf0kLk7ejS=t6fB1i4scOg9VZk4bdfA3inA@mail.gmail.com>
Subject: Re: Anyone having trouble submitting I-Ds?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Content-Type: multipart/alternative; boundary=e89a8f64701ba581a804e43cf73c
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 18:26:52 -0000

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

On Fri, Aug 16, 2013 at 7:27 PM, Benjamin Kaduk <kaduk@mit.edu> wrote:

> On Fri, 16 Aug 2013, Benjamin Kaduk wrote:
>
>  My web submission told me "Your submission is pending email
>> authentication. An email has been sent you with instructions." more than an
>> hour ago, but I haven't seen such a mail.
>>
>> I sent a note to internet-drafts@ mentioning my experience, but wanted
>> to check if anyone else was seeing this behavior.
>>
>
> It turns out this was user error -- I was not listed as an author on the
> previous version of the document, even though I did the actual upload for
> that version.  The anti-hijacking feature causes the confirmation email to
> only go to the authors listed on the previous version of the document, so
> mail was not sent to me and things are working as expected.
>

This behavior is not documented to the user when they submit the document
and is therefore a bug.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 16, 2013 at 7:27 PM, Benjamin Kaduk <span dir=3D"ltr">&=
lt;<a href=3D"mailto:kaduk@mit.edu" target=3D"_blank">kaduk@mit.edu</a>&gt;=
</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Fri, 16 Aug 2013, Benja=
min Kaduk wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
My web submission told me &quot;Your submission is pending email authentica=
tion. An email has been sent you with instructions.&quot; more than an hour=
 ago, but I haven&#39;t seen such a mail.<br>
<br>
I sent a note to internet-drafts@ mentioning my experience, but wanted to c=
heck if anyone else was seeing this behavior.<br>
</blockquote>
<br></div>
It turns out this was user error -- I was not listed as an author on the pr=
evious version of the document, even though I did the actual upload for tha=
t version. =A0The anti-hijacking feature causes the confirmation email to o=
nly go to the authors listed on the previous version of the document, so ma=
il was not sent to me and things are working as expected.<br>
</blockquote><div><br></div><div>This behavior is not documented to the use=
r when they submit the document and is therefore a bug.</div><div>=A0</div>=
</div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>

</div></div>

--e89a8f64701ba581a804e43cf73c--

From johnl@iecc.com  Sun Aug 18 14:03:18 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1A011E8129 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 14:03:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EU0rnRY79ozL for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 14:03:14 -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 117B611E8174 for <ietf@ietf.org>; Sun, 18 Aug 2013 14:03:09 -0700 (PDT)
Received: (qmail 70110 invoked from network); 18 Aug 2013 21:03:08 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Aug 2013 21:03:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5211368c.xn--i8sz2z.k1308; i=johnl@user.iecc.com; bh=b/dkxZnhBEsmBb9LZLWAAr7ukEQfGAYo1Rg6uBeIVbA=; b=vICA3h6YDi1tOmk8zQucFvYlV+AOrPwF2kv1RNAKJkrwpWDOv/+okbq+ZA58gdcUCEYB8OX2BuVeyCPErUz1+TfpWhKdPQmDWZ4mw+Bx/nN1g7IkFUzRGPBYwylUc3wIbPtfiv1HXXa8Ilsc+LgCcVVWSLxP3wv1v0RtJr44nQTaGkvLi+AK+VcUQYkKN+jHtQ/JuUTE2R4AsOcKw8tex1iRQL6Wz4tqOoc9rhRArihZvaUcK3E2ZrdravQHuv1Z
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5211368c.xn--i8sz2z.k1308; olt=johnl@user.iecc.com; bh=b/dkxZnhBEsmBb9LZLWAAr7ukEQfGAYo1Rg6uBeIVbA=; b=Ctd7Kh5vLCa9auOt8IIsdQScz1xbfEb72N7Df/BjPYg9XMfRTUuDbS3OqD76+ODMV87XYyB7CRVPAg7NCoEa6+MYOOt+1DAm4tI58skoxMMmX1CL3nLhPUgwnaWkCkPN0HCDeWbOZCfENHM/9ohgpt0LPyZ0/ZPcJt5Kt+hgWgE3VxaQDMfoTI5wt7nyfZLMnd3l5QtTHQ6TGHKqo7mFuSILx6q0etW06P3C0UMmyoLbSjsTURSW651RKIyNuamO
Date: 18 Aug 2013 21:02:46 -0000
Message-ID: <20130818210246.53296.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Academic and open source rate (was: Charging remote participants)
In-Reply-To: <01672754-1C4F-465B-B737-7E82DC5B3775@oracle.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 21:03:19 -0000

In article <01672754-1C4F-465B-B737-7E82DC5B3775@oracle.com> you write:
>
>I've been told, though obviously I don't know, that the costs are proportional.  I assume it's not literally a "if we get
>one additional person, it costs an additional $500".  But I assume SM wasn't proposing to get just one or a few more "open
>source developer" attendees.  If we're talking about just a few people it's not worth arguing about... or doing anything
>about.  It would only be useful if we got a lot of such attendees.

My trip to the Berlin IETF cost me about $3300, of which the
registration fee was only $650.  (The plane ticket was expensive,
since I flew from upstate NY, but the hotel was cheap because I booked
at a place a block away with a prepaid rate back in May.)

If we're going to provide financial inducements for people to come,
whether open source developers or anyone else, unless they happen to
live in the city where we're meeting, we'll need to give them cash
travel grants, not just waive the fee.  The IRTF brings winners of
their research prize to the meetings to present the winning papers,
so we can look at those numbers to see what it costs.




From johnl@iecc.com  Sun Aug 18 14:04:34 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0F011E8183 for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 14:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8OYSZx0rIqd for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 14:04:29 -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 9B77A11E8129 for <ietf@ietf.org>; Sun, 18 Aug 2013 14:04:29 -0700 (PDT)
Received: (qmail 70312 invoked from network); 18 Aug 2013 21:04:29 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Aug 2013 21:04:29 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=521136dc.xn--btvx9d.k1308; i=johnl@user.iecc.com; bh=PsyWXMuGvTJ0N0pO9kAB5kV2JA/LE7iI/vrhte4E7KA=; b=LK27i30Ef8jLijTVUv386ZNk9vYk7wFii/ZaCtCbC/20O0mJ47kA2EgrQOFf7xeyqst3/4t7trmFYfT71aEo76jJAHwgNmqVeqk85iWOBCSXRlY/O/lhM0jVlbh7nH2jUgaCAcbQBjv4fw9WgIJJgAh9+zFzl4mdK7fGHeU+6LoENgBPmO+RBvvK5id52RKKJ5D38KptDt1nLmgIyRaOkbGqmIWzFTdxmJjX+iQLi0OpCMB3wX+JfQdPybDn7Jcn
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=521136dc.xn--btvx9d.k1308; olt=johnl@user.iecc.com; bh=PsyWXMuGvTJ0N0pO9kAB5kV2JA/LE7iI/vrhte4E7KA=; b=vMUtJfeHiK8kUhm/6VYbXMhRnFWx5jdiukCl9FrSn1iVGXq6hAVW6SPl/JofXowyLn4SPzN5gIpTut7rVlDUdUUzOePOIYa/5zib9l7q++ZIQtpi8J1mW7PCVmiYpDV3RlCdTefkvr53qxuuewkARUO/Qo0LrOo8IOjUIvNzxOINlMWeBXcTaor+inl2aQ9/9vSm3lcM8aYw82MEBZ5tNg9a9Q9SrqVYZDqOZkDfVucJItaqJUsbjDmNgQmgVVFe
Date: 18 Aug 2013 21:04:06 -0000
Message-ID: <20130818210406.53318.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Anyone having trouble submitting I-Ds?
In-Reply-To: <CAMm+LwiiRBYrucjjf0kLk7ejS=t6fB1i4scOg9VZk4bdfA3inA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Aug 2013 21:04:34 -0000

>> The anti-hijacking feature causes the confirmation email to
>> only go to the authors listed on the previous version of the document, so
>> mail was not sent to me and things are working as expected.
>
>This behavior is not documented to the user when they submit the document
>and is therefore a bug.

It's sort of documented somewhere, but I agree that it's a bug that it
doesn't tell the submitter what happened.

I reported it as a bug a while ago, dunno where it is in the tracker.


From sm@resistor.net  Sun Aug 18 17:06:00 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A0E21F99DC for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 17:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.485
X-Spam-Level: 
X-Spam-Status: No, score=-102.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJJcG1mFSMBK for <ietf@ietfa.amsl.com>; Sun, 18 Aug 2013 17:05:58 -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 577CB21F99CE for <ietf@ietf.org>; Sun, 18 Aug 2013 17: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 r7J05kkx008951; Sun, 18 Aug 2013 17:05:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376870753; bh=EAGvQeoYdW7QTnlLFAPFwW5Qt4bskn+SZIQOEvga4xU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=g2fhM9J+Bi4YrnjU4WGn7AQzkA3lEbjDGR0E7IfvNA/dVJA2Vgj19dS847nZktHbW Zwq5EIAQzm9KafzMBkxGIoPIHgmMk9UqVK2sTWdvz8B+Jvca7pm8v4Z9F105nYLsis z6QgbbwUURpmPz3V4c1aSPKXFA+YJJUxgLphO1N8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376870753; i=@resistor.net; bh=EAGvQeoYdW7QTnlLFAPFwW5Qt4bskn+SZIQOEvga4xU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MdNg5rdUpd6YGqtOm+Tplph6bWb38sSwApN/1gqorfUwOJ64DzV9oOFztzyop7xAj 3ucxFEqPSNyiHGIrdHkBeeb5pyq2FgOCuKK98Sg+EAsvxwrzkLczC/YXn7bUz75AxW VN0tvXrmrjtOg5s2Rtai4rSX4mnXfHxcNO6si/gw=
Message-Id: <6.2.5.6.2.20130818150230.0d8d8918@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 18 Aug 2013 17:04:39 -0700
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
From: SM <sm@resistor.net>
Subject: Re: Academic and open source rate (was: Charging remote participants)
In-Reply-To: <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 00:06:00 -0000

Hi Hadriel,
At 05:33 18-08-2013, Hadriel Kaplan wrote:
>Define "open source developers".  Technically quite a lot of 
>developers at my employer develop "open source", as do many at many 
>of the corporations which send people to the IETF.  Heck, even I 
>personally submit code to Wireshark now and then.  Distinguishing 
>between "Self-paying" vs. "Expensing" is pretty easy.  "Open source" 
>vs. "Closed source" is a big can of worms.
>
>I'd love to get more developers in general to participate - whether 
>they're open or closed source doesn't matter.  But I don't know how 
>to do that, beyond what we do now.  The email lists are free and 
>open.  The physical meetings are remotely accessible for free and open.

On reading the second paragraph of the above message I see that you 
and I might have a common objective.  You mentioned that you don't 
know how to do that beyond what is done now.  I suggested a rate for 
people with an open source affiliation.  I did not define what open 
source means.  I think that you will be acting in good faith and that 
you will be able to convince your employer that it will not make you 
look good if you are listed in a category which is intended to lessen 
the burden for open source developers who currently cannot attend 
meetings or who attend meetings on a very limited budget.

We can discuss about whether a few hundred United States dollars 
makes a significant difference or we can sit by a pool and discuss 
about more interesting things.  Your colleagues will probably wonder 
why you brought more value to your company compared to them.  You 
could tell them that it is because you like strawberry ice cream as 
it is something that wills the void between rational discussion and 
all-out thermonuclear war. :-)

At 08:50 18-08-2013, Hadriel Kaplan wrote:
>I've been told, though obviously I don't know, that the costs are 
>proportional.  I assume it's not literally a "if we get one 
>additional person, it costs an additional $500".  But I assume SM 
>wasn't proposing to get just one or a few more "open source 
>developer" attendees.  If we're talking about just a few people it's 
>not worth arguing about... or doing anything about.  It would only 
>be useful if we got a lot of such attendees.

What I proposed might have an impact on just one or a few more 
persons.  The rest is left to the imagination of the reader. :-)

Regards,
-sm 


From stefan.winter@restena.lu  Mon Aug 19 01:16:12 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DB6C21F9A59; Mon, 19 Aug 2013 01:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kl+I1brXbzy6; Mon, 19 Aug 2013 01:16:04 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 5BAF921F9A30; Mon, 19 Aug 2013 01:16:03 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 7B4751057F; Mon, 19 Aug 2013 10:16:01 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id 66CB51057E; Mon, 19 Aug 2013 10:16:01 +0200 (CEST)
Message-ID: <5211D43D.2030408@restena.lu>
Date: Mon, 19 Aug 2013 10:15:57 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: dime@ietf.org, 'IETF Discussion Mailing List' <ietf@ietf.org>
Subject: Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
References: <20130813162403.9625.46995.idtracker@ietfa.amsl.com>
In-Reply-To: <20130813162403.9625.46995.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="94M1lKVwfbOllhaHSdeEbsoVTxQVjRDej"
X-Virus-Scanned: ClamAV
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 08:16:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--94M1lKVwfbOllhaHSdeEbsoVTxQVjRDej
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hello,

> The IESG has received a request from the Diameter Maintenance and
> Extensions WG (dime) to consider the following document:
> - 'Realm-Based Redirection In Diameter'
>   <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard

Sorry for bringing this up so late, but as I was writing my own dynamic
discovery draft for RADIUS, it occured to me that the usage of S-NAPTR
for Diameter brings a built-in support to signal realm-based redirect
*if* S-NAPTR discovery is used.

That only affects this document periphally; it describes realm-based
redirect for agent-based redirects, not for DNS-based; but still, the
wording in section 2 implies that using a realm-based-redirect-aware
Diameter agent is the only choice, and I think that should be rectified.

The mechanism for S-NAPTR realm-based redirect is built into the S-NAPTR
spec by allowing for "non-terminal" lookups; this is signalled by having
neither an "s" flag (for SRV targets) nor an "a" flag (for A/AAAA
targets); but instead an "" (empty) flag. The replacement string in the
NAPTR record is then the label of /another/ NAPTR lookup; that lookup is
then to be performed with the same service/protocol tag.

That makes the whole realm-based redirect problem very easy
protocol-wise. Consider a realm "foo.example" who wants to tell its
Diameter peers that its realm's application ID 123 is from now on served
from "example.com". It puts into DNS

foo.example.  43200   IN  NAPTR   100 10 "" "aaa+ap123:diameter.tls" ""
example.com

A client who got this answer would then query for

example.com NAPTR "aaa+ap123:diameter.tls"

and would get example.com's servers via SRV or A/AAAA records as
configured by the admins of example.com.

This is described in section 2.2.3 of RFC3958.

Now for the wording in the draft:

Sction 2: the first para needs a bit of a rewrite to factor in S-NAPTR's
capabilities.

I suggest something along the lines of:

"Realm-based redirection is implicitly a part of the Diameter base
protocol, but only where peer discovery using S-NAPTR is used (section
5.2 of [RFC6733], by using the non-terminal S-NAPTR flag). This allows
for both application-specific realm-based redirects, and for
application-agnostic (unconditional) realm-based redirects, and does not
require any Diameter agents.

For deployments which do not make use of S-NAPTR peer discovery, support
of realm-based redirection MUST be specified as part of functionality
supported by a Diameter application. (... continue with the rest of the
section ...)

Greetings,

Stefan Winter



>=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 2013-08-27. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    Message redirection is a basic capability provided by the Diameter
>    base protocol.  In its conventional form, message redirection is
>    performed by an application-independent "redirect agent", which
>    returns one or more individual hosts to the message sender as
>    possible destinations of the redirected message.
>=20
>    However, in some circumstances an operator may wish to redirect
>    messages to an alternate domain without specifying individual hosts.=

>    This document specifies an application-specific mechanism by which
>    that can be achieved.  New applications may incorporate this
>    capability by reference to the present document.
>=20
>    Because the redirection mechanism is application-specific, it must b=
e
>    performed by a Diameter server or proxy rather than a basic redirect=

>    agent as defined in the Diameter base protocol.  A new term, "Realm-=

>    based Redirect Server", is introduced in this document to
>    differentiate the application-specific nature of realm-based
>    redirection from the conventional Diameter redirection performed by =
a
>    basic redirect agent.
>=20
>    This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to
>    the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
>    AVPs.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/ba=
llot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>    http://datatracker.ietf.org/ipr/1254/
>=20
>=20
>=20
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>=20


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--94M1lKVwfbOllhaHSdeEbsoVTxQVjRDej
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlIR1EEACgkQ+jm90f8eFWbtwQCdF7alTpdVqwHJz8j1Vm/Kr7sp
7HUAn0m4/+kXpXyUHRc4shNR0oZI0sTR
=wc03
-----END PGP SIGNATURE-----

--94M1lKVwfbOllhaHSdeEbsoVTxQVjRDej--

From fanf2@hermes.cam.ac.uk  Mon Aug 19 02:08:35 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B30111E8217 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 02:08: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 sABJIyLKX1CB for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 02:08:30 -0700 (PDT)
Received: from ppsw-33.csi.cam.ac.uk (ppsw-33.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f33]) by ietfa.amsl.com (Postfix) with ESMTP id 5660011E8223 for <ietf@ietf.org>; Mon, 19 Aug 2013 02:08:22 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:33640) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1VBLRj-0007lz-j5 (Exim 4.80_167-5a66dd3) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 19 Aug 2013 10:08:20 +0100
Received: from fanf2 by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1VBLRj-0005BD-UE (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Mon, 19 Aug 2013 10:08:19 +0100
Date: Mon, 19 Aug 2013 10:08:19 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
In-Reply-To: <85C56F28-353C-48F3-82EA-3A3C058A2B4B@vpnc.org>
Message-ID: <alpine.LSU.2.00.1308190946240.6019@hermes-2.csi.cam.ac.uk>
References: <520D520F.8050104@gmail.com> <85C56F28-353C-48F3-82EA-3A3C058A2B4B@vpnc.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, 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: Mon, 19 Aug 2013 09:08:35 -0000

Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> On Aug 15, 2013, at 3:11 PM, Yaron Sheffer <yaronf.ietf@gmail.com>
> wrote:
>
> > - A parser that looks for duplicates must be able to detect that
> > {{"a":1, "b":2}:4, {"b":2, "a":1}:5} does in fact have a duplicate
> > key, because the two internal maps (used as keys) are identical. So in
> > general, parsers need to canonicalize maps to any depth in order to
> > detect duplicates. This is "complex" by any definition of the word.
>
> It does not need to canonicalize, but it does need to reify (or some
> word that means "know what each name means"). This is not additional
> code: the decoder already has that in the semantic processor. It is only
> additional runtime during decoding, and only in protocols/applications
> that use maps as keys.
>
> We could say "you cannot use maps as keys in maps because it is too
> hard", but then the question is where do we draw the line on "too hard".
> Is it "too hard" to use arrays? They might be arrays with arrays in
> them; is that too hard? Instead of the CBOR spec saying "this is too
> hard for you to do", we at some point have to trust the
> protocol/application developer to understand the tradeoffs.

YAML allows map keys to be arbitrary data structures. It requires keys to
be unique and uses structural equality to determine uniqueness, which
leads to the interesting difficulty that Yaron Sheffer pointed out.

Lua allows table keys to be arbitrary data structures. It requires keys to
be unique, but keys that are composite data structures are compared by
reference: each table literal is a new table.

You can express Lua-style data structures in YAML by giving unique tags to
each part of the data structure. You can express sharing in Lua by
assigning a part of the structure to a variable which is later used to
refer to that part.

I think CBOR should be clear about how it handles sharing and equality.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From masinter@adobe.com  Mon Aug 19 03:18:30 2013
Return-Path: <masinter@adobe.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E74411E822B for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 03:18:30 -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 ix9MvPe2YxaU for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 03:18:24 -0700 (PDT)
Received: from exprod6og101.obsmtp.com (exprod6og101.obsmtp.com [64.18.1.181]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6E111E823A for <ietf@ietf.org>; Mon, 19 Aug 2013 03:18:22 -0700 (PDT)
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob101.postini.com ([64.18.5.12]) with SMTP ID DSNKUhHw6Xh35lT3iuqTI7aMtEhtP/AEU2tq@postini.com; Mon, 19 Aug 2013 03:18:23 PDT
Received: from inner-relay-1.corp.adobe.com (inner-relay-1.sea.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r7JAIG96017646; Mon, 19 Aug 2013 03:18:16 -0700 (PDT)
Received: from nahub01.corp.adobe.com (nahub01.corp.adobe.com [10.8.189.97]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id r7JAIF6A009829; Mon, 19 Aug 2013 03:18:15 -0700 (PDT)
Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nahub01.corp.adobe.com ([10.8.189.97]) with mapi; Mon, 19 Aug 2013 03:18:15 -0700
From: Larry Masinter <masinter@adobe.com>
To: Tony Finch <dot@dotat.at>, Paul Hoffman <paul.hoffman@vpnc.org>
Date: Mon, 19 Aug 2013 03:18:11 -0700
Subject: RE: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Topic: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Thread-Index: Ac6cxNJlq6Q1gvYXSp+0k6mk1l8JkA==
Message-ID: <C68CB012D9182D408CED7B884F441D4D3472A46C1C@nambxv01a.corp.adobe.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: Yaron Sheffer <yaronf.ietf@gmail.com>, 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: Mon, 19 Aug 2013 10:18:30 -0000

>>> parsers need to canonicalize maps to any depth in order to
>>> detect duplicates. This is "complex" by any definition of the word.

It isn't complex in terms of computational efficiency ... you can canonical=
ize in O(N log N) and do it while reading.
And the consequence of not using structure-equality in duplicate detection =
is complex.

> I think CBOR should be clear about how it handles sharing and equality.
agree.=20


Larry
--
http://larry.masinter.net

(obscure footnote: Serializing structures with duplicate pointers is fun, y=
ou need some notation to signify back pointers and to drop anchors. Using h=
ash tables and canonical values was part of the circlprint/hprint http://pd=
p-10.trailing-edge.com/decuslib20-01/01/decus/20-0004/21lisp.tty.html imple=
mentation.)


From cabo@tzi.org  Mon Aug 19 03:38:29 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4446611E8242 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 03:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I-Mcum9TPi8J for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 03:38:23 -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 A121A11E823C for <ietf@ietf.org>; Mon, 19 Aug 2013 03:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7JAbh4Q027876; Mon, 19 Aug 2013 12:37:43 +0200 (CEST)
Received: from [192.168.217.105] (p54892636.dip0.t-ipconnect.de [84.137.38.54]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 26B84EF;  Mon, 19 Aug 2013 12:37:43 +0200 (CEST)
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <alpine.LSU.2.00.1308190946240.6019@hermes-2.csi.cam.ac.uk>
Date: Mon, 19 Aug 2013 12:37:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACF0AE51-0760-40EF-8529-03F091AE0146@tzi.org>
References: <520D520F.8050104@gmail.com> <85C56F28-353C-48F3-82EA-3A3C058A2B4B@vpnc.org> <alpine.LSU.2.00.1308190946240.6019@hermes-2.csi.cam.ac.uk>
To: Tony Finch <dot@dotat.at>
X-Mailer: Apple Mail (2.1508)
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: Mon, 19 Aug 2013 10:38:29 -0000

On Aug 19, 2013, at 11:08, Tony Finch <dot@dotat.at> wrote:

> sharing

CBOR and JSON have in common that their data model is based on trees.

A number of other data representation formats generalize this model to =
(directed, usually connected) graphs.
E.g., as you say YAML has ways to explicitly reference a part of the =
structure (which previously has to have been assigned a label).
(With other formats such as Python's pickle, I'm not even sure the =
resulting graph is always connected...)

With the data formats that provide sharing, there almost always is a =
semantic ambiguity:
Is the sharing just being used for more efficient transport of what =
semantically is a tree, or is the sharing actually part of the semantics =
(i.e., the format does express a graph for use by the application)?

An earlier version of what has become CBOR actually had both versions of =
sharing (it's easy to write them up in the spec, no? :-).
We decided to go back to a plain tree based on implementer feedback*).
We also weren't too happy about the security implications of =
implementation bugs in this space.

> equality.

The tree model should make it clear that the model of equality is what =
is called structural comparison in programming languages; reference =
comparison would be vacuous (always unequal).

Yes, both (tree model, structural comparison) should be said explicitly.

Gr=FC=DFe, Carsten

*) CBOR is extensible, though.  If an application really needs =
(semantic) sharing, it can still use CBOR after defining two tags: def =
and ref.

def([5, {"foo": "bar"}]) defines a label 5 for the data item given as =
the second element of the array, which is also included in the graph at =
the point where it occurs.
ref(5) adds an edge to that data item at the point where it occurs.
(Yes, you could even allow def([5, {"foo": "bar", "cycle": ref(5)}]) -- =
depending on where in the sequence of decoding the effect of the "def" =
occurs.  No, you don't actually have to include the label in the def =97 =
that could be assigned in sequence, and you could use relative =
references to enable painless nesting.  Etc., etc.)

We don't think we can generalize tags like these enough so they belong =
in the CBOR spec.
There are several ways to do them and an application that needs them, if =
any, should decide on the details based on its needs.


From david.black@emc.com  Mon Aug 19 06:08:55 2013
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 0FD8111E827A; Mon, 19 Aug 2013 06:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUwSZBWAfM4E; Mon, 19 Aug 2013 06:08:47 -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 A8A0511E826F; Mon, 19 Aug 2013 06:08:26 -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 r7JD80FS005380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 09:08:02 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd03.lss.emc.com [10.254.221.145]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 19 Aug 2013 09:07:48 -0400
Received: from mxhub02.corp.emc.com (mxhub02.corp.emc.com [10.254.141.104]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7JD7l9m025893; Mon, 19 Aug 2013 09:07:47 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub02.corp.emc.com ([10.254.141.104]) with mapi; Mon, 19 Aug 2013 09:07:47 -0400
From: "Black, David" <david.black@emc.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 19 Aug 2013 09:07:46 -0400
Subject: RE: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
Thread-Topic: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
Thread-Index: Ac6aqrVVQtelCuouRdyi7Cd0ThxhZgCMHC6g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C4893A1@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489289@MX15A.corp.emc.com> <tslob8x345i.fsf@mit.edu>
In-Reply-To: <tslob8x345i.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Dacheng Zhang \(zhangdacheng@huawei.com\)" <zhangdacheng@huawei.com>, "Black, David" <david.black@emc.com>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 13:08:55 -0000

> I'm somewhat uncomfortable with that sort of bar for IANA registries in
> general, although I have supported it from time to time.  (My discomfort
> with this has grown significantly since my time as an AD).  I do not
> support that sort of bar for this registry.
>=20
> I think we understand each other, but disagree.

I believe that is the case (we understand each other, but disagree).

> The question now is whether you can gain sufficient support to show
> rough consensus for a change in the document or to show that while there
> was rough consensus behind the document in the KARP WG, there's a lack
> of consensus on handling this issue between KARP and some other
> significant segment of the IETF like the security area.

I will simply point to RFC 3365 ("Strong Security Requirements for
Internet Engineering Task Force Standard Protocols") and suggest that it
is relevant to determining what the registration procedure should be
based on how this registry is likely to be used and as an example of
reasons for the IESG to not follow the rough consensus of a WG.

I believe that a discussion of how the registry is likely to be used
in practice would be productive, although I am concerned about statements
that weak password mechanisms are intended to be in scope, even though
the draft (as I read it) excludes them, starting with the draft's title.

Thanks,
--David


> -----Original Message-----
> From: Sam Hartman [mailto:hartmans-ietf@mit.edu]
> Sent: Friday, August 16, 2013 2:03 PM
> To: Black, David
> Cc: Sam Hartman; housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
> (zhangdacheng@huawei.com); General Area Review Team (gen-art@ietf.org);
> karp@ietf.org; ietf@ietf.org
> Subject: Re: [karp] IANA policy for draft-ietf-karp-crypto-key-table-08
>=20
> >>>>> "Black," =3D=3D Black, David <david.black@emc.com> writes:
>=20
>     Black,> done.  IMHO, we really should be setting a bar that says
>     Black,> that this sort of IETF imprimatur of approval of a crypto
>     Black,> algorithm actually means something.
>=20
>=20
>=20
> Something got manged there.
> I agree that publishing a standards-track document  should endorce the
> algorithm in question.
>=20
> I'm somewhat uncomfortable with that sort of bar for IANA registries in
> general, although I have supported it from time to time.  (My discomfort
> with this has grown significantly since my time as an AD).  I do not
> support that sort of bar for this registry.
>=20
> I think we understand each other, but disagree.
>=20
> The question now is whether you can gain sufficient support to show
> rough consensus for a change in the document or to show that while there
> was rough consensus behind the document in the KARP WG, there's a lack
> of consensus on handling this issue between KARP and some other
> significant segment of the IETF like the security area.


From john-ietf@jck.com  Mon Aug 19 06:11:37 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D05C011E80F6 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:11:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qnmn7LNxzLLc for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:11:32 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D1F2321F9C7A for <ietf@ietf.org>; Mon, 19 Aug 2013 06:11:31 -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 1VBPF4-000FTj-KN; Mon, 19 Aug 2013 09:11:30 -0400
Date: Mon, 19 Aug 2013 09:11:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>
Subject: Re: Academic and open source rate (was: Charging remote participants)
Message-ID: <750FC4DACA4B5EF79C93C4C7@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20130818150230.0d8d8918@resistor.net>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com> <6.2.5.6.2.20130818150230.0d8d8918@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 13:11:37 -0000

--On Sunday, August 18, 2013 17:04 -0700 SM <sm@resistor.net>
wrote:

>> I'd love to get more developers in general to participate -
>> whether  they're open or closed source doesn't matter.  But I
>> don't know how  to do that, beyond what we do now.  The email
>> lists are free and  open.  The physical meetings are remotely
>> accessible for free and open.
> 
> On reading the second paragraph of the above message I see
> that you and I might have a common objective.  You mentioned
> that you don't know how to do that beyond what is done now.  I
> suggested a rate for people with an open source affiliation.
> I did not define what open source means.  I think that you
> will be acting in good faith and that you will be able to
> convince your employer that it will not make you look good if
> you are listed in a category which is intended to lessen the
> burden for open source developers who currently cannot attend
> meetings or who attend meetings on a very limited budget.

I think this is bogus and takes us down an undesirable path.
First, I note that, in some organizations (including some large
ones), someone might be working on an open source project one
month and a proprietary one the next, or maybe both
concurrently.  Would it be appropriate for such a person (or the
company's CFO) to claim the lower rate, thereby expecting those
who pay full rate to subsidize them?  Or would their involvement
in any proprietary-source activity contaminate them morally and
require them to pay the full rate?  Second, remember that "open
source" is actually a controversial term with some history of
source being made open and available, presumably for study, but
with very restrictive licensing rules associated with its
adaptation or use.

Does it count if the open source software is basically
irrelevant to the work of the IETF?  Written in, e.g., HTML5?
Do reference implementations of IETF protocols count more (if
I'm going to be expected to subsidize someone else's attendance
at the IETF, I think they should).

Shouldn't we be tying this to the discussion about IPR
preference hierarchies s.t. FOSS software with no license
requirements get more points (and bigger discounts) than BSD or
GPL software, which get more points than FRAND, and so on?

Finally, there seems to be an assumption underlying all of this
that people associated with open source projects intrinsically
have more restrictive meeting or travel budgets and policies
than those working on proprietary efforts in clearly-for-profit
organizations (especially large one).  As anyone who have lived
through a serious travel freeze or authorization escalation in a
large company knows too well, that doesn't reflect reality.

best,
   john





From hallam@gmail.com  Mon Aug 19 06:29:22 2013
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 7D63711E8101 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.371
X-Spam-Level: 
X-Spam-Status: No, score=-1.371 tagged_above=-999 required=5 tests=[AWL=-1.227, BAYES_00=-2.599, FRT_ADOBE2=2.455, 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 D0npK-eyQ-QV for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:29:21 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 38C1F11E80F1 for <ietf@ietf.org>; Mon, 19 Aug 2013 06:29:21 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id y10so3446951wgg.4 for <ietf@ietf.org>; Mon, 19 Aug 2013 06:29:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7nUCtrCAycz3+H7d3T7AzXXn/nfKW/eWHAuT8lSVppc=; b=ZWldO+38QABgqSfYWksJJ8vS/+D4GYAXZx5DWsl0jbW/zDBmTpL89o1Tei+Y9ZgQxR HSc+a4LUerTYXlHuqXeJ1NQrrB3vysYp/ry1DIL9CSw9haef1SVWCCasnPuoors3Dc/C zbbWm5aKp8f9f8QGOskPiTPtsK/rALKe0XHUZ47FUjnq4i6PGBFIbmWugY7tHWGZ6SDg eK9mw0779g4xNUKM1u+fYjiC1xht26US2PNZLsUnw04QaZIufMrSDmT1xQvspS+PzYV4 ptknKs51N7/z3gA3sVO5i/jDXWB+U8Z8IX3ExIi0NtlM7FUdADIEIK36xHOkSbf1lLeG nbPg==
MIME-Version: 1.0
X-Received: by 10.180.38.73 with SMTP id e9mr8440393wik.37.1376918960383; Mon, 19 Aug 2013 06:29:20 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Mon, 19 Aug 2013 06:29:20 -0700 (PDT)
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D3472A46C1C@nambxv01a.corp.adobe.com>
References: <C68CB012D9182D408CED7B884F441D4D3472A46C1C@nambxv01a.corp.adobe.com>
Date: Mon, 19 Aug 2013 09:29:20 -0400
Message-ID: <CAMm+LwiHtdLCwCBYLRZ=2nUc2rs1EP_KRvNejxq566Li4NumFg@mail.gmail.com>
Subject: Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Larry Masinter <masinter@adobe.com>
Content-Type: multipart/alternative; boundary=e89a8f64701b84ae5204e44cedcc
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>, 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: Mon, 19 Aug 2013 13:29:22 -0000

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

On Mon, Aug 19, 2013 at 6:18 AM, Larry Masinter <masinter@adobe.com> wrote:

> >>> parsers need to canonicalize maps to any depth in order to
> >>> detect duplicates. This is "complex" by any definition of the word.
>
> It isn't complex in terms of computational efficiency ... you can
> canonicalize in O(N log N) and do it while reading.
> And the consequence of not using structure-equality in duplicate detection
> is complex.
>
> > I think CBOR should be clear about how it handles sharing and equality.
> agree.
>

I don't see a need to declare them as maps at all.

In any data encoding / pickling type scheme there is data that is put out
on the wire and there is additional information which is needed to make
sense of it. Some encoding formats have more of the latter than others but
there is no schema language that is rich enough to completely express the
semantics of the messages so there is always some additional data.

JSON has a number of design choices that mean that there is rather more
additional information that needs to be added in than in XML or ASN.1. JSON
conflates lists and sets for example. It does not require data to be
serialized in a particular order. But this is not a problem as there is no
particular need to have that information on the wire. Sets, lists, bags,
arrays can all be expressed as lists as LISP demonstrates quite well.

These map encodings are essentially just a function definition which can be
represented as an array of 2-tuples with an additional constraint that the
mapping be a surjection (many to one). This is exactly how a surjection is
defined in Z.

Why force the constraint that the mapping be a surjection into the encoding
format? Why fetishize just surjections, what about bijections?


I much prefer the JSON approach. The only reason to need a fully self
describing data structure in a protocol is for debugging. And you don't
need a lot of structure information to make sense of the data.

There is a better case for an extensive schema in an encoding format for
experimental data and the like or for a document format. Dumping the schema
or the like into each file is polite. But that could just as easily be done
by reserving a tag for 'meta data follows, may be ignored'.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Aug 19, 2013 at 6:18 AM, Larry Masinter <span dir=3D"ltr">&=
lt;<a href=3D"mailto:masinter@adobe.com" target=3D"_blank">masinter@adobe.c=
om</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt;&gt;&gt; parsers need =
to canonicalize maps to any depth in order to<br>
&gt;&gt;&gt; detect duplicates. This is &quot;complex&quot; by any definiti=
on of the word.<br>
<br>
</div>It isn&#39;t complex in terms of computational efficiency ... you can=
 canonicalize in O(N log N) and do it while reading.<br>
And the consequence of not using structure-equality in duplicate detection =
is complex.<br>
<div class=3D"im"><br>
&gt; I think CBOR should be clear about how it handles sharing and equality=
.<br>
</div>agree.<br></blockquote><div><br></div><div>I don&#39;t see a need to =
declare them as maps at all.</div><div><br></div><div>In any data encoding =
/ pickling type scheme there is data that is put out on the wire and there =
is additional information which is needed to make sense of it. Some encodin=
g formats have more of the latter than others but there is no schema langua=
ge that is rich enough to completely express the semantics of the messages =
so there is always some additional data.</div>
<div><br></div><div>JSON has a number of design choices that mean that ther=
e is rather more additional information that needs to be added in than in X=
ML or ASN.1. JSON conflates lists and sets for example. It does not require=
 data to be serialized in a particular order. But this is not a problem as =
there is no particular need to have that information on the wire. Sets, lis=
ts, bags, arrays can all be expressed as lists as LISP demonstrates quite w=
ell.</div>
<div><br></div><div>These map encodings are essentially just a function def=
inition which can be represented as an array of 2-tuples with an additional=
 constraint that the mapping be a surjection (many to one). This is exactly=
 how a surjection is defined in Z.</div>
<div><br></div><div>Why force the constraint that the mapping be a surjecti=
on into the encoding format? Why fetishize just surjections, what about bij=
ections?</div><div><br></div><div><br></div><div>I much prefer the JSON app=
roach. The only reason to need a fully self describing data structure in a =
protocol is for debugging. And you don&#39;t need a lot of structure inform=
ation to make sense of the data.=A0</div>
<div><br></div><div>There is a better case for an extensive schema in an en=
coding format for experimental data and the like or for a document format. =
Dumping the schema or the like into each file is polite. But that could jus=
t as easily be done by reserving a tag for &#39;meta data follows, may be i=
gnored&#39;.</div>
<div><br></div></div><div><br></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--e89a8f64701b84ae5204e44cedcc--

From hadriel.kaplan@oracle.com  Mon Aug 19 06:35:35 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8574A11E80F1 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.467
X-Spam-Level: 
X-Spam-Status: No, score=-6.467 tagged_above=-999 required=5 tests=[AWL=0.132,  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 NPNYzBpHzSm8 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:35:28 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id CC6FE11E8101 for <ietf@ietf.org>; Mon, 19 Aug 2013 06:35:28 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7JDZQT4007915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Aug 2013 13:35:28 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7JDZPQS001007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 13:35:26 GMT
Received: from abhmt120.oracle.com (abhmt120.oracle.com [141.146.116.72]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7JDZPPk001002; Mon, 19 Aug 2013 13:35:25 GMT
Received: from [10.1.21.34] (/10.5.21.34) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 19 Aug 2013 06:35:25 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Academic and open source rate (was: Charging remote participants)
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <6.2.5.6.2.20130818150230.0d8d8918@resistor.net>
Date: Mon, 19 Aug 2013 09:35:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8F201592-5F9D-40A1-B7A5-665F88420F5A@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com> <6.2.5.6.2.20130818150230.0d8d8918@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 13:35:35 -0000

On Aug 18, 2013, at 8:04 PM, SM <sm@resistor.net> wrote:

> On reading the second paragraph of the above message I see that you =
and I might have a common objective.  You mentioned that you don't know =
how to do that beyond what is done now.  I suggested a rate for people =
with an open source affiliation.  I did not define what open source =
means.  I think that you will be acting in good faith and that you will =
be able to convince your employer that it will not make you look good if =
you are listed in a category which is intended to lessen the burden for =
open source developers who currently cannot attend meetings or who =
attend meetings on a very limited budget.

But my point was more that "open source" is meaningless, and not what I =
think we're missing/need.  I agree we need more developers (at least in =
RAI it would help), but whether the things they develop are open source =
or not doesn't matter.  Developers of open source are no better or worse =
than those of closed source.  And their source code "openness" is not =
tied to their ability to pay or not, either.

-hadriel


From scott@kitterman.com  Mon Aug 19 06:41:55 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4552511E8266 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns4iBRGCImRC for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 06:41:50 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE3E11E8108 for <ietf@ietf.org>; Mon, 19 Aug 2013 06:41:50 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 0C71D20E410F; Mon, 19 Aug 2013 09:41:48 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376919708; bh=OCve+1ATewxFAPjCWidG+cpclcihw2Y4dPjExiuTFVw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RAUTEakaeJUOEdrcXAf+nc5284EED1/sbExoZTdULPYT9QOEtXlzlCPcNI/jWZ/yN 5Bbych8QdE/TcyYoAmtTM3jNS/oEfXwr02URh/L/aU4f5GzK9A2WlfCd9X9QwpYCJa eNp+mbkXoEPi8uUfoHHTyVkRXlNuyMjZPvQZCnM8=
Received: from scott-latitude-e6320.localnet (252.sub-70-192-195.myvzw.com [70.192.195.252]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id D7DD020E40CB;  Mon, 19 Aug 2013 09:41:47 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Academic and open source rate (was: Charging remote participants)
Date: Mon, 19 Aug 2013 09:41:34 -0400
Message-ID: <1459149.nS7rhtzaPE@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <8F201592-5F9D-40A1-B7A5-665F88420F5A@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <6.2.5.6.2.20130818150230.0d8d8918@resistor.net> <8F201592-5F9D-40A1-B7A5-665F88420F5A@oracle.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 13:41:55 -0000

On Monday, August 19, 2013 09:35:25 Hadriel Kaplan wrote:
> On Aug 18, 2013, at 8:04 PM, SM <sm@resistor.net> wrote:
> > On reading the second paragraph of the above message I see that you and I
> > might have a common objective.  You mentioned that you don't know how to
> > do that beyond what is done now.  I suggested a rate for people with an
> > open source affiliation.  I did not define what open source means.  I
> > think that you will be acting in good faith and that you will be able to
> > convince your employer that it will not make you look good if you are
> > listed in a category which is intended to lessen the burden for open
> > source developers who currently cannot attend meetings or who attend
> > meetings on a very limited budget.
> But my point was more that "open source" is meaningless, and not what I
> think we're missing/need.  I agree we need more developers (at least in RAI
> it would help), but whether the things they develop are open source or not
> doesn't matter.  Developers of open source are no better or worse than
> those of closed source.  And their source code "openness" is not tied to
> their ability to pay or not, either.

They aren't equivalent.  A developer of a Free/Open implementation can openly 
show/discuss the code related to development issues associated with protocol 
development.  That's often more useful than hand waving about implementation 
issues that can't be shared.  Not that proprietary implementations don't 
server to inform the process at all, but it's not equivalent to what can be 
accomplished with a Free/Open implementation.

Note: I'm not claiming this should change anyone's mind about discounts.

Scott K

From vinayakh@gmail.com  Mon Aug 19 07:10:24 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E356311E810E for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 07:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 sTsAMrXYBuwp for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 07:10:24 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 553F611E8103 for <ietf@ietf.org>; Mon, 19 Aug 2013 07:10:24 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id xa7so5019252pbc.3 for <ietf@ietf.org>; Mon, 19 Aug 2013 07:10:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oR9IDybs87meVgnqyuOfWgH3xllx1E58TyCH6Ujmz1w=; b=P7o9TORxV0L2whGP9I//kVNLBnkkunFT1zjhVib7lDS7kXU74+d1OwWhyHMbc5a3Sf zu+DYpBmwGrv9h2eGl6wr7rQYeAFtc0sXY3hlvQ8858Wp7tVvuymKB99ML5iIKwJJFTe pHfPI2oXIwJOgodPB7ugo1zBv1I31S0h0UQhH/z1gnbrc4pwcjBqOKzLOYUfWmzA80mT fdUe8P8AegKDkpl2dIWjlAxfSf8JcgEj7vFqkxbeoMH1hEKvZi9jGndTtPK/DrrbanSc yeBMkrn/Gutzq7t2qo4SS49mcmmV4r90QHr1SIfJhtNNNF7+boY5KKsoSObMU5YFzpEz KpEg==
MIME-Version: 1.0
X-Received: by 10.66.162.167 with SMTP id yb7mr13759866pab.16.1376921423887; Mon, 19 Aug 2013 07:10:23 -0700 (PDT)
Received: by 10.66.100.226 with HTTP; Mon, 19 Aug 2013 07:10:22 -0700 (PDT)
In-Reply-To: <1459149.nS7rhtzaPE@scott-latitude-e6320>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <6.2.5.6.2.20130818150230.0d8d8918@resistor.net> <8F201592-5F9D-40A1-B7A5-665F88420F5A@oracle.com> <1459149.nS7rhtzaPE@scott-latitude-e6320>
Date: Mon, 19 Aug 2013 19:40:22 +0530
Message-ID: <CAKe6YvMRMX8bzmdXc+QK=5iz5Ve0Ed=50QE74cDi8_nOzEXO2Q@mail.gmail.com>
Subject: Re: Academic and open source rate (was: Charging remote participants)
From: Vinayak Hegde <vinayakh@gmail.com>
To: Scott Kitterman <scott@kitterman.com>
Content-Type: multipart/alternative; boundary=047d7bacbe705ac19f04e44d80ca
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: Mon, 19 Aug 2013 14:10:25 -0000

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

On Mon, Aug 19, 2013 at 7:11 PM, Scott Kitterman <scott@kitterman.com>wrote:

> > But my point was more that "open source" is meaningless, and not what I
> > think we're missing/need.  I agree we need more developers (at least in
> RAI
> > it would help), but whether the things they develop are open source or
> not
> > doesn't matter.  Developers of open source are no better or worse than
> > those of closed source.  And their source code "openness" is not tied to
> > their ability to pay or not, either.
>
> They aren't equivalent.  A developer of a Free/Open implementation can
> openly
> show/discuss the code related to development issues associated with
> protocol
> development.  That's often more useful than hand waving about
> implementation
> issues that can't be shared.  Not that proprietary implementations don't
> server to inform the process at all, but it's not equivalent to what can be
> accomplished with a Free/Open implementation.
>
> Note: I'm not claiming this should change anyone's mind about discounts.
>

+1 to the fact that you can openly show/discuss the code. I also want to
repeat the fact that many libraries (Apache / BSD / public domain) get
bundled into proprietary code as well (for example see how many products
ship some version of curl/zlib library). So while it is hard to define
"open source" no doubt, we as a community should look at how to get more
implementers (whose code is likely to be widely deployed). That will help
us to avoid fixing quirk down the road which is difficult and expensive. It
is a problem worth looking at.

-- Vinayak

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Aug 19, 2013 at 7:11 PM, Scott Kitterman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:scott@kitterman.com" target=3D"_blank">scott@kitterman.com</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"HOEnZb"><div class=3D"h5">&gt;=
 But my point was more that &quot;open source&quot; is meaningless, and not=
 what I<br>

&gt; think we&#39;re missing/need. =A0I agree we need more developers (at l=
east in RAI<br>
&gt; it would help), but whether the things they develop are open source or=
 not<br>
&gt; doesn&#39;t matter. =A0Developers of open source are no better or wors=
e than<br>
&gt; those of closed source. =A0And their source code &quot;openness&quot; =
is not tied to<br>
&gt; their ability to pay or not, either.<br>
<br>
</div></div>They aren&#39;t equivalent. =A0A developer of a Free/Open imple=
mentation can openly<br>
show/discuss the code related to development issues associated with protoco=
l<br>
development. =A0That&#39;s often more useful than hand waving about impleme=
ntation<br>
issues that can&#39;t be shared. =A0Not that proprietary implementations do=
n&#39;t<br>
server to inform the process at all, but it&#39;s not equivalent to what ca=
n be<br>
accomplished with a Free/Open implementation.<br>
<br>
Note: I&#39;m not claiming this should change anyone&#39;s mind about disco=
unts.<br></blockquote><div><br></div><div>+1 to the fact that you can openl=
y show/discuss the code. I also want to repeat the fact that many libraries=
 (Apache / BSD / public domain) get bundled into proprietary code as well (=
for example see how many products ship some version of curl/zlib library). =
So while it is hard to define &quot;open source&quot; no doubt, we as a com=
munity should look at how to get more implementers (whose code is likely to=
 be widely deployed). That will help us to avoid fixing quirk down the road=
 which is difficult and expensive. It is a problem worth looking at.<br>
<br></div><div>-- Vinayak<br></div></div></div></div>

--047d7bacbe705ac19f04e44d80ca--

From carter@qosient.com  Fri Aug 16 10:57:28 2013
Return-Path: <carter@qosient.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4242421F9FCA; Fri, 16 Aug 2013 10:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level: 
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, 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 2PzfUL3FHnV7; Fri, 16 Aug 2013 10:57:23 -0700 (PDT)
Received: from mail1.g1.pair.com (mail1.g1.pair.com [66.39.3.162]) by ietfa.amsl.com (Postfix) with ESMTP id 3F0BD21F9D5F; Fri, 16 Aug 2013 10:57:23 -0700 (PDT)
Received: from thoth.newyork.qosient.com (207-237-36-98.c3-0.avec-ubr1.nyr-avec.ny.static.cable.rcn.com [207.237.36.98]) by mail1.g1.pair.com (Postfix) with ESMTPSA id 242F32BD37; Fri, 16 Aug 2013 13:57:18 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [karp] IANA policy for  draft-ietf-karp-crypto-key-table-08
From: Carter Bullard <carter@qosient.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489288@MX15A.corp.emc.com>
Date: Fri, 16 Aug 2013 13:57:17 -0400
Message-Id: <41E3D887-7FAD-47BA-AEBB-FF65F14F3F88@qosient.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C2B7440@MX15A.corp.emc.com> <tslvc38cc7p.fsf@mit.edu> <8D3D17ACE214DC429325B2B98F3AE7129C489288@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Mon, 19 Aug 2013 07:30:26 -0700
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Sam Hartman <hartmans-ietfc@mit.edu>, "karp@ietf.org" <karp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Aug 2013 17:57:28 -0000

--Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hey David,
Having been down this path a number of times, I would like to
suggest that one shouldn't attempt to qualify any algorithm,
technique, method or approach that may be submitted to the
registration process.

By suggesting that the registry somehow contains only " good "
strategies, without any consideration regarding a specific
implementation, you're making a claim that is unsupportable.
Bad implementations of " good " strategies can be worst than
plaintext passwords =85 really.

Let the user decide what mechanisms they want to use, based
on their criteria.

Clear text passwords used over a triple AES encrypted channel
is not "by definition" a bad strategy.  Theoretically, it could
be abstracted as a two-factor system, which has its advantages,
regardless of the perceived " strength ".  Why not ??

Carter

On Aug 16, 2013, at 1:00 PM, "Black, David" <david.black@emc.com> wrote:

> Sam,
>=20
> Thanks for picking this up.  Unlike my other two concerns with this =
draft,
> I think we have a longer discussion ahead of us on this one.
>=20
> Your summary of my concern is on the mark:
>=20
>> David's main concern is that bad security will get registered.
>=20
> I understand the response to be two-fold:
>=20
> 1) It doesn't matter; the controlling registry for crypto algorithm =
usage
> is the protocol-specific registry, not the key table database =
registry.
>=20
> 2) The guidance for the Expert Reviewer will be very difficult to =
write.
>=20
> I'm not convinced by either of these, sorry.
>=20
> I'm concerned that the two-registry subtlety in 1) will be lost on
> implementers, especially because (as mentioned in the IESG thread), =
this
> key table database is likely to see use beyond routing protocols.  =
Among
> other things, it's being proposed as a general mechanism for keying =
RSVP,
> not just RSVP-TE (I'm one of the co-chairs of the tsvwg WG that's
> responsible for RSVP).  That key table databases registry is also =
likely
> to be a place that designers of new protocols look to figure out what =
to
> use for security.
>=20
> As for cleartext passwords:
>=20
>> Also, some routing protocols are protected by cleartext passwords =
sent
>> over the network.  We want to be able to manage that, so we will be
>> registering plaintext password in these registries.
>> I don't think anyone will come up with anything worse than that.
>=20
> I read the first sentence in Section 2 of this draft as excluding
> cleartext passwords:
>=20
>   The database is characterized as a table, where each row represents
>   a single long-lived symmetric cryptographic key.
>=20
> If someone wants to argue that a cleartext password is a "long-lived
> symmetric cryptographic key", I'll go break out the popcorn and watch
> w/amusement :-).
>=20
> Seriously, if the intention is to include cleartext passwords, then I
> think some more rewriting is in order, and I would suggest checking
> directly with the Security ADs before going there.
>=20
> As for 2), the fact that it will be difficult (with which I agree)
> doesn't imply that it isn't necessary or shouldn't be done.  IMHO, we
> really should be setting a bar that says that this sort of IETF
> imprimatur of approval of a crypto algorithm actually means something.
>=20
> I appreciate that FCFS provides an easier path forward, however I'm
> reminded by analogy of something I learned from my grad school
> software engineering professor:
>=20
> 	I can make the code run arbitrarily fast ...
> 	...  if it doesn't have to be correct.
>=20
> I'm rather uncomfortable with this use of process expediency as a
> rationale for avoiding a technical concern.
>=20
> This may ultimately be an issue that the IESG needs to sort out, as =
the
> level of security for IETF protocols and concerns about "vanity =
crypto"=20
> extend well beyond the karp WG, but discussion ought to start here.
>=20
> Thanks,
> --David
>=20
>=20
>> -----Original Message-----
>> From: Sam Hartman [mailto:hartmans-ietfc@mit.edu]
>> Sent: Wednesday, August 14, 2013 3:19 PM
>> To: Black, David
>> Cc: housley@vigilsec.com; tim.polk@nist.gov; Dacheng Zhang
>> (zhangdacheng@huawei.com); General Area Review Team =
(gen-art@ietf.org);
>> karp@ietf.org; ietf@ietf.org
>> Subject: Re: [karp] IANA policy for =
draft-ietf-karp-crypto-key-table-08
>>=20
>>=20
>>=20
>> David, as we mentioned in the IESG thread, we seem to have dropped =
the
>> response to your comments about IANA actions.
>>=20
>> WG:
>> =46rom the genart review:
>>=20
>> [9] I suggest Expert Review for the new IANA registries, not just
>> First Come First Served, so that someone with a security "clue" can
>> check that the proposed registrations are reasonable.
>>=20
>>=20
>> Stephen has filed a related DISCUSS position.  He's confused why we =
need
>> a registry for  KDFs or algorithms.
>> He argues that the protocols should already have such a registry.  He
>> argues that it would be non-sensical to register a value in this
>> registry but not the protocol registry.
>>=20
>> In a somewhat related discussion, multiple people have asked what the
>> scope of this document is.  Are we defining something for routing
>> protocols?  Any security protocol in the world?  Something =
in-between?
>>=20
>>=20
>> IU'm going to make two responses:
>>=20
>> 1)
>> I think FCFS is not harmful for these registries.
>>=20
>> David's main concern is that bad security will get registered.
>>=20
>> I'll point out that these registries are not about what security you =
can
>> use with a routing protocol, but about what security you can =
configure
>> from a management standpoint.
>> Registering rot13 or similarly questionable security here wouldn't =
mean
>> I could use it with a routing protocol, only that I could ask a =
system
>> to do so.  If ROT13 was not actually in the security-specific =
registries
>> for the protocols in question there'd be no way to send a
>> rot13-transformed message.
>>=20
>> I think people wanting to use bad security in routing protocols will
>> focus on specifying how to use the security for the protocols, and
>> that's the appropriate place to do any gateway review.
>> Yeah, I guess with FCFS it's possible someone could register here and
>> then later realize they cannot get their md4 security approved in the
>> actual protocol registry document.
>>=20
>> That might be confusing but doesn't seem very harmful.
>>=20
>> Also, some routing protocols are protected by cleartext passwords =
sent
>> over the network.  We want to be able to manage that, so we will be
>> registering plaintext password in these registries.
>> I don't think anyone will come up with anything worse than that.
>>=20
>> Finally, I think a lot of us have begun to question the value in
>> security review for codepoint assignment.  Some security WGs care a =
lot;
>> some don't seem to care much at all.
>>=20
>> 2)  Why I prefer FCFS or at least would object strongly to expert
>> review.
>>=20
>> If we're going to say we want expert review I want us to give  expert
>> instructions at least good enough that I believe I could answer the
>> question of what registrations to approve if I were appointed the
>> expert.
>>=20
>> I don't think we could come to consensus on those instructions very
>> easily.
>> In particular, I think it would be challenging for us to describe =
what
>> security protocols the protocol registry applies to and which ones it
>> does not.
>>=20
>> I'm totally fine publishing this document knowing it will be used for
>> routing protocols but not knowing what beyond routing protocols it =
will
>> be used for.
>> If we do that FCFS makes a lot of sense.
>>=20
>> So, my recommendation is that we keep our current registration =
policy.
>=20
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp
>=20


--Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIXZzCCBXAw
ggRYoAMCAQICAQ8wDQYJKoZIhvcNAQEFBQAwTTELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRUNBMRYwFAYDVQQDEw1FQ0EgUm9vdCBDQSAyMB4XDTExMDYw
MTEzNDMzM1oXDTE3MDUzMDEzNDMzM1owcDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292
ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVz
MRUwEwYDVQQDEwxPUkMgRUNBIFNXIDQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDM
p/zFNAJfjYagDX701xRpK6QjRa7rhtR2U/CIE1pTSAR1BINfsYNHt2+bi0SH4SwZ61Xw9hMqCMBP
y05JJpeerEz0xpDbkqDz2NDqBm02rwdcRFqOWQn8Of3ALJKopAF6ZSkeF1j7KFCKQlIntAIyJ/c+
THyZJJD0Ns4SUrmQmBsm3q0kEl06lT7MHLPTv5LXkB+5PayhAJUWEXq/iUEhLDBstTaD1NGOleIM
sv3i1X01amB9GywN2v/kKlfGuGQpFAWi0QabC4hMfUjM217bGQS0/v1VV11zBpRlEEzH0zJgQQDX
WQy+V7vRbLav2bK3oWwvNTJGhb2CWHah7FrlAgMBAAGjggI2MIICMjASBgNVHRMBAf8ECDAGAQH/
AgEAMA4GA1UdDwEB/wQEAwIBhjAdBgNVHQ4EFgQUQpz0um9t6TDXOtZG9LI07p3STyYwHwYDVR0j
BBgwFoAU7eSH0CfEUOaEOvfM9+s6SfxSTiEwMwYDVR0gBCwwKjAMBgpghkgBZQMCAQwBMAwGCmCG
SAFlAwIBDAIwDAYKYIZIAWUDAgEMAzCBwAYDVR0fBIG4MIG1MCygKqAohiZodHRwOi8vY3JsLmRp
c2EubWlsL2NybC9FQ0FST09UQ0EyLmNybDCBhKCBgaB/hn1sZGFwOi8vY3JsLmdkcy5kaXNhLm1p
bC9jbiUzZEVDQSUyMFJvb3QlMjBDQSUyMDIlMmNvdSUzZEVDQSUyY28lM2RVLlMuJTIwR292ZXJu
bWVudCUyY2MlM2RVUz9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0O2JpbmFyeTCB0wYIKwYBBQUH
AQEEgcYwgcMwOgYIKwYBBQUHMAKGLmh0dHA6Ly9jcmwuZGlzYS5taWwvaXNzdWVkdG8vRUNBUk9P
VENBMl9JVC5wN2MwgYQGCCsGAQUFBzAChnhsZGFwOi8vY3JsLmdkcy5kaXNhLm1pbC9jbiUzZEVD
QSUyMFJvb3QlMjBDQSUyMDIlMmNvdSUzZEVDQSUyY28lM2RVLlMuJTIwR292ZXJubWVudCUyY2Ml
M2RVUz9jcm9zc0NlcnRpZmljYXRlUGFpcjtiaW5hcnkwDQYJKoZIhvcNAQEFBQADggEBAIP4M608
IEZJdXBySeHjlgiTtsQTq9xo6icy9Fa/zaJag+SoGitVohk26JAX44c+WsTdOmjnqCROFMwRDz3O
Qa5QBLt5+PGbsZhL+s1L4XLh6+961ALZxMi88jiIcR71uBnZqm3WnImmf0ebnK4N8N8ZJbQfncbj
ZlOOPo5NuVhEi22Mq8LHZd6UMl9xdSVAcHBV0F+sEBPY6S8OwptTz7+XusknKSkVPthJEEYnpHpk
pcBVe9HY2M421E8MSYeXZxuKvEjNMMRk2pkH8lOWU1uKsNCjHQYvK7GJtptFpc5aKbOIgI/jSrSr
qjcybZreD76lb1vZ8lcbHsnG+k22CCAwggVwMIIEWKADAgECAgEPMA0GCSqGSIb3DQEBBQUAME0x
CzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEWMBQG
A1UEAxMNRUNBIFJvb3QgQ0EgMjAeFw0xMTA2MDExMzQzMzNaFw0xNzA1MzAxMzQzMzNaMHAxCzAJ
BgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAGA1UE
CxMZQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0MIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzKf8xTQCX42GoA1+9NcUaSukI0Wu64bUdlPwiBNa
U0gEdQSDX7GDR7dvm4tEh+EsGetV8PYTKgjAT8tOSSaXnqxM9MaQ25Kg89jQ6gZtNq8HXERajlkJ
/Dn9wCySqKQBemUpHhdY+yhQikJSJ7QCMif3Pkx8mSSQ9DbOElK5kJgbJt6tJBJdOpU+zByz07+S
15AfuT2soQCVFhF6v4lBISwwbLU2g9TRjpXiDLL94tV9NWpgfRssDdr/5CpXxrhkKRQFotEGmwuI
TH1IzNte2xkEtP79VVddcwaUZRBMx9MyYEEA11kMvle70Wy2r9myt6FsLzUyRoW9glh2oexa5QID
AQABo4ICNjCCAjIwEgYDVR0TAQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwHQYDVR0OBBYE
FEKc9Lpvbekw1zrWRvSyNO6d0k8mMB8GA1UdIwQYMBaAFO3kh9AnxFDmhDr3zPfrOkn8Uk4hMDMG
A1UdIAQsMCowDAYKYIZIAWUDAgEMATAMBgpghkgBZQMCAQwCMAwGCmCGSAFlAwIBDAMwgcAGA1Ud
HwSBuDCBtTAsoCqgKIYmaHR0cDovL2NybC5kaXNhLm1pbC9jcmwvRUNBUk9PVENBMi5jcmwwgYSg
gYGgf4Z9bGRhcDovL2NybC5nZHMuZGlzYS5taWwvY24lM2RFQ0ElMjBSb290JTIwQ0ElMjAyJTJj
b3UlM2RFQ0ElMmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y2VydGlmaWNhdGVSZXZv
Y2F0aW9uTGlzdDtiaW5hcnkwgdMGCCsGAQUFBwEBBIHGMIHDMDoGCCsGAQUFBzAChi5odHRwOi8v
Y3JsLmRpc2EubWlsL2lzc3VlZHRvL0VDQVJPT1RDQTJfSVQucDdjMIGEBggrBgEFBQcwAoZ4bGRh
cDovL2NybC5nZHMuZGlzYS5taWwvY24lM2RFQ0ElMjBSb290JTIwQ0ElMjAyJTJjb3UlM2RFQ0El
MmNvJTNkVS5TLiUyMEdvdmVybm1lbnQlMmNjJTNkVVM/Y3Jvc3NDZXJ0aWZpY2F0ZVBhaXI7Ymlu
YXJ5MA0GCSqGSIb3DQEBBQUAA4IBAQCD+DOtPCBGSXVwcknh45YIk7bEE6vcaOonMvRWv82iWoPk
qBorVaIZNuiQF+OHPlrE3Tpo56gkThTMEQ89zkGuUAS7efjxm7GYS/rNS+Fy4evvetQC2cTIvPI4
iHEe9bgZ2apt1pyJpn9Hm5yuDfDfGSW0H53G42ZTjj6OTblYRIttjKvCx2XelDJfcXUlQHBwVdBf
rBAT2OkvDsKbU8+/l7rJJykpFT7YSRBGJ6R6ZKXAVXvR2NjONtRPDEmHl2cbirxIzTDEZNqZB/JT
llNbirDQox0GLyuxibabRaXOWimziICP40q0q6o3Mm2a3g++pW9b2fJXGx7JxvpNtgggMIIGOTCC
BSGgAwIBAgICMX0wDQYJKoZIhvcNAQEFBQAwcDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4g
R292ZXJubWVudDEMMAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0
aWVzMRUwEwYDVQQDEwxPUkMgRUNBIFNXIDQwHhcNMTMwNDIzMjA1MDI5WhcNMTYwNDIyMjA1MDI5
WjCBhjELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEMMAoGA1UECxMDRUNB
MQwwCgYDVQQLEwNPUkMxFDASBgNVBAsTC1FvU2llbnQgTExDMSswKQYDVQQDEyJCdWxsYXJkLldp
bGxpYW0uQy5PUkMxMDAwMDM3MTAxLklEMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
uVgzvMTViFK3KLdCW8Ah9TtLt57dyDCaw2yroulxbhKpJVXv5lpLt/h0WFgYdOKOohJn9zA8ngRO
9BRocofISpQmLV/dqJg1a0zrTRHAxbQvJIihZ1/hIcC9/+iA/4ZEKUwVdcd619V70w6+wsh3UIQj
DLJsB7Zrs2bAsEjaJ+SoBCrvNiSCpV6D/32/bV2B/gnZ/5a09jasJEIYGbKVVp9f/SVh8XV5DSSu
ppsb7ZCaKnNgwGLeIpwS3iRa6FqAMJK6K07F5EYeltjXb006U5rwk00dvoqvww3vV/D9sgjeuNYj
va0uKxJ3E8t7p493CG4bzs7SW6aRaFOe5XPANwIDAQABo4ICxDCCAsAwHwYDVR0jBBgwFoAUQpz0
um9t6TDXOtZG9LI07p3STyYwHQYDVR0OBBYEFC7uy3C6OCsNX5V3mBpvbPf/B4keMIIBIwYIKwYB
BQUHAQEEggEVMIIBETAeBggrBgEFBQcwAYYSaHR0cDovL2V2YS5vcmMuY29tMDIGCCsGAQUFBzAC
hiZodHRwOi8vZWNhLm9yYy5jb20vY2FDZXJ0cy9FQ0EtU1c0LnA3YzCBugYIKwYBBQUHMAKGga1s
ZGFwOi8vZWNhLWRzLm9yYy5jb20vY24lM2RPUkMlMjBFQ0ElMjBTVyUyMDQlMmNvdSUzZENlcnRp
ZmljYXRpb24lMjBBdXRob3JpdGllcyUyY291JTNkRUNBJTJjbyUzZFUuUy4lMjBHb3Zlcm5tZW50
JTJjYyUzZFVTP2NBQ2VydGlmaWNhdGU7YmluYXJ5LGNyb3NzQ2VydGlmaWNhdGVQYWlyO2JpbmFy
eTAOBgNVHQ8BAf8EBAMCBsAwHQYDVR0RBBYwFIESY2FydGVyQHFvc2llbnQuY29tMBcGA1UdIAQQ
MA4wDAYKYIZIAWUDAgEMATCB8QYDVR0fBIHpMIHmMCugKaAnhiVodHRwOi8vZWNhLm9yYy5jb20v
Q1JMcy9PUkNFQ0FTVzQuY3JsMIG2oIGzoIGwhoGtbGRhcDovL2VjYS1kcy5vcmMuY29tOjM4OS9j
biUzRE9SQyUyMEVDQSUyMFNXJTIwNCUyQyUyMG91JTNEQ2VydGlmaWNhdGlvbiUyMEF1dGhvcml0
aWVzJTJDJTIwb3UlM0RFQ0ElMkMlMjBvJTNEVS5TLiUyMEdvdmVybm1lbnQlMkMlMjBjJTNEVVM/
Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdDtiaW5hcnkwGwYDVR0JBBQwEjAQBggrBgEFBQcJBDEE
EwJVUzANBgkqhkiG9w0BAQUFAAOCAQEAHi35mJzjiIIok76AITqnPNaWmW8J6CQnss/fVgXpcfAJ
OqM0UX6OEzc638AmGpTL5f3yI0b0daetLCEvOK/4v4Tw9HHTpfHRa1g64JoEDyNgAG/oCH2HDviP
ybd1C1/2OZB969gUoxvd0VdhKFI3ZF/mCCmdv+CBbvTCFpBXkeDkglC9IUHotxu6n+ZqKzZTVn3v
2T+2IwW6Pn++i6Gyak9QBQAKPJWovOlO5y4fS5yjOEshZWCdmkKQOj48oorv09gOfNpFFR9KtlTh
tpal1Lf+7c+XHXMKdrnRvYzYLqdklL27qAze4AiW1/Fj0IRfQ17YiylEE4F2BZSCcOLq0TCCBj4w
ggUmoAMCAQICAjF+MA0GCSqGSIb3DQEBBQUAMHAxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMu
IEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAGA1UECxMZQ2VydGlmaWNhdGlvbiBBdXRob3Jp
dGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0MB4XDTEzMDQyMzIwNTE1MloXDTE2MDQyMjIwNTE1
MlowgYsxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VD
QTEMMAoGA1UECxMDT1JDMRQwEgYDVQQLEwtRb1NpZW50IExMQzEwMC4GA1UEAxMnQnVsbGFyZC5X
aWxsaWFtLkMuT1JDMTAwMDAzNzEwMS5FbmNyeXB0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA0KufbZ9gPXn75bWXHqJsr49YLh0gkRXxWIUg5pUWkpnbqlxKmaXu97U2syVtCThHzzMr
9jb93pGVe9qgqsgeaPmI6UN0NHWlPlkfMZfib4PSmp9gFxDxaTCXGtxBJs1HGR/XHd7d34P17RKv
ucgajz1KkZgp8GMRj2qL1SZAQcZCRt5O4XxVIbl+BL3mKdEtSk24NUtTT9WjwVSHHoonZzsTBbkz
7gBcgP+a7vE/1W9KBAnn0RGtPeqCHz9PUFHhjYGzloKxD8lI4Y+UFX6n5uW56b80LsqV+1mfl5Dy
FwfBegaO69dwtUzcqJ95doauexSFe22y7yU3v+7TcYarRwIDAQABo4ICxDCCAsAwHwYDVR0jBBgw
FoAUQpz0um9t6TDXOtZG9LI07p3STyYwHQYDVR0OBBYEFEmIoE5Wahgjz6mivsXWwtbvptwGMIIB
IwYIKwYBBQUHAQEEggEVMIIBETAeBggrBgEFBQcwAYYSaHR0cDovL2V2YS5vcmMuY29tMDIGCCsG
AQUFBzAChiZodHRwOi8vZWNhLm9yYy5jb20vY2FDZXJ0cy9FQ0EtU1c0LnA3YzCBugYIKwYBBQUH
MAKGga1sZGFwOi8vZWNhLWRzLm9yYy5jb20vY24lM2RPUkMlMjBFQ0ElMjBTVyUyMDQlMmNvdSUz
ZENlcnRpZmljYXRpb24lMjBBdXRob3JpdGllcyUyY291JTNkRUNBJTJjbyUzZFUuUy4lMjBHb3Zl
cm5tZW50JTJjYyUzZFVTP2NBQ2VydGlmaWNhdGU7YmluYXJ5LGNyb3NzQ2VydGlmaWNhdGVQYWly
O2JpbmFyeTAOBgNVHQ8BAf8EBAMCBSAwHQYDVR0RBBYwFIESY2FydGVyQHFvc2llbnQuY29tMBcG
A1UdIAQQMA4wDAYKYIZIAWUDAgEMATCB8QYDVR0fBIHpMIHmMCugKaAnhiVodHRwOi8vZWNhLm9y
Yy5jb20vQ1JMcy9PUkNFQ0FTVzQuY3JsMIG2oIGzoIGwhoGtbGRhcDovL2VjYS1kcy5vcmMuY29t
OjM4OS9jbiUzRE9SQyUyMEVDQSUyMFNXJTIwNCUyQyUyMG91JTNEQ2VydGlmaWNhdGlvbiUyMEF1
dGhvcml0aWVzJTJDJTIwb3UlM0RFQ0ElMkMlMjBvJTNEVS5TLiUyMEdvdmVybm1lbnQlMkMlMjBj
JTNEVVM/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdDtiaW5hcnkwGwYDVR0JBBQwEjAQBggrBgEF
BQcJBDEEEwJVUzANBgkqhkiG9w0BAQUFAAOCAQEAi8sBhl4hOnT1puxe0CiOKgkFfMybOPqCPjfi
/Rm+OVZFk2uCFnTqZBePzqDjkH/SDdv8hZyLySDEoLbJuH8NzW2pHWP7+anW46Bxfpkm4WGf33S7
VorBXhZvwd3kktNzHiX2hEPZs/V4PGhlHMekqcq6TvKxKYWBix5bq0mcaelycj2mC9UTUm3SBwJm
rp83IgUrJgI6Ow+6SQduYQX/KSFxyTXnr6XZzWTo/c6HOH1oG1TlLnX32l7ZlosBdBkK8IhYoWbB
DnDehnii9X2jpFLAH3aPQ379m/kzP2rkIq1DZnNMRwL6Cl4QxNmQZbGCThh8iq3NG4A5pQqd94lf
aDGCAxAwggMMAgEBMHYwcDELMAkGA1UEBhMCVVMxGDAWBgNVBAoTD1UuUy4gR292ZXJubWVudDEM
MAoGA1UECxMDRUNBMSIwIAYDVQQLExlDZXJ0aWZpY2F0aW9uIEF1dGhvcml0aWVzMRUwEwYDVQQD
EwxPUkMgRUNBIFNXIDQCAjF9MAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTEzMDgxNjE3NTcxOFowIwYJKoZIhvcNAQkEMRYEFHPRhVdOtog8
qVXtCA7JNt+SFYaQMIGFBgkrBgEEAYI3EAQxeDB2MHAxCzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9V
LlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAGA1UECxMZQ2VydGlmaWNhdGlvbiBBdXRo
b3JpdGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0AgIxfjCBhwYLKoZIhvcNAQkQAgsxeKB2MHAx
CzAJBgNVBAYTAlVTMRgwFgYDVQQKEw9VLlMuIEdvdmVybm1lbnQxDDAKBgNVBAsTA0VDQTEiMCAG
A1UECxMZQ2VydGlmaWNhdGlvbiBBdXRob3JpdGllczEVMBMGA1UEAxMMT1JDIEVDQSBTVyA0AgIx
fjANBgkqhkiG9w0BAQEFAASCAQCkJiMfCeHBvlXePgsPshFc2dRpua9hvRHCk3GVnY7IAVnRxxe5
YLbyjEspXRhYqnmdB8pkwZasRVlku7Tbt3IgX/vXcFzFLZjnJgTv1ZcCIHcU0PcK12kfP6h5fijz
EhpqfrE43mOILWM8m+aUE/pSsU7WS0T2IDa5kGs6qyIeTQofj7vIdEJDRiYwqeUq0/gYwqeTfiG1
tQQoLxypgkbJICcezOLhTZ6ObvSSn9UpP5DiCDjffS7jEzmbllQoOoL2ktacWy3LNB1cMcsOvXid
GT5S0dksz4MgfYiH/y26rCJ+Su2GZGTAJKUIyY6gO6Sq3IyCrh9e0XPCrR1Ohro0AAAAAAAA

--Apple-Mail=_69F64EE4-81C0-425F-8C9E-CD3C38D0CCEC--

From nico@cryptonector.com  Sat Aug 17 13:21:23 2013
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9348311E8118; Sat, 17 Aug 2013 13:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.777
X-Spam-Level: 
X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JWVU-pwlzAaB; Sat, 17 Aug 2013 13:21:18 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id ACAEF21F8F24; Sat, 17 Aug 2013 13:21:18 -0700 (PDT)
Received: from homiemail-a33.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTP id 99A0A594062; Sat, 17 Aug 2013 13:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=SfHC01VeGpcR2a7dhszw y3a1B1A=; b=aJYor6jdrTNjFuPZtc8wNeQrMhJXHzmsdE0XFcemX9xg8sn6VQ+b RefvzJZ7lrtDO+YdjClrgPITvRIaE3h1NKhr3j+to2lwqOcMOjAtA/Cp6/czu7Bc FWoQ2Pl1dPzJzg//tqpkmtZRc0XXxJUR019eMCcJ2RvjnFqXeLUgcaI=
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a33.g.dreamhost.com (Postfix) with ESMTPSA id E375E594058;  Sat, 17 Aug 2013 13:21:13 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id j17so1844437wiw.5 for <multiple recipients>; Sat, 17 Aug 2013 13:21:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CfjRK02Fhaylr9pd9S72TltO85AbktKPp9TQLZBKdU4=; b=QrLvn+fSZrasQfIzkw6S5GcqS4aItPmWy3MUmI12VjDIGTb7SGjXj7xKMv2UEe1MDE rg0GLSs2jw99C0fJvp8a4GxJ0UWq+oXzN7XFLBnBIBqAJnPLTyMQ/n53Fh2aWKrIPwdc FDw5+/gY9GpnI4DrLYF82zowH0k0hAHGzcmnkkS7b9FnO764yZHYg/KN1YSTd2lAoRiQ O/gm4pGl/2q3+AF80mqU1q11xcRNVhywev4Gua8I0jj6/32wRdAgas6dDIJhGoA3VfAg 8/TmVzILxRnxzBxOU2gEIuIpj5TVse5gQOVVVLn665gI8NbRsA9IRKDJXenTLBiLoNqY x0WA==
MIME-Version: 1.0
X-Received: by 10.180.187.41 with SMTP id fp9mr2643175wic.33.1376770872308; Sat, 17 Aug 2013 13:21:12 -0700 (PDT)
Received: by 10.216.31.193 with HTTP; Sat, 17 Aug 2013 13:21:12 -0700 (PDT)
In-Reply-To: <A1A67BD7-9E24-4A5F-A923-37504E1B1C23@vigilsec.com>
References: <20130812215435.24472.26514.idtracker@ietfa.amsl.com> <F9B17A73-4529-4FBF-BD86-27FDC6DF5AAE@isoc.org> <19670_1376684203_r7GKGfQ0008333_3323B8ED-8465-4F63-95FA-6E401E52D7A3@amsl.com> <1376741389.24016.104.camel@destiny.pc.cs.cmu.edu> <A1A67BD7-9E24-4A5F-A923-37504E1B1C23@vigilsec.com>
Date: Sat, 17 Aug 2013 15:21:12 -0500
Message-ID: <CAK3OfOhkBGEtLWk0GYOkmFhGsYx=ezqznBFUtGe-0T1V52nDvg@mail.gmail.com>
Subject: Re: [rfc-i] [IAOC] Community Input Sought on SOWs for RFC Production Center and RFC Publisher
From: Nico Williams <nico@cryptonector.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Mon, 19 Aug 2013 07:30:35 -0700
Cc: IAOC <iaoc@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, RFC Interest <rfc-interest@rfc-editor.org>, IETF <ietf@ietf.org>, Jeffrey Hutzelman <jhutz@cmu.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, 17 Aug 2013 20:21:23 -0000

Several open-source compilers exist.  It would not be hard to a) make
a library of modules from RFCs (to deal with IMPORTS), b) make a
cgi-bin compiler.  It's not what I do on a daily basis, but if you put
together a cgi-bin where all I need to provide is a command to run on
a file and output warnings and errors, well, I can do that trivially.

From arturo.servin@gmail.com  Mon Aug 19 07:34:50 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3030B11E828A for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 07:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ox5KdfDi-Fe6 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 07:34:49 -0700 (PDT)
Received: from mail-gh0-x230.google.com (mail-gh0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6250C11E8113 for <ietf@ietf.org>; Mon, 19 Aug 2013 07:34:48 -0700 (PDT)
Received: by mail-gh0-f176.google.com with SMTP id z17so874102ghb.7 for <ietf@ietf.org>; Mon, 19 Aug 2013 07:34:48 -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=U1IMgGcIgsy1Z+V8D7jCX9Hxk537A9zeaZVKIfmXhLM=; b=AZTDK6QsDZcGwgJp8ZKRb7zPtObm/UfRmicoelif1Hso6vwcXcvWGbHn1nBpF7cWut fYgt28P3x3IKUUIt/jdzr5twctH8cmNpKYzhDXV0sv0WTmBqkliGOY/0fIcPpEGPnEv9 /S0+3JHWakMhfibsWDDdt5Wnj58/ox31nhNUh9rr5jdXVFB9d3rqdkvbmwBGOS3p/r2i 9P3eEijWU3MJAUQddyX+17FQlChDZesjrgfXiqNDiRc9dCYHNKy8X4LCJbHLzXMv5PCX DIQqC71TiNdEM8KpnfyLI3vBTJZ3yQkURAXhYlSeeJwlvtAEi9eZl0L89Nk2BFh5LEMX ykFQ==
X-Received: by 10.236.28.196 with SMTP id g44mr576558yha.101.1376922887869; Mon, 19 Aug 2013 07:34:47 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (r190-64-26-200.su-static.adinet.com.uy. [190.64.26.200]) by mx.google.com with ESMTPSA id c6sm13931625yhl.22.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 19 Aug 2013 07:34:47 -0700 (PDT)
Message-ID: <52122D03.8060906@gmail.com>
Date: Mon, 19 Aug 2013 11:34:43 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Academic and open source rate
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130818014356.0bb745b8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 14:34:50 -0000

	Academic might work. "Open source" not so much as other mentioned. Does
"Big Corporation" doing Open Source apply?

	I was tempted to propose "non-profit", but also there are organizations
with large budgets. And profit driven ones with not much money.

/as

On 8/18/13 6:21 AM, SM wrote:
> Hi Hadriel,
> At 12:31 16-08-2013, Hadriel Kaplan wrote:
>> I may be misunderstanding you, but I'm proposing we charge "large
>> corporations with large travel budgets" slightly *more* than
>> others.[1]  I'm not suggesting an overhaul of the system.  I'm not
>> proposing they get more attention, or more weight, or any such thing.
> 
> That sounds like the ability to pay.  It might be worth considering
> changing the student rate to an academic and open source rate and
> doubling the rate.  I am not getting into a definition of "academic" or
> "open source" [1].  It is left to the organization to determine whether
> it is a good idea to be honest or try the weasel words [2] approach.
> 
> Regards,
> -sm
> 
> 1. If the IETF is serious about running code (see RFC 6982) it would try
> to encourage open source developers to participate more effectively in
> the IETF.
> 
> 2. weasel words give the impression of taking a firm position while
> avoiding commitment to any specific claim. 

From mansaxel@besserwisser.org  Mon Aug 19 08:05:25 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED11311E82A9; Mon, 19 Aug 2013 08:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JLsE8axdJROK; Mon, 19 Aug 2013 08:05:24 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 475A111E829F; Mon, 19 Aug 2013 08:05:24 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id C10729E98; Mon, 19 Aug 2013 17:05:21 +0200 (CEST)
Date: Mon, 19 Aug 2013 17:05:21 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130819150521.GB21088@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5I6of5zJg18YgZEa"
Content-Disposition: inline
In-Reply-To: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: spfbis@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 15:05:25 -0000

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

Subject: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Pol=
icy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to =
Proposed Standard Date: Mon, Aug 19, 2013 at 06:19:16AM -0700 Quoting The I=
ESG (iesg-secretary@ietf.org)
>=20
> The IESG has received a request from the SPF Update WG (spfbis) to
> consider the following document:
> - 'Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,
>    Version 1'
>   <draft-ietf-spfbis-4408bis-19.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 2013-09-02. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.

I strongly OPPOSE draft-ietf-spfbis-4408bis-19.txt being published as
RFC unless substantial parts are reworked.

* The charter disallows major protocol changes -- removing the SPF RR type
is a direct charter violation; since SPF is being used on the Internet.

* The overloading of the TXT record is a hack at best, aimed at
circumventing DNS management systems vendors that fail to ship
support. Breaking the DNS model with specific resource records is not
the way to get better application support. (besides, the major argument
at the time was "it's so hard and takes ages to get a RR type", which
isn't true anymore and also, the RRtype is allocated, what's the fuss? )

* The empirical data that was gathered and the conclusions from which
that where published as RFC 6686 are IMNSHO flawed and rushed in that they
set far too optimistic deadlines for adaptation before declaring failure.

The IESG should send draft-ietf-spfbis-4408bis-19 back to spfbis wg and tell
the wg that instead of deprecating SPF it should be algorithmically
preferred while maintaining support for TXT.

Thanks,=20
--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
It was a JOKE!!  Get it??  I was receiving messages from DAVID LETTERMAN!!
YOW!!

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

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

iEYEARECAAYFAlISNDEACgkQ02/pMZDM1cXK+gCfYQ1Mv1CHjy9DDn7sA7DC7dF3
b48An1b49Zqf/du3dvN6pmj6in+CEujB
=soFG
-----END PGP SIGNATURE-----

--5I6of5zJg18YgZEa--

From johnl@iecc.com  Mon Aug 19 09:12:58 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6027311E8124 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 09:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level: 
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0t8Bt0v1V63Y for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 09:12:54 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4623A11E812A for <ietf@ietf.org>; Mon, 19 Aug 2013 09:12:53 -0700 (PDT)
Received: (qmail 47639 invoked from network); 19 Aug 2013 16:06:12 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Aug 2013 16:06:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52124274.xn--i8sz2z.k1308; i=johnl@user.iecc.com; bh=cllz/Y/tkjV2g+FZAU6ts0SbkmbaBWxV8eCn4q13w4I=; b=nmndMim0e72pXXCiy0I1vdLRz48r4QtDdbyyfbxMjb+W2QARB07SgN49M3k/mZ+Jm3Pw6GpH6Ou4r3qrOZ+IT0706/Gekez21thCOz5NgWdufLerz2oR6+PRyyzUlgf4lmTjNBiq6lHp0lKYNXp8uhHamMT346Bv+OZbhk2wBg3eX2MV9ReWGKdovDP/4vda4NONRerz2hT/3V+V+0eRboQBvy70qbarhs1Fr9GzrGPMOs6bj5RGsDPLO0HiGeCZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52124274.xn--i8sz2z.k1308; olt=johnl@user.iecc.com; bh=cllz/Y/tkjV2g+FZAU6ts0SbkmbaBWxV8eCn4q13w4I=; b=jfI6fj+NfQ/UKQp0vteMoxv9FHpd2cObTCzof4p5tlxSken3WqblcyH1HPMjs4Jo9jPjUCGOo7K09Ewu4RDttojM829TDH9x7Sl1sj+4Wt/Tb9gUV8BoOdOfz3loRQz7qcUIqnnv1DcupFBQKCdJcqrnhHSqr7oK0aYfpiNCDgAm0TQHi+5F2w3grTp2Cp9Rhl0EL0xgfxuCeHu3yGFJ4pfQ11FrCBFkzKUaYVftcFat2ixD7csYYBRiZoFQydss
Date: 19 Aug 2013 16:05:49 -0000
Message-ID: <20130819160549.61542.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130819150521.GB21088@besserwisser.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: mansaxel@besserwisser.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 16:12:58 -0000

>* The charter disallows major protocol changes -- removing the SPF RR type
>is a direct charter violation; since SPF is being used on the Internet. ...

Uh huh.

$ dig besserwisser.org txt

;; QUESTION SECTION:
;besserwisser.org.		IN	TXT

;; ANSWER SECTION:
besserwisser.org.	86173	IN	TXT	"MN-1334-RIPE"
besserwisser.org.	86173	IN	TXT	"v=spf0x44 be allowed to contaminate the DNS."
besserwisser.org.	86173	IN	TXT	"v=spf0x42 besides, SPF as concept is a layering violation."
besserwisser.org.	86173	IN	TXT	"v=spf0x41 not valid. because SPF records belong in RRtype 99."
besserwisser.org.	86173	IN	TXT	"v=spf0x43 adding insult to injury, this layering violation MUST not "

$ dig besserwisser.org spf

;; QUESTION SECTION:
;besserwisser.org.		IN	SPF

;; ANSWER SECTION:
besserwisser.org.	86140	IN	SPF	"v=spf1 ip6:0::/0 -all"
besserwisser.org.	86140	IN	SPF	"v=spf1 ip4:0.0.0.0/0 -all"

R's,
John



From mansaxel@besserwisser.org  Mon Aug 19 12:05:35 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D592C11E82B8 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.3
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 tagged_above=-999 required=5 tests=[AWL=-1.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7E+Y7E6qWGv for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:05:35 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB3911E8185 for <ietf@ietf.org>; Mon, 19 Aug 2013 12:05:35 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 87D469E98; Mon, 19 Aug 2013 21:05:33 +0200 (CEST)
Date: Mon, 19 Aug 2013 21:05:33 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: John Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130819190533.GA30516@besserwisser.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv"
Content-Disposition: inline
In-Reply-To: <20130819160549.61542.qmail@joyce.lan>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:05:36 -0000

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

Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender=
 Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1)=
 to Proposed Standard Date: Mon, Aug 19, 2013 at 04:05:49PM -0000 Quoting J=
ohn Levine (johnl@taugh.com):
> >* The charter disallows major protocol changes -- removing the SPF RR ty=
pe
> >is a direct charter violation; since SPF is being used on the Internet. =
=2E..
>=20
> Uh huh.

Yes.  The TXT specification is=20

"TXT-DATA        One or more <character-string>s.

TXT RRs are used to hold descriptive text.  The semantics of the text
depends on the domain where it is found."

	(RFC 1035 section 3.3.14.)

There is nothing syntactially worng with those entries. I congratulate
people advocating SPF in TXT records while also writing parsers.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Youth of today!  Join me in a mass rally for traditional mental
attitudes!

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

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

iEYEARECAAYFAlISbH0ACgkQ02/pMZDM1cUx8ACcDHrAManbqTtqz1f+RMwHeWg6
LkEAnRPr7lkwWfEgMEQEAtV0fbzjdDY+
=eDfC
-----END PGP SIGNATURE-----

--ZGiS0Q5IWpPtfppv--

From scott@kitterman.com  Mon Aug 19 12:11:16 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0277821F9A6C for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GyG6ZYa65ViF for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:11:11 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id DAD7321F997B for <ietf@ietf.org>; Mon, 19 Aug 2013 12:11:10 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 9DF6E20E4149; Mon, 19 Aug 2013 15:11:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376939465; bh=4XcZnEn4FWump6U7AnqkqwJKOCyWxAyAEYMc3KX5O00=; h=From:To:Subject:Date:In-Reply-To:References:From; b=HMBh8gTFIkhN0JapTkTns1/VAb31LgpE09SzX92lPdX6yMG3KxVZhgjr3t1DEwaC/ ldK07ZnnZksujmAorMP9wgNzr0xbpsv9q73nEUpEufSz8TNzqJH2CCy+73uF87CPNL FxcWyVMzJhx8kSmMdlcqBhlS2gj3S7Luo2fukleE=
Received: from scott-latitude-e6320.localnet (unknown [209.144.63.76]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 482B120E410F;  Mon, 19 Aug 2013 15:11:04 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Mon, 19 Aug 2013 15:10:59 -0400
Message-ID: <4751241.GTNxysAlzm@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130819190533.GA30516@besserwisser.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:11:16 -0000

On Monday, August 19, 2013 21:05:33 M=E5ns Nilsson wrote:
> Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (=
Sender=20
Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version=
 1) to=20
Proposed Standard Date: Mon, Aug 19, 2013 at 04:05:49PM -0000 Quoting J=
ohn=20
Levine (johnl@taugh.com):
> > >* The charter disallows major protocol changes -- removing the SPF=
 RR
> > >type
> > >is a direct charter violation; since SPF is being used on the Inte=
rnet.
> > >...
> >=20
> > Uh huh.
>=20
> Yes.  The TXT specification is
>=20
> "TXT-DATA        One or more <character-string>s.
>=20
> TXT RRs are used to hold descriptive text.  The semantics of the text=

> depends on the domain where it is found."
>=20
> =09(RFC 1035 section 3.3.14.)
>=20
> There is nothing syntactially worng with those entries. I congratulat=
e
> people advocating SPF in TXT records while also writing parsers.

I did check and the library I help maintain, pyspf, correctly didn't th=
ink any=20
of the TXT records you have published are SPF records.  It's not that h=
ard. =20
Operationally, there are far more problems associated with actually try=
ing to=20
use Type 99 than there are with SPF records in Type TXT.

As Michael Hammer mentioned, we've been through all this before and peo=
ple=20
might want to review the previous WG discussion on the topic.

Scott K

From rjsparks@nostrum.com  Mon Aug 19 12:29:59 2013
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94FDD11E82D8 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:29:59 -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 zcSxy73xotp3 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:29:59 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0A99D11E82D2 for <ietf@ietf.org>; Mon, 19 Aug 2013 12:29:58 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-069-137.mycingular.net [166.147.69.137]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7JJTvEj003046 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Mon, 19 Aug 2013 14:29:58 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5212722F.7080404@nostrum.com>
Date: Mon, 19 Aug 2013 14:29:51 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Anyone having trouble submitting I-Ds?
References: <20130818210406.53318.qmail@joyce.lan>
In-Reply-To: <20130818210406.53318.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 166.147.69.137 is authenticated by a trusted mechanism)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:29:59 -0000

On 8/18/13 4:04 PM, John Levine wrote:
>>> The anti-hijacking feature causes the confirmation email to
>>> only go to the authors listed on the previous version of the document, so
>>> mail was not sent to me and things are working as expected.
>> This behavior is not documented to the user when they submit the document
>> and is therefore a bug.
> It's sort of documented somewhere, but I agree that it's a bug that it
> doesn't tell the submitter what happened.
>
> I reported it as a bug a while ago, dunno where it is in the tracker.
>
I remember that report, but am not finding the corresponding ticket with 
a quick search, so I've entered another to make sure this gets addressed:
<http://trac.tools.ietf.org/tools/ietfdb/ticket/1097>

If it turns out that's a duplicate, that's easy to fix.

RjS

From johnl@taugh.com  Mon Aug 19 12:59:54 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B55311E82D2 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=-0.150,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kW6Tu0HTpj6N for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 12:59:53 -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 976E611E82BA for <ietf@ietf.org>; Mon, 19 Aug 2013 12:59:53 -0700 (PDT)
Received: (qmail 91845 invoked from network); 19 Aug 2013 19:59:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=166c4.52127937.k1308; bh=7kRE0s1LIirmlYQrbhSspCraGZ/R9SC0rtMqgsdFfTw=; b=E1DvQ6AjPyV3KA4JUV4vPtZGKfMkFAb0VnjnCEZxRJbT+RHNRLzftcJsJWCOwi1vayvaW3NuXu41VdWbRZP6tIGlDdeI4cdtXTfDOsoiMFSILSc7M2di+8teuBuvbCqyH4/JhumgC/qv75mzB1+h7LTUhSL8DUwMx9jyHsZBl5V6TRNPlNd3AtjksBxpcHxm1yJqfGLR/HjvMkaF6l17X3ZrjivE6b9zF1epJ2PqF/VmRxL+qnyZpLxHL1HPyLnR
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=166c4.52127937.k1308; bh=7kRE0s1LIirmlYQrbhSspCraGZ/R9SC0rtMqgsdFfTw=; b=cOgKbk6+GnfA1Yc4qKvwXCvusZiIS3ip0FjAzN1UIIA+MqqkC6JIUFoFvLLMqWG3Jv3/Mt2bjGDQyNnye04ki6JnyEjQzCu89b+QhUdTUSDHdrVsQjSz28CvWJf9ogdV0+hX95R7D/x+zCPtOwd02QnUueJwd4XnMItjyrqOf5kv0Pb1A2uhwY0C85egvz2/iSq+VvfCezBRCu9EsFvJFC/CpOHXMrd/FpglZ9d02fv9BJlacPJoJ7RV+3ex6cRc
Received: (ofmipd 127.0.0.1); 19 Aug 2013 19:59:29 -0000
Date: 19 Aug 2013 15:59:50 -0400
Message-ID: <alpine.BSF.2.00.1308191543490.62330@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "=?UTF-8?Q?M=C3=A5ns_Nilsson?=" <mansaxel@besserwisser.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130819190533.GA30516@besserwisser.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; 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: Mon, 19 Aug 2013 19:59:54 -0000

>>> * The charter disallows major protocol changes -- removing the SPF RR type
>>> is a direct charter violation; since SPF is being used on the Internet. ...

The SPF working group discussed this issue at painful, extensive length.

As you saw when you read the WG archives, there is a significant interop 
bug in rfc 4408 in the handling of SPF and TXT records, which (again after 
painful and extension discussion) we decided the least bad fix was to get 
rid of SPF records.  I don't see anything in your note about how else you 
think we should address the interop bug.

In your case it doesn't matter, since your TXT and SPF records make no 
usable assertions, but a lot of people use SPF right now as part of their 
mail stream management.

R's,
John

From ajs@anvilwalrusden.com  Mon Aug 19 13:08:04 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BFA11E82BA; Mon, 19 Aug 2013 13:08:04 -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 5jEGDFnwNCss; Mon, 19 Aug 2013 13:07:59 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id F02CC11E82CB; Mon, 19 Aug 2013 13:07:58 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 3506D8A031; Mon, 19 Aug 2013 20:07:58 +0000 (UTC)
Date: Mon, 19 Aug 2013 16:08:02 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: spfbis@ietf.org, ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130819200802.GI19481@mx1.yitter.info>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20130819150521.GB21088@besserwisser.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, 19 Aug 2013 20:08:04 -0000

Note that I am not the shepherd for this draft, but I am the WG
co-chair.

On Mon, Aug 19, 2013 at 05:05:21PM +0200, MÃ¥ns Nilsson wrote:

> * The charter disallows major protocol changes -- removing the SPF RR type
> is a direct charter violation; since SPF is being used on the Internet.

That argument doesn't work, because the WG had to make a major
protocol change in this area no matter what, since 4408 has an
interoperability problem.  If you wish to argue that the WG decided on
the wrong protocol change, that line is open to you; but nobody can
argue that the change is wrong because of our charter.  

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@resistor.net  Mon Aug 19 13:10:32 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1A6B11E82E4 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 13:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.087, 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 FOPmRc5SwpS8 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 13:10:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2A1511E82D0 for <ietf@ietf.org>; Mon, 19 Aug 2013 13:10:25 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7JKAEsF020393; Mon, 19 Aug 2013 13:10:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376943021; bh=sqGsVb4nO3YzxHzKOAamVhZlYrQcREveXmjAW4KlboQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TeeUZeTrDh30LgsdJb4yiAE/IDnnBGxddWX/wOdD36Wgcq94hv5AMh0LWo8u3PgkF 3OXRa+xiQaHn9Ub0Gy1lqtWjN41COdI6k3Cyb869xT49cxWYbeY7eEL4x8Re0LOtJ/ yM2a/Ks+HQI7nKWJ/Xr5BbSkpl7sVw29LvgBz3qA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376943021; i=@resistor.net; bh=sqGsVb4nO3YzxHzKOAamVhZlYrQcREveXmjAW4KlboQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ChCSiqhpsQ4+BXDKLNTgcfK8/dzOy7jyRd+tDRfAb6yd5gVxhsC5OOHgYv7Ufp2dv 6xECZsro/SBIbH3WqUBZGHC4jOEWIXGsjR1ErQZnAvQxxHTSnc7yWyuV6OjDw/cV5t wjEY9saGwDhUcjjO/+6JM5Bg1kgX4duvl2C5wBgk=
Message-Id: <6.2.5.6.2.20130819074949.0cba8300@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 19 Aug 2013 08:48:47 -0700
To: Arturo Servin <arturo.servin@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Academic and open source rate
In-Reply-To: <52122D03.8060906@gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <52122D03.8060906@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 20:10:33 -0000

Hola Arturo,
At 07:34 19-08-2013, Arturo Servin wrote:
>         Academic might work. "Open source" not so much as other 
> mentioned. Does
>"Big Corporation" doing Open Source apply?
>
>         I was tempted to propose "non-profit", but also there are 
> organizations
>with large budgets. And profit driven ones with not much money.

"Open source" is difficult.  As people pointed out "open source" does 
not necessarily mean free.  "open source" does not necessarily mean 
"non-profit".  I used the term loosely.  If hypothetically speaking, 
there was formal action, a clearer term might be needed.

Irrespective of my views, "big corporation" is what helps the IETF 
operate.  If "big corporation" doing open source applies it will 
become a problem for the IETF.  The main issue is why should the IETF 
subsidize a particular group.  It can also be argued that it is not 
fair to subsidize a particular group.

Regards,
-sm  


From sm@resistor.net  Mon Aug 19 13:10:33 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61BD11E82D0 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 13:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: 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-OH2cJ-mAP8 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 13:10:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 361E411E82E2 for <ietf@ietf.org>; Mon, 19 Aug 2013 13:10:26 -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 r7JKAEsH020393; Mon, 19 Aug 2013 13:10:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376943025; bh=Twm+QtV3N76hHfQQ9rOBfCa0p5J8syW3CCP0l/O/TV0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QHdtB/oARsJMlAA1e7c2AYn6NZPNpE0VdAdv5w9wZFmMjTEEEeOQzR89BGb7PoVo+ vfkF6iqw9V/q8CVo91s2p4ELuaP/0gm1TKgq+KmeOuAWI5Fe/pEkiRpOnqnf9IAewO dgu8oHSUghfHlgdmffXUeQeYgqanWs9s7xw4ojcM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1376943025; i=@resistor.net; bh=Twm+QtV3N76hHfQQ9rOBfCa0p5J8syW3CCP0l/O/TV0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fYhYtMGewkLbjBnYEVe2AG5FybUQ9vhTjEvxwYESDaIQOzwcI9JJs3qDuddYfrI8X VE8eGs5oz8hWZfcaR1RVkHhC26jPjU7aMJnXUuk2IOku9ILLKb0psMgcmN2m24PjFa NYi1BRcg8jmPhODwwPVIRqpBoMjKQTnO2xU4O+Zc=
Message-Id: <6.2.5.6.2.20130819085022.0d3ab910@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 19 Aug 2013 12:49:34 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Academic and open source rate (was: Charging remote participants)
In-Reply-To: <750FC4DACA4B5EF79C93C4C7@JcK-HP8200.jck.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com> <6.2.5.6.2.20130818150230.0d8d8918@resistor.net> <750FC4DACA4B5EF79C93C4C7@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 20:10:33 -0000

Hi John,
At 06:11 19-08-2013, John C Klensin wrote:
>I think this is bogus and takes us down an undesirable path.

Ok.

>First, I note that, in some organizations (including some large
>ones), someone might be working on an open source project one
>month and a proprietary one the next, or maybe both
>concurrently.  Would it be appropriate for such a person (or the
>company's CFO) to claim the lower rate, thereby expecting those
>who pay full rate to subsidize them?  Or would their involvement
>in any proprietary-source activity contaminate them morally and
>require them to pay the full rate?  Second, remember that "open

The above reminds me of the Double Irish with a Dutch sandwich. If I 
was an employee of a company I would pay the regular fee.  If I am 
sponsored by an open source project and my Internet-Draft will have 
that as my affiliation I would claim the lower rate.

>source" is actually a controversial term with some history of
>source being made open and available, presumably for study, but
>with very restrictive licensing rules associated with its
>adaptation or use.

Yes.

>Does it count if the open source software is basically
>irrelevant to the work of the IETF?  Written in, e.g., HTML5?
>Do reference implementations of IETF protocols count more (if
>I'm going to be expected to subsidize someone else's attendance
>at the IETF, I think they should).

This would require setting a demarcation line.  That isn't always a clear line.

A subsidy is a grant or other financial assistance given by one party 
for the support or development of another.  If the lower rate is 
above meeting costs it is not a subsidy.

>Shouldn't we be tying this to the discussion about IPR
>preference hierarchies s.t. FOSS software with no license
>requirements get more points (and bigger discounts) than BSD or
>GPL software, which get more points than FRAND, and so on?

No. :-)

Regards,
-sm 


From johnl@iecc.com  Mon Aug 19 13:43:07 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5511E11E82EB for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 13:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.885
X-Spam-Level: 
X-Spam-Status: No, score=-102.885 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3rFHACnJqgC2 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 13:43:03 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AADD411E82D8 for <ietf@ietf.org>; Mon, 19 Aug 2013 13:43:00 -0700 (PDT)
Received: (qmail 99639 invoked from network); 19 Aug 2013 20:42:59 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Aug 2013 20:42:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52128353.xn--yuvv84g.k1308; i=johnl@user.iecc.com; bh=D1+kPJ9a9oByNsixsCWTTrniOPIcmOy1S3ovsYJRzZ4=; b=VZ1Y89f0hm/YYevCiw2jfasuOmycHjAeraKfmiTyW0VGegoy5D+8mLLhhz7M/Dij2kKtcq3CAOssKspQtX4Xpzk06Yoe0mwvDWofDrXqyxD5LGDDAN4RNHuMw7be25PBbGr+STOInZCW9qq/d+hIOwINKy5UdwgieU8b5oOZV1Rmf/2L/fbvn1EwOLOhJ2qDcBuuEqdO+1G4DTw6Svafuf9P/i9GwfeChKmvfPTzXBjmwjnE7jl5vCrQppUOkOho
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52128353.xn--yuvv84g.k1308; olt=johnl@user.iecc.com; bh=D1+kPJ9a9oByNsixsCWTTrniOPIcmOy1S3ovsYJRzZ4=; b=kEESQbnhZ7k5JsXVIr/TY9ivBcUJLMUlhpRxRKRWo6hgSFRFd8zWNDSmDDzShZQTZ1ytjFv4Pdggir0iKgw0Fvh9mzYYCuOWNa+58z+PvKMxU53n3JPQY7DRAqXDzfWxKqDvm27jrvcwctN46ouXJZfCZWV02gFEZqrcndCZXQJYKefCjKyAsT/DgvLmYeo7d6LCouo2jvTkqlYigT6ogaaup3heuEoqd7EOFSd6hiZTZO0UmBo71GcCl+viZS5f
Date: 19 Aug 2013 20:42:37 -0000
Message-ID: <20130819204237.62528.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130819190533.GA30516@besserwisser.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: mansaxel@besserwisser.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 20:43:07 -0000

>There is nothing syntactially worng with those entries. I congratulate
>people advocating SPF in TXT records while also writing parsers.

None of your TXT records are SPF records because they don't start with
the required version tag.  You have two type 99 records that start
with the version tag, which is invalid under section 3.1.2 of RFC 4408
and the similar section 3.2 of 4408bis.  

So you're publishing no SPF information at all.  I gather that you've
tried the popular SPF implementations like libspf2 and verified that
they correctly report that they found nothing.

I really don't understand what point you're making here.

R's,
John


From sant9442@gmail.com  Mon Aug 19 13:44:33 2013
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 054F811E82D8; Mon, 19 Aug 2013 13:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.359
X-Spam-Level: 
X-Spam-Status: No, score=-1.359 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F86gIJC-bI4V; Mon, 19 Aug 2013 13:44:32 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4B19A11E82EC; Mon, 19 Aug 2013 13:44:29 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so320152wes.19 for <multiple recipients>; Mon, 19 Aug 2013 13:44:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1ixrfPypIwZN+2rh9jWFhKhYdNCvzcfUTjC3uIUctxw=; b=nG6ePkvLZySpI/Iy+fvbM//HKbRYMrRu3uUI2EcpFjMoA1Lw5EhrNCu7fwkn+UZopm qNXI4LtBFS8OTrM0bTiT27jjA/p/Jf0DUoy/Hr35BG4vBsoQ8w1TbeJhCsaNlI4oZHIj 0GnzF2Kz7wk1ybV3aQlCVfFvqrYMZD0hlcKdn14MHxeHMBisI5z4xgCJlt57dYeNIo5D TvRT5xMpJTYuNOC24ahg3EuNKDQH4UzuF8Zx4iZ8Qv+8TaFJ6EoQGh6X801T+/+tGseN bPoYwIZiO4dTqWqQrpJBSHswWq+7chBnHiNaOYyPHGP5PeH8Cef5izw04GyBeIb69eMc l2eA==
MIME-Version: 1.0
X-Received: by 10.194.63.228 with SMTP id j4mr3967238wjs.34.1376945068379; Mon, 19 Aug 2013 13:44:28 -0700 (PDT)
Received: by 10.216.52.198 with HTTP; Mon, 19 Aug 2013 13:44:28 -0700 (PDT)
In-Reply-To: <20130819200802.GI19481@mx1.yitter.info>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info>
Date: Mon, 19 Aug 2013 16:44:28 -0400
Message-ID: <CAEa=Q_XqASMUBeyaL==OjmzcDwUqF-9Oa30aM_VtjxseQsqaEA@mail.gmail.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: HLS <sant9442@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=047d7ba97f3aad13ff04e45301e9
Cc: spfbis@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 20:44:33 -0000

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

I'm having a hard time with both sides of the argument, especially the
supposed existence of a "interop problem" which seems to only to be
highlighted to "procedurally" stump the SPF type advocates.  I don't
believe there was an adequate answer from the advocates of removing the SPF
RR type and the repeated assertion that its been discussed at length has
not resolved the issue because it really hasn't been appropriately address.
 Its not convincing. This is the reason the issue will not go away.

My take is that the the initial MARID design expectations where being met
and to me, that is a very important design consideration in all this; what
were the original expectations with a TXT/SPF migration. Although very
slowly, there were some deployments administratively and technically.

In my estimation, the WG did receive positive support that there was
sincere interest in adding support for the SPF record type primarily
because there was some level of adoption discovered during the "interop"
report work.  You can include us (SSI) as having interest in
enabling/adding SPF record support.

I  recommend the following to basically allow IMPLEMENTATORS to decide:

1) Continue with the TXT/SPF migration plan,

2) Address any technical protocol issue with using an SPF type,

3) Add implementation designs notes on the pros and cons.

This will allow coders to add the optimized logic for usage.  It will also
allow for new problem solving seeds to be laid down. It will hopefully get
the DNS software vendors to finally add direct support for unnamed TYPE
support (query and passthru).

Finally, which is what I have been trying to get - why hasn't the IETF
taking this issue (unnamed type support) very serious? The reason I wonder
because if the DNS vendors don't address this, then to me, that should be
the only reason to remove the SPF type or even bother with any new RR type
concept.  The interop problem cited about RFC 4408 is not convincing to me.
The only reason my package as an early adopter didn't have SPF support was
purely for short term optimizations and lack of servers with unnamed type
processing  support reasons - no mas.

--
HLS



On Mon, Aug 19, 2013 at 4:08 PM, Andrew Sullivan <ajs@anvilwalrusden.com>wr=
ote:

> Note that I am not the shepherd for this draft, but I am the WG
> co-chair.
>
> On Mon, Aug 19, 2013 at 05:05:21PM +0200, M=C3=A5ns Nilsson wrote:
>
> > * The charter disallows major protocol changes -- removing the SPF RR
> type
> > is a direct charter violation; since SPF is being used on the Internet.
>
> That argument doesn't work, because the WG had to make a major
> protocol change in this area no matter what, since 4408 has an
> interoperability problem.  If you wish to argue that the WG decided on
> the wrong protocol change, that line is open to you; but nobody can
> argue that the change is wrong because of our charter.
>
> Best regards,
>
> A
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>



--=20
hls

--047d7ba97f3aad13ff04e45301e9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m having a hard time with both sides of the argument=
, especially the supposed existence of a &quot;interop problem&quot; which =
seems to only to be highlighted to &quot;procedurally&quot; stump the SPF t=
ype advocates. =C2=A0I don&#39;t believe there was an adequate answer from =
the advocates of removing the SPF RR type and the repeated assertion that i=
ts been discussed at length has not resolved the issue because it really ha=
sn&#39;t been appropriately address. =C2=A0Its not convincing. This is the =
reason the issue will not go away. =C2=A0<div>

<br></div><div>My take is that the the initial MARID design expectations wh=
ere being met and to me, that is a very important design consideration in a=
ll this; what were the original expectations with a TXT/SPF migration. Alth=
ough very slowly, there were some deployments administratively and technica=
lly.=C2=A0</div>

<div><br></div><div>In my estimation,=C2=A0the WG did receive positive supp=
ort that there was sincere interest in adding support for the SPF record ty=
pe primarily because there was some level of adoption discovered during the=
 &quot;interop&quot; report work. =C2=A0You can include us (SSI) as having =
interest in enabling/adding SPF record support. =C2=A0=C2=A0</div>

<div><br></div><div>I =C2=A0recommend the following to basically allow IMPL=
EMENTATORS to decide:</div><div><br></div><div>1) Continue with the TXT/SPF=
 migration plan,</div><div><br></div><div>2) Address any technical protocol=
 issue with using an SPF type,</div>

<div><br></div><div>3) Add implementation designs notes on the pros and con=
s.=C2=A0</div><div><br></div><div>This will allow coders to add the optimiz=
ed logic for usage. =C2=A0It will also allow for new problem solving seeds =
to be laid down. It will hopefully get the DNS software vendors to finally =
add direct support for unnamed TYPE support (query and passthru).<br>

</div><div><br></div><div>Finally, which is what I have been trying to get =
- why hasn&#39;t the IETF taking this issue (unnamed type support) very ser=
ious? The reason I wonder because if the DNS vendors don&#39;t address this=
, then to me, that should be the only reason to remove the SPF type or even=
 bother with any new RR type concept. =C2=A0The interop problem cited about=
 RFC 4408 is not convincing to me. The only reason my package as an early a=
dopter didn&#39;t have SPF support was purely for short term optimizations =
and lack of servers with unnamed type processing =C2=A0support reasons - no=
 mas.</div>

<div><br></div><div>--</div><div>HLS</div><div><br></div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Aug 19, 2013 at=
 4:08 PM, Andrew Sullivan <span dir=3D"ltr">&lt;<a href=3D"mailto:ajs@anvil=
walrusden.com" target=3D"_blank">ajs@anvilwalrusden.com</a>&gt;</span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Note that I am not the shepherd for this dra=
ft, but I am the WG<br>
co-chair.<br>
<div class=3D"im"><br>
On Mon, Aug 19, 2013 at 05:05:21PM +0200, M=C3=A5ns Nilsson wrote:<br>
<br>
&gt; * The charter disallows major protocol changes -- removing the SPF RR =
type<br>
&gt; is a direct charter violation; since SPF is being used on the Internet=
.<br>
<br>
</div>That argument doesn&#39;t work, because the WG had to make a major<br=
>
protocol change in this area no matter what, since 4408 has an<br>
interoperability problem. =C2=A0If you wish to argue that the WG decided on=
<br>
the wrong protocol change, that line is open to you; but nobody can<br>
argue that the change is wrong because of our charter.<br>
<br>
Best regards,<br>
<br>
A<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Andrew Sullivan<br>
<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>hls
</div>

--047d7ba97f3aad13ff04e45301e9--

From presnick@qti.qualcomm.com  Mon Aug 19 13:49:33 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C6FD11E82FC; Mon, 19 Aug 2013 13:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.282
X-Spam-Level: 
X-Spam-Status: No, score=-106.282 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 dJFNkHPwyHlO; Mon, 19 Aug 2013 13:49:27 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 20C0011E82EB; Mon, 19 Aug 2013 13:49:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1376945366; x=1408481366; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=HJwcwlVb/h+TZki1Udc4848GKWpUSIWBVyX+e//igyc=; b=f/AaDV/31RoDETFzTWGspi80j74tUFKwJ794XS7rrtgiO3rb0lMlH4E2 w7okEF/iS8ccl2m3hZUz+TuZO23cmO1ZxlXYAROpgaUFutCLSyEKVFLul RJguSImSvOIhpojsKwTbFBUyjdMCsdNO0lzT9YB++dLr5Ppqltf1ld6Lh A=;
X-IronPort-AV: E=McAfee;i="5400,1158,7172"; a="69459219"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 19 Aug 2013 13:49:25 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7172"; a="523607167"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Aug 2013 13:49:23 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Mon, 19 Aug 2013 13:48:39 -0700
Message-ID: <521284A4.4050901@qti.qualcomm.com>
Date: Mon, 19 Aug 2013 15:48:36 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, =?ISO-8859-1?Q?M=E5ns_Nil?= =?ISO-8859-1?Q?sson?= <mansaxel@besserwisser.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>	<20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info>
In-Reply-To: <20130819200802.GI19481@mx1.yitter.info>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.39.5]
Cc: spfbis@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 20:49:33 -0000

Speaking in my capacity as responsible AD for this WG and document, and 
the one who is going to have to judge the consensus of this Last Call 
and report to the IESG.

On 8/19/13 3:08 PM, Andrew Sullivan wrote:

> Note that I am not the shepherd for this draft, but I am the WG
> co-chair.
>
> On Mon, Aug 19, 2013 at 05:05:21PM +0200, Måns Nilsson wrote:
>
>    
>> * The charter disallows major protocol changes -- removing the SPF RR type
>> is a direct charter violation; since SPF is being used on the Internet.
>>      
> That argument doesn't work, because the WG had to make a major
> protocol change in this area no matter what, since 4408 has an
> interoperability problem.  If you wish to argue that the WG decided on
> the wrong protocol change, that line is open to you; but nobody can
> argue that the change is wrong because of our charter.
>    

To reinforce this point: Nowhere does the charter "disallow major 
protocol changes"; words to that effect do not appear in the charter. It 
does say that features in current use cannot be removed, but it also 
says that errors can be corrected. In this case the WG concluded that 
fixing the interoperability problem fell under the auspices of 
"correction of errors". The chairs agreed, and I saw no reason to disagree.

>> * The overloading of the TXT record is a hack at best, aimed at
>> circumventing DNS management systems vendors that fail to ship
>> support. Breaking the DNS model with specific resource records is not
>> the way to get better application support. (besides, the major argument
>> at the time was "it's so hard and takes ages to get a RR type", which
>> isn't true anymore and also, the RRtype is allocated, what's the fuss? )
>>      

This issue *was* considered and extensively discussed on the spfbis 
list. AFAICT, the conclusion the WG came to was *not* based on the 
argument that "it's so hard and takes ages to get an RR type". (Yes, the 
original decision to use TXT included that argument, but that was not 
the basis for the decision in the current WG.) And I don't know that 
anyone in the WG would disagree that "the use of the TXT record is a 
hack". The conclusion was that it was a hack that we are stuck with due 
to the current deployment profile. I think you will have to find 
something that the WG missed in that discussion to be convincing that a 
substantial change is needed.

There is no doubt the consensus in the WG was rough on the above two 
issues, but it was, by my reading, solid.

>> * The empirical data that was gathered and the conclusions from which
>> that where published as RFC 6686 are IMNSHO flawed and rushed in that they
>> set far too optimistic deadlines for adaptation before declaring failure.

I think you're going to need substantially more explanation (and perhaps 
some data) to make a convincing case that RFC 6686 needs to be 
reconsidered, thereby affecting this last call. The above states a 
conclusion, but provides no data or explanation. I don't know how to 
evaluation this.

pr

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


From presnick@qti.qualcomm.com  Mon Aug 19 13:55:27 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E9F21F9EA9; Mon, 19 Aug 2013 13:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.284
X-Spam-Level: 
X-Spam-Status: No, score=-106.284 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 phQk19rjmBnX; Mon, 19 Aug 2013 13:55:22 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3B18B11E8300; Mon, 19 Aug 2013 13:55:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1376945722; x=1408481722; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=u97Vd1UZXIXyxbQ1crEZpKNZgAChr6bluYXkIQ8WKOw=; b=XN8zQgcLvXa0V54xZNY17hDyMGkY8txoq/ritAbMIH+KJBCy9T1NQXBH 2pBCPpv9JX9cSW6vCOt6GQ7/HTSFMA561/aY0CvlmP65xJ99YeorSVJkk t48KY7ZO63TueRqWWvlRDhFaeegi1OzzWRg/zk+dOTATmBQQ86Pnkx+sx E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7172"; a="69460139"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 19 Aug 2013 13:55:13 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7172"; a="587109484"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Aug 2013 13:55:13 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Mon, 19 Aug 2013 13:55:13 -0700
Message-ID: <5212862F.3080507@qti.qualcomm.com>
Date: Mon, 19 Aug 2013 15:55:11 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, =?ISO-8859-1?Q?M=E5ns_Nil?= =?ISO-8859-1?Q?sson?= <mansaxel@besserwisser.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>	<20130819150521.GB21088@besserwisser.org>	<20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com>
In-Reply-To: <521284A4.4050901@qti.qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: spfbis@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 20:55:27 -0000

My apologies: A typo rendering a sentence incoherent that I missed 
before hitting "Send":

On 8/19/13 3:48 PM, Pete Resnick wrote:
>>> * The empirical data that was gathered and the conclusions from which
>>> that where published as RFC 6686 are IMNSHO flawed and rushed in 
>>> that they
>>> set far too optimistic deadlines for adaptation before declaring 
>>> failure.
>
> I think you're going to need substantially more explanation (and 
> perhaps some data) to make a convincing case that RFC 6686 needs to be 
> reconsidered, thereby affecting this last call. The above states a 
> conclusion, but provides no data or explanation. I don't know how to 
> evaluation this.

Of course, I meant, "I don't know how to *evaluate* this."

pr

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


From dhc@dcrocker.net  Mon Aug 19 14:00:37 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7CA21F8540; Mon, 19 Aug 2013 14:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.58
X-Spam-Level: 
X-Spam-Status: No, score=-6.58 tagged_above=-999 required=5 tests=[AWL=0.019,  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 adv326cZSmpB; Mon, 19 Aug 2013 14:00:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 474E421F89D8; Mon, 19 Aug 2013 14:00:10 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7JL022Z008905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Aug 2013 14:00:05 -0700
Message-ID: <5212873B.1010007@dcrocker.net>
Date: Mon, 19 Aug 2013 13:59:39 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>	<20130819150521.GB21088@besserwisser.org>	<20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com>
In-Reply-To: <5212862F.3080507@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 19 Aug 2013 14:00:06 -0700 (PDT)
Cc: spfbis@ietf.org, =?ISO-8859-1?Q?M=E5ns_Nil?= =?ISO-8859-1?Q?sson?= <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 21:00:37 -0000

> On 8/19/13 3:48 PM, Pete Resnick wrote:
>>>> * The empirical data that was gathered and the conclusions from which
>>>> that where published as RFC 6686 are IMNSHO flawed and rushed in
>>>> that they
>>>> set far too optimistic deadlines for adaptation before declaring
>>>> failure.
>>
>> I think you're going to need substantially more explanation (and
>> perhaps some data) to make a convincing case that RFC 6686 needs to be
>> reconsidered, thereby affecting this last call. The above states a
>> conclusion, but provides no data or explanation. I don't know how to
>> evaluation this.
>
> Of course, I meant, "I don't know how to *evaluate* this."


 From earlier exchanges about this concern, the assertion that I recall 
is that 7 years is not long enough, to determine whether a feature will 
be adopted.  That is, failure to gain deployment traction after 7 years 
from the time of publication should not be taken as a sufficient waiting 
period.

I do not recall anyone (else) showing support for that view, but 
certainly not any substantial constituency.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From superuser@gmail.com  Mon Aug 19 14:04:12 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBE2A21F9C99; Mon, 19 Aug 2013 14:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 b3devI204NW3; Mon, 19 Aug 2013 14:04:12 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A485421F8481; Mon, 19 Aug 2013 14:04:11 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w62so1515635wes.15 for <multiple recipients>; Mon, 19 Aug 2013 14:04: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=+4ddx6O5F/ju5AQE0dKT5GrqEnwvOPbrMPngd2i3A+I=; b=B9iNjoHBUajP/yfJWYC83iXEPgYPttkHvlZqlhDyu9pLcLIvhlsH40kDhNaTSLI9aT yALlUQMCxG3XTDyrErP2LbHbFOWCpqKzmXAAXXv8zfolLM7Ply1We20QkWXauxrOCHdA sdGVuMqysRtbzftTxFF6aP8jUscgzdZSCGyDsAoZ3NQuFrH/UOZ4NJcuCZVYEI2aoWNT EvBD/h2qe2DTTldyF309+iSQICdkZIieSBqQctzJbNvostBzMMMlH/IlVq8gKSdBqhyG YwbLmTtnwck4U/xTL0nv+EqiSesD6VexIz0UOA8shiBBmDgqqTkO3l8rDghfSxbEdWm4 SUqg==
MIME-Version: 1.0
X-Received: by 10.180.183.51 with SMTP id ej19mr9886856wic.60.1376946250594; Mon, 19 Aug 2013 14:04:10 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Mon, 19 Aug 2013 14:04:10 -0700 (PDT)
In-Reply-To: <5212873B.1010007@dcrocker.net>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net>
Date: Mon, 19 Aug 2013 14:04:10 -0700
Message-ID: <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c2409e243f5704e4534896
Cc: "spfbis@ietf.org" <spfbis@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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: Mon, 19 Aug 2013 21:04:12 -0000

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

On Mon, Aug 19, 2013 at 1:59 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/19/13 3:48 PM, Pete Resnick wrote:
>
>> * The empirical data that was gathered and the conclusions from which
>>>>> that where published as RFC 6686 are IMNSHO flawed and rushed in
>>>>> that they
>>>>> set far too optimistic deadlines for adaptation before declaring
>>>>> failure.
>>>>>
>>>>
>>> I think you're going to need substantially more explanation (and
>>> perhaps some data) to make a convincing case that RFC 6686 needs to be
>>> reconsidered, thereby affecting this last call. The above states a
>>> conclusion, but provides no data or explanation. I don't know how to
>>> evaluation this.
>>>
>>
>> Of course, I meant, "I don't know how to *evaluate* this."
>>
>
>
> From earlier exchanges about this concern, the assertion that I recall is
> that 7 years is not long enough, to determine whether a feature will be
> adopted.  That is, failure to gain deployment traction after 7 years from
> the time of publication should not be taken as a sufficient waiting period.
>
> I do not recall anyone (else) showing support for that view, but certainly
> not any substantial constituency.
>
>
Moreover:

What is the premise for seven years being "not long enough"?  And what does
constitute "long enough"?  And upon what is that last answer based?

It would be wonderful if the boundaries for this test were written down
somewhere, so that we would've had that information when we did the
research for RFC6686.

-MSK

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

<div dir=3D"ltr">On Mon, Aug 19, 2013 at 1:59 PM, Dave Crocker <span dir=3D=
"ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocke=
r.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 8/19/13 3:48 PM, Pete R=
esnick 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"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
* The empirical data that was gathered and the conclusions from which<br>
that where published as RFC 6686 are IMNSHO flawed and rushed in<br>
that they<br>
set far too optimistic deadlines for adaptation before declaring<br>
failure.<br>
</blockquote></blockquote>
<br>
I think you&#39;re going to need substantially more explanation (and<br>
perhaps some data) to make a convincing case that RFC 6686 needs to be<br>
reconsidered, thereby affecting this last call. The above states a<br>
conclusion, but provides no data or explanation. I don&#39;t know how to<br=
>
evaluation this.<br>
</blockquote>
<br>
Of course, I meant, &quot;I don&#39;t know how to *evaluate* this.&quot;<br=
>
</blockquote>
<br>
<br></div>
>From earlier exchanges about this concern, the assertion that I recall is t=
hat 7 years is not long enough, to determine whether a feature will be adop=
ted. =A0That is, failure to gain deployment traction after 7 years from the=
 time of publication should not be taken as a sufficient waiting period.<br=
>

<br>
I do not recall anyone (else) showing support for that view, but certainly =
not any substantial constituency.<span class=3D"HOEnZb"><font color=3D"#888=
888"><br>
<br></font></span></blockquote><div><br></div><div>Moreover:<br><br></div><=
div>What is the premise for seven years being &quot;not long enough&quot;?=
=A0 And what does constitute &quot;long enough&quot;?=A0 And upon what is t=
hat last answer based?<br>
<br></div><div>It would be wonderful if the boundaries for this test were w=
ritten down somewhere, so that we would&#39;ve had that information when we=
 did the research for RFC6686.<br><br></div><div>-MSK<br></div></div><br>
</div></div>

--001a11c2409e243f5704e4534896--

From dhc@dcrocker.net  Mon Aug 19 14:06:43 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CCFB11E8128; Mon, 19 Aug 2013 14:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.581
X-Spam-Level: 
X-Spam-Status: No, score=-6.581 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zFUCPQ24DTXN; Mon, 19 Aug 2013 14:06:38 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 992B111E82EA; Mon, 19 Aug 2013 14:06:38 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7JL6UEv009011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Aug 2013 14:06:33 -0700
Message-ID: <521288BF.20005@dcrocker.net>
Date: Mon, 19 Aug 2013 14:06:07 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com>
In-Reply-To: <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 19 Aug 2013 14:06:34 -0700 (PDT)
Cc: "spfbis@ietf.org" <spfbis@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>, Dave Crocker <dcrocker@bbiw.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 21:06:43 -0000

On 8/19/2013 2:04 PM, Murray S. Kucherawy wrote:
> Moreover:
>
> What is the premise for seven years being "not long enough"?  And what
> does constitute "long enough"?  And upon what is that last answer based?
>
> It would be wonderful if the boundaries for this test were written down
> somewhere, so that we would've had that information when we did the
> research for RFC6686.


Well, they were written down 15 years ago, but they haven't gained 
traction yet, though I remain hopeful.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hsantos@isdg.net  Mon Aug 19 14:14:36 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FDFD21F92B9 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.453
X-Spam-Level: 
X-Spam-Status: No, score=-101.453 tagged_above=-999 required=5 tests=[AWL=-0.094, BAYES_00=-2.599, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsljT0SCrX1S for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:14:31 -0700 (PDT)
Received: from mail.catinthebox.net (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0B19D21F92CD for <ietf@ietf.org>; Mon, 19 Aug 2013 14:14:29 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5970; t=1376946857; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=Xww1xRK K0v2Eu/uK8tzvdAqO67I=; b=OD0AYzJwLY7A1W7bLEpGIvlFAiE1yWZaSb3II5X TowdVvHc+sydfghO4uKkmUdNmxL/MN0GFctbUGN91SWaUxi/42fI8mac489vleea efjsKeR3/OFLNKsaYVta2J/llsdcKOjBnmCmfPQyO3+lFsVahrtnWYdvDOThhhSH i1JE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 19 Aug 2013 17:14:17 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3409374411.13144.5448; Mon, 19 Aug 2013 17:14:16 -0400
Message-ID: <521289C3.9070500@isdg.net>
Date: Mon, 19 Aug 2013 17:10:27 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: SPF TYPE support
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>	<20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com>
In-Reply-To: <521284A4.4050901@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: spfbis@ietf.org, =?ISO-8859-1?Q?M=E5ns_Nil?= =?ISO-8859-1?Q?sson?= <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 21:14:36 -0000

Hi,

I'm having a hard time with both sides of the argument, especially the 
supposed existence of an "interop problem" which seems to only highlight 
how to "procedurally" stump the SPF type advocates with a "error 
correction" standpoint.   What is that error by the way?

I don't believe there was an adequate answer from the advocates of 
removing the SPF RR type and the repeated assertion that its been 
discussed at length has not been convincing it was appropriately 
addressed. It all seem to be a "Shut up" approach to the problem (always 
suggest that its been discussed already). This seems to be one of the 
reasons why the issue will not go away.

My take is that the initial MARID design expectations were being met. 
This fact is a very important design consideration in all this; the 
original expectation for a TXT/SPF migration, although very slowly, 
there were some deployments administratively (publishers) and 
technically (processors). I would like to point out the lack of a 
majority does not/should not represent a lack of interest.

In my estimation, the WG did receive positive support expressing sincere 
technical interest in adding support for the SPF record type primarily 
because there was some level of adoption discovered during the "interop" 
report work.  Please include us (SSI) as having interest in 
enabling/adding SPF record support.

I recommend the following to be considered to basically allow 
implementators to decide:

1) Continue with the TXT/SPF migration plan, fix up this plan,

2) Address any technical protocol issue with using an SPF type,

3) Add implementation designs notes on the pros and cons.

This will allow coders to add the optimized logic for usage.  It will 
also allow for new problem solving seeds to be laid down. It will 
hopefully get the DNS software vendors to finally add direct support for 
unnamed TYPE support (query and passthru) not only for SPF but for 
future DNS application protocols.

Finally, which is what I have been trying to get - why hasn't the IETF 
taking this issue (unnamed type support) very serious?

This is an integration DNS issue - not just an SPF issue. If the DNS 
vendors don't address this, this, to me, would be the only logical and 
feasible reason to remove the SPF type or even bother with any new RR 
type concept.  The interop problem cited to exist within RFC 4408 is not 
convincing to me.

Overall, as an early adopter, the only reason my package doesn't have 
SPF support was purely for short term optimizations and lack of servers 
with unnamed type processing support - no mas.   If we remove SPF 
support, then we lost it forever.  I don't think we have viewed a 
possible long term solution from an integrated protocol standpoint.

--
HLS



On 8/19/2013 4:48 PM, Pete Resnick wrote:
> Speaking in my capacity as responsible AD for this WG and document, and
> the one who is going to have to judge the consensus of this Last Call
> and report to the IESG.
>
> On 8/19/13 3:08 PM, Andrew Sullivan wrote:
>
>> Note that I am not the shepherd for this draft, but I am the WG
>> co-chair.
>>
>> On Mon, Aug 19, 2013 at 05:05:21PM +0200, Måns Nilsson wrote:
>>
>>> * The charter disallows major protocol changes -- removing the SPF RR
>>> type
>>> is a direct charter violation; since SPF is being used on the Internet.
>> That argument doesn't work, because the WG had to make a major
>> protocol change in this area no matter what, since 4408 has an
>> interoperability problem.  If you wish to argue that the WG decided on
>> the wrong protocol change, that line is open to you; but nobody can
>> argue that the change is wrong because of our charter.
>
> To reinforce this point: Nowhere does the charter "disallow major
> protocol changes"; words to that effect do not appear in the charter. It
> does say that features in current use cannot be removed, but it also
> says that errors can be corrected. In this case the WG concluded that
> fixing the interoperability problem fell under the auspices of
> "correction of errors". The chairs agreed, and I saw no reason to disagree.
>
>>> * The overloading of the TXT record is a hack at best, aimed at
>>> circumventing DNS management systems vendors that fail to ship
>>> support. Breaking the DNS model with specific resource records is not
>>> the way to get better application support. (besides, the major argument
>>> at the time was "it's so hard and takes ages to get a RR type", which
>>> isn't true anymore and also, the RRtype is allocated, what's the fuss? )
>
> This issue *was* considered and extensively discussed on the spfbis
> list. AFAICT, the conclusion the WG came to was *not* based on the
> argument that "it's so hard and takes ages to get an RR type". (Yes, the
> original decision to use TXT included that argument, but that was not
> the basis for the decision in the current WG.) And I don't know that
> anyone in the WG would disagree that "the use of the TXT record is a
> hack". The conclusion was that it was a hack that we are stuck with due
> to the current deployment profile. I think you will have to find
> something that the WG missed in that discussion to be convincing that a
> substantial change is needed.
>
> There is no doubt the consensus in the WG was rough on the above two
> issues, but it was, by my reading, solid.
>
>>> * The empirical data that was gathered and the conclusions from which
>>> that where published as RFC 6686 are IMNSHO flawed and rushed in that
>>> they
>>> set far too optimistic deadlines for adaptation before declaring
>>> failure.
>
> I think you're going to need substantially more explanation (and perhaps
> some data) to make a convincing case that RFC 6686 needs to be
> reconsidered, thereby affecting this last call. The above states a
> conclusion, but provides no data or explanation. I don't know how to
> evaluation this.
>
> pr
>


From ajs@anvilwalrusden.com  Mon Aug 19 14:41:37 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A472121F9FD5 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jKs5+8+Y0LLQ for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:41:31 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C1EB621F9AD8 for <ietf@ietf.org>; Mon, 19 Aug 2013 14:41:31 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id EC3F98A031 for <ietf@ietf.org>; Mon, 19 Aug 2013 21:41:28 +0000 (UTC)
Date: Mon, 19 Aug 2013 17:41:39 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130819214139.GB19946@mx1.yitter.info>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@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, 19 Aug 2013 21:41:37 -0000

I'm not going to copy the spfbis WG list on this, because this is part
of the IETF last call.  No hat.

On Mon, Aug 19, 2013 at 02:04:10PM -0700, Murray S. Kucherawy wrote:
> On Mon, Aug 19, 2013 at 1:59 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> > From earlier exchanges about this concern, the assertion that I recall is
> > that 7 years is not long enough, to determine whether a feature will be
> > adopted.

> What is the premise for seven years being "not long enough"?  And what does
> constitute "long enough"?  And upon what is that last answer based?

I have two observations about this.  First, EDNS0, which is of
significantly greater benefit to DNS operators than the mere addition
of an RRTYPE, took well over 10 years to get widespread adoption.
Second, we all know where IPv6 adoption stands today, and that has
certainly been around longer than 7 years.  So I think it _is_ fair to
say that adoption of features in core infrastructure takes a very long
time, and if one wants to add such features one has to be prepared to
wait.

But, second, I think all of that is irrelevant anyway.  The plain fact
is that, once 4408 offered more than one way to publish a record, the
easiest publication approach was going to prevail.  That's the
approach that uses a TXT record.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From dhc@dcrocker.net  Mon Aug 19 14:47:50 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CAA611E816F for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:47:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKG4IAhBszjh for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:47:45 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 961A311E814B for <ietf@ietf.org>; Mon, 19 Aug 2013 14:47:45 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7JLlbZ2009556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Aug 2013 14:47:41 -0700
Message-ID: <52129262.7070803@dcrocker.net>
Date: Mon, 19 Aug 2013 14:47:14 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info>
In-Reply-To: <20130819214139.GB19946@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 19 Aug 2013 14:47:41 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 21:47:50 -0000

On 8/19/2013 2:41 PM, Andrew Sullivan wrote:
>    So I think it _is_ fair to
> say that adoption of features in core infrastructure takes a very long
> time, and if one wants to add such features one has to be prepared to
> wait.

As long as the generic topic is being commented on...

The difference between a "slow" adoption rate and an adoption rate of 
essentially zero is fundamental.    So yes, a pure single number of 
years can be misleading and needs some sense of whether the is any 
progress at all.

There also needs to be some care about marking the start of the clock, 
given that some technologies have multiple components needed before they 
are worth adopting, and an initial, incomplete set might be published 
before a sufficient set is available.


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From presnick@qti.qualcomm.com  Mon Aug 19 14:48:06 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB1011E8304; Mon, 19 Aug 2013 14:48:06 -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 UAvm8zBpo+Ov; Mon, 19 Aug 2013 14:48:02 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 59B3A11E8301; Mon, 19 Aug 2013 14:47:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1376948879; x=1408484879; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gswrRaznl74WiE6jFjdOp3cow2nHmdFpODk6oU1yAoA=; b=FNvzJxSiThTBzNA/8EEflkKBizB+GBATQBO0gT1rZWHQXnbv3mUp+k1H DuaYPPjePywpiqFSJb3DQ3H+5+6hKz9ns84q+UTj3zyFAeOm1GzcrIk03 K2QDT+umQjQqj0hhvx1/YA1TSKwygYkdV1tA/HrZFBFxu0m3HTOvxeY2C 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,7172"; a="49906240"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 19 Aug 2013 14:47:57 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7172"; a="18249364"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Aug 2013 14:47:57 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Mon, 19 Aug 2013 14:47:57 -0700
Message-ID: <5212928B.3010502@qti.qualcomm.com>
Date: Mon, 19 Aug 2013 16:47:55 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: SPF TYPE support
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>	<20130819150521.GB21088@besserwisser.org>	<20130819200802.GI19481@mx1.yitter.info>	<521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net>
In-Reply-To: <521289C3.9070500@isdg.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: spfbis@ietf.org, =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 21:48:06 -0000

I will let the document shepherd/editor address particular points in 
this and other messages, but on one procedural point:

On 8/19/13 4:10 PM, Hector Santos wrote:
> I don't believe there was an adequate answer from the advocates of 
> removing the SPF RR type...

That's an appropriate issue to raise during Last Call, and I expect the 
shepherd to elaborate on why the WG came to its conclusion, and you to 
follow up with more explanation if you still think it is inadequate. 
However:

> ...and the repeated assertion that its been discussed at length has 
> not been convincing it was appropriately addressed. It all seem to be 
> a "Shut up" approach to the problem (always suggest that its been 
> discussed already). This seems to be one of the reasons why the issue 
> will not go away. 

The above is *not* appropriate to raise. The first part is attributing 
motives to folks, which is out of line. Even if the motives of folks 
asserting these things *were* malicious, I am expected to call the 
consensus on the basis of the technical arguments and to ignore the 
motives, and that is what I plan to do. And the last sentence above is 
trying to divine the psychological state of the IETF as to why or why 
not it continues to discuss an issue, an equally inappropriate and 
unproductive thing to do during Last Call.

Let's stick to issues and not delve into these areas please.

pr

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


From drc@virtualized.org  Mon Aug 19 14:55:20 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F8011E830D for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lF5aTYjCpXD5 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 14:55:11 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 7711D11E8141 for <ietf@ietf.org>; Mon, 19 Aug 2013 14:55:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 0A33F8712A for <ietf@ietf.org>; Mon, 19 Aug 2013 17:54:48 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 01793-01 for <ietf@ietf.org>; Mon, 19 Aug 2013 17:54:47 -0400 (EDT)
Received: from terminus.lan (menlopark.keplers.com [74.93.6.213]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 9897D87128 for <ietf@ietf.org>; Mon, 19 Aug 2013 17:54:46 -0400 (EDT)
From: David Conrad <drc@virtualized.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_4EEBAF9D-3034-4958-ACAC-DE10DC442AC2"; protocol="application/pgp-signature"; micalg=pgp-sha1
Message-Id: <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Mon, 19 Aug 2013 14:54:44 -0700
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320>
To: ietf@ietf.org
In-Reply-To: <4751241.GTNxysAlzm@scott-latitude-e6320>
X-Mailer: Apple Mail (2.1508)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 21:55:20 -0000

--Apple-Mail=_4EEBAF9D-3034-4958-ACAC-DE10DC442AC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On Aug 19, 2013, at 12:10 PM, Scott Kitterman <scott@kitterman.com> =
wrote:
> Operationally, there are far more problems associated with actually =
trying to=20
> use Type 99 than there are with SPF records in Type TXT.

Given the abysmal state of implementation of middleboxes _today_, this =
isn't surprising.  I'm unsure this sad state applies for all future time =
to come.

> As Michael Hammer mentioned, we've been through all this before and =
people=20
> might want to review the previous WG discussion on the topic.

+1

However, despite the operational issues mentioned above and the fact =
that this has been discussed to death, I also strongly oppose the =
deprecation of the SPF record. AFAICT, no one is arguing that =
overloading TXT in the way recommended by this draft is a good idea, =
rather the best arguments appear to be that it is a pragmatic "least =
bad" solution to the fact that (a) people often implement (poorly) the =
very least they can get away with and (b) it can take a very long time =
to fix mistakes on the Internet.=20

Of course, both (a) and (b) can be improved over time.  The argument =
that "it's already been X years and only Y% of implementers have =
supported SPF so we should throw in the towel now" seems specious to me =
since:

1) the SPF type code has been allocated -- it isn't going away or going =
to be reused: deprecation gains nothing from a DNS perspective;
2) pretty much every implementation of name servers supports SPF (to one =
degree or another);
3) there exist implementations of DNS frontend UIs that support SPF and =
since the semantics are identical to TXT, future implementation would =
seem to be trivial if a UI supports TXT; and
4) deprecation of SPF imposes additional complexity on every other =
protocol implementation that uses TXT at the zone apex either now or in =
the future.

In the past, the IETF/IESG has frowned on 'squatting' on port numbers, =
addresses, etc., regardless of the potential operational implications of =
accepting that squattage. I personally feel the use of TXT in this =
context is only marginally different than squatting. In my view, =
deprecating SPF only makes sense if the protocol that would use SPF is =
not going to see further deployment.  Since as far as I know, the point =
of 4408bis is to clarify implementation requirements for future =
implementations, deprecation makes no sense to me.

Regards,
-drc




--Apple-Mail=_4EEBAF9D-3034-4958-ACAC-DE10DC442AC2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSEpQlAAoJEIzZ2DQOJFbKvycH/3kLQddgJHBvTjDbOJg/F/PV
9zWx0iT5Ovf+XEFJhhOD2gRqvo50TzFbKXOa4wKxC1WAxLMzZ0IZx4zY/XnCKD87
PynF3h409s97ddTpncJX+kA8hPaH903MxV0+I/evtV5rvvg7W/i6XB18hs382BNk
auVv5d2OlpIYfwbX77/eyPPo0j8KI6bh0tbA/byafhGEL2rvD4ONAhEH8rYZ6TFu
I/zvNx0fy7OT4vh1I24WqyEUuplPgWgJ5NEj+aS1ABO5RVzTzYAVQ8UlEwcQ9lY/
NNhHHZQkIpnCY5shbLgjCMi7AXbjwaP5sdPG3NaCpiKh/nqPJKuUsVJuUSnxdbc=
=0gRM
-----END PGP SIGNATURE-----

--Apple-Mail=_4EEBAF9D-3034-4958-ACAC-DE10DC442AC2--

From john-ietf@jck.com  Mon Aug 19 15:08:17 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3095911E830B for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.287
X-Spam-Level: 
X-Spam-Status: No, score=-102.287 tagged_above=-999 required=5 tests=[AWL=-0.188, BAYES_00=-2.599, GB_PAYLESS=0.5, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HpvqmlUu-QF4 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:08:11 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5188111E82F9 for <ietf@ietf.org>; Mon, 19 Aug 2013 15:08:06 -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 1VBXcL-000G6E-2Q; Mon, 19 Aug 2013 18:08:05 -0400
Date: Mon, 19 Aug 2013 18:08:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>
Subject: Re: Academic and open source rate (was: Charging remote participants)
Message-ID: <D12AABFF2E7F92C7BD99460F@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20130819085022.0d3ab910@resistor.net>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.co m> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.co m> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <E93D4EE6-B27E-4BA0-9E30-7662E3BF6F47@oracle.com> <6.2.5.6.2.20130818150230.0d8d8918@resistor.net> <750FC4DACA4B5EF79C93C4C7@JcK-HP8200.jck.com> <6.2.5.6.2.20130819085022.0d3ab910@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:08:17 -0000

--On Monday, August 19, 2013 12:49 -0700 SM <sm@resistor.net>
wrote:

>...
>> First, I note that, in some organizations (including some
>> large ones), someone might be working on an open source
>> project one month and a proprietary one the next, or maybe
>> both
>> concurrently.  Would it be appropriate for such a person (or
>> the company's CFO) to claim the lower rate, thereby expecting
>> those who pay full rate to subsidize them?  Or would their
>...

> The above reminds me of the Double Irish with a Dutch
> sandwich. If I was an employee of a company I would pay the
> regular fee.  If I am sponsored by an open source project and
> my Internet-Draft will have that as my affiliation I would
> claim the lower rate.

Without understanding your analogy (perhaps a diversity
problem?), if you are trying to make a distinction between
"employee of a company" and "sponsored by an open source
project", that distinction just does not hold up.  I'm
particular, some of the most important reference implementations
of Internet protocols -- open source, freely available and
usable, well-documented, openly tested, etc.-- have come out of
"companies", even for-profit companies.

If the distinction you are really trying to draw has to do with
poverty or the lack thereof, assuming that, if a large company
imposes severe travel restrictions, its employees should pay
full fare if they manage to get approval, then you are back to
Hadriel's suggestion (which more or less requires that someone
self-identify as "poor") or mine (which involves individual
self-assessment of ability to pay without having to identify the
reasons or circumstances).
 
>...
>> Does it count if the open source software is basically
>> irrelevant to the work of the IETF?  Written in, e.g., HTML5?
>> Do reference implementations of IETF protocols count more (if
>> I'm going to be expected to subsidize someone else's
>> attendance at the IETF, I think they should).
> 
> This would require setting a demarcation line.  That isn't
> always a clear line.

What I'm trying to suggest is that the line will almost always
be unclear and will require case by case interpretation by
someone other than the would-be participant.  I continue to find
any peer evaluation model troubling, especially as long as the
people and bodies who are likely to made the evaluations are
heavily slanted toward a narrow range of participants (and that
will be the case as long as those leadership or evaluation roles
require significant time over long periods).

> A subsidy is a grant or other financial assistance given by
> one party for the support or development of another.  If the
> lower rate is above meeting costs it is not a subsidy.

I note that you used that term in a later message,  More
important, I believe the IAOC has repeatedly assured us that, at
least over a reasonable span of meetings, they never seek to
make a profit on registration fees.  Indeed, I suspect that,
with reasonable accounting assumptions, meetings are always a
net money-loser although not my much and more than others.  Any
decision that some people are going to pay less than others
(including the reduced fee arrangements we already have) is a
decision that some people and groups are going to bear a higher
share of the costs than others.  And that is a subsidy, even by
your definition above.

best,
   john



From scott@kitterman.com  Mon Aug 19 15:25:38 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4574611E81BA for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_PAYLESS=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aFixnpwvhSFc for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:25:33 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id D97F411E8172 for <ietf@ietf.org>; Mon, 19 Aug 2013 15:25:12 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id B752620E410F; Mon, 19 Aug 2013 18:25:10 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376951110; bh=TBzbrRZp9n8KoXocdFlpdlRgidPM//Gx8PwShpOPYZc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XsHB/m/fIWWbYyxhqFeo2iDwfSQWgV25GGiffcNtrTfTW4eUpQf5Zse1JOOVlLMw9 M8Bhdi5GjCPasgG95U3LZg5ksdS4by7yoMAW6iQGxV/YyqQWQUI5YfaLlhLYac8sFZ iTuD6b2GWWYRlt7y+SJE1EVTbXxqrgull42toPEA=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id A082320E40CB;  Mon, 19 Aug 2013 18:25:10 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Academic and open source rate (was: Charging remote participants)
Date: Mon, 19 Aug 2013 18:25:09 -0400
Message-ID: <1536527.ebgBccp97i@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <D12AABFF2E7F92C7BD99460F@JcK-HP8200.jck.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <D12AABFF2E7F92C7BD99460F@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:25:38 -0000

On Monday, August 19, 2013 18:08:00 John C Klensin wrote:
> --On Monday, August 19, 2013 12:49 -0700 SM <sm@resistor.net>
> 
> wrote:
> >...
> >
> >> First, I note that, in some organizations (including some
> >> large ones), someone might be working on an open source
> >> project one month and a proprietary one the next, or maybe
> >> both
> >> concurrently.  Would it be appropriate for such a person (or
> >> the company's CFO) to claim the lower rate, thereby expecting
> >> those who pay full rate to subsidize them?  Or would their
> >
> >...
> >
> > The above reminds me of the Double Irish with a Dutch
> > sandwich. If I was an employee of a company I would pay the
> > regular fee.  If I am sponsored by an open source project and
> > my Internet-Draft will have that as my affiliation I would
> > claim the lower rate.
> 
> Without understanding your analogy (perhaps a diversity
> problem?), if you are trying to make a distinction between
> "employee of a company" and "sponsored by an open source
> project", that distinction just does not hold up.  I'm
> particular, some of the most important reference implementations
> of Internet protocols -- open source, freely available and
> usable, well-documented, openly tested, etc.-- have come out of
> "companies", even for-profit companies.
> 
> If the distinction you are really trying to draw has to do with
> poverty or the lack thereof, assuming that, if a large company
> imposes severe travel restrictions, its employees should pay
> full fare if they manage to get approval, then you are back to
> Hadriel's suggestion (which more or less requires that someone
> self-identify as "poor") or mine (which involves individual
> self-assessment of ability to pay without having to identify the
> reasons or circumstances).
> 
> >...
> >
> >> Does it count if the open source software is basically
> >> irrelevant to the work of the IETF?  Written in, e.g., HTML5?
> >> Do reference implementations of IETF protocols count more (if
> >> I'm going to be expected to subsidize someone else's
> >> attendance at the IETF, I think they should).
> > 
> > This would require setting a demarcation line.  That isn't
> > always a clear line.
> 
> What I'm trying to suggest is that the line will almost always
> be unclear and will require case by case interpretation by
> someone other than the would-be participant.  I continue to find
> any peer evaluation model troubling, especially as long as the
> people and bodies who are likely to made the evaluations are
> heavily slanted toward a narrow range of participants (and that
> will be the case as long as those leadership or evaluation roles
> require significant time over long periods).
> 
> > A subsidy is a grant or other financial assistance given by
> > one party for the support or development of another.  If the
> > lower rate is above meeting costs it is not a subsidy.
> 
> I note that you used that term in a later message,  More
> important, I believe the IAOC has repeatedly assured us that, at
> least over a reasonable span of meetings, they never seek to
> make a profit on registration fees.  Indeed, I suspect that,
> with reasonable accounting assumptions, meetings are always a
> net money-loser although not my much and more than others.  Any
> decision that some people are going to pay less than others
> (including the reduced fee arrangements we already have) is a
> decision that some people and groups are going to bear a higher
> share of the costs than others.  And that is a subsidy, even by
> your definition above.

Speaking as someone who is self-employed and a Free/Open Source software 
developer:

The actual price of the IETF admission is the smallest part of the economic 
burden associated with attendance.  It's not just the travel/hotel (as John 
Levine mentioned), but also consulting revenue forgone.  Even if the price 
were zero, it wouldn't materially affect my willingness to take time off and 
travel to an IETF meeting.  Even though I've participated in several IETF 
working groups, I've never been to a meeting and really don't expect to come.  
The value proposition isn't there (for me).

I have participated remotely and it was ~fine.  Taking an hour out of my day 
for something I'm interested in has a completely different cost/benefit ratio 
that a week of travel.  For someone who's used to participating in distributed 
development efforts, an IETF working group session isn't so hard to do as long 
as the people in the room are mindful of the remote participants.

I wouldn't worry too much about finding a special rate for F/OSS developers.  
The only time it might make a difference, IME, is for people who are local to 
the meeting venue and the IETF should already be working on attracting local 
participants, F/OSS developers or not.

Scott K

From scott@kitterman.com  Mon Aug 19 15:39:13 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A189511E8193 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=0.250,  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 HcaqfGLJphcM for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:39:02 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id E62B211E8159 for <ietf@ietf.org>; Mon, 19 Aug 2013 15:39:00 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 0C6E220E410F; Mon, 19 Aug 2013 18:38:44 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376951924; bh=rKu9jXqq7OTt9JFww68iZP+HzAe7uQKkC2blt16LAdY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Cz33ZccRBuWyvMbyr9+mADQfFGK/2qlw/vwJNzty97LtCszWLPzg46Pxvnp5XK4nn w75JhNiLmd+yTL7SvhgVYPYoUTwoe9jPNjeD37+bbrpynp0vx1Qk6mo3Ilxf8zIBtY pYdWsTlr8MajD9hPSu8Qdg1QPtRbcwi4bGXvY3ks=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id DEDFC20E40CB;  Mon, 19 Aug 2013 18:38:43 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Mon, 19 Aug 2013 18:38:43 -0400
Message-ID: <3838694.73Ou9CL5uf@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>
References: <20130819150521.GB21088@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2807556.Nq54VVYpvy"; micalg="pgp-sha1"; protocol="application/pgp-signature"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:39:13 -0000

--nextPart2807556.Nq54VVYpvy
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Monday, August 19, 2013 14:54:44 David Conrad wrote:
> Hi,
> 
> On Aug 19, 2013, at 12:10 PM, Scott Kitterman <scott@kitterman.com> wrote:
> > Operationally, there are far more problems associated with actually trying
> > to use Type 99 than there are with SPF records in Type TXT.
> 
> Given the abysmal state of implementation of middleboxes _today_, this isn't
> surprising.  I'm unsure this sad state applies for all future time to come.
> > As Michael Hammer mentioned, we've been through all this before and people
> > might want to review the previous WG discussion on the topic.
> 
> +1
> 
> However, despite the operational issues mentioned above and the fact that
> this has been discussed to death, I also strongly oppose the deprecation of
> the SPF record. AFAICT, no one is arguing that overloading TXT in the way
> recommended by this draft is a good idea, rather the best arguments appear
> to be that it is a pragmatic "least bad" solution to the fact that (a)
> people often implement (poorly) the very least they can get away with and
> (b) it can take a very long time to fix mistakes on the Internet.
> 
> Of course, both (a) and (b) can be improved over time.  The argument that
> "it's already been X years and only Y% of implementers have supported SPF
> so we should throw in the towel now" seems specious to me since:
> 
> 1) the SPF type code has been allocated -- it isn't going away or going to
> be reused: deprecation gains nothing from a DNS perspective; 2) pretty much
> every implementation of name servers supports SPF (to one degree or
> another); 3) there exist implementations of DNS frontend UIs that support
> SPF and since the semantics are identical to TXT, future implementation
> would seem to be trivial if a UI supports TXT; and 4) deprecation of SPF
> imposes additional complexity on every other protocol implementation that
> uses TXT at the zone apex either now or in the future.
> 
> In the past, the IETF/IESG has frowned on 'squatting' on port numbers,
> addresses, etc., regardless of the potential operational implications of
> accepting that squattage. I personally feel the use of TXT in this context
> is only marginally different than squatting. In my view, deprecating SPF
> only makes sense if the protocol that would use SPF is not going to see
> further deployment.  Since as far as I know, the point of 4408bis is to
> clarify implementation requirements for future implementations, deprecation
> makes no sense to me.

Possibly because your 'a' and 'b' strawman don't reflect the working group's 
rationale.  As previously mentioned, it's in the archives.

Scott K
--nextPart2807556.Nq54VVYpvy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

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

iEYEABECAAYFAlISnnMACgkQHajaM93NaGqEcACeJZkzdf0BZmh5dCoZpkF5Y9QD
tzcAoI5DTEE4iWga8ihxXCZkXK5tseGL
=wAFg
-----END PGP SIGNATURE-----

--nextPart2807556.Nq54VVYpvy--


From johnl@iecc.com  Mon Aug 19 15:58:37 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC14E11E818D for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:58:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.849
X-Spam-Level: 
X-Spam-Status: No, score=-102.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBJol1eRkcXG for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:58: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 49D0611E8175 for <ietf@ietf.org>; Mon, 19 Aug 2013 15:58:33 -0700 (PDT)
Received: (qmail 24910 invoked from network); 19 Aug 2013 22:58:32 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 19 Aug 2013 22:58:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5212a318.xn--hew.k1308; i=johnl@user.iecc.com; bh=dctAc47gcn44H2vUPEzx08ox7umN/a+nIXenHLibNck=; b=c97QqDPPrTlJ454SBmyrB3/2M722o1WAQ4A5Ul66dBsGqJw6wu3EN/qNUDhrbVaYGF0hxAevXamcMaU2wj6wl/K30bT33Sx+n4A8tjYe6jzTGu6bxLaJN41qPpSoP9i3Gg6/eV/4cnpNCFc1x56ZBLb8k06P5ADCViKXZsNxT8WIFf8JFU13VqYfKB4ZpUstlGMPFJ/EL8ZCZ6PyCJekq65gtkG5cQTsm1eSw/TK9Bd31wGVTXidPLKuT+qkEppE
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5212a318.xn--hew.k1308; olt=johnl@user.iecc.com; bh=dctAc47gcn44H2vUPEzx08ox7umN/a+nIXenHLibNck=; b=tnCYYAiEUo/R8n8cQjLTdMJhWvKWgVpc9Lxf3Bs36/LBRdfhMmxCPq3FXandANWjY9vFOZxJqracd42SHw7cPfgEXTM5ICsqXmPp20EUKgw7gvohiwgiNohUcC3EO9GqM9yT/0zM6luiRhzhi5bgJir3fwvOqdbC/0pNSUbpVEMx9PLTZLIOAVuQJPU5yB9P6KHzrhqsoe2h5qJymz6QS0zQqarkGO8cneABG/NcIQrrrI5UEN6bVEi5rZ8U9/Nb
Date: 19 Aug 2013 22:58:10 -0000
Message-ID: <20130819225810.63086.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:58:37 -0000

>AFAICT, no one is arguing that overloading TXT in the
>way recommended by this draft is a good idea, rather the best arguments appear to be that it is a pragmatic
>"least bad" solution to the fact that (a) people often implement (poorly) the very least they can get away
>with and (b) it can take a very long time to fix mistakes on the Internet. 

Neither of those are the reason the WG dropped type 99 records.  The
actual reason has been discussed at length, and was most recently
described earlier today in this thread.

Once again, I really don't understand what the point is here.

R's,
John

From sm@elandsys.com  Mon Aug 19 16:48:54 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6BE11E81A2; Mon, 19 Aug 2013 16:48: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=[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 e12fMdPBfJqb; Mon, 19 Aug 2013 16:48:54 -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 070C811E81CA; Mon, 19 Aug 2013 16:48:51 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.26]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7JNmSFU000073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 16:48:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376956127; bh=Xpbdv8WaJBbH6yb3/jO9GLiat9Ff/VGjQOZm3Ah6qjk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HRt8HnEEl672W/fUpI0Lv2/p6K/CIVLBYddgup5QnUwXuIesEiWsTvfdnO+clWL/C +vqvAg6lagV27wBN0AaARZJirleAMXxaxhgElwqXpij75xNYjbsqjutErloW1xOeq1 d/9hlpL+vSJGpnJpVJYHN1vqSYAo+vgyGUMJlIJQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1376956127; i=@elandsys.com; bh=Xpbdv8WaJBbH6yb3/jO9GLiat9Ff/VGjQOZm3Ah6qjk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ai1ZgEZvR3DKAkdH+AgZEEM+82/LC8qTxUM6bJ6cmkb/4yt1pzzhfDTVLen708KIW /YxiOgPthn4JFQ6e0IVb3Cifz8Ug0RcWP5tba0cygTNTvLveLI68JmWeyvlioU5ml2 MsLnMOIhJ4vyeKN+1M88MK4SwguyEt9P9DpBVMx8=
Message-Id: <6.2.5.6.2.20130819151912.0b861e98@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 19 Aug 2013 16:42:42 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: SPF TYPE support
In-Reply-To: <521289C3.9070500@isdg.net>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 23:48:54 -0000

Hi Hector,
At 14:10 19-08-2013, Hector Santos wrote:
>I'm having a hard time with both sides of the argument, especially 
>the supposed existence of an "interop problem" which seems to only 
>highlight how to "procedurally" stump the SPF type advocates with a 
>"error correction" standpoint.   What is that error by the way?

In a message dated February 27, 2012, the SPFBIS Chairs commented 
that the discussion about Issue #9 (SPF RRTYPE) has revealed an 
interoperability concern in the existing RFC (4408).

 From RFC 6686:

   "RFC 4408 itself included a faulty transition plan, likely because of
    the late addition of a requirement to develop one -- it said:

       An SPF-compliant domain name SHOULD have SPF records of both RR
       types.  A compliant domain name MUST have a record of at least
       one type.

    which means both can claim to be fully compliant while failing
    utterly to interoperate."

The consensus of the SPFBIS WG was that this is an interoperability 
issue and it would have to be corrected.  That is what was considered 
as an error correction.

>I don't believe there was an adequate answer from the advocates of 
>removing the SPF RR type and the repeated assertion that its been 
>discussed at length has not been convincing it was appropriately 
>addressed. It all seem to be a "Shut up" approach to the problem 
>(always suggest that its been discussed already). This seems to be 
>one of the reasons why the issue will not go away.

I personally do not think that it is appropriate to ask any working 
group participant to "shut up".  I welcome hearing arguments and I 
expect a working group to carefully consider them.

Regards,
S. Moonesamy (as document shepherd) 


From Ted.Lemon@nominum.com  Mon Aug 19 17:16:12 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9272A11E8306; Mon, 19 Aug 2013 17:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.585
X-Spam-Level: 
X-Spam-Status: No, score=-106.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id auiyXffX+CXY; Mon, 19 Aug 2013 17:16:04 -0700 (PDT)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id AA0D211E8186; Mon, 19 Aug 2013 17:16:02 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUhK1QrfikoBIor7fjl2JxChARSKJZjrT@postini.com; Mon, 19 Aug 2013 17:16:02 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2DD891B827D; Mon, 19 Aug 2013 17:16:02 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1200A19006C; Mon, 19 Aug 2013 17:16:02 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Mon, 19 Aug 2013 17:16:02 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: [spfbis] SPF TYPE support
Thread-Topic: [spfbis] SPF TYPE support
Thread-Index: AQHOnSEdAUqJkK3Ia0WBBOtw9V8i3Jmdr/wA
Date: Tue, 20 Aug 2013 00:16:01 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077525C6EC@mbx-01.win.nominum.com>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net>
In-Reply-To: <521289C3.9070500@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <1902D2A849168A468FAF5616FEF2AF84@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<spfbis@ietf.org>" <spfbis@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 20 Aug 2013 00:16:14 -0000

On Aug 19, 2013, at 5:10 PM, Hector Santos <hsantos@isdg.net> wrote:
> This will allow coders to add the optimized logic for usage.  It will als=
o allow for new problem solving seeds to be laid down. It will hopefully ge=
t the DNS software vendors to finally add direct support for unnamed TYPE s=
upport (query and passthru) not only for SPF but for future DNS application=
 protocols.

It would help if you would go review the working group discussion on this p=
oint; if you had done so, I do not believe you could make this point with a=
 straight face, because it was soundly refuted by the working group.   I tr=
ied to make the same point to the working group, and they successfully argu=
ed me around.   Although I'm sure you're aware that I am quite stubborn, it=
's possible that they would not succeed in arguing you around as they did m=
e.  But you ought at least to do us the service of allowing them to try by =
reviewing the discussion yourself.


From marka@isc.org  Mon Aug 19 18:27:52 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BA821F968B for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 18:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.055
X-Spam-Level: 
X-Spam-Status: No, score=-2.055 tagged_above=-999 required=5 tests=[AWL=0.544,  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 CvfImEGHsZeD for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 18:27:47 -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 3199621F8EE6 for <ietf@ietf.org>; Mon, 19 Aug 2013 18:27:47 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 72CC0C949D; Tue, 20 Aug 2013 01:27:32 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1376962066; bh=6zd+gchOB63Raf2rW4xnU6qK0nBtRoz55uWWz5+fu5A=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=qIcAwJ72n3A5evKVz2BDfwhi7j1QghJf1i9NphP2EU3GE1Ip6UY0vGuso8LixIxkp casONnOIHT24sZhhS1CK0CxWjAPORgthbeeeNSgVMkHlDebkYakKJ/szoeFDmseQ9B Qrn69LI71zKzWAv57ypt7eZKux/YQkfDzoPh/kig=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue, 20 Aug 2013 01:27:32 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 2E8BA160219; Tue, 20 Aug 2013 01:27:36 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id CAF36160127; Tue, 20 Aug 2013 01:27:35 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 47C5C38B03BB; Tue, 20 Aug 2013 11:27:26 +1000 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Mon, 19 Aug 2013 17:41:39 -0400." <20130819214139.GB19946@mx1.yitter.info>
Date: Tue, 20 Aug 2013 11:27:25 +1000
Message-Id: <20130820012726.47C5C38B03BB@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 01:27:52 -0000

In message <20130819214139.GB19946@mx1.yitter.info>, Andrew Sullivan writes:
> I'm not going to copy the spfbis WG list on this, because this is part
> of the IETF last call.  No hat.
> 
> On Mon, Aug 19, 2013 at 02:04:10PM -0700, Murray S. Kucherawy wrote:
> > On Mon, Aug 19, 2013 at 1:59 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> 
> > > From earlier exchanges about this concern, the assertion that I recall is
> > > that 7 years is not long enough, to determine whether a feature will be
> > > adopted.
> 
> > What is the premise for seven years being "not long enough"?  And what does
> > constitute "long enough"?  And upon what is that last answer based?
> 
> I have two observations about this.  First, EDNS0, which is of
> significantly greater benefit to DNS operators than the mere addition
> of an RRTYPE, took well over 10 years to get widespread adoption.
> Second, we all know where IPv6 adoption stands today, and that has
> certainly been around longer than 7 years.  So I think it _is_ fair to
> say that adoption of features in core infrastructure takes a very long
> time, and if one wants to add such features one has to be prepared to
> wait.
> 
> But, second, I think all of that is irrelevant anyway.  The plain fact
> is that, once 4408 offered more than one way to publish a record, the
> easiest publication approach was going to prevail.  That's the
> approach that uses a TXT record.

Except you are trying to unring a bell.  The SPF type exists and
is supported in nameservers, resolver libraries and in SPF specific
libraries.  Support is integrated into SMTP servers.  Basically it
is all there.  Deployment is happening.  More and more SMTP servers
are making SPF requests before TXT requests.

There was no rush to migrate to the new type.  Suddenly there is a
"oh we have not moved fast enough" so we need to abandon the migration
for lots of really spurious reasons.

* RFC 4408 allows to publish records that might not be read by a
client.  This isn't actually bad.  At some point you have to drop
support for legacy users.  RFC 4408 *allows* this to happen.  The
worst that happens is a forgery isn't detected but we don't guarentee
to stop all forgeries.

* SPF and TXT records may get out of sync.  If we really need to do
something about this we can request that nameserver vendors keep these
records in sync but in reality the SPF record will be the one that
get used more and more and TXT record will not be looked up at all
if we just let the migration continue.

* SPF lookups fail or are slow.  So do TXT lookups.  Most of these
are due to misconfigured nameservers that return the wrong SOA
record as they are configured to server a parent zone rather than
the delegated zone or load balancers which are not RFC 1034 compliant
as they don't respond to anything other than a limited set of types.

* Nameservers don't support SPF.  Most currently shipping nameservers
do support SPF and have for years.  Some OS vendors are slow to
pickup new nameservers which doesn't help.  Of those that don't
support SPF moving from experimental to standard will/should help
with getting the support added.

* Resolver libraries don't support SPF lookups.  Such libraries are
not RFC 1034 compliant as support for lookups of unknown types is
a explictly listed requirement.  Most resolver libraries are capable
of looking up unknown types though they can only present them as a
blob of data.

* Registrars don't support type SPF records.  Shop around there are
those that do.

TXT was described as legacy in RFC 4408.  The spf specific libraries
look for SPF first then TXT if a SPF RR is not present which is
exactly what you would expect when TXT is described as legacy.

You also have a problem that "SPF record" means two things if we
stop the migration.  The TXT record with "v=spf1" at the start and
the type SPF record that is deprecated.

There are other problems like undoing all the changes to support
type SPF.  You need to modify all the servers that now support SPF
to warn / fail to load if they see a SPF record in a zone.

Note it doesn't help that companies charge extra to support SPF
over TXT as you well know.

RFC 4408 treated the SPF type as a foot note.  All the examples
were done using TXT not SPF with the exception of the single example
showing identical TXT and SPF records.  When all the examples are
done with TXT how do you expect people to know that they should be
using type SPF?

Lots of people were not aware of the SPF type.  Named now warns
when both TXT and SPF versions of SPF records are not present and
it could be made into a failure unless the test is explicitly
downgraded to a warning or disabled.

The code could also be extended to enforce consistancy between the
two types of records when present.  I'm willing to write the code
for named.

Mark

> Best,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ajs@anvilwalrusden.com  Mon Aug 19 19:22:22 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488EE11E8328 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 19:22:22 -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 jJ5hOmeBptJc for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 19:22:16 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 7B48811E8155 for <ietf@ietf.org>; Mon, 19 Aug 2013 19:22:15 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 45A2D8A031 for <ietf@ietf.org>; Tue, 20 Aug 2013 02:22:14 +0000 (UTC)
Date: Mon, 19 Aug 2013 22:22:09 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130820022209.GA56138@mx1.yitter.info>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info> <20130820012726.47C5C38B03BB@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130820012726.47C5C38B03BB@drugs.dv.isc.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: Tue, 20 Aug 2013 02:22:22 -0000

Again, I'm not the shepherd on this, but I was involved in the
consensus call in the WG when we determined that the WG wanted to
deprecate use of RRTYPE 99.  (Note that this "deprecation" means just
that users of SPF stop publishing that record.  There's nothing in the
draft to remove the RRTYPE, as that would be absurd.)

On Tue, Aug 20, 2013 at 11:27:25AM +1000, Mark Andrews wrote:
> Deployment is happening.  More and more SMTP servers
> are making SPF requests before TXT requests.

I think those are the two central premises that are up for dispute.
RFC 6686 made the determination about the former claim, and therefore
that premise is not up for debate: deployment appears not to be
happening.  If people wish to argue with the conclusions of RFC 6686,
that's fine, but it seems that one at least needs to write an
anti-6686 document in that case.  The draft currently up for last call
is relying on the conclusions of RFC 6686 as a premise, and is not
itself arguing whether RRTYPE 99 deployment is or is not happening.

The fact that SPF processors are making SPF queries before TXT queries
is in fact part of the reasoning for why RRTYPE 99 ought to be
deprecated.  If many clients make a query and only a tiny number of
zones have that type published (or are likely ever to publish the
type), it's simply wasteful to continue using that type.  If this
seems a familiar line of argument, it's because it's one you see in
the spfbis list archives when this issue was decided by the WG.
 
> Note it doesn't help that companies charge extra to support SPF
> over TXT as you well know.

I'm not sure whether that's supposed to be a swipe at my employer, but
just so we're clear: Dyn (my employer) supports the SPF RRTYPE in its
enterprise-focussed offerings.  There's no extra charge.

The front end for the basic DNS service (many people know this as
DynDNS or Dyn's Standard DNS or other such trade names) is intended to
be simple and self-service.  It's cheap, and the margins don't allow
us to provide a lot of personalized support.  Dyn found that people
who were good candidate customers for that self-service system knew
how to do things with TXT, did not know about or care about the SPF
type, and were confused by having two types for one purpose.  For
practical purposes, it was necessary to support SPF over TXT (since
some clients didn't check the SPF type).  So, one type it was, and TXT
at that.  This all happened long before I worked at Dyn, but I assure
you that the commercial pressure for adding TYPE 99 support to the
basic platform (actually, it's just the front end) is just as
non-existent today as it was when that decision was made.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From mansaxel@besserwisser.org  Mon Aug 19 19:49:24 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 500F611E819C for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 19:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5 tests=[AWL=-0.500,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjF0X7RzgTUE for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 19:49:23 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF5B11E8328 for <ietf@ietf.org>; Mon, 19 Aug 2013 19:49:22 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 119DE9E98; Tue, 20 Aug 2013 04:49:15 +0200 (CEST)
Date: Tue, 20 Aug 2013 04:49:15 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: John R Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130820024914.GB30516@besserwisser.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <alpine.BSF.2.00.1308191543490.62330@joyce.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1308191543490.62330@joyce.lan>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 02:49:24 -0000

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

Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender=
 Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1)=
 to Proposed Standard Date: Mon, Aug 19, 2013 at 03:59:50PM -0400 Quoting J=
ohn R Levine (johnl@taugh.com
> >>>* The charter disallows major protocol changes -- removing the SPF RR =
type
> >>>is a direct charter violation; since SPF is being used on the Internet=
=2E ...
>=20
> The SPF working group discussed this issue at painful, extensive length.
>=20
> As you saw when you read the WG archives, there is a significant
> interop bug in rfc 4408 in the handling of SPF and TXT records,
> which (again after painful and extension discussion) we decided the
> least bad fix was to get rid of SPF records.  I don't see anything
> in your note about how else you think we should address the interop
> bug.

It is in the archives, but for your convenience, and in haste:=20

SPF MUST be published. TXT MAY be published to help in migration. If both,
they MUST align. [0]

The lookup order should be : Ask for SPF, if not found, ask for TXT,
if not found, return ANY. Long-term, one may disregard the TXT fallback.
If TXT and SPF differ (and TXT happens to look like SPF syntax), assume
that migration is in place, discard TXT and use SPF.

And before the whining on query rate starts: The amount of queries is
presently uninteresting from a DNS operations perspective. Does matter
much less than the squatting on TXT. Besides, we've got caching in DNS,
which scales very well.

Caching in itself does introduce some pits to fall in, especially
regarding TTL in migration states. If deemed suitable, some
recommendations on TTL can be discussed. These should however be limited
to the unique situation that is trying to publish the same record
twice. My na=C3=AFve hunch is to either recommend publishing both with the
same TTL or possibly TXT with a significantly shorter. The latter is
probably only interesting in short-term migration states.

This discussion is however best had on the spfbis mailing list, after
the -19 draft is sent back.
=20
> In your case it doesn't matter, since your TXT and SPF records make
> no usable assertions, but a lot of people use SPF right now as part
> of their mail stream management.

Off-topic: They do make usable assertions. It is just that my email policy
seems to differ from what you think prudent. I believe I'm free to have
a differing policy.[1]

Praeterea censeo, Carthaginem esse delendam.
--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Don't hit me!!  I'm in the Twilight Zone!!!

[0] Please note that my besserwisser.org records are SPF only.=20
    The fact that there is argumentation with a funny prefix in
    some TXT records is simply "some use" of TXT records.

[1] Mail from me should be authenticated by my PGP signature, not by
    which IP address that happened to deliver it to your MX node.

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

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

iEYEARECAAYFAlIS2SoACgkQ02/pMZDM1cWBbACeKBqQ1QENQ8ph6szFNHIbOP/O
UyoAoIFmLhhEtC2C1FIbSiKVWbOkn5t+
=Jvp2
-----END PGP SIGNATURE-----

--PmA2V3Z32TCmWXqI--

From mansaxel@besserwisser.org  Mon Aug 19 20:01:55 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82DE711E8188; Mon, 19 Aug 2013 20:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level: 
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtuxRSlwdMwT; Mon, 19 Aug 2013 20:01:55 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id E88B811E8199; Mon, 19 Aug 2013 20:01:54 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id DEC7B9E98; Tue, 20 Aug 2013 05:01:52 +0200 (CEST)
Date: Tue, 20 Aug 2013 05:01:52 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: SPF TYPE support
Message-ID: <20130820030152.GC30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net> <6.2.5.6.2.20130819151912.0b861e98@resistor.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nmemrqcdn5VTmUEE"
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20130819151912.0b861e98@resistor.net>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: spfbis@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 03:01:55 -0000

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

Subject: Re: SPF TYPE support Date: Mon, Aug 19, 2013 at 04:42:42PM -0700 Q=
uoting S Moonesamy (sm+ietf@elandsys.com):
=20
> I personally do not think that it is appropriate to ask any working
> group participant to "shut up".  I welcome hearing arguments and I
> expect a working group to carefully consider them.

The repeated assertions of "This has been discussed already" are in effect
"shut up", but slightly more polite. I complied until last call. As was
recommended by wg chairs.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Yes, but will I see the EASTER BUNNY in skintight leather at an IRON
MAIDEN concert?

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

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

iEUEARECAAYFAlIS3CAACgkQ02/pMZDM1cV6kwCfbRy/S/AGPhXrSixfEM5fYmOZ
kOEAliPBhSu/DZGtS5vrTOlTyshy6YM=
=T9xe
-----END PGP SIGNATURE-----

--nmemrqcdn5VTmUEE--

From marka@isc.org  Mon Aug 19 20:19:20 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69A5211E8199 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 20:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[AWL=0.490,  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 FIeechiWfm+G for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 20:19:16 -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 0110811E80FF for <ietf@ietf.org>; Mon, 19 Aug 2013 20:19:15 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 6EEBCC9477; Tue, 20 Aug 2013 03:19:02 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1376968755; bh=UBtk4+sGpE7Cq3mdqfN/v5adTzcWSP/z2NQDrAfjeGc=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=Vtye71uoH7W2bZCFH9Hg4tTBEYofBBdAAJiw01vaWBB4CItVflXZwd3hOMqbUhwC1 3BCm/Ot8jT6SMX+GES287qRL3gQPc8TDbkFdTO1QBYVD/mZOrQIDHx4Mq85Xb04A6x iy8gt8Jnng5U4INjIXKeckM0j3GGce16Mo+8sjig=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue, 20 Aug 2013 03:19:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7DB8D160219; Tue, 20 Aug 2013 03:19:06 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 20B34160127; Tue, 20 Aug 2013 03:19:06 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 595D438B0B62; Tue, 20 Aug 2013 13:18:57 +1000 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info> <20130820012726.47C5C38B03BB@drugs.dv.isc.org> <20130820022209.GA56138@mx1.yitter.info>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Mon, 19 Aug 2013 22:22:09 -0400." <20130820022209.GA56138@mx1.yitter.info>
Date: Tue, 20 Aug 2013 13:18:56 +1000
Message-Id: <20130820031857.595D438B0B62@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 03:19:20 -0000

In message <20130820022209.GA56138@mx1.yitter.info>, Andrew Sullivan writes:
> Again, I'm not the shepherd on this, but I was involved in the
> consensus call in the WG when we determined that the WG wanted to
> deprecate use of RRTYPE 99.  (Note that this "deprecation" means just
> that users of SPF stop publishing that record.  There's nothing in the
> draft to remove the RRTYPE, as that would be absurd.)

Recommending that people not publish RRTYPE 99 does not address the
problem.  You need to forceable stop people using RRTYPE 99 or you
need to continue the migration by deploying more software that looks
up type SPF then type TXT if SPF is not available.

Those are the only solutions to the so called problem of publishers
and checkers not interoperating with each other.  
 
> On Tue, Aug 20, 2013 at 11:27:25AM +1000, Mark Andrews wrote:
> > Deployment is happening.  More and more SMTP servers
> > are making SPF requests before TXT requests.
> 
> I think those are the two central premises that are up for dispute.
> RFC 6686 made the determination about the former claim, and therefore
> that premise is not up for debate: deployment appears not to be
> happening.  If people wish to argue with the conclusions of RFC 6686,
> that's fine, but it seems that one at least needs to write an
> anti-6686 document in that case.  The draft currently up for last call
> is relying on the conclusions of RFC 6686 as a premise, and is not
> itself arguing whether RRTYPE 99 deployment is or is not happening.

When you only do a point measurement and don't have any long term
trends the data is meaning less.  Lots of zones were setup pre RFC
4408 with no campain to transition them to RFC 4408 status.  Similarly
it takes several years for new support to make its way into production.
You have to write the libraries.  You have to integrate the new
libraries into the servers.  You have to get those servers deployed
which is often only done on hardware replacement.

> The fact that SPF processors are making SPF queries before TXT queries
> is in fact part of the reasoning for why RRTYPE 99 ought to be
> deprecated.  If many clients make a query and only a tiny number of
> zones have that type published (or are likely ever to publish the
> type), it's simply wasteful to continue using that type.  If this
> seems a familiar line of argument, it's because it's one you see in
> the spfbis list archives when this issue was decided by the WG.

So the solution is to educate.  The long term goal is to get to
type 99 only.  The complaints about delays could be removed with
draft-wkumari-dnsop-hammer and addressing the bigger problem of
broken nameservers draft-andrews-dns-no-response-issue or have TLD
operators actually do what was requested of them in RFC 1034 and
periodically CHECK delegations which would address some of
misconfiguration issues.

> > Note it doesn't help that companies charge extra to support SPF
> > over TXT as you well know.
> 
> I'm not sure whether that's supposed to be a swipe at my employer, but
> just so we're clear: Dyn (my employer) supports the SPF RRTYPE in its
> enterprise-focussed offerings.  There's no extra charge.

There is a extra charge over basic support which support A, AAAA,
CNAME, MX, TXT, SRV, NS, LOC, PTR compared to the premium product
which supports A, AAAA, CERT, CNAME, DHCID, DNAME, DNSKEY, DS,
IPSECKEY, KEY, KX, LOC, MX, NAPTR, NS, NSAP, PTR, PX, RP, SOA, SPF,
SRV, SSHFP, TXT.

http://dyn.com/dns/dns-comparison/

> The front end for the basic DNS service (many people know this as
> DynDNS or Dyn's Standard DNS or other such trade names) is intended to
> be simple and self-service.  It's cheap, and the margins don't allow
> us to provide a lot of personalized support.  Dyn found that people
> who were good candidate customers for that self-service system knew
> how to do things with TXT, did not know about or care about the SPF
> type, and were confused by having two types for one purpose.  For
> practical purposes, it was necessary to support SPF over TXT (since
> some clients didn't check the SPF type).  So, one type it was, and TXT
> at that.  This all happened long before I worked at Dyn, but I assure
> you that the commercial pressure for adding TYPE 99 support to the
> basic platform (actually, it's just the front end) is just as
> non-existent today as it was when that decision was made.

So rather than do what RFC 4408 said to do and support the SHOULD Dyn
made it impossible for the non enterprise customer to do RFC 4408
properly.

Mark

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

From drc@virtualized.org  Mon Aug 19 21:57:41 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1018C21F8596 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 21:57: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 h3s7GXagh5sU for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 21:57:36 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id E0A3F11E80F2 for <ietf@ietf.org>; Mon, 19 Aug 2013 21:57:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id AF7DC8712A; Tue, 20 Aug 2013 00:57:33 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 01829-08; Tue, 20 Aug 2013 00:57:30 -0400 (EDT)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id BC90387128; Tue, 20 Aug 2013 00:57:28 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_08CA41F6-B55C-4165-87B9-D9D02B7101F9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20130819225810.63086.qmail@joyce.lan>
Date: Mon, 19 Aug 2013 21:57:26 -0700
Message-Id: <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org>
References: <20130819225810.63086.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 04:57:41 -0000

--Apple-Mail=_08CA41F6-B55C-4165-87B9-D9D02B7101F9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

John,

On Aug 19, 2013, at 3:58 PM, John Levine <johnl@taugh.com> wrote:
>> AFAICT, no one is arguing that overloading TXT in the
>> way recommended by this draft is a good idea, rather the best =
arguments appear to be that it is a pragmatic
>> "least bad" solution to the fact that (a) people often implement =
(poorly) the very least they can get away
>> with and (b) it can take a very long time to fix mistakes on the =
Internet.=20
>=20
> Neither of those are the reason the WG dropped type 99 records. =20

My apologies for trying to provide a high-level summary of what I =
believe the arguments to be.  My understanding of the reasons the WG =
decided to deprecate the SPF RR:

1) the low level of deployment of the SPF RR "both on the publishing =
side and the validation side" relative to TXT RRs

This corresponds to (a): people implement/deploy TXT because it is =
currently sufficient, both from what people put into their zone data as =
well as what middlebox and DNS UI implementors bother supporting.  I =
believe it is sufficient because the migration strategy proposed in RFC =
4408 was in error.

2) a "race condition" or "interoperability problem" resulting from what =
is documented in RFC 6686, Appendix A, #4.

This corresponds to (b): there was a mistake in 4408 and fixing that =
mistake takes a long time.

> Once again, I really don't understand what the point is here.

To quote from "http://www.openspf.org/FAQ/TXT_abuse" (a page on one of =
the websites referenced in RFC 6686):

"The Right Thing To Do is to get our own RRtype, and although it took a =
long time to get it, we have it assigned."

Regards,
-drc


--Apple-Mail=_08CA41F6-B55C-4165-87B9-D9D02B7101F9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSEvc3AAoJEIzZ2DQOJFbKr3AH/3SkQBVXPf+YK4Ue7mhtz6S7
FsRTQeamvZhx5XOqAF+dOjtlEV6bULvtUA+2b5ii/At4W27nzRLuQO8JJCr09USD
kIgnN2grL/+FCitFT+l6hThmgQos0Xx6U/pXqqeA/lZROb1YhmCnuJKn4YHLzo/K
iBqtkx8x54WivvRP2x6cHn7Ul71zn9o0qfKWtArRmDaaqM3g4X//wOSaN1Y1HYwB
n1xHza1RYWAx42Te06PD7l3+XRnGm3vehsx2OKG4giEJehCRyVnPNsg6OdoV8W0K
TH9UwB59xqwOE3scdUzE1erpKntaJDyPyPxFppUPMBXXU6EMqzX3tVyRdsogYiY=
=b472
-----END PGP SIGNATURE-----

--Apple-Mail=_08CA41F6-B55C-4165-87B9-D9D02B7101F9--

From scott@kitterman.com  Mon Aug 19 22:08:04 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 568E611E80F2 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0-QCytjQWPk for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:07:59 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 963E911E8198 for <ietf@ietf.org>; Mon, 19 Aug 2013 22:07:59 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 9EF4620E410F; Tue, 20 Aug 2013 01:07:56 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1376975276; bh=EmvonCTuM1SPkUds2ZH/9SVI84epDEXCMeeDzWOR+/o=; h=From:To:Subject:Date:In-Reply-To:References:From; b=DqCXLUJ5+YzbLqbsiLN3KPE3rM/f9Yft20HFdxa0ZG8KpeSUifJ3Ye792gP1kWbrl RzaqyH88b4POAFwNZdSW6fLAK+hY2w2WOgkR+y1213shJQBhzUKxgcjhj4Za0PXaHG CIvAJb0SB1X0mpTqBs6LiU5NU5YTQuV1LM421aEE=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 81CFE20E40CB;  Tue, 20 Aug 2013 01:07:56 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Tue, 20 Aug 2013 01:07:41 -0400
Message-ID: <1611736.YDOKKx2rmU@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-27-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 05:08:04 -0000

On Monday, August 19, 2013 21:57:26 David Conrad wrote:
> John,
> 
> On Aug 19, 2013, at 3:58 PM, John Levine <johnl@taugh.com> wrote:
> >> AFAICT, no one is arguing that overloading TXT in the
> >> way recommended by this draft is a good idea, rather the best arguments
> >> appear to be that it is a pragmatic "least bad" solution to the fact
> >> that (a) people often implement (poorly) the very least they can get
> >> away with and (b) it can take a very long time to fix mistakes on the
> >> Internet.> 
> > Neither of those are the reason the WG dropped type 99 records.
> 
> My apologies for trying to provide a high-level summary of what I believe
> the arguments to be.  My understanding of the reasons the WG decided to
> deprecate the SPF RR:
> 
> 1) the low level of deployment of the SPF RR "both on the publishing side
> and the validation side" relative to TXT RRs
> 
> This corresponds to (a): people implement/deploy TXT because it is currently
> sufficient, both from what people put into their zone data as well as what
> middlebox and DNS UI implementors bother supporting.  I believe it is
> sufficient because the migration strategy proposed in RFC 4408 was in
> error.
> 
> 2) a "race condition" or "interoperability problem" resulting from what is
> documented in RFC 6686, Appendix A, #4.
> 
> This corresponds to (b): there was a mistake in 4408 and fixing that mistake
> takes a long time.
> > Once again, I really don't understand what the point is here.
> 
> To quote from "http://www.openspf.org/FAQ/TXT_abuse" (a page on one of the
> websites referenced in RFC 6686):
> 
> "The Right Thing To Do is to get our own RRtype, and although it took a long
> time to get it, we have it assigned."

According to the history of the page, I wrote that in 2006.  Don't confuse 
engineering and marketing.  Despite the revisionist claims to the contrary, 
the SPF community pushed pretty hard on type SPF deployment, but it didn't 
work out very well.  Most open source libraries have given up on type SPF 
query be default, despite having supported it initially.

Support for type SPF in SPF verifiers is more likely declining than increasing.  
At least for the open source implementations capable of supporting it, the 
code has been there for half a decade.  It's mostly been turned off by default 
for operational reasons.

Scott K

From sm@elandsys.com  Mon Aug 19 22:13:48 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E8E011E8101; Mon, 19 Aug 2013 22:13: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 Rx9kIs+M-Cqx; Mon, 19 Aug 2013 22:13:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 528A111E80E9; Mon, 19 Aug 2013 22:13:47 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.26]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7K5DUMX029943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Aug 2013 22:13:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1376975624; bh=8ayir6hEw2MQ7y66ZKEvseITCib7UNg3Lq+9r/bxuXo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IGGmNpYS+NapXOJj0l8ZIRNK25uvIGN0z3NVYFJgBPKgSOEE/3KcQTXfKdJgD5ep9 atwW71CxRDKZk/tJlpHR2lepi0gM4ARNo4usgU+9UrT7cemA5hrTBZIlkl71wwUozC PhFKplsInhM93E5DiGdMdLkUzMKZiFbyVOURxwUM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1376975624; i=@elandsys.com; bh=8ayir6hEw2MQ7y66ZKEvseITCib7UNg3Lq+9r/bxuXo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=R5KrY1yM5qWOpRSiaosAPXUFhTUaEDdRYQMismve9kdKVy1UykeTtE3dybLqbIbh4 n87V1AJwwZHz5h2aZQdKD+EhgZ3PsGqAj+LXpg2b3Y24SzxYGB9E4COeoVAjhFfOTp 7IRPUOLOv27771S/xOcJoQy0MjPLjLyVKLOQ5Bjo=
Message-Id: <6.2.5.6.2.20130819202422.0d1756a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 19 Aug 2013 22:12:18 -0700
To: mansaxel@besserwisser.org, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130819150521.GB21088@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: spfbis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 05:13:48 -0000

At 08:05 19-08-2013, M=C3ns Nilsson wrote:
>I strongly OPPOSE draft-ietf-spfbis-4408bis-19.txt being published as
>RFC unless substantial parts are reworked.
>
>* The charter disallows major protocol changes -- removing the SPF RR type
>is a direct charter violation; since SPF is being used on the Internet.
>
>* The overloading of the TXT record is a hack at best, aimed at
>circumventing DNS management systems vendors that fail to ship
>support. Breaking the DNS model with specific resource records is not
>the way to get better application support. (besides, the major argument
>at the time was "it's so hard and takes ages to get a RR type", which
>isn't true anymore and also, the RRtype is allocated, what's the fuss? )
>
>* The empirical data that was gathered and the conclusions from which
>that where published as RFC 6686 are IMNSHO flawed and rushed in that they
>set far too optimistic deadlines for adaptation before declaring failure.
>
>The IESG should send draft-ietf-spfbis-4408bis-19 back to spfbis wg and=
 tell
>the wg that instead of deprecating SPF it should be algorithmically
>preferred while maintaining support for TXT.

I read the SPFBIS charter (=20
https://datatracker.ietf.org/wg/spfbis/charter/ )=20
again.  The charter violation the above may be referring might be about:

  "Specifically out-of-scope for this working group:

   * Removal of existing features that are in current use."

There is a message from the Responsible Area=20
Director at=20
http://www.ietf.org/mail-archive/web/spfbis/current/msg02167.html=20
which might shine some light about that part of the charter.

Both RR Type 16 and RR Type 99 are in use on the=20
Internet.  Tony Hansen mentioned during the IETF 83 session that:

   "when you write a protocol, there is definite harm if there is a
    choice in what you publish and what you look for.  He is of
    the view that there is a definite bug in RFC 4408."

Fixing that bug falls within the scope of the SPFBIS charter, specifically:

   "Changes to the SPF specification will be limited to the correction
    of errors, removal of unused features, addition of any enhancements
    that have already gained widespread support, and addition of
    clarifying language. "

The fourth paragraph (see quoted text) states=20
that the conclusions from that where RFC 6866=20
were flawed and rushed.  The explanation given is=20
because the working group declared failure too=20
soon.  The SPFBIS WG discovered a bug during the=20
review of the SPF specification.  One of the main=20
considerations for the decision was to fix the=20
bug.  The working group had to choose one RRTYPE=20
as the conclusion was that it was the appropriate=20
way to fix the bug and ensure interoperability.

The comments posted up to now for the Last Call=20
points to a disagreement about the choice of RRTYPE.

Regards,
S. Moonesamy (as document shepherd) =20


From randy@psg.com  Mon Aug 19 22:14:32 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B7B11E8190 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwzeGDzweV6O for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:14:32 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id E6BF811E8101 for <ietf@ietf.org>; Mon, 19 Aug 2013 22:14:31 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VBeGx-0006gi-Vx; Tue, 20 Aug 2013 05:14:28 +0000
Date: Tue, 20 Aug 2013 14:14:27 +0900
Message-ID: <m2siy56j0s.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Conrad <drc@virtualized.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: 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, 20 Aug 2013 05:14:32 -0000

so, according to your message, one lesson i might take from this is, if
i want to deploy a new hack which needs an rrtype, not to use txt in the
interim.  i will be caught in a mess which will appear to be of my own
making.  is that somewhat correct?

randy

From dhc@dcrocker.net  Mon Aug 19 22:17:26 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C079721F9B8D; Mon, 19 Aug 2013 22:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.433
X-Spam-Level: 
X-Spam-Status: No, score=-6.433 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 AP7UA5tpOcA4; Mon, 19 Aug 2013 22:17:20 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C899421F842B; Mon, 19 Aug 2013 22:17:20 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7K5HECd016397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Aug 2013 22:17:18 -0700
Message-ID: <5212FBB8.60200@dcrocker.net>
Date: Mon, 19 Aug 2013 22:16:40 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?UTF-8?B?TcOlbnMgTmlsc3Nvbg==?= <mansaxel@besserwisser.org>
Subject: Re: SPF TYPE support
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net> <6.2.5.6.2.20130819151912.0b861e98@resistor.net> <20130820030152.GC30516@besserwisser.org>
In-Reply-To: <20130820030152.GC30516@besserwisser.org>
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.66]); Mon, 19 Aug 2013 22:17:18 -0700 (PDT)
Cc: spfbis@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 05:17:27 -0000

On 8/19/2013 8:01 PM, MÃ¥ns Nilsson wrote:
> The repeated assertions of "This has been discussed already" are in effect
> "shut up", but slightly more polite. I complied until last call. As was
> recommended by wg chairs.


There is a fundamental difference between telling someone to shut up and 
asking the person to familiarize themselves with the group's history 
before speaking up.

It's a question of who is being required to carry the primary burden for 
making their case.  In the current circumstance, the burden is on the 
person lodging the concern, namely you, rather than on the group.

The alternative is, effectively, a denial of service attack on the 
group's progress, by requiring that it be (potentially constantly) 
required to re-visit old and resolved topics.

Since there is, in fact, an extensive -- possibly even complete -- 
public archive of discussions, placing the burden on the person lodging 
the concern is singularly reasonable.

As others have attempted to point out, this reduces to requiring that 
someone raising a concern during the last call start with the group's 
context and, therefore, either point out what the group missed or 
explain how it assessed reality incorrectly or otherwise made a 
problematic engineering choice.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Mon Aug 19 22:22:27 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 468B011E8163 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.577
X-Spam-Level: 
X-Spam-Status: No, score=-6.577 tagged_above=-999 required=5 tests=[AWL=0.022,  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 gHWXI7uDCqOe for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:22:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5E511E8101 for <ietf@ietf.org>; Mon, 19 Aug 2013 22:22:22 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7K5MHv9016468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 19 Aug 2013 22:22:21 -0700
Message-ID: <5212FCEF.80701@dcrocker.net>
Date: Mon, 19 Aug 2013 22:21:51 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com>
In-Reply-To: <m2siy56j0s.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 19 Aug 2013 22:22:21 -0700 (PDT)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 05:22:27 -0000

On 8/19/2013 10:14 PM, Randy Bush wrote:
> so, according to your message, one lesson i might take from this is, if
> i want to deploy a new hack which needs an rrtype, not to use txt in the
> interim.  i will be caught in a mess which will appear to be of my own
> making.  is that somewhat correct?


Whether it's what he meant, it's not the correct lesson.  There are 
probably two realistic lessons:

      The first is that there now a number of other apps using TXT 
records, with no problems, because they are stored under scoping nodes 
(underscore-prefaced names).  This approach might be aesthetically 
displeasing, but it works just fine.

      The second is that, unfortunately, deploying a new RR that gains 
widespread, end-to-end support remains problematic, assurances to the 
contrary notwithstanding.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From drc@virtualized.org  Mon Aug 19 22:27:26 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45FF11E80FD for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DuGsTBYBI3G7 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 22:27:20 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id B3AFD11E80F3 for <ietf@ietf.org>; Mon, 19 Aug 2013 22:27:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id E8D138712A; Tue, 20 Aug 2013 01:27:17 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 01793-10; Tue, 20 Aug 2013 01:27:16 -0400 (EDT)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 32BF687128; Tue, 20 Aug 2013 01:27:14 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: David Conrad <drc@virtualized.org>
In-Reply-To: <m2siy56j0s.wl%randy@psg.com>
Date: Mon, 19 Aug 2013 22:27:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4FC3784-EA30-4927-A1D2-62B12E15196F@virtualized.org>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1508)
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, 20 Aug 2013 05:27:26 -0000

On Aug 19, 2013, at 10:14 PM, Randy Bush <randy@psg.com> wrote:
> so, according to your message, one lesson i might take from this is, =
if
> i want to deploy a new hack which needs an rrtype, not to use txt in =
the
> interim.  i will be caught in a mess which will appear to be of my own
> making.  is that somewhat correct?

Not exactly.=20

Given the situation at the time (specifically, the difficulty getting =
new RR types -- a problem since fixed), I believe the use of TXT was =
appropriate. Unfortunately, the migration strategy away from TXT was =
flawed. My personal belief is that the rationale to migrate away from =
TXT remains valid and the appropriate course of action is to fix the =
migration strategy, not permanently encode what everyone agrees is a =
hack into a proposed standard.

Regards,
-drc


From paf@frobbit.se  Mon Aug 19 23:34:02 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57E3211E81C5 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 23:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rwsL6E9KS8E for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 23:34:02 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id D1A5011E8180 for <ietf@ietf.org>; Mon, 19 Aug 2013 23:34:01 -0700 (PDT)
Received: from [IPv6:2a01:3f0:1::85d3:8d58:735a:e251] (unknown [IPv6:2a01:3f0:1:0:85d3:8d58:735a:e251]) by mail.frobbit.se (Postfix) with ESMTPSA id 46AC923F78; Tue, 20 Aug 2013 08:33:59 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <5212FCEF.80701@dcrocker.net>
Date: Tue, 20 Aug 2013 08:33:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <55459829-933F-4157-893A-F90552D4441A@frobbit.se>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
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, 20 Aug 2013 06:34:02 -0000

On 20 aug 2013, at 07:21, Dave Crocker <dhc@dcrocker.net> wrote:

>     The first is that there now a number of other apps using TXT =
records, with no problems, because they are stored under scoping nodes =
(underscore-prefaced names).  This approach might be aesthetically =
displeasing, but it works just fine.

That can not be said generally. Reason for this is that the RR with an =
underscored prefix MIGHT end up in a different zone than the record =
without. This implies that two records with the same owner and different =
RRType MUST be in the same zone, while a name without and one with =
prefix MIGHT NOT, where also one of the zones is signed and the other is =
not.

   Patrik


From stefan.winter@restena.lu  Mon Aug 19 23:37:29 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB6D21F9A31; Mon, 19 Aug 2013 23:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZbzfmvO10B1; Mon, 19 Aug 2013 23:37:27 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 046A111E8180; Mon, 19 Aug 2013 23:37:26 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id CBDF210589; Tue, 20 Aug 2013 08:37:24 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id B769C10581; Tue, 20 Aug 2013 08:37:24 +0200 (CEST)
Message-ID: <52130E9D.9080602@restena.lu>
Date: Tue, 20 Aug 2013 08:37:17 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: lionel.morand@orange.com
Subject: Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
References: <20130813162403.9625.46995.idtracker@ietfa.amsl.com> <5211D43D.2030408@restena.lu> <16081_1376927192_52123DD8_16081_108_1_6B7134B31289DC4FAF731D844122B36E24C0D7@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <16081_1376927192_52123DD8_16081_108_1_6B7134B31289DC4FAF731D844122B36E24C0D7@PEXCVZYM13.corporate.adroot.infra.ftgroup>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AVUoru2qt6rNQjwR028h0r41tiVULLgG1"
X-Virus-Scanned: ClamAV
Cc: "dime@ietf.org" <dime@ietf.org>, '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: Tue, 20 Aug 2013 06:37:29 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AVUoru2qt6rNQjwR028h0r41tiVULLgG1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

> When relying on S-NAPTR (RFC3958), redirection is only possible inside =
sub-domains of the original domain name.

I don't think that's true. RFC3958 has exactly this use case in it's
first example section (2.2): a domain example.com redirects service
"EM:protA" to another domain, namely someisp.example - with the
non-terminal flag, as I described in my original mail. This is
absolutely a different domain name.

> This is a restriction compared to the use of normal NAPTR and REGEXP.

While making my own experiences with NAPTR, I learned that there is no
"normal" use of NAPTR. NAPTR records are not allowed to be used "in the
wild" without a valid DDDS specification defining its exact semantics.
That is precisely the reason why RFC3588 had to be revised in that
regard. RFC3958 provides that semantics, so it was a natural choice to
re-base Diameter's usage in an S-NAPTR.

> The following recommendations can be also found in the RFC6733: "The do=
main suffixes in the NAPTR replacement field SHOULD match the domain of t=
he original query." Actually, I don't even understand the "SHOULD" here w=
ithout any clarification on what to do if not... but it is another debate=
=2E

I now see that RFC6733 has put this IMHO arbitrary restriction in place.
It really serves no particular purpose; if there was some thinking
behind it, then that really should have been explained in the document.

I would tend to ignore that SHOULD if I were implementing Diameter (I'm
not :-) ). Different domain names are perfectly in scope for S-NAPTRs,
and you would have to consciously lobotomise libraries or code snippets
to *not* permit redirections to other domains.

We are also regularly using s-flag S-NAPTRs in eduroam and RADIUS
Dynamic Discovery to point to a delegate RADIUS server residing in a
different domain. It's just normal operations.

This limitation in RFC6733 is at best "funny" IMHO.

> Therefore, my understanding is that the use of S-NAPTR is not suitable =
for redirection when the target domain name is different from the origina=
l one. And the current draft proposes to allow any kind of redirection wi=
thout any impact on existing DNS infra.

I would rather take a very good look at the section in RFC6733 that
discourages other domain names in the replacement. It's more like an
erratum for me; and if that restriction were away you would have a
working solution to your redirection problem with zero effort.

And anyway, it's a SHOULD without considerations or consequences
attached. Which makes it more of a DONTCARE anyway ;-)

> But as I said, it is only based on my understanding and I'm not an expe=
rt on DNS.

I don't think DNS is the problem here. It's more that Diameter butchers
its NAPTR usage unnecessarily.

Greetings,

Stefan Winter

>=20
> Regards,
>=20
> Lionel
>=20
> -----Message d'origine-----
> De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part de=
 Stefan Winter
> Envoy=E9 : lundi 19 ao=FBt 2013 10:16
> =C0 : dime@ietf.org; 'IETF Discussion Mailing List'
> Objet : Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.=
txt> (Realm-Based Redirection In Diameter) to Proposed Standard
>=20
> Hello,
>=20
>> The IESG has received a request from the Diameter Maintenance and=20
>> Extensions WG (dime) to consider the following document:
>> - 'Realm-Based Redirection In Diameter'
>>   <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard
>=20
> Sorry for bringing this up so late, but as I was writing my own dynamic=
 discovery draft for RADIUS, it occured to me that the usage of S-NAPTR f=
or Diameter brings a built-in support to signal realm-based redirect
> *if* S-NAPTR discovery is used.
>=20
> That only affects this document periphally; it describes realm-based re=
direct for agent-based redirects, not for DNS-based; but still, the wordi=
ng in section 2 implies that using a realm-based-redirect-aware Diameter =
agent is the only choice, and I think that should be rectified.
>=20
> The mechanism for S-NAPTR realm-based redirect is built into the S-NAPT=
R spec by allowing for "non-terminal" lookups; this is signalled by havin=
g neither an "s" flag (for SRV targets) nor an "a" flag (for A/AAAA targe=
ts); but instead an "" (empty) flag. The replacement string in the NAPTR =
record is then the label of /another/ NAPTR lookup; that lookup is then t=
o be performed with the same service/protocol tag.
>=20
> That makes the whole realm-based redirect problem very easy protocol-wi=
se. Consider a realm "foo.example" who wants to tell its Diameter peers t=
hat its realm's application ID 123 is from now on served from "example.co=
m". It puts into DNS
>=20
> foo.example.  43200   IN  NAPTR   100 10 "" "aaa+ap123:diameter.tls" ""=

> example.com
>=20
> A client who got this answer would then query for
>=20
> example.com NAPTR "aaa+ap123:diameter.tls"
>=20
> and would get example.com's servers via SRV or A/AAAA records as config=
ured by the admins of example.com.
>=20
> This is described in section 2.2.3 of RFC3958.
>=20
> Now for the wording in the draft:
>=20
> Sction 2: the first para needs a bit of a rewrite to factor in S-NAPTR'=
s capabilities.
>=20
> I suggest something along the lines of:
>=20
> "Realm-based redirection is implicitly a part of the Diameter base prot=
ocol, but only where peer discovery using S-NAPTR is used (section
> 5.2 of [RFC6733], by using the non-terminal S-NAPTR flag). This allows =
for both application-specific realm-based redirects, and for application-=
agnostic (unconditional) realm-based redirects, and does not require any =
Diameter agents.
>=20
> For deployments which do not make use of S-NAPTR peer discovery, suppor=
t of realm-based redirection MUST be specified as part of functionality s=
upported by a Diameter application. (... continue with the rest of the se=
ction ...)
>=20
> Greetings,
>=20
> Stefan Winter
>=20
>=20
>=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=
=20
>> ietf@ietf.org mailing lists by 2013-08-27. Exceptionally, comments may=
=20
>> be sent to iesg@ietf.org instead. In either case, please retain the=20
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    Message redirection is a basic capability provided by the Diameter
>>    base protocol.  In its conventional form, message redirection is
>>    performed by an application-independent "redirect agent", which
>>    returns one or more individual hosts to the message sender as
>>    possible destinations of the redirected message.
>>
>>    However, in some circumstances an operator may wish to redirect
>>    messages to an alternate domain without specifying individual hosts=
=2E
>>    This document specifies an application-specific mechanism by which
>>    that can be achieved.  New applications may incorporate this
>>    capability by reference to the present document.
>>
>>    Because the redirection mechanism is application-specific, it must =
be
>>    performed by a Diameter server or proxy rather than a basic redirec=
t
>>    agent as defined in the Diameter base protocol.  A new term, "Realm=
-
>>    based Redirect Server", is introduced in this document to
>>    differentiate the application-specific nature of realm-based
>>    redirection from the conventional Diameter redirection performed by=
 a
>>    basic redirect agent.
>>
>>    This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to=

>>    the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
>>    AVPs.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/b=

>> allot/
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>>    http://datatracker.ietf.org/ipr/1254/
>>
>>
>>
>> _______________________________________________
>> DiME mailing list
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>>
>=20
>=20
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nation=
ale et de la Recherche 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
>=20
> _______________________________________________________________________=
__________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations conf=
identielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez =
recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les message=
s electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme=
 ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or privileged=
 information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have b=
een modified, changed or falsified.
> Thank you.
>=20


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--AVUoru2qt6rNQjwR028h0r41tiVULLgG1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlITDqQACgkQ+jm90f8eFWbc7QCeLXfIZYHh5rweH/GOK/9J/v1p
TbMAnj6fR2oP7Pk3XBeMYFgeu5iM9uvy
=CqrH
-----END PGP SIGNATURE-----

--AVUoru2qt6rNQjwR028h0r41tiVULLgG1--

From dhc@dcrocker.net  Tue Aug 20 00:15:02 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4385511E81E0 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 00:15:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.428
X-Spam-Level: 
X-Spam-Status: No, score=-6.428 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 n7R8OMbDqXxl for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 00:14:56 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2179C11E81DB for <ietf@ietf.org>; Tue, 20 Aug 2013 00:14:56 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7K7Ejkf017729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Aug 2013 00:14:48 -0700
Message-ID: <5213174D.7080504@dcrocker.net>
Date: Tue, 20 Aug 2013 00:14:21 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se>
In-Reply-To: <55459829-933F-4157-893A-F90552D4441A@frobbit.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.0 (sbh17.songbird.com [72.52.113.66]); Tue, 20 Aug 2013 00:14:50 -0700 (PDT)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 07:15:02 -0000

On 8/19/2013 11:33 PM, Patrik Fältström wrote:
> Reason for this is that the RR with an underscored prefix MIGHT end up in a different zone than the record without.


Patrik,

Please clarify.  I don't know what you mean by the 'with' and 'without' 
references.

And as long as I'm asking for more explanation, given the number of 
years of use the construct has had and for the number of different 
applications, where has the problem (whatever you mean specifically) 
been seen?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From paf@frobbit.se  Tue Aug 20 00:43:21 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39EE421F9D55 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 00:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level: 
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[AWL=-0.150,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6-kbm3m0fZmd for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 00:43:20 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id BA00221F9C22 for <ietf@ietf.org>; Tue, 20 Aug 2013 00:43:20 -0700 (PDT)
Received: from [IPv6:2a01:3f0:1::85d3:8d58:735a:e251] (unknown [IPv6:2a01:3f0:1:0:85d3:8d58:735a:e251]) by mail.frobbit.se (Postfix) with ESMTPSA id 597C621F7E; Tue, 20 Aug 2013 09:43:19 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <5213174D.7080504@dcrocker.net>
Date: Tue, 20 Aug 2013 09:43:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2148A40-2673-40C7-8349-0A65D0D01794@frobbit.se>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
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, 20 Aug 2013 07:43:21 -0000

On 20 aug 2013, at 09:14, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/19/2013 11:33 PM, Patrik F=E4ltstr=F6m wrote:
>> Reason for this is that the RR with an underscored prefix MIGHT end =
up in a different zone than the record without.
>=20
> Patrik,
>=20
> Please clarify.  I don't know what you mean by the 'with' and =
'without' references.

The two following records MUST be in the same zone:

foo.example. IN X RDATAX
foo.example. IN Y RDATAY

The two following MIGHT NOT be in the same zone:

foo.example. IN X RDATAX
_bar.foo.example. IN TXT RDATAY

> And as long as I'm asking for more explanation, given the number of =
years of use the construct has had and for the number of different =
applications, where has the problem (whatever you mean specifically) =
been seen?

When using DNSSEC if the _bar.foo.example record in the 2nd example =
above is unsigned, while the foo.example in the first example is.

   Patrik


From hallam@gmail.com  Tue Aug 20 01:50:02 2013
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 8597D11E81F5 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 01:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level: 
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=0.205,  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 pT4Jyf5QCzTz for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 01:50:01 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id ED00911E81F4 for <ietf@ietf.org>; Tue, 20 Aug 2013 01:50:00 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id z12so115993wgg.34 for <ietf@ietf.org>; Tue, 20 Aug 2013 01:50: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=stmg6NnZS7IRbWl+FmKm0O6GOcdqYlWNEhkZ40ybf5E=; b=0d/Dk0gqlxwpKrv8puNrF0FV7swtwdT5siCj7UTc0zKr3dnTuwBBAAKlgLbWB/ZtL+ 4oYEQ6Wqfhyd9Q5g/QGEt+/3dwz6OddjwQAInzgiJjBtXr1Hi1XBbW/6KTx9uIlprVrE 1zhRFiGDZ/XsxJ7RkFRc/zWBzBV63OgSzug9jUS2ha9Py6M6TwHoKyTrNnzbeyFSzfGp YduNfB06GjNgKvqXLooGltB/oVP+1TIs6fStBlxOURxfEjhaiNiV/F2YsEmoPB3ijuto T7PUNl7UWZlOmpjqRWVvbk7SbYc6GAHTuQgNP4D/vzmi3HNtfwy1rS62j2DZKDudWwIb pvYA==
MIME-Version: 1.0
X-Received: by 10.180.38.73 with SMTP id e9mr348828wik.37.1376988600055; Tue, 20 Aug 2013 01:50:00 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Tue, 20 Aug 2013 01:49:59 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130819074949.0cba8300@resistor.net>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <OF7C8B5CF8.DD8CFB55-ON85257BC9.004A95C2-85257BC9.004AE588@csc.com> <520E3D9B.5020901@network-heretics.com> <38AB9072-85B5-4BE4-9EE5-A03EF3F63C4E@oracle.com> <520E7942.8060705@network-heretics.com> <C11BDD11-4F24-484E-8DC3-9DAAA536C238@oracle.com> <6.2.5.6.2.20130818014356.0bb745b8@resistor.net> <52122D03.8060906@gmail.com> <6.2.5.6.2.20130819074949.0cba8300@resistor.net>
Date: Tue, 20 Aug 2013 04:49:59 -0400
Message-ID: <CAMm+Lwh2bQVngng6eRubTex9Sg0mMURDzyQKWBHfghZwiYXC9g@mail.gmail.com>
Subject: Re: Academic and open source rate
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=e89a8f64701b5dc0e404e45d2450
Cc: Arturo Servin <arturo.servin@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 08:50:02 -0000

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

On Mon, Aug 19, 2013 at 11:48 AM, SM <sm@resistor.net> wrote:

> Hola Arturo,
>
> At 07:34 19-08-2013, Arturo Servin wrote:
>
>>         Academic might work. "Open source" not so much as other
>> mentioned. Does
>> "Big Corporation" doing Open Source apply?
>>
>>         I was tempted to propose "non-profit", but also there are
>> organizations
>> with large budgets. And profit driven ones with not much money.
>>
>
> "Open source" is difficult.  As people pointed out "open source" does not
> necessarily mean free.  "open source" does not necessarily mean
> "non-profit".  I used the term loosely.  If hypothetically speaking, there
> was formal action, a clearer term might be needed.
>
> Irrespective of my views, "big corporation" is what helps the IETF
> operate.  If "big corporation" doing open source applies it will become a
> problem for the IETF.  The main issue is why should the IETF subsidize a
> particular group.  It can also be argued that it is not fair to subsidize a
> particular group.
>

If getting open source implementations is a desirable goal then the way to
address that goal is for ISOC or other parties with funds to provide
bursaries to the developers. Isn't that the reason they got the $$$ .org
money?


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Aug 19, 2013 at 11:48 AM, SM <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hola Arturo,<div class=3D"im"><br>
At 07:34 19-08-2013, Arturo Servin wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 Academic might work. &quot;Open source&quot; not so much as=
 other mentioned. Does<br>
&quot;Big Corporation&quot; doing Open Source apply?<br>
<br>
=A0 =A0 =A0 =A0 I was tempted to propose &quot;non-profit&quot;, but also t=
here are organizations<br>
with large budgets. And profit driven ones with not much money.<br>
</blockquote>
<br></div>
&quot;Open source&quot; is difficult. =A0As people pointed out &quot;open s=
ource&quot; does not necessarily mean free. =A0&quot;open source&quot; does=
 not necessarily mean &quot;non-profit&quot;. =A0I used the term loosely. =
=A0If hypothetically speaking, there was formal action, a clearer term migh=
t be needed.<br>

<br>
Irrespective of my views, &quot;big corporation&quot; is what helps the IET=
F operate. =A0If &quot;big corporation&quot; doing open source applies it w=
ill become a problem for the IETF. =A0The main issue is why should the IETF=
 subsidize a particular group. =A0It can also be argued that it is not fair=
 to subsidize a particular group.<br>
</blockquote><div><br></div><div>If getting open source implementations is =
a desirable goal then the way to address that goal is for ISOC or other par=
ties with funds to provide bursaries to the developers. Isn&#39;t that the =
reason they got the $$$ .org money?</div>
<div>=A0</div></div><div><br></div>-- <br>Website: <a href=3D"http://hallam=
baker.com/">http://hallambaker.com/</a><br>
</div></div>

--e89a8f64701b5dc0e404e45d2450--

From stefan.winter@restena.lu  Tue Aug 20 04:37:22 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAC3B11E8217; Tue, 20 Aug 2013 04:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBQ5LLQJSP1H; Tue, 20 Aug 2013 04:37:21 -0700 (PDT)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 3885411E8213; Tue, 20 Aug 2013 04:37:20 -0700 (PDT)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 0FDE010589; Tue, 20 Aug 2013 13:37:20 +0200 (CEST)
Received: from aragorn.restena.lu (aragorn.restena.lu [IPv6:2001:a18:1:8::155]) by smtprelay.restena.lu (Postfix) with ESMTPS id E9DAD1057F; Tue, 20 Aug 2013 13:37:19 +0200 (CEST)
Message-ID: <521354EB.3080900@restena.lu>
Date: Tue, 20 Aug 2013 13:37:15 +0200
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: lionel.morand@orange.com
Subject: Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
References: <20130813162403.9625.46995.idtracker@ietfa.amsl.com> <5211D43D.2030408@restena.lu> <16081_1376927192_52123DD8_16081_108_1_6B7134B31289DC4FAF731D844122B36E24C0D7@PEXCVZYM13.corporate.adroot.infra.ftgroup> <52130E9D.9080602@restena.lu> <25683_1376996822_52134DD6_25683_1915_1_6B7134B31289DC4FAF731D844122B36E24D288@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <25683_1376996822_52134DD6_25683_1915_1_6B7134B31289DC4FAF731D844122B36E24D288@PEXCVZYM13.corporate.adroot.infra.ftgroup>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CDEfaAHUfHGMmA1XBD1JrT4jAu7fhDPOm"
X-Virus-Scanned: ClamAV
Cc: "dime@ietf.org" <dime@ietf.org>, '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: Tue, 20 Aug 2013 11:37:23 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CDEfaAHUfHGMmA1XBD1JrT4jAu7fhDPOm
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

> Thank you for quick feedback.
> I agree with your analysis. I think that we should provide more info on=
 the possible use of S-NAPTR for realm-based redirection.
> Taking into account your proposal, what do you think of the following p=
roposed changes:

The new text reads pretty well.

One thing worth considering is maybe: this draft already updates
RFC6733. It may be worth making explicit that the RFC6733 SHOULD
regarding same-domain targets is being made obsolete in by this draft.

One more sentence in the section 2 text below should do the trick:


> NEW:
>=20
>    Using the S-NAPTR DDDS application [RFC3958], the DNS-based dynamic =
peer=20
>    discovery mechanism defined in the Diameter base protocol [RFC6733]
>    provides a simple mechanism for realm-based redirection. When S-NAPT=
R is
>    used for peer discovery, redirection of Diameter request from the or=
iginal
>    realm to a new realm may be performed by updating the existing NAPTR=
 resource
>    records for the original realm as follow: the NAPTR RR for the desir=
ed=20
>    application(s) and supported application protocol(s) provided by the=
=20
>    new realm will have an empty FLAG field and the REPLACEMENT field wi=
ll
>    contain the new realm to use for the next DNS lookup.

ADD:

The new realm can be arbitrary; the restriction in RFC6733 that the
NAPTR replacement field SHOULD match the domain of the original query
does not apply for realm-based redirect purposes.

All the rest of the text is fine.

Greetings,

Stefan Winter

>=20
>    However, the use of DNS-based dynamic peer discovery is optional for=
 Diameter=20
>    implementations. For deployments which do not make use of S-NAPTR pe=
er=20
>    discovery, support of realm-based redirection MUST be specified as p=
art of=20
>    functionality supported by a Diameter application.  In this way, sup=
port of the=20
>    considered Diameter application (discovered during capabilities exch=
ange=20
>    procedures as defined in Diameter base protocol [RFC6733]) indicates=
=20
>    implicit support of the realm-based redirection mechanism.  Designer=
s of
>    new applications can incorporate the mechanism specified here into t=
heir=20
>    application by normative reference to this document.
>=20
>    The result of making realm-based redirection an application-specific=

>    behaviour is that it cannot be performed by a redirect agent as
>    defined in [RFC6733], but MUST be performed instead by an
>    application-aware Diameter node (Diameter server or proxy) (hereafte=
r
>    called a "Realm-based Redirect Server").
>=20
>    An application can specify that realm-based redirection operates onl=
y
>    on complete sessions beginning with the initial message, or on every=

>    message within the application, even if earlier messages of the same=

>    session were not redirected.  This distinction matters only when
>    realm-based redirection is first initiated.  In the former case,
>    existing sessions will not be disrupted by the deployment of realm-
>    based redirection.  In the latter case, existing sessions will be
>    disrupted if they are stateful.
>=20
> Regards,
>=20
> Lionel
>=20
> -----Message d'origine-----
> De : Stefan Winter [mailto:stefan.winter@restena.lu]=20
> Envoy=E9 : mardi 20 ao=FBt 2013 08:37
> =C0 : MORAND Lionel OLNC/OLN
> Cc : dime@ietf.org; 'IETF Discussion Mailing List'
> Objet : Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.=
txt> (Realm-Based Redirection In Diameter) to Proposed Standard
>=20
> Hi,
>=20
>> When relying on S-NAPTR (RFC3958), redirection is only possible inside=
 sub-domains of the original domain name.
>=20
> I don't think that's true. RFC3958 has exactly this use case in it's fi=
rst example section (2.2): a domain example.com redirects service "EM:pro=
tA" to another domain, namely someisp.example - with the non-terminal fla=
g, as I described in my original mail. This is absolutely a different dom=
ain name.
>=20
>> This is a restriction compared to the use of normal NAPTR and REGEXP.
>=20
> While making my own experiences with NAPTR, I learned that there is no =
"normal" use of NAPTR. NAPTR records are not allowed to be used "in the w=
ild" without a valid DDDS specification defining its exact semantics.
> That is precisely the reason why RFC3588 had to be revised in that rega=
rd. RFC3958 provides that semantics, so it was a natural choice to re-bas=
e Diameter's usage in an S-NAPTR.
>=20
>> The following recommendations can be also found in the RFC6733: "The d=
omain suffixes in the NAPTR replacement field SHOULD match the domain of =
the original query." Actually, I don't even understand the "SHOULD" here =
without any clarification on what to do if not... but it is another debat=
e.
>=20
> I now see that RFC6733 has put this IMHO arbitrary restriction in place=
=2E
> It really serves no particular purpose; if there was some thinking behi=
nd it, then that really should have been explained in the document.
>=20
> I would tend to ignore that SHOULD if I were implementing Diameter (I'm=
 not :-) ). Different domain names are perfectly in scope for S-NAPTRs, a=
nd you would have to consciously lobotomise libraries or code snippets to=
 *not* permit redirections to other domains.
>=20
> We are also regularly using s-flag S-NAPTRs in eduroam and RADIUS Dynam=
ic Discovery to point to a delegate RADIUS server residing in a different=
 domain. It's just normal operations.
>=20
> This limitation in RFC6733 is at best "funny" IMHO.
>=20
>> Therefore, my understanding is that the use of S-NAPTR is not suitable=
 for redirection when the target domain name is different from the origin=
al one. And the current draft proposes to allow any kind of redirection w=
ithout any impact on existing DNS infra.
>=20
> I would rather take a very good look at the section in RFC6733 that dis=
courages other domain names in the replacement. It's more like an erratum=
 for me; and if that restriction were away you would have a working solut=
ion to your redirection problem with zero effort.
>=20
> And anyway, it's a SHOULD without considerations or consequences attach=
ed. Which makes it more of a DONTCARE anyway ;-)
>=20
>> But as I said, it is only based on my understanding and I'm not an exp=
ert on DNS.
>=20
> I don't think DNS is the problem here. It's more that Diameter butchers=
 its NAPTR usage unnecessarily.
>=20
> Greetings,
>=20
> Stefan Winter
>=20
>>
>> Regards,
>>
>> Lionel
>>
>> -----Message d'origine-----
>> De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part=20
>> de Stefan Winter Envoy=E9 : lundi 19 ao=FBt 2013 10:16 =C0 : dime@ietf=
=2Eorg;=20
>> 'IETF Discussion Mailing List'
>> Objet : Re: [Dime] Last Call:=20
>> <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based Redirection=
=20
>> In Diameter) to Proposed Standard
>>
>> Hello,
>>
>>> The IESG has received a request from the Diameter Maintenance and=20
>>> Extensions WG (dime) to consider the following document:
>>> - 'Realm-Based Redirection In Diameter'
>>>   <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard
>>
>> Sorry for bringing this up so late, but as I was writing my own=20
>> dynamic discovery draft for RADIUS, it occured to me that the usage of=
=20
>> S-NAPTR for Diameter brings a built-in support to signal realm-based=20
>> redirect
>> *if* S-NAPTR discovery is used.
>>
>> That only affects this document periphally; it describes realm-based r=
edirect for agent-based redirects, not for DNS-based; but still, the word=
ing in section 2 implies that using a realm-based-redirect-aware Diameter=
 agent is the only choice, and I think that should be rectified.
>>
>> The mechanism for S-NAPTR realm-based redirect is built into the S-NAP=
TR spec by allowing for "non-terminal" lookups; this is signalled by havi=
ng neither an "s" flag (for SRV targets) nor an "a" flag (for A/AAAA targ=
ets); but instead an "" (empty) flag. The replacement string in the NAPTR=
 record is then the label of /another/ NAPTR lookup; that lookup is then =
to be performed with the same service/protocol tag.
>>
>> That makes the whole realm-based redirect problem very easy=20
>> protocol-wise. Consider a realm "foo.example" who wants to tell its=20
>> Diameter peers that its realm's application ID 123 is from now on=20
>> served from "example.com". It puts into DNS
>>
>> foo.example.  43200   IN  NAPTR   100 10 "" "aaa+ap123:diameter.tls" "=
"
>> example.com
>>
>> A client who got this answer would then query for
>>
>> example.com NAPTR "aaa+ap123:diameter.tls"
>>
>> and would get example.com's servers via SRV or A/AAAA records as confi=
gured by the admins of example.com.
>>
>> This is described in section 2.2.3 of RFC3958.
>>
>> Now for the wording in the draft:
>>
>> Sction 2: the first para needs a bit of a rewrite to factor in S-NAPTR=
's capabilities.
>>
>> I suggest something along the lines of:
>>
>> "Realm-based redirection is implicitly a part of the Diameter base=20
>> protocol, but only where peer discovery using S-NAPTR is used (section=

>> 5.2 of [RFC6733], by using the non-terminal S-NAPTR flag). This allows=
 for both application-specific realm-based redirects, and for application=
-agnostic (unconditional) realm-based redirects, and does not require any=
 Diameter agents.
>>
>> For deployments which do not make use of S-NAPTR peer discovery,=20
>> support of realm-based redirection MUST be specified as part of=20
>> functionality supported by a Diameter application. (... continue with =

>> the rest of the section ...)
>>
>> Greetings,
>>
>> Stefan Winter
>>
>>
>>
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits=
=20
>>> final comments on this action. Please send substantive comments to=20
>>> the ietf@ietf.org mailing lists by 2013-08-27. Exceptionally,=20
>>> comments may be sent to iesg@ietf.org instead. In either case, please=
=20
>>> retain the beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>    Message redirection is a basic capability provided by the Diameter=

>>>    base protocol.  In its conventional form, message redirection is
>>>    performed by an application-independent "redirect agent", which
>>>    returns one or more individual hosts to the message sender as
>>>    possible destinations of the redirected message.
>>>
>>>    However, in some circumstances an operator may wish to redirect
>>>    messages to an alternate domain without specifying individual host=
s.
>>>    This document specifies an application-specific mechanism by which=

>>>    that can be achieved.  New applications may incorporate this
>>>    capability by reference to the present document.
>>>
>>>    Because the redirection mechanism is application-specific, it must=
 be
>>>    performed by a Diameter server or proxy rather than a basic redire=
ct
>>>    agent as defined in the Diameter base protocol.  A new term, "Real=
m-
>>>    based Redirect Server", is introduced in this document to
>>>    differentiate the application-specific nature of realm-based
>>>    redirection from the conventional Diameter redirection performed b=
y a
>>>    basic redirect agent.
>>>
>>>    This memo updates Sections 6.13 and 6.14 of RFC6733 with respect t=
o
>>>    the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
>>>    AVPs.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/=

>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/=

>>> b
>>> allot/
>>>
>>>
>>> The following IPR Declarations may be related to this I-D:
>>>
>>>    http://datatracker.ietf.org/ipr/1254/
>>>
>>>
>>>
>>> _______________________________________________
>>> DiME mailing list
>>> DiME@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dime
>>>
>>
>>
>> --
>> Stefan WINTER
>> Ingenieur de Recherche
>> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Natio=
nale=20
>> et de la Recherche 6, rue Richard Coudenhove-Kalergi
>> L-1359 Luxembourg
>>
>> Tel: +352 424409 1
>> Fax: +352 422473
>>
>>
>> ______________________________________________________________________=

>> ___________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations=20
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses, =

>> exploites ou copies sans autorisation. Si vous avez recu ce message=20
>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi q=
ue les pieces jointes. Les messages electroniques etant susceptibles d'al=
teration, Orange decline toute responsabilite si ce message a ete altere,=
 deforme ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or=20
>> privileged information that may be protected by law; they should not b=
e distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and=
 delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have =
been modified, changed or falsified.
>> Thank you.
>>
>=20
>=20
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nation=
ale et de la Recherche 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
>=20
> _______________________________________________________________________=
__________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations conf=
identielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez =
recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les message=
s electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme=
 ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or privileged=
 information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and =
delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have b=
een modified, changed or falsified.
> Thank you.
>=20


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--CDEfaAHUfHGMmA1XBD1JrT4jAu7fhDPOm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlITVO8ACgkQ+jm90f8eFWaKuwCfer7DW8VLQF/LrBnUz1j6/QcC
XAEAnjJaInWb52fKDYfzT/gZYQOT6eYA
=qFxK
-----END PGP SIGNATURE-----

--CDEfaAHUfHGMmA1XBD1JrT4jAu7fhDPOm--

From sustrik@250bpm.com  Tue Aug 20 05:35:40 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0749911E817A for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 05:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNumZJlX32vs for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 05:35:34 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5F35911E80D9 for <ietf@ietf.org>; Tue, 20 Aug 2013 05:35:24 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 75A98180354D; Tue, 20 Aug 2013 14:35:21 +0200 (CEST)
Message-ID: <52136288.6090408@250bpm.com>
Date: Tue, 20 Aug 2013 14:35:20 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu>
In-Reply-To: <520E6A55.6010802@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 12:35:40 -0000

On 16/08/13 20:07, Joe Touch wrote:
>
>
> On 8/15/2013 10:38 PM, Martin Sustrik wrote:
>> On 16/08/13 03:23, Wesley Eddy wrote:
>>
>>>> There are semantics issues to; see draft-touch-tcp-portnames-00 for
>>>> information (this is being revised for resubmission shortly, FWIW).
>>>>
>>> I totally agree.  In fact, in the update to the TCP roadmap [1], we
>>> added TCPMUX to the section on "Historic and Undeployed Extensions",
>>> though it definitely bears further discussion than is currently in
>>> the roadmap.  I think we should add a reference to your portnames doc
>>> to explain why this should be Historic plus check a bit more to see if
>>> the code that's out there is really being used or whether it's just
>>> hanging out like a vestigal limb in the various inetd packages.
>>>
>>> If it's fair to ask Martin ... I'm kind of curious why you might want
>>> to be using it or think it sounds useful?  I think a lot of admins
>>> would be concerned that it could be used to get around port-based
>>> firewall rules, etc.
>>
>> Ok, let me explain.
>>
>> I am coming from enterprise messaging world (think of IBM MQ series,
>> JMS, ActiveMQ, RabbitMQ et c.)
>>
>> Once I was participating on AMQP protocol development (now at OASIS).
>> So, what AMQP and other enterprise messaging products do is exposing a
>> "message broker" on a single TCP port, which then forwards messages to
>> any connected services. As can be seen, single open firewall port can be
>> used to access any internal service.
>
> I don't understand that statement.
>
> Services are currently indicated by the destination port. If there is
> only one destination port available, there is only one service provided
> - because very few services can be identified solely by in-band
> information.

"service" here is used in very generic manner; it means "some 
functionality that can be executed remotely".

>> That being obviously the *wrong* way to do things, I've written ZeroMQ
>> later which takes the strict approach: If you want to expose a new
>> service, you have to use a separate TCP port number.
>>
>> Since then it turned out that this as a limitation that people are most
>> complaining about.
>
> It would be useful if you could be more specific about the problem you
> are trying to solve.
>
> So far I hear "people want one port that serves multiple services". I'd
> like a pony ;-) I.e., just because they want it, doesn't mean it either
> makes sense or should get it.

It's about cutting the corporate process out of the deployment loop.

If every update to your system require opening/closing ports in the 
firewall, the corporate process kicks in and each iteration is going to 
take months if not years.

>> Now, the reason seems to be that ZeroMQ requires you to use different
>> TCP connections for doing different kinds of stuff to avoid head-of-line
>> blocking et c. (think of SCTP channels simulated via TCP)
>
> Different connections don't have anything to do with the use of a single
> port. A single port can serve multiple connections, and yes - that's a
> useful way to avoid HOL blocking.

Ack.

>> What that means is that you have a lot of fine-grained services and as
>> the development of your application proceeds you add more of them,
>> remove them and so on.
>>
>> That in turn requires admins (and the corporate approval process!) to
>> get into the deployment cycle and open the TCP ports as appropriate. The
>> result is that the development basically grinds to halt.
>
> That sounds a lot like the desires of admins is in conflict with the
> desires of your users. I.e., an admin that wants to block anything they
> don't explicitly allow WANTS to block this sort of mechanism too.

Yes. That's the pretty common case. There's a internal conflict at your 
customer's site that you cannot solve. However, despite the conflick, 
you still need to deploy, otherwise you'll go bankrupt.

>> The solution IMO is to preserve the port-based services functionality
>> for those that truly care about security and -- optionally -- support
>> some kind of multiplexer such as TCPMUX for those that care more about
>> short deployment cycle.
>
> TCPMUX won't do what you're asking - if you're asking to block based on
> the service type. If it did, then the sysadmin would just block TCPMUX
> connections to services they didn't know, and you'd be right back where
> you are now (i.e., without TCPMUX).
>
> Again, what is the goal?

Admins are concerned about ports, not TCPMUX services because that's 
what they corporate process requires.

Yes, it isn't sane, but don't expect things to be sane in corporate 
environment.

> (note: the goal of the portnames approach is NOT to provide a single
> multiplexing port; it's to decouple the dest port's two uses - demux
> info and service identifier. the primary reason for portnames is to
> allow more than 65K concurrent/timewait connections to a single service;

The proposal looks good. Once it is widely deployed, I'll be happy to 
drop the TCPMUX idea. Till then though...

> FWIW, I cited it because of its description of the limitations of
> TCPMUX, not because the approach there was relevant here).

Yes. TCPMUX can support max 65536 concurrent connections. Not good, but 
still better than nothing.

>> That being said, IIRC, there's such functionality in WebSockets as well.
>> Open a connection to fixed pot (80) and particular URL (string), then
>> after the initial negotiation, switch to raw TCP mode and hand the
>> connection to whatever application is suppose to handle it. The reason I
>> don't like that solution is that you have to have web server installed
>> to work as a multiplexer, which is kind of strange.
>
> If you want a multiplexer to serve different connections from a single
> service port, you need a multiplexer server (tcpmux daemon, websockets,
> whatever you want to call it).

Ack. The web server is a problem though, because you typically don't 
have control of it. I.e. you cannot randomly plug-in your code into it.

Martin


From hsantos@isdg.net  Tue Aug 20 06:34:15 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6BD511E821F for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 06:34:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.181
X-Spam-Level: 
X-Spam-Status: No, score=-102.181 tagged_above=-999 required=5 tests=[AWL=0.418, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FxWELN8R5Hn9 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 06:34:11 -0700 (PDT)
Received: from dkim.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B138411E81C9 for <ietf@ietf.org>; Tue, 20 Aug 2013 06:34:07 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6693; t=1377005645; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=WiPx4sB 0K5X2MSqtCoMDjVj5Pew=; b=aCcjSt1uf3UrWB0tYm+v6ZiaR+1tHOtC4D3rPXt PHuYSXpAyxVd2MtcQX4yqI/5ppuKIZZISJcuTWKyGNjOEwHlpxClOU/zimrsYMEO LM9cgzZxm/5+gtR3Y2igFeUU/vEIMIa5vzJbGAxkc0aksEPCj+yoep2lQ+rJrsWJ AwwY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 20 Aug 2013 09:34:05 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3468161282.3.2612; Tue, 20 Aug 2013 09:34:03 -0400
Message-ID: <52136F65.6020703@isdg.net>
Date: Tue, 20 Aug 2013 09:30:13 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] SPF TYPE support
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net> <6.2.5.6.2.20130819151912.0b861e98@resistor.net>
In-Reply-To: <6.2.5.6.2.20130819151912.0b861e98@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 13:34:15 -0000

On 8/19/2013 7:42 PM, S Moonesamy wrote:>
> At 14:10 19-08-2013, Hector Santos wrote:
>> I'm having a hard time with both sides of the argument, especially
>> the supposed existence of an "interop problem" which seems to only
>> highlight how to "procedurally" stump the SPF type advocates with a
>> "error correction" standpoint.   What is that error by the way?
>
> In a message dated February 27, 2012, the SPFBIS Chairs commented
> that the discussion about Issue #9 (SPF RRTYPE) has revealed an
> interoperability concern in the existing RFC (4408).
>
>  From RFC 6686:
>
>    "RFC 4408 itself included a faulty transition plan, likely because of
>     the late addition of a requirement to develop one -- it said:
>
>        An SPF-compliant domain name SHOULD have SPF records of both RR
>        types.  A compliant domain name MUST have a record of at least
>        one type.
>
>     which means both can claim to be fully compliant while failing
>     utterly to interoperate."
>
> The consensus of the SPFBIS WG was that this is an interoperability
> issue and it would have to be corrected.  That is what was considered as
> an error correction.

I have a few questions and points:

May I ask why was the above was not an area for clarification as oppose 
as the presumed stated technical reason for removal?

There was adequate information for the expected and original optimal 
migration plan but it could of been further codified and clarified. It 
would of been on par with BIS level of work.  Issue #9 should not have 
been a reason for removal.  I reported issue #25 [1] regarding the 
complexity of the recommended parallel processing approach.  I believe 
most folks agreed the ideal and optimal migration approach was:

     Query SPF type first,
     Fallback to TXT secord.

It was common sense, at least to me.

Second, I was under the impression interop reports (RFC 6686) were not 
making any conclusions or recommendations?  Is that a correct basic 
understanding of interop reports?  They were observations, collection of 
available data and while it might be eventually used to rethink a 
protocol design, I don't think the above RFC 4408 statement is a serious 
"error" in the functional description to justify removal. There are 
other parts of 4408 which helped clarify the migration path.

But overall, a correction (not removal) would of suffice. It would of 
been on par for BIS-like corrections and protocol updates.

Third, I believe removal required a more deeper IETF discussion about 
the initial presumed engineering expectation that DNS servers (all top 
DNS servers, including and especially Microsoft DNS servers) would 
eventually directly support a new registered SPF type or at the very 
least support RFC 3597 (Handling of Unknown DNS Resource Record (RR) 
Type) [2].

If this is no longer the expectation, then it would make sense to remove 
the SPF type but also be aware that in general, this will also  nix (not 
help) any future idea for successfully adopting new RR types.
It would be added statement that TXT based applications are acceptable. 
  I think the DNS community continues to have a problem with this.

>> I don't believe there was an adequate answer from the advocates of
>> removing the SPF RR type and the repeated assertion that its been
>> discussed at length has not been convincing it was appropriately
>> addressed. It all seem to be a "Shut up" approach to the problem
>> (always suggest that its been discussed already). This seems to be one
>> of the reasons why the issue will not go away.
>
> I personally do not think that it is appropriate to ask any working
> group participant to "shut up".  I welcome hearing arguments and I
> expect a working group to carefully consider them.
>
> Regards,
> S. Moonesamy (as document shepherd)

SM, Pete, thank you for the opportunity to clarify my point. For the 
record, there was no intent to imply it occurred but quite frankly when 
it is repeatedly stated, this deeply divided issue has not be resolved 
at any point,  it does have an intimidation factor.  As Mr. Crocker 
stated, the burden is on the those who oppose the removal. But my 
question was always why was the decision made to remove in the first 
place done when in fact it was quite obvious it would not have industry 
wide endorsement. The burden should of been to justify removal. Now it 
has become difficult to effectively add it back. This is why I posed the 
question in two forums to get community input over the last few years. 
It was quite obvious to me that the DNS community would be against this 
removal.  So in this vain, it was prematurely removed in the WG without 
early IETF/IESG/DNS concerns adequately dealt with.  Unfortunately, we 
were advise to raise the issue again in LC, but by that point, all the 
IETF procedural moves were made making it it a very high burden to add 
something that should not been removed in the first place.

The only reason our own early adoption package did not support the SPF 
type was because we could not; the Microsoft DNS server (NT 4.0 at the 
time) had not directly support the SPF type but more importantly it did 
not support RFC 3597.  Unfortunately, not even MS DNS 5.0 which did add 
direct support for other new RR types (SRV, DNSSEC, AAAA, etc).

In my engineering opinion, the implications of the SPF type removal are 
wide spread as it implies a no confidence in the future of DNS servers 
to support safe, transparent passthru, recursive queries of unnamed types.

If such is the case with the IETF DNS community,  then it makes 
engineering sense to remove the SPF type but also keep in mind new RR 
types are also unrealistic as well. All future DNS DOMAIN policy based 
applications will be TXT only based which may be the acceptable reality 
today.  It wasn't yester-years (during MARID).  The endorsement of DKIM 
as an IS specification is testament of this TXT based solution 
acceptability in the market place.

To me, that would be the reason for removal. Otherwise, if we still have 
confidence in the future of RFC 3597 support in DNS servers across the 
board out of the box, then we should correct and clarify the SPF/TXT 
query method migration path in RFC 4408-bis.

As stated a number of times in the SPF WG, I would support SPF type in 
our implementation once Microsoft DNS server supported at the very least 
unnamed RR type processing.  It can't be provisional software, i.e. 
custom, that would not cut it. It needs to be out of the box for wide 
network query support.

Thanks

--
HLS


[1] http://www.ietf.org/mail-archive/web/spfbis/current/msg00586.html
[2] http://tools.ietf.org/html/rfc3597


From hsantos@isdg.net  Tue Aug 20 07:20:36 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F065D11E8226 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.32
X-Spam-Level: 
X-Spam-Status: No, score=-102.32 tagged_above=-999 required=5 tests=[AWL=0.279, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAgBE9wSwsU5 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:20:31 -0700 (PDT)
Received: from dkim.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7719C11E8221 for <ietf@ietf.org>; Tue, 20 Aug 2013 07:20:27 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3869; t=1377008418; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=O9w8Mr3 HUNMnCv6ZtJDW8wkFRRM=; b=mqvFNdAwEPD2Bf7O1ktrIQqBk6eF7b2UXCwU1+t XX0rLFa1kNrb49YBOu3idAqiXTq3Ia0QtcXfDZQeWrVzTZdoQ/b7bD/1kIihXJci ILZRjEZc9VTYuLMAI26iK//XgwTdGW63NnF5KHUg/6Pd457xMhlRlE8qme83EtPK 6p1A=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 20 Aug 2013 10:20:18 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3470934637.3.4580; Tue, 20 Aug 2013 10:20:17 -0400
Message-ID: <52137A3B.6040200@isdg.net>
Date: Tue, 20 Aug 2013 10:16:27 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <6.2.5.6.2.20130819202422.0d1756a8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130819202422.0d1756a8@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: spfbis@ietf.org, mansaxel@besserwisser.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 14:20:36 -0000

On 8/20/2013 1:12 AM, S Moonesamy wrote:

> There is a message from the Responsible Area Director at
> http://www.ietf.org/mail-archive/web/spfbis/current/msg02167.html which
> might shine some light about that part of the charter.
>
> Both RR Type 16 and RR Type 99 are in use on the Internet.  Tony Hansen
> mentioned during the IETF 83 session that:
>
>    "when you write a protocol, there is definite harm if there is a
>     choice in what you publish and what you look for.  He is of
>     the view that there is a definite bug in RFC 4408."
>
> Fixing that bug falls within the scope of the SPFBIS charter, specifically:
>
>    "Changes to the SPF specification will be limited to the correction
>     of errors, removal of unused features, addition of any enhancements
>     that have already gained widespread support, and addition of
>     clarifying language. "


This doesn't seem to be correct. My apology if I don't follow or see the 
logic.   The only real issue as it was since day zero in MARID was the 
infrastructure support for recursive passthru queries which is what RFC 
3597 (Handling of Unknown DNS Resource Record (RR) Type).  Without this, 
which allows for servers to delay/plan direct new RR type support yet 
still not error out on an unnamed type, there COULD NOT be any 
reasonable expectation to even only suggest a dual query migration 
approach, either in serial or parallel. It is very important to consider 
the mindset when it was first considered and written for RFC 4408 
because to me, that is the mindset that has changed.

If we don't think the infrastructure, the DNS vendors primarily, will 
support RFC 3497, then it seems proper to me to finally forget the idea.

But if we still think its desirable and possible, then I would prefer to 
keep the protocol feature/option, corrected of course, and allow 
implementers the design choice to support it.

The way I see it, if more implementations did begin to add support of a 
clarified BIS specification, that doesn't mean they may enabled it 
(default ON) out of the box.  I would want to initially offer the lowest 
overheard operational setup out of the box.  It will still be a long 
term migration path, shorter if we can encourage the major DNS vendors 
to add at least RFC 3597 support.  Without, no new RR type will work 
across the board.


> The fourth paragraph (see quoted text) states that the conclusions from
> that where RFC 6866 were flawed and rushed.  The explanation given is
> because the working group declared failure too soon.  The SPFBIS WG
> discovered a bug during the review of the SPF specification.  One of the
> main considerations for the decision was to fix the bug.  The working
> group had to choose one RRTYPE as the conclusion was that it was the
> appropriate way to fix the bug and ensure interoperability.
>
> The comments posted up to now for the Last Call points to a disagreement
> about the choice of RRTYPE.

I hope I am reading this incorrectly.  It may be too procedural oriented 
to me at this point.

I would like to see a simple just distinctive consensus on what the 
entire IETF/DNS community believes is the future of DNS servers offering 
unnamed RR type processing because that is the main barrier for any kind 
success. We knew this as far back as MARID.  I don't quite understand 
why this key point seems to be left out, instead MARID was deemed off 
topic. That was an error because if there is no future in unnamed RR 
type support, then it really doesn't matter and the problem is solved. 
TXT only will be the only fast entry point for new DNS DOMAIN policy 
applications.

If the community still believes it possible, then clarifying and 
codifying the SPF/TYPE lookup procedure seems to me to be the only real 
correction to make here.

Thanks

--
HLS

[1] http://tools.ietf.org/html/rfc3597



From johnl@iecc.com  Tue Aug 20 07:46:22 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9016E11E8225 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.821
X-Spam-Level: 
X-Spam-Status: No, score=-102.821 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JT7IfJSgCQN4 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:46:17 -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 584AA21F99E1 for <ietf@ietf.org>; Tue, 20 Aug 2013 07:46:12 -0700 (PDT)
Received: (qmail 83760 invoked from network); 20 Aug 2013 14:46:11 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 20 Aug 2013 14:46:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52138133.xn--9vv.k1308; i=johnl@user.iecc.com; bh=XQWDbqTEzgSKwYhmyfquO/nxBojQ75S8bWVx/Xr9oZs=; b=GzUJcRo3F8Xu5+Csx9mS11P69Eq7Bj++ZGiynytIcsj+pupjIluKHb5QO7sy0YsO3sfwG6KY4s6UJ3TV6DE5TfRZ2XZuUlzGiGqUJfdUrv2RNyKHhp7radrv+NBHVNK7nIuCm1oHqpci2BqZ3fd1WGmWN/MtLF8FHg3d6llOGBCtav0anknobhXHajgcjGzBteD93bQQzzDpLXEPOkPcWzdupoUXVs4P1HqZfvlfJCg2r9ZqnuyPsq44dcLf9Ulx
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52138133.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=XQWDbqTEzgSKwYhmyfquO/nxBojQ75S8bWVx/Xr9oZs=; b=CySugIUIqYnyPJnKURoSGtgG+pVg9xAH+qZKFzrxsPRRguGLCi6xMvfWJZgDGNdQHIArRzmVIHJpj/AdBvhvfS7OTS9avdcNPYjyj1imdVsc+JT19AknqRX0RRWJa17v6V+m5qsbvj/kF0z8J1JwzUyHSusg9u+lLwi68Us3IvrFmUNKyaiGVoEX5GJO41TXU+y+mDeLcVmI8GHn++ZY4ueXJZimYdAFUgjykZwRa1rmGVmiNVd+wu8UKaq8i6Io
Date: 20 Aug 2013 14:45:48 -0000
Message-ID: <20130820144548.73129.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
In-Reply-To: <D2148A40-2673-40C7-8349-0A65D0D01794@frobbit.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paf@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 14:46:22 -0000

Newsgroups: iecc.lists.ietf.ietf
From: John Levine <johnl@iecc.com>
Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
Summary:
Expires:
References: <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net> <D2148A40-2673-40C7-8349-0A65D0D01794@frobbit.se>
Sender:
Followup-To:
Distribution: 
Organization: 
Keywords: 
Cc: 
Cleverness: some

>The two following MIGHT NOT be in the same zone:
>
>foo.example. IN X RDATAX
>_bar.foo.example. IN TXT RDATAY

Since prefixed names have never been used for anything other than
providing information about the unprefixed name, what conceivable
operational reason could there be to put a zone cut at the prefix?

This impresses me as one of those problems where the solution is
"don't do that."

R's,
John

From ajs@anvilwalrusden.com  Tue Aug 20 07:47:31 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6DD11E8225 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:47:31 -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 sUaEZ167EUzT for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 07:47:26 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id AFAC921F8FD8 for <ietf@ietf.org>; Tue, 20 Aug 2013 07:46:54 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id DA5B98A031 for <ietf@ietf.org>; Tue, 20 Aug 2013 14:46:47 +0000 (UTC)
Date: Tue, 20 Aug 2013 10:46:46 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130820144646.GE20618@mx1.yitter.info>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5213174D.7080504@dcrocker.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 14:47:31 -0000

On Tue, Aug 20, 2013 at 12:14:21AM -0700, Dave Crocker wrote:
> 
> And as long as I'm asking for more explanation, given the number of
> years of use the construct has had and for the number of different
> applications, where has the problem (whatever you mean specifically)
> been seen?

Quite apart from the DNSSEC example that Patrik sent, underscore
labels also cause problems and confusion when aliases are involved.
The alias stuff is a corner case, of course, but it's still a basic
problem with the approach of specifying policy for a target name at a
different name than the target itself.  This trade-off might be a
legitimate one (I certainly think it's preferable to the strategy SPF
adopted, of stepping all over the TXT RRTYPE at a given name), but it
won't do to dismiss the problem with a point-and-laugh argument.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From touch@isi.edu  Tue Aug 20 08:02:52 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1907F11E823E for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTr87oK6-P7N for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:02:45 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id AAC7711E822B for <ietf@ietf.org>; Tue, 20 Aug 2013 08:02:45 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7KF1Bg3014067 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Aug 2013 08:01:20 -0700 (PDT)
Message-ID: <521384B8.9020505@isi.edu>
Date: Tue, 20 Aug 2013 08:01:12 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com>
In-Reply-To: <52136288.6090408@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 15:02:52 -0000

On 8/20/2013 5:35 AM, Martin Sustrik wrote:
>> If you want a multiplexer to serve different connections from a single
>> service port, you need a multiplexer server (tcpmux daemon, websockets,
>> whatever you want to call it).
>
> Ack. The web server is a problem though, because you typically don't
> have control of it. I.e. you cannot randomly plug-in your code into it.

You have control over a web server you install. Yes, that would eat one 
IP address, but there are a lot more IP addresses than port numbers 
(i.e., using a port to avoid using a separate IP address consumes the 
wrong resource).

However, see my other message - it's hard to recommend an approach when 
we don't understand the problem you're trying to solve.

Joe

From dotzero@gmail.com  Mon Aug 19 12:03:08 2013
Return-Path: <dotzero@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 236F921F8F2E; Mon, 19 Aug 2013 12:03:08 -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=[BAYES_00=-2.599, GB_I_LETTER=-2, 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 M-jF1ch2k3sk; Mon, 19 Aug 2013 12:03:07 -0700 (PDT)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 49EB021F8E40; Mon, 19 Aug 2013 12:03:07 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id o17so6693698oag.35 for <multiple recipients>; Mon, 19 Aug 2013 12:03: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=QZ1iaIX8m+MUQkSa4EvO7vfMH3GS8ltrxzSDM1qvPAM=; b=lgIdo9js0J6wyvNhw8yqmpJgt8S25tSF3VFOxCnbONT59305/x7t2H3CCj9hd4sAKs tyMy/8Uh7Avj3HSPb+LTE1Virm1htSn5eYY7OwKGSQ+J8Y5IoaDlZbiCdDxT+UAnBxdL YgWvAed3X1D1gZOSpIKXBOSitM3ymd8lo8+1176itKvUwRVPMhn3/xonYayHMQhMV7ye dsL+gWTF5rCC7DJWEdbQvpA/X9M4EmMouk43lvylEsnUQAeGUGltYXsOpEkwD5eZSN1Y qKoH1DwWAYXh2HQkLvWQ8BFzX7+Acy8+rfC9JBH11J97zvF5+NAr/vqTVkvD0576L7BM ofYw==
MIME-Version: 1.0
X-Received: by 10.182.121.137 with SMTP id lk9mr14801490obb.32.1376938986737;  Mon, 19 Aug 2013 12:03:06 -0700 (PDT)
Received: by 10.182.34.232 with HTTP; Mon, 19 Aug 2013 12:03:06 -0700 (PDT)
In-Reply-To: <20130819150521.GB21088@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org>
Date: Mon, 19 Aug 2013 15:03:06 -0400
Message-ID: <CAJ4XoYfF05FUq7F9aJ0R8ksLeHC8TraLHV_FR08Nh0f9VW2uHQ@mail.gmail.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Dotzero <dotzero@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Tue, 20 Aug 2013 08:04:44 -0700
Cc: "spfbis@ietf.org" <spfbis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 19:03:08 -0000

The issue M=E5ns Nilsson raises was discussed extensively on the SPFbis
list prior to as well as during last call on the list and I believe
the appropriate decision was reached by the working group. If there is
any doubt in the minds of the IESG regarding whether the working group
reached the correct decision, I would urge those IESG members to
review the threads in the archives related to this issue.

Several related issues, including a race condition, were identified
and the solution to go with TXT only records is IMHO the correct one
under the circumstances. The relatively small uptake of Type 99
records in the wild (both on the publishing side AND on the validation
side) in comparison to the implementation for TXT records made a
compelling case for the decision of the working group.

With regard to the limitations of the working group charter, some
significant change was required to eliminate the race condition
regardless of what that change would be. The decision of the working
group (IMHO - I do not want to put words into anyones mouth) was to go
with the approach which had the least impact on what is arguably a
very large installed existing base on both the sender AND the
validator sides of implementation.

Based on this I would ask that tehe IESG move
draft-ietf-spfbis-4408bis-19.txt to Proposed Standard.

Michael Hammer

On Mon, Aug 19, 2013 at 11:05 AM, M=E5ns Nilsson
<mansaxel@besserwisser.org> wrote:
> Subject: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender P=
olicy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1) t=
o Proposed Standard Date: Mon, Aug 19, 2013 at 06:19:16AM -0700 Quoting The=
 IESG (iesg-secretary@ietf.org)
>>
>> The IESG has received a request from the SPF Update WG (spfbis) to
>> consider the following document:
>> - 'Sender Policy Framework (SPF) for Authorizing Use of Domains in Email=
,
>>    Version 1'
>>   <draft-ietf-spfbis-4408bis-19.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-09-02. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>
> I strongly OPPOSE draft-ietf-spfbis-4408bis-19.txt being published as
> RFC unless substantial parts are reworked.
>
> * The charter disallows major protocol changes -- removing the SPF RR typ=
e
> is a direct charter violation; since SPF is being used on the Internet.
>
> * The overloading of the TXT record is a hack at best, aimed at
> circumventing DNS management systems vendors that fail to ship
> support. Breaking the DNS model with specific resource records is not
> the way to get better application support. (besides, the major argument
> at the time was "it's so hard and takes ages to get a RR type", which
> isn't true anymore and also, the RRtype is allocated, what's the fuss? )
>
> * The empirical data that was gathered and the conclusions from which
> that where published as RFC 6686 are IMNSHO flawed and rushed in that the=
y
> set far too optimistic deadlines for adaptation before declaring failure.
>
> The IESG should send draft-ietf-spfbis-4408bis-19 back to spfbis wg and t=
ell
> the wg that instead of deprecating SPF it should be algorithmically
> preferred while maintaining support for TXT.
>
> Thanks,
> --
> M=E5ns Nilsson     primary/secondary/besserwisser/machina
> MN-1334-RIPE                             +46 705 989668
> It was a JOKE!!  Get it??  I was receiving messages from DAVID LETTERMAN!=
!
> YOW!!
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAlISNDEACgkQ02/pMZDM1cXK+gCfYQ1Mv1CHjy9DDn7sA7DC7dF3
> b48An1b49Zqf/du3dvN6pmj6in+CEujB
> =3DsoFG
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> spfbis mailing list
> spfbis@ietf.org
> https://www.ietf.org/mailman/listinfo/spfbis
>

From khalil.yacoub@atecgrp.com  Mon Aug 19 15:19:42 2013
Return-Path: <khalil.yacoub@atecgrp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3E811E8182 for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:19:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ktb9LMULBd2A for <ietf@ietfa.amsl.com>; Mon, 19 Aug 2013 15:19:37 -0700 (PDT)
Received: from mail41.atl.registeredsite.com (mail41.atl.registeredsite.com [209.237.134.231]) by ietfa.amsl.com (Postfix) with ESMTP id 471D511E8175 for <ietf@ietf.org>; Mon, 19 Aug 2013 15:19:36 -0700 (PDT)
Received: from mymail.myregisteredsite.com ([209.237.135.203]) by mail41.atl.registeredsite.com (8.12.11.20060308/8.12.11) with ESMTP id r7JMJWTV002790 for <ietf@ietf.org>; Mon, 19 Aug 2013 18:19:32 -0400
Received: (qmail 1369 invoked by uid 80); 19 Aug 2013 22:19:32 -0000
Received: from unknown (HELO Khalilwork) (khalil.yacoub@atecgrp.com@209.237.129.45) by mymail.myregisteredsite.com with ESMTPA; 19 Aug 2013 22:19:32 -0000
From: "ATEC" <khalil.yacoub@atecgrp.com>
To: <ietf@ietf.org>
References: <20130819220633.6777.1508.idtracker@ietfa.amsl.com>
In-Reply-To: <20130819220633.6777.1508.idtracker@ietfa.amsl.com>
Subject: RE: Protocol Action: 'RADIUS Option for DHCPv6 Relay Agent' to Proposed	Standard (draft-ietf-dhc-dhcpv6-radius-opt-14.txt)
Date: Mon, 19 Aug 2013 18:19:31 -0400
Message-ID: <006b01ce9d2a$2d472e70$87d58b50$@atecgrp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQIB8PrDbMCbvecnxVwRXvsvzhnYn5k2cjww
Content-Language: en-us
X-Mailman-Approved-At: Tue, 20 Aug 2013 08:05:44 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 22:19:42 -0000

Could anyone tell me how to remove my email from this distrubution?

-----Original Message-----
From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org]
On Behalf Of The IESG
Sent: Monday, August 19, 2013 6:07 PM
To: IETF-Announce
Cc: dhc mailing list; dhc chair; RFC Editor
Subject: Protocol Action: 'RADIUS Option for DHCPv6 Relay Agent' to Proposed
Standard (draft-ietf-dhc-dhcpv6-radius-opt-14.txt)

The IESG has approved the following document:
- 'RADIUS Option for DHCPv6 Relay Agent'
  (draft-ietf-dhc-dhcpv6-radius-opt-14.txt) as Proposed Standard

This document is the product of the Dynamic Host Configuration Working
Group.

The IESG contact persons are Ted Lemon and Brian Haberman.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-radius-opt/




Technical Summary:

  This document defines RADIUS DHCPv6 option that is similar to its DHCPv4
  counter-part that was defined in RFC4014. The DHCPv6 RADIUS option
provides a
  mechanism to exchange authorization and identification information between
the
  DHCPv6 relay agent and the DHCPv6 server.  This mechanism is meant for the
  centralized DHCPv6 server to select the right configuration for the
requesting
  DHCPv6 client based on the authorization information received from the
RADIUS
  server, which is not co-located with the DHCPv6 server.  The Network
Access
  Server (NAS) acts as DHCPv6 relay agent and RADIUS client simultaneously
in
  this document.

Working Group Summary:

  This document was called draft-yeh-dhc-dhcpv6-authorization-opt prior to
its
  adoption. There was unanimous support for it (9 people in favor of
adoption
  and none against), so this document was adopted in May 2012. There was
quite
  high interest in this work - 55 posts since its adoption. There was never
any
  opposition for this work.

Document Quality:

  I'm not aware of any existing implementations, but the level of support
from
  both DHCP vendors (Nominum, Weird Solutions, Cisco, ISC), hardware vendors
  (Huawei, Cisco) and operators (Orange, Telecom Italia) suggests that this
will
  be implemented and deployed shortly after option code is assigned by IANA.
  There was no single lead reviewer and many people contributed to the draft
(55
  posts about it to DHC list, 41 posts to RADEXT during its WG life). This
  document went through rapid updates (10 revisions 10 months), because its
lead
  author - Leaf Yeh - was eager to address any comments as soon as they
appeared.

Personnel:

Who is the Document Shepherd? Who is the Responsible Area Director?

  Tomek Mrugalski is the document shepherd. Ted Lemon is the responsible AD.


From lionel.morand@orange.com  Mon Aug 19 08:46:38 2013
Return-Path: <lionel.morand@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D079B11E8290; Mon, 19 Aug 2013 08:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2V7AvCseUleS; Mon, 19 Aug 2013 08:46:34 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 43D8411E8116; Mon, 19 Aug 2013 08:46:34 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id 0A9E2338039; Mon, 19 Aug 2013 17:46:33 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id D98B235C045; Mon, 19 Aug 2013 17:46:32 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Mon, 19 Aug 2013 17:46:32 +0200
From: <lionel.morand@orange.com>
To: Stefan Winter <stefan.winter@restena.lu>, "dime@ietf.org" <dime@ietf.org>,  'IETF Discussion Mailing List' <ietf@ietf.org>
Subject: RE: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
Thread-Topic: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
Thread-Index: AQHOnLSPSLtXWQYXGE65LWcMXZKnzZmcmcNQ
Date: Mon, 19 Aug 2013 15:46:31 +0000
Message-ID: <16081_1376927192_52123DD8_16081_108_1_6B7134B31289DC4FAF731D844122B36E24C0D7@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20130813162403.9625.46995.idtracker@ietfa.amsl.com> <5211D43D.2030408@restena.lu>
In-Reply-To: <5211D43D.2030408@restena.lu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.26.63617
X-Mailman-Approved-At: Tue, 20 Aug 2013 08:07:59 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2013 15:46:38 -0000

Hi Stephan,

When relying on S-NAPTR (RFC3958), redirection is only possible inside sub-=
domains of the original domain name. This is a restriction compared to the =
use of normal NAPTR and REGEXP. The following recommendations can be also f=
ound in the RFC6733: "The domain suffixes in the NAPTR replacement field SH=
OULD match the domain of the original query." Actually, I don't even unders=
tand the "SHOULD" here without any clarification on what to do if not... bu=
t it is another debate.

Therefore, my understanding is that the use of S-NAPTR is not suitable for =
redirection when the target domain name is different from the original one.=
 And the current draft proposes to allow any kind of redirection without an=
y impact on existing DNS infra.

But as I said, it is only based on my understanding and I'm not an expert o=
n DNS.

Regards,

Lionel

-----Message d'origine-----
De=A0: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part de S=
tefan Winter
Envoy=E9=A0: lundi 19 ao=FBt 2013 10:16
=C0=A0: dime@ietf.org; 'IETF Discussion Mailing List'
Objet=A0: Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.tx=
t> (Realm-Based Redirection In Diameter) to Proposed Standard

Hello,

> The IESG has received a request from the Diameter Maintenance and=20
> Extensions WG (dime) to consider the following document:
> - 'Realm-Based Redirection In Diameter'
>   <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard

Sorry for bringing this up so late, but as I was writing my own dynamic dis=
covery draft for RADIUS, it occured to me that the usage of S-NAPTR for Dia=
meter brings a built-in support to signal realm-based redirect
*if* S-NAPTR discovery is used.

That only affects this document periphally; it describes realm-based redire=
ct for agent-based redirects, not for DNS-based; but still, the wording in =
section 2 implies that using a realm-based-redirect-aware Diameter agent is=
 the only choice, and I think that should be rectified.

The mechanism for S-NAPTR realm-based redirect is built into the S-NAPTR sp=
ec by allowing for "non-terminal" lookups; this is signalled by having neit=
her an "s" flag (for SRV targets) nor an "a" flag (for A/AAAA targets); but=
 instead an "" (empty) flag. The replacement string in the NAPTR record is =
then the label of /another/ NAPTR lookup; that lookup is then to be perform=
ed with the same service/protocol tag.

That makes the whole realm-based redirect problem very easy protocol-wise. =
Consider a realm "foo.example" who wants to tell its Diameter peers that it=
s realm's application ID 123 is from now on served from "example.com". It p=
uts into DNS

foo.example.  43200   IN  NAPTR   100 10 "" "aaa+ap123:diameter.tls" ""
example.com

A client who got this answer would then query for

example.com NAPTR "aaa+ap123:diameter.tls"

and would get example.com's servers via SRV or A/AAAA records as configured=
 by the admins of example.com.

This is described in section 2.2.3 of RFC3958.

Now for the wording in the draft:

Sction 2: the first para needs a bit of a rewrite to factor in S-NAPTR's ca=
pabilities.

I suggest something along the lines of:

"Realm-based redirection is implicitly a part of the Diameter base protocol=
, but only where peer discovery using S-NAPTR is used (section
5.2 of [RFC6733], by using the non-terminal S-NAPTR flag). This allows for =
both application-specific realm-based redirects, and for application-agnost=
ic (unconditional) realm-based redirects, and does not require any Diameter=
 agents.

For deployments which do not make use of S-NAPTR peer discovery, support of=
 realm-based redirection MUST be specified as part of functionality support=
ed by a Diameter application. (... continue with the rest of the section ..=
.)

Greetings,

Stefan Winter



>=20
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2013-08-27. Exceptionally, comments may=20
> be sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    Message redirection is a basic capability provided by the Diameter
>    base protocol.  In its conventional form, message redirection is
>    performed by an application-independent "redirect agent", which
>    returns one or more individual hosts to the message sender as
>    possible destinations of the redirected message.
>=20
>    However, in some circumstances an operator may wish to redirect
>    messages to an alternate domain without specifying individual hosts.
>    This document specifies an application-specific mechanism by which
>    that can be achieved.  New applications may incorporate this
>    capability by reference to the present document.
>=20
>    Because the redirection mechanism is application-specific, it must be
>    performed by a Diameter server or proxy rather than a basic redirect
>    agent as defined in the Diameter base protocol.  A new term, "Realm-
>    based Redirect Server", is introduced in this document to
>    differentiate the application-specific nature of realm-based
>    redirection from the conventional Diameter redirection performed by a
>    basic redirect agent.
>=20
>    This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to
>    the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
>    AVPs.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/b
> allot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>    http://datatracker.ietf.org/ipr/1254/
>=20
>=20
>=20
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime
>=20


--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nationale =
et de la Recherche 6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From lorenzo@google.com  Tue Aug 20 02:39:40 2013
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D75BF11E814C for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 02:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.678
X-Spam-Level: 
X-Spam-Status: No, score=-0.678 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUStFEJlYuwz for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 02:39:40 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 3024311E8128 for <ietf@ietf.org>; Tue, 20 Aug 2013 02:39:40 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id j6so256454oag.28 for <ietf@ietf.org>; Tue, 20 Aug 2013 02:39:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=DZPCBM3NwRWeXgwzENQOWenrjemQzOMP/GDFuZ+Sn0Y=; b=kS799GDK89wAqG49vcNzm0TOCyP5te6tL5aEEkFIG35UDGraieiNGmFvEP4sg0MWPq 0HKwGI2LC8lslAgfeg5D1GnWkf2evpJYyhOlnBqKF/0qSJSgLCSyH0aGaUf8xE4g4hcf AZNMsqAR6J6M048+IzfBfa9CmrhIrUDe1rPqoVIsdDz3Z/Imiiyr+AiXTRX94dHb+WYh wNskG+86UEB4C0e8VNX1Di0FCjKbTwHzZ4qXJhzszu3cafS1QrO0B1ths+EFyfpjmb6y Kw450SSSmMzT2Base6S44NZERnk0XpymrO2CTUrSatJQwzeluh3PA4vgHdvWK8S6fLcs GG+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=DZPCBM3NwRWeXgwzENQOWenrjemQzOMP/GDFuZ+Sn0Y=; b=E/hQR34/K/LsBv4gSqnyseuYDVVNJJFgp0G42bus1JqT2fXkFr6KzbTXkfhS4A3uKF b/M+nLuDNO5UKPRbCMGvHiyG9Kwn9oBhrp5s5Es427A4RW7sAfsc7HsZPOngMOy35dAg v/H6RMreMpJ7chvFZ9IYacbmHB8KwGWZmljRXILl2Yg0tfB17J1qHDQmpZHk1dl03md2 XVtOPsyN6ahrj/BoEA8e/np+YJIty1+FRu1eW8kbdq+HRaGhNKYs+rJI4DGRY+TxteQ7 bV4clCBPdBZXJ5sgXhAKWfAE51RFiZ5vztmXxt1QQpQ/gVfrQUpWoj6jm7JUlZsPKrGI EQyg==
X-Gm-Message-State: ALoCoQk6JlDNvq2rOrOmj0FQFC4gqINptVl9thQ9HYOUVTYYcW2rPLyZIvJCbo1RUxgumT6V/bd14iLrPgUKKrHIRXJVXoJNYgHogQ+Frl7HpRu8BQGG0chbIBX1CQQvXrAOkl5M9TzBS8GZ12bIJ+Hz3DgXN0MkAPWbjZoAiHvnWXMJy8YTM+KtFi9kh8njyrD2F2vpxylU
X-Received: by 10.50.130.65 with SMTP id oc1mr4412691igb.49.1376991579484; Tue, 20 Aug 2013 02:39:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.221.132 with HTTP; Tue, 20 Aug 2013 02:39:18 -0700 (PDT)
In-Reply-To: <20130819135219.8236.40060.idtracker@ietfa.amsl.com>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 20 Aug 2013 18:39:18 +0900
Message-ID: <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b2e153bf470f504e45dd536
X-Mailman-Approved-At: Tue, 20 Aug 2013 08:07:58 -0700
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 09:39:41 -0000
X-List-Received-Date: Tue, 20 Aug 2013 09:39:41 -0000

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

On Mon, Aug 19, 2013 at 10:52 PM, The IESG <iesg-secretary@ietf.org> wrote:

>    This document specifies an IPv6 profile for 3GPP mobile devices.  It
>    lists the set of features a 3GPP mobile device is to be compliant
>    with to connect to an IPv6-only or dual-stack wireless network
>    (including 3GPP cellular network and IEEE 802.11 network).
>

I object to this document on the grounds that it is little more than a list
of (34!) features with little technical justification. I see this as a
problem because:

1. It is out of the IETF's mandate. It is not the IETF's job to specify
which features or protocols should or should not be implemented in hosts.
Even the hosts requirements RFCs are careful and sparing in their language.
The IETF is certainly not in the business of rubberstamping feature
wishlists without good technical reasons. I would challenge the authors to
find a precedent RFC containing such broad requirements.

2. It is over-broad. The vast majority of the features are in no way
necessary to build a mobile device that works well over IPv6. Today, the
overwhelming majority of mobile device traffic comes from devices that
implement only a handful of these requirements. More specifically,
requirements #3, #9, #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20,
#21, #22, #23, #24, #25, #26, #27 (a whole RFC!), #28, #29, #31, #32 (which
cover all applications running on the device - yes, all of them), and #34,
are not necessary to connect to IPv6 mobile networks.

3. It is so daunting as to act as a deterrent to IPv6 deployment. I would
challenge the authors to find a single product today that implements all,
or even a substantial majority, of these requirements. It seems to me that
the sheer length of the list, and the fact that is not prioritized, create
a real risk that implementors will simply write it off as wishful thinking
or even shy away in terror.

4. The document has few technical contributions of its own. Most of the
requirements are simply listed one after another.

I'm all for IPv6 deployment in mobile networks, but making a list of what
seems like all the features that the IETF has ever developed, and then
saying that they all need to be implemented, is not the way to get there.
The way to do it is to document use cases and working scenarios gleaned
from operational experience.

Regards,
Lorenzo

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

<div dir=3D"ltr">On Mon, Aug 19, 2013 at 10:52 PM, The IESG <span dir=3D"lt=
r">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-se=
cretary@ietf.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">=A0 =A0This document specifies an IPv6 profile for 3GPP mo=
bile devices. =A0It<br>


=A0 =A0lists the set of features a 3GPP mobile device is to be compliant<br=
>
=A0 =A0with to connect to an IPv6-only or dual-stack wireless network<br>
=A0 =A0(including 3GPP cellular network and IEEE 802.11 network).<br></bloc=
kquote><div>=A0</div><div>I object to this document on the grounds that it =
is little more than a list of (34!) features with little technical justific=
ation. I see this as a problem because:</div>

<div><br></div><div>1. It is out of the IETF&#39;s mandate. It is not the I=
ETF&#39;s job to specify which features or protocols should or should not b=
e implemented in hosts. Even the hosts requirements RFCs are careful and sp=
aring in their language. The IETF is certainly not in the business of rubbe=
rstamping feature wishlists without good technical reasons. I would challen=
ge the authors to find a precedent RFC containing such broad requirements.<=
/div>

<div><br></div><div>2. It is over-broad. The vast majority of the features =
are in no way necessary to build a mobile device that works well over IPv6.=
 Today, the overwhelming majority of mobile device traffic comes from devic=
es that implement only a handful of these requirements. More specifically, =
requirements #3, #9, #10, #11, #12, #13, #14, #15, #16, #17, #18, #19, #20,=
 #21, #22, #23, #24, #25, #26, #27 (a whole RFC!), #28, #29, #31, #32 (whic=
h cover all applications running on the device - yes, all of them), and #34=
, are not necessary to connect to IPv6 mobile networks.</div>

<div><br></div><div>3. It is so daunting as to act as a deterrent to IPv6 d=
eployment. I would challenge the authors to find a single product today tha=
t implements all, or even a substantial majority, of these requirements. It=
 seems to me that the sheer length of the list, and the fact that is not pr=
ioritized, create a real risk that implementors will simply write it off as=
 wishful thinking or even=A0shy away in terror.<br>

</div><div><br></div><div>4. The document has few technical contributions o=
f its own. Most of the requirements are simply listed one after another.</d=
iv><div><br></div><div>I&#39;m all for IPv6 deployment in mobile networks, =
but making a list of what seems like all the features that the IETF has eve=
r developed, and then saying that they all need to be implemented, is not t=
he way to get there. The way to do it is to document use cases and working =
scenarios gleaned from operational experience.</div>

<div><br></div><div>Regards,</div><div>Lorenzo</div></div></div></div>

--047d7b2e153bf470f504e45dd536--

From lionel.morand@orange.com  Tue Aug 20 04:07:08 2013
Return-Path: <lionel.morand@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85EA021F9346; Tue, 20 Aug 2013 04:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, 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 tN8ivl6Pna0R; Tue, 20 Aug 2013 04:07:04 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id DFD9011E81F5; Tue, 20 Aug 2013 04:07:03 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 8CDE03B5129; Tue, 20 Aug 2013 13:07:02 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id 708C34C063; Tue, 20 Aug 2013 13:07:02 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 20 Aug 2013 13:07:02 +0200
From: <lionel.morand@orange.com>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: RE: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
Thread-Topic: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
Thread-Index: AQHOnLSPSLtXWQYXGE65LWcMXZKnzZmcmcNQgADquYCAAEt90A==
Date: Tue, 20 Aug 2013 11:07:01 +0000
Message-ID: <25683_1376996822_52134DD6_25683_1915_1_6B7134B31289DC4FAF731D844122B36E24D288@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20130813162403.9625.46995.idtracker@ietfa.amsl.com> <5211D43D.2030408@restena.lu> <16081_1376927192_52123DD8_16081_108_1_6B7134B31289DC4FAF731D844122B36E24C0D7@PEXCVZYM13.corporate.adroot.infra.ftgroup> <52130E9D.9080602@restena.lu>
In-Reply-To: <52130E9D.9080602@restena.lu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.6.28.101520
X-Mailman-Approved-At: Tue, 20 Aug 2013 08:08:00 -0700
Cc: "dime@ietf.org" <dime@ietf.org>, '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: Tue, 20 Aug 2013 11:07:08 -0000

Hi Stephan,

Thank you for quick feedback.
I agree with your analysis. I think that we should provide more info on the=
 possible use of S-NAPTR for realm-based redirection.
Taking into account your proposal, what do you think of the following propo=
sed changes:


Abstract:

OLD:=20=20
=20
   However, in some circumstances an operator may wish to redirect
   messages to an alternate domain without specifying individual hosts.
   This document specifies an application-specific mechanism by which
   that can be achieved.  New applications may incorporate this
   capability by reference to the present document.

NEW:

   However, in some circumstances an operator may wish to redirect
   messages to an alternate domain without specifying individual hosts.
   This document specifies an application-specific mechanism by which
   that can be achieved when S-NAPTR is not used for dynamic peer discovery=
.=20
   New applications may incorporate this capability by reference to the=20
   present document.



Section 2:

OLD:

   Because realm-based redirection is not part of the Diameter base
   protocol [RFC6733], support of realm-based redirection MUST be
   specified as part of functionality supported by a Diameter
   application.  In this way, support of the considered Diameter
   application (discovered during capabilities exchange procedures as
   defined in Diameter base protocol [RFC6733]) indicates implicit
   support of the realm-based redirection mechanism.  Designers of new
   applications can incorporate the mechanism specified here into their
   application by normative reference to this document.

   The result of making realm-based redirection an application-specific
   behaviour is that it cannot be performed by a redirect agent as
   defined in [RFC6733], but MUST be performed instead by an
   application-aware Diameter node (Diameter server or proxy) (hereafter
   called a "Realm-based Redirect Server").

   An application can specify that realm-based redirection operates only
   on complete sessions beginning with the initial message, or on every
   message within the application, even if earlier messages of the same
   session were not redirected.  This distinction matters only when
   realm-based redirection is first initiated.  In the former case,
   existing sessions will not be disrupted by the deployment of realm-
   based redirection.  In the latter case, existing sessions will be
   disrupted if they are stateful.

NEW:

   Using the S-NAPTR DDDS application [RFC3958], the DNS-based dynamic peer=
=20
   discovery mechanism defined in the Diameter base protocol [RFC6733]
   provides a simple mechanism for realm-based redirection. When S-NAPTR is
   used for peer discovery, redirection of Diameter request from the origin=
al
   realm to a new realm may be performed by updating the existing NAPTR res=
ource
   records for the original realm as follow: the NAPTR RR for the desired=
=20
   application(s) and supported application protocol(s) provided by the=20
   new realm will have an empty FLAG field and the REPLACEMENT field will
   contain the new realm to use for the next DNS lookup.

   However, the use of DNS-based dynamic peer discovery is optional for Dia=
meter=20
   implementations. For deployments which do not make use of S-NAPTR peer=
=20
   discovery, support of realm-based redirection MUST be specified as part =
of=20
   functionality supported by a Diameter application.  In this way, support=
 of the=20
   considered Diameter application (discovered during capabilities exchange=
=20
   procedures as defined in Diameter base protocol [RFC6733]) indicates=20
   implicit support of the realm-based redirection mechanism.  Designers of
   new applications can incorporate the mechanism specified here into their=
=20
   application by normative reference to this document.

   The result of making realm-based redirection an application-specific
   behaviour is that it cannot be performed by a redirect agent as
   defined in [RFC6733], but MUST be performed instead by an
   application-aware Diameter node (Diameter server or proxy) (hereafter
   called a "Realm-based Redirect Server").

   An application can specify that realm-based redirection operates only
   on complete sessions beginning with the initial message, or on every
   message within the application, even if earlier messages of the same
   session were not redirected.  This distinction matters only when
   realm-based redirection is first initiated.  In the former case,
   existing sessions will not be disrupted by the deployment of realm-
   based redirection.  In the latter case, existing sessions will be
   disrupted if they are stateful.

Regards,

Lionel

-----Message d'origine-----
De=A0: Stefan Winter [mailto:stefan.winter@restena.lu]=20
Envoy=E9=A0: mardi 20 ao=FBt 2013 08:37
=C0=A0: MORAND Lionel OLNC/OLN
Cc=A0: dime@ietf.org; 'IETF Discussion Mailing List'
Objet=A0: Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.tx=
t> (Realm-Based Redirection In Diameter) to Proposed Standard

Hi,

> When relying on S-NAPTR (RFC3958), redirection is only possible inside su=
b-domains of the original domain name.

I don't think that's true. RFC3958 has exactly this use case in it's first =
example section (2.2): a domain example.com redirects service "EM:protA" to=
 another domain, namely someisp.example - with the non-terminal flag, as I =
described in my original mail. This is absolutely a different domain name.

> This is a restriction compared to the use of normal NAPTR and REGEXP.

While making my own experiences with NAPTR, I learned that there is no "nor=
mal" use of NAPTR. NAPTR records are not allowed to be used "in the wild" w=
ithout a valid DDDS specification defining its exact semantics.
That is precisely the reason why RFC3588 had to be revised in that regard. =
RFC3958 provides that semantics, so it was a natural choice to re-base Diam=
eter's usage in an S-NAPTR.

> The following recommendations can be also found in the RFC6733: "The doma=
in suffixes in the NAPTR replacement field SHOULD match the domain of the o=
riginal query." Actually, I don't even understand the "SHOULD" here without=
 any clarification on what to do if not... but it is another debate.

I now see that RFC6733 has put this IMHO arbitrary restriction in place.
It really serves no particular purpose; if there was some thinking behind i=
t, then that really should have been explained in the document.

I would tend to ignore that SHOULD if I were implementing Diameter (I'm not=
 :-) ). Different domain names are perfectly in scope for S-NAPTRs, and you=
 would have to consciously lobotomise libraries or code snippets to *not* p=
ermit redirections to other domains.

We are also regularly using s-flag S-NAPTRs in eduroam and RADIUS Dynamic D=
iscovery to point to a delegate RADIUS server residing in a different domai=
n. It's just normal operations.

This limitation in RFC6733 is at best "funny" IMHO.

> Therefore, my understanding is that the use of S-NAPTR is not suitable fo=
r redirection when the target domain name is different from the original on=
e. And the current draft proposes to allow any kind of redirection without =
any impact on existing DNS infra.

I would rather take a very good look at the section in RFC6733 that discour=
ages other domain names in the replacement. It's more like an erratum for m=
e; and if that restriction were away you would have a working solution to y=
our redirection problem with zero effort.

And anyway, it's a SHOULD without considerations or consequences attached. =
Which makes it more of a DONTCARE anyway ;-)

> But as I said, it is only based on my understanding and I'm not an expert=
 on DNS.

I don't think DNS is the problem here. It's more that Diameter butchers its=
 NAPTR usage unnecessarily.

Greetings,

Stefan Winter

>=20
> Regards,
>=20
> Lionel
>=20
> -----Message d'origine-----
> De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part=20
> de Stefan Winter Envoy=E9 : lundi 19 ao=FBt 2013 10:16 =C0 : dime@ietf.or=
g;=20
> 'IETF Discussion Mailing List'
> Objet : Re: [Dime] Last Call:=20
> <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based Redirection=20
> In Diameter) to Proposed Standard
>=20
> Hello,
>=20
>> The IESG has received a request from the Diameter Maintenance and=20
>> Extensions WG (dime) to consider the following document:
>> - 'Realm-Based Redirection In Diameter'
>>   <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard
>=20
> Sorry for bringing this up so late, but as I was writing my own=20
> dynamic discovery draft for RADIUS, it occured to me that the usage of=20
> S-NAPTR for Diameter brings a built-in support to signal realm-based=20
> redirect
> *if* S-NAPTR discovery is used.
>=20
> That only affects this document periphally; it describes realm-based redi=
rect for agent-based redirects, not for DNS-based; but still, the wording i=
n section 2 implies that using a realm-based-redirect-aware Diameter agent =
is the only choice, and I think that should be rectified.
>=20
> The mechanism for S-NAPTR realm-based redirect is built into the S-NAPTR =
spec by allowing for "non-terminal" lookups; this is signalled by having ne=
ither an "s" flag (for SRV targets) nor an "a" flag (for A/AAAA targets); b=
ut instead an "" (empty) flag. The replacement string in the NAPTR record i=
s then the label of /another/ NAPTR lookup; that lookup is then to be perfo=
rmed with the same service/protocol tag.
>=20
> That makes the whole realm-based redirect problem very easy=20
> protocol-wise. Consider a realm "foo.example" who wants to tell its=20
> Diameter peers that its realm's application ID 123 is from now on=20
> served from "example.com". It puts into DNS
>=20
> foo.example.  43200   IN  NAPTR   100 10 "" "aaa+ap123:diameter.tls" ""
> example.com
>=20
> A client who got this answer would then query for
>=20
> example.com NAPTR "aaa+ap123:diameter.tls"
>=20
> and would get example.com's servers via SRV or A/AAAA records as configur=
ed by the admins of example.com.
>=20
> This is described in section 2.2.3 of RFC3958.
>=20
> Now for the wording in the draft:
>=20
> Sction 2: the first para needs a bit of a rewrite to factor in S-NAPTR's =
capabilities.
>=20
> I suggest something along the lines of:
>=20
> "Realm-based redirection is implicitly a part of the Diameter base=20
> protocol, but only where peer discovery using S-NAPTR is used (section
> 5.2 of [RFC6733], by using the non-terminal S-NAPTR flag). This allows fo=
r both application-specific realm-based redirects, and for application-agno=
stic (unconditional) realm-based redirects, and does not require any Diamet=
er agents.
>=20
> For deployments which do not make use of S-NAPTR peer discovery,=20
> support of realm-based redirection MUST be specified as part of=20
> functionality supported by a Diameter application. (... continue with=20
> the rest of the section ...)
>=20
> Greetings,
>=20
> Stefan Winter
>=20
>=20
>=20
>>
>> The IESG plans to make a decision in the next few weeks, and solicits=20
>> final comments on this action. Please send substantive comments to=20
>> the ietf@ietf.org mailing lists by 2013-08-27. Exceptionally,=20
>> comments may be sent to iesg@ietf.org instead. In either case, please=20
>> retain the beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    Message redirection is a basic capability provided by the Diameter
>>    base protocol.  In its conventional form, message redirection is
>>    performed by an application-independent "redirect agent", which
>>    returns one or more individual hosts to the message sender as
>>    possible destinations of the redirected message.
>>
>>    However, in some circumstances an operator may wish to redirect
>>    messages to an alternate domain without specifying individual hosts.
>>    This document specifies an application-specific mechanism by which
>>    that can be achieved.  New applications may incorporate this
>>    capability by reference to the present document.
>>
>>    Because the redirection mechanism is application-specific, it must be
>>    performed by a Diameter server or proxy rather than a basic redirect
>>    agent as defined in the Diameter base protocol.  A new term, "Realm-
>>    based Redirect Server", is introduced in this document to
>>    differentiate the application-specific nature of realm-based
>>    redirection from the conventional Diameter redirection performed by a
>>    basic redirect agent.
>>
>>    This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to
>>    the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
>>    AVPs.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect/
>> b
>> allot/
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>>    http://datatracker.ietf.org/ipr/1254/
>>
>>
>>
>> _______________________________________________
>> DiME mailing list
>> DiME@ietf.org
>> https://www.ietf.org/mailman/listinfo/dime
>>
>=20
>=20
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e=20
> et de la Recherche 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
>=20
> ______________________________________________________________________
> ___________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations=20
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20
> exploites ou copies sans autorisation. Si vous avez recu ce message=20
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que =
les pieces jointes. Les messages electroniques etant susceptibles d'alterat=
ion, Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or=20
> privileged information that may be protected by law; they should not be d=
istributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>=20


--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nationale =
et de la Recherche 6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From lionel.morand@orange.com  Tue Aug 20 04:39:13 2013
Return-Path: <lionel.morand@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 048E111E8215; Tue, 20 Aug 2013 04:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, 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 CxKnpLGKha9L; Tue, 20 Aug 2013 04:39:09 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA1C11E80D9; Tue, 20 Aug 2013 04:39:08 -0700 (PDT)
Received: from omfedm07.si.francetelecom.fr (unknown [xx.xx.xx.3]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 08880324D27; Tue, 20 Aug 2013 13:39:00 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm07.si.francetelecom.fr (ESMTP service) with ESMTP id DDC4F4C06B; Tue, 20 Aug 2013 13:38:59 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.02.0328.009; Tue, 20 Aug 2013 13:38:59 +0200
From: <lionel.morand@orange.com>
To: Stefan Winter <stefan.winter@restena.lu>
Subject: RE: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
Thread-Topic: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based	Redirection In Diameter) to Proposed Standard
Thread-Index: AQHOnLSPSLtXWQYXGE65LWcMXZKnzZmcmcNQgADquYCAAEt90IAACFOAgAAh5XA=
Date: Tue, 20 Aug 2013 11:38:58 +0000
Message-ID: <25685_1376998739_52135553_25685_8637_1_6B7134B31289DC4FAF731D844122B36E24D356@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <20130813162403.9625.46995.idtracker@ietfa.amsl.com> <5211D43D.2030408@restena.lu> <16081_1376927192_52123DD8_16081_108_1_6B7134B31289DC4FAF731D844122B36E24C0D7@PEXCVZYM13.corporate.adroot.infra.ftgroup> <52130E9D.9080602@restena.lu> <25683_1376996822_52134DD6_25683_1915_1_6B7134B31289DC4FAF731D844122B36E24D288@PEXCVZYM13.corporate.adroot.infra.ftgroup> <521354EB.3080900@restena.lu>
In-Reply-To: <521354EB.3080900@restena.lu>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.8.20.72416
X-Mailman-Approved-At: Tue, 20 Aug 2013 08:08:00 -0700
Cc: "dime@ietf.org" <dime@ietf.org>, '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: Tue, 20 Aug 2013 11:39:13 -0000

Works for me.

Regards,

Lionel

-----Message d'origine-----
De=A0: Stefan Winter [mailto:stefan.winter@restena.lu]=20
Envoy=E9=A0: mardi 20 ao=FBt 2013 13:37
=C0=A0: MORAND Lionel OLNC/OLN
Cc=A0: dime@ietf.org; 'IETF Discussion Mailing List'
Objet=A0: Re: [Dime] Last Call: <draft-ietf-dime-realm-based-redirect-11.tx=
t> (Realm-Based Redirection In Diameter) to Proposed Standard

Hi,

> Thank you for quick feedback.
> I agree with your analysis. I think that we should provide more info on t=
he possible use of S-NAPTR for realm-based redirection.
> Taking into account your proposal, what do you think of the following pro=
posed changes:

The new text reads pretty well.

One thing worth considering is maybe: this draft already updates RFC6733. I=
t may be worth making explicit that the RFC6733 SHOULD regarding same-domai=
n targets is being made obsolete in by this draft.

One more sentence in the section 2 text below should do the trick:


> NEW:
>=20
>    Using the S-NAPTR DDDS application [RFC3958], the DNS-based dynamic pe=
er=20
>    discovery mechanism defined in the Diameter base protocol [RFC6733]
>    provides a simple mechanism for realm-based redirection. When S-NAPTR =
is
>    used for peer discovery, redirection of Diameter request from the orig=
inal
>    realm to a new realm may be performed by updating the existing NAPTR r=
esource
>    records for the original realm as follow: the NAPTR RR for the desired=
=20
>    application(s) and supported application protocol(s) provided by the=
=20
>    new realm will have an empty FLAG field and the REPLACEMENT field will
>    contain the new realm to use for the next DNS lookup.

ADD:

The new realm can be arbitrary; the restriction in RFC6733 that the NAPTR r=
eplacement field SHOULD match the domain of the original query does not app=
ly for realm-based redirect purposes.

All the rest of the text is fine.

Greetings,

Stefan Winter

>=20
>    However, the use of DNS-based dynamic peer discovery is optional for D=
iameter=20
>    implementations. For deployments which do not make use of S-NAPTR peer=
=20
>    discovery, support of realm-based redirection MUST be specified as par=
t of=20
>    functionality supported by a Diameter application.  In this way, suppo=
rt of the=20
>    considered Diameter application (discovered during capabilities exchan=
ge=20
>    procedures as defined in Diameter base protocol [RFC6733]) indicates=
=20
>    implicit support of the realm-based redirection mechanism.  Designers =
of
>    new applications can incorporate the mechanism specified here into the=
ir=20
>    application by normative reference to this document.
>=20
>    The result of making realm-based redirection an application-specific
>    behaviour is that it cannot be performed by a redirect agent as
>    defined in [RFC6733], but MUST be performed instead by an
>    application-aware Diameter node (Diameter server or proxy) (hereafter
>    called a "Realm-based Redirect Server").
>=20
>    An application can specify that realm-based redirection operates only
>    on complete sessions beginning with the initial message, or on every
>    message within the application, even if earlier messages of the same
>    session were not redirected.  This distinction matters only when
>    realm-based redirection is first initiated.  In the former case,
>    existing sessions will not be disrupted by the deployment of realm-
>    based redirection.  In the latter case, existing sessions will be
>    disrupted if they are stateful.
>=20
> Regards,
>=20
> Lionel
>=20
> -----Message d'origine-----
> De : Stefan Winter [mailto:stefan.winter@restena.lu] Envoy=E9 : mardi 20=
=20
> ao=FBt 2013 08:37 =C0 : MORAND Lionel OLNC/OLN Cc : dime@ietf.org; 'IETF=
=20
> Discussion Mailing List'
> Objet : Re: [Dime] Last Call:=20
> <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based Redirection=20
> In Diameter) to Proposed Standard
>=20
> Hi,
>=20
>> When relying on S-NAPTR (RFC3958), redirection is only possible inside s=
ub-domains of the original domain name.
>=20
> I don't think that's true. RFC3958 has exactly this use case in it's firs=
t example section (2.2): a domain example.com redirects service "EM:protA" =
to another domain, namely someisp.example - with the non-terminal flag, as =
I described in my original mail. This is absolutely a different domain name.
>=20
>> This is a restriction compared to the use of normal NAPTR and REGEXP.
>=20
> While making my own experiences with NAPTR, I learned that there is no "n=
ormal" use of NAPTR. NAPTR records are not allowed to be used "in the wild"=
 without a valid DDDS specification defining its exact semantics.
> That is precisely the reason why RFC3588 had to be revised in that regard=
. RFC3958 provides that semantics, so it was a natural choice to re-base Di=
ameter's usage in an S-NAPTR.
>=20
>> The following recommendations can be also found in the RFC6733: "The dom=
ain suffixes in the NAPTR replacement field SHOULD match the domain of the =
original query." Actually, I don't even understand the "SHOULD" here withou=
t any clarification on what to do if not... but it is another debate.
>=20
> I now see that RFC6733 has put this IMHO arbitrary restriction in place.
> It really serves no particular purpose; if there was some thinking behind=
 it, then that really should have been explained in the document.
>=20
> I would tend to ignore that SHOULD if I were implementing Diameter (I'm n=
ot :-) ). Different domain names are perfectly in scope for S-NAPTRs, and y=
ou would have to consciously lobotomise libraries or code snippets to *not*=
 permit redirections to other domains.
>=20
> We are also regularly using s-flag S-NAPTRs in eduroam and RADIUS Dynamic=
 Discovery to point to a delegate RADIUS server residing in a different dom=
ain. It's just normal operations.
>=20
> This limitation in RFC6733 is at best "funny" IMHO.
>=20
>> Therefore, my understanding is that the use of S-NAPTR is not suitable f=
or redirection when the target domain name is different from the original o=
ne. And the current draft proposes to allow any kind of redirection without=
 any impact on existing DNS infra.
>=20
> I would rather take a very good look at the section in RFC6733 that disco=
urages other domain names in the replacement. It's more like an erratum for=
 me; and if that restriction were away you would have a working solution to=
 your redirection problem with zero effort.
>=20
> And anyway, it's a SHOULD without considerations or consequences=20
> attached. Which makes it more of a DONTCARE anyway ;-)
>=20
>> But as I said, it is only based on my understanding and I'm not an exper=
t on DNS.
>=20
> I don't think DNS is the problem here. It's more that Diameter butchers i=
ts NAPTR usage unnecessarily.
>=20
> Greetings,
>=20
> Stefan Winter
>=20
>>
>> Regards,
>>
>> Lionel
>>
>> -----Message d'origine-----
>> De : dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] De la part=20
>> de Stefan Winter Envoy=E9 : lundi 19 ao=FBt 2013 10:16 =C0 : dime@ietf.o=
rg;=20
>> 'IETF Discussion Mailing List'
>> Objet : Re: [Dime] Last Call:=20
>> <draft-ietf-dime-realm-based-redirect-11.txt> (Realm-Based=20
>> Redirection In Diameter) to Proposed Standard
>>
>> Hello,
>>
>>> The IESG has received a request from the Diameter Maintenance and=20
>>> Extensions WG (dime) to consider the following document:
>>> - 'Realm-Based Redirection In Diameter'
>>>   <draft-ietf-dime-realm-based-redirect-11.txt> as Proposed Standard
>>
>> Sorry for bringing this up so late, but as I was writing my own=20
>> dynamic discovery draft for RADIUS, it occured to me that the usage=20
>> of S-NAPTR for Diameter brings a built-in support to signal=20
>> realm-based redirect
>> *if* S-NAPTR discovery is used.
>>
>> That only affects this document periphally; it describes realm-based red=
irect for agent-based redirects, not for DNS-based; but still, the wording =
in section 2 implies that using a realm-based-redirect-aware Diameter agent=
 is the only choice, and I think that should be rectified.
>>
>> The mechanism for S-NAPTR realm-based redirect is built into the S-NAPTR=
 spec by allowing for "non-terminal" lookups; this is signalled by having n=
either an "s" flag (for SRV targets) nor an "a" flag (for A/AAAA targets); =
but instead an "" (empty) flag. The replacement string in the NAPTR record =
is then the label of /another/ NAPTR lookup; that lookup is then to be perf=
ormed with the same service/protocol tag.
>>
>> That makes the whole realm-based redirect problem very easy=20
>> protocol-wise. Consider a realm "foo.example" who wants to tell its=20
>> Diameter peers that its realm's application ID 123 is from now on=20
>> served from "example.com". It puts into DNS
>>
>> foo.example.  43200   IN  NAPTR   100 10 "" "aaa+ap123:diameter.tls" ""
>> example.com
>>
>> A client who got this answer would then query for
>>
>> example.com NAPTR "aaa+ap123:diameter.tls"
>>
>> and would get example.com's servers via SRV or A/AAAA records as configu=
red by the admins of example.com.
>>
>> This is described in section 2.2.3 of RFC3958.
>>
>> Now for the wording in the draft:
>>
>> Sction 2: the first para needs a bit of a rewrite to factor in S-NAPTR's=
 capabilities.
>>
>> I suggest something along the lines of:
>>
>> "Realm-based redirection is implicitly a part of the Diameter base=20
>> protocol, but only where peer discovery using S-NAPTR is used=20
>> (section
>> 5.2 of [RFC6733], by using the non-terminal S-NAPTR flag). This allows f=
or both application-specific realm-based redirects, and for application-agn=
ostic (unconditional) realm-based redirects, and does not require any Diame=
ter agents.
>>
>> For deployments which do not make use of S-NAPTR peer discovery,=20
>> support of realm-based redirection MUST be specified as part of=20
>> functionality supported by a Diameter application. (... continue with=20
>> the rest of the section ...)
>>
>> Greetings,
>>
>> Stefan Winter
>>
>>
>>
>>>
>>> The IESG plans to make a decision in the next few weeks, and=20
>>> solicits final comments on this action. Please send substantive=20
>>> comments to the ietf@ietf.org mailing lists by 2013-08-27.=20
>>> Exceptionally, comments may be sent to iesg@ietf.org instead. In=20
>>> either case, please retain the beginning of the Subject line to allow a=
utomated sorting.
>>>
>>> Abstract
>>>
>>>
>>>    Message redirection is a basic capability provided by the Diameter
>>>    base protocol.  In its conventional form, message redirection is
>>>    performed by an application-independent "redirect agent", which
>>>    returns one or more individual hosts to the message sender as
>>>    possible destinations of the redirected message.
>>>
>>>    However, in some circumstances an operator may wish to redirect
>>>    messages to an alternate domain without specifying individual hosts.
>>>    This document specifies an application-specific mechanism by which
>>>    that can be achieved.  New applications may incorporate this
>>>    capability by reference to the present document.
>>>
>>>    Because the redirection mechanism is application-specific, it must be
>>>    performed by a Diameter server or proxy rather than a basic redirect
>>>    agent as defined in the Diameter base protocol.  A new term, "Realm-
>>>    based Redirect Server", is introduced in this document to
>>>    differentiate the application-specific nature of realm-based
>>>    redirection from the conventional Diameter redirection performed by a
>>>    basic redirect agent.
>>>
>>>    This memo updates Sections 6.13 and 6.14 of RFC6733 with respect to
>>>    the usage of the Redirect-Host-Usage and Redirect-Max-Cache-Time
>>>    AVPs.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect
>>> /
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-dime-realm-based-redirect
>>> /
>>> b
>>> allot/
>>>
>>>
>>> The following IPR Declarations may be related to this I-D:
>>>
>>>    http://datatracker.ietf.org/ipr/1254/
>>>
>>>
>>>
>>> _______________________________________________
>>> DiME mailing list
>>> DiME@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dime
>>>
>>
>>
>> --
>> Stefan WINTER
>> Ingenieur de Recherche
>> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nationa=
le=20
>> et de la Recherche 6, rue Richard Coudenhove-Kalergi
>> L-1359 Luxembourg
>>
>> Tel: +352 424409 1
>> Fax: +352 422473
>>
>>
>> _____________________________________________________________________
>> _ ___________________________________________________
>>
>> Ce message et ses pieces jointes peuvent contenir des informations=20
>> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20
>> exploites ou copies sans autorisation. Si vous avez recu ce message=20
>> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que=
 les pieces jointes. Les messages electroniques etant susceptibles d'altera=
tion, Orange decline toute responsabilite si ce message a ete altere, defor=
me ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or=20
>> privileged information that may be protected by law; they should not be =
distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and d=
elete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have be=
en modified, changed or falsified.
>> Thank you.
>>
>=20
>=20
> --
> Stefan WINTER
> Ingenieur de Recherche
> Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e=20
> et de la Recherche 6, rue Richard Coudenhove-Kalergi
> L-1359 Luxembourg
>=20
> Tel: +352 424409 1
> Fax: +352 422473
>=20
>=20
> ______________________________________________________________________
> ___________________________________________________
>=20
> Ce message et ses pieces jointes peuvent contenir des informations=20
> confidentielles ou privilegiees et ne doivent donc pas etre diffuses,=20
> exploites ou copies sans autorisation. Si vous avez recu ce message=20
> par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que =
les pieces jointes. Les messages electroniques etant susceptibles d'alterat=
ion, Orange decline toute responsabilite si ce message a ete altere, deform=
e ou falsifie. Merci.
>=20
> This message and its attachments may contain confidential or=20
> privileged information that may be protected by law; they should not be d=
istributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>=20


--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nationale =
et de la Recherche 6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


From marka@isc.org  Tue Aug 20 08:13:16 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9749611E822C for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.191
X-Spam-Level: 
X-Spam-Status: No, score=-2.191 tagged_above=-999 required=5 tests=[AWL=0.408,  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 7dAsU8Q9I6zx for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:13:11 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id C709711E8225 for <ietf@ietf.org>; Tue, 20 Aug 2013 08:13:11 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id BC83CC94D1; Tue, 20 Aug 2013 15:12:57 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377011590; bh=B8gMORvZktqhF09WOKll9xQ78jvSSzrcvNScZK38rBs=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=Sgowm2lgN7mukoiqtigCkiixOcWcnvCDSUUZm2At07pDpA1ihl7EqBH/jZPIwMIZK peYijICWggnHTbs37j4ilSJdxDFnR0QUtd6GbDFrf9riyv8C9/GHIAK4tirLSzRXq6 EIkY936hdeP2I8G+gYClDENFn11JcSsWhUDCTQaE=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Tue, 20 Aug 2013 15:12:57 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id F358B1602B4; Tue, 20 Aug 2013 15:13:03 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id C5085160219; Tue, 20 Aug 2013 15:13:03 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 8C49538B579B; Wed, 21 Aug 2013 01:12:55 +1000 (EST)
To: "John Levine" <johnl@taugh.com>
From: Mark Andrews <marka@isc.org>
References: <20130820144548.73129.qmail@joyce.lan>
Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
In-reply-to: Your message of "20 Aug 2013 14:45:48 +0000." <20130820144548.73129.qmail@joyce.lan>
Date: Wed, 21 Aug 2013 01:12:55 +1000
Message-Id: <20130820151255.8C49538B579B@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org, paf@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 15:13:16 -0000

In message <20130820144548.73129.qmail@joyce.lan>, "John Levine" writes:
> Newsgroups: iecc.lists.ietf.ietf
> From: John Levine <johnl@iecc.com>
> Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408b
> is-19.txt>
> Summary:
> Expires:
> References: <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D444
> 1A@frobbit.se> <5213174D.7080504@dcrocker.net> <D2148A40-2673-40C7-8349-0A65D
> 0D01794@frobbit.se>
> Sender:
> Followup-To:
> Distribution: 
> Organization: 
> Keywords: 
> Cc: 
> Cleverness: some
> 
> >The two following MIGHT NOT be in the same zone:
> >
> >foo.example. IN X RDATAX
> >_bar.foo.example. IN TXT RDATAY
> 
> Since prefixed names have never been used for anything other than
> providing information about the unprefixed name, what conceivable
> operational reason could there be to put a zone cut at the prefix?

When you have "_users" and you want to move the users out of the
hosts namespace and have whom ever deals with people manage that
part of the namespace.

> This impresses me as one of those problems where the solution is
> "don't do that."

There are good reasons to split off administrative control.  "don't
do that" isn't a answer.

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

From dhc@dcrocker.net  Tue Aug 20 08:47:42 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8597921F9C47 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.122
X-Spam-Level: 
X-Spam-Status: No, score=-6.122 tagged_above=-999 required=5 tests=[AWL=-0.423, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, MIME_8BIT_HEADER=0.3, 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 t-OI-jXCqrjX for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:47:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3A011E8229 for <ietf@ietf.org>; Tue, 20 Aug 2013 08:47:32 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7KFlLxu027805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Aug 2013 08:47:24 -0700
Message-ID: <52138F71.3050203@dcrocker.net>
Date: Tue, 20 Aug 2013 08:46:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <patrik@frobbit.se>
Subject: Re: [spfbis] prefixed names, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
References: <20130820144548.73129.qmail@joyce.lan> <20130820151255.8C49538B579B@drugs.dv.isc.org>
In-Reply-To: <20130820151255.8C49538B579B@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 20 Aug 2013 08:47:26 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 15:47:42 -0000

On 8/20/2013 8:12 AM, Mark Andrews wrote:
> In message <20130820144548.73129.qmail@joyce.lan>, "John Levine" writes:
...
>>> The two following MIGHT NOT be in the same zone:
>>>
>>> foo.example. IN X RDATAX
>>> _bar.foo.example. IN TXT RDATAY
>>
>> Since prefixed names have never been used for anything other than
>> providing information about the unprefixed name, what conceivable
>> operational reason could there be to put a zone cut at the prefix?
>
> When you have "_users" and you want to move the users out of the
> hosts namespace and have whom ever deals with people manage that
> part of the namespace.
>
>> This impresses me as one of those problems where the solution is
>> "don't do that."
>
> There are good reasons to split off administrative control.  "don't
> do that" isn't a answer.


Exactly right.  For some of the 'underscore' uses, maintenance of the 
information in that subordinate node is best performed by a team that is 
separate from the regular DNS operations people.

DKIM is an easy example, since the records often are better handled by 
the email operations folk.

So I'm continuing to miss the 'problem' here.  Being able to separate 
administration of the underscore-based attribute information is a 
feature, not a bug.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Tue Aug 20 08:54:41 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8C221F9CC6 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:54:39 -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 mlrNpQAcCC3S for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 08:54:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 34EA121F9C99 for <ietf@ietf.org>; Tue, 20 Aug 2013 08:54:30 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7KFsQFp027957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 20 Aug 2013 08:54:30 -0700
Message-ID: <5213911A.6010301@dcrocker.net>
Date: Tue, 20 Aug 2013 08:54:02 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net> <20130820144646.GE20618@mx1.yitter.info>
In-Reply-To: <20130820144646.GE20618@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 20 Aug 2013 08:54:30 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 15:54:41 -0000

> Quite apart from the DNSSEC example that Patrik sent, underscore
> labels also cause problems and confusion when aliases are involved.
> The alias stuff is a corner case, of course, but it's still a basic
> problem with the approach of specifying policy for a target name at a
> different name than the target itself.  This trade-off might be a
> legitimate one (I certainly think it's preferable to the strategy SPF
> adopted, of stepping all over the TXT RRTYPE at a given name), but it
> won't do to dismiss the problem with a point-and-laugh argument.


Use of underscore names does impose some limitations.  Occasionally 
those limitations are noteworthy for real-world operations, but 
experience across a range of applications so far has not created any 
show-stoppers.

One of the more serious problems about using the underscore construct is 
that arguments against it sometimes are based on an insistence for 
pure-and-complete original DNS capabilities, rather than attending to 
the real-world utility.  It would be nice to have the construct impose 
no additional constraints, but 'nice' isn't the same as 'necessary', 
when evaluating pragmatic trade-offs.

In other words, the specific technical limitations being noted are 
unfortunate but (so far) not serious.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ajs@anvilwalrusden.com  Tue Aug 20 09:08:52 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B194A11E80E1 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 09:08:52 -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 XoYpusHOYn-b for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 09:08:47 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id AD94E11E80E4 for <ietf@ietf.org>; Tue, 20 Aug 2013 09:08:46 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 7387D8A035 for <ietf@ietf.org>; Tue, 20 Aug 2013 16:08:45 +0000 (UTC)
Date: Tue, 20 Aug 2013 12:08:44 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130820160844.GE21439@mx1.yitter.info>
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net> <20130820144646.GE20618@mx1.yitter.info> <5213911A.6010301@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5213911A.6010301@dcrocker.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 16:08:53 -0000

On Tue, Aug 20, 2013 at 08:54:02AM -0700, Dave Crocker wrote:

> In other words, the specific technical limitations being noted are
> unfortunate but (so far) not serious.

You should explain that to my employer's support department.

In any case, I don't think this topic is directly relevant to the
SPFBIS discussion, so I'll not comment on it further.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@elandsys.com  Tue Aug 20 10:32:23 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AD721F898A; Tue, 20 Aug 2013 10:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ixsfsm85tAV; Tue, 20 Aug 2013 10:32:21 -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 D3E8F11E80E4; Tue, 20 Aug 2013 10:32:19 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.26]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7KHVw1U028951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Aug 2013 10:32:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377019935; bh=dxpdIwRik6URiwtaZvpZf517giZhDxMaF7N1utnK5uM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2gmaLJHoMVI3QHgYXvviZ2flzfH6nG3fOeXA0GJuQrC1l3rBA2gPyKTP0zqsnJIUN vB69+yUv5bNf42QV2LT5FYGs+qTg7uNdldU2hHdbVjRHMqDaI2azcVG3BVYbLb+qEE vskSX7FUpl2KTxDf+VwSw9Sdqx7QeLm8OSmmblhY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377019935; i=@elandsys.com; bh=dxpdIwRik6URiwtaZvpZf517giZhDxMaF7N1utnK5uM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=s57CIEuQY8t24I//DDOQr/z495YWkZh/ZVItTQrxsdkkV6ptbBbjomi6mbWmFtHnh inyE3KZh1CTjA3yaUziYe+wVD0RlrdqA+EhdDb+6Lr0yOiKUjocxU6aSvo1+nQIIDl gnMJ1mD9nbrv6crQ7RqfaUxQh02FX10YrwY4pOng=
Message-Id: <6.2.5.6.2.20130820074828.0df2aac8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Aug 2013 10:02:57 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] SPF TYPE support
In-Reply-To: <52136F65.6020703@isdg.net>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <521289C3.9070500@isdg.net> <6.2.5.6.2.20130819151912.0b861e98@resistor.net> <52136F65.6020703@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@ietf.org, =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 17:32:23 -0000

Hi Hector,
At 06:30 20-08-2013, Hector Santos wrote:
>I have a few questions and points:
>
>May I ask why was the above was not an area for clarification as 
>oppose as the presumed stated technical reason for removal?

The SPFBIS WG had a session at IETF 83.  The minutes for that session 
is at 
http://www.ietf.org/proceedings/83/minutes/minutes-83-spfbis.txt 
Item C on the agenda is about "SPF RR Type and TXT RR (issue 
#9)".  Andrew Sullivan, as SPFBIS Chair, explained that:

   'The were people on the mailing list in favor of using the TXT RR
    appeared to be a modest majority and there were people who argued
    for SPF RR Type on the grounds of DNS hygiene.  The Chair explained
    that it appears as an empirical matter, overwhelmingly, the TXT RR
    is used but RRTYPE 99 does not qualify under the unused provision
    of the SPFBIS charter.'

Pete Resnick, as Area Director, commented that:

   'the deal with the IESG, as a general statement, the working can removed
    what is unused and put in what is widely deployed. He pointed out that
    saying that TXT RR is part of an experiment is contrary to the agreement
    made with the IESG.  His opinion is that either way, the proposal is stuck
    with TXT RR and that it is not an issue.  The only issue is whether the
    proposal can remove the SPF RRTYPE as unused.'

On February 26, 2012, Barry Leiba, as a participant, posted a message 
( http://www.ietf.org/mail-archive/web/spfbis/current/msg00654.html ) 
which I will quote:

   "These two statements make a pretty compelling case that there is, indeed,
    an error in RFC4408.  There are, of course, multiple ways to resolve it,
    and I have no immediate opinion on which is best."

My opinion, as one of the SPFBIS WG Chairs, was that there was an 
error.  As Barry Leiba mentioned, there were several possible ways to 
fix that.  The SPFBIS Chair stated at the meeting that:

   "The conclusion reached by the Chair was that the document will say
    SHOULD NOT publish RRTYPE 99 and MUST NOT query RRTYPE 99."

That statement was posted to the SPFBIS mailing list ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg01369.html 
).  Nobody disagreed.


>There was adequate information for the expected and original optimal 
>migration plan but it could of been further codified and clarified. 
>It would of been on par with BIS level of work.  Issue #9 should not 
>have been a reason for removal.  I reported issue #25 [1] regarding 
>the complexity of the recommended parallel processing approach.  I 
>believe most folks agreed the ideal and optimal migration approach was:
>
>     Query SPF type first,
>     Fallback to TXT secord.
>
>It was common sense, at least to me.

Both Issue #9 and Issue #25 (see SPFBIS tracker)  were 
well-discussed.  Was every technical point carefully considered?  I 
don't think so as it is possible that a technical point may have been 
missed.  There is an opportunity for anyone to comment during the 
Last Call if the person believes that a technical point has been 
missed or was not addressed appropriately by the working group.  In 
my opinion the SPFBIS WG carefully considered all the comments which 
were made in reaching its decision.

>Second, I was under the impression interop reports (RFC 6686) were 
>not making any conclusions or recommendations?  Is that a correct 
>basic understanding of interop reports?  They were observations, 
>collection of available data and while it might be eventually used 
>to rethink a protocol design, I don't think the above RFC 4408 
>statement is a serious "error" in the functional description to 
>justify removal. There are other parts of 4408 which helped clarify 
>the migration path.

 From the Introduction Section of RFC 6686:

   "In line with the IESG's request to evaluate after a period of time,
    this document concludes the experiments by presenting evidence
    regarding both deployment and comparative effect of the two
    protocols.  At the end, it presents conclusions based on the data
    collected."

In my opinion RFC 6686 does make conclusions (see Section 6 of RFC 
6686).  There is some background information about the RRTYPE issue 
in Appendix A.

>But overall, a correction (not removal) would of suffice. It would 
>of been on par for BIS-like corrections and protocol updates.

Andrew Sullivan, as SPFBIS WG Chair, mentioned that "We have to do 
_something_, though any action would introduce a backward 
incompatibility ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03595.html ).

>Third, I believe removal required a more deeper IETF discussion 
>about the initial presumed engineering expectation that DNS servers 
>(all top DNS servers, including and especially Microsoft DNS 
>servers) would eventually directly support a new registered SPF type 
>or at the very least support RFC 3597 (Handling of Unknown DNS 
>Resource Record (RR) Type) [2].

There were comments about RFC 3567 during the working group 
discussions (see 
http://www.ietf.org/mail-archive/web/spfbis/current/msg00545.html 
http://www.ietf.org/mail-archive/web/spfbis/current/msg00820.html ).

>If this is no longer the expectation, then it would make sense to 
>remove the SPF type but also be aware that in general, this will 
>also  nix (not help) any future idea for successfully adopting new RR types.
>It would be added statement that TXT based applications are 
>acceptable.  I think the DNS community continues to have a problem with this.

Noted.

>SM, Pete, thank you for the opportunity to clarify my point. For the 
>record, there was no intent to imply it occurred but quite frankly 
>when it is repeatedly stated, this deeply divided issue has not be 
>resolved at any point,  it does have an intimidation factor.  As Mr. 
>Crocker stated, the burden is on the those who oppose the removal. 
>But my question was always why was the decision made to remove in 
>the first place done when in fact it was quite obvious it would not 
>have industry wide endorsement. The burden should of been to justify 
>removal. Now it has become difficult to effectively add it back. 
>This is why I posed the question in two forums to get community 
>input over the last few years. It was quite obvious to me that the 
>DNS community would be against this removal.  So in this vain, it 
>was prematurely removed in the WG without early IETF/IESG/DNS 
>concerns adequately dealt with.  Unfortunately, we were advise to 
>raise the issue again in LC, but by that point, all the IETF 
>procedural moves were made making it it a very high burden to add 
>something that should not been removed in the first place.

There are two SPFBIS WG Chairs.  The way we work is: I read the 
mailing list messages, the other Chair reads the mailing list 
messages, each chair reaches his own conclusion and we discuss about 
it.  Once the Chairs agree a message is posted to the WG mailing 
list.  Let's assume that the Chairs did not carefully consider the 
comments or their determination was incorrect.  There is a Last Call 
where the matter can be raised again.  That is the advice that was 
given.  There is indeed a high burden as the person raising the issue 
again will have to read the mailing list messages to determine 
whether they have been carefully considered.

Regards,
S. Moonesamy (as document shepherd) 


From sm@elandsys.com  Tue Aug 20 10:32:24 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36C0711E80E4; Tue, 20 Aug 2013 10:32: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHMDZ2WfnNJb; Tue, 20 Aug 2013 10:32:23 -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 A0DC821F898A; Tue, 20 Aug 2013 10:32:23 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.26]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7KHVw1W028951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Aug 2013 10:32:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377019941; bh=fN+2exVJPVJjd6houtZMULSPqKVytijD2xJnY+LWCsw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kNDmrnGQ13NrlkJEGfEfQTaLs9qSzCgmHByBwQH6Pbfv7/Z7GKheh26eMwgujvSno xOru3DBPa6+gC6c7umwYFn93k3kJSD0XFlTrxz1TMwUncQ6itMPL95aJEjHjsVDqJD B412a/p7wNZpeROaOxfKVaFWZdeHVy0Yg63jKrBs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377019941; i=@elandsys.com; bh=fN+2exVJPVJjd6houtZMULSPqKVytijD2xJnY+LWCsw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=r4e+02j6UMRZIMSwDczD4C4++yDDpXPKpqxHTibMW8aWB1t5kZI9+bWNbxgaFR56B XD+vGoQCi11nWTYRJoVsJ9QZcRo7oTQ/JtT+QpP2Tu22V844hKnkbGW4ohNAj1EP8z E3KEMiTa/0BmZf3ihjbRhqnlLvC7ix/BKVwmZ2io=
Message-Id: <6.2.5.6.2.20130820100431.0df2aea0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Aug 2013 10:30:41 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <52137A3B.6040200@isdg.net>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <6.2.5.6.2.20130819202422.0d1756a8@resistor.net> <52137A3B.6040200@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: spfbis@ietf.org, mansaxel@besserwisser.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 17:32:24 -0000

Hi Hector,
At 07:16 20-08-2013, Hector Santos wrote:
>This doesn't seem to be correct. My apology if I don't follow or see 
>the logic.   The only real issue as it was since day zero in MARID 
>was the infrastructure support for recursive passthru queries which 
>is what RFC 3597 (Handling of Unknown DNS Resource Record (RR) 
>Type).  Without this, which allows for servers to delay/plan direct 
>new RR type support yet still not error out on an unnamed type, 
>there COULD NOT be any reasonable expectation to even only suggest a 
>dual query migration approach, either in serial or parallel. It is 
>very important to consider the mindset when it was first considered 
>and written for RFC 4408 because to me, that is the mindset that has changed.

This would be a process issue then as the SPFBIS Chairs determination 
was made on the basic of the text from the SPFBIS Charter which was 
cited.  A person can raise an objection (I am okay with that as 
that's part of the work) with substantive comments to support the objection.

>I hope I am reading this incorrectly.  It may be too procedural 
>oriented to me at this point.
>
>I would like to see a simple just distinctive consensus on what the 
>entire IETF/DNS community believes is the future of DNS servers 
>offering unnamed RR type processing because that is the main barrier 
>for any kind success. We knew this as far back as MARID.  I don't 
>quite understand why this key point seems to be left out, instead 
>MARID was deemed off topic. That was an error because if there is no 
>future in unnamed RR type support, then it really doesn't matter and 
>the problem is solved. TXT only will be the only fast entry point 
>for new DNS DOMAIN policy applications.
>
>If the community still believes it possible, then clarifying and 
>codifying the SPF/TYPE lookup procedure seems to me to be the only 
>real correction to make here.

My reading of  the SPFBIS Charter is that the working group was not 
tasked to work on the future of DNS servers.  That does not mean that 
arguments about the future of DNS servers are not relevant.

There are several questions:

  (a) Was there an error in RFC 4408?

  (b) What was the error in RFC 4408?

  (c) Why was there an error in RFC 4408?

  (d) What should be done about the error?

There isn't anything that can be done about question (c) except not 
to repeat the same mistake.

Is there disagreement on the answers to questions (a) and (b)?

Regards,
S. Moonesamy (as document shepherd) 


From sm@elandsys.com  Tue Aug 20 11:38:35 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23BCE11E80DF; Tue, 20 Aug 2013 11:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kM9-DDV9BJmi; Tue, 20 Aug 2013 11:38:33 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A8A7611E812F; Tue, 20 Aug 2013 11:38:32 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.26]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7KIc8uK028387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Aug 2013 11:38:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377023903; bh=Sv2/3w0QtBWCaWv4IqgxOwuIZ4KLQVhbKrq7HRrTKYc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sKPkKo/7vEBVo11hQFvp2jk6zefhXJdSw/SpggksQBV8kNo3to+QBnbs2KG7YuFRx WiXx37oXUifLyQN4JDFNcgbChalfFEeqNxR6Ohr72WGQDYhHKHagYouKJtLZ+yXrWS v4NjDUZbpHuiS6mQZgKiF/CJOh/aUmARyrjy9H1Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377023903; i=@elandsys.com; bh=Sv2/3w0QtBWCaWv4IqgxOwuIZ4KLQVhbKrq7HRrTKYc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=d7Q124M7iq+YSbXrWeIJuEIyrEicR/XQNH8Nnh1IQRMepnKc7HlLW2gzHkKjtO1oW vHHJT7Kl1e9NeCExNSurtxzneb3glRcZLvXQrWa459GDcbIPkha7Dh9a4UwSnwJoey KRe6LQui6dhGp9ibfXdIRyXeNnFFOLM+oQKfI2AM=
Message-Id: <6.2.5.6.2.20130820110057.0bead1e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Aug 2013 11:36:55 -0700
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [dnsext] Deprecating SPF
In-Reply-To: <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se>
References: <E3DE33F3-B0A5-494B-9202-499E16ECCFB1@virtualized.org> <20130819222037.GA55876@mx1.yitter.info> <93130B0B-5C37-45EE-8380-AF209CA54B8F@frobbit.se> <521385AA.9080401@qti.qualcomm.com> <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dnsext@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 18:38:35 -0000

Hi Patrik,

I am copying the message to ieft@ as there is an ongoing Last Call.

At 08:28 20-08-2013, Patrik F=E4ltstr=F6m wrote:
>The consensus related to how to fix RFC 4408=20
>will be very rough. That is clear. And I feel=20
>sorry for responsible AD and IESG to be forced=20
>to make a decision that such a large rough part=20
>of the rough consensus will not be happy with.=20
>Regardless of what the decision will be.
>
>
>An architectural correct solution is to change:
>
>OLD:
>
>    An SPF-compliant domain name SHOULD have SPF records of both RR
>    types.  A compliant domain name MUST have a record of at least one
>    type.  If a domain has records of both types, they MUST have
>    identical content.
>
>NEW:
>
>    An SPF-compliant domain name SHOULD have SPF records of both RR
>    types.  A compliant domain name MUST have a record of at type SPF,
>    code 99.  Lookup MUST first be of type SPF and SHOULD if no response
>    is received be of type TXT.
>
>
>Reasoning: The use of the TXT record for SPF is=20
>not sounds for a number of reasons:
>
>1. The TXT record already can have multiple=20
>fields, and it is very unfortunate that the SPF=20
>use of TXT records do not use that feature.=20
>Instead the SPF specification do say that the=20
>first field should be used, and if there are=20
>more than one they should be concatenated. After=20
>one have one and only one field, that field=20
>should be parsed and divided in fields.
>
>2. It is even (compared to some other TXT=20
>related documents) pointed out in RFC 4408 that=20
>collisions as described in RFC 5507 might happen.
>
>3. It is also pointed out that there might be=20
>size issues with the records, and experience=20
>from use of NAPTR show that selecting a=20
>preferred mechanism that potentially blows the=20
>size of the RRSet is not very wise. This is btw=20
>why the URI RR Type do not use a prefixed length=20
>"text" field in the RDATA but do set the string=20
>the URI is to the full length of the RDATA, i.e.=20
>without any 255 byte limitation.
>
>4. DNS is by design (as pointed out in RFC 5507)=20
>created with a tuple consisting of owner, type=20
>and class for selection by the client what=20
>record set to be retrieved. This RRSet=20
>architecture is something that comes back not=20
>only in the query/response architecture of the=20
>DNS protocol, but also in the DNSSEC=20
>architecture where RRSets are the units that are=20
>signed. Not explicitly ensuring an RRSet is used=20
>for SPF (and nothing more) is an architectural choice I strongly am=
 against.
>
>
>Because of these reasons, I do believe the=20
>choice is wrong to say that TXT MUST be=20
>implemented and instead I am in favor of having=20
>type SPF be mandatory for interoperability with fallback to lookup of TXT.

 From Section 3.1 of draft-ietf-spfbis-4408bis-19:

   "SPF records MUST be published as a DNS TXT (type 16) Resource Record
    (RR) [RFC1035] only.  The character content of the record is encoded
    as [US-ASCII].  Use of alternative DNS RR types was supported in
    SPF's experimental phase, but has been discontinued."

There is a message from Pete Resnick about RFC=20
2119 usage (=20
http://www.ietf.org/mail-archive/web/spfbis/current/msg03642.html=20
).  The interpretation of "SHOULD" and MUST" in=20
that part of RFC 4408 was an issue which the SPFBIS WG discussed about.

It would be better to have the discussion on the=20
ietf@ mailing list as that's the venue which the=20
IESG identified for last Call comments.

Regards,
S. Moonesamy=20


From paf@frobbit.se  Tue Aug 20 11:45:27 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADBC211E8131; Tue, 20 Aug 2013 11:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[AWL=-0.100,  BAYES_00=-2.599, J_CHICKENPOX_22=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQd99d779BwU; Tue, 20 Aug 2013 11:45:26 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id AAACF11E812F; Tue, 20 Aug 2013 11:45:25 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::e0a8:d413:1cf1:c2f5] (unknown [IPv6:2a02:80:3ffc:0:e0a8:d413:1cf1:c2f5]) by mail.frobbit.se (Postfix) with ESMTPSA id 0702F21F96; Tue, 20 Aug 2013 20:45:24 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [dnsext] Deprecating SPF
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <6.2.5.6.2.20130820110057.0bead1e8@resistor.net>
Date: Tue, 20 Aug 2013 20:45:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFDAC92A-3990-4FCC-B955-7CA2154BA4B6@frobbit.se>
References: <E3DE33F3-B0A5-494B-9202-499E16ECCFB1@virtualized.org> <20130819222037.GA55876@mx1.yitter.info> <93130B0B-5C37-45EE-8380-AF209CA54B8F@frobbit.se> <521385AA.9080401@qti.qualcomm.com> <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se> <6.2.5.6.2.20130820110057.0bead1e8@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dnsext@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 18:45:27 -0000

On 20 aug 2013, at 20:36, S Moonesamy <sm+ietf@elandsys.com> wrote:

> It would be better to have the discussion on the ietf@ mailing list as =
that's the venue which the IESG identified for last Call comments.

Understood, and thanks.

The reason why I did not post there at first was that a) I did not feel =
I had followed the rules laid out for discussions [read all messages in =
the mailing list archives] and b) the discussion on the dnsext list was =
more general on overload of TXT records [something DNS people have =
always been against -- see IAB document on DNS choices].

But, when having that discussion on the dnsext mailing list, to which I =
cc:ed Pete as responsible AD for full disclosure, Pete did ask me for a =
complete explanation of my view, which I posted.

Once again, without re-reading the mailing list archives.

   Patrik


From adrian@olddog.co.uk  Tue Aug 20 11:50:54 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BC511E8131; Tue, 20 Aug 2013 11:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.029,  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 RgBjOmlJ3I53; Tue, 20 Aug 2013 11:50:49 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id E6DD711E8144; Tue, 20 Aug 2013 11:50:48 -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 r7KIolaf027502;  Tue, 20 Aug 2013 19:50:47 +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 r7KIokYD027494 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 20 Aug 2013 19:50:47 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt> (Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for the evolving G.709 Optical Transport Networks Control) to Proposed Standard
Date: Tue, 20 Aug 2013 19:50:44 +0100
Message-ID: <00fe01ce9dd6$2dc59a10$8950ce30$@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: Ac6d1f8U/0fVrXNNRjCEO33cHnCIig==
Content-Language: en-gb
Cc: ccamp@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, 20 Aug 2013 18:50:54 -0000

As sponsoring AD I have the following last call comments I hope you will take on
board.

Thanks,
Adrian

Please fix the two lines that are too long (see idnits)

---

Please expand "OTN" on first use in the main text.
Please expand "TS" on its first use.

---

6.2

   The ingress node of an LSP MAY include Label ERO (Explicit Route 
   Object) to indicate the label in each hops along the path.

Missing "subobject".

---

6.2.1

   When an upstream node receives a Resv message containing an 
   GENERALIZED_LABEL object

s/an/a/

---

Please consider and note what updates to GMPLS management tools are
needed.

Are there any changes to the Alarms that might arise? We have a document
for that.

Are there any changes to the way OAM is controlled? We have a document
for that.

Should the new G-PIDs show in the TC MIB managed by IANA at
https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml
This should happen automgically when the feeding registries are updated
but it is probably best to add a specific request for IANA.

Will other MIB work be needed (in the future) to make it possible to 
read new information (labels, tspecs) from network devices?

---

Please fix so that you have three sections:

Authors' Addresses (only those people on the front page)
Contributors (other people who made significant text contributions to
the document)
Acknowledgements (other people who helped with the work)

---

[OTN-OSPF] should be a normative reference for its use to define the 
value of the switching type used in signaling.


From paf@frobbit.se  Tue Aug 20 11:59:35 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9B7E21F91F2; Tue, 20 Aug 2013 11:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.075
X-Spam-Level: 
X-Spam-Status: No, score=-2.075 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7H1RijMU8LNx; Tue, 20 Aug 2013 11:59:34 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 9D7A911E8274; Tue, 20 Aug 2013 11:58:16 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::e0a8:d413:1cf1:c2f5] (unknown [IPv6:2a02:80:3ffc:0:e0a8:d413:1cf1:c2f5]) by mail.frobbit.se (Postfix) with ESMTPSA id A2EAA23F2B; Tue, 20 Aug 2013 20:58:10 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Last call of draft-ietf-spfbis-4408bis-19
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <6.2.5.6.2.20130820110057.0bead1e8@resistor.net>
Date: Tue, 20 Aug 2013 20:58:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DEE47E1-885D-4F12-A766-D9BB2284BA09@frobbit.se>
References: <E3DE33F3-B0A5-494B-9202-499E16ECCFB1@virtualized.org> <20130819222037.GA55876@mx1.yitter.info> <93130B0B-5C37-45EE-8380-AF209CA54B8F@frobbit.se> <521385AA.9080401@qti.qualcomm.com> <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se> <6.2.5.6.2.20130820110057.0bead1e8@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dnsext@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 18:59:35 -0000

As the bottle is opened, I hereby state my objection to Section 3.1 of =
draft-ietf-spfbis-4408bis-19 for the reasons explained below. I do agree =
(as stated below) that the section of RFC 4408 that specify how to use =
both SPF and TXT resource record types include an error as it does not =
lead to interoperability.

As the intention with use of both TXT and SPF originally was to migrate =
from TXT to SPF I instead of what is outlined in the draft suggest that =
a proper migration strategy is laid out (look up mandatory to implement =
SPF and fall back to TXT). This instead of deprecation of the SPF =
record.

In general I do believe, for example when looking at IPv6 and DNSSEC and =
similar technologies, that the lifetime of RFC 4408 is too short to =
deprecate any of the proposed records that are in use, specifically as =
RFC 4408 explicitly do allow use of both.

   Patrik

On 20 aug 2013, at 20:36, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Patrik,
>=20
> I am copying the message to ieft@ as there is an ongoing Last Call.
>=20
> At 08:28 20-08-2013, Patrik F=E4ltstr=F6m wrote:
>> The consensus related to how to fix RFC 4408 will be very rough. That =
is clear. And I feel sorry for responsible AD and IESG to be forced to =
make a decision that such a large rough part of the rough consensus will =
not be happy with. Regardless of what the decision will be.
>>=20
>>=20
>> An architectural correct solution is to change:
>>=20
>> OLD:
>>=20
>>   An SPF-compliant domain name SHOULD have SPF records of both RR
>>   types.  A compliant domain name MUST have a record of at least one
>>   type.  If a domain has records of both types, they MUST have
>>   identical content.
>>=20
>> NEW:
>>=20
>>   An SPF-compliant domain name SHOULD have SPF records of both RR
>>   types.  A compliant domain name MUST have a record of at type SPF,
>>   code 99.  Lookup MUST first be of type SPF and SHOULD if no =
response
>>   is received be of type TXT.
>>=20
>>=20
>> Reasoning: The use of the TXT record for SPF is not sounds for a =
number of reasons:
>>=20
>> 1. The TXT record already can have multiple fields, and it is very =
unfortunate that the SPF use of TXT records do not use that feature. =
Instead the SPF specification do say that the first field should be =
used, and if there are more than one they should be concatenated. After =
one have one and only one field, that field should be parsed and divided =
in fields.
>>=20
>> 2. It is even (compared to some other TXT related documents) pointed =
out in RFC 4408 that collisions as described in RFC 5507 might happen.
>>=20
>> 3. It is also pointed out that there might be size issues with the =
records, and experience from use of NAPTR show that selecting a =
preferred mechanism that potentially blows the size of the RRSet is not =
very wise. This is btw why the URI RR Type do not use a prefixed length =
"text" field in the RDATA but do set the string the URI is to the full =
length of the RDATA, i.e. without any 255 byte limitation.
>>=20
>> 4. DNS is by design (as pointed out in RFC 5507) created with a tuple =
consisting of owner, type and class for selection by the client what =
record set to be retrieved. This RRSet architecture is something that =
comes back not only in the query/response architecture of the DNS =
protocol, but also in the DNSSEC architecture where RRSets are the units =
that are signed. Not explicitly ensuring an RRSet is used for SPF (and =
nothing more) is an architectural choice I strongly am against.
>>=20
>>=20
>> Because of these reasons, I do believe the choice is wrong to say =
that TXT MUST be implemented and instead I am in favor of having type =
SPF be mandatory for interoperability with fallback to lookup of TXT.
>=20
> =46rom Section 3.1 of draft-ietf-spfbis-4408bis-19:
>=20
>  "SPF records MUST be published as a DNS TXT (type 16) Resource Record
>   (RR) [RFC1035] only.  The character content of the record is encoded
>   as [US-ASCII].  Use of alternative DNS RR types was supported in
>   SPF's experimental phase, but has been discontinued."
>=20
> There is a message from Pete Resnick about RFC 2119 usage ( =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03642.html ).  =
The interpretation of "SHOULD" and MUST" in that part of RFC 4408 was an =
issue which the SPFBIS WG discussed about.
>=20
> It would be better to have the discussion on the ietf@ mailing list as =
that's the venue which the IESG identified for last Call comments.
>=20
> Regards,
> S. Moonesamy=20


From presnick@qti.qualcomm.com  Tue Aug 20 12:03:31 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807C111E82B9 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 12:03:31 -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 hpG3-rGqGVGM for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 12:03:27 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 3784621F830F for <ietf@ietf.org>; Tue, 20 Aug 2013 12:01:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377025311; x=1408561311; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=2nVzwqx2miKm9F8fRz6HJJGkAA3/tDiBHPQzCeUJOMg=; b=S41gi7Kdc7erixvvuYNsGZ60RJrurA8gUDX/1INeOialgsLX+afFXs9H PZNw2BzQd0+3evksK/r8vDWvSvIflmDMdPZrC8/SyOzNn/bhsQunLBpSJ RosAtW+Pu6IJ4FuYArjjCh+0EWFy+P2BQoaEy0DscawRmdv1ira4IEOBw w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="49854899"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 20 Aug 2013 12:01:44 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="18283182"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 20 Aug 2013 12:01:43 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 20 Aug 2013 12:01:43 -0700
Message-ID: <5213BD15.2080500@qti.qualcomm.com>
Date: Tue, 20 Aug 2013 14:01:41 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of	Internet Official Protocol Standards: Replaced by an Online Database"
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
In-Reply-To: <6.2.5.6.2.20130815114542.0c4e8780@resistor.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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: Tue, 20 Aug 2013 19:03:32 -0000

On 8/15/13 2:06 PM, SM wrote:
> At 11:48 14-08-2013, IAB Chair wrote:
>> This is a call for review of "List of Internet Official Protocol 
>> Standards: Replaced by an Online Database" prior to potential 
>> approval as an IAB stream RFC.
>
> My guess is that draft-rfced-rfcxx00-retired cannot update RFC 2026.  
> Does the IAB have any objection if I do something about that?
> [...]
> The document argues that STD 1 is historic as there is an online list now.

The IESG and the IAB had an email exchange about these two points. 
Moving a document from Standard to Historic is really an IETF thing to 
do. And it would be quite simple for the IETF to say, "We are no longer 
asking for the 'Official Protocol Standards' RFC to be maintained" by 
updating (well, effectively removing) the one paragraph in 2026 that 
asks for it, and requesting the move from Standard to Historic. So I 
prepared a *very* short document to do that:

http://datatracker.ietf.org/doc/draft-resnick-retire-std1/

I'm asking Jari to Last Call it along with a status change for STD 1 
(RFC 5000) to Historic. If the RFC Editor wants to explain more of the 
history and whatever else they're going to do in a separate document, 
that's up to the IAB. But declaring Standards to be Historic is 
something the RFC Editor or IAB shouldn't be doing. The above document 
solves the problem by making it clear that the IETF isn't interested in 
the document being updated anymore.

pr

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


From sm@elandsys.com  Tue Aug 20 12:33:00 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 378C621F92E7; Tue, 20 Aug 2013 12:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.142
X-Spam-Level: 
X-Spam-Status: No, score=-102.142 tagged_above=-999 required=5 tests=[AWL=-0.443, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 aT62nsdWx0gR; Tue, 20 Aug 2013 12:32: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 6DA7311E80DF; Tue, 20 Aug 2013 12:32:57 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.26]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7KJWPLl023456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Aug 2013 12:32:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377027158; bh=eTv+GC/SA2M/uQuSIfnNNxetTJA2eM+eb1Il4e8xd44=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MKdBzAOrR94b/+AJ7eplb0SMhe1XVisCfKgxgh9GuhOGxo8kgbnNMCQJ6jonLUIWr iUjVXzjpkjACrpgPNopGiBIC+kL1VBqXyh56ioH5dE9WWW/KWk3jhWGGwfnjRprdw4 2ziQfcv/B9vhVb6nCtJnfQ088ckcE+okfWr3SH8I=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377027158; i=@elandsys.com; bh=eTv+GC/SA2M/uQuSIfnNNxetTJA2eM+eb1Il4e8xd44=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HpeEJdWeskaSqH4BAEXtanKg6ZriVnaaBUAtIwEjXzirweNrvsdKjtcvPY2l4CIm0 vdg4BgfSsGE+GCtat2jrwNsMPd+LaxDfaGIKVohr7DZWJxIO6krOFQJg5528yf8e9Z ShTpJYbAeBX+4X8I0ALTC7CgTNjPEbZU8SfUHXrU=
Message-Id: <6.2.5.6.2.20130820115012.0de38728@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Aug 2013 12:30:48 -0700
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [dnsext] Deprecating SPF
In-Reply-To: <AFDAC92A-3990-4FCC-B955-7CA2154BA4B6@frobbit.se>
References: <E3DE33F3-B0A5-494B-9202-499E16ECCFB1@virtualized.org> <20130819222037.GA55876@mx1.yitter.info> <93130B0B-5C37-45EE-8380-AF209CA54B8F@frobbit.se> <521385AA.9080401@qti.qualcomm.com> <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se> <6.2.5.6.2.20130820110057.0bead1e8@resistor.net> <AFDAC92A-3990-4FCC-B955-7CA2154BA4B6@frobbit.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dnsext@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 19:33:00 -0000

Hi Patrik,
At 11:45 20-08-2013, Patrik F=E4ltstr=F6m wrote:
>The reason why I did not post there at first was=20
>that a) I did not feel I had followed the rules=20
>laid out for discussions [read all messages in=20
>the mailing list archives] and b) the discussion=20
>on the dnsext list was more general on overload=20
>of TXT records [something DNS people have always=20
>been against -- see IAB document on DNS choices].
>
>But, when having that discussion on the dnsext=20
>mailing list, to which I cc:ed Pete as=20
>responsible AD for full disclosure, Pete did ask=20
>me for a complete explanation of my view, which I posted.
>
>Once again, without re-reading the mailing list archives.

First of all, I apologize for copying the message=20
to ietf@.  The advice given was to read the=20
comments in the SPFBIS mailing list archives.  It=20
is not a rule.  If a person did not read all the=20
messages and the person raises a point or=20
provides arguments which were not discussed=20
previously I will ask the SPFBIS WG to address them.

I don't know whether to process your comments or=20
the other comments posted on dnsext@ as part of=20
the Last Call or not.  It is unclear to me as to=20
whether I should only consider messages with the=20
appropriate Last Call subject line.  My sense is=20
that I should listen to your concerns.

Regards,
S. Moonesamy=20


From paf@frobbit.se  Tue Aug 20 12:37:21 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C9F11E8226; Tue, 20 Aug 2013 12:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.15
X-Spam-Level: 
X-Spam-Status: No, score=-2.15 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HNDiqq8NUt3W; Tue, 20 Aug 2013 12:37:21 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 360EA11E8171; Tue, 20 Aug 2013 12:37:21 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::e0a8:d413:1cf1:c2f5] (unknown [IPv6:2a02:80:3ffc:0:e0a8:d413:1cf1:c2f5]) by mail.frobbit.se (Postfix) with ESMTPSA id 8E66524015; Tue, 20 Aug 2013 21:37:20 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [dnsext] Deprecating SPF
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <6.2.5.6.2.20130820115012.0de38728@resistor.net>
Date: Tue, 20 Aug 2013 21:37:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <67725DA7-EB62-494C-BB79-0692C32057A6@frobbit.se>
References: <E3DE33F3-B0A5-494B-9202-499E16ECCFB1@virtualized.org> <20130819222037.GA55876@mx1.yitter.info> <93130B0B-5C37-45EE-8380-AF209CA54B8F@frobbit.se> <521385AA.9080401@qti.qualcomm.com> <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se> <6.2.5.6.2.20130820110057.0bead1e8@resistor.net> <AFDAC92A-3990-4FCC-B955-7CA2154BA4B6@frobbit.se> <6.2.5.6.2.20130820115012.0de38728@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dnsext@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 19:37:21 -0000

On 20 aug 2013, at 21:30, S Moonesamy <sm+ietf@elandsys.com> wrote:

> First of all, I apologize for copying the message to ietf@.

No apology needed.

> I don't know whether to process your comments or the other comments =
posted on dnsext@ as part of the Last Call or not.  It is unclear to me =
as to whether I should only consider messages with the appropriate Last =
Call subject line.  My sense is that I should listen to your concerns.

I was the one making mistakes.

Mea culpa.

   Patrik


From hallam@gmail.com  Tue Aug 20 13:27:06 2013
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 4713011E8281 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 13:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.463
X-Spam-Level: 
X-Spam-Status: No, score=-2.463 tagged_above=-999 required=5 tests=[AWL=0.136,  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 GuNxXKJtybkr for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 13:27:02 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 72B3111E8160 for <ietf@ietf.org>; Tue, 20 Aug 2013 13:26:59 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hr7so4816519wib.10 for <ietf@ietf.org>; Tue, 20 Aug 2013 13:26:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Lnuw7ZCancDbvGKE5vnH7deYktGSwrsNdj3gHsJSjeY=; b=e9oY3hfCwLxlqjTfMiBHHDw4MgPoi7foGfcvTw/CE+J2pweOQQ+pPAPuOP0KVC6NlZ G43C7IR6a4VxsT9IMEGBkAbvO6Me2gk71f8Ix1O2FlraCIsTVx+drAcn7oiX2LBnr3yi d4BH6duWDHPLQHZj95udxu2HVtPh4Qzw0w/yY8hoTHLf55/RV9i0mjbCO3JkXC+/lBV5 icP5DBOeST685vlS1WvM75G2/BQYLVXOTyGIsP8FsO2iKNF3brVCpxg2oy7jTlc5tInp bLmgLbg8PAEq+j9t1wBBsTVAPEzEfW8JbvW+utwU4bCywhCYR/WdvUu4pJaPd9Jbb+EM CskQ==
MIME-Version: 1.0
X-Received: by 10.180.72.104 with SMTP id c8mr13711131wiv.63.1377030418396; Tue, 20 Aug 2013 13:26:58 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Tue, 20 Aug 2013 13:26:58 -0700 (PDT)
In-Reply-To: <520E7ADD.9060509@gmail.com>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <6E29F0AB625F4250CB35B273@192.168.1.128> <520E7ADD.9060509@gmail.com>
Date: Tue, 20 Aug 2013 16:26:58 -0400
Message-ID: <CAMm+Lwi7z0S6HR5R8NpZ_J6WNACmPjP2ZxM+GD4Gx0UK4qgNTQ@mail.gmail.com>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2b5b2ef008904e466e059
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, IAB IAB <iab@iab.org>, 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: Tue, 20 Aug 2013 20:27:06 -0000

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

I am having trouble understanding this discussion.

If the data is in a database then surely the production of RFC xx00
standards series is simply running an automated query on the database and
emitting the result as an RFC?

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

<div dir=3D"ltr">I am having trouble understanding this discussion.<div><br=
></div><div>If the data is in a database then surely the production of RFC =
xx00 standards series is simply running an automated query on the database =
and emitting the result as an RFC?</div>
<div><br></div><div><br></div></div>

--001a11c2b5b2ef008904e466e059--

From john-ietf@jck.com  Tue Aug 20 13:29:09 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD14511E824E; Tue, 20 Aug 2013 13:29:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rfFk1VSrzx2; Tue, 20 Aug 2013 13:29:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E4F4E11E8160; Tue, 20 Aug 2013 13:29: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 1VBsY4-000HxI-7o; Tue, 20 Aug 2013 16:29:04 -0400
Date: Tue, 20 Aug 2013 16:28:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of	Internet	Official Protocol Standards: Replaced by an Online Database"
Message-ID: <DE14182479BE643C9E769628@JcK-HP8200.jck.com>
In-Reply-To: <5213BD15.2080500@qti.qualcomm.com>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <5213BD15.2080500@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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: Tue, 20 Aug 2013 20:29:10 -0000

--On Tuesday, August 20, 2013 14:01 -0500 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> On 8/15/13 2:06 PM, SM wrote:
>> At 11:48 14-08-2013, IAB Chair wrote:
>>> This is a call for review of "List of Internet Official
>>> Protocol  Standards: Replaced by an Online Database" prior
>>> to potential  approval as an IAB stream RFC.
>> 
>> My guess is that draft-rfced-rfcxx00-retired cannot update
>> RFC 2026.   Does the IAB have any objection if I do something
>> about that? [...]
>> The document argues that STD 1 is historic as there is an
>> online list now.
> 
> The IESG and the IAB had an email exchange about these two
> points. Moving a document from Standard to Historic is really
> an IETF thing to do. And it would be quite simple for the IETF
> to say, "We are no longer asking for the 'Official Protocol
> Standards' RFC to be maintained" by updating (well,
> effectively removing) the one paragraph in 2026 that asks for
> it, and requesting the move from Standard to Historic. So I
> prepared a *very* short document to do that:
> 
> http://datatracker.ietf.org/doc/draft-resnick-retire-std1/

FWIW, I've reviewed your draft and have three comments:

(1) You are to be complemented on its length and complexity.

(2)  I agree that the core issue belongs to the IETF, and IETF
Stream, issue, not the RFC Editor and/or IAB.

(3) I far prefer this approach to the more complex and
convoluted RFC Editor draft.   If we really need to do something
formally here (about which I still have some small doubts), then
let's make it short, focused, and to the point.  Your draft
appears to accomplish those goals admirably.

   john


From sm@resistor.net  Tue Aug 20 13:52:36 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E72B11E82BC; Tue, 20 Aug 2013 13:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level: 
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.102, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itupb40AjhM8; Tue, 20 Aug 2013 13:52:35 -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 A306D11E8286; Tue, 20 Aug 2013 13:52:34 -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 r7KKqS9O005996; Tue, 20 Aug 2013 13:52:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377031954; bh=czckfCmSSfOapliSdZqUyXZcxA0pnOIYv0/QYJFJKbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2/0iRt6QU8bhmIzpyZbGzP4LyQPAwmrTRpS1d/f1ddaBSnBYrSWKmxRaJZmUOmKu/ GcloCacLao4c0LdetulX28IQaPR/loFe+k1Mx+uTAuOcxxv5jeqax7+QmkbW3L62aW KvbkKv051GT6p3FUI2BcExUyQ0V0PStcFN0tIKcQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377031954; i=@resistor.net; bh=czckfCmSSfOapliSdZqUyXZcxA0pnOIYv0/QYJFJKbM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Mb/fgQA6pnEW1vaTTnM7F0C1KqDqO28ppmuEGd+yHUD2Qtke5QLY6gYfRgt6zI/Tu JA9Z8kvm/JIimTJesUeAX/Y8ut+UyCm8u3ffoK1Hedtv5VjPFFlZKQFR3yJVfMIxWP W9UJiiKmEwka3Hum0/4U6XrjgCLZ7LR5N7uDWjUU=
Message-Id: <6.2.5.6.2.20130820134308.0b8a6b38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 20 Aug 2013 13:51:05 -0700
To: Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of	Internet Official Protocol Standards: Replaced by an Online Database"
In-Reply-To: <5213BD15.2080500@qti.qualcomm.com>
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <5213BD15.2080500@qti.qualcomm.com>
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: Tue, 20 Aug 2013 20:52:36 -0000

Hi Pete,
At 12:01 20-08-2013, Pete Resnick wrote:
>The IESG and the IAB had an email exchange about these two points. 
>Moving a document from Standard to Historic is really an IETF thing 
>to do. And it would be quite simple for the IETF to say, "We are no 
>longer asking for the 'Official Protocol Standards' RFC to be 
>maintained" by updating (well, effectively removing) the one 
>paragraph in 2026 that asks for it, and requesting the move from 
>Standard to Historic. So I prepared a *very* short document to do that:
>
>http://datatracker.ietf.org/doc/draft-resnick-retire-std1/

I read the draft.  I agree with what is written above.

>I'm asking Jari to Last Call it along with a status change for STD 1 
>(RFC 5000) to Historic. If the RFC Editor wants to explain more of 
>the history and whatever else they're going to do in a separate 
>document, that's up to the IAB. But declaring Standards to be 
>Historic is something the RFC Editor or IAB shouldn't be doing. The 
>above document solves the problem by making it clear that the IETF 
>isn't interested in the document being updated anymore.

I support moving the draft to Last Call as it solves the problem.

Regards,
-sm 


From presnick@qti.qualcomm.com  Tue Aug 20 14:16:09 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684BB11E82CE for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.455
X-Spam-Level: 
X-Spam-Status: No, score=-106.455 tagged_above=-999 required=5 tests=[AWL=0.144, 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 y24Xf0CuB40a for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:16:04 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id CF97A11E82CF for <ietf@ietf.org>; Tue, 20 Aug 2013 14:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377033359; x=1408569359; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=BtPr+6rgKHSOJF6YXglW5vQbYIdEh/9H+0vVcbHkB/8=; b=lnpNxgi6R7stSf6cfvsvmzknA0eGEUxxbgGhD5o66JECoKipRdjc3l/9 6AKcaQVUX66M/TG+3iLIlqJcXBdohNRmqpkNQ8hFWgwqvPS+Q7LGjxu9N tyw9UkJ+pTWKRE82qPJ3YUh7LbzpOBffSK03bgWDY3sN7+uHOpCF0mJPc M=;
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="69512500"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 20 Aug 2013 14:15:58 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="524123889"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 20 Aug 2013 14:15:57 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 20 Aug 2013 14:15:57 -0700
Message-ID: <5213DC8A.3020703@qti.qualcomm.com>
Date: Tue, 20 Aug 2013 16:15:54 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org>	<6.2.5.6.2.20130815114542.0c4e8780@resistor.net>	<6E29F0AB625F4250CB35B273@192.168.1.128>	<520E7ADD.9060509@gmail.com> <CAMm+Lwi7z0S6HR5R8NpZ_J6WNACmPjP2ZxM+GD4Gx0UK4qgNTQ@mail.gmail.com>
In-Reply-To: <CAMm+Lwi7z0S6HR5R8NpZ_J6WNACmPjP2ZxM+GD4Gx0UK4qgNTQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, IAB IAB <iab@iab.org>, 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: Tue, 20 Aug 2013 21:16:09 -0000

On 8/20/13 3:26 PM, Phillip Hallam-Baker wrote:
> If the data is in a database then surely the production of RFC xx00 
> standards series is simply running an automated query on the database 
> and emitting the result as an RFC?

I'm sure that such a tool could be created. To date, I believe the 
document was being built by hand.

However, the document hasn't been produced in over 5 years and nobody 
seems to miss it. The RFC Editor has indicated that they're not 
enthusiastic about keeping the document up to date given that there's a 
web page with that information that is getting good use. So the thinking 
behind the document I submitted was, "Let the RFC Editor off the hook. 
We, the IETF, don't need the RFC published separately anymore, so we 
should just say that."

I suppose if there's a real resurgence of sentiment that the RFC Editor 
should keep producing that document, we can tell the IAB that the IETF 
still really wants that document produced and send them off to write a 
tool that queries their database and auto-creates the RFC. In the 
absence of such sentiment, I think we should just use the web-based 
database and clean up the STD series as stated.

pr

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


From hallam@gmail.com  Tue Aug 20 14:17:06 2013
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 CC45211E82A4 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level: 
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123,  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 uGt8Wkp36q6w for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:17:06 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 6D29811E82CD for <ietf@ietf.org>; Tue, 20 Aug 2013 14:17:02 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id y10so861634wgg.16 for <ietf@ietf.org>; Tue, 20 Aug 2013 14:16:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Aa4AscfMqWgXqqm7bmxojJEZ9yA6apqhu4KQOLGYzYs=; b=G2Nks3XH1ifW1TVflHy79NOOAaltAoeVwlKly8+5zSB7RUNRMsacKXEYSYGyt9da7x NeV3WURAwQPSvFG8mn6snZ1pYH3LMpf16QbHknz2x2WonUrL+CNRdpC7uRZgpH1pma+J BPKFEgcrS+2TTcor7uHwbJ6tvDrL5B10I1j8gsG6fOqSI2NgCnr9xCSwsuarMbvZuoLe 7S8VG0uvyGBR/w7SJMWj1+HLBHnHQhPstxik2pH5qNxrjS1gQUVtJPv/kJhYem6ySZJW zAVEMXuPRqH4WJw0jhFjJDIRDGzw2cJ9SjgG1r4Y2bjUgXtreWUbKRMoFq6lRtFXb9Sf Q/ag==
MIME-Version: 1.0
X-Received: by 10.180.72.47 with SMTP id a15mr2743601wiv.63.1377033418099; Tue, 20 Aug 2013 14:16:58 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Tue, 20 Aug 2013 14:16:56 -0700 (PDT)
In-Reply-To: <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>
Date: Tue, 20 Aug 2013 17:16:56 -0400
Message-ID: <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary=001a11c2567cbad34804e4679322
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: Tue, 20 Aug 2013 21:17:07 -0000

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

>From a pure protocol point of view the SPF record does have one major
advantage over TXT and that is in the use of wildcard records.

In short a wildcard on a TXT record for SPF is going to have impact on
every other scheme that overloads TXT, of which there are many. SPF does
have a mechanism to resolve the ambiguity but that does not stop the record
sets from getting to be larger than will fit in DNS UDP responses.

This has not been much of a problem because most of the other TXT overloads
don't have a use for a wildcard. There is not much point in a wildcard DANE
record. But it could be an issue.


So keeping SPF records does actually have a utility since it allows
wildcarded records to be isolated from other protocols and avoiding the
wildcard record set bloat issue.


The criteria to use to decide is not the proportion of SPF records
published as TXT vs SPF but what the validators look for. If at this point
there is little to no takeup by the validators for the SPF RR then it is
time to call time on a failed experiment. If there was a significant
support base for SPF RR validation then it is a harder call.

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

<div dir=3D"ltr">From a pure protocol point of view the SPF record does hav=
e one major advantage over TXT and that is in the use of wildcard records.=
=A0<div><br></div><div>In short a wildcard on a TXT record for SPF is going=
 to have impact on every other scheme that overloads TXT, of which there ar=
e many. SPF does have a mechanism to resolve the ambiguity but that does no=
t stop the record sets from getting to be larger than will fit in DNS UDP r=
esponses.</div>
<div><br></div><div>This has not been much of a problem because most of the=
 other TXT overloads don&#39;t have a use for a wildcard. There is not much=
 point in a wildcard DANE record. But it could be an issue.</div><div><br>
</div><div><br></div><div>So keeping SPF records does actually have a utili=
ty since it allows wildcarded records to be isolated from other protocols a=
nd avoiding the wildcard record set bloat issue.</div><div><br></div><div>
<br></div><div>The criteria to use to decide is not the proportion of SPF r=
ecords published as TXT vs SPF but what the validators look for. If at this=
 point there is little to no takeup by the validators for the SPF RR then i=
t is time to call time on a failed experiment. If there was a significant s=
upport base for SPF RR validation then it is a harder call.=A0</div>
<div><br></div><div><br></div><div><br></div></div>

--001a11c2567cbad34804e4679322--

From tony@att.com  Tue Aug 20 14:22:29 2013
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 B59AB11E82DF for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.953
X-Spam-Level: 
X-Spam-Status: No, score=-105.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6dkuaaMEnos for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:22:22 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC6A11E8145 for <ietf@ietf.org>; Tue, 20 Aug 2013 14:22:22 -0700 (PDT)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id e0ed3125.0.1292126.00-360.3612458.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>);  Tue, 20 Aug 2013 21:22:22 +0000 (UTC)
X-MXL-Hash: 5213de0e5c02fbe5-72d438792537a7e3d036a54dfcb076d7c4bd31be
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7KLMLm8024000 for <ietf@ietf.org>; Tue, 20 Aug 2013 17:22:21 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7KLM8Vh023899 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 20 Aug 2013 17:22:18 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor) for <ietf@ietf.org>; Tue, 20 Aug 2013 21:21:56 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7KLLu5n024032 for <ietf@ietf.org>; Tue, 20 Aug 2013 17:21:56 -0400
Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7KLLpuR023910 for <ietf@ietf.org>; Tue, 20 Aug 2013 17:21:52 -0400
Received: from [135.70.127.240] (vpn-135-70-127-240.vpn.swst.att.com[135.70.127.240]) by maillennium.att.com (mailgw1) with ESMTP id <20130820212149gw1004nh6ie> (Authid: tony); Tue, 20 Aug 2013 21:21:51 +0000
X-Originating-IP: [135.70.127.240]
Message-ID: <5213DDEB.3030708@att.com>
Date: Tue, 20 Aug 2013 17:21:47 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org> <6.2.5.6.2.20130815114542.0c4e8780@resistor.net> <5213BD15.2080500@qti.qualcomm.com>
In-Reply-To: <5213BD15.2080500@qti.qualcomm.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
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.229.23]
X-AnalysisOut: [v=2.0 cv=UdfmvtuN c=1 sm=0 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=8pgaCy3H6LMA:10 a=sCfsyOEanakA:10 a=FTLmomD6aqUA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=zQP7CpK]
X-AnalysisOut: [OAAAA:8 a=AQZ7Rv8wVL4A:10 a=48vgC7mUAAAA:8 a=Uw11rc--J2DWk]
X-AnalysisOut: [t9IXrsA:9 a=wPNLvfGTeEIA:10]
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: Tue, 20 Aug 2013 21:22:29 -0000

On 8/20/2013 3:01 PM, Pete Resnick wrote:
> On 8/15/13 2:06 PM, SM wrote:
>> At 11:48 14-08-2013, IAB Chair wrote:
>>> This is a call for review of "List of Internet Official Protocol
>>> Standards: Replaced by an Online Database" prior to potential
>>> approval as an IAB stream RFC.
>>
>> My guess is that draft-rfced-rfcxx00-retired cannot update RFC 2026. 
>> Does the IAB have any objection if I do something about that?
>> [...]
>> The document argues that STD 1 is historic as there is an online list
>> now.
>
> The IESG and the IAB had an email exchange about these two points.
> Moving a document from Standard to Historic is really an IETF thing to
> do. And it would be quite simple for the IETF to say, "We are no
> longer asking for the 'Official Protocol Standards' RFC to be
> maintained" by updating (well, effectively removing) the one paragraph
> in 2026 that asks for it, and requesting the move from Standard to
> Historic. So I prepared a *very* short document to do that:
>
> http://datatracker.ietf.org/doc/draft-resnick-retire-std1/
>
> I'm asking Jari to Last Call it along with a status change for STD 1
> (RFC 5000) to Historic. If the RFC Editor wants to explain more of the
> history and whatever else they're going to do in a separate document,
> that's up to the IAB. But declaring Standards to be Historic is
> something the RFC Editor or IAB shouldn't be doing. The above document
> solves the problem by making it clear that the IETF isn't interested
> in the document being updated anymore.
>
> pr
>

I support this. But it also raises a couple other questions.

What about rfcxx99 series, published along with the rfcxx00 series? Were
they ever formally retired?

After rfcxx00 is retired, can the RFC editor start using both xx99 and
xx00 as normal RFC numbers?

I'm not saying that Pete

    Tony Hansen

From presnick@qti.qualcomm.com  Tue Aug 20 14:42:01 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE24411E8151 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:42:00 -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 mGxJJV4OCZEP for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 14:41:56 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 199C921F9AA8 for <ietf@ietf.org>; Tue, 20 Aug 2013 14:41:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377034914; x=1408570914; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RUVV3ojnk+eRoxJJ5sh+Ks+FNs8ATXVWah4F/0pZ/PU=; b=Sd1i93l0bfGhT7RCK/RxntrsvhRweLQI9+fzhM6NbEbjjW4epHHY9O6f zsD2VyOukrXreJGbslZZKVxPM69OdV2n8HmOmehhsXsoHg9BNZf6gXave gdV+n+w+K897avMnN5hvMQ96u7RPmtzuvbQj91Ud44cNx6kdpkrh9PfWF E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="49865167"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 20 Aug 2013 14:41:53 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7173"; a="524138529"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 20 Aug 2013 14:41:53 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 20 Aug 2013 14:41:53 -0700
Message-ID: <5213E2A0.5040303@qti.qualcomm.com>
Date: Tue, 20 Aug 2013 16:41:52 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: Call for Review of draft-rfced-rfcxx00-retired, "List of Internet Official Protocol Standards: Replaced by an Online Database"
References: <9F1A328F-12F4-4299-9604-CAA5019005C3@iab.org>	<6.2.5.6.2.20130815114542.0c4e8780@resistor.net>	<5213BD15.2080500@qti.qualcomm.com> <5213DDEB.3030708@att.com>
In-Reply-To: <5213DDEB.3030708@att.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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: Tue, 20 Aug 2013 21:42:01 -0000

On 8/20/13 4:21 PM, Tony Hansen wrote:
> I support this. But it also raises a couple other questions.
>
> What about rfcxx99 series, published along with the rfcxx00 series? Were
> they ever formally retired?
>    

That's not an IETF matter. There's no STD on this. There's nothing 
(AFAICT) in a BCP about this. So nothing for the IETF to do.

> After rfcxx00 is retired, can the RFC editor start using both xx99 and
> xx00 as normal RFC numbers?
>    

Again, entirely up to the RFC Editor. The IETF never documented that 
particular numbers would be used for such purposes; that's entirely an 
RFC Editor convention (again, AFAICT).

pr

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


From jhw@apple.com  Tue Aug 20 16:58:34 2013
Return-Path: <jhw@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB55111E8141; Tue, 20 Aug 2013 16:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TKVmdglMowfd; Tue, 20 Aug 2013 16:58:27 -0700 (PDT)
Received: from mail-out.apple.com (honeycrisp.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 613A611E8134; Tue, 20 Aug 2013 16:58:27 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay6.apple.com ([17.128.113.90]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MRU0026XT9AVTQ0@mail-out.apple.com>; Tue, 20 Aug 2013 16:58:23 -0700 (PDT)
X-AuditID: 1180715a-b7f8e6d000006c98-a8-5214029ea4c9
Received: from aniseed.apple.com (aniseed.apple.com [17.128.115.23]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay6.apple.com (Apple SCV relay) with SMTP id 7F.A5.27800.F9204125; Tue, 20 Aug 2013 16:58:23 -0700 (PDT)
Received: from kallisti.apple.com ([17.193.13.64]) by aniseed.apple.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MRU007VPT9ACN00@aniseed.apple.com>; Tue, 20 Aug 2013 16:58:22 -0700 (PDT)
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
From: james woodyatt <jhw@apple.com>
In-reply-to: <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com>
Date: Tue, 20 Aug 2013 16:58:22 -0700
Message-id: <A4B538DE-16B9-45D4-89F3-51441984B12F@apple.com>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com> <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com>
To: v6ops@ietf.org, WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1793.4)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrNLMWRmVeSWpSXmKPExsUi2FAsrjufSSTI4Mh6NotnG+ezWJw+tpfZ gcljyZKfTAGMUVw2Kak5mWWpRfp2CVwZb5f8YixYz1Jx/0ArawPjDuYuRk4OCQETiV9HG1kg bDGJC/fWs3UxcnEICfQzSTx8PZEJwmllkmg++IIdpIpZQEei9/s3oG4ODl4BA4nPDT4gNcIC axklXuzZyQRSwyagIvHt8l0wm1MgWGLCgXesIDaLgKrEuY0z2SDmKEu8OfOfCcLWlnjy7gJY Da+AjcSltfPZIRa3M0rc7zoA1iAioC6x+spRRohT5SXafv9km8AoMAvJTbMQbpqFZOwCRuZV jAJFqTmJlWZ6iQUFOal6yfm5mxjBQVgYtYOxYbnVIUYBDkYlHl7OEuEgIdbEsuLK3EOMEhzM SiK8O74ChXhTEiurUovy44tKc1KLDzFKc7AoifPu1QBKCaQnlqRmp6YWpBbBZJk4OKUaGFPu CW8KFfHd2Liv6J7s3VBvnWJG4wmzX7Q8rL6hWnHrqWqLTt3+XYsvnor6sPKHwJ7byqu3XQvd xBHrsOlCk/j/VY+4o9TX9aTqrvOU+fqJYUKXqVTDpuvmQtP9fh5x/pT0JOtzrcfk01MmrGEW 3vIv30T2QcEh3sMqGdvyrNLETgZq7PRq0VBiKc5INNRiLipOBABmCbu0PgIAAA==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Aug 2013 23:58:34 -0000

On Aug 20, 2013, at 02:39 , Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> [...] It seems to me that the sheer length of the list, and the fact that is not prioritized, create a real risk that implementors will simply write it off as wishful thinking or even shy away in terror. [...]

My views on the technical merits of this draft remain unchanged from the last time I offered them here, and I am basically in agreement with Lorenzo.  This draft seems unnecessary to me.


--
james woodyatt <jhw@apple.com>
core os networking


From dhc@dcrocker.net  Tue Aug 20 19:14:36 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4331F0D4F for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 19:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Xldmgd7bSuS for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 19:14:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4F4F81F0D37 for <ietf@ietf.org>; Tue, 20 Aug 2013 19:14:31 -0700 (PDT)
Received: from [192.168.2.26] (adsl-99-183-241-57.dsl.pltn13.sbcglobal.net [99.183.241.57]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7L2ENWq006005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 20 Aug 2013 19:14:28 -0700
Message-ID: <52141C74.8000305@dcrocker.net>
Date: Tue, 20 Aug 2013 18:48:36 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <5212FCEF.80701@dcrocker.net> <55459829-933F-4157-893A-F90552D4441A@frobbit.se> <5213174D.7080504@dcrocker.net> <20130820144646.GE20618@mx1.yitter.info> <5213911A.6010301@dcrocker.net> <20130820160844.GE21439@mx1.yitter.info>
In-Reply-To: <20130820160844.GE21439@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 20 Aug 2013 19:14:29 -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, 21 Aug 2013 02:14:36 -0000

On 8/20/2013 9:08 AM, Andrew Sullivan wrote:
> On Tue, Aug 20, 2013 at 08:54:02AM -0700, Dave Crocker wrote:
>> In other words, the specific technical limitations being noted are
>> unfortunate but (so far) not serious.
>
> You should explain that to my employer's support department.
>
> In any case, I don't think this topic is directly relevant to the
> SPFBIS discussion, so I'll not comment on it further.



The construct has been standardized multiple times, going back at least 
13 years, is very widely deployed and very heavily used.  In other 
words, it is very fully incorporated into Internet infrastructure services.

In the face of that, any support group that spends its time complaining 
about the construct is ignoring pragmatics and is, instead, paying 
attention to other issues.

For a support group, that means the issue is not technology or 
operations, but rather organizational management.

I'd be glad to assist your employer in helping its support team to 
reassess its priorities.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ajs@anvilwalrusden.com  Tue Aug 20 21:00:12 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A2611E8388 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 21:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgj4uvWZNa1V for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 21:00:06 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 2921411E8384 for <ietf@ietf.org>; Tue, 20 Aug 2013 21:00:06 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id A0E8F8A031 for <ietf@ietf.org>; Wed, 21 Aug 2013 04:00:05 +0000 (UTC)
Date: Wed, 21 Aug 2013 00:00:04 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130821040003.GL607@mx1.yitter.info>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@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, 21 Aug 2013 04:00:12 -0000

No hat.

On Tue, Aug 20, 2013 at 05:16:56PM -0400, Phillip Hallam-Baker wrote:
> >From a pure protocol point of view the SPF record does have one major
> advantage over TXT and that is in the use of wildcard records.

This is an extremely interesting point, and I'm ashamed to admit I
hadn't really thought about it from quite this perspective.  I say
that even though the draft contains some text that attempts to deal
with wildcards and the WG discussed the issue from a slightly
different perspective.  I think it is worth considering.  Note,
however, that â€¦

> This has not been much of a problem because most of the other TXT overloads
> don't have a use for a wildcard. There is not much point in a wildcard DANE
> record. But it could be an issue.

â€¦it wouldn't be an issue for most of the cases where TXT is
overloaded, because (partly due to the mess that SPF caused) most of
the TXT overloads we see are now scoped using underscore labels, where
the wildcard at a superordinate place in the FQDN isn't going to
matter.  Phill's is still a valuable observation, and one I think the
WG actually didn't consider in every dimension.
 
> The criteria to use to decide is not the proportion of SPF records
> published as TXT vs SPF but what the validators look for. 

The WG had a hard time coming up with really good data about what
validators look for, but to the extent we were able to draw
conclusions about that the evidence was that virtually nobody is
looking for SPF records.  This is mentioned at the end of section 3.1
of RFC 6686.  If someone else with some busy nameservers wants to
provide different evidence now, it wouldn't hurt.  We were unable to
find anyone among the participating validators in the SPFBIS WG who
was willing to argue in public that they felt the SPF lookup was more
valuable to them, but we did have some large participants who said
they did _not_ do the TYPE99 lookup except under unusual circumstances
(the draft author, who is also the maintainer of an important SPF
library, has already made this point elsewhere in this thread).

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From aallen@blackberry.com  Tue Aug 20 22:52:42 2013
Return-Path: <aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4BD11E81A1 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 22:52:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 OfZmpwA-n1Pc for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 22:52:37 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id DD06911E819A for <ietf@ietf.org>; Tue, 20 Aug 2013 22:52:36 -0700 (PDT)
X-AuditID: 0a41282f-b7f8b6d000004656-ca-521455833f00
Received: from XCT103ADS.rim.net (xct103ads.rim.net [10.67.111.44]) by mhs060cnc.rim.net (SBG) with SMTP id 9E.25.18006.38554125; Wed, 21 Aug 2013 00:52:03 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT103ADS.rim.net ([fe80::c8f6:ae2e:c42b:3614%21]) with mapi id 14.03.0123.003; Wed, 21 Aug 2013 00:52:02 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "martin.thomson@gmail.com" <martin.thomson@gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOhJEO4fYTwuVTOkCw8MDTXs0bMZlsItsKgABg4wCAAaXI/oADKwUAgC4Hb4Q=
Date: Wed, 21 Aug 2013 05:52:01 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338E00C83@XMB104ADS.rim.net>
In-Reply-To: <CABkgnnV8Xbf_O08OTZ11GFHRNDfMOmj67Zpc4sVC-kSVmFvPsw@mail.gmail.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMKsWRmVeSWpSXmKPExsXC5Zyvo9scKhJk0PVX3OLZxvksFtfO/GO0 WPpnPosDs8fOWXfZPZYs+cnkcWnpZOYA5qgGRpvEvLz8ksSSVIWU1OJkWyWf1PTEHIWAosyy xORKBZfM4uScxMzc1CIlhcwUWyUTJYWCnMTk1NzUvBJbpcSCgtS8FCU7LgUMYANUlpmnkJqX nJ+SmZduq+QZ7K9rYWFqqWuoZKeLBBL+cWc8f2xXcJirYtH7WSwNjBc4uhg5OSQETCReLDnI CGGLSVy4t56ti5GLQ0hgJaPEjjsXWUASQgKbGSVePS8BsdkEtCT2H57OBGKLCFhKHNwxCayZ WSBEYvGLB+wgtrCArcTl038YIWrsJL4fvMQCYftJTF5+A6yGRUBV4sxUCJtXwENietcmsJmc AoESfbNfg9mMArISu89eZ4KYLy5x68l8JohDBSSW7DnPDGGLSrx8/I8VwlaUeNzSzQJRrydx Y+oUNghbW2LZwtfMELsEJU7OfMIygVF0FpKxs5C0zELSMgtJywJGllWMgrkZxQZmBsl5yXpF mbl6eaklmxhBCcJRQ38H49v3FocYBTgYlXh431qKBAmxJpYVV+YeYpTgYFYS4d3vDBTiTUms rEotyo8vKs1JLT7E6AoMiYnMUtzJ+cDklVcSb2xggJujJM7rqvIhUEggHZiQslNTC1KLYOYw cXBKNTCqXCz727rzs4RE59bv35e+uLXhWv5vNaaf3zNlr//Xi7qUOF8gWmqhqeb/hkrBv1In K3bIhZrwlG65UCexfZvP/p1n/woYeMRz7/ouc/a+/Qf/pRsUt3PKMzJHnbYJdNeXMlV8qLb0 GCO7LrO8/NHZtSZ7l6sd7Fq783qWCUOt9IWcv2o+2pVKLMUZiYZazEXFiQBwwMUeNgMAAA==
Cc: "tbray@textuality.com" <tbray@textuality.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, 21 Aug 2013 05:52:42 -0000

Martin

Further to our conversation on this topic in Berlin I now respond formerly o=
n the list. 

3GPP has defined the mobile terminal as performing the UA role since the ver=
y beginning of IMS. Therefore the mapping between the terminal and the insta=
nce ID in IMS is a one to one relationship. 

Andrew

----- Original Message -----
From: Martin Thomson [mailto:martin.thomson@gmail.com]
Sent: Monday, July 22, 2013 12:57 PM Central Standard Time=0A=
To: Andrew Allen
Cc: tbray@textuality.com <tbray@textuality.com>; ietf@ietf.org <ietf@ietf.or=
g>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

On 20 July 2013 15:34, Andrew Allen <aallen@blackberry.com> wrote:
> There are obviously always alternative design choices but why would you wa=
nt to include both a pre assigned device ID and a generated device ID in the=
 same message?

I think that reading this thread should provide you with ample reasons.

The instance ID in outbound has certain stability requirements that do
not strictly correspond to the lifetime of the hardware in use.  The
other use cases answer very different questions, which include: is
this a stolen device, is this device authorized to use the networks,
etc...   I'm certain those questions can be answered without a device
identifier traversing the network.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From superuser@gmail.com  Tue Aug 20 23:53:06 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBE3811E81B1 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 23:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2bDBV3d7p5W for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 23:53:06 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8227D11E81A1 for <ietf@ietf.org>; Tue, 20 Aug 2013 23:53:05 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e12so30283wgh.33 for <ietf@ietf.org>; Tue, 20 Aug 2013 23:53: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=50+XofXY/NKBaA4uL43ZDGgI93mi8+6i1cfGQRew7c4=; b=cVtY7bsx0WkMxAYHZapTD4LrTZ6Hq024lzodnf3bLX7agZj8tZrVrs4x5PumImuUAg hK2oBqaUDp1kTk3YwZOE6Tgdj5jorvL5J0Xrgjayd6eAMVyiq6j2Epy4zU4+B+Eaj5SZ cphWhi8yoau0se3+0LKSkh4IAX7R8R1AqEmRcBGaRHuWbbgtOKolNsPw34kc+1gzJ7ku GuBljh3inePLfQDRFw2F+6rQX0vw9IGXICpHJTCCtIUx8iMptjipUnT+dOtfUhkfB7N7 ra744qpiBy07Lc3zxr2ZE8aodaxZv5uU/3AaldhvoETcDe9VcDvFysAGR3of+i0LHt5H rhHQ==
MIME-Version: 1.0
X-Received: by 10.194.202.230 with SMTP id kl6mr4612054wjc.9.1377067984604; Tue, 20 Aug 2013 23:53:04 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Tue, 20 Aug 2013 23:53:04 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130815092301.0b86a398@resistor.net>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net>
Date: Tue, 20 Aug 2013 23:53:04 -0700
Message-ID: <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=047d7b873a100dd68b04e46fa04c
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, 21 Aug 2013 06:53:06 -0000

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

On Thu, Aug 15, 2013 at 10:13 AM, SM <sm@resistor.net> wrote:

> The draft-iet-repute-model reference is a down-ref.
>

I agree, the model document should be considered for PS instead.


>
>   "A server receiving a query about an application it does not
>    recognize or explicitly support support (e.g., by virtue of
>    private agreements or experimental extensions) MUST return a
>    404 error code."
>
> There is a typo: "support support".
>

Fixed.


>
> Are there other cases where a 404 is appropriate?  I am asking the
> question as there is a string of proposals built upon RFC 2616 which
> attempt to use HTTP status codes to communicate errors for the layered
> protocol.
>

I don't believe so.  The only cases we can think of are those where the
supported application does or does not exist, and the service being queried
does or does not have data about the subject.  Elsewhere we describe that
there's a specific mechanism to say in a valid reply that no data are
available, so that handles the second question.  You only get to the second
question if the answer to the first is "yes", which leaves the first answer
of "no" that needs handling specified.


>
> In Section 3.2:
>
>   "and SHOULD include an Expires field (see Section 14.21 of [HTTP])
>    indicating a duration for which the template is to be considered
>    valid by clients and not re-queried."
>
> Why is this a RFC 2119 SHOULD?  There is a "SHOULD NOT" following that
> paragraph with a "don't query for a day if there isn't an Expires field".
>  Wouldn't it be easier to have "MUST include the Expires field"?
>

An operator that calculates reputation values on demand would conceivably
give a new value for every query.  If a client wants that up-to-the-moment
accuracy, then Expires is counterproductive.  On the other hand, an
operator that calculates reputation values daily could indicate this by
setting an Expires field of either a day (86400) or the total time between
"now" and the next calculation.

The latter case is likely more prevalent, but it doesn't seem like saying
"MUST" and requiring a value of 0 for the former case is strictly the right
solution.


>   "The template file might contain more than one template.  Such a file
>    MUST have each template separated by a newline (ASCII 0x0D)
>    character."
>
> As this is line oriented it may be better to have CRLF.
>

Why is that?


>
> In Section 3.3:
>
>   "A server SHOULD include support for providing service over HTTP"
>
> Is there a case where the service with work if the server does not support
> HTTP?
>

A client could support HTTP for the template retrieval but only HTTPS for
the service itself, for all the usual privacy and security reasons.

In Section 5:
>
>   "The reputation service itself will use HTTP or other transport
>    methods to issue queries and receive replies.  Those protocols have
>    registered URI schemes and, as such, presumably have documented
>    security considerations."
>
> This is odd.  What other protocols are there to retrieve the URI template?
>

Any URI scheme is supported.  Only HTTP/HTTPS are currently implemented at
the moment.


>
> If I understood the draft, the Proposed Standard angle is:
>
>   http://{service}/{application}**/{subject}/{assertion}
>
> with a "application/reputon+json" response.  Why should that be a Proposed
> Standard?
>
>
That's not "the" angle, it's one possible template.

Does it not qualify as a Proposed Standard?  If not, why not?  Will it fail
to interoperate?

-MSK

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

<div dir=3D"ltr">On Thu, Aug 15, 2013 at 10:13 AM, SM <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&g=
t;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
The draft-iet-repute-model reference is a down-ref.<br></blockquote><div><b=
r></div><div>I agree, the model document should be considered for PS instea=
d.<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
=A0 &quot;A server receiving a query about an application it does not<br>
=A0 =A0recognize or explicitly support support (e.g., by virtue of<br>
=A0 =A0private agreements or experimental extensions) MUST return a<br>
=A0 =A0404 error code.&quot;<br>
<br>
There is a typo: &quot;support support&quot;.<br></blockquote><div><br></di=
v><div>Fixed.<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Are there other cases where a 404 is appropriate? =A0I am asking the questi=
on as there is a string of proposals built upon RFC 2616 which attempt to u=
se HTTP status codes to communicate errors for the layered protocol.<br>
</blockquote><div><br></div><div>I don&#39;t believe so.=A0 The only cases =
we can think of are those where the supported application does or does not =
exist, and the service being queried does or does not have data about the s=
ubject.=A0 Elsewhere we describe that there&#39;s a specific mechanism to s=
ay in a valid reply that no data are available, so that handles the second =
question.=A0 You only get to the second question if the answer to the first=
 is &quot;yes&quot;, which leaves the first answer of &quot;no&quot; that n=
eeds handling specified.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
<br>
In Section 3.2:<br>
<br>
=A0 &quot;and SHOULD include an Expires field (see Section 14.21 of [HTTP])=
<br>
=A0 =A0indicating a duration for which the template is to be considered<br>
=A0 =A0valid by clients and not re-queried.&quot;<br>
<br>
Why is this a RFC 2119 SHOULD? =A0There is a &quot;SHOULD NOT&quot; followi=
ng that paragraph with a &quot;don&#39;t query for a day if there isn&#39;t=
 an Expires field&quot;. =A0Wouldn&#39;t it be easier to have &quot;MUST in=
clude the Expires field&quot;?<br>
</blockquote><div><br></div>An operator that calculates reputation values o=
n demand would conceivably give a new value for every query.=A0 If a client=
 wants that up-to-the-moment accuracy, then Expires is counterproductive.=
=A0 On the other hand, an operator that calculates reputation values daily =
could indicate this by setting an Expires field of either a day (86400) or =
the total time between &quot;now&quot; and the next calculation.<br>
<br>The latter case is likely more prevalent, but it doesn&#39;t seem like =
saying &quot;MUST&quot; and requiring a value of 0 for the former case is s=
trictly the right solution.<br><br></div><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">

<br>
=A0 &quot;The template file might contain more than one template. =A0Such a=
 file<br>
=A0 =A0MUST have each template separated by a newline (ASCII 0x0D)<br>
=A0 =A0character.&quot;<br>
<br>
As this is line oriented it may be better to have CRLF.<br></blockquote><di=
v><br></div><div>Why is that?<br>=A0<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">

<br>
In Section 3.3:<br>
<br>
=A0 &quot;A server SHOULD include support for providing service over HTTP&q=
uot;<br>
<br>
Is there a case where the service with work if the server does not support =
HTTP?<br></blockquote><div><br></div>A client could support HTTP for the te=
mplate retrieval but only HTTPS for the service itself, for all the usual p=
rivacy and security reasons.<br>
</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote"><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
In Section 5:<br>
<br>
=A0 &quot;The reputation service itself will use HTTP or other transport<br=
>
=A0 =A0methods to issue queries and receive replies. =A0Those protocols hav=
e<br>
=A0 =A0registered URI schemes and, as such, presumably have documented<br>
=A0 =A0security considerations.&quot;<br>
<br>
This is odd. =A0What other protocols are there to retrieve the URI template=
?<br></blockquote><div><br></div><div>Any URI scheme is supported.=A0 Only =
HTTP/HTTPS are currently implemented at the moment.<br>=A0<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">

<br>
If I understood the draft, the Proposed Standard angle is:<br>
<br>
=A0 http://{service}/{application}<u></u>/{subject}/{assertion}<br>
<br>
with a &quot;application/reputon+json&quot; response. =A0Why should that be=
 a Proposed Standard?<br>
<br></blockquote><div><br></div><div>That&#39;s not &quot;the&quot; angle, =
it&#39;s one possible template.<br><br>Does it not qualify as a Proposed St=
andard?=A0 If not, why not?=A0 Will it fail to interoperate?<br><br></div>
<div>-MSK<br></div></div></div></div>

--047d7b873a100dd68b04e46fa04c--

From superuser@gmail.com  Tue Aug 20 23:58:17 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCC411E81B1 for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 23:58: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, 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 YqhETinCtjVW for <ietf@ietfa.amsl.com>; Tue, 20 Aug 2013 23:58:16 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8B511E81A1 for <ietf@ietf.org>; Tue, 20 Aug 2013 23:58:16 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id n5so36135wev.34 for <ietf@ietf.org>; Tue, 20 Aug 2013 23:58: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=9jFL59sXRcazDnbeeuDaqEkPU0gSe8iVgxeIZ9J6hQs=; b=0Jc6iXUVgYPybJjDTQgJJRo0tHMKshMRYTIiPHqIDuvKwH2X+zJvXN4rvJC6u/PHiR 5Oj5SI8pCrx6fSU7Pj+YsH/uTbHufI2zOsXo+UtNRiPVIzbiuO+hofEJhJJmAH5E7Y/B yv342Ng2/D3X+OepHmJ20cI6W2bO5wMca17l63rgRyp8KDF7q+lIv5IudSE7PU7NJHe7 CVaHO9jVRQlKi5SQYUjBBgTDUVqyNUBM1NxsegM7vk6PpWDscQiN9jduZqCnjPEIGCP8 WHdNtLvtICLOD6je9USAEoyiFh5NpbRM2q2FiTMnFt2KJLEeT5fV22qfncsiA/SlJw4m /tvw==
MIME-Version: 1.0
X-Received: by 10.180.84.196 with SMTP id b4mr4297445wiz.19.1377068284117; Tue, 20 Aug 2013 23:58:04 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Tue, 20 Aug 2013 23:58:04 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130815101412.0b86a108@resistor.net>
References: <20130815144348.25999.91573.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815101412.0b86a108@resistor.net>
Date: Tue, 20 Aug 2013 23:58:04 -0700
Message-ID: <CAL0qLwa=VDEi6ZChCXz+NNgMY29T5W24dU6GMjSA+kY_wj+P+g@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-email-identifiers-08.txt> (A Reputation Response Set for Email Identifiers) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=f46d04426e2ae80b6f04e46fb1f1
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, 21 Aug 2013 06:58:17 -0000

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

On Thu, Aug 15, 2013 at 10:24 AM, SM <sm@resistor.net> wrote:

>
> draft-ietf-repute-model is a down-ref.  I suggest referencing the updated
> SPF specification as that specification is said to fix some issues in RFC
> 4408.
>

The downref was discussed on another thread.

I left the reference to RFC4408 as is because I was unclear on the timing
of the processing of this document versus RFC4408bis.  I'm fine with making
that change if Pete thinks it's the right choice at this point.

Why is DKIM and SPF normatively referenced while SMTP is an informative
> reference?
>

Yes, they should probably all be the same.  Will fix.

Section 5 states that the draft "is primarily an IANA action and doesn't
> describe any protocols or protocol elements".  Why is the intended status
> "Proposed Standard"?
>

It may not need that status given some of the material that was originally
here has been moved to the other WG documents.  I'll defer to the chairs or
the AD on that one.

-MSK

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

<div dir=3D"ltr">On Thu, Aug 15, 2013 at 10:24 AM, SM <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&g=
t;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
<div class=3D"im"><br></div>
draft-ietf-repute-model is a down-ref. =A0I suggest referencing the updated=
 SPF specification as that specification is said to fix some issues in RFC =
4408.<br></blockquote><div><br></div><div>The downref was discussed on anot=
her thread.<br>
<br></div>I left the reference to RFC4408 as is because I was unclear on th=
e timing of the processing of this document versus RFC4408bis.=A0 I&#39;m f=
ine with making that change if Pete thinks it&#39;s the right choice at thi=
s point.<br>
<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Why is DKIM and SPF normatively referenced while SMTP is an informative ref=
erence?<br></blockquote><div><br></div>Yes, they should probably all be the=
 same.=A0 Will fix.<br><br></div><div class=3D"gmail_quote"><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">

Section 5 states that the draft &quot;is primarily an IANA action and doesn=
&#39;t describe any protocols or protocol elements&quot;. =A0Why is the int=
ended status &quot;Proposed Standard&quot;?<br></blockquote><div><br></div>
<div>It may not need that status given some of the material that was origin=
ally here has been moved to the other WG documents.=A0 I&#39;ll defer to th=
e chairs or the AD on that one.<br><br>-MSK<br></div></div></div></div>

--f46d04426e2ae80b6f04e46fb1f1--

From superuser@gmail.com  Wed Aug 21 00:05:27 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDA7711E81BE for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, 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 PxH9B4k8E5fm for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:05:26 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9BE11E81B1 for <ietf@ietf.org>; Wed, 21 Aug 2013 00:05:25 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id l12so331012wiv.4 for <ietf@ietf.org>; Wed, 21 Aug 2013 00:05:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tWtYkJa2oNkY+h7rX+XM1Hroi/ICZhL04OgFVicqld0=; b=yh6W7Q61X6dInJxoQtd/bUEwLUf2cLxmDLmp5pRq0REfrNSDA36SQRxZ21XciZUNfA P2de6OSvO81BIzR/CrbPUJrw3dBMI6l6QigJXXxGdS70pCDsI8oKoCLFTi3A62ETTzRK iAIW4I/KM1um2vkVlT6yLktaGKG25AxYM4GxBBlMdV4MwKtYhm9mrBhZ0es0hbDEXiuA +hk+MOa0MHYBBQjHRJ/7z/vUZJadzsyWfhsbM6mNZ/x47hqgSWImtXaS6qRe3BsNz8HY fhb9AREUJl8c6Rs5/ixNnGzPvpmf27qhFzSJKNFNLx2IZPuQ8ZA2I1KIL2Dnqk3fZ4Wt NnXA==
MIME-Version: 1.0
X-Received: by 10.194.176.163 with SMTP id cj3mr4510632wjc.8.1377068724396; Wed, 21 Aug 2013 00:05:24 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Wed, 21 Aug 2013 00:05:24 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130815102618.0b86a4e0@resistor.net>
References: <20130815144419.712.35650.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815102618.0b86a4e0@resistor.net>
Date: Wed, 21 Aug 2013 00:05:24 -0700
Message-ID: <CAL0qLwYFXkB5E-5u5PykJu5BztLdhutzJoC41B2k85Lce87cGQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-media-type-10.txt> (A Media Type for Reputation Interchange) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=089e013cbfea26280304e46fccfb
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, 21 Aug 2013 07:05:27 -0000

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

On Thu, Aug 15, 2013 at 10:40 AM, SM <sm@resistor.net> wrote:

>
> From Section 3.1:
>
>    "expires:  A timestamp indicating a time beyond which the score
>       reported is likely not to be valid.  Expressed as the number of
>       seconds since January 1, 1970 00:00 UTC.  See Section 5 for
>       discussion."
>
> And Section 5:
>
>   'A reputon can contain an "expires" field indicating a timestamp after
>    which the client SHOULD NOT use the rating it contains, and SHOULD'
>
> The "expires" field uses "HTTP-date".  It is easier to code for one
> timestamp format instead of two (see Unix timestamp in Section 3.1).
>

By that I assume you mean the Expires field in the HTTP exchange, and not
this value.

An HTTP exchange can contain multiple reputons.  The expiration timestamp
might be different for each.


>
> In Section 3.1:
>
>   "An application service provider might operate with an enhanced form
>    of common services, which might in turn prompt development and
>    reporting of specialized reputation information."
>
> I don't see anything actionable in the above.
>

Taken out of context, of course not.  The text that follows indicates that
the default set of reputon attributes might not be sufficient for
describing all of the information needed in a reputon for a given
application space.  It could be necessary to document additional attributes
and their syntaxes and semantics for those applications.  Those need to be
done in separate documents that register those applications.


> Why was "specification required" chosen for the Reputation Applications
> Registry?
>
>
As alluded to above, there can be quite a bit of information needed for an
application to be defined beyond the defaults assumed when a name is
registered.  There didn't seem to be any need to require such definition to
be in an IETF document, but it also seems as though more information than
what's needed with just FCFS or DE or the other lesser rules is appropriate
either.

-MSK

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

<div dir=3D"ltr">On Thu, Aug 15, 2013 at 10:40 AM, SM <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&g=
t;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
<div class=3D"im"><br></div>
>From Section 3.1:<br>
<br>
=A0 =A0&quot;expires: =A0A timestamp indicating a time beyond which the sco=
re<br>
=A0 =A0 =A0 reported is likely not to be valid. =A0Expressed as the number =
of<br>
=A0 =A0 =A0 seconds since January 1, 1970 00:00 UTC. =A0See Section 5 for<b=
r>
=A0 =A0 =A0 discussion.&quot;<br>
<br>
And Section 5:<br>
<br>
=A0 &#39;A reputon can contain an &quot;expires&quot; field indicating a ti=
mestamp after<br>
=A0 =A0which the client SHOULD NOT use the rating it contains, and SHOULD&#=
39;<br>
<br>
The &quot;expires&quot; field uses &quot;HTTP-date&quot;. =A0It is easier t=
o code for one timestamp format instead of two (see Unix timestamp in Secti=
on 3.1).<br></blockquote><div><br></div><div>By that I assume you mean the =
Expires field in the HTTP exchange, and not this value.<br>
<br></div><div>An HTTP exchange can contain multiple reputons.=A0 The expir=
ation timestamp might be different for each.<br></div><div>=A0<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">

<br>
In Section 3.1:<br>
<br>
=A0 &quot;An application service provider might operate with an enhanced fo=
rm<br>
=A0 =A0of common services, which might in turn prompt development and<br>
=A0 =A0reporting of specialized reputation information.&quot;<br>
<br>
I don&#39;t see anything actionable in the above.<br></blockquote><div><br>=
</div><div>Taken out of context, of course not.=A0 The text that follows in=
dicates that the default set of reputon attributes might not be sufficient =
for describing all of the information needed in a reputon for a given appli=
cation space.=A0 It could be necessary to document additional attributes an=
d their syntaxes and semantics for those applications.=A0 Those need to be =
done in separate documents that register those applications.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
<br>
Why was &quot;specification required&quot; chosen for the Reputation Applic=
ations Registry?<br>
<br></blockquote><div><br></div><div>As alluded to above, there can be quit=
e a bit of information needed for an application to be defined beyond the d=
efaults assumed when a name is registered.=A0 There didn&#39;t seem to be a=
ny need to require such definition to be in an IETF document, but it also s=
eems as though more information than what&#39;s needed with just FCFS or DE=
 or the other lesser rules is appropriate either.<br>
</div><div><br></div><div>-MSK<br></div></div><br></div></div>

--089e013cbfea26280304e46fccfb--

From superuser@gmail.com  Wed Aug 21 00:17:13 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B219321F9C46 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVEtSVgIliQh for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:17:13 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D108121F9CB5 for <ietf@ietf.org>; Wed, 21 Aug 2013 00:17:12 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w62so53326wes.29 for <ietf@ietf.org>; Wed, 21 Aug 2013 00:17: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=mqmjvSIcxbLnsQDD6LswoNzqGZ6rT0U7UP7ZPtlZTTc=; b=ZufhSV5vOu8PYzHooAaaraZNBtwzmlyfoWOBlVXBnFqW/OpOQlO74DGPAKOpNGF1s+ LpKFHE4+HsTnI2ZGHJuopGZVOLH1m6yyg2YbcimTp2nYfBZVV+ZHVVHahJvE7C6jbL9X M0sgnx2K7sSpnqJatXolf9/0fg8MksfehN8vzsS2LaJ4WYZCGT1twv9uMa9RZAPyozGz P/oLavGAQP7/W2uXvpqHTqXybQ30Ru87qxtAs87LFY1z/Eu29+x+gnPzgwwC+fsTx9JI ZHjbFzBsFga+DHOR9fpq80dtvhzphqvu/b/aObCdNH+dnimuhEt62Kt+Ozyn25GsbGCN mEMA==
MIME-Version: 1.0
X-Received: by 10.194.109.68 with SMTP id hq4mr4576308wjb.12.1377069431969; Wed, 21 Aug 2013 00:17:11 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Wed, 21 Aug 2013 00:17:11 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130815104802.0b87f9b0@resistor.net>
References: <20130815144507.22504.36661.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815104802.0b87f9b0@resistor.net>
Date: Wed, 21 Aug 2013 00:17:11 -0700
Message-ID: <CAL0qLwZ-o_1jmLExgGxdNVG686Zs-n8iW54m5b9rU96vxR-d1w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-model-07.txt> (A Model for Reputation Reporting) to Informational RFC
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=089e0102e6da52e0eb04e46ff604
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, 21 Aug 2013 07:17:13 -0000

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

On Thu, Aug 15, 2013 at 11:24 AM, SM <sm@resistor.net> wrote:

> The Privacy Considerations Section focuses on data in transit and
> collection of data only.  Section 8.1 mentions protecting the data from
> "unauthorized access and viewing".  That would only be unauthorized viewing
> while the data is in transit.
>

Sure, mentioning something about the stored aggregated data also makes
sense in Section 8.  I'll add something.


>
> I don't know whether people overlook this; the queries leak out
> information.  Information which the user might consider as private is sent
> out without the person's knowledge.  I suggest pushing that discussion to
> the specification which defines the identity (e.g. draft-ietf-repute-email-
> **identifiers-08).
>

I don't think this point is specific to email identifiers.  This is the
right place to say it.


>
> As a general comment I would say that the issue is less about privacy and
> more about reputation.  There is a saying: Tell me what you read and I will
> tell you who you are.
>
>
Reputations can certainly be private things, both as an aggregate "result"
and as the pieces of data that allowed that result to be reached.  But I
don't think that's a new point given the above.  The new text will cover it.

-MSK

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

<div dir=3D"ltr">On Thu, Aug 15, 2013 at 11:24 AM, SM <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&g=
t;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
The Privacy Considerations Section focuses on data in transit and collectio=
n of data only. =A0Section 8.1 mentions protecting the data from &quot;unau=
thorized access and viewing&quot;. =A0That would only be unauthorized viewi=
ng while the data is in transit.<br>
</blockquote><div><br></div><div>Sure, mentioning something about the store=
d aggregated data also makes sense in Section 8.=A0 I&#39;ll add something.=
<br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
I don&#39;t know whether people overlook this; the queries leak out informa=
tion. =A0Information which the user might consider as private is sent out w=
ithout the person&#39;s knowledge. =A0I suggest pushing that discussion to =
the specification which defines the identity (e.g. draft-ietf-repute-email-=
<u></u>identifiers-08).<br>
</blockquote><div><br></div><div>I don&#39;t think this point is specific t=
o email identifiers.=A0 This is the right place to say it.<br>=A0<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<br>
As a general comment I would say that the issue is less about privacy and m=
ore about reputation. =A0There is a saying: Tell me what you read and I wil=
l tell you who you are.<br>
<br></blockquote><div><br></div>Reputations can certainly be private things=
, both as an aggregate &quot;result&quot; and as the pieces of data that al=
lowed that result to be reached.=A0 But I don&#39;t think that&#39;s a new =
point given the above.=A0 The new text will cover it.<br>
<br>-MSK<br></div></div></div>

--089e0102e6da52e0eb04e46ff604--

From drc@virtualized.org  Wed Aug 21 00:18:06 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DF111E81C0 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yhMKnex9ZFe5 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:18:01 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id B9E8921F9D12 for <ietf@ietf.org>; Wed, 21 Aug 2013 00:18:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id E79708712A; Wed, 21 Aug 2013 03:17:59 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 19528-06; Wed, 21 Aug 2013 03:17:59 -0400 (EDT)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 1787D87128; Wed, 21 Aug 2013 03:17:58 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E2EFB081-0F33-40E3-B4CA-BEB1E7EB5ABB"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20130821040003.GL607@mx1.yitter.info>
Date: Wed, 21 Aug 2013 00:17:57 -0700
Message-Id: <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 07:18:06 -0000

--Apple-Mail=_E2EFB081-0F33-40E3-B4CA-BEB1E7EB5ABB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Aug 20, 2013, at 9:00 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
> The WG had a hard time coming up with really good data about what =
validators look for, ... If someone else with some busy nameservers =
wants to provide different evidence now, it wouldn't hurt.

Out of morbid curiosity, I just looked at the logs from my name server =
(which has both TXT and SPF RRs but which is very, very far from being =
busy) with a quick perl hack:

2011/07/30 08:07:51 spf: 2, txt: 1, 200.000000%
2011/08/10 21:28:41 spf: 4, txt: 121, 3.305785%
2011/08/14 21:30:11 spf: 1, txt: 45, 2.222222%
2011/08/16 17:20:40 spf: 0, txt: 5, 0.000000%
2011/08/17 00:53:42 spf: 1, txt: 1, 100.000000%
2011/08/19 01:10:53 spf: 0, txt: 6, 0.000000%
2011/08/21 03:09:09 spf: 27, txt: 45, 60.000000%
2011/09/13 04:25:21 spf: 30, txt: 113, 26.548673%
2011/09/15 16:19:41 spf: 3, txt: 16, 18.750000%
2011/09/15 17:16:35 spf: 0, txt: 3, 0.000000%
2011/09/22 18:35:07 spf: 6, txt: 22, 27.272727%
2011/09/26 19:08:48 spf: 0, txt: 7, 0.000000%
2011/09/30 01:02:42 spf: 1, txt: 7, 14.285714%
2011/10/10 03:53:19 spf: 42, txt: 157, 26.751592%
2011/10/20 00:39:06 spf: 2, txt: 14, 14.285714%
2011/10/31 19:08:55 spf: 5, txt: 141, 3.546099%
2011/11/02 20:37:05 spf: 0, txt: 16, 0.000000%
2011/11/15 17:15:38 spf: 8, txt: 196, 4.081633%
2011/11/30 19:04:48 spf: 47, txt: 335, 14.029851%
2011/12/12 22:18:55 spf: 1, txt: 294, 0.340136%
2011/12/25 16:04:50 spf: 16, txt: 611, 2.618658%
2011/12/29 17:58:19 spf: 1, txt: 2, 50.000000%
2012/01/12 01:15:17 spf: 2, txt: 52, 3.846154%
2012/01/18 22:24:14 spf: 0, txt: 60, 0.000000%
2012/01/30 00:45:27 spf: 2, txt: 121, 1.652893%
2012/02/02 17:18:54 spf: 54, txt: 288, 18.750000%
2012/02/10 23:59:02 spf: 0, txt: 102, 0.000000%
2012/02/23 00:52:47 spf: 20, txt: 201, 9.950249%
2012/03/19 03:17:46 spf: 118, txt: 580, 20.344828%
2012/03/24 18:33:15 spf: 2, txt: 46, 4.347826%
2012/04/13 16:41:10 spf: 121, txt: 1743, 6.942054%
2012/05/19 18:20:14 spf: 54, txt: 631, 8.557845%
2012/06/07 13:52:26 spf: 82, txt: 961, 8.532778%
2012/07/05 02:48:39 spf: 26, txt: 339, 7.669617%
2012/07/05 18:24:30 spf: 0, txt: 4, 0.000000%
2012/07/07 19:21:02 spf: 3, txt: 25, 12.000000%
2012/07/17 14:48:32 spf: 3, txt: 156, 1.923077%
2012/08/07 18:19:36 spf: 7, txt: 269, 2.602230%
2012/08/19 04:38:08 spf: 23, txt: 198, 11.616162%
2012/08/31 21:23:20 spf: 27, txt: 190, 14.210526%
2012/10/21 07:45:13 spf: 185, txt: 1285, 14.396887%
2012/12/07 21:59:04 spf: 74, txt: 704, 10.511364%
2012/12/11 18:28:28 spf: 0, txt: 24, 0.000000%
2012/12/31 07:51:05 spf: 52, txt: 436, 11.926606%
2013/01/08 00:30:31 spf: 10, txt: 119, 8.403361%
2013/02/02 01:30:47 spf: 22, txt: 341, 6.451613%
2013/02/16 06:44:53 spf: 20, txt: 143, 13.986014%
2013/02/28 01:58:33 spf: 11, txt: 153, 7.189542%
2013/03/05 02:38:51 spf: 5, txt: 75, 6.666667%
2013/03/08 23:47:17 spf: 0, txt: 99, 0.000000%
2013/03/09 02:21:46 spf: 1, txt: 1, 100.000000%
2013/03/20 01:29:03 spf: 46, txt: 1232, 3.733766%
2013/03/24 06:22:59 spf: 15, txt: 212, 7.075472%
2013/03/26 06:03:50 spf: 0, txt: 11, 0.000000%
2013/03/31 23:17:16 spf: 8, txt: 208, 3.846154%
2013/04/06 05:19:48 spf: 37, txt: 587, 6.303237%
2013/04/07 21:53:19 spf: 1, txt: 37, 2.702703%
2013/04/16 18:50:43 spf: 13, txt: 279, 4.659498%
2013/04/22 05:52:43 spf: 3, txt: 163, 1.840491%
2013/04/29 17:56:04 spf: 14, txt: 440, 3.181818%
2013/05/22 16:26:40 spf: 20, txt: 606, 3.300330%
2013/05/23 12:08:25 spf: 1, txt: 9, 11.111111%
2013/05/23 12:30:12 spf: 0, txt: 1, 0.000000%
2013/05/28 19:14:02 spf: 21, txt: 380, 5.526316%
2013/07/01 02:29:15 spf: 51, txt: 2246, 2.270703%
2013/07/01 15:02:05 spf: 2, txt: 16, 12.500000%
2013/07/07 04:50:19 spf: 0, txt: 109, 0.000000%
2013/07/24 01:09:39 spf: 36, txt: 1395, 2.580645%
totals: spf: 1389, txt: 19435, 7.146900%

(the numbers are queries since the name server last restarted/dumped =
stats)

Will look for better data than my measly little name server.

Regards,
-drc


--Apple-Mail=_E2EFB081-0F33-40E3-B4CA-BEB1E7EB5ABB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSFGmlAAoJEIzZ2DQOJFbKY1YH/RT05upCWRCVhJuRa8YJmzxd
PMUhtDr/J+7gUScwwSWAIDRldXTk1BMLkNHu6bLxG0i7bSY2/3DPSzq/LnXGFYVN
wM2CHmrfoUTDGFACpHCKKLjUvO0UfP9+xi6woCuNK4wZZagIK0/pjLIpoApTTs93
OBIwpuyAt4DxKDflcLHui6HBHSTt6apoCfzU5hg0HxmwSX/VRMl+W7aKhUwBA5IW
D3IrkbyLUYxLRHcoUhtAssCno+iXVdtktpLY7EoPsIe+S7U73MRsRPbUzZpTuZtz
VbykkTYYblbkUEDReNMflbyjbZ7tIFvzaOZB101DQREo5rCGhMnpSuN1BnDoLy8=
=XHKz
-----END PGP SIGNATURE-----

--Apple-Mail=_E2EFB081-0F33-40E3-B4CA-BEB1E7EB5ABB--

From zhangfatai@huawei.com  Wed Aug 21 00:41:34 2013
Return-Path: <zhangfatai@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4108B11E81C0; Wed, 21 Aug 2013 00:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.649
X-Spam-Level: 
X-Spam-Status: No, score=-5.649 tagged_above=-999 required=5 tests=[AWL=0.949,  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 bc+TfkdK0xpN; Wed, 21 Aug 2013 00:41:30 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 31D6B11E81D7; Wed, 21 Aug 2013 00:41:29 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUO65662; Wed, 21 Aug 2013 07:41:28 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 21 Aug 2013 08:40:58 +0100
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 21 Aug 2013 08:41:26 +0100
Received: from SZXEML552-MBS.china.huawei.com ([169.254.2.110]) by szxeml402-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.007; Wed, 21 Aug 2013 15:39:33 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt> (Generalized	Multi-Protocol Label Switching (GMPLS) Signaling Extensions	for the evolving G.709 Optical Transport Networks Control) to	Proposed Standard
Thread-Topic: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt> (Generalized	Multi-Protocol Label Switching (GMPLS) Signaling Extensions	for the evolving G.709 Optical Transport Networks Control) to	Proposed Standard
Thread-Index: Ac6d1f8U/0fVrXNNRjCEO33cHnCIigAaKmFg
Date: Wed, 21 Aug 2013 07:39:32 +0000
Message-ID: <F82A4B6D50F9464B8EBA55651F541CF85AF38E3A@SZXEML552-MBS.china.huawei.com>
References: <00fe01ce9dd6$2dc59a10$8950ce30$@olddog.co.uk>
In-Reply-To: <00fe01ce9dd6$2dc59a10$8950ce30$@olddog.co.uk>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.72.159]
Content-Type: multipart/alternative; boundary="_000_F82A4B6D50F9464B8EBA55651F541CF85AF38E3ASZXEML552MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 07:41:34 -0000

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

Hi Adrian,



Thanks very much.



I can update the nits and editorial issues quickly, but I would like to dis=
cuss more with you for the following points to make things clear before I u=
pdate the draft.



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Please consider and note what updates to GMPLS management tools are needed.



[Fatai]This has been mentioned in [Framework] document. Did you mean that w=
e need add one sentence in some place of this document to refer to [Framewo=
rk] document to mention management tools?



Are there any changes to the Alarms that might arise? We have a document fo=
r that.



[Fatai] No. RFC4783 is still applicable.



Are there any changes to the way OAM is controlled? We have a document for =
that.



[Fatai] No, it could be done through NMS or [draft-ietf-ccamp-rsvp-te-sdh-o=
tn-oam-ext].



Should the new G-PIDs show in the TC MIB managed by IANA at

https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml

This should happen automgically when the feeding registries are updated

but it is probably best to add a specific request for IANA.



[Fatai] Will do that.



Will other MIB work be needed (in the future) to make it possible to

read new information (labels, tspecs) from network devices?



[Fatai] I am not sure. I asked the similar question (not on this draft) dur=
ing Berlin meeting. The chairs answered that it could be driven by drafts.







Best Regards



Fatai



-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of A=
drian Farrel
Sent: Wednesday, August 21, 2013 2:51 AM
To: ietf@ietf.org
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-signaling-g709v3-11=
.txt> (Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensi=
ons for the evolving G.709 Optical Transport Networks Control) to Proposed =
Standard



As sponsoring AD I have the following last call comments I hope you will ta=
ke on

board.



Thanks,

Adrian



Please fix the two lines that are too long (see idnits)



---



Please expand "OTN" on first use in the main text.

Please expand "TS" on its first use.



---



6.2



   The ingress node of an LSP MAY include Label ERO (Explicit Route

   Object) to indicate the label in each hops along the path.



Missing "subobject".



---



6.2.1



   When an upstream node receives a Resv message containing an

   GENERALIZED_LABEL object



s/an/a/



---



Please consider and note what updates to GMPLS management tools are

needed.



Are there any changes to the Alarms that might arise? We have a document

for that.



Are there any changes to the way OAM is controlled? We have a document

for that.



Should the new G-PIDs show in the TC MIB managed by IANA at

https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml

This should happen automgically when the feeding registries are updated

but it is probably best to add a specific request for IANA.



Will other MIB work be needed (in the future) to make it possible to

read new information (labels, tspecs) from network devices?



---



Please fix so that you have three sections:



Authors' Addresses (only those people on the front page)

Contributors (other people who made significant text contributions to

the document)

Acknowledgements (other people who helped with the work)



---



[OTN-OSPF] should be a normative reference for its use to define the

value of the switching type used in signaling.



_______________________________________________

CCAMP mailing list

CCAMP@ietf.org

https://www.ietf.org/mailman/listinfo/ccamp

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	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:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.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"ZH-CN" link=3D"blue" vlink=3D"purple" style=3D"text-justify-t=
rim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Hi Adrian,<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Thanks very much. <o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">I can update the nits and ed=
itorial issues quickly, but I would like to discuss more with you for the f=
ollowing points to make things clear before I update the draft.
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please consider and note wha=
t updates to GMPLS management tools are needed.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:#002060">[Fat=
ai]This has been mentioned in [Framework] document. Did you mean that we ne=
ed add one sentence in some place of this document to refer to [Framework] =
document to mention management tools?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Are there any changes to the=
 Alarms that might arise? We have a document for that.<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:#002060">[Fat=
ai] No. RFC4783 is still applicable.</span><span lang=3D"EN-US"><o:p></o:p>=
</span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Are there any changes to the=
 way OAM is controlled? We have a document for that.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:#002060">[Fat=
ai] No, it could be done through NMS or [draft-ietf-ccamp-rsvp-te-sdh-otn-o=
am-ext].</span><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Should the new G-PIDs show i=
n the TC MIB managed by IANA at<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">https://www.iana.org/assignm=
ents/ianagmplstc-mib/ianagmplstc-mib.xhtml<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">This should happen automgica=
lly when the feeding registries are updated<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">but it is probably best to a=
dd a specific request for IANA.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:#002060">[Fat=
ai] Will do that.</span><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Will other MIB work be neede=
d (in the future) to make it possible to
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">read new information (labels=
, tspecs) from network devices?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:#002060">[Fat=
ai] I am not sure. I asked the similar question (not on this draft) during =
Berlin meeting. The chairs answered that it could be driven by drafts.</spa=
n><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Best Regards<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Fatai<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-----Original Message-----<b=
r>
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of A=
drian Farrel<br>
Sent: Wednesday, August 21, 2013 2:51 AM<br>
To: ietf@ietf.org<br>
Cc: ccamp@ietf.org<br>
Subject: Re: [CCAMP] Last Call: &lt;draft-ietf-ccamp-gmpls-signaling-g709v3=
-11.txt&gt; (Generalized Multi-Protocol Label Switching (GMPLS) Signaling E=
xtensions for the evolving G.709 Optical Transport Networks Control) to Pro=
posed Standard<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">As sponsoring AD I have the =
following last call comments I hope you will take on<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">board.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Thanks,<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Adrian<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please fix the two lines tha=
t are too long (see idnits)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please expand &quot;OTN&quot=
; on first use in the main text.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please expand &quot;TS&quot;=
 on its first use.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">6.2<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; The ingress nod=
e of an LSP MAY include Label ERO (Explicit Route
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;Object) to=
 indicate the label in each hops along the path.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Missing &quot;subobject&quot=
;.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">6.2.1<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp; When an upstrea=
m node receives a Resv message containing an
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;GENERALIZE=
D_LABEL object<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">s/an/a/<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please consider and note wha=
t updates to GMPLS management tools are<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">needed.<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Are there any changes to the=
 Alarms that might arise? We have a document<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">for that.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Are there any changes to the=
 way OAM is controlled? We have a document<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">for that.<o:p></o:p></span><=
/p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Should the new G-PIDs show i=
n the TC MIB managed by IANA at<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">https://www.iana.org/assignm=
ents/ianagmplstc-mib/ianagmplstc-mib.xhtml<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">This should happen automgica=
lly when the feeding registries are updated<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">but it is probably best to a=
dd a specific request for IANA.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Will other MIB work be neede=
d (in the future) to make it possible to
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">read new information (labels=
, tspecs) from network devices?<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Please fix so that you have =
three sections:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Authors' Addresses (only tho=
se people on the front page)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Contributors (other people w=
ho made significant text contributions to<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">the document)<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Acknowledgements (other peop=
le who helped with the work)<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">---<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">[OTN-OSPF] should be a norma=
tive reference for its use to define the
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">value of the switching type =
used in signaling.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">____________________________=
___________________<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">CCAMP mailing list<o:p></o:p=
></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">CCAMP@ietf.org<o:p></o:p></s=
pan></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">https://www.ietf.org/mailman=
/listinfo/ccamp<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_F82A4B6D50F9464B8EBA55651F541CF85AF38E3ASZXEML552MBSchi_--

From sustrik@250bpm.com  Wed Aug 21 00:50:22 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C515211E81DA for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnKKQVQNc07q for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:50:17 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id D561711E81C0 for <ietf@ietf.org>; Wed, 21 Aug 2013 00:50:16 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 39E4A1803548; Wed, 21 Aug 2013 09:50:14 +0200 (CEST)
Message-ID: <52147135.9060705@250bpm.com>
Date: Wed, 21 Aug 2013 09:50:13 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu>
In-Reply-To: <521384B8.9020505@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 07:50:23 -0000

On 20/08/13 17:01, Joe Touch wrote:

> However, see my other message - it's hard to recommend an approach when
> we don't understand the problem you're trying to solve.

The scenario is simple.

You want admin to open one port in the firewall when the project is 
started. Going through the corporate process at this point is bearable 
and makes sense.

Afterwards, you want to be able to expose arbitrary services through 
that port without having to go through port-opening process over and 
over again.

The services are actually different aspects of the same distributed 
application, say, data distribution service, management service, 
heartbeating service etc. so not requiring additional process for adding 
them makes sense.

The real problem here IMO is how to distinguish between "adding a 
completely new application" -- which should require approval process -- 
and "adding a new component within an existing distributed application" 
-- which should be managed by devs themselves.

Martin


From sm@resistor.net  Wed Aug 21 00:55:48 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B2F11E81DE for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.501
X-Spam-Level: 
X-Spam-Status: No, score=-102.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJAh36lD+qUq for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 00:55:45 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DFA811E81BD for <ietf@ietf.org>; Wed, 21 Aug 2013 00:55:44 -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 r7L7tWfC027358; Wed, 21 Aug 2013 00:55:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377071740; bh=TVicVMYeOBjP6mxJc+jIgVhaUPdxiK+u/8QjxkvvBqI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=A1LoZTUOXaheU9yqfo0IFV54m1JY4vxUPOlRbeZvAROeHjm27ip3olsNP+Y8dQkiZ cl9/J9INnW064hg0RXgoLxp+rdh7o8TPNRXK5F4OfWdNmS5+G7CC3OoxIY6sxVxtNn w86uPG4EORtm4VUczNMO/OkuxyW5QUydt199i2iQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377071740; i=@resistor.net; bh=TVicVMYeOBjP6mxJc+jIgVhaUPdxiK+u/8QjxkvvBqI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uElDS0zdfxtb3DkwUam/FM6HVNYGLX7Jrm3AVqy7znvPz/ejPrP9Miv9L0ArfBlps NYa7RNL+jgCqIr9Oug3wCz730hrG9KIEolwqgl32+4ctAwb08jbSQb4lvUApkVGP/U 84gVkJJDnQRCVQ4pGHd7yKlmd/a1fkraXB7vGso0=
Message-Id: <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Aug 2013 00:43:44 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
In-Reply-To: <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.g mail.com>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@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, 21 Aug 2013 07:55:48 -0000

At 23:53 20-08-2013, Murray S. Kucherawy wrote:
>I don't believe so.  The only cases we can think of are those where 
>the supported application does or does not exist, and the service 
>being queried does or does not have data about the 
>subject.  Elsewhere we describe that there's a specific mechanism to 
>say in a valid reply that no data are available, so that handles the 
>second question.  You only get to the second question if the answer 
>to the first is "yes", which leaves the first answer of "no" that 
>needs handling specified.

Ok.

>An operator that calculates reputation values on demand would 
>conceivably give a new value for every query.  If a client wants 
>that up-to-the-moment accuracy, then Expires is 
>counterproductive.  On the other hand, an operator that calculates 
>reputation values daily could indicate this by setting an Expires 
>field of either a day (86400) or the total time between "now" and 
>the next calculation.
>
>The latter case is likely more prevalent, but it doesn't seem like 
>saying "MUST" and requiring a value of 0 for the former case is 
>strictly the right solution.

I see what you mean.  The server-specified expiration (see RFC 2616) 
uses other headers as well.

>Why is that?

The media type is "text/plain".


>A client could support HTTP for the template retrieval but only 
>HTTPS for the service itself, for all the usual privacy and security reasons.

Ok.

>Any URI scheme is supported.  Only HTTP/HTTPS are currently 
>implemented at the moment.

Ok.

>That's not "the" angle, it's one possible template.
>
>Does it not qualify as a Proposed Standard?  If not, why not?  Will 
>it fail to interoperate?

The quick answer is that I am not sure.  I'll defer to you.

Regards,
-sm 


From superuser@gmail.com  Wed Aug 21 01:14:47 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F0E11E81DF for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 01:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 wV09gRgiw47n for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 01:14:46 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id B3B3611E81CB for <ietf@ietf.org>; Wed, 21 Aug 2013 01:14:45 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id q57so100554wes.26 for <ietf@ietf.org>; Wed, 21 Aug 2013 01:14: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=TzKiLOZptEDVrHvRE5+EUf0Tdj567M42CoNR8CNHWUY=; b=qf7Na8tORu+2FtUJuBUz0GXC4OSwXYL1vIEazHpotsp/7HJp1TH9Vrm30smd16y6Na lO2dsouxmF1h7EY3+arbvZPRWcZgQaiOP2OTwJjyvGQhUymZyUtYFzsrLvxrRnr7fXkM w0KqDZWVGb/9rvWrMFajM+K6JESAdv4Z3HrUh76AZnBIOMXQGANquFUXdHzJmVxupU56 b/mJq2KnMwQtB3ZtLxDYHeEsy4fjrGqoH8W9YKGfrA/AiMab8GZj4J4j+1rqjlzMIx6o DoeTvo+0iz9WKLi10u+88cNnv3w6CRnNyvKwNDmfzyAVt0x9RGhHsTu9OCyYGnI+Bd5E W1Gg==
MIME-Version: 1.0
X-Received: by 10.180.84.196 with SMTP id b4mr4551564wiz.19.1377072884462; Wed, 21 Aug 2013 01:14:44 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Wed, 21 Aug 2013 01:14:44 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com> <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net>
Date: Wed, 21 Aug 2013 01:14:44 -0700
Message-ID: <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=f46d04426e2a1bb80c04e470c47f
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, 21 Aug 2013 08:14:47 -0000

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

On Wed, Aug 21, 2013 at 12:43 AM, SM <sm@resistor.net> wrote:

>
>  Why is that?
>>
>
> The media type is "text/plain".
>
>
Ah.  I realize that CRLF is standard line termination for SMTP; is it
automatically the expected line termination for all line-oriented
protocols?  I don't know about others.

-MSK

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

<div dir=3D"ltr">On Wed, Aug 21, 2013 at 12:43 AM, SM <span dir=3D"ltr">&lt=
;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&g=
t;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Why is that?<br>
</blockquote>
<br>
The media type is &quot;text/plain&quot;.<div class=3D"im"><br></div></bloc=
kquote><div><br></div><div>Ah.=A0 I realize that CRLF is standard line term=
ination for SMTP; is it automatically the expected line termination for all=
 line-oriented protocols?=A0 I don&#39;t know about others.<br>
<br></div><div>-MSK<br></div></div></div></div>

--f46d04426e2a1bb80c04e470c47f--

From mansaxel@besserwisser.org  Wed Aug 21 03:01:07 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2A0711E81BA; Wed, 21 Aug 2013 03:01:07 -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.250,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zsjy1P75zr92; Wed, 21 Aug 2013 03:01:07 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 3108511E80ED; Wed, 21 Aug 2013 03:01:07 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 191BF9E98; Wed, 21 Aug 2013 12:00:56 +0200 (CEST)
Date: Wed, 21 Aug 2013 12:00:56 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130821100055.GF30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <6.2.5.6.2.20130819202422.0d1756a8@resistor.net> <52137A3B.6040200@isdg.net> <6.2.5.6.2.20130820100431.0df2aea0@elandnews.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Zs/RYxT/hKAHzkfQ"
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20130820100431.0df2aea0@elandnews.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: spfbis@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 10:01:07 -0000

--Zs/RYxT/hKAHzkfQ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender=
 Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1)=
 to Proposed Standard Date: Tue, Aug 20, 2013 at 10:30:41AM -0700 Quoting S=
 Moonesamy (sm+ietf@elandsys.c
=20
> My reading of  the SPFBIS Charter is that the working group was not
> tasked to work on the future of DNS servers.  That does not mean
> that arguments about the future of DNS servers are not relevant.

The codification of a pessimistic view of the ability of the DNS installed
base to adapt to new RRtypes is - in itself - a statement that influences
the future of DNS. That this was not completely understood in terms of
influence weight is one of the reasons for this debate.
=20
> There are several questions:
>=20
>  (a) Was there an error in RFC 4408?

Yes.=20
=20
>  (b) What was the error in RFC 4408?

The TXT rrtype was not properly decommissioned; it lacked definitiveness,
and neither publication instructions nor selection/query algorithm
satisfy this (originally intended, I suppose and believe) sunset view
of the TXT record r=C3=B4le vis =C3=A0 vis SPF.

>  (c) Why was there an error in RFC 4408?
>=20
>  (d) What should be done about the error?

4408bis needs a better defined depreciation statement for TXT,
accompanied by publication and  query methods that will ensure the
continous phasing-out of SPF data in TXT records.

A clarification here will help in making DNS UI vendors doing the right
thing. I'm quite confident that presently, the UI vendors sleep soundly
after reading 4408 and continuing to ignore SPF/99. That is not=20
desirable.=20
=20
> There isn't anything that can be done about question (c) except not
> to repeat the same mistake.
>=20
> Is there disagreement on the answers to questions (a) and (b)?

Apparently.=20

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
I'm using my X-RAY VISION to obtain a rare glimpse of the INNER
WORKINGS of this POTATO!!

--Zs/RYxT/hKAHzkfQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iEYEARECAAYFAlIUj9cACgkQ02/pMZDM1cWoRQCfdvStmypCAbYiuhp8hxkMM9oJ
82IAn21zIW8Jlt1CR9yPIZUpNU1Xdk6u
=Rde7
-----END PGP SIGNATURE-----

--Zs/RYxT/hKAHzkfQ--

From adrian@olddog.co.uk  Wed Aug 21 03:12:46 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 675BD11E81FE; Wed, 21 Aug 2013 03:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.027,  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 day94XmTs7Rz; Wed, 21 Aug 2013 03:12:41 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id E598E11E8101; Wed, 21 Aug 2013 03:12:40 -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 r7LACSwV032503;  Wed, 21 Aug 2013 11:12:28 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7LACPwc032470 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 21 Aug 2013 11:12:26 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Fatai Zhang'" <zhangfatai@huawei.com>, <ietf@ietf.org>
References: <00fe01ce9dd6$2dc59a10$8950ce30$@olddog.co.uk> <F82A4B6D50F9464B8EBA55651F541CF85AF38E3A@SZXEML552-MBS.china.huawei.com>
In-Reply-To: <F82A4B6D50F9464B8EBA55651F541CF85AF38E3A@SZXEML552-MBS.china.huawei.com>
Subject: RE: [CCAMP] Last Call:	<draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt> (Generalized	Multi-Protocol Label Switching (GMPLS) Signaling Extensions	for the evolving G.709 Optical Transport Networks Control) to	Proposed Standard
Date: Wed, 21 Aug 2013 11:12:24 +0100
Message-ID: <008e01ce9e56$ef180d30$cd482790$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008F_01CE9E5F.50DFF7A0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIsbNb5TgnC0suQ8+Rs20wgK20xygJciecUmNDvnBA=
Content-Language: en-gb
Cc: ccamp@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, 21 Aug 2013 10:12:46 -0000

This is a multipart message in MIME format.

------=_NextPart_000_008F_01CE9E5F.50DFF7A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Fatai,
 
I think you nicely answered your own questions :-)
 
I would suggest adding a small section including all of the statements you made
in your email. (Well, no need to refer to Berlin and the CCAMP chairs :-)
 
Cheers,
Adrian
 
From: Fatai Zhang [mailto:zhangfatai@huawei.com] 
Sent: 21 August 2013 08:40
To: adrian@olddog.co.uk; ietf@ietf.org
Cc: ccamp@ietf.org
Subject: RE: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt>
(Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for the
evolving G.709 Optical Transport Networks Control) to Proposed Standard
 
Hi Adrian,
 
Thanks very much. 
 
I can update the nits and editorial issues quickly, but I would like to discuss
more with you for the following points to make things clear before I update the
draft. 
 
================================================================================
=========
Please consider and note what updates to GMPLS management tools are needed.
 
[Fatai]This has been mentioned in [Framework] document. Did you mean that we
need add one sentence in some place of this document to refer to [Framework]
document to mention management tools?
 
Are there any changes to the Alarms that might arise? We have a document for
that.
 
[Fatai] No. RFC4783 is still applicable.
 
Are there any changes to the way OAM is controlled? We have a document for that.
 
[Fatai] No, it could be done through NMS or
[draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext].
 
Should the new G-PIDs show in the TC MIB managed by IANA at
https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml
This should happen automgically when the feeding registries are updated
but it is probably best to add a specific request for IANA.
 
[Fatai] Will do that.
 
Will other MIB work be needed (in the future) to make it possible to 
read new information (labels, tspecs) from network devices?
 
[Fatai] I am not sure. I asked the similar question (not on this draft) during
Berlin meeting. The chairs answered that it could be driven by drafts.
 
 
 
Best Regards
 
Fatai
 
-----Original Message-----
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of Adrian
Farrel
Sent: Wednesday, August 21, 2013 2:51 AM
To: ietf@ietf.org
Cc: ccamp@ietf.org
Subject: Re: [CCAMP] Last Call: <draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt>
(Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for the
evolving G.709 Optical Transport Networks Control) to Proposed Standard
 
As sponsoring AD I have the following last call comments I hope you will take on
board.
 
Thanks,
Adrian
 
Please fix the two lines that are too long (see idnits)
 
---
 
Please expand "OTN" on first use in the main text.
Please expand "TS" on its first use.
 
---
 
6.2
 
   The ingress node of an LSP MAY include Label ERO (Explicit Route 
   Object) to indicate the label in each hops along the path.
 
Missing "subobject".
 
---
 
6.2.1
 
   When an upstream node receives a Resv message containing an 
   GENERALIZED_LABEL object
 
s/an/a/
 
---
 
Please consider and note what updates to GMPLS management tools are
needed.
 
Are there any changes to the Alarms that might arise? We have a document
for that.
 
Are there any changes to the way OAM is controlled? We have a document
for that.
 
Should the new G-PIDs show in the TC MIB managed by IANA at
https://www.iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml
This should happen automgically when the feeding registries are updated
but it is probably best to add a specific request for IANA.
 
Will other MIB work be needed (in the future) to make it possible to 
read new information (labels, tspecs) from network devices?
 
---
 
Please fix so that you have three sections:
 
Authors' Addresses (only those people on the front page)
Contributors (other people who made significant text contributions to
the document)
Acknowledgements (other people who helped with the work)
 
---
 
[OTN-OSPF] should be a normative reference for its use to define the 
value of the switching type used in signaling.
 
_______________________________________________
CCAMP mailing list
CCAMP@ietf.org
https://www.ietf.org/mailman/listinfo/ccamp

------=_NextPart_000_008F_01CE9E5F.50DFF7A0
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@01CE9E5F.4E2125C0"><!--[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:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:roman;
	mso-font-format:other;
	mso-font-pitch:auto;
	mso-font-signature:0 0 0 0 0 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;
	text-align:justify;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
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:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
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";
	mso-ansi-font-size:10.5pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Consolas","serif";
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Consolas;}
p.a, li.a, div.a
	{mso-style-name:\7EAF\6587\672C;
	mso-style-unhide:no;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	mso-pagination:widow-orphan;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;}
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:"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;}
--></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;text-justify-trim:punctuation'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New Roman";color:#1F497D'>Hi =
Fatai,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New Roman";color:#1F497D'>I =
think you nicely answered your own questions :-)<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New Roman";color:#1F497D'>I =
would suggest adding a small section including all of the statements you =
made in your email. (Well, no need to refer to Berlin and the CCAMP =
chairs :-)<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily:Calibri;mso-bidi-font-family:"Times New =
Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;mso-ascii-font-family:Calibri;mso-hansi-font-fa=
mily: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 align=3Dleft =
style=3D'text-align:left'><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'> Fatai Zhang =
[mailto:zhangfatai@huawei.com] <br><b>Sent:</b> 21 August 2013 =
08:40<br><b>To:</b> adrian@olddog.co.uk; ietf@ietf.org<br><b>Cc:</b> =
ccamp@ietf.org<br><b>Subject:</b> RE: [CCAMP] Last Call: =
&lt;draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt&gt; (Generalized =
Multi-Protocol Label Switching (GMPLS) Signaling Extensions for the =
evolving G.709 Optical Transport Networks Control) to Proposed =
Standard<o:p></o:p></span></p></div></div><p class=3DMsoNormal =
align=3Dleft style=3D'text-align:left'><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Hi =
Adrian,<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Thanks very =
much. <o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>I can =
update the nits and editorial issues quickly, but I would like to =
discuss more with you for the following points to make things clear =
before I update the draft. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Please =
consider and note what updates to GMPLS management tools are =
needed.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#002060;mso-ansi-language:EN-US;mso-fareast-language:ZH-CN=
'>[Fatai]This has been mentioned in [Framework] document. Did you mean =
that we need add one sentence in some place of this document to refer to =
[Framework] document to mention management =
tools?<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Are there =
any changes to the Alarms that might arise? We have a document for =
that.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#002060;mso-ansi-language:EN-US;mso-fareast-language:ZH-CN=
'>[Fatai] No. RFC4783 is still applicable.</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Are there =
any changes to the way OAM is controlled? We have a document for =
that.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#002060;mso-ansi-language:EN-US;mso-fareast-language:ZH-CN=
'>[Fatai] No, it could be done through NMS or =
[draft-ietf-ccamp-rsvp-te-sdh-otn-oam-ext].</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Should the =
new G-PIDs show in the TC MIB managed by IANA at<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>https://www.=
iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml<o:p></o:p></sp=
an></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>This should =
happen automgically when the feeding registries are =
updated<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>but it is =
probably best to add a specific request for =
IANA.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#002060;mso-ansi-language:EN-US;mso-fareast-language:ZH-CN=
'>[Fatai] Will do that.</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Will other =
MIB work be needed (in the future) to make it possible to =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>read new =
information (labels, tspecs) from network =
devices?<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'color:#002060;mso-ansi-language:EN-US;mso-fareast-language:ZH-CN=
'>[Fatai] I am not sure. I asked the similar question (not on this =
draft) during Berlin meeting. The chairs answered that it could be =
driven by drafts.</span><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p></o:p><=
/span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Best =
Regards<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Fatai<o:p></=
o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>-----Origina=
l Message-----<br>From: ccamp-bounces@ietf.org =
[mailto:ccamp-bounces@ietf.org] On Behalf Of Adrian Farrel<br>Sent: =
Wednesday, August 21, 2013 2:51 AM<br>To: ietf@ietf.org<br>Cc: =
ccamp@ietf.org<br>Subject: Re: [CCAMP] Last Call: =
&lt;draft-ietf-ccamp-gmpls-signaling-g709v3-11.txt&gt; (Generalized =
Multi-Protocol Label Switching (GMPLS) Signaling Extensions for the =
evolving G.709 Optical Transport Networks Control) to Proposed =
Standard<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>As =
sponsoring AD I have the following last call comments I hope you will =
take on<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>board.<o:p><=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Thanks,<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Adrian<o:p><=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Please fix =
the two lines that are too long (see idnits)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>---<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Please =
expand &quot;OTN&quot; on first use in the main =
text.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Please =
expand &quot;TS&quot; on its first use.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>---<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>6.2<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;=
 The ingress node of an LSP MAY include Label ERO (Explicit Route =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;=
&nbsp;Object) to indicate the label in each hops along the =
path.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Missing =
&quot;subobject&quot;.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>---<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>6.2.1<o:p></=
o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;=
 When an upstream node receives a Resv message containing an =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>&nbsp;&nbsp;=
&nbsp;GENERALIZED_LABEL object<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>s/an/a/<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>---<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Please =
consider and note what updates to GMPLS management tools =
are<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>needed.<o:p>=
</o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Are there =
any changes to the Alarms that might arise? We have a =
document<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>for =
that.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Are there =
any changes to the way OAM is controlled? We have a =
document<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>for =
that.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Should the =
new G-PIDs show in the TC MIB managed by IANA at<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>https://www.=
iana.org/assignments/ianagmplstc-mib/ianagmplstc-mib.xhtml<o:p></o:p></sp=
an></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>This should =
happen automgically when the feeding registries are =
updated<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>but it is =
probably best to add a specific request for =
IANA.<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Will other =
MIB work be needed (in the future) to make it possible to =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>read new =
information (labels, tspecs) from network =
devices?<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>---<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Please fix =
so that you have three sections:<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Authors' =
Addresses (only those people on the front page)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Contributors=
 (other people who made significant text contributions =
to<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>the =
document)<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>Acknowledgem=
ents (other people who helped with the work)<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>---<o:p></o:=
p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>[OTN-OSPF] =
should be a normative reference for its use to define the =
<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>value of =
the switching type used in signaling.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>____________=
___________________________________<o:p></o:p></span></p><p =
class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>CCAMP =
mailing list<o:p></o:p></span></p><p class=3DMsoPlainText><span =
lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>CCAMP@ietf.o=
rg<o:p></o:p></span></p><p class=3DMsoPlainText><span lang=3DEN-US =
style=3D'mso-ansi-language:EN-US;mso-fareast-language:ZH-CN'>https://www.=
ietf.org/mailman/listinfo/ccamp<o:p></o:p></span></p></div></div></body><=
/html>
------=_NextPart_000_008F_01CE9E5F.50DFF7A0--


From paf@frobbit.se  Wed Aug 21 03:15:22 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F3A11E81D4 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 03:15:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=-0.187, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n0TdLEUNKq1S for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 03:15:22 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 3799611E81C3 for <ietf@ietf.org>; Wed, 21 Aug 2013 03:15:22 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::12] (unknown [IPv6:2a02:80:3ffc::12]) by mail.frobbit.se (Postfix) with ESMTPA id 5F5AA23F76; Wed, 21 Aug 2013 12:15:21 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_13484E25-8FE3-4E70-94AF-A299313E02CA"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>
Date: Wed, 21 Aug 2013 12:15:21 +0200
Message-Id: <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 10:15:22 -0000

--Apple-Mail=_13484E25-8FE3-4E70-94AF-A299313E02CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 21 aug 2013, at 09:17, David Conrad <drc@virtualized.org> wrote:

> On Aug 20, 2013, at 9:00 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
>> The WG had a hard time coming up with really good data about what =
validators look for, ... If someone else with some busy nameservers =
wants to provide different evidence now, it wouldn't hurt.
>=20
> Out of morbid curiosity, I just looked at the logs from my name server =
(which has both TXT and SPF RRs but which is very, very far from being =
busy) with a quick perl hack:
:
:
:
> totals: spf: 1389, txt: 19435, 7.146900%
>=20
> (the numbers are queries since the name server last restarted/dumped =
stats)
>=20
> Will look for better data than my measly little name server.

I have been looking at the queries to one of the nameservers that =
Frobbit runs (which is authoritative for quite a number of zones, =
although not GoDaddy), and a tcpdump for a while today gives the =
following data:

$ /usr/sbin/tcpdump -nr dns.pcap | grep 'SPF?' | wc -l
reading from file dns.pcap, link-type EN10MB (Ethernet)
tcpdump: pcap_loop: truncated dump file; tried to read 271 captured =
bytes, only got 95
1105
$ /usr/sbin/tcpdump -nr dns.pcap | grep 'TXT?' | wc -l
reading from file dns.pcap, link-type EN10MB (Ethernet)
tcpdump: pcap_loop: truncated dump file; tried to read 94 captured =
bytes, only got 18
2819

I.e. 2819 queries for TXT while there was 1105 for SPF resource record.

Now, I have no idea whether all of those queries for TXT was only for =
the SPF usage of TXT of course, but this gives it was at least 28% of =
(TXT+SPF)-queries that was for SPF.

Deprecating something that is in use that much just does not make any =
sense.

   Patrik


--Apple-Mail=_13484E25-8FE3-4E70-94AF-A299313E02CA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlIUkzkACgkQrMabGguI1833uACfTT6kQOfXm20mILwZGC+Vxjdn
WmkAnRv+/QS69WHhZEE8VajvO6Uw69Gg
=VHte
-----END PGP SIGNATURE-----

--Apple-Mail=_13484E25-8FE3-4E70-94AF-A299313E02CA--

From lear@cisco.com  Wed Aug 21 03:27:13 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B073521F8413 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 03:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.123
X-Spam-Level: 
X-Spam-Status: No, score=-110.123 tagged_above=-999 required=5 tests=[AWL=-0.425, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6, 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 k6AcmiNR1WGc for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 03:26:58 -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 C102D11E81BA for <ietf@ietf.org>; Wed, 21 Aug 2013 03:26:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6459; q=dns/txt; s=iport; t=1377080818; x=1378290418; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=YQ0TfDENoA66D7xHtuoNBr6bnzL7iaUIDFNhSLgu28k=; b=E8vX9XUuEge4Qs8f/HiB6f6LJMm1R/2H6+AvmcB+ncJ3bBRFHDg6v74m XIFrPEAYdPP/oNSP9WP2j2swCLcEwxzUqh1V1MimrRwAIHExhs3moNd3m iDQO9LFy6VEEcnBpw8mSzuRqb2DZnzrHec8n4pv+273L3kxgTHJ5Zc669 U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFADaVFFKQ/khM/2dsb2JhbABagwWEIIVdtmKBJRZ0giQBAQEEI1UBEAsYCRYEBwICCQMCAQIBRQYNAQUCAQGIDKMiimuPDIFJB4JogSwDl2WRVoFhgT06gS4HFwY
X-IronPort-AV: E=Sophos;i="4.89,927,1367971200"; d="scan'208,217";a="16880473"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 21 Aug 2013 10:26:54 +0000
Received: from ams3-vpn-dhcp4704.cisco.com (ams3-vpn-dhcp4704.cisco.com [10.61.82.95]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7LAQqR2022845 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 10:26:52 GMT
Message-ID: <521495EB.7060207@cisco.com>
Date: Wed, 21 Aug 2013 12:26:51 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>
In-Reply-To: <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------070402010809020806060909"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 10:27:13 -0000

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

Patrik,

First, I appreciate that you and Dave are bringing data to the table. 
However, in this case, it is not in dispute that queries are happening. 
What *is* in dispute is whether there are answers.  I must admit I am
having a difficult time understanding the logic, even so.  The *hard*
part about this was supposed to be implementation of the record in the
application software.  Can the shepherd answer this question:

  * To what extent has that happened?

The easy part was supposed to be people actually using the SPF record,
once it was out there.  And so your data doesn't indicate what sort of
answers you're getting.

And another thing. Randy, is it your position that WGs shouldn't create
new TXT records due to transition issues?

Eliot


On 8/21/13 12:15 PM, Patrik FÃ¤ltstrÃ¶m wrote:
> On 21 aug 2013, at 09:17, David Conrad <drc@virtualized.org> wrote:
>
>> On Aug 20, 2013, at 9:00 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
>>> The WG had a hard time coming up with really good data about what validators look for, ... If someone else with some busy nameservers wants to provide different evidence now, it wouldn't hurt.
>> Out of morbid curiosity, I just looked at the logs from my name server (which has both TXT and SPF RRs but which is very, very far from being busy) with a quick perl hack:
> :
> :
> :
>> totals: spf: 1389, txt: 19435, 7.146900%
>>
>> (the numbers are queries since the name server last restarted/dumped stats)
>>
>> Will look for better data than my measly little name server.
> I have been looking at the queries to one of the nameservers that Frobbit runs (which is authoritative for quite a number of zones, although not GoDaddy), and a tcpdump for a while today gives the following data:
>
> $ /usr/sbin/tcpdump -nr dns.pcap | grep 'SPF?' | wc -l
> reading from file dns.pcap, link-type EN10MB (Ethernet)
> tcpdump: pcap_loop: truncated dump file; tried to read 271 captured bytes, only got 95
> 1105
> $ /usr/sbin/tcpdump -nr dns.pcap | grep 'TXT?' | wc -l
> reading from file dns.pcap, link-type EN10MB (Ethernet)
> tcpdump: pcap_loop: truncated dump file; tried to read 94 captured bytes, only got 18
> 2819
>
> I.e. 2819 queries for TXT while there was 1105 for SPF resource record.
>
> Now, I have no idea whether all of those queries for TXT was only for the SPF usage of TXT of course, but this gives it was at least 28% of (TXT+SPF)-queries that was for SPF.
>
> Deprecating something that is in use that much just does not make any sense.
>
>    Patrik
>


--------------070402010809020806060909
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">
    Patrik,<br>
    <br>
    First, I appreciate that you and Dave are bringing data to the
    table.Â  However, in this case, it is not in dispute that queries are
    happening.Â  What *is* in dispute is whether there are answers.Â  I
    must admit I am having a difficult time understanding the logic,
    even so.Â  The *hard* part about this was supposed to be
    implementation of the record in the application software.Â  Can the
    shepherd answer this question:<br>
    <ul>
      <li>To what extent has that happened?</li>
    </ul>
    <p>The easy part was supposed to be people actually using the SPF
      record, once it was out there.Â  And so your data doesn't indicate
      what sort of answers you're getting.<br>
    </p>
    <p>And another thing. Randy, is it your position that WGs shouldn't
      create new TXT records due to transition issues?<br>
    </p>
    <p>Eliot<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 8/21/13 12:15 PM, Patrik FÃ¤ltstrÃ¶m
      wrote:<br>
    </div>
    <blockquote
      cite="mid:7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se"
      type="cite">
      <pre wrap="">
On 21 aug 2013, at 09:17, David Conrad <a class="moz-txt-link-rfc2396E" href="mailto:drc@virtualized.org">&lt;drc@virtualized.org&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">On Aug 20, 2013, at 9:00 PM, Andrew Sullivan <a class="moz-txt-link-rfc2396E" href="mailto:ajs@anvilwalrusden.com">&lt;ajs@anvilwalrusden.com&gt;</a> wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">The WG had a hard time coming up with really good data about what validators look for, ... If someone else with some busy nameservers wants to provide different evidence now, it wouldn't hurt.
</pre>
        </blockquote>
        <pre wrap="">
Out of morbid curiosity, I just looked at the logs from my name server (which has both TXT and SPF RRs but which is very, very far from being busy) with a quick perl hack:
</pre>
      </blockquote>
      <pre wrap="">:
:
:
</pre>
      <blockquote type="cite">
        <pre wrap="">totals: spf: 1389, txt: 19435, 7.146900%

(the numbers are queries since the name server last restarted/dumped stats)

Will look for better data than my measly little name server.
</pre>
      </blockquote>
      <pre wrap="">
I have been looking at the queries to one of the nameservers that Frobbit runs (which is authoritative for quite a number of zones, although not GoDaddy), and a tcpdump for a while today gives the following data:

$ /usr/sbin/tcpdump -nr dns.pcap | grep 'SPF?' | wc -l
reading from file dns.pcap, link-type EN10MB (Ethernet)
tcpdump: pcap_loop: truncated dump file; tried to read 271 captured bytes, only got 95
1105
$ /usr/sbin/tcpdump -nr dns.pcap | grep 'TXT?' | wc -l
reading from file dns.pcap, link-type EN10MB (Ethernet)
tcpdump: pcap_loop: truncated dump file; tried to read 94 captured bytes, only got 18
2819

I.e. 2819 queries for TXT while there was 1105 for SPF resource record.

Now, I have no idea whether all of those queries for TXT was only for the SPF usage of TXT of course, but this gives it was at least 28% of (TXT+SPF)-queries that was for SPF.

Deprecating something that is in use that much just does not make any sense.

   Patrik

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070402010809020806060909--

From paf@frobbit.se  Wed Aug 21 03:42:58 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B8711E820D for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 03:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.133,  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 Rw3SU3vXjfzf for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 03:42:56 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id C2D8211E81BA for <ietf@ietf.org>; Wed, 21 Aug 2013 03:42:56 -0700 (PDT)
Received: from vpn-client-208.netnod.se (vpn-client-208.netnod.se [192.71.80.208]) by mail.frobbit.se (Postfix) with ESMTPA id 1B8D621F96; Wed, 21 Aug 2013 12:42:56 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_018A6A01-F0B6-4A32-8016-D60811F79CE7"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <521495EB.7060207@cisco.com>
Date: Wed, 21 Aug 2013 12:42:55 +0200
Message-Id: <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 10:42:58 -0000

--Apple-Mail=_018A6A01-F0B6-4A32-8016-D60811F79CE7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 21 aug 2013, at 12:26, Eliot Lear <lear@cisco.com> wrote:

> The easy part was supposed to be people actually using the SPF record, =
once it was out there.  And so your data doesn't indicate what sort of =
answers you're getting.

These are logs on one of my authoritative servers, and the queries you =
see are the queries sent _TO_ the server. So of course I also have the =
responses I give to the one those queries.

   Patrik


--Apple-Mail=_018A6A01-F0B6-4A32-8016-D60811F79CE7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlIUma8ACgkQrMabGguI1819ogCdFdxX7zQ8yDwdQXzLztMVFVzW
RhwAniM7iei5/yReR3JECRqldPRlpnMO
=PuTp
-----END PGP SIGNATURE-----

--Apple-Mail=_018A6A01-F0B6-4A32-8016-D60811F79CE7--

From lear@cisco.com  Wed Aug 21 04:33:48 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B98111E820C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 04:33:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.391
X-Spam-Level: 
X-Spam-Status: No, score=-110.391 tagged_above=-999 required=5 tests=[AWL=-0.092, 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 n2foImvtV50c for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 04:33: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 38FCE11E81FD for <ietf@ietf.org>; Wed, 21 Aug 2013 04:33:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=592; q=dns/txt; s=iport; t=1377084824; x=1378294424; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=dmfBT6U0hPZELzit8GlzR8R3K51hMZYo75khTlGyrBU=; b=k/02MecpnAftOxqmPOrcESw6w329MEHicbq2V+z94WOJcj8wzyVMV27l S9YKeoV0nF3+1K3HzMsn85DcOtv/axCyzfzDmSgmfOKN0MFEd8yG9qDEU YBCQWQqrzjlD8XzPZ0IsolAtm+LEkPT1a82J0k4JvbHuC/QtZeTuzaVam 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUFAHOkFFKQ/khM/2dsb2JhbABbgwWDWUe8P4EiFnSCJAEBAQQjDwFFARALGAICBRYEBwICCQMCAQIBRQYNAQUCAQGIDKMWinOBKY1jgUkHgmiBLAOXZZFWgWGBPTqBNQ
X-IronPort-AV: E=Sophos;i="4.89,927,1367971200"; d="scan'208";a="16882556"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 21 Aug 2013 11:33:43 +0000
Received: from ams3-vpn-dhcp4704.cisco.com (ams3-vpn-dhcp4704.cisco.com [10.61.82.95]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r7LBXdXk009921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 11:33:40 GMT
Message-ID: <5214A593.8030907@cisco.com>
Date: Wed, 21 Aug 2013 13:33:39 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>
In-Reply-To: <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 11:33:48 -0000

So your point is that their conclusions that nobody has the record
installed is false?

Eliot

On 8/21/13 12:42 PM, Patrik FÃ¤ltstrÃ¶m wrote:
> On 21 aug 2013, at 12:26, Eliot Lear <lear@cisco.com> wrote:
>
>> The easy part was supposed to be people actually using the SPF record, once it was out there.  And so your data doesn't indicate what sort of answers you're getting.
> These are logs on one of my authoritative servers, and the queries you see are the queries sent _TO_ the server. So of course I also have the responses I give to the one those queries.
>
>    Patrik
>


From bmanning@isi.edu  Wed Aug 21 04:56:28 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9A511E8396 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 04:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.999
X-Spam-Level: 
X-Spam-Status: No, score=-105.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_34=0.6, 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 JCxyKgRh75HT for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 04:56:21 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id A696E11E8392 for <ietf@ietf.org>; Wed, 21 Aug 2013 04:56:21 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r7LBtXwj022449 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 21 Aug 2013 04:55:43 -0700 (PDT)
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <521495EB.7060207@cisco.com>
Date: Wed, 21 Aug 2013 04:55:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9C96A4F-36CA-47E4-B2DF-4BFDD7EC277D@isi.edu>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: ietf@ietf.org, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 11:56:28 -0000

regarding adoption=85  it would be interesting to take a second snapshot =
from each of these servers in about six months
to see if the trend has changed (modulo PAFs observations that not all =
TXT =3D=3D SPF).   In the mean time, declare a suspension of
last call to gauge if the presumption of failure of the SPF RR merits =
this drastic action.

/bill


On 21August2013Wednesday, at 3:26, Eliot Lear wrote:

> Patrik,
>=20
> First, I appreciate that you and Dave are bringing data to the table.  =
However, in this case, it is not in dispute that queries are happening.  =
What *is* in dispute is whether there are answers.  I must admit I am =
having a difficult time understanding the logic, even so.  The *hard* =
part about this was supposed to be implementation of the record in the =
application software.  Can the shepherd answer this question:
> 	=95 To what extent has that happened?
> The easy part was supposed to be people actually using the SPF record, =
once it was out there.  And so your data doesn't indicate what sort of =
answers you're getting.
> And another thing. Randy, is it your position that WGs shouldn't =
create new TXT records due to transition issues?
> Eliot
>=20
> On 8/21/13 12:15 PM, Patrik F=E4ltstr=F6m wrote:
>> On 21 aug 2013, at 09:17, David Conrad <drc@virtualized.org>
>>  wrote:
>>=20
>>=20
>>> On Aug 20, 2013, at 9:00 PM, Andrew Sullivan =
<ajs@anvilwalrusden.com>
>>>  wrote:
>>>=20
>>>> The WG had a hard time coming up with really good data about what =
validators look for, ... If someone else with some busy nameservers =
wants to provide different evidence now, it wouldn't hurt.
>>>>=20
>>> Out of morbid curiosity, I just looked at the logs from my name =
server (which has both TXT and SPF RRs but which is very, very far from =
being busy) with a quick perl hack:
>>>=20
>> :
>> :
>> :
>>=20
>>> totals: spf: 1389, txt: 19435, 7.146900%
>>>=20
>>> (the numbers are queries since the name server last restarted/dumped =
stats)
>>>=20
>>> Will look for better data than my measly little name server.
>>>=20
>> I have been looking at the queries to one of the nameservers that =
Frobbit runs (which is authoritative for quite a number of zones, =
although not GoDaddy), and a tcpdump for a while today gives the =
following data:
>>=20
>> $ /usr/sbin/tcpdump -nr dns.pcap | grep 'SPF?' | wc -l
>> reading from file dns.pcap, link-type EN10MB (Ethernet)
>> tcpdump: pcap_loop: truncated dump file; tried to read 271 captured =
bytes, only got 95
>> 1105
>> $ /usr/sbin/tcpdump -nr dns.pcap | grep 'TXT?' | wc -l
>> reading from file dns.pcap, link-type EN10MB (Ethernet)
>> tcpdump: pcap_loop: truncated dump file; tried to read 94 captured =
bytes, only got 18
>> 2819
>>=20
>> I.e. 2819 queries for TXT while there was 1105 for SPF resource =
record.
>>=20
>> Now, I have no idea whether all of those queries for TXT was only for =
the SPF usage of TXT of course, but this gives it was at least 28% of =
(TXT+SPF)-queries that was for SPF.
>>=20
>> Deprecating something that is in use that much just does not make any =
sense.
>>=20
>>    Patrik
>>=20
>>=20
>=20


From scott@kitterman.com  Wed Aug 21 05:51:52 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E6811E8391 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 05:51:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hy9WGbcFhTVg for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 05:51:47 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 3483A11E8386 for <ietf@ietf.org>; Wed, 21 Aug 2013 05:51:46 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id F1EE220E40FD; Wed, 21 Aug 2013 08:51:33 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377089494; bh=hKIWefjO/sQnG0nqlkgcW4adavgH9JaAF/ncArMzt0U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=he6WlAUKH53CfakVHJo/BH9XGWot2A7DquHR1vMxj5w26/ys9JGIb8Gq8lETQ+LJb CgwAJKgNP7AMIxzWlHZ3+TfAxv/WDeDavi8zLSUEYr0Crnj9yQ5kZGu2sn5liDNbcq o2r5F0bmqAzKt2nMURhkPbqeaehcAeDdGWt8QcYo=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id D1EFD20E40C2;  Wed, 21 Aug 2013 08:51:33 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 21 Aug 2013 08:51:31 -0400
Message-ID: <13637683.gDTVOaM8nE@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821100055.GF30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130820100431.0df2aea0@elandnews.com> <20130821100055.GF30516@besserwisser.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 12:51:52 -0000

On Wednesday, August 21, 2013 12:00:56 M=E5ns Nilsson wrote:
> Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (=
Sender
> Policy?Framework (SPF) for Authorizing Use of Domains in Email, Versi=
on 1)
> to Proposed Standard Date: Tue, Aug 20, 2013 at 10:30:41AM -0700 Quot=
ing S
> Moonesamy (sm+ietf@elandsys.c
> > My reading of  the SPFBIS Charter is that the working group was not=

> > tasked to work on the future of DNS servers.  That does not mean
> > that arguments about the future of DNS servers are not relevant.
>=20
> The codification of a pessimistic view of the ability of the DNS inst=
alled
> base to adapt to new RRtypes is - in itself - a statement that influe=
nces
> the future of DNS. That this was not completely understood in terms o=
f
> influence weight is one of the reasons for this debate.
>=20
> > There are several questions:
> >  (a) Was there an error in RFC 4408?
>=20
> Yes.
>=20
> >  (b) What was the error in RFC 4408?
>=20
> The TXT rrtype was not properly decommissioned; it lacked definitiven=
ess,
> and neither publication instructions nor selection/query algorithm
> satisfy this (originally intended, I suppose and believe) sunset view=

> of the TXT record r=F4le vis =E0 vis SPF.
>=20
> >  (c) Why was there an error in RFC 4408?
> > =20
> >  (d) What should be done about the error?
>=20
> 4408bis needs a better defined depreciation statement for TXT,
> accompanied by publication and  query methods that will ensure the
> continous phasing-out of SPF data in TXT records.
>=20
> A clarification here will help in making DNS UI vendors doing the rig=
ht
> thing. I'm quite confident that presently, the UI vendors sleep sound=
ly
> after reading 4408 and continuing to ignore SPF/99. That is not
> desirable.
>=20
> > There isn't anything that can be done about question (c) except not=

> > to repeat the same mistake.
> >=20
> > Is there disagreement on the answers to questions (a) and (b)?
>=20
> Apparently.

Translated:

RFC 4408 was in error because it didn't abandon it's installed base.  I=
 gather=20
this is an error you propose to rectify.

Scott K

From kathleen.moriarty@emc.com  Wed Aug 21 06:16:56 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3FE11E8216 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kF8-b3+hJ0v3 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:16:52 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2B611E80D3 for <ietf@ietf.org>; Wed, 21 Aug 2013 06:16:49 -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 r7LDGeW4018803 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 21 Aug 2013 09:16:44 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor) for <ietf@ietf.org>; Wed, 21 Aug 2013 09:16:24 -0400
Received: from mxhub26.corp.emc.com (mxhub26.corp.emc.com [10.254.110.182]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7LDGO2k030974 for <ietf@ietf.org>; Wed, 21 Aug 2013 09:16:24 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub26.corp.emc.com ([10.254.110.182]) with mapi; Wed, 21 Aug 2013 09:16:24 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 21 Aug 2013 09:16:04 -0400
Subject: WG overview - MILE video
Thread-Topic: WG overview - MILE video
Thread-Index: AQHOnnCifbJBI/4uKUez38nTuDLU9A==
Message-ID: <F5063677821E3B4F81ACFB7905573F24E36596FE@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 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, 21 Aug 2013 13:16:56 -0000

Hello,

Sometime before Berlin, I had suggested the use of a video to provide an ov=
erview of current work within a working group to see if that might be a use=
ful tool.  It was suggested, on this list, I should do this for MILE and se=
e how it works out.  While in Berlin, with the help of the fabulous MeetEch=
o team, we made a brief video and t is now posted as a link within the MILE=
 charter.  I'd like to collect feedback to see how useful it is and some ma=
y be anecdotal from lurkers who now better understand the work or maybe we'=
ll see an increase in participation.

http://datatracker.ietf.org/wg/mile/charter/

Thank you,
Kathleen

From ron.even.tlv@gmail.com  Wed Aug 21 06:29:35 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F23011E8396; Wed, 21 Aug 2013 06:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 iNaQLPa3imcn; Wed, 21 Aug 2013 06:29:34 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C32F111E80DE; Wed, 21 Aug 2013 06:29:33 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id n12so408877wgh.24 for <multiple recipients>; Wed, 21 Aug 2013 06:29:32 -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 :thread-index:content-language; bh=h7MnCGGYN6vapeaS4e4bugFkN5rC80oWOpaLWkXN998=; b=VNObMlPgE+sV/CST+4Cezae8PkyhcjbzZ8K3uR2WvghQpQDUjtlN0G/F6CMQY3brzC ufxGObtt29GO7EEpl0u++uko2mZKnsGolFzAjwpeQKkSjl4JPJWvoe9476k0olKabByh jCexvvyrg3+iKdTbW5kVpwi3NG/sAKxb7KZrAZo6fjFHPPc7Fm8yrjcbHbis1BYeD+nq sAkSUkwhg2jEyhy+f3uulPVco2ujGgM3ubMA9vdWqUHbJBS5igpTMSt16vCHdQtgywAs o0fvjMQvEhpyDWbrFyyljqqJJpNg/wA/jPRbzsBFssjsEi9wuOQGY4oDKXvu/6jby90D Xtlw==
X-Received: by 10.180.109.10 with SMTP id ho10mr16607757wib.14.1377091772810;  Wed, 21 Aug 2013 06:29:32 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id dt17sm31148295wic.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 21 Aug 2013 06:29:32 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-repute-model.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-repute-model-07
Date: Wed, 21 Aug 2013 16:27:03 +0300
Message-ID: <02be01ce9e72$25ac43f0$7104cbd0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02BF_01CE9E8B.4AFA1830"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6ech93EjPEiJ4iR5m11MTCM0qVkg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 13:29:35 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02BF_01CE9E8B.4AFA1830
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-repute-model-07

Reviewer: Roni Even

Review Date:2013-8-20

IETF LC End Date: 2013-8-29

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

Minor issues:

I was wondering why the "Further Discussion" section 9.3 is part of the
security section. I think it should be a separate section.

Nits/editorial comments:

Section 3 the end of 2nd paragraph "mechansisms" to "mechanisms"

 

 


------=_NextPart_000_02BF_01CE9E8B.4AFA1830
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-repute-model-07</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;20<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-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 an Informational 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=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>I was =
wondering why the &#8220;Further Discussion&#8221; section 9.3 is part =
of the security section. I think it should be a separate =
section.<o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal>Section 3 the end of =
2<sup>nd</sup> paragraph &#8220;mechansisms&#8221; to =
&#8220;mechanisms&#8221;<span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3Dpolicy.abstract></a><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02BF_01CE9E8B.4AFA1830--


From marka@isc.org  Wed Aug 21 06:32:57 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88CA11E83AF for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[AWL=0.327,  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 Q-5Zs9q+1bWV for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:32:53 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 3DFDC11E839A for <ietf@ietf.org>; Wed, 21 Aug 2013 06:32:49 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 23FDAC944E; Wed, 21 Aug 2013 13:32:36 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377091969; bh=H3yhNx3qJ6EHJJssuA2AtstGbxWNPqogv7tF6QRnhDI=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=R9bFB1Ksm4K6s7kvMIZQuXTRnGwwC6vkcmFJCVPA4QQwlvaRfAwDB0/nzx1iYgfl6 w3PGnj120RaB/C5VOyK4RBgNEWfAUl4zzKMtacoHQvzm+eOFtYNoxVm3tLB1etjMLz UbfSEdz9P7HLbP2sQ39gr/5wLFtd9akRGfRZTSmY=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 21 Aug 2013 13:32:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 6C0991602E9; Wed, 21 Aug 2013 13:32:46 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 3D4DE1602B4; Wed, 21 Aug 2013 13:32:46 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id D0A6B38BE02F; Wed, 21 Aug 2013 23:32:33 +1000 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130820100431.0df2aea0@elandnews.com> <20130821100055.GF30516@besserwisser.org> <13637683.gDTVOaM8nE@scott-latitude-e6320>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Wed, 21 Aug 2013 08:51:31 -0400." <13637683.gDTVOaM8nE@scott-latitude-e6320>
Date: Wed, 21 Aug 2013 23:32:33 +1000
Message-Id: <20130821133233.D0A6B38BE02F@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 13:32:58 -0000

I object to the removal of the SPF record.

Name servers already have access controls down to the granuality
of TYPE.  If this draft proceeds as currently described it is forcing
name server vendors to access controls at the sub TYPE granuality.

With SPF lookup first I can specify the SPF policy using SPF and
leave TXT free for other uses without having to worry about the
records being misinterpeted.

SPF validators MUST NOT proceed to a TXT lookup on SERVFAIL for SPF.
This is similar to not proceeding to A/AAAA lookups on MX lookup
failures. 

I would also suggest that there be a sunset date published for the
use of TXT for SPF.

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

From ajs@anvilwalrusden.com  Wed Aug 21 06:39:46 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8170711E839A for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yoCVbBMuUsnF for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:39:40 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id A45BC11E83A1 for <ietf@ietf.org>; Wed, 21 Aug 2013 06:39:40 -0700 (PDT)
Received: from crankycanuck.ca (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 89DE48A031 for <ietf@ietf.org>; Wed, 21 Aug 2013 13:39:30 +0000 (UTC)
Date: Wed, 21 Aug 2013 09:39:28 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130821133928.GA27579@crankycanuck.ca>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <521495EB.7060207@cisco.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, 21 Aug 2013 13:39:46 -0000

No hat

On Wed, Aug 21, 2013 at 12:26:51PM +0200, Eliot Lear wrote:

> However, in this case, it is not in dispute that queries are happening. 

Actually, that _was_ in question.  Remember, part of the justification
for ditching TYPE99 is not only that publishers don't use it, but also
that if they did there'd be no benefit.

The evidence the WG produced was that there were hardly any validators
querying for SPF.  The WG originally had somewhat stronger claims in
the draft, and I objected because I felt our sample wasn't good
enough.  The data that Patrik and David have presented suggest that
there might indeed be more to the story, but again there are some
issues with the samples.

There are two additional things that would help make sense of these
numbers.  First, the raw number of queries isn't very interesting, if
mail transactions all turn out to be with the same parties.  We can't
count the same party asking for TYPE99 twice as two validators.
Second, how many of these TYPE99 queries arrive within the same time
frame (yes, I'm waving my hands)?  If the TYPE99 queries are being
issued at the same time as the TXT record, that's an indication that
the query source actually has no preference, and just wants the answer
that comes fastest.

The evidence that the WG looked at suggested that really only Yahoo
preferred TYPE99, and that they stopped preferring it.  There was one
large mail system (I can't recall who) that sent TYPE99 queries, but
actually sent both SPF and TXT at the same time in an effort to get
the quickest response possible.  As Scott has noted elsewhere in this
thread, the SPF processing is often a blocking operation for mail
systems, so latency added by two lookups in that processing is a big
deal (particularly for very large systems).

>   * To what extent has that happened?

I'm not the shepherd, but it is undeniable that most current-era
shipping DNS servers support RRTYPE 99.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ajs@anvilwalrusden.com  Wed Aug 21 06:44:32 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F11311E83BC for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:44:32 -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 E2zCNdRXZojs for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 06:44:26 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id CDEB311E83C0 for <ietf@ietf.org>; Wed, 21 Aug 2013 06:44:25 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 4FFAD8A031 for <ietf@ietf.org>; Wed, 21 Aug 2013 13:44:25 +0000 (UTC)
Date: Wed, 21 Aug 2013 09:44:26 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130821134426.GB27579@mx1.yitter.info>
References: <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <E9C96A4F-36CA-47E4-B2DF-4BFDD7EC277D@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E9C96A4F-36CA-47E4-B2DF-4BFDD7EC277D@isi.edu>
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, 21 Aug 2013 13:44:32 -0000

Speaking as the SPFBIS co-chairâ€¦

On Wed, Aug 21, 2013 at 04:55:33AM -0700, manning bill wrote:
> to see if the trend has changed (modulo PAFs observations that not all TXT == SPF).   In the mean time, declare a suspension of
> last call to gauge if the presumption of failure of the SPF RR merits this drastic action.

I think this would have been a fair request for the LC of RFC 6686,
which was presenting data about the state of the world at the time.
We had a heck of a time getting people to review that document, to
provide data, or to analyse the data.  I think it's unfair to the WG
to have refused to pitch in, and now to tell the WG that it has to sit
on its hands and then do some more work later, particularly because
these two data sets are hardly representative ones.  If we're going to
undertake a large scale data gathering experiment, I'll be all for it
as soon as we have some really large mail system operators involved.
(We did have those in SPFBIS, please note.)

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Jelte.Jansen@sidn.nl  Wed Aug 21 07:03:33 2013
Return-Path: <Jelte.Jansen@sidn.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 15AB021F92B9 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:03:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.715
X-Spam-Level: 
X-Spam-Status: No, score=-0.715 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYvWPSEp2ZlY for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:03:28 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 55F5F21F93BF for <ietf@ietf.org>; Wed, 21 Aug 2013 07:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=oRfvkrrFOUg55HVrNQ86HUsOsUBIYRqiCo8KWhAH9SI=; b=YaewqsZp1tXCbcHWPwEJZmvidD46YncjpQ/6rRWVV0NS5pQjnjNOUjX+iJzSSddMcwG+E5GdueDl6ns1pBsdsTFlihTkfxsRsAT8k8qMjQ3VnMMnTyZu2DpdxYSKdKZzBpApd11BWueyShXfifp/HrU1iV8ZXndVTF9LKqi+uTs=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by ede1-kamx.sidn.nl  with ESMTP id r7LE3I0p013145-r7LE3I0r013145 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Wed, 21 Aug 2013 16:03:18 +0200
Received: from [94.198.152.217] (94.198.152.217) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 21 Aug 2013 16:03:18 +0200
Message-ID: <5214C8A6.9020609@sidn.nl>
Date: Wed, 21 Aug 2013 16:03:18 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <E9C96A4F-36CA-47E4-B2DF-4BFDD7EC277D@isi.edu> <20130821134426.GB27579@mx1.yitter.info>
In-Reply-To: <20130821134426.GB27579@mx1.yitter.info>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [94.198.152.217]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 14:03:33 -0000

On 08/21/2013 03:44 PM, Andrew Sullivan wrote:
> Speaking as the SPFBIS co-chairâ€¦
> 
> On Wed, Aug 21, 2013 at 04:55:33AM -0700, manning bill wrote:
>> to see if the trend has changed (modulo PAFs observations that not all TXT == SPF).   In the mean time, declare a suspension of
>> last call to gauge if the presumption of failure of the SPF RR merits this drastic action.
> 
> I think this would have been a fair request for the LC of RFC 6686,
> which was presenting data about the state of the world at the time.
> We had a heck of a time getting people to review that document, to
> provide data, or to analyse the data.  I think it's unfair to the WG
> to have refused to pitch in, and now to tell the WG that it has to sit
> on its hands and then do some more work later, particularly because
> these two data sets are hardly representative ones.  If we're going to
> undertake a large scale data gathering experiment, I'll be all for it
> as soon as we have some really large mail system operators involved.
> (We did have those in SPFBIS, please note.)
> 

Just wondering, could OARC's recent DITL data help? (perhaps if only to
see whether another large-scale targeted effort is needed)

I definitely see TYPE=99 queries on our servers, but I can't see the
answers.

Jelte


From vesely@tana.it  Wed Aug 21 07:14:10 2013
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1FC711E83C6 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:14:10 -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 4a5Cj5obkBIj for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:14:06 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id C605711E821C for <ietf@ietf.org>; Wed, 21 Aug 2013 07:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1377094443; bh=SIaC7/iPbDA1StpwGLIFBW3OLPyX1mTg2tMGrTxtMbM=; l=737; h=Date:From:To:References:In-Reply-To; b=kSnC4GwhfFbvOJdhDRN1c499JsyLzNO0BS5u/zeNvJEOQU8jcmyAQePEmgF8OQ2Ow 6rkHZ15oFi/9uhbXoLuJ3Dfq6YGowRVVr9ffOWblsixUXr/vAKfj+JPoR22mgX6keb oNjGrQG0N/3V5OrXfgfN4a0Iyxt69Bqv39wr0W6E=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [192.168.43.171] (ge-19-118-234.service.infuturo.it [151.19.118.234]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Wed, 21 Aug 2013 16:13:57 +0200 id 00000000005DC047.000000005214CB26.0000078D
Message-ID: <5214CAFC.6050001@tana.it>
Date: Wed, 21 Aug 2013 16:13:16 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819225810.63086.qmail@joyce.lan> <5FF26B6A-7A6C-45FE-BF93-8EB17851159D@virtualized.org> <m2siy56j0s.wl%randy@psg.com> <E4FC3784-EA30-4927-A1D2-62B12E15196F@virtualized.org>
In-Reply-To: <E4FC3784-EA30-4927-A1D2-62B12E15196F@virtualized.org>
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, 21 Aug 2013 14:14:11 -0000

On Tue 20/Aug/2013 07:27:12 +0200 David Conrad wrote:
> On Aug 19, 2013, at 10:14 PM, Randy Bush <randy@psg.com> wrote:
>>
>> one lesson i might take from this is, if i want to deploy a new
>> hack which needs an rrtype, not to use txt in the interim.

Nor the same format, IMHO.

> My personal belief is that the rationale to migrate away from TXT
> remains valid and the appropriate course of action is to fix the 
> migration strategy, not permanently encode what everyone agrees is a 
> hack into a proposed standard.

Normally, it's easier to have new births than to revive dead horses.

The proposed standard is what currently works.  By the time DKIM keys
are transmitted in binary, SPF will have a better spec too.


From paf@frobbit.se  Wed Aug 21 07:17:27 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0551011E8217 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxmE2z4cfxmV for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:17:26 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id A2F2811E8224 for <ietf@ietf.org>; Wed, 21 Aug 2013 07:17:23 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::12] (unknown [IPv6:2a02:80:3ffc::12]) by mail.frobbit.se (Postfix) with ESMTPA id 816E223FC2; Wed, 21 Aug 2013 16:17:22 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_A9A40862-CAD2-4FF8-BF17-16622195A783"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <5214A593.8030907@cisco.com>
Date: Wed, 21 Aug 2013 16:17:21 +0200
Message-Id: <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 14:17:27 -0000

--Apple-Mail=_A9A40862-CAD2-4FF8-BF17-16622195A783
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

My conclusion is that a statement that nobody queries for it is false.

   Patrik

On 21 aug 2013, at 13:33, Eliot Lear <lear@cisco.com> wrote:

> So your point is that their conclusions that nobody has the record
> installed is false?
>=20
> Eliot
>=20
> On 8/21/13 12:42 PM, Patrik F=E4ltstr=F6m wrote:
>> On 21 aug 2013, at 12:26, Eliot Lear <lear@cisco.com> wrote:
>>=20
>>> The easy part was supposed to be people actually using the SPF =
record, once it was out there.  And so your data doesn't indicate what =
sort of answers you're getting.
>> These are logs on one of my authoritative servers, and the queries =
you see are the queries sent _TO_ the server. So of course I also have =
the responses I give to the one those queries.
>>=20
>>   Patrik
>>=20
>=20


--Apple-Mail=_A9A40862-CAD2-4FF8-BF17-16622195A783
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlIUy/IACgkQrMabGguI182i8QCfRCNRrsPT5P6NBs5vgIQnsh1a
R60AniGr58uWvBeJRlzckcV5u69WD6lH
=eZqe
-----END PGP SIGNATURE-----

--Apple-Mail=_A9A40862-CAD2-4FF8-BF17-16622195A783--

From arturo.servin@gmail.com  Wed Aug 21 07:28:22 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F57721F9B97 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:28:22 -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 FkuqlouoxnZO for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 07:28:22 -0700 (PDT)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C915B21F9B80 for <ietf@ietf.org>; Wed, 21 Aug 2013 07:28:21 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id kw10so312867vcb.29 for <ietf@ietf.org>; Wed, 21 Aug 2013 07:28:20 -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=V0EuK/lBymNrGtfz0qlV/5LU9I/NfLpa/1EbNV2FH0M=; b=vFk3/qinGPIMerp09+o/EM1aqWPasjimdrfO0azOz7B1G1rKtrgtuja+CA+TvoLK7S mLsA2xSuVo2SEPEkAXYbOE8v7fGYMu4VVdP93BDOcf73PlyytTPP7EfxMYakFvOWwL0W GPE00JQjrY5GyUUtuRGoqY78dWAQKZ8D7kgfkIvqaLxA1M3LbbzwC4/F6ic/UMaGB44W qMct6L0zE8Vh22QLDszFK/7L+LfZXZE6GvJpSoujIWN1i01MDRCk4vco/7Q96DIqmpbk uj4UtHkeLlvFHgwAZBwLr2h/2bQv7u3c1LrAyX/fPrtEnoHYDzQ223VAtAhdqLmYjcD9 v/8A==
X-Received: by 10.58.207.103 with SMTP id lv7mr315813vec.33.1377095300276; Wed, 21 Aug 2013 07:28:20 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:d06a:9ea1:cd0a:5769]) by mx.google.com with ESMTPSA id zq8sm1484847vdb.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 21 Aug 2013 07:28:19 -0700 (PDT)
Message-ID: <5214CE81.4060404@gmail.com>
Date: Wed, 21 Aug 2013 11:28:17 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WG overview - MILE video
References: <F5063677821E3B4F81ACFB7905573F24E36596FE@MX15A.corp.emc.com>
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24E36596FE@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 14:28:22 -0000

Kathleen,

	Great idea, great job!

	Congratulations.

Best regards,
as
	

On 8/21/13 10:16 AM, Moriarty, Kathleen wrote:
> Hello,
> 
> Sometime before Berlin, I had suggested the use of a video to provide an overview of current work within a working group to see if that might be a useful tool.  It was suggested, on this list, I should do this for MILE and see how it works out.  While in Berlin, with the help of the fabulous MeetEcho team, we made a brief video and t is now posted as a link within the MILE charter.  I'd like to collect feedback to see how useful it is and some may be anecdotal from lurkers who now better understand the work or maybe we'll see an increase in participation.
> 
> http://datatracker.ietf.org/wg/mile/charter/
> 
> Thank you,
> Kathleen
> 

From owen@delong.com  Tue Aug 20 17:16:10 2013
Return-Path: <owen@delong.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7F511E815B; Tue, 20 Aug 2013 17:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.683
X-Spam-Level: 
X-Spam-Status: No, score=-1.683 tagged_above=-999 required=5 tests=[AWL=0.316,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-Hw+dWrKRNc; Tue, 20 Aug 2013 17:16:06 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA8911E8338; Tue, 20 Aug 2013 17:15:58 -0700 (PDT)
Received: from [10.255.251.216] (kiwi.he.net [216.218.252.66]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r7L0Dlnd025614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 20 Aug 2013 17:13:48 -0700
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r7L0Dlnd025614
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1377044028; bh=0X8dCqygwxFcYjpjKbFRr1j2WKI=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=Jqua9WepWcWH5E9dLUQPUH5ERShnvhESJOP8h3Tuj0Z16BM886+G0qXs6qR0bDZ0r B45B5Op+V8mviTNPE1HuP8E2eYw0X/eJg709PRUwmDrezWPg5M1y1Ua0Sv5rN/WNyM QNrKrtFfI61ywtxZrTHzKu7Dfd1c/qSbiW2TYpfk=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
From: Owen DeLong <owen@delong.com>
In-Reply-To: <A4B538DE-16B9-45D4-89F3-51441984B12F@apple.com>
Date: Tue, 20 Aug 2013 17:13:47 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E52BC6E6-DB55-49A5-B3AA-6D57451676ED@delong.com>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com> <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com> <A4B538DE-16B9-45D4-89F3-51441984B12F@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1508)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Tue, 20 Aug 2013 17:13:48 -0700 (PDT)
X-Mailman-Approved-At: Wed, 21 Aug 2013 08:05:38 -0700
Cc: v6ops@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 00:16:10 -0000

I also agree with James and Lorenzo.

Owen

On Aug 20, 2013, at 4:58 PM, james woodyatt <jhw@apple.com> wrote:

> On Aug 20, 2013, at 02:39 , Lorenzo Colitti <lorenzo@google.com> =
wrote:
>>=20
>> [...] It seems to me that the sheer length of the list, and the fact =
that is not prioritized, create a real risk that implementors will =
simply write it off as wishful thinking or even shy away in terror. =
[...]
>=20
> My views on the technical merits of this draft remain unchanged from =
the last time I offered them here, and I am basically in agreement with =
Lorenzo.  This draft seems unnecessary to me.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> core os networking
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From touch@isi.edu  Wed Aug 21 08:14:22 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E6C11E8234 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SssGGd3tG-zO for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:14:16 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8005211E8112 for <ietf@ietf.org>; Wed, 21 Aug 2013 08:14:16 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7LFCvMh024420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 08:13:06 -0700 (PDT)
Message-ID: <5214D8E7.50002@isi.edu>
Date: Wed, 21 Aug 2013 08:12:39 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com>
In-Reply-To: <52147135.9060705@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 15:14:22 -0000

On 8/21/2013 12:50 AM, Martin Sustrik wrote:
> On 20/08/13 17:01, Joe Touch wrote:
>
>> However, see my other message - it's hard to recommend an approach when
>> we don't understand the problem you're trying to solve.
>
> The scenario is simple.
>
> You want admin to open one port in the firewall when the project is
> started. Going through the corporate process at this point is bearable
> and makes sense.
>
> Afterwards, you want to be able to expose arbitrary services through
> that port without having to go through port-opening process over and
> over again.

There's nothing new about multiplexing services over a single port; it's 
a known problem with a few common solutions:
	- dispatch the connections inside your system based on
	in-band info
	- initiate connections inside a handler, and transfer them
	to spawned subprocesses
	- use initial connections to exchange inband info for other
	connections on dynamic ports (as done in FTP)

They each have their challenges.

> The services are actually different aspects of the same distributed
> application, say, data distribution service, management service,
> heartbeating service etc. so not requiring additional process for adding
> them makes sense.

Each distinct, independently-useable service may warrant a new port or 
could all be muxed together. Which of these you seek is up to you. 
That's a design decision.

> The real problem here IMO is how to distinguish between "adding a
> completely new application" -- which should require approval process --
> and "adding a new component within an existing distributed application"
> -- which should be managed by devs themselves.

IMO it's easy - any group of services you want others to be able to use 
independently could justify a new port, but you can always mux them all 
together if you want to avoid additional firewall configuration issues.

I.e., this is your call. But it doesn't appear to have anything to do 
with the notion of a single port to access any *existing* service, which 
is what TCPMUX and its descendants does.

Joe

From touch@isi.edu  Wed Aug 21 08:16:40 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67ABA11E83C9 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFmQF3UWoSl0 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:16:34 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACB711E83C7 for <ietf@ietf.org>; Wed, 21 Aug 2013 08:16:31 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7LFFdrp025015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 08:15:48 -0700 (PDT)
Message-ID: <5214D99E.3000504@isi.edu>
Date: Wed, 21 Aug 2013 08:15:42 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com>
In-Reply-To: <52147135.9060705@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 15:16:40 -0000

On 8/21/2013 12:50 AM, Martin Sustrik wrote:
...
> You want admin to open one port in the firewall when the project is
> started. Going through the corporate process at this point is bearable
> and makes sense.
>
> Afterwards, you want to be able to expose arbitrary services through
> that port without having to go through port-opening process over and
> over again.

One additional point - if you really mean "arbitrary", including 
existing services, I hope you understand that a network operator that 
shuts down ANY current services would conclude they must then block 
yours too.

I.e., if I don't want FTP over the firewall (because it uses cleartext 
passwords), I definitely don't want TCPMUX (which allows FTP), or any 
other "accesses arbitrary services" port.

So that seems like a non-starter, unless by "arbitrary" you mean 
"extensions within your system" - which is how all current ports already 
work.

Joe

From sustrik@250bpm.com  Wed Aug 21 08:31:42 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91AC511E821E for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xw+nYo4K4dcZ for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 08:31:34 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7027011E8112 for <ietf@ietf.org>; Wed, 21 Aug 2013 08:31:34 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id 3A43D1803548; Wed, 21 Aug 2013 17:31:33 +0200 (CEST)
Message-ID: <5214DD54.60009@250bpm.com>
Date: Wed, 21 Aug 2013 17:31:32 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com> <5214D8E7.50002@isi.edu>
In-Reply-To: <5214D8E7.50002@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 15:31:43 -0000

On 21/08/13 17:12, Joe Touch wrote:

>> The real problem here IMO is how to distinguish between "adding a
>> completely new application" -- which should require approval process --
>> and "adding a new component within an existing distributed application"
>> -- which should be managed by devs themselves.
>
> IMO it's easy - any group of services you want others to be able to use
> independently could justify a new port, but you can always mux them all
> together if you want to avoid additional firewall configuration issues.

So what would you use for muxing, if TCPMUX is not a good idea?

> I.e., this is your call. But it doesn't appear to have anything to do
> with the notion of a single port to access any *existing* service, which
> is what TCPMUX and its descendants does.

Martin


From Ted.Lemon@nominum.com  Wed Aug 21 09:23:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B11E11E8110 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.437
X-Spam-Level: 
X-Spam-Status: No, score=-106.437 tagged_above=-999 required=5 tests=[AWL=-0.138, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 rMoAR06lBwXq for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:22:52 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id 4624511E8112 for <ietf@ietf.org>; Wed, 21 Aug 2013 09:22:52 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUhTpW6kqA31AqKrhSAP2wsIl6s3UpLcP@postini.com; Wed, 21 Aug 2013 09:22:52 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AE1C61B82AD for <ietf@ietf.org>; Wed, 21 Aug 2013 09:22:51 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 174F019006E; Wed, 21 Aug 2013 09:22:51 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Wed, 21 Aug 2013 09:22:51 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: =?Windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Thread-Topic: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Thread-Index: AQHOneqwiRHwqjkl/E2l9OdgBMkwq5mff1gAgAA3SoCAADGQgIAAAzeAgAAEfYCAAA4tgIAALbyAgAAjDoA=
Date: Wed, 21 Aug 2013 16:22:50 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077525FC8E@mbx-01.win.nominum.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>
In-Reply-To: <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <B988836A0E47D44EAFA2BCCFDD0FDB0A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 16:23:02 -0000

On Aug 21, 2013, at 7:17 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote:
> My conclusion is that a statement that nobody queries for it is false.

I am curious if the folks who did the analysis of query rates know the answ=
ers to the following questions:

1. Per unit of mail delivered (as opposed to per domain), for what percenta=
ge of delivered mail for which SPF TXT records exist do SPF RRtype records =
_also_ exist?   I wasn't clear on whether an attempt was made to come up wi=
th an answer to this question.

2. Per unit of mail received, for what percentage of received mail does the=
 receiver currently issue SPF RRtype queries.

The reason I ask these questions is that the rationale for the decision mad=
e by the working group was that the data supported it, and I think that was=
 a good rationale, but only if the data _actually_ supports it.   But I don=
't think that the data was analyzed on the basis of units of mail delivered=
, but rather on the basis of number of queries seen.

The reason I think the distinction is important is that as several people h=
ave observed, there are some heavy hitters in this discussion=97Yahoo and G=
oogle, for example.   If the heavy hitters  all already publish the SPF RRt=
ype, that might make a difference.

Actually, I just checked.   Right now, none of them seem to publish SPF RRt=
ype records.   Yahoo doesn't even publish a TXT record containing SPF infor=
mation.   An argument could be made that if we really wanted to push the ad=
option of SPF RRtypes, getting Google, Yahoo and Hotmail to publish SPF RRt=
ype records would actually make it worthwhile to query SPF first, because m=
ost queries probably go to those domains.

I think the people who are pushing for a different outcome than the spfbis =
working group arrived at would do a lot to make their case if they could us=
e their collective influence to get these three domain owners to publish SP=
F RRtype records.   This is a really easy thing to do; if it can't be done,=
 that's a pretty clear indication that the SPF RRtype is doomed.


From scott@kitterman.com  Wed Aug 21 09:54:36 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3269E11E8123 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:54:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rzFVYbwW5xK for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 09:54:17 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id B9CDD21F9BC3 for <ietf@ietf.org>; Wed, 21 Aug 2013 09:54:15 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 2DADC20E40FD; Wed, 21 Aug 2013 12:54:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377104053; bh=vpHZgcx1YgzsgWHNbkjkyidz5z6R/IhDnRLy4nBGiBI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Jck746uYn+cMNFx/USjWyVdPXka/Qzk3YZMY4XMQkM7xE6yDy/tRLpV1Q1FHC+oE/ FdWekUFgnEkXT0UqkA6VXlHzUSay3HpH1gq9r7AUDG+4ziChmvB6jxhXPBigJzKrej 4S8Zmdq/iYMDGmQJoNCvqD0w1NVm41bkF2B7BvGE=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id DB3E520E40C2;  Wed, 21 Aug 2013 12:54:12 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 21 Aug 2013 12:54:11 -0400
Message-ID: <2298307.uzZxXYiUrK@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821133928.GA27579@crankycanuck.ca>
References: <20130819150521.GB21088@besserwisser.org> <521495EB.7060207@cisco.com> <20130821133928.GA27579@crankycanuck.ca>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 16:54:37 -0000

On Wednesday, August 21, 2013 09:39:28 Andrew Sullivan wrote:
...
> >   * To what extent has that happened?
> 
> I'm not the shepherd, but it is undeniable that most current-era
> shipping DNS servers support RRTYPE 99.

The operational issues I've encountered with actually trying to use RRTYPE99 
in the wild weren't caused by a lack of support in current-era shipping DNS 
servers.  Sometimes it's not even anything directly related to the DNS.  I 
recall cases where it appeared that firewalls were the root of the problem (I 
don't recall details, sorry).  Solving the DNS servers must support unknown 
RRTYPE/SPF type problem only gets you started.

Scott K

From touch@isi.edu  Wed Aug 21 10:01:56 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFE8311E8264 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVM9Q8q0KMHA for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:01:50 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id EBF3B11E8106 for <ietf@ietf.org>; Wed, 21 Aug 2013 10:01:49 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7LH0Sc6015877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 10:00:37 -0700 (PDT)
Message-ID: <5214F219.6000506@isi.edu>
Date: Wed, 21 Aug 2013 10:00:09 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com> <5214D8E7.50002@isi.edu> <5214DD54.60009@250bpm.com>
In-Reply-To: <5214DD54.60009@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:01:56 -0000

On 8/21/2013 8:31 AM, Martin Sustrik wrote:
> On 21/08/13 17:12, Joe Touch wrote:
>
>>> The real problem here IMO is how to distinguish between "adding a
>>> completely new application" -- which should require approval process --
>>> and "adding a new component within an existing distributed application"
>>> -- which should be managed by devs themselves.
>>
>> IMO it's easy - any group of services you want others to be able to use
>> independently could justify a new port, but you can always mux them all
>> together if you want to avoid additional firewall configuration issues.
>
> So what would you use for muxing, if TCPMUX is not a good idea?

You need to roll your own. The requirements of systems vary widely, as 
do the costs/benefits of different approaches.

I listed a few before, but here's a more comprehensive list:
	- service per message
		demux based on message ID
		use IPC (interprocess comm) to handoff internal
		to your system

	- service per connection
		demux based on the first message in an
		association (TCP or UDP), and either continue to
		forward messages to a different process or handoff
		the connection

	- subservice on different ports
		determine what subservice you want to initiate,
		start it on an ephemeral port, and indicate the
		port number in-band (e.g., as with FTP and others)

Given you want to keep things on a single port, the first two are 
probably more useful.

Joe

From scott@kitterman.com  Wed Aug 21 10:03:20 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BABB11E8234 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T5OFgwqsVWUI for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:03:15 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id CEA7011E8261 for <ietf@ietf.org>; Wed, 21 Aug 2013 10:02:42 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 9625F20E40FD; Wed, 21 Aug 2013 13:02:34 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377104554; bh=GcWrSpVK6erHJw9dpjBsB//k6ggIbktwXjh5P1XscM0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jDJwYrYOwhudPbJwO32hP4JWuVAE52iObz7XnB2K27FWTNMaBPxB9d4WB9/Ef+4Gn vwwxrLICLZYRmX/asFhFIuavlsdqdPm9o7RjwTGg5jixDcDGKC8MgB+huKdoruLi/C p/DjfPDJPCtzoSbCTYbrimzvT8owmItcXycvmTRI=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 7FCC520E40C2;  Wed, 21 Aug 2013 13:02:34 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 21 Aug 2013 13:02:33 -0400
Message-ID: <7917527.VmCQD3a6Q3@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821133233.D0A6B38BE02F@drugs.dv.isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:03:20 -0000

On Wednesday, August 21, 2013 23:32:33 Mark Andrews wrote:
> I object to the removal of the SPF record.

This is not a shock.  You were in the rough when we discussed it in the WG 
too.

> Name servers already have access controls down to the granuality
> of TYPE.  If this draft proceeds as currently described it is forcing
> name server vendors to access controls at the sub TYPE granuality.

It's primarily an issue for applications.  To the DNS, it's exactly what it 
is, a TXT record.

> With SPF lookup first I can specify the SPF policy using SPF and
> leave TXT free for other uses without having to worry about the
> records being misinterpeted.

Unless you have some specific reason to be concerned about accidentally 
starting an unrelated TXT record with "v=spf1 ", I can't imagine you don't 
have more important things to worry about.  This being a "problem" is a great 
theory, but it just doesn't happen in practice.

> SPF validators MUST NOT proceed to a TXT lookup on SERVFAIL for SPF.
> This is similar to not proceeding to A/AAAA lookups on MX lookup
> failures.

Except that it's quite common for a SERVFAIL on TYPESPF to occur for a domain 
that has an actual SPF record due to various operational issues.  SERVFAIL on 
type SPF doesn't reliably tell you anything about what a type TXT lookup would 
produce.  So it's similar, but only superficially so.

> I would also suggest that there be a sunset date published for the
> use of TXT for SPF.

Do you also suggest creation of an Internet police force to enforce this?  
What would be be mandatory minimum sentence?

Scott K

From hsantos@isdg.net  Wed Aug 21 10:20:57 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DAA711E8395 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:20:57 -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.432, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9yttyQai8dBs for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:20:51 -0700 (PDT)
Received: from secure.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E104F11E8120 for <ietf@ietf.org>; Wed, 21 Aug 2013 10:20:50 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1838; t=1377105637; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=7Qaua16BKR2/0OTOLbI4+v5gmno=; b=AtwG9oqTeoPyZwdI1clo 0ih0fRZkU5eoIcy9b4t8n1AFwOYhzydc6wr43F7yT8CUBGtqfC9YCps9lH7Ky7nB KRPVIn1Ss/bCYjblU9L3102DLmQol9NUeOJb8p16EUdPBc78U2QhFCLhaFGkJU2Y 34Ovc7nhdrZkPvqnzdd3C8w=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 21 Aug 2013 13:20:37 -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 3568152650.840.2456; Wed, 21 Aug 2013 13:20:36 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1838; t=1377105324; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=QWdmF5L F7PaJq8rgfZaHjq5jFWkKf7XOMiDbbWhGDAk=; b=mdKF4X9f0ZNgn8e2Y/urisQ v7eEzfdrR+G7/f51yDWTnpsxr1jeqGSpsuwy/ujlA7OWCsZZtGrn2iy68uAOGXZV clD5radN1nDXqX9PcFPLHjsuRGam0j4K1bvM7psurjRehjAUBUiul7inzj/JZqEW tTU8duyUOrZpfSxJD18Q=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 21 Aug 2013 13:15:24 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3014571877.9.7380; Wed, 21 Aug 2013 13:15:23 -0400
Message-ID: <5214F6D7.9080703@isdg.net>
Date: Wed, 21 Aug 2013 13:20:23 -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: Eliot Lear <lear@cisco.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com>
In-Reply-To: <521495EB.7060207@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:20:57 -0000

Eliot Lear wrote:
> Patrik,
> 
> First, I appreciate that you and Dave are bringing data to the table. 
> However, in this case, it is not in dispute that queries are happening. 
> What *is* in dispute is whether there are answers.  I must admit I am
> having a difficult time understanding the logic, even so.  The *hard*
> part about this was supposed to be implementation of the record in the
> application software.  Can the shepherd answer this question:
> 
>   * To what extent has that happened?
> 
> The easy part was supposed to be people actually using the SPF record,
> once it was out there.  And so your data doesn't indicate what sort of
> answers you're getting.

Eliot, we will add SPF type support in our implementation once the 
infrastructure is ready. For us, as a windows shop, namely Microsoft 
DNS servers.

So the better question I believe would be:

     If the DNS servers begin to support RFC 3597, would you add
     or enable SPF type99 support?  Would you support new RR types
     based on this support presumption?

Of course, the existing base would be low or marginal simply because 
for optimization and lower overhead reasons, it was not added or 
disabled in existing packages.

But I believe the interest was and still is there to support in 
general new RR types once the infrastructure is ready, especially in 
the DNS community.  The question to ask is if it is reasonable to 
believe DNS servers will be improved to support this industry desire 
or need.  If not, then its reasonable to remove SPF type in RFC 
4408bis, and for that matter, forget about all future new RR type 
proposals.  TXT will be the fast entry record of choice.  All recent 
mail related DNS protocols have been TXT, including the new DMARC and 
I don't see that changing (the same folks are producing them).

--
HLS



From sm@elandsys.com  Wed Aug 21 10:32:04 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29CDD11E825A for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FV+Denl9PrFG for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:32: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 1014211E8245 for <ietf@ietf.org>; Wed, 21 Aug 2013 10:31:53 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.232.108]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7LHVPme017687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 10:31:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377106301; bh=qNMvrE18iKEZgzSzoVq3kfgJy1+pZLN8v2iRTDurgNY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FX0eRYNMYM2hUS/5OqlrufsCsVn3cIYwSgkORrUEfvpbB0ZRrJA0B7MQfIBJfDr/v uGNfIjGHpJBbM5wZWevmoW91qBaiwgEN6vOAQ8wnFLm/IJDzA11VGoYBQ/q+N/JyTa kgh/kW2fPvunuSPm/NvFLF236qmt32qdkeEXAUsk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377106301; i=@elandsys.com; bh=qNMvrE18iKEZgzSzoVq3kfgJy1+pZLN8v2iRTDurgNY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qzmHhis/b3FrU8BNKPVI0JNU0RkWZY2cHJ8M+2rvUyaG+b+5ocEshf65neAeZj+dH 4MG5n0hwzfVg8WYTy97CXqanNQd5hGKIif0NEKB2XbG6zfSKy+Lm6KE2IK2yoGyp4S zEVkFztFX83vqMyiHRCIttu5f8LiDl2AmRv6WMzA=
Message-Id: <6.2.5.6.2.20130821084147.0bd3fd88@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Aug 2013 10:04:15 -0700
To: manning bill <bmanning@isi.edu>, Jelte Jansen <jelte.jansen@sidn.nl>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <E9C96A4F-36CA-47E4-B2DF-4BFDD7EC277D@isi.edu>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <E9C96A4F-36CA-47E4-B2DF-4BFDD7EC277D@isi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:32:04 -0000

At 04:55 21-08-2013, manning bill wrote:
>regarding adoption=85  it would be interesting to=20
>take a second snapshot from each of these servers in about six months
>to see if the trend has changed (modulo PAFs=20
>observations that not all TXT =3D=3D SPF).   In the=20
>mean time, declare a suspension of
>last call to gauge if the presumption of failure=20
>of the SPF RR merits this drastic action.

The IETF chartered the SPFBIS WG to deliver:

   (i)   A document describing the SPF/Sender-ID experiment and its
         conclusions to the IESG for publication.

   (ii)  A standards track document defining SPF, based on RFC4408
         and as amended above, to the IESG for publication.

There is a message from the Responsible Area=20
Director (=20
http://www.ietf.org/mail-archive/web/spfbis/current/msg00331.html=20
) and the SPFBIS Chairs (=20
http://www.ietf.org/mail-archive/web/spfbis/current/msg00355.html=20
) about (i).  The SPFBIS  WG was asked to make a=20
good-faith effort and that is what the working group did.

The editor of RFC 6686 did a good job.  The IESG=20
approved the publication of the draft.  The=20
working group worked on its second deliverable=20
(ii) after that.  There wasn't any concern about=20
the TXT RR as the matter was considered as=20
resolved in RFC 6686.  I asked DNSEXT about the=20
SPF RRTYPE in the (IANA) DNS Parameters registry=20
(=20
http://www.ietf.org/mail-archive/web/spfbis/current/msg03412.html=20
).  It generated long threads on several IETF=20
mailing lists.  It was unusual to have that=20
amount of comments after the end of a WGLC.

Suspending the Last Call for six months is a=20
drastic action.  I would ask the Responsible Area=20
Director to consider that if the SPFBIS WG did=20
not make a good-faith effort or if there is an=20
issue with the process that was followed.  My=20
opinion is that the SPFBIS WG made a good-faith=20
effort.  There are at least three Area Directors=20
reading the SPFBIS mailing list.  They did not flag any process-related=
 issue.

At 07:03 21-08-2013, Jelte Jansen wrote:
>Just wondering, could OARC's recent DITL data help? (perhaps if only to
>see whether another large-scale targeted effort is needed)

Yes.  Someone also has to do the work.

Regards,
S. Moonesamy (as document shepherd) =20


From dhc@dcrocker.net  Wed Aug 21 10:32:17 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6757E21F9A17 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.384
X-Spam-Level: 
X-Spam-Status: No, score=-6.384 tagged_above=-999 required=5 tests=[AWL=-0.085, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 QXmdNhkZVwbq for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:32:12 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF8A11E83C2 for <ietf@ietf.org>; Wed, 21 Aug 2013 10:32:12 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7LHW4Nu022476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 10:32:08 -0700
Message-ID: <5214F97B.2080400@dcrocker.net>
Date: Wed, 21 Aug 2013 10:31:39 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>
In-Reply-To: <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.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.0 (sbh17.songbird.com [72.52.113.66]); Wed, 21 Aug 2013 10:32:08 -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, 21 Aug 2013 17:32:17 -0000

Patrik,


On 8/21/2013 7:17 AM, Patrik Fältström wrote:
> My conclusion is that a statement that nobody queries for it is
> false.

Assuming that your conclusion is based on pragmatics and not
mathematical purity -- that is, that it is concerned with significant
operational effort, rather than a stray implementation here or there,
which counts as "noise" in any legitimate statistical analysis -- what
is the basis for your conclusion?

In other words, please explain how your objection is based on real-world
utility rather than something more abstract and detached from practical
operations.




 From your posting to the dnsext working group:

> On 8/20/2013 11:58 AM, Patrik Fältström wrote: In general I do
> believe, for example when looking at IPv6 and DNSSEC and similar
> technologies, that the lifetime of RFC 4408 is too short to
> deprecate any of the proposed records that are in use, specifically
> as RFC 4408 explicitly do allow use of both.

On its face, this sort of thinking means that, in practical terms,
nothing can ever be deprecated.

It also requires a rather willful ignorance of the essential community
operations differences between SPF and IPv6 and DNSSec.  There is
massive effort to increase use of the latter.  There is massive apathy
about the former.

That is, the metric of essentially no adoption or use is matched by no
vector of change.

So if you really insist on pursuing your objection, please find some
arguments that are anchored in relevant, real-world analytic legitimacy.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From johnl@iecc.com  Wed Aug 21 10:45:01 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4F211E8136 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:45:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.654
X-Spam-Level: 
X-Spam-Status: No, score=-102.654 tagged_above=-999 required=5 tests=[AWL=-0.211, 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 h06eHuAgzZ2V for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 10:44: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 0F70311E80FA for <ietf@ietf.org>; Wed, 21 Aug 2013 10:44:56 -0700 (PDT)
Received: (qmail 83833 invoked from network); 21 Aug 2013 17:44:54 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 21 Aug 2013 17:44: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; s=5214fc96.xn--9vv.k1308; i=johnl@user.iecc.com; bh=j5TGF71YPYJ+rKz53tojkviur97tuTA42Hk2XCE+82s=; b=LWy7HY461TO5E/Pswoc4u6n+FwhQoIWW8ZWPX6NlwuTAdF16Tx4O7PuBv6RBklGZuli4cqmWnu9+AjB2fit+aBkP+sBWNB0xXLb3+3Y26YlzUMgPDvklSl19RitRZGY8Ys7/da1MHUOUVSCXSh+fuDD6h0WomhCz1QQIcnRhLpCyxfUWLfTWyyWhfIkKnx9PfPYnxOdLhwCD9PJbJy2O6X5ecGh6HpTxOTBNvsAifAoJW7u27AHq+9i7K9twFpTO
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5214fc96.xn--9vv.k1308; olt=johnl@user.iecc.com; bh=j5TGF71YPYJ+rKz53tojkviur97tuTA42Hk2XCE+82s=; b=Xoq2lgSNOHjaLEGnqyiv3De+u5REd+GGndZ80rKTaiWBcUrGKEBS7dq3Sd2Z/cWsqbhuC6cXkSY7quHklHhqSVtXqOvBr8HRPEMn/rbW2PFYzXn7KhlXxG4ioNdplrOzbJWwfr54tauNY+UVWz4LnoK3ZTr8IHZrUNZ0aaxaQ2nfir58j4BIqOgp0Xp6ZbwGnrEhnrQS+xN2/TYSjjy9C1VBvhG2K6sZ7vEyFvqBGDFVB1HrPu/sXNVFoViGvJ4a
Date: 21 Aug 2013 17:44:32 -0000
Message-ID: <20130821174432.89957.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] there is no transitiion, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077525FC8E@mbx-01.win.nominum.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 17:45:01 -0000

>Actually, I just checked.   Right now, none of them seem to publish SPF RRtype records.
>Yahoo doesn't even publish a TXT record containing SPF information.   An argument could
>be made that if we really wanted to push the adoption of SPF RRtypes, getting Google,
>Yahoo and Hotmail to publish SPF RRtype records would actually make it worthwhile to
>query SPF first, because most queries probably go to those domains.

This would require some reason why it is worth them spending time and
money to do something that has no operational benefit whatsoever.

If they start publishing type 99, something will break, because when
you change something in large systems, something always breaks.  Some
mail systems somewhere with bugs in type 99 handling that they never
noticed will start making mail fail.  For doing that, will anyone's
mail work better?  No.  Will their DNS work better?  No.

As I have mentioned a couple of times already, even though Yahoo
doesn't publish SPF (I believe due to political issues related to the
history of Domainkeys and DKIM), they do check SPF.  They used to
check both TXT and type 99, and stopped checking type 99.  What
argumment is there to spend money to revisit and reverse that
decision?

Arguments about DNS purity, and hypothetical arguments about other TXT
records that will never exist are unlikely to be persusasive.

R's,
John

From braden@isi.edu  Wed Aug 21 11:04:07 2013
Return-Path: <braden@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 CD57311E83B4 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vsRiMcWut3zF for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:04:02 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 069FD11E83A6 for <ietf@ietf.org>; Wed, 21 Aug 2013 11:04:01 -0700 (PDT)
Received: from [128.9.160.107] (cat.isi.edu [128.9.160.107]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7LI382o027382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 11:03:08 -0700 (PDT)
Message-ID: <521500DB.9040203@isi.edu>
Date: Wed, 21 Aug 2013 11:03:07 -0700
From: Bob Braden <braden@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: wes@mti-systems.com
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com>
In-Reply-To: <520D7F0D.10905@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:04:07 -0000

On 8/15/2013 6:23 PM, Wesley Eddy wrote:
> I totally agree. In fact, in the update to the TCP roadmap [1], we 
> added TCPMUX to the section on "Historic and Undeployed Extensions", 
> though it definitely bears further discussion than is currently in the 
> roadmap. I think we should add a reference to your portnames doc to 
> explain why this should be Historic plus check a bit more to see if 
> the code that's out there is really being used or whether it's just 
> hanging out like a vestigal limb in the various inetd packages. 
Wes,

Indeed, TCPMUX is quite historic... it represents a Road Not Taken. My 
memory is a bit hazy after 30+ years,
but I think there was a serious discussion around 1979 of using strings 
instead of contact port numbers
for opening TCP connections. Here is the hazy part... I *think* that 
Chaosnet used strings, and two
well known MIT Daves introduced a proposal to adopt this mechanism for 
TCP. (Also, maybe XNS
used strings? Not sure about that...) The internet working group 
ultimately rejected the idea, I think when Jon Postel argued that 
contact ports provided greater conceptual economy.

Maybe I got this wrong, but in any case I hope that someone else who was 
in the room then will correct me. Jack? Vint? Dave?  Danny?

Bob Braden


From paf@frobbit.se  Wed Aug 21 11:13:57 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E4111E8137 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1279geHTMDCh for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:13:56 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id B435E11E812E for <ietf@ietf.org>; Wed, 21 Aug 2013 11:13:56 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) by mail.frobbit.se (Postfix) with ESMTPSA id DF8A121F96; Wed, 21 Aug 2013 20:13:54 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <5214F97B.2080400@dcrocker.net>
Date: Wed, 21 Aug 2013 20:13:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:13:57 -0000

On 21 aug 2013, at 19:31, Dave Crocker <dhc@dcrocker.net> wrote:

> Assuming that your conclusion is based on pragmatics and not
> mathematical purity -- that is, that it is concerned with significant
> operational effort, rather than a stray implementation here or there,
> which counts as "noise" in any legitimate statistical analysis -- what
> is the basis for your conclusion?

As I did show, the numbers comes directly from tcpdump on my auth DNS =
server, where I checked how many do query for TXT and SPF(*). I do not =
understand the question. What else do you want?

As a few others have said, 4408 do have an error that makes it =
impossible to use RFC 4408 for migration from TXT to SPF which was the =
original intent. I do not understand how the conclusion, given the =
number of SPF queries that is made, on how to fix the problem with RFC =
4408 is to deprecate the SPF RRtype.

And to your question on deprecation, yes, to me one do need much more =
arguments to deprecate something. Specifically when originally the =
intent was to migrate to what is now to be deprecated.

And this is why I am objecting to 4408bis to be published as an RFC.

If you had an RFC without issues that really did talk about a migration =
strategy (including having examples using SPF records and not TXT which =
one should migrate from) and still people did not migrate, then we would =
have a different discussion.

But we are not there. A proper migration strategy to SPF has not been =
published.

   Patrik

(*) I have now removed TXT version of the SPF record for frobbit.se to =
see whether the number of queries for SPF RRType go up or not.


From Ted.Lemon@nominum.com  Wed Aug 21 11:22:29 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10CE611E812C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.507
X-Spam-Level: 
X-Spam-Status: No, score=-106.507 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 DxUMWKc44mQy for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:22:22 -0700 (PDT)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id C279211E8108 for <ietf@ietf.org>; Wed, 21 Aug 2013 11:21:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUhUFGiQQ+miZq56FFoLLfH+FgD+/Fq+6@postini.com; Wed, 21 Aug 2013 11:21:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5FAFB1B82AD for <ietf@ietf.org>; Wed, 21 Aug 2013 11:21:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 14E5E19006E; Wed, 21 Aug 2013 11:21:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 21 Aug 2013 11:21:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John Levine <johnl@taugh.com>
Subject: Re: [spfbis] there is no transitiion, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
Thread-Topic: [spfbis] there is no transitiion, was Last Call: <draft-ietf-spfbis-4408bis-19.txt>
Thread-Index: AQHOnpYmNVttRC6LkE+NyfK9PIh2+JmgbpoA
Date: Wed, 21 Aug 2013 18:21:12 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307752602E4@mbx-01.win.nominum.com>
References: <20130821174432.89957.qmail@joyce.lan>
In-Reply-To: <20130821174432.89957.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0CE5266CC1A0A34C95D172172D529654@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:22:29 -0000

On Aug 21, 2013, at 10:44 AM, John Levine <johnl@taugh.com> wrote:
> This would require some reason why it is worth them spending time and
> money to do something that has no operational benefit whatsoever.

Sorry, I wasn't trying to make an argument for you to refute.   I'm saying =
that if the people who want to change the outcome of the spfbis consensus a=
re serious, this would be a good way to show that they have community suppo=
rt for their position.


From dhc@dcrocker.net  Wed Aug 21 11:30:34 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03BD21F0ED1 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:30:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.381
X-Spam-Level: 
X-Spam-Status: No, score=-6.381 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 kCLM7aO9EzuZ for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:30:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1F6E71F0ED0 for <ietf@ietf.org>; Wed, 21 Aug 2013 11:30:28 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7LIUJ4h023639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 11:30:23 -0700
Message-ID: <52150722.1070307@dcrocker.net>
Date: Wed, 21 Aug 2013 11:29:54 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>
In-Reply-To: <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.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.0 (sbh17.songbird.com [72.52.113.66]); Wed, 21 Aug 2013 11:30:23 -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, 21 Aug 2013 18:30:34 -0000

On 8/21/2013 11:13 AM, Patrik Fältström wrote:
> But we are not there. A proper migration strategy to SPF has not been published.


Oh.  Now I understand.

You are trying to impose new requirements on the original work, many 
years after the IETF approved it.

Thanks.  Very helpful.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ogud@ogud.com  Wed Aug 21 11:44:38 2013
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F06D21F9ABB for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:44: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 Qe-LNbrA-72K for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:44:33 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) by ietfa.amsl.com (Postfix) with ESMTP id 1378221F9A87 for <ietf@ietf.org>; Wed, 21 Aug 2013 11:44:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B96D6140177; Wed, 21 Aug 2013 14:44:32 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id AF8B01401E9;  Wed, 21 Aug 2013 14:44:29 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20130819214139.GB19946@mx1.yitter.info>
Date: Wed, 21 Aug 2013 14:44:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:44:38 -0000

On Aug 19, 2013, at 5:41 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> I'm not going to copy the spfbis WG list on this, because this is part
> of the IETF last call.  No hat.
>=20
> On Mon, Aug 19, 2013 at 02:04:10PM -0700, Murray S. Kucherawy wrote:
>> On Mon, Aug 19, 2013 at 1:59 PM, Dave Crocker <dhc@dcrocker.net> =
wrote:
>=20
>>> =46rom earlier exchanges about this concern, the assertion that I =
recall is
>>> that 7 years is not long enough, to determine whether a feature will =
be
>>> adopted.
>=20
>> What is the premise for seven years being "not long enough"?  And =
what does
>> constitute "long enough"?  And upon what is that last answer based?
>=20
> I have two observations about this.  First, EDNS0, which is of
> significantly greater benefit to DNS operators than the mere addition
> of an RRTYPE, took well over 10 years to get widespread adoption.
> Second, we all know where IPv6 adoption stands today, and that has
> certainly been around longer than 7 years.  So I think it _is_ fair to
> say that adoption of features in core infrastructure takes a very long
> time, and if one wants to add such features one has to be prepared to
> wait.
>=20
> But, second, I think all of that is irrelevant anyway.  The plain fact
> is that, once 4408 offered more than one way to publish a record, the
> easiest publication approach was going to prevail.  That's the
> approach that uses a TXT record.
>=20

For the record I think SPF RRtype retirement is not in the good-idea =
category, but nor is it
in the bad-idea category,  it falls in the we =
need-to-do-something-that-works.=20

Most of the recent arguments against SPF type have come down to the =
following (as far as I can tell):=20
	a) I can not add SPF RRtype  via my provisioning system into my =
DNS servers
	b) My firewall doesl not let SPF Records through=20
	c) My DNS library does not return SPF records through or does =
not understand it, thus the application can not receive it.
	d) Looking up SPF is a waste of time as they do not get through, =
thus we only look up TXT

So what I have taken from this is that the DNS infrastructure is =
agnostic to RRtype=3D99 but the=20
edges have problems.=20
As to the arguments 7 years is not long enough to reach conclusion and =
force the changes through the
infrastructure and to the edges. The "need" for SPF has been blunted by =
the "DUAL SPF/TXT" strategy and=20
thus we are basically in the place where the path of lowest-resistence =
has taken us.=20

What I want the IESG to add a note to the document is that says =
something like the following:=20
"The retirement of SPF from specification is not to be taken that new =
RRtypes can not be used by applications,=20
the retirement is consequence of the dual "quick-deploy" strategy. The =
IETF will continue to advocate application=20
specific RRtypes applications/firewalls/libraries SHOULD support that =
approach."


	Olafur



From paf@frobbit.se  Wed Aug 21 11:45:14 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B37E21F9AEF for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:45:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000,  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 4S2fHx-QRgC3 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:45:12 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 6167321F9AFE for <ietf@ietf.org>; Wed, 21 Aug 2013 11:45:04 -0700 (PDT)
Received: from [192.165.72.14] (unknown [192.165.72.14]) by mail.frobbit.se (Postfix) with ESMTPSA id 3B7F123F2B; Wed, 21 Aug 2013 20:45:03 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <52150722.1070307@dcrocker.net>
Date: Wed, 21 Aug 2013 20:45:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EEB6782-45B3-421B-899F-8B453F49197A@frobbit.se>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:45:14 -0000

On 21 aug 2013, at 20:29, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/21/2013 11:13 AM, Patrik F=E4ltstr=F6m wrote:
>> But we are not there. A proper migration strategy to SPF has not been =
published.
>=20
> Oh.  Now I understand.
>=20
> You are trying to impose new requirements on the original work, many =
years after the IETF approved it.
>=20
> Thanks.  Very helpful.

Dave, I do not appreciate the tone of your message.

I explain as part of a last call of a message to the IETF mailing list =
why I object to publication of an I-D as an RFC.

If the IESG comes to the conclusion that the document should be =
published fine. If they say it should not. Fine.

That is the IETF process.

I should have staid on the DNS mailing list as I said originally, where =
I promised people I should not discuss SPF anymore on the main IETF list =
because I knew the pushback from you and a few others would be exactly =
like this. I was convinced to give my view on SPF to the IETF list so =
that it was known correctly to the last call process. A process I have =
always trusted and believed it. And still trust and still believe in.


This is my last posting in this thread.

   Patrik


From presnick@qti.qualcomm.com  Wed Aug 21 11:48:04 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40CC21F9C91; Wed, 21 Aug 2013 11:48:04 -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.013, 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 o-IJFpPjFZaI; Wed, 21 Aug 2013 11:48:00 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 368A121F9C68; Wed, 21 Aug 2013 11:48:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377110880; x=1408646880; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=/bM+OhFCHv4uJLxCYp43sF7LwG5vfn1T7lUXXZYTsq0=; b=tBFgKUAirtgN2o0J6JfkdpZJxx36ioSpHZDVVDtYIi0OxivwbgMjILif AqzjieRyOGDW+asKkqSAYYJTi5pk6zpkv7UPy8AvOdGl/TevVtmgLWglK mf/pQkNV1DmDoGClAg8NLuE0If/9q6uLOOpE1PXEPPJfIu8DrFuYrSAy9 Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="50045704"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 21 Aug 2013 11:47:57 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="524707818"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Aug 2013 11:47:57 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Wed, 21 Aug 2013 11:47:57 -0700
Message-ID: <52150B5A.1060503@qti.qualcomm.com>
Date: Wed, 21 Aug 2013 13:47:54 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-repute-model-07
References: <02be01ce9e72$25ac43f0$7104cbd0$@gmail.com>
In-Reply-To: <02be01ce9e72$25ac43f0$7104cbd0$@gmail.com>
Content-Type: multipart/alternative; boundary="------------050508060307080700060401"
X-Originating-IP: [172.30.39.5]
Cc: draft-ietf-repute-model.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: Wed, 21 Aug 2013 18:48:05 -0000

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

As per a suggestion in another thread: Would you also say that this 
draft is ready for publication as a Proposed Standard? This is more 
architectural overview than protocol per-se, but I do think it is 
necessary to the understanding of the other protocol documents (hence it 
is a normative reference), and I think it can progress with the rest.

(I haven't seen an objection to doing so in the other Last Call thread, 
so unless there is a good reason not to, I'm inclined to re-initiate the 
Last Call for Proposed Standard instead.)

pr

On 8/21/13 8:27 AM, Roni Even wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on 
> Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments 
> you may receive.
>
> Document: draft-ietf-repute-model-07
>
> Reviewer: Roni Even
>
> Review Date:2013--8--20
>
> IETF LC End Date: 2013-8--29
>
> IESG Telechat date:
>
> Summary: This draft is ready for publication as an Informational RFC.
>
> Major issues:
>
> Minor issues:
>
> I was wondering why the "Further Discussion" section 9.3 is part of 
> the security section. I think it should be a separate section.
>
> Nits/editorial comments:
>
> Section 3 the end of 2^nd paragraph "mechansisms" to "mechanisms"
>

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


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
As per a suggestion in another thread: Would you also say that this
draft is ready for publication as a Proposed Standard? This is more
architectural overview than protocol per-se, but I do think it is
necessary to the understanding of the other protocol documents (hence
it is a normative reference), and I think it can progress with the rest.<br>
<br>
(I haven't seen an objection to doing so in the other Last Call thread,
so unless there is a good reason not to, I'm inclined to re-initiate
the Last Call for Proposed Standard instead.)<br>
<br>
pr<br>
<br>
On 8/21/13 8:27 AM, Roni Even wrote:
<blockquote cite="mid:02be01ce9e72$25ac43f0$7104cbd0$@gmail.com"
 type="cite">
  <meta http-equiv="Content-Type"
 content="text/html; charset=ISO-8859-1">
  <meta name="Generator" content="Microsoft Word 14 (filtered medium)">
  <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="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"><a moz-do-not-send="true" name="OLE_LINK1"></a><a
 moz-do-not-send="true" name="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 moz-do-not-send="true"
 href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
 target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
  <p class="MsoNormal">Please resolve these comments along with any
other Last Call comments you may receive.<o:p></o:p></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Document:
  </span><span style="font-family: &quot;Courier New&quot;;">draft-ietf-repute-model-07</span><o:p></o:p></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Reviewer:
Roni Even<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Review
Date:2013&#8211;8&#8211;20<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">IETF LC
End Date: 2013-8&#8211;29<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">IESG
Telechat date: <o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">Summary:
This draft is ready for publication as an Informational RFC</span><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;">.<o:p></o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoPlainText"><span
 style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;;"><o:p>&nbsp;</o:p></span></p>
  <p class="MsoNormal">Major issues:<o:p></o:p></p>
  <p class="MsoNormal">Minor issues:<o:p></o:p></p>
  <p class="MsoNormal">I was wondering why the &#8220;Further Discussion&#8221;
section 9.3 is part of the security section. I think it should be a
separate section.<o:p></o:p></p>
  <p class="MsoNormal">Nits/editorial comments:<o:p></o:p></p>
  <p class="MsoNormal">Section 3 the end of 2<sup>nd</sup> paragraph
&#8220;mechansisms&#8221; to &#8220;mechanisms&#8221;<span style="color: black;"><o:p></o:p></span></p>
  <p class="MsoNormal"><a moz-do-not-send="true" name="policy.abstract"></a><o:p>&nbsp;</o:p></p>
  <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
  </div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Technologies, Inc. - +1 (858)651-4478</pre>
</body>
</html>

--------------050508060307080700060401--

From scott@kitterman.com  Wed Aug 21 11:51:03 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F61721F9C53 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXSNU7j0Fu0c for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:50:56 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8228321F9CA9 for <ietf@ietf.org>; Wed, 21 Aug 2013 11:50:56 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id D3AC020E40FD; Wed, 21 Aug 2013 14:50:55 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377111055; bh=8+UdX2mBzna3UDKjW3TdiQ16RCIPgJsagAKMN39+1n0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JF23617PUI8LJt5OTTq54CG12LpfgFXnKJ+/9bLhvos63eE9Og9nQOFnY21I0VGwc BX6DvTf9+0HwEzUZaRKTRy5196XCVEH9jKzhANayjqQaqx5+/NC/l7y4ye6Ur9RRB2 K/UvAUWmnV31j7O9xAG8EWlfIeIO4Jwujryv+0nw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id BCC1C20E40C2;  Wed, 21 Aug 2013 14:50:55 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 21 Aug 2013 14:50:54 -0400
Message-ID: <2213585.EOg7LJb1ub@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819214139.GB19946@mx1.yitter.info> <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:51:03 -0000

On Wednesday, August 21, 2013 14:44:41 Olafur Gudmundsson wrote:
> On Aug 19, 2013, at 5:41 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> > I'm not going to copy the spfbis WG list on this, because this is part
> > of the IETF last call.  No hat.
> > 
> > On Mon, Aug 19, 2013 at 02:04:10PM -0700, Murray S. Kucherawy wrote:
> >> On Mon, Aug 19, 2013 at 1:59 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> >>> From earlier exchanges about this concern, the assertion that I recall
> >>> is
> >>> that 7 years is not long enough, to determine whether a feature will be
> >>> adopted.
> >> 
> >> What is the premise for seven years being "not long enough"?  And what
> >> does
> >> constitute "long enough"?  And upon what is that last answer based?
> > 
> > I have two observations about this.  First, EDNS0, which is of
> > significantly greater benefit to DNS operators than the mere addition
> > of an RRTYPE, took well over 10 years to get widespread adoption.
> > Second, we all know where IPv6 adoption stands today, and that has
> > certainly been around longer than 7 years.  So I think it _is_ fair to
> > say that adoption of features in core infrastructure takes a very long
> > time, and if one wants to add such features one has to be prepared to
> > wait.
> > 
> > But, second, I think all of that is irrelevant anyway.  The plain fact
> > is that, once 4408 offered more than one way to publish a record, the
> > easiest publication approach was going to prevail.  That's the
> > approach that uses a TXT record.
> 
> For the record I think SPF RRtype retirement is not in the good-idea
> category, but nor is it in the bad-idea category,  it falls in the we
> need-to-do-something-that-works.
> 
> Most of the recent arguments against SPF type have come down to the
> following (as far as I can tell): a) I can not add SPF RRtype  via my
> provisioning system into my DNS servers b) My firewall doesl not let SPF
> Records through
> 	c) My DNS library does not return SPF records through or does not
> understand it, thus the application can not receive it. d) Looking up SPF
> is a waste of time as they do not get through, thus we only look up TXT
> 
> So what I have taken from this is that the DNS infrastructure is agnostic to
> RRtype=99 but the edges have problems.
> As to the arguments 7 years is not long enough to reach conclusion and force
> the changes through the infrastructure and to the edges. The "need" for SPF
> has been blunted by the "DUAL SPF/TXT" strategy and thus we are basically
> in the place where the path of lowest-resistence has taken us.
> 
> What I want the IESG to add a note to the document is that says something
> like the following: "The retirement of SPF from specification is not to be
> taken that new RRtypes can not be used by applications, the retirement is
> consequence of the dual "quick-deploy" strategy. The IETF will continue to
> advocate application specific RRtypes applications/firewalls/libraries
> SHOULD support that approach."

I'm a bit unsure that continue is the right word.  DKIM moved to the TXT with 
underscore approach and, IIRC, never considered a new RRTYPE, nor did anyone 
ever suggest they should.  DMARC, which has had a BoF and for which a WG is 
being considered will do the same (there's no variant of proposed charter text 
floating around that would allow them to consider otherwise).  

I agree with that the notion of a statement that SPF is what it is for a 
variety of reasons and shouldn't be considered as a precedent for the future 
might be a reasonable thing to add.  I don't think the IETF has been very 
consistent about what one ought to do instead.

Scott K

From presnick@qti.qualcomm.com  Wed Aug 21 11:59:02 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1E6D21F9E63 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:59:02 -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 Cd9tFand5b0a for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 11:58:58 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id A600C21F9E5C for <ietf@ietf.org>; Wed, 21 Aug 2013 11:58:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377111538; x=1408647538; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=AgKTceE37xhZhD/9kIkO6h+WNo6kiTJ0AwfrNM0RHfQ=; b=PM1/Ghh0kSIviAxcL0+nhdqU+4Pkxo/8X2FTf5B1cVvLwFbUowIhANXN dkGqdvvn3TUcsYHNjYlYOYr2PFZMvsjHsV9ldqlpUEXvZdrNfEymPmv+f 0iwvtc9IXEVOBi8wYdGK+JyAQNA1G3q4ZdQ8siyNHmYCfibQO7hvBm4r7 E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="50046453"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 21 Aug 2013 11:58:58 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="524710899"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Aug 2013 11:58:58 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Wed, 21 Aug 2013 11:58:58 -0700
Message-ID: <52150DF0.6070800@qti.qualcomm.com>
Date: Wed, 21 Aug 2013 13:58:56 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <dcrocker@bbiw.net>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net>
In-Reply-To: <52150722.1070307@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6?= =?ISO-8859-1?Q?m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 18:59:02 -0000

AD hat squarely on my head.

On 8/21/13 1:29 PM, Dave Crocker wrote:

> Oh.  Now I understand.
>
> You are trying to impose new requirements on the original work, many 
> years after the IETF approved it.
>
> Thanks.  Very helpful.

That's not an appropriate response. It is certainly not helpful to me as 
the consensus caller. And it is rude.

It's perfectly reasonable to say, "This would constitute a new 
requirement and I don't think there is a good justification to pursue 
that line." The sarcasm is not reasonable.

Please stop.

pr

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


From dhc@dcrocker.net  Wed Aug 21 12:07:47 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2114011E811E; Wed, 21 Aug 2013 12:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Level: 
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071,  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 fMpuxIGZl91G; Wed, 21 Aug 2013 12:07:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF5A21F9E68; Wed, 21 Aug 2013 12:07:40 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7LJ7RLA024392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 12:07:30 -0700
Message-ID: <52150FD6.8010306@dcrocker.net>
Date: Wed, 21 Aug 2013 12:07:02 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WG Review: Secure Telephone Identity Revisited (stir)
References: <20130821175202.24713.10458.idtracker@ietfa.amsl.com>
In-Reply-To: <20130821175202.24713.10458.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 21 Aug 2013 12:07:31 -0700 (PDT)
Cc: stir WG <stir@ietf.org>, The IESG <iesg-secretary@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, 21 Aug 2013 19:07:47 -0000

The following mostly are points that I raised within the group's mailing 
list discussion, during charter development.  In my view, they have not 
yet been adequately resolved:


On 8/21/2013 10:52 AM, The IESG wrote:
>    Please send your comments to the IESG mailing list (iesg
> at ietf.org) by 2013-08-28.
...
> The STIR working group will specify Internet-based mechanisms that allow
> verification of the calling party's authorization to use a particular
> telephone number for an incoming call.

"use a particular telephone number for an incoming call" has no obvious 
and unambiguous technical meaning.  In fact, it seems to imply the 
meaning of "authorization to call a particular number".  However of 
course that's not the intended meaning.  Since this is the only text in 
this paragraph that says what the working group will /do/ it should make 
its statement with clarity and technical substance.

That is, the charter needs to use a precise term for specifying the 
specific role of the number of interest.  In earlier drafts, "caller id" 
was used.  The next sentence uses "source telephone number".  Perhaps 
that is acceptable.


> Since it has  become fairly easy
> to present an incorrect source telephone number, a growing set of
> problems have emerged over the last decade.  As with email, the claimed
> source identity of a SIP request is not verified, permitting unauthorized

As a matter of form, I'll note the SIP's community's use of "identity" 
is what is called "identifier" in the identity community.

...

> As its priority mechanism work item, the working group will specify a SIP

Reference to work priority is only meaningful in the face of a list of 
tasks that will be considered simultaneously and what it means to give 
priority to one over another.  Based on the lengthy mailing list 
discussion of in-band vs. out-of-band, it appears that the current 
charter is actually intended to support simultaneous work on alternative 
mechanisms, rather than pursuing them sequentially.

This should be made explicit.  If the requirement is to work on them 
sequentially, then state that.  If the intent is to work on both 
approaches simultaneously, then say that.

...


> In addition to its priority mechanism work item, the working group will
> consider a mechanism for verification of the originator during session
> establishment in an environment with one or more non-SIP hops, most
> likely requiring an out-of-band authorization mechanism.  However, the
> in-band and the out-of-band mechanisms should share as much in common as
> possible, especially the credentials.  The in-band mechanism must be sent
> to the IESG for approval and publication prior to the out-of-band
> mechanism.

"in-band and the out-of-band mechanisms should share as much in common 
as possible"

This is the essential text that mandates working on both approaches 
simultaneously and makes the earliet assertion about priority moot. 
(Note how far down in the charter this is buried, yet how fundamental a 
requirement is establishes.)


...

> Input to working group discussions shall include:
>

That's a lengthy list of documents.  Why has it left out other documents 
discussed during charter development and clearly of continuing interest 
to the effort, namely:

    A proposal for Caller Identity in a DNS-based Entrusted Registry
    (CIDER)
    draft-kaplan-stir-cider-00

    An Identity Key-based and Effective Signature for Origin-Unknown
    Types
    draft-kaplan-stir-ikes-out-00


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Wed Aug 21 12:17:56 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A07921F9A8C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 12:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.53
X-Spam-Level: 
X-Spam-Status: No, score=-6.53 tagged_above=-999 required=5 tests=[AWL=0.069,  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 dT5kEBT8mY0Y for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 12:17:50 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 583DC21F9950 for <ietf@ietf.org>; Wed, 21 Aug 2013 12:17:47 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7LJHhhw024672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 12:17:46 -0700
Message-ID: <5215123E.5080203@dcrocker.net>
Date: Wed, 21 Aug 2013 12:17:18 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com>
In-Reply-To: <52150DF0.6070800@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 21 Aug 2013 12:17:46 -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, 21 Aug 2013 19:17:56 -0000

On 8/21/2013 11:58 AM, Pete Resnick wrote:
> AD hat squarely on my head.
>
> On 8/21/13 1:29 PM, Dave Crocker wrote:
>
>> Oh.  Now I understand.
>>
>> You are trying to impose new requirements on the original work, many
>> years after the IETF approved it.
>>
>> Thanks.  Very helpful.
>
> That's not an appropriate response. It is certainly not helpful to me as
> the consensus caller. And it is rude.


Since you've made this a formal process point, I'll ask you to 
substantiate it carefully and also formally.  The implication of your 
assessment is that IETF participants must not comment on the utility of 
comments by others.

I don't recall that being a proscribed behavior, since it has nothing to 
do with personalities.  So, please explain this in a way that does not 
sound like Procrustean political correctness.

For the record, I entirely acknowledge that my note has an edge to it 
and yes, of course alternate wording was possible.  However the thread 
is attempting to reverse extensive and careful working group effort and 
to ignore widely deployed and essential operational realities, including 
published research data.

A bit of edge is warranted for such wasteful, distracting and 
destabilizing consumption of IETF resources.  In fact an important 
problem with the alternate wording, such as you offered, is that it 
implies a possible utility in the thread that does not exist.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From christopher.morrow@gmail.com  Wed Aug 21 12:18:24 2013
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C008021F9BD0; Wed, 21 Aug 2013 12:18:24 -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 ap2ejhNv0mDs; Wed, 21 Aug 2013 12:18:24 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id B687F21F9F3D; Wed, 21 Aug 2013 12:18:19 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id u12so691123lbd.26 for <multiple recipients>; Wed, 21 Aug 2013 12:18:18 -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:message-id:subject :from:to:cc:content-type; bh=vDOd/6qrES4yp1m05LXxJwQfPfOip0VzcJzHpI/5jAw=; b=wFn5T2wGHe2GD3NLUc8swW3FZuolcFkdUTkXKqz5o2VaWIC8f3vbNuXFyB85SQN0/e 0xGDjAKOjaeBK+dlrsfbYEj8ETUM/2cCvPSWBNkw7TIpvqPkgyHOBVKP4xf3T8E9hqXA 97T/s8q+ilDpC7gzPkng4XayfyhTeDdd/53SR4KI3Kdug52lyINT/NMy2uUg12mCIimX ePcfdUHvCSGyTN85nGWx7A34wcNDZ5+Fbz96Am/Sy/rD5rJfIRfNw9JKWmSZD75Vg6P0 1HkvwiJipjcVny2AAgFIVrqHwEBonwvkHK8xrNmk4AkfuWUdO4p6AKthdjsOCamMQ3gh 9kqg==
MIME-Version: 1.0
X-Received: by 10.112.57.49 with SMTP id f17mr8405809lbq.26.1377112698637; Wed, 21 Aug 2013 12:18:18 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.6.3 with HTTP; Wed, 21 Aug 2013 12:18:18 -0700 (PDT)
In-Reply-To: <52150FD6.8010306@dcrocker.net>
References: <20130821175202.24713.10458.idtracker@ietfa.amsl.com> <52150FD6.8010306@dcrocker.net>
Date: Wed, 21 Aug 2013 15:18:18 -0400
X-Google-Sender-Auth: NXYYWtq26JbHbgTJaot5rRuEZLE
Message-ID: <CAL9jLaaOwB4UNmrgxrEOV=03n2CkQbECR3USUd258-xu_ehiJw@mail.gmail.com>
Subject: Re: WG Review: Secure Telephone Identity Revisited (stir)
From: Christopher Morrow <morrowc.lists@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: stir WG <stir@ietf.org>, The IESG <iesg-secretary@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 19:18:24 -0000

On Wed, Aug 21, 2013 at 3:07 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> The following mostly are points that I raised within the group's mailing
> list discussion, during charter development.  In my view, they have not yet
> been adequately resolved:
>
>
> On 8/21/2013 10:52 AM, The IESG wrote:
>>
>>    Please send your comments to the IESG mailing list (iesg
>> at ietf.org) by 2013-08-28.
>
> ...
>>
>> The STIR working group will specify Internet-based mechanisms that allow
>> verification of the calling party's authorization to use a particular
>> telephone number for an incoming call.
>
>
> "use a particular telephone number for an incoming call" has no obvious and

it'd actually be kind of nice if the focus was NOT on the (us)
10-digit "number", but instead on the 'identity' making the call.
There's a real chance to move beyond the '10-digit number' and to some
stronger, wider, richer sense of 'identity'... we should take that
opportunity and run with it.

> unambiguous technical meaning.  In fact, it seems to imply the meaning of
> "authorization to call a particular number".  However of course that's not
> the intended meaning.  Since this is the only text in this paragraph that
> says what the working group will /do/ it should make its statement with
> clarity and technical substance.
>
> That is, the charter needs to use a precise term for specifying the specific
> role of the number of interest.  In earlier drafts, "caller id" was used.

s/number/identity/

> The next sentence uses "source telephone number".  Perhaps that is
> acceptable.

no... focus on 'telephone number' is broken. Hell, it's not even
what's used in the phone system anyway... not really.

>> Since it has  become fairly easy
>> to present an incorrect source telephone number, a growing set of
>> problems have emerged over the last decade.  As with email, the claimed
>> source identity of a SIP request is not verified, permitting unauthorized
>
>
> As a matter of form, I'll note the SIP's community's use of "identity" is
> what is called "identifier" in the identity community.
>
> ...
>
>> As its priority mechanism work item, the working group will specify a SIP
>
>
> Reference to work priority is only meaningful in the face of a list of tasks
> that will be considered simultaneously and what it means to give priority to
> one over another.  Based on the lengthy mailing list discussion of in-band
> vs. out-of-band, it appears that the current charter is actually intended to
> support simultaneous work on alternative mechanisms, rather than pursuing
> them sequentially.
>
> This should be made explicit.  If the requirement is to work on them
> sequentially, then state that.  If the intent is to work on both approaches
> simultaneously, then say that.
>
> ...
>
>
>> In addition to its priority mechanism work item, the working group will
>> consider a mechanism for verification of the originator during session
>> establishment in an environment with one or more non-SIP hops, most
>> likely requiring an out-of-band authorization mechanism.  However, the
>> in-band and the out-of-band mechanisms should share as much in common as
>> possible, especially the credentials.  The in-band mechanism must be sent
>> to the IESG for approval and publication prior to the out-of-band
>> mechanism.
>
>
> "in-band and the out-of-band mechanisms should share as much in common as
> possible"
>
> This is the essential text that mandates working on both approaches
> simultaneously and makes the earliet assertion about priority moot. (Note
> how far down in the charter this is buried, yet how fundamental a
> requirement is establishes.)
>
>
> ...
>
>> Input to working group discussions shall include:
>>
>
> That's a lengthy list of documents.  Why has it left out other documents
> discussed during charter development and clearly of continuing interest to
> the effort, namely:
>
>    A proposal for Caller Identity in a DNS-based Entrusted Registry
>    (CIDER)
>    draft-kaplan-stir-cider-00
>
>    An Identity Key-based and Effective Signature for Origin-Unknown
>    Types
>    draft-kaplan-stir-ikes-out-00
>
>
> d/
>
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net

From christopher.morrow@gmail.com  Wed Aug 21 12:25:30 2013
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8041B21F9FBF; Wed, 21 Aug 2013 12:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mjnt11DhmFEE; Wed, 21 Aug 2013 12:25:25 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 46F4621F9F9B; Wed, 21 Aug 2013 12:25:24 -0700 (PDT)
Received: by mail-la0-f50.google.com with SMTP id ek20so708958lab.9 for <multiple recipients>; Wed, 21 Aug 2013 12:25:20 -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:message-id:subject :from:to:cc:content-type; bh=eLfaQ8Qw2veCXkZpiocSiMBPt01SPwF59l3fETsfbsQ=; b=oQBPTXxW5ef6E0avS/HuuF5LyKr9MHJDcjFcyJTc9ZNet6jaVmL/z9oaTZIdqMcZpu np3laeXEwUnk01pETrN1OXklsbaY2Ao2cMhuDG1ReJWNQ0uIarPNYpqYVXo6QB8M7zO8 YrPZNP7QpBCrDER0ZQCvq61X3dezcNo9UefOFWPVj4zBegZXNNqOTNLI18wtov0SBraV FrigHAYJXAjj14WvoYKjLwwHWCw02i3Z9RU6zsJlHEsEpu11Fkv5TN0d9xPQrXTxnpWB rBU05lVC1Ck1IMyNlTxZ0YXAIsZEN4YOzPyUKTUv9GwtBRR2N7ptqHpL4Q0FwSI4EY9N rHTA==
MIME-Version: 1.0
X-Received: by 10.112.40.65 with SMTP id v1mr13051lbk.69.1377113120718; Wed, 21 Aug 2013 12:25:20 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.152.6.3 with HTTP; Wed, 21 Aug 2013 12:25:20 -0700 (PDT)
In-Reply-To: <CAL9jLaaOwB4UNmrgxrEOV=03n2CkQbECR3USUd258-xu_ehiJw@mail.gmail.com>
References: <20130821175202.24713.10458.idtracker@ietfa.amsl.com> <52150FD6.8010306@dcrocker.net> <CAL9jLaaOwB4UNmrgxrEOV=03n2CkQbECR3USUd258-xu_ehiJw@mail.gmail.com>
Date: Wed, 21 Aug 2013 15:25:20 -0400
X-Google-Sender-Auth: stUDZpaE4X1E-1nR0quMqttrwE8
Message-ID: <CAL9jLaZ_6w6XRPQ1G8sYC5JTPW3i3uqvaq-rx79Kta2Rwnqu_Q@mail.gmail.com>
Subject: Re: WG Review: Secure Telephone Identity Revisited (stir)
From: Christopher Morrow <morrowc.lists@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@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: Wed, 21 Aug 2013 19:25:30 -0000

+ iesg
-iesg-secretary

On Wed, Aug 21, 2013 at 3:18 PM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
> On Wed, Aug 21, 2013 at 3:07 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>> The following mostly are points that I raised within the group's mailing
>> list discussion, during charter development.  In my view, they have not yet
>> been adequately resolved:
>>
>>
>> On 8/21/2013 10:52 AM, The IESG wrote:
>>>
>>>    Please send your comments to the IESG mailing list (iesg
>>> at ietf.org) by 2013-08-28.
>>
>> ...
>>>
>>> The STIR working group will specify Internet-based mechanisms that allow
>>> verification of the calling party's authorization to use a particular
>>> telephone number for an incoming call.
>>
>>
>> "use a particular telephone number for an incoming call" has no obvious and
>
> it'd actually be kind of nice if the focus was NOT on the (us)
> 10-digit "number", but instead on the 'identity' making the call.
> There's a real chance to move beyond the '10-digit number' and to some
> stronger, wider, richer sense of 'identity'... we should take that
> opportunity and run with it.
>
>> unambiguous technical meaning.  In fact, it seems to imply the meaning of
>> "authorization to call a particular number".  However of course that's not
>> the intended meaning.  Since this is the only text in this paragraph that
>> says what the working group will /do/ it should make its statement with
>> clarity and technical substance.
>>
>> That is, the charter needs to use a precise term for specifying the specific
>> role of the number of interest.  In earlier drafts, "caller id" was used.
>
> s/number/identity/
>
>> The next sentence uses "source telephone number".  Perhaps that is
>> acceptable.
>
> no... focus on 'telephone number' is broken. Hell, it's not even
> what's used in the phone system anyway... not really.
>
>>> Since it has  become fairly easy
>>> to present an incorrect source telephone number, a growing set of
>>> problems have emerged over the last decade.  As with email, the claimed
>>> source identity of a SIP request is not verified, permitting unauthorized
>>
>>
>> As a matter of form, I'll note the SIP's community's use of "identity" is
>> what is called "identifier" in the identity community.
>>
>> ...
>>
>>> As its priority mechanism work item, the working group will specify a SIP
>>
>>
>> Reference to work priority is only meaningful in the face of a list of tasks
>> that will be considered simultaneously and what it means to give priority to
>> one over another.  Based on the lengthy mailing list discussion of in-band
>> vs. out-of-band, it appears that the current charter is actually intended to
>> support simultaneous work on alternative mechanisms, rather than pursuing
>> them sequentially.
>>
>> This should be made explicit.  If the requirement is to work on them
>> sequentially, then state that.  If the intent is to work on both approaches
>> simultaneously, then say that.
>>
>> ...
>>
>>
>>> In addition to its priority mechanism work item, the working group will
>>> consider a mechanism for verification of the originator during session
>>> establishment in an environment with one or more non-SIP hops, most
>>> likely requiring an out-of-band authorization mechanism.  However, the
>>> in-band and the out-of-band mechanisms should share as much in common as
>>> possible, especially the credentials.  The in-band mechanism must be sent
>>> to the IESG for approval and publication prior to the out-of-band
>>> mechanism.
>>
>>
>> "in-band and the out-of-band mechanisms should share as much in common as
>> possible"
>>
>> This is the essential text that mandates working on both approaches
>> simultaneously and makes the earliet assertion about priority moot. (Note
>> how far down in the charter this is buried, yet how fundamental a
>> requirement is establishes.)
>>
>>
>> ...
>>
>>> Input to working group discussions shall include:
>>>
>>
>> That's a lengthy list of documents.  Why has it left out other documents
>> discussed during charter development and clearly of continuing interest to
>> the effort, namely:
>>
>>    A proposal for Caller Identity in a DNS-based Entrusted Registry
>>    (CIDER)
>>    draft-kaplan-stir-cider-00
>>
>>    An Identity Key-based and Effective Signature for Origin-Unknown
>>    Types
>>    draft-kaplan-stir-ikes-out-00
>>
>>
>> d/
>>
>>
>> --
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net

From hadriel.kaplan@oracle.com  Wed Aug 21 12:34:47 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C796321F9F6C; Wed, 21 Aug 2013 12:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.507
X-Spam-Level: 
X-Spam-Status: No, score=-6.507 tagged_above=-999 required=5 tests=[AWL=0.092,  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 jsiQ4IlLAowa; Wed, 21 Aug 2013 12:34:41 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id CEADB21F9F5E; Wed, 21 Aug 2013 12:34:40 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7LJYcwm015410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Aug 2013 19:34:39 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7LJYc2E007930 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 19:34:38 GMT
Received: from abhmt118.oracle.com (abhmt118.oracle.com [141.146.116.70]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7LJYcrJ000955; Wed, 21 Aug 2013 19:34:38 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 21 Aug 2013 12:34:37 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: WG Review: Secure Telephone Identity Revisited (stir)
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CAL9jLaaOwB4UNmrgxrEOV=03n2CkQbECR3USUd258-xu_ehiJw@mail.gmail.com>
Date: Wed, 21 Aug 2013 15:34:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E28E51E7-6A0E-464C-847A-3ADC2250D13F@oracle.com>
References: <20130821175202.24713.10458.idtracker@ietfa.amsl.com> <52150FD6.8010306@dcrocker.net> <CAL9jLaaOwB4UNmrgxrEOV=03n2CkQbECR3USUd258-xu_ehiJw@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
Cc: stir WG <stir@ietf.org>, The IESG <iesg-secretary@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 19:34:47 -0000

On Aug 21, 2013, at 3:18 PM, Christopher Morrow =
<morrowc.lists@gmail.com> wrote:

>> "use a particular telephone number for an incoming call" has no =
obvious and
>=20
> it'd actually be kind of nice if the focus was NOT on the (us)
> 10-digit "number", but instead on the 'identity' making the call.
> There's a real chance to move beyond the '10-digit number' and to some
> stronger, wider, richer sense of 'identity'... we should take that
> opportunity and run with it.

To be clear, the focus is not on a 10-digit number nor numbers for any =
specific country-code.  It's for the global E.164 number space.

With regard to other 'identities', if you mean =
non-telephone-number-based SIP user@domain type names, the IETF has a PS =
RFC for that: RFC 4474.  Its adoption rate requires double =
floating-point precision to detect it not being 0%. ;)

This proposed-WG is due to real-world issues in deployments using =
telephone numbers, so that's been our focus scope to "fix".  As it =
happens, both of the proposed STIR solutions so far have in fact =
addressed more than just telephone numbers, including the user@domain =
type.  I've been told so long as we get it "for free" so-to-speak, we =
can address them as well in our deliverables - we just need to focus on =
telephone numbers since that's the problem that needs fixin'.


> no... focus on 'telephone number' is broken. Hell, it's not even
> what's used in the phone system anyway... not really.

Ummm... ok, what is it you think is used in the phone system really?  Or =
what better word/term would you use to label what's used in the phone =
system?

-hadriel


From hannes.tschofenig@gmx.net  Wed Aug 21 12:34:53 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA80121F9FED for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 12:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.799
X-Spam-Level: 
X-Spam-Status: No, score=-102.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZU7aCGZKGeyf for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 12:34:47 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id D929F21F9F2B for <ietf@ietf.org>; Wed, 21 Aug 2013 12:34:46 -0700 (PDT)
Received: from [172.16.254.200] ([195.149.218.67]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MZfZi-1VVXyt1mAg-00LWfF for <ietf@ietf.org>; Wed, 21 Aug 2013 21:34:45 +0200
Message-ID: <5215165D.9080000@gmx.net>
Date: Wed, 21 Aug 2013 21:34:53 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: WG Review: Secure Telephone Identity Revisited (stir)
References: <20130821175202.24713.10458.idtracker@ietfa.amsl.com> <52150FD6.8010306@dcrocker.net> <CAL9jLaaOwB4UNmrgxrEOV=03n2CkQbECR3USUd258-xu_ehiJw@mail.gmail.com> <CAL9jLaZ_6w6XRPQ1G8sYC5JTPW3i3uqvaq-rx79Kta2Rwnqu_Q@mail.gmail.com>
In-Reply-To: <CAL9jLaZ_6w6XRPQ1G8sYC5JTPW3i3uqvaq-rx79Kta2Rwnqu_Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:SMvRmSYS9yZHpfAFARq/KGl/uC9pgFv60ikQqNxZcrxQ04P2OYI 346fWP+5jxdLYA3SW86Hqt1jCYJDS66aOB44gJP1au+LN6Q6aUEjTINNGuQ5vTo1gOvNleS vv/NWH/A0UFBsL9Sbl7aQiQZeh1a4DuISkqv8Ihisx18dCO1GlrgpH/fEZrnTHzM93LGz/J 2BAQ1AvpZ9SKupzbajd/g==
Cc: IESG IESG <iesg@ietf.org>, 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: Wed, 21 Aug 2013 19:34:53 -0000

I noticed in a few places the suggestion to replace telephone number 
with 'identity'.

I think that this is a particularly bad enhancement given how widely the 
term identity is understood by most people.

In RFC 6973 we defined the term (which is inline with many of the 
identity management efforts) as:

    $ Identity:  Any subset of an individual's attributes, including
       names, that identifies the individual within a given context.
       Individuals usually have multiple identities for use in different
       contexts.

I don't think that this is what the work is about.

Let's keep the charter text concise and enhance it later once work gets 
done.

Ciao
Hannes

On 08/21/2013 09:25 PM, Christopher Morrow wrote:
> + iesg
> -iesg-secretary
>
> On Wed, Aug 21, 2013 at 3:18 PM, Christopher Morrow
> <morrowc.lists@gmail.com> wrote:
>> On Wed, Aug 21, 2013 at 3:07 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>>> The following mostly are points that I raised within the group's mailing
>>> list discussion, during charter development.  In my view, they have not yet
>>> been adequately resolved:
>>>
>>>
>>> On 8/21/2013 10:52 AM, The IESG wrote:
>>>>
>>>>     Please send your comments to the IESG mailing list (iesg
>>>> at ietf.org) by 2013-08-28.
>>>
>>> ...
>>>>
>>>> The STIR working group will specify Internet-based mechanisms that allow
>>>> verification of the calling party's authorization to use a particular
>>>> telephone number for an incoming call.
>>>
>>>
>>> "use a particular telephone number for an incoming call" has no obvious and
>>
>> it'd actually be kind of nice if the focus was NOT on the (us)
>> 10-digit "number", but instead on the 'identity' making the call.
>> There's a real chance to move beyond the '10-digit number' and to some
>> stronger, wider, richer sense of 'identity'... we should take that
>> opportunity and run with it.
>>
>>> unambiguous technical meaning.  In fact, it seems to imply the meaning of
>>> "authorization to call a particular number".  However of course that's not
>>> the intended meaning.  Since this is the only text in this paragraph that
>>> says what the working group will /do/ it should make its statement with
>>> clarity and technical substance.
>>>
>>> That is, the charter needs to use a precise term for specifying the specific
>>> role of the number of interest.  In earlier drafts, "caller id" was used.
>>
>> s/number/identity/
>>
>>> The next sentence uses "source telephone number".  Perhaps that is
>>> acceptable.
>>
>> no... focus on 'telephone number' is broken. Hell, it's not even
>> what's used in the phone system anyway... not really.
>>
>>>> Since it has  become fairly easy
>>>> to present an incorrect source telephone number, a growing set of
>>>> problems have emerged over the last decade.  As with email, the claimed
>>>> source identity of a SIP request is not verified, permitting unauthorized
>>>
>>>
>>> As a matter of form, I'll note the SIP's community's use of "identity" is
>>> what is called "identifier" in the identity community.
>>>
>>> ...
>>>
>>>> As its priority mechanism work item, the working group will specify a SIP
>>>
>>>
>>> Reference to work priority is only meaningful in the face of a list of tasks
>>> that will be considered simultaneously and what it means to give priority to
>>> one over another.  Based on the lengthy mailing list discussion of in-band
>>> vs. out-of-band, it appears that the current charter is actually intended to
>>> support simultaneous work on alternative mechanisms, rather than pursuing
>>> them sequentially.
>>>
>>> This should be made explicit.  If the requirement is to work on them
>>> sequentially, then state that.  If the intent is to work on both approaches
>>> simultaneously, then say that.
>>>
>>> ...
>>>
>>>
>>>> In addition to its priority mechanism work item, the working group will
>>>> consider a mechanism for verification of the originator during session
>>>> establishment in an environment with one or more non-SIP hops, most
>>>> likely requiring an out-of-band authorization mechanism.  However, the
>>>> in-band and the out-of-band mechanisms should share as much in common as
>>>> possible, especially the credentials.  The in-band mechanism must be sent
>>>> to the IESG for approval and publication prior to the out-of-band
>>>> mechanism.
>>>
>>>
>>> "in-band and the out-of-band mechanisms should share as much in common as
>>> possible"
>>>
>>> This is the essential text that mandates working on both approaches
>>> simultaneously and makes the earliet assertion about priority moot. (Note
>>> how far down in the charter this is buried, yet how fundamental a
>>> requirement is establishes.)
>>>
>>>
>>> ...
>>>
>>>> Input to working group discussions shall include:
>>>>
>>>
>>> That's a lengthy list of documents.  Why has it left out other documents
>>> discussed during charter development and clearly of continuing interest to
>>> the effort, namely:
>>>
>>>     A proposal for Caller Identity in a DNS-based Entrusted Registry
>>>     (CIDER)
>>>     draft-kaplan-stir-cider-00
>>>
>>>     An Identity Key-based and Effective Signature for Origin-Unknown
>>>     Types
>>>     draft-kaplan-stir-ikes-out-00
>>>
>>>
>>> d/
>>>
>>>
>>> --
>>> Dave Crocker
>>> Brandenburg InternetWorking
>>> bbiw.net


From presnick@qti.qualcomm.com  Wed Aug 21 12:50:22 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76D8D21F9F5E for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 12:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.464
X-Spam-Level: 
X-Spam-Status: No, score=-106.464 tagged_above=-999 required=5 tests=[AWL=0.135, 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 rydrITB2o1BP for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 12:50:16 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 37D4721F9F45 for <ietf@ietf.org>; Wed, 21 Aug 2013 12:50:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377114616; x=1408650616; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RyZ1YqKJdjTAUqXkpGvK21tSIZc8lBw7MG3YCvG8ess=; b=Do0ckdK8QuBGoY3CdUdgrDK3yADIr0w+3I0pBHoRdg38teeSrf3v/jYO w7OfAeQsVIMz/bXgDrc4Yep6kEfjp1U2aUykBiL628xaP0PQuCddqdzyK eVPs4Cj2VVKRka627hWcBlpJkhmYtov0ndV1XdO3MJyrFr1OGKMdyUWka Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="69887504"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 21 Aug 2013 12:50:14 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="524739494"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Aug 2013 12:50:12 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.146.2; Wed, 21 Aug 2013 12:46:13 -0700
Message-ID: <52151903.4030402@qti.qualcomm.com>
Date: Wed, 21 Aug 2013 14:46:11 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <dcrocker@bbiw.net>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>	<52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>
In-Reply-To: <5215123E.5080203@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 19:50:22 -0000

On 8/21/13 2:17 PM, Dave Crocker wrote:
> On 8/21/2013 11:58 AM, Pete Resnick wrote:
>> AD hat squarely on my head.
>>
>> On 8/21/13 1:29 PM, Dave Crocker wrote:
>>
>>> Oh.  Now I understand.
>>>
>>> You are trying to impose new requirements on the original work, many
>>> years after the IETF approved it.
>>>
>>> Thanks.  Very helpful.
>>
>> That's not an appropriate response. It is certainly not helpful to me as
>> the consensus caller. And it is rude.
>
> Since you've made this a formal process point, I'll ask you to 
> substantiate it carefully and also formally.  The implication of your 
> assessment is that IETF participants must not comment on the utility 
> of comments by others.

That's not what I said, and in fact if you look at the line immediately 
following what you quoted, you will see that I said:

>> It's perfectly reasonable to say, "This would constitute a new 
>> requirement and I don't think there is a good justification to pursue 
>> that line."

It is not your complaint about the imposition of new requirements that 
is problematic, or your point that it is not useful to continue that 
line of discussion. Talk about the utility of a comment all that you 
want. It is the sarcasm and the rudeness that I am saying is 
unreasonable. Especially coming from a senior member of the community, 
the only purpose it seems to serve is to bully others into not 
participating in the conversation. If you think that the conversation 
has gone on too long, you're perfectly within rights to ask the manager 
of the thread (in this case, myself or the chairs), in public if you 
like, to make a call and say that the issue is closed. But again, the 
tactics displayed above are not professional and not reasonable 
rhetorical mode.

> I don't recall that being a proscribed behavior, since it has nothing 
> to do with personalities.  So, please explain this in a way that does 
> not sound like Procrustean political correctness.

I am not sure what the first sentence means. And I'm sorry that you 
believe that my stance on this is Procrustean. But the fact is that rude 
comments of this sort do not contribute to consensus-building in the least.

> For the record, I entirely acknowledge that my note has an edge to it 
> and yes, of course alternate wording was possible.  However the thread 
> is attempting to reverse extensive and careful working group effort 
> and to ignore widely deployed and essential operational realities, 
> including published research data.

I appreciate your input that you believe that some or all of the 
objectors are ignoring operational realities. Perhaps they are. But the 
fact is that Last Call is a time for the community to take a last look 
at WG output. If senior members of the community (among which there are 
several in this thread) are suspicious of the output, it *is* important 
to make sure that their concerns are addressed. Maybe they simply don't 
have all of the information. But maybe the WG has missed something 
essential in all that careful work. Both have historically happened many 
times.

> A bit of edge is warranted for such wasteful, distracting and 
> destabilizing consumption of IETF resources.  In fact an important 
> problem with the alternate wording, such as you offered, is that it 
> implies a possible utility in the thread that does not exist.

It is far more distracting and destabilizing for the IETF to come out of 
a Last Call with experienced members of the community suspicious that a 
bad result has occurred, especially if the tactic used to end the 
discussion was sarcasm to chase people away from the discussion. You are 
looking at only the little picture. The consensus might end up on the 
rough side, but  having the conversation has utility in and of itself.

I find your "edge" much more disruptive to the conversation, making it 
much more adversarial than explanatory, and damaging the consensus that 
might be built. I think that lowers the utility of the output tremendously.

pr

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


From mansaxel@besserwisser.org  Wed Aug 21 13:06:01 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBA221F9E80 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 13:06:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=-0.200,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1x1+mWhlSftN for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 13:05:59 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0F221F9F1F for <ietf@ietf.org>; Wed, 21 Aug 2013 13:05:45 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id D030F9E5B; Wed, 21 Aug 2013 22:05:37 +0200 (CEST)
Date: Wed, 21 Aug 2013 22:05:37 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130821200537.GH30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130820100431.0df2aea0@elandnews.com> <20130821100055.GF30516@besserwisser.org> <13637683.gDTVOaM8nE@scott-latitude-e6320>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bygAmIonOAIqBxQB"
Content-Disposition: inline
In-Reply-To: <13637683.gDTVOaM8nE@scott-latitude-e6320>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 20:06:01 -0000

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

Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender=
 Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1)=
 to Proposed Standard Date: Wed, Aug 21, 2013 at 08:51:31AM -0400 Quoting S=
cott Kitterman (scott@kitterma
> > Apparently.
>=20
> Translated:
>=20
> RFC 4408 was in error because it didn't abandon it's installed base.  I g=
ather=20
> this is an error you propose to rectify.

Well, almost. 4408 sort of blunders about like the elephant in a china
shop wrt. query method and depreciation.=20
	(As I have been sternly lectured off-list that I do not understand
	the SPF payload and therefore am in no position to discuss the
	DNS usage, I'd like to assert that the payload syntax matters
	marginally, if at all, for the discussion about which DNS records
	to use and how.)

Specifically, 4408 section 3.1.1 should be updated to:=20

* A domain SHOULD use SPF and MAY use TXT. The latter is only suitable if
  SPF is impossible to publish.=20

* If it is possible to use SPF as a result of having modern provisioning
  systems, SPF MUST be used and consequently, TXT SHOULD NOT be used. (I'd
  like MUST here, but I'm not certain it flies.) If SPF and TXT coexist,=20
  they MUST agree wrt content.=20

* The notion of a sunset date as introduced by Mark Andrews, is interesting=
=2E=20

Section 4.1.1 in 4408 should be altered to direct implementations to
FIRST look for SPF and then _perhaps_ (I'm open for discussion) ask for
TXT, thus creating an incentive to improve performance by serving SPF
rather than TXT. After a possible sunset, TXT MUST NOT be queried for.=20

The preference for SPF vs TXT that is present in 4408 is to be kept
unaltered.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
I'm gliding over a NUCLEAR WASTE DUMP near ATLANTA, Georgia!!

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

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

iEYEARECAAYFAlIVHZEACgkQ02/pMZDM1cWZ2QCbBVA9xy5LcJNMo6A7rGy8D/tc
+zMAnRyPnkFhKF/dsoTCPryKUni297GG
=S3Xa
-----END PGP SIGNATURE-----

--bygAmIonOAIqBxQB--

From sm@elandsys.com  Wed Aug 21 13:36:57 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A4721F9F21 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 13:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.709
X-Spam-Level: 
X-Spam-Status: No, score=-101.709 tagged_above=-999 required=5 tests=[AWL=-0.806, BAYES_00=-2.599, MIME_8BIT_HEADER=0.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 D-7xktJkA5WT for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 13:36: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 2A0C721F9DFA for <ietf@ietf.org>; Wed, 21 Aug 2013 13:36:55 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.232.108]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7LKaWgL013781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 13:36:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377117404; bh=2MQbTCu+T7TxrPaSQ0R2hHuKcUV53nIfR4U05CIw0jA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aVZIilT/QOLSH7/nRvjdGT0cAuArl8UT5dxOONqepjgld6VxwnWF0HNBK0a4TUGXs ECDGVmv03RWvBBLX4lVfyJ9V7btG79tPbTM6tsRnWMOtOVyhapifgPmziEb8fABW8o s8dRNjGYdlhSpJfhoH5rIlg5dAVNlkTJeZaCvzps=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377117404; i=@elandsys.com; bh=2MQbTCu+T7TxrPaSQ0R2hHuKcUV53nIfR4U05CIw0jA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TBh8Gd/8a/1k2I+0MyNS1m7o5uY9vmbEKR5u8tSO1+ScWjEnbPcmiUY349Uq6HGTv dRKynHc8tPWKMyx3FRfOu4/JGYn4KS90/rNq3jgMzYOwNiMau0Qjo65l5jPG+9Ravp sDb6u+LjxRPrWK8u3EWXD+J400c073rL+KLK8oZg=
Message-Id: <6.2.5.6.2.20130821111815.0bd08080@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Aug 2013 13:35:02 -0700
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call of draft-ietf-spfbis-4408bis-19
In-Reply-To: <6DEE47E1-885D-4F12-A766-D9BB2284BA09@frobbit.se>
References: <E3DE33F3-B0A5-494B-9202-499E16ECCFB1@virtualized.org> <20130819222037.GA55876@mx1.yitter.info> <93130B0B-5C37-45EE-8380-AF209CA54B8F@frobbit.se> <521385AA.9080401@qti.qualcomm.com> <933357EA-6472-4C77-AED3-E6411BC684B6@frobbit.se> <6.2.5.6.2.20130820110057.0bead1e8@resistor.net> <6DEE47E1-885D-4F12-A766-D9BB2284BA09@frobbit.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 20:36:57 -0000

Hi Patrik,
At 11:58 20-08-2013, Patrik F=E4ltstr=F6m wrote:
>As the bottle is opened, I hereby state my=20
>objection to Section 3.1 of=20
>draft-ietf-spfbis-4408bis-19 for the reasons=20
>explained below. I do agree (as stated below)=20
>that the section of RFC 4408 that specify how to=20
>use both SPF and TXT resource record types=20
>include an error as it does not lead to interoperability.
>
>As the intention with use of both TXT and SPF=20
>originally was to migrate from TXT to SPF I=20
>instead of what is outlined in the draft suggest=20
>that a proper migration strategy is laid out=20
>(look up mandatory to implement SPF and fall=20
>back to TXT). This instead of deprecation of the SPF record.
>
>In general I do believe, for example when=20
>looking at IPv6 and DNSSEC and similar=20
>technologies, that the lifetime of RFC 4408 is=20
>too short to deprecate any of the proposed=20
>records that are in use, specifically as RFC=20
>4408 explicitly do allow use of both.

draft-ietf-spfbis-4408bis-19 is not the usual=20
Proposed Standard effort.  The SPFBIS WG was=20
tasked to move RFC 4408 to Proposed Standard with=20
restrictions.  One of the restrictions is not to=20
review the design.  I hope that explains why=20
draft-ietf-spfbis-4408bis-19 is what it is.  I=20
suggested to the working group to review the=20
issue of the migration strategy (see=20
http://www.ietf.org/mail-archive/web/spfbis/current/msg03934.html ).

 From Section 3.1.1 of RFC 4408:

   "It is recognized that the current practice (using a TXT record) is
    not optimal, but it is necessary because there are a number of DNS
    server and resolver implementations in common use that cannot handle
    the new RR type.  The two-record-type scheme provides a forward path
    to the better solution of using an RR type reserved for this purpose."

There isn't similar text=20
in  draft-ietf-spfbis-4408bis-19.  Hector Santos commented that:

   "we will add SPF type support in our implementation once the=
 infrastructure
    is ready. For us, as a windows shop, namely Microsoft DNS servers."

I read=20
http://social.technet.microsoft.com/Forums/windowsserver/en-US/5841e884-db22=
-42a1-8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-records=
=20
My conclusion is that there is a DNS server that cannot handle the new RR=
 Type.

The question is how to address the objection about the migration strategy.

Regards,
S. Moonesamy (as document shepherd)



From scott@kitterman.com  Wed Aug 21 13:53:12 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6986C11E810F for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 13:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nc65GtkvFOFK for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 13:53:06 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id A9F9011E8124 for <ietf@ietf.org>; Wed, 21 Aug 2013 13:53:03 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 1150A20E40FD; Wed, 21 Aug 2013 16:53:00 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377118380; bh=aM8Fl9QpD3kAVNIXzm0XCRakLND2U1TOPjqvfUPh1s0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KlpIinMN0xYijINp6dSW2rno64L5KwwaJ79tS25Q3ikdYZ/VswqpQ75L93kFOdpTh s8HeUbYwXZ1AG0yfI8VUfr1wFS+FecbKmvHbmTEG87bv8afDeMSZpXE5Ioz3yjO83T bWlbwLIhbNjWjR6HIbBHR8AGYD7m/xI29Om/lDMY=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id EA6C720E40C2;  Wed, 21 Aug 2013 16:52:59 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 21 Aug 2013 16:52:59 -0400
Message-ID: <1978913.hEkO1ZYpDI@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821200537.GH30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821200537.GH30516@besserwisser.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 20:53:12 -0000

On Wednesday, August 21, 2013 22:05:37 M=E5ns Nilsson wrote:
> Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (=
Sender
> Policy?Framework (SPF) for Authorizing Use of Domains in Email, Versi=
on 1)
> to Proposed Standard Date: Wed, Aug 21, 2013 at 08:51:31AM -0400 Quot=
ing
> Scott Kitterman (scott@kitterma
> > > Apparently.
> >=20
> > Translated:
> >=20
> > RFC 4408 was in error because it didn't abandon it's installed base=
.  I
> > gather this is an error you propose to rectify.
>=20
> Well, almost. 4408 sort of blunders about like the elephant in a chin=
a
> shop wrt. query method and depreciation.
> =09(As I have been sternly lectured off-list that I do not understand=

> =09the SPF payload and therefore am in no position to discuss the
> =09DNS usage, I'd like to assert that the payload syntax matters
> =09marginally, if at all, for the discussion about which DNS records
> =09to use and how.)
>=20
> Specifically, 4408 section 3.1.1 should be updated to:
>=20
> * A domain SHOULD use SPF and MAY use TXT. The latter is only suitabl=
e if
>   SPF is impossible to publish.

This is the point where you abandon the installed base.  Particularly g=
iven=20
the charter, I think this is an inappropriate approach.

> * If it is possible to use SPF as a result of having modern provision=
ing
>   systems, SPF MUST be used and consequently, TXT SHOULD NOT be used.=
 (I'd
>   like MUST here, but I'm not certain it flies.) If SPF and TXT coexi=
st,
>   they MUST agree wrt content.

draft-schlitt-spf-classic-02, which became RFC 4408, had this MUST when=
 it was=20
approved by the IESG.  Since at the time of IESG approval, the RRTYPE f=
or SPF=20
hadn't been allocated yet, they - by necessity - approved a paper desig=
n. =20
Fortunately the RRTYPE was allocated sufficiently before AUTH48 that we=
 were=20
able to experiment with running code and determine that this MUST was=20=

operationally extremely problematic, so it was removed as part of the A=
UTH 48=20
review.

> * The notion of a sunset date as introduced by Mark Andrews, is inter=
esting.
>=20
> Section 4.1.1 in 4408 should be altered to direct implementations to
> FIRST look for SPF and then _perhaps_ (I'm open for discussion) ask f=
or
> TXT, thus creating an incentive to improve performance by serving SPF=

> rather than TXT. After a possible sunset, TXT MUST NOT be queried for=
.

The performance implications are more generally constraining on the rec=
eive=20
side in high volume mail systems.  Adding a second set of sequential DN=
S=20
queries is a non-starter.  It's much more efficient to go straight to T=
XT where=20
99%+ of the time I'll get a correct answer [there are a minute number o=
f=20
domains that publish SPF only, but virtually all type SPF publishers al=
so=20
publish TXT].  I think you're putting the performance implications on t=
he=20
wrong end of the conversation.

Let's say we get to this magical sunset date, whose behavior do you thi=
nk it=20
will influence if they are finding the TXT queries still useful (if the=
y aren't,=20
they won't do it and you don't need the sunset date)?

> The preference for SPF vs TXT that is present in 4408 is to be kept
> unaltered.

Here's a related conundrum that I haven't seen operationally (due to li=
mited=20
RRTYPE SPF deployment, but I have seen similarly for real in the fallba=
ck to=20
v=3Dspf1 records in the SenderID RFCs).  It's an example of why you can=
't ignore=20
the payload.  One of the widely used features of SPF is the "include"=20=

mechanism.  It allows a sender to authorize the hosts of a third party =
to send=20
mail on its behalf.  It also allows SPF records to be chained together =
to=20
publish more information while staying in the standard UDP packet limit=
. =20
Here's an example for the latter from Microsoft's current SPF record:

v=3Dspf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com ...

A key aspect of "include" is that the targe domain MUST have an SPF rec=
ord. =20
If it doesn't, it's a "permerror" - permanent error.  Let's imagine for=
 a=20
moment that example.com has this record published in RRTYPE SPF:

v=3Dspf1 a include:example.org -all

Then let's consider example.org and imagine that, like most SPF partici=
pants=20
today, they have their record published in RRTYPE TXT only:

v=3Dspf1 a -all

A receiver, as you suggest, checks RRTYPE SPF when they get mail from=20=

example.com.  Their SPF verifier processes the "include" mechanism and=20=

determines it needs to do a lookup for example.org's SPF record.  They =
query=20
RRTYPE SPF and they get ANSWER: 0 in return.  Should this verifier:

1.  Return a "permerror" because the target domain of an "include" does=
n't=20
exist?

2.  Press on and query RRTYPE TXT, get an SPF record back, and finish t=
he=20
transaction without error?

RFC 4408 doesn't help us here because it's treatment of the TXT/SPF=20
coexistence model is not complete. =20

I have said before that I don't think an effective transition model exi=
sts nor=20
can it be created.  I think Olafur Gudmundsson's suggestion that 4408bi=
s=20
document this use of TXT as an architectural wart and move on is a good=
 one.

I think this is a symptom of the larger problem that most initial devel=
opment=20
work in this space is done outside the IETF and only brought to the IET=
F when=20
it's reasonably well baked.  This is true for SPF, DK -> DKIM, and DMAR=
C, all=20
of which use TXT.  I would encourage those who want this to be differen=
t in the=20
future to make contact with the people involved in DMARC (I wasn't) and=
 ask=20
them what it would have taken to get them to consider a new RRTYPE in t=
heir=20
design.  Whatever those barriers are, that's what needs to be addressed=
. =20
Focusing to trying to "fix" SPF shouldn't be the priority.  It is what =
it is.

Scott K

From dhc@dcrocker.net  Wed Aug 21 14:41:17 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97E7B11E819C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 14:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.535
X-Spam-Level: 
X-Spam-Status: No, score=-6.535 tagged_above=-999 required=5 tests=[AWL=0.064,  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 I8LVV+XlGfEp for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 14:41:12 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 957C211E8144 for <ietf@ietf.org>; Wed, 21 Aug 2013 14:41:12 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7LLf8I4027585 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Aug 2013 14:41:12 -0700
Message-ID: <521533DB.4040001@dcrocker.net>
Date: Wed, 21 Aug 2013 14:40:43 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>	<52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com>
In-Reply-To: <52151903.4030402@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 21 Aug 2013 14:41:12 -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, 21 Aug 2013 21:41:17 -0000

On 8/21/2013 12:46 PM, Pete Resnick wrote:
> It is not your complaint about the imposition of new requirements that
> is problematic, or your point that it is not useful to continue that
> line of discussion. Talk about the utility of a comment all that you
> want. It is the sarcasm and the rudeness that I am saying is
> unreasonable. Especially coming from a senior member of the community,

OK.  No sarcasm in IETF postings.  Good luck with that.

More seriously...

You might have noticed that there have been a variety of folk making 
unrealistic or misguided suggestions and that they have been receiving 
entirely muted and exploratory -- albeit negative -- responses.

The implication that I think you've missed here is the obligation that 
should hold for a 'senior' participant who is lodging concerns.  The 
current thread is being tenaciously pursued by another "senior" member 
and former AD and the line of objections and requirements being put 
forward are studiously ignoring the considerable efforts of the working 
group and the considerable practical field history.

As such, they represent their own form of disrespect.

The alternative phrasing you suggest makes sense for average, random, 
problematic criticism.  But as I indicated in the previous note, the 
phrasing suffers from implying a degree of legitimacy that is not 
warranted for this thread, from another 'senior' participant.

I realize you don't agree with that view, but I'll again note that I'm 
not aware of any formal rule that my posting violated and certainly not 
any pattern of IETF practice.  (Of course I can read the Code of Conduct 
to the contrary, but having done that, I felt that each of its relevant 
points had a counter in this case.)

I, too, preferred a far more constructive tone to the thread, and 
attempted to contribute that initially.  But persistent 
unreasonableness, when it can't be attributed to ignorance, warrants an 
explicit note.  So I gave it.

Taking this thread seriously, even to the extent of treating it with a 
cautiously respectful tone, encourages a persistent silliness in the 
IETF that is strategically destructive, because it communicates our 
tolerance for having experienced participants waste people's time and 
effort.


> the only purpose it seems to serve is to bully others into not
> participating in the conversation.

You think I could bully Patrik?  Good luck with that, too.


 >If you think that the conversation
> has gone on too long, you're perfectly within rights to ask the manager
> of the thread (in this case, myself or the chairs), in public if you
> like, to make a call and say that the issue is closed. But again, the
> tactics displayed above are not professional and not reasonable
> rhetorical mode.

The thread itself does not have a professional premise, Pete.  The 
record needs to reflect at least one comment to that effect.


>> I don't recall that being a proscribed behavior, since it has nothing
>> to do with personalities.  So, please explain this in a way that does
>> not sound like Procrustean political correctness.
>
> I am not sure what the first sentence means. And I'm sorry that you
> believe that my stance on this is Procrustean. But the fact is that rude
> comments of this sort do not contribute to consensus-building in the least.

The thread has its own responsibility to attempt consensus building.  It 
wasn't doing that.  In fact, in its way, it has represented a classic, 
continuing of bullying against DNS pragmatics.


>> For the record, I entirely acknowledge that my note has an edge to it
>> and yes, of course alternate wording was possible.  However the thread
>> is attempting to reverse extensive and careful working group effort
>> and to ignore widely deployed and essential operational realities,
>> including published research data.
>
> I appreciate your input that you believe that some or all of the
> objectors are ignoring operational realities.

I didn't say that.  This current exchange is about a specific thread. 
It is now your turn to be more careful in what you assert.


> Perhaps they are. But the
> fact is that Last Call is a time for the community to take a last look
> at WG output. If senior members of the community (among which there are
> several in this thread) are suspicious of the output, it *is* important
> to make sure that their concerns are addressed.

Only after determining that their concerns are reasonable.


> Maybe they simply don't
> have all of the information. But maybe the WG has missed something
> essential in all that careful work. Both have historically happened many
> times.

Again, you are missing the point that we'd already done through quite a 
bit of that, with no apparent effect.


> It is far more distracting and destabilizing for the IETF to come out of
> a Last Call with experienced members of the community suspicious that a
> bad result has occurred,

As an abstraction, your point is of course entirely valid.  But your 
premise is that a reasonable discussion is possible and that the 
suspicions can be allayed.  We already had solid indications that 
neither were achievable.


d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From marka@isc.org  Wed Aug 21 14:48:54 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFBBF11E81C7 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 14:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.327
X-Spam-Level: 
X-Spam-Status: No, score=-2.327 tagged_above=-999 required=5 tests=[AWL=0.272,  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 9SV4SXI9121r for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 14:48:49 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id BB13E11E8129 for <ietf@ietf.org>; Wed, 21 Aug 2013 14:48:48 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id C8CD9C9424; Wed, 21 Aug 2013 21:48:35 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377121728; bh=l8k4IMu6BF4tYTqJbJ7W44iEDssYoSoAo55Y3Sn5vJQ=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=tAlbuIhAPCpIqc8cQDQBRE/SS1OajXWm5tYfL4x+vtG+M4ysT8zEdpwJgEdj7H9wM dW8EEAJsp1jH9MHefLIu2xSm0Yzrs0RwHG2FQoXzIeddVsj+Cd7PU2nOwwXQhZRXfk 2cFEJ6d7bn2nw7psZIsW2hP/n2NKGxFigJciYtUI=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 21 Aug 2013 21:48:35 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 978401602E9; Wed, 21 Aug 2013 21:48:47 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 33F0D1602B4; Wed, 21 Aug 2013 21:48:47 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 1C92538C0230; Thu, 22 Aug 2013 07:48:32 +1000 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Wed, 21 Aug 2013 13:02:33 -0400." <7917527.VmCQD3a6Q3@scott-latitude-e6320>
Date: Thu, 22 Aug 2013 07:48:31 +1000
Message-Id: <20130821214832.1C92538C0230@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 21:48:55 -0000

In message <7917527.VmCQD3a6Q3@scott-latitude-e6320>, Scott Kitterman writes:
> On Wednesday, August 21, 2013 23:32:33 Mark Andrews wrote:
> > I object to the removal of the SPF record.
> 
> This is not a shock.  You were in the rough when we discussed it in the WG 
> too.
> 
> > Name servers already have access controls down to the granuality
> > of TYPE.  If this draft proceeds as currently described it is forcing
> > name server vendors to access controls at the sub TYPE granuality.
> 
> It's primarily an issue for applications.  To the DNS, it's exactly what it 
> is, a TXT record.

No.  It isn't.  By overloading TXT you prevent thing like this which
existed before SPF was even dreamed up.

	update-policy {
		grant key-one subdomain example.net ANY
		deny key-two domain example.net SPF
		grant key-two domain example.net ANY
	};

	or

	update-policy {
		grant key-one subdomain example.net ANY
		grant key-two domain example.net TXT
	};

Overloading a type is bad on so many levels which is why it was
argued that SPF needed its own type.  TXT is good for prototyping
and that is about all.

	update-policy {
		grant key-one subdomain example.net ANY
		deny key-two domain example.net TXT/v=spf1
		grant key-two domain example.net ANY
	};

	update-policy {
		grant key-one subdomain example.net ANY
		deny key-two domain example.net TXT/v=spf1
		grant key-two domain example.net TXT!v=spf1
	};

> > With SPF lookup first I can specify the SPF policy using SPF and
> > leave TXT free for other uses without having to worry about the
> > records being misinterpeted.
> 
> Unless you have some specific reason to be concerned about accidentally 
> starting an unrelated TXT record with "v=spf1 ", I can't imagine you don't 
> have more important things to worry about.  This being a "problem" is a great 
> theory, but it just doesn't happen in practice.

It's about being able to hand someone update control and not having to
worry about them stuffing up the SPF records.
 
> > SPF validators MUST NOT proceed to a TXT lookup on SERVFAIL for SPF.
> > This is similar to not proceeding to A/AAAA lookups on MX lookup
> > failures.
> 
> Except that it's quite common for a SERVFAIL on TYPESPF to occur for a domain 
> that has an actual SPF record due to various operational issues.  SERVFAIL on 
> type SPF doesn't reliably tell you anything about what a type TXT lookup would 
> produce.  So it's similar, but only superficially so.

And the worst that happens is that you let some *additional*
potentially spoofed email through.  This WG seems to treat this
as a catastrophic errror when it isn't.  This whole debate is
because this working group treats not stopping one additional
forgery as a catastrophic errror.

Note also that it will be the publishing site to blame for having
a non RFC 1034 compliant server (it didn't respond to SPF queries)
or misconfigured zone (returns wrong SOA in the negative response 
which can't happen when they have a SPF record).

> > I would also suggest that there be a sunset date published for the
> > use of TXT for SPF.
> 
> Do you also suggest creation of an Internet police force to enforce this?  
> What would be be mandatory minimum sentence?

You just code the cut off date into the code that does the verification
and stop making TXT queries.  You code the date into the code that
checks for missing SPF records and change the complaint.

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

From barryleiba.mailing.lists@gmail.com  Wed Aug 21 15:13:09 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 293CA11E823B for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.958
X-Spam-Level: 
X-Spam-Status: No, score=-101.958 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndq08rp1FbDI for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:13:08 -0700 (PDT)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id A000611E8234 for <ietf@ietf.org>; Wed, 21 Aug 2013 15:13:08 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id db10so923324veb.28 for <ietf@ietf.org>; Wed, 21 Aug 2013 15:13:07 -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:message-id:subject :from:to:content-type; bh=fvnMNdi7ii13mt9UhgPWfiJQbCrNY3F+1KfYX+tD220=; b=J1VeqEBkWhsxceEWfRVYZ73HhNrrIt0o4K/5fLXuGYTZpf5VAxkZfAGdbzxNrdsvnA Tqpwsvx5U2JsStzq/QYtaE8uadnFWF3qyPdwdd42MhQF27iZi2Pd6tA7Dp0SidLj7tFV 4r3zgXM5XNiSMWQwaNtG8xdFNkedl2rL98fQe//8TpBPN5Wic1Ut44R6wbBO3FUpyRYJ XXbZo8Qz3YkC0qfIlCP6ILekFKZV23lFh4+AQ1D5Uosxi0rDkQpSakfyHQLQQsuu2spT +7mMi0FJYE0doU2F5lQ4VLMDsr0I9PAC1PeVZcrGvQFk9/QuGXia6dna6YRuBRzxbxD/ wQZQ==
MIME-Version: 1.0
X-Received: by 10.52.36.204 with SMTP id s12mr26767vdj.36.1377123187045; Wed, 21 Aug 2013 15:13:07 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.215.16 with HTTP; Wed, 21 Aug 2013 15:13:06 -0700 (PDT)
In-Reply-To: <521533DB.4040001@dcrocker.net>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net>
Date: Wed, 21 Aug 2013 18:13:06 -0400
X-Google-Sender-Auth: NFt_ogIipWivgs8dIt5zmhp9D7A
Message-ID: <CAC4RtVDM4N9=cGyP+RGkv39=qBuJN04PLUubHMwUDfsqM7uJng@mail.gmail.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,  Version 1) to Proposed Standard)
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: Wed, 21 Aug 2013 22:13:09 -0000

In this conversation between Pete and Dave, there's one point that's
come up which has come up often enough that I want to call it out
separately for comment:

>> the only purpose it seems to serve is to bully others into not
>> participating in the conversation.
>
> You think I could bully Patrik?  Good luck with that, too.

Let's take this out of the context of the discussion at hand, and be
more general -- because, as I said, I'm reacting not to the statement
as it stands, but to how often I've seen it made (twice within the
last few weeks alone).

The form is this:
Point: You behaved badly toward [person X].
Counterpoint: Well, [person X] has been around, he can handle it.

Often, there's a further response that agrees that, indeed, [person X]
can take it, so all is OK.

No.  All is not OK.
What this argument leaves out is consideration of everyone *else*
who's reading this exchange and putting themselves in the shoes of
[person X].  Many of them are looking at what to expect from engaging
in IETF discussions, many of them are not old-timers with thick skins
and an understanding of IETF rhetoric, and many of them will be put
off of participating because they see how we treat those who do
participate.

Again, remember: I'm not talking about this particular discussion, so
let's not fixate on whether or not being abrupt, sarcastic, abusive,
offensive, profane, or whatever... is appropriate for this
conversation.  The general point is that the new people whom we want
to draw in as productive participants will be watching how we treat
each other and deciding whether they want to wade into that pool.

Barry

From stephen.farrell@cs.tcd.ie  Wed Aug 21 15:25:25 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C81411E825B for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level: 
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IM6OeG1EGbaI for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:25:20 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id CDDB811E8118 for <ietf@ietf.org>; Wed, 21 Aug 2013 15:25:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8EF08BE83; Wed, 21 Aug 2013 23:25:18 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PiIUrfdtehyP; Wed, 21 Aug 2013 23:25:16 +0100 (IST)
Received: from [10.87.48.8] (unknown [86.42.16.220]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C9B7EBE77; Wed, 21 Aug 2013 23:25:16 +0100 (IST)
Message-ID: <52153E42.1090703@cs.tcd.ie>
Date: Wed, 21 Aug 2013 23:25:06 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <CAC4RtVDM4N9=cGyP+RGkv39=qBuJN04PLUubHMwUDfsqM7uJng@mail.gmail.com>
In-Reply-To: <CAC4RtVDM4N9=cGyP+RGkv39=qBuJN04PLUubHMwUDfsqM7uJng@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 22:25:25 -0000

On 08/21/2013 11:13 PM, Barry Leiba wrote:
>   The general point is that the new people whom we want
> to draw in as productive participants will be watching how we treat
> each other and deciding whether they want to wade into that pool.

Yes, that is a factor that merits attention.
But not the only nor an always-overriding one.
For example brevity matters, technical correctness
wins, humour is important and can be cruel.

I can't myself think of a good justification for
sarcasm, (well, maybe [1]:-) but I can understand
that sometimes people make mistakes. And sometimes
the same people make the same mistakes many times.
We're not here to make them better though. Calling
'em on it is a good way to handle it I think.
 Generalising to the point where we are all expected
to be politically correct clones would not. (Yes,
I'm exaggerating what you're saying there:-)

S.

[1] https://en.wikipedia.org/wiki/List_of_Father_Ted_characters
and search for sarcastic:-)


From marka@isc.org  Wed Aug 21 15:25:53 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89C011E813D for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.695
X-Spam-Level: 
X-Spam-Status: No, score=-1.695 tagged_above=-999 required=5 tests=[AWL=-0.388, 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 mgUyXPK0g+p5 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:25:48 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 8889611E8263 for <ietf@ietf.org>; Wed, 21 Aug 2013 15:25:48 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 1F0BAC94C3; Wed, 21 Aug 2013 22:25:21 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377123939; bh=mRIc8SqrH7Y4K/4wJ9M3DA/v99+SoK7oUO9hnSp0tYw=; h=Cc:From:References:Subject:In-reply-to:Date; b=ahAa/77CNR895qQNa2RImyrVdoRf7MmyK7h3hZqRDvR4q3Uz+Po7jGdzYmePu6AVK 5+F3y9w7xa/mmUXz26tpSIaH5FkJh6bsuMQv3cyrqFznbrk+1qpheizlfzBxwWC5oc 8slmxZmLBcAYLiHvw1A0KTxFiP6bwM2TLayaJapk=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 21 Aug 2013 22:25:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0825C1602E9; Wed, 21 Aug 2013 22:25:33 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id CE1021602B4; Wed, 21 Aug 2013 22:25:32 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id A617138C05EC; Thu, 22 Aug 2013 08:25:14 +1000 (EST)
From: Mark Andrews <marka@isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320> <20130821214832.1C92538C0230@drugs.dv.isc.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Thu, 22 Aug 2013 07:48:31 +1000." <20130821214832.1C92538C0230@drugs.dv.isc.org>
Date: Thu, 22 Aug 2013 08:25:14 +1000
Message-Id: <20130821222514.A617138C05EC@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 22:25:54 -0000

In message <20130821214832.1C92538C0230@drugs.dv.isc.org>, Mark Andrews writes:
> > It's primarily an issue for applications.  To the DNS, it's exactly what it 
> > is, a TXT record.

I can hand update of A and AAAA records to the machine.
I can hand update of MX records to the mail adminstrator.
I can hand update of SPF records to the mail adminstrator.
I can hand update of TXT records to ??????

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

From mansaxel@besserwisser.org  Wed Aug 21 15:26:55 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC4111E8118 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.467
X-Spam-Level: 
X-Spam-Status: No, score=-2.467 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-+-JFOx5nA4 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:26:45 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id DE2F311E8267 for <ietf@ietf.org>; Wed, 21 Aug 2013 15:26:36 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 5B8CB9E99; Thu, 22 Aug 2013 00:26:35 +0200 (CEST)
Date: Thu, 22 Aug 2013 00:26:35 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130821222635.GJ30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821200537.GH30516@besserwisser.org> <1978913.hEkO1ZYpDI@scott-latitude-e6320>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBdJBemW82xJqIAr"
Content-Disposition: inline
In-Reply-To: <1978913.hEkO1ZYpDI@scott-latitude-e6320>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 22:26:55 -0000

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

Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender=
 Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1)=
 to Proposed Standard Date: Wed, Aug 21, 2013 at 04:52:59PM -0400 Quoting S=
cott Kitterman (scott@kitterma
> On Wednesday, August 21, 2013 22:05:37 M=C3=A5ns Nilsson wrote:
> > Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Se=
nder
> > Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version=
 1)
> > to Proposed Standard Date: Wed, Aug 21, 2013 at 08:51:31AM -0400 Quoting
> > Scott Kitterman (scott@kitterma
> > > > Apparently.
> > >=20
> > > Translated:
> > >=20
> > > RFC 4408 was in error because it didn't abandon it's installed base. =
 I
> > > gather this is an error you propose to rectify.
> >=20
> > Well, almost. 4408 sort of blunders about like the elephant in a china
> > shop wrt. query method and depreciation.
> > 	(As I have been sternly lectured off-list that I do not understand
> > 	the SPF payload and therefore am in no position to discuss the
> > 	DNS usage, I'd like to assert that the payload syntax matters
> > 	marginally, if at all, for the discussion about which DNS records
> > 	to use and how.)
> >=20
> > Specifically, 4408 section 3.1.1 should be updated to:
> >=20
> > * A domain SHOULD use SPF and MAY use TXT. The latter is only suitable =
if
> >   SPF is impossible to publish.
>=20
> This is the point where you abandon the installed base.  Particularly giv=
en=20
> the charter, I think this is an inappropriate approach.

As I'm thinking about migration here, let's be generous. Allow publication
of TXT too, even if SPF is possible, but then not alone.
=20
> > * If it is possible to use SPF as a result of having modern provisioning
> >   systems, SPF MUST be used and consequently, TXT SHOULD NOT be used. (=
I'd
> >   like MUST here, but I'm not certain it flies.) If SPF and TXT coexist,
> >   they MUST agree wrt content.
>=20
> draft-schlitt-spf-classic-02, which became RFC 4408, had this MUST when i=
t was=20
> approved by the IESG.  Since at the time of IESG approval, the RRTYPE for=
 SPF=20
> hadn't been allocated yet, they - by necessity - approved a paper design.=
 =20
> Fortunately the RRTYPE was allocated sufficiently before AUTH48 that we w=
ere=20
> able to experiment with running code and determine that this MUST was=20
> operationally extremely problematic, so it was removed as part of the AUT=
H 48=20
> review.

Hence my comment about perhaps flying.=20
=20
> > * The notion of a sunset date as introduced by Mark Andrews, is interes=
ting.
> >=20
> > Section 4.1.1 in 4408 should be altered to direct implementations to
> > FIRST look for SPF and then _perhaps_ (I'm open for discussion) ask for
> > TXT, thus creating an incentive to improve performance by serving SPF
> > rather than TXT. After a possible sunset, TXT MUST NOT be queried for.
>=20
> The performance implications are more generally constraining on the recei=
ve=20
> side in high volume mail systems.  Adding a second set of sequential DNS=
=20
> queries is a non-starter. =20

Why? There is caching. DNS queries are cheap. The problem of overloading TX=
T is=20
IMNSHO so bad that it is worth the cost of additional queries; especially
if we can collaborate on text to stimulate migration by constructing
and specifying algorithms that are faster when using SPF rrtype only.

> It's much more efficient to go straight to TXT where=20

(ITYM TODAY it is much more efficient and that might change)

> 99%+ of the time I'll get a correct answer [there are a minute number of=
=20
> domains that publish SPF only, but virtually all type SPF publishers also=
=20
> publish TXT].  I think you're putting the performance implications on the=
=20
> wrong end of the conversation.
>=20
> Let's say we get to this magical sunset date, whose behavior do you think=
 it=20
> will influence if they are finding the TXT queries still useful (if they =
aren't,=20
> they won't do it and you don't need the sunset date)?
>=20
> > The preference for SPF vs TXT that is present in 4408 is to be kept
> > unaltered.
>=20
> Here's a related conundrum that I haven't seen operationally (due to limi=
ted=20
> RRTYPE SPF deployment, but I have seen similarly for real in the fallback=
 to=20
> v=3Dspf1 records in the SenderID RFCs).  It's an example of why you can't=
 ignore=20
> the payload.  One of the widely used features of SPF is the "include"=20
> mechanism.  It allows a sender to authorize the hosts of a third party to=
 send=20
> mail on its behalf.  It also allows SPF records to be chained together to=
=20
> publish more information while staying in the standard UDP packet limit. =
=20
> Here's an example for the latter from Microsoft's current SPF record:
>=20
> v=3Dspf1 include:_spf-a.microsoft.com include:_spf-b.microsoft.com ...
>=20
> A key aspect of "include" is that the targe domain MUST have an SPF recor=
d. =20
> If it doesn't, it's a "permerror" - permanent error.  Let's imagine for a=
=20
> moment that example.com has this record published in RRTYPE SPF:
>=20
> v=3Dspf1 a include:example.org -all
>=20
> Then let's consider example.org and imagine that, like most SPF participa=
nts=20
> today, they have their record published in RRTYPE TXT only:
>=20
> v=3Dspf1 a -all
>=20
> A receiver, as you suggest, checks RRTYPE SPF when they get mail from=20
> example.com.  Their SPF verifier processes the "include" mechanism and=20
> determines it needs to do a lookup for example.org's SPF record.  They qu=
ery=20
> RRTYPE SPF and they get ANSWER: 0 in return.  Should this verifier:
>=20
> 1.  Return a "permerror" because the target domain of an "include" doesn'=
t=20
> exist?
>=20
> 2.  Press on and query RRTYPE TXT, get an SPF record back, and finish the=
=20
> transaction without error?
>=20
> RFC 4408 doesn't help us here because it's treatment of the TXT/SPF=20
> coexistence model is not complete. =20

Indeed, and I was inexact in endorsing current text. What I meant was this =
sentence:=20

   2. If any records of type SPF are in the set, then all records of
      type TXT are discarded.

	(section 4.5, record selection process)=20

> I have said before that I don't think an effective transition model exist=
s nor=20
> can it be created. =20

I think this stems from two things, both fixable;=20

* The somewhat confused "migration" model of 4408 creating a "cheap
  escape" for vendors and users.

* The lack of normative language stating that SPF MUST be used.=20

> I think Olafur Gudmundsson's suggestion that 4408bis=20
> document this use of TXT as an architectural wart and move on is a good o=
ne.

I happen to think that this wart is malign and will create undesirable
growth, as has been proven with a number of other spam-stomping systems
using TXT. Short of amputation I think we can justify a lot more surgery
than the present make-up.

> I think this is a symptom of the larger problem that most initial develop=
ment=20
> work in this space is done outside the IETF and only brought to the IETF =
when=20
> it's reasonably well baked.  This is true for SPF, DK -> DKIM, and DMARC,=
 all=20
> of which use TXT.  I would encourage those who want this to be different =
in the=20
> future to make contact with the people involved in DMARC (I wasn't) and a=
sk=20
> them what it would have taken to get them to consider a new RRTYPE in the=
ir=20
> design.  Whatever those barriers are, that's what needs to be addressed. =
=20

I agree.=20

> Focusing to trying to "fix" SPF shouldn't be the priority.  It is what it=
 is.

SPF is a flagship case for the "use a TXT record and continue to IPO"
fast and sloppy crowd. It needs correcting. Badly.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
All of life is a blur of Republicans and meat!

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

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

iEYEARECAAYFAlIVPpsACgkQ02/pMZDM1cV+TACdEEYuGOO+RwG3qGbkkC7To6Js
AesAnRuM7c9C3knqeN6mT9M+5qO9reEe
=6Bac
-----END PGP SIGNATURE-----

--gBdJBemW82xJqIAr--

From sm@elandsys.com  Wed Aug 21 15:36:14 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40DF21F9344 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8JqyJuzVR3kB for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 15:36:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A88CF21F92CD for <ietf@ietf.org>; Wed, 21 Aug 2013 15:36:12 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.102]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7LMZrl6022507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 21 Aug 2013 15:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377124564; bh=6iO6hK/hvZ8DP9f5VCDp1IhuikmzHczs3U2YULp8r3g=; h=Date:To:From:Subject:In-Reply-To:References; b=Nafrrjiv1AJnB2H2BjF3d3qiEs0oqxa1jxqUOZIimWkKTNQrpZSPbcO38gYV6zy9Z NHdphcVewGM3+ZIDLoqr1Iig1H4zL7LtkQkoDZeXTpYIQmjiplKatKy/+fUpUYNkQI k0vYD/66NniS6BROBdN63yT2DmJym9c6emul1MS0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377124564; i=@elandsys.com; bh=6iO6hK/hvZ8DP9f5VCDp1IhuikmzHczs3U2YULp8r3g=; h=Date:To:From:Subject:In-Reply-To:References; b=DBtvjcngI5pKScQPMzee3upBfjtd82VCJmmxUx53N0rzfthMXJxGOGq7RxOOc/d1d rd/L5czmD1rCxnH1Z1pvQCAX+Xs10rHSDg+KL/QVzqGZOcaK91c1dFk2kjPgvUlXhu EcGPoExo5wCWL6dkdVct8lib2yDxkO66h3qkiDrM=
Message-Id: <6.2.5.6.2.20130821152207.0cb13f10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Aug 2013 15:32:16 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
In-Reply-To: <521533DB.4040001@dcrocker.net>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 22:36:14 -0000

Hello,

Lars Eggert mentioned [1] the following:

   "cool off, take the intensity out of the discussion, and try
    to provide data/facts for your different standpoints, so the
    rest of us who are sitting on the sidelines watching the
    fireworks can form an opinion."

Regards,
S. Moonesamy

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


From scott@kitterman.com  Wed Aug 21 16:07:38 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41C9321F8C7C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:07: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 IKfUlCGTMsD9 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:07:37 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id AF44321F8C65 for <ietf@ietf.org>; Wed, 21 Aug 2013 16:07:25 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id D3E27D04085; Wed, 21 Aug 2013 19:07:23 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377126443; bh=+dBoUx2Wd6GRsP15rGG6hQtu0o1FqVvuIRMb+17sQjk=; h=In-Reply-To:References:Subject:From:Date:To:From; b=jwG0Q4Z58sk8AaDaijgYvY4NoohDrTuyqryhFJy21+ciXByRQZh6x57opZU1Xcy5t 5eyY6Ej74IPBs8nAUUIzo6lndR0VrD1ax5sDqiG7HxMZZIx4Ft2xB6YOANfucFABr6 4W66iGC8NASe5z4TaYdQ1VEEHX3M88WRLGpXMEwM=
Received: from [IPV6:2600:1003:b10f:dd68:4953:6750:ff67:6451] (unknown [IPv6:2600:1003:b10f:dd68:4953:6750:ff67:6451]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 4DF5ED0405B;  Wed, 21 Aug 2013 19:07:22 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <20130821222514.A617138C05EC@drugs.dv.isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320> <20130821214832.1C92538C0230@drugs.dv.isc.org> <20130821222514.A617138C05EC@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Scott Kitterman <scott@kitterman.com>
Date: Wed, 21 Aug 2013 19:07:25 -0400
To: ietf@ietf.org
Message-ID: <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 23:07:38 -0000

Mark Andrews <marka@isc.org> wrote:
>
>In message <20130821214832.1C92538C0230@drugs.dv.isc.org>, Mark Andrews
>writes:
>> > It's primarily an issue for applications.  To the DNS, it's exactly
>what it 
>> > is, a TXT record.
>
>I can hand update of A and AAAA records to the machine.
>I can hand update of MX records to the mail adminstrator.
>I can hand update of SPF records to the mail adminstrator.
>I can hand update of TXT records to ??????

No one because it has multiple uses.  This is true whether SPF exists or not.  SPF use of RRTYPE TXT for SPF records makes that neither better nor worse.

You could publish:

example.com IN TXT v=spf1 redirect=_spf.example.com
_spf.example. com IN TXT v=spf1 [actual content here]

Then delegate _spf.example.com to the mail administrator.  Problem solved.

Scott K

From scott@kitterman.com  Wed Aug 21 16:12:59 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E0D521F9A7D for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mVnOPRWg1iOj for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:12:53 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 17A2C21F84DB for <ietf@ietf.org>; Wed, 21 Aug 2013 16:12:26 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 83D45D04085; Wed, 21 Aug 2013 19:12:25 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377126745; bh=7oGDwvNTQgPcwd+Lix97Z5Z1XtiXLJegacadMLaX7fY=; h=In-Reply-To:References:Subject:From:Date:To:From; b=UA3QsNaXBWcE+z6o1jFTtiu3xWn67/XaKeoDhFWGJI0QG2HzsTf2/J2tf3CZ+56Mu efHuqIY1k9NPREHu+Ro+vuLVU/f9j7FkZM6EKsOHne+XEQhOoZIcfFMONqGLGdntc8 Ze1qRVTc5JUUXIsh21qL9xQKM9APcxWGCW8derMc=
Received: from [IPV6:2600:1003:b10f:dd68:4953:6750:ff67:6451] (unknown [IPv6:2600:1003:b10f:dd68:4953:6750:ff67:6451]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 03318D0405B;  Wed, 21 Aug 2013 19:12:24 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <20130821214832.1C92538C0230@drugs.dv.isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320> <20130821214832.1C92538C0230@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Scott Kitterman <scott@kitterman.com>
Date: Wed, 21 Aug 2013 19:12:27 -0400
To: ietf@ietf.org
Message-ID: <09389910-47bf-455b-8de7-80b737b8dfa4@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 23:12:59 -0000

Mark Andrews <marka@isc.org> wrote:
>
>In message <7917527.VmCQD3a6Q3@scott-latitude-e6320>, Scott Kitterman
>writes:
>> On Wednesday, August 21, 2013 23:32:33 Mark Andrews wrote:
>> > I object to the removal of the SPF record.
>> 
>> This is not a shock.  You were in the rough when we discussed it in
>the WG 
>> too.
>> 
>> > Name servers already have access controls down to the granuality
>> > of TYPE.  If this draft proceeds as currently described it is
>forcing
>> > name server vendors to access controls at the sub TYPE granuality.
>> 
>> It's primarily an issue for applications.  To the DNS, it's exactly
>what it 
>> is, a TXT record.
>
>No.  It isn't.  By overloading TXT you prevent thing like this which
>existed before SPF was even dreamed up.
>
>	update-policy {
>		grant key-one subdomain example.net ANY
>		deny key-two domain example.net SPF
>		grant key-two domain example.net ANY
>	};
>
>	or
>
>	update-policy {
>		grant key-one subdomain example.net ANY
>		grant key-two domain example.net TXT
>	};
>
>Overloading a type is bad on so many levels which is why it was
>argued that SPF needed its own type.  TXT is good for prototyping
>and that is about all.
>
>	update-policy {
>		grant key-one subdomain example.net ANY
>		deny key-two domain example.net TXT/v=spf1
>		grant key-two domain example.net ANY
>	};
>
>	update-policy {
>		grant key-one subdomain example.net ANY
>		deny key-two domain example.net TXT/v=spf1
>		grant key-two domain example.net TXT!v=spf1
>	};

This can be solved other ways.  See my repky to your later message.

>> > With SPF lookup first I can specify the SPF policy using SPF and
>> > leave TXT free for other uses without having to worry about the
>> > records being misinterpeted.
>> 
>> Unless you have some specific reason to be concerned about
>accidentally 
>> starting an unrelated TXT record with "v=spf1 ", I can't imagine you
>don't 
>> have more important things to worry about.  This being a "problem" is
>a great 
>> theory, but it just doesn't happen in practice.
>
>It's about being able to hand someone update control and not having to
>worry about them stuffing up the SPF records.
> 
>> > SPF validators MUST NOT proceed to a TXT lookup on SERVFAIL for
>SPF.
>> > This is similar to not proceeding to A/AAAA lookups on MX lookup
>> > failures.
>> 
>> Except that it's quite common for a SERVFAIL on TYPESPF to occur for
>a domain 
>> that has an actual SPF record due to various operational issues. 
>SERVFAIL on 
>> type SPF doesn't reliably tell you anything about what a type TXT
>lookup would 
>> produce.  So it's similar, but only superficially so.
>
>And the worst that happens is that you let some *additional*
>potentially spoofed email through.  This WG seems to treat this
>as a catastrophic errror when it isn't.  This whole debate is
>because this working group treats not stopping one additional
>forgery as a catastrophic errror.

I prefer to design things for reliability rather than ignore interoperability problems. 

>Note also that it will be the publishing site to blame for having
>a non RFC 1034 compliant server (it didn't respond to SPF queries)
>or misconfigured zone (returns wrong SOA in the negative response 
>which can't happen when they have a SPF record).

Or some firewall in a box in between. Blame is not so easy to determine. 

>> > I would also suggest that there be a sunset date published for the
>> > use of TXT for SPF.
>> 
>> Do you also suggest creation of an Internet police force to enforce
>this?  
>> What would be be mandatory minimum sentence?
>
>You just code the cut off date into the code that does the verification
>and stop making TXT queries.  You code the date into the code that
>checks for missing SPF records and change the complaint.

Is there an example of this kind of approach working? 

Scott K


From sm@elandsys.com  Wed Aug 21 16:18:41 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E5511E8258 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2XrjO3UTDwdK for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:18:39 -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 DB5B911E823B for <ietf@ietf.org>; Wed, 21 Aug 2013 16:18:39 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.102]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7LNIBPi009418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 16:18:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377127105; bh=iOl7nnUNMSgvpRkgwaj/GO1ijCivuhRFi1HLSgP6Lug=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JvuLO7oWr1HBYga7e+8c/yZ8bwNYJqxJNTIQWVsHpWmDkxkxmIAWV1E3UNFhz+kF1 BUudh4X9Rkn9KQmvvQBHEOLcmdEH1bn4LK2Ne84vE6OKXcsHvCjkLogEPshNrdWa2I eK0AmIovwZnzt2B6YFc3+PgsY6F3nttwEup82J/0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377127105; i=@elandsys.com; bh=iOl7nnUNMSgvpRkgwaj/GO1ijCivuhRFi1HLSgP6Lug=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=auW/IyeS8Os2XZg/tQm7gqe+AYHhueTyeNR9hgUPGrl6kQy3ZlXc7ZaPbooQFLvTi MgR8qw0/G2xdDSWJ7klKEiecibqrM9e9azWlL52vQb/GoN6SdPyr8+6frJ9nGAUr/M PAaCvfv/O0v9Oc6ypw9HiElFEZjnWI3D+XTJAH3w=
Message-Id: <6.2.5.6.2.20130821153516.0c69e9d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Aug 2013 16:16:12 -0700
To: Eliot Lear <lear@cisco.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <521495EB.7060207@cisco.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 23:18:41 -0000

Hi Eliot,
At 03:26 21-08-2013, Eliot Lear wrote:
>First, I appreciate that you and Dave are bringing data to the 
>table.  However, in this case, it is not in dispute that queries are 
>happening.  What *is* in dispute is whether there are answers.  I 
>must admit I am having a difficult time understanding the logic, 
>even so.  The *hard* part about this was supposed to be 
>implementation of the record in the application software.  Can the 
>shepherd answer this question:
>To what extent has that happened?

There is a thread about libspf2 querying for RRTYPE 99 first ( 
https://lists.exim.org/lurker/message/20110812.094310.3a53c0f6.gl.html#exim-users 
).

I'll also mention 
http://support.godaddy.com/groups/domains-management-and-services/forum/topic/spf-type-99/ 
and http://features.cpanel.net/responses/ability-to-create-spf-type-99-records

Here are a few messages on the SPFBIS mailing list about RRTYPE 99:

http://www.ietf.org/mail-archive/web/spfbis/current/msg00555.html
http://www.ietf.org/mail-archive/web/spfbis/current/msg03778.html
http://www.ietf.org/mail-archive/web/spfbis/current/msg03781.html

The SPFBIS WG Chair asked a question about what to conclude given the 
SPFBIS Charter ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03779.html ).

Regards,
S. Moonesamy (as document shepherd)


From marka@isc.org  Wed Aug 21 16:31:28 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B1411E8143 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level: 
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277,  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 lb+0RntqEG1S for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 16:31:23 -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 EC27E11E8261 for <ietf@ietf.org>; Wed, 21 Aug 2013 16:31:22 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 43CF2C94C8; Wed, 21 Aug 2013 23:31:10 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377127882; bh=Jj/PSCf1QaxPUhuMiavWEzqkpTbGtO66iQ7/BYHE+TQ=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=ZuyGO2KTOM7jrltHTtmk/Go4VSeYAB+unUpvVEd1hps+RCZaVfOiVNcXADZvkoiWz aCxi1cOqMoOJmIF79izEz7f73N7QWqFKsekpzSCmJic/QmMcR+O1/n5hvgO+QFD1Vs hTF1obAfLN7ecMAEh131Mmn+Y+LGz+24IpTzsNBQ=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 21 Aug 2013 23:31:10 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 5F8A01602E9; Wed, 21 Aug 2013 23:31:22 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 302371602B4; Wed, 21 Aug 2013 23:31:22 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 39C5338C0A87; Thu, 22 Aug 2013 09:31:03 +1000 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320> <20130821214832.1C92538C0230@drugs.dv.isc.org> <20130821222514.A617138C05EC@drugs.dv.isc.org> <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Wed, 21 Aug 2013 19:07:25 -0400." <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>
Date: Thu, 22 Aug 2013 09:31:03 +1000
Message-Id: <20130821233103.39C5338C0A87@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2013 23:31:28 -0000

In message <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>, Scott Kitterman writes:
> 
> 
> Mark Andrews <marka@isc.org> wrote:
> >
> >In message <20130821214832.1C92538C0230@drugs.dv.isc.org>, Mark Andrews
> >writes:
> >> > It's primarily an issue for applications.  To the DNS, it's exactly
> >what it 
> >> > is, a TXT record.
> >
> >I can hand update of A and AAAA records to the machine.
> >I can hand update of MX records to the mail adminstrator.
> >I can hand update of SPF records to the mail adminstrator.
> >I can hand update of TXT records to ??????
> 
> No one because it has multiple uses.  This is true whether SPF exists or not.  SPF use of RRTYPE TXT for SPF records mak
> es that neither better nor worse.
> 
> You could publish:
> 
> example.com IN TXT v=spf1 redirect=_spf.example.com
> _spf.example. com IN TXT v=spf1 [actual content here]
> 
> Then delegate _spf.example.com to the mail administrator.  Problem solved.

No, it is NOT solved.  You have to trust *everyone* with the ability
to update TXT not to remove / alter that record.  You can't give someone
you don't trust the ability to update TXT.

With a published SPF record and SPF lookup first stopping on success
or lookup failure (SERVFAIL) you can give update control of TXT to
someone you don't trust enough to not remove / alter the SPF TXT
record.

You keep telling us the TXT is just another record in the DNS.  Well
the DNS is managed at the granuality of the TYPE.  4408bis is forcing
sub-type management to be developed and deployed to maintain the
status quo.  TXT is no longer "just another record in the DNS" with
4408bis as it currently stands.

And to Google your motto is "Do No Evil".  Publishing a TXT SPF record
without publish a SPF SPF record is "Evil" as it encourages other to
do the same.

Mark

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

From hsantos@isdg.net  Wed Aug 21 17:32:45 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 950D321F90C3 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 17:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.951
X-Spam-Level: 
X-Spam-Status: No, score=-101.951 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwAJgaorEEtA for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 17:32:40 -0700 (PDT)
Received: from mail.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id DFB2321F90AC for <ietf@ietf.org>; Wed, 21 Aug 2013 17:32:39 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3086; t=1377131557; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=BQ9/VD2Ng0MRYl+bIRKKrl+oBH4=; b=pKbnCy6nHDr+EMDUDcuk VZacjiw3zGh5xED9PyqieXofTtx8BC61904zo2LJPMYWeK3Q5J26amC9e4bs3mJ/ SCCx+OrCw3VZPI+NBifiObULi/4/6pqqo01r+U8Lf0p6MNIgIaTGXwvfU7SxbRj2 MPjyvAoyIoMMTlsmUE+Q77U=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 21 Aug 2013 20:32:37 -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 3594073215.840.2900; Wed, 21 Aug 2013 20:32:37 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3086; t=1377131245; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=mkEx0BA bKocyKdrF2fgpdXGs/7bxRimvDEteGHusH58=; b=g33ezIczd1wspfTNlc6Cp2e j8zb1SNOC+q4E7Ve1cAM5qFW4xE1LKVe4VpMnRiVt0OmPuzblL5A/FKtaFvcSMP3 3x4XWJ67tohK5dh9+waAPQoA8aarkq1DoDRRlzcmb0+A8fzXqLiR1k0QswtiWnIV wDyv6ru84WZVwBH/brnE=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 21 Aug 2013 20:27:25 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3040493252.9.3040; Wed, 21 Aug 2013 20:27:24 -0400
Message-ID: <52155C1A.6090306@isdg.net>
Date: Wed, 21 Aug 2013 20:32:26 -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: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>	<20130819214139.GB19946@mx1.yitter.info>	<7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com> <2213585.EOg7LJb1ub@scott-latitude-e6320>
In-Reply-To: <2213585.EOg7LJb1ub@scott-latitude-e6320>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 00:32:45 -0000

Scott Kitterman wrote:
> On Wednesday, August 21, 2013 14:44:41 Olafur Gudmundsson wrote:
>> What I want the IESG to add a note to the document is that says something
>> like the following: "The retirement of SPF from specification is not to be
>> taken that new RRtypes can not be used by applications, the retirement is
>> consequence of the dual "quick-deploy" strategy. The IETF will continue to
>> advocate application specific RRtypes applications/firewalls/libraries
>> SHOULD support that approach."
> 
> I'm a bit unsure that continue is the right word.  DKIM moved to the TXT with 
> underscore approach and, IIRC, never considered a new RRTYPE, nor did anyone 
> ever suggest they should.  DMARC, which has had a BoF and for which a WG is 
> being considered will do the same (there's no variant of proposed charter text 
> floating around that would allow them to consider otherwise).  

Consider that those specifications were written by the same author and 
group of folks. In no special meaning in any way, they all have had 
the same engineering mindset when it came the DKIM, VBR, ADSP and now 
even yet another DMARC proposed protocol. Same engineers, same 
engineering synergism.   Thats not a negative commentary. This is 
desirable in an integrated world, but it can also locked down certain 
views as it has this case.

DKIM learned from the SPF success with TXT. I specifically recall the 
WG decision discussion and it made practical sense. It allowed for an 
immediate entry point and fast proof of concept industry wide by using 
a TXT-based protocol, not only for DKIM but also for its original 
companion protocol ADSP (formerly SSP).  Overall, I had sense a 
growing change in TXT-based protocol acceptability with many folks who 
otherwise were against it and this was quite apparent to me being 
highly considerate and cognizant of the technical design issue.

It was for this reason I asked the question in the DNSEXT list and 
IETF before LC about where the industry stood in regards to TXT based 
solutions. I always had  several ideas of my own for TXT-based DNS 
proposals such as DSAP (DKIM Signature Authorization Protocol) and a 
few others and if the IETF/DNS community was going to changed its 
belief and now endorse the TXT ideas, I didn't want to propose 
anything that would be controversial such as a new RR type, although 
that would most likely appease the DNS folks.

> I agree with that the notion of a statement that SPF is what it is for a 
> variety of reasons and shouldn't be considered as a precedent for the future 
> might be a reasonable thing to add.  I don't think the IETF has been very 
> consistent about what one ought to do instead.

I don't agree with the SPF exception. If you believe in the future 
infrastructure to support new RR types, then there is no sensible 
reason to remove the SPF type and migration path from an updated 
RFC-4408BIS document.

I don't see any harm in keeping the migration path IFF there is 
confidence a supportive infrastructure will be available in the future.


--
HLS



From drc@virtualized.org  Wed Aug 21 17:47:18 2013
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D16711E8141 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 17:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Wvt0+Yg2XYT1 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 17:47:12 -0700 (PDT)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 2784D11E817D for <ietf@ietf.org>; Wed, 21 Aug 2013 17:47:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id CF60C8712A; Wed, 21 Aug 2013 20:47:00 -0400 (EDT)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 31165-03; Wed, 21 Aug 2013 20:47:00 -0400 (EDT)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 2012487128; Wed, 21 Aug 2013 20:46:59 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_6F761A69-2C1D-4930-A9D6-C4069138A6AC"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt>	(Sender Policy Framework (SPF) for Authorizing Use of Domains	in Email, Version 1) to Proposed Standard
From: David Conrad <drc@virtualized.org>
In-Reply-To: <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>
Date: Wed, 21 Aug 2013 17:46:58 -0700
Message-Id: <5B7FC3D8-ECBB-4541-95CE-7F8B1EC5E05C@virtualized.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <13637683.gDTVOaM8nE@scott-latitude-e6320> <20130821133233.D0A6B38BE02F@drugs.dv.isc.org> <7917527.VmCQD3a6Q3@scott-latitude-e6320> <20130821214832.1C92538C0230@drugs.dv.isc.org> <20130821222514.A617138C05EC@drugs.dv.isc.org> <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 00:47:18 -0000

--Apple-Mail=_6F761A69-2C1D-4930-A9D6-C4069138A6AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Scott,

On Aug 21, 2013, at 4:07 PM, Scott Kitterman <scott@kitterman.com> =
wrote:
> You could publish:
>=20
> example.com IN TXT v=3Dspf1 redirect=3D_spf.example.com
> _spf.example. com IN TXT v=3Dspf1 [actual content here]
>=20
> Then delegate _spf.example.com to the mail administrator.  Problem =
solved.

Wouldn't this cause an extra lookup that you were arguing was =
prohibitive for large scale mail providers?

Regards,
-drc


--Apple-Mail=_6F761A69-2C1D-4930-A9D6-C4069138A6AC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSFV+CAAoJEIzZ2DQOJFbK84oIAKGxCCiXOcZr1ZsOAeH+DQom
mTeD8UFETta0edLwpsH+zim07ampTC7FNqnwC4YUPCA8U6W03KJTgLUId/NbD82m
PqKkvfOXjykr9TfIdtzU9F68aoEjGy9d1oIm5rrg0INO8G+5fDzi5PPjUszBlJ19
Km2wdRPfF1h11zkzW/jtGA77fiJyUofo0GaoNFSAa2RwEoxYi2yZCGHSCtBLCyNv
T9OtGfoi8uO1kcJWR6kRPpgWqHA1kR6Elpj9LeGQypeLG/X0wH5glVMmBT/t2K3K
W/KfEl/hIJ84qz8aXHWyYTBtY74kqgrV0CdBlAdeSDAzyP9JqAcfvE059GeM3uk=
=AhQX
-----END PGP SIGNATURE-----

--Apple-Mail=_6F761A69-2C1D-4930-A9D6-C4069138A6AC--

From john@jlc.net  Wed Aug 21 20:02:13 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D27E11E81AB for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 20:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.24
X-Spam-Level: 
X-Spam-Status: No, score=-106.24 tagged_above=-999 required=5 tests=[AWL=0.359, 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 7j2FzaKPBCNt for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 20:02:03 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 393C711E81A6 for <ietf@ietf.org>; Wed, 21 Aug 2013 20:02:03 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 9E42D33C2E; Wed, 21 Aug 2013 23:02:02 -0400 (EDT)
Date: Wed, 21 Aug 2013 23:02:02 -0400
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130822030202.GP68553@verdi>
References: <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5215123E.5080203@dcrocker.net>
User-Agent: Mutt/1.4.1i
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 03:02:13 -0000

NB: I have read the rest of the thread; but this is what deserves a reply:

Dave Crocker <dhc@dcrocker.net> wrote:
> On 8/21/2013 11:58 AM, Pete Resnick wrote:
> 
>> AD hat squarely on my head.

   (There may have been a miscommunication here -- what particular AD
function Pete was speaking in; but to me, at least, it becomes clear
in context.)

>> On 8/21/13 1:29 PM, Dave Crocker wrote:
>>
>>> Oh.  Now I understand.
>>>
>>> You are trying to impose new requirements on the original work, many
>>> years after the IETF approved it.
>>>
>>> Thanks.  Very helpful.
>>
>> That's not an appropriate response.

   Dave has every right to disagree on that; but I quite agree with
Pete. It is decidedly not helpful, not productive, and tends towards
escalating a discussion which has no need of escalation.

>> It is certainly not helpful to me as the consensus caller.

   Dave has no right to disagree with this. We pay Pete the big bucks
to call consensus on difficult issues like this. We need to understand
it will be hard sometimes.

   I'm sure Dave has read Pete's draft on the meaning of consensus.
I'm less sure he remembered it as he responded here.

   If this is the sort of response given to somewhat-valid questions
raised about the draft being proposed, Pete will eventually have to
say there _is_ no consensus. :^(

>> And it is rude.

   Pete's opinion. (I happen to share it.)

   Consensus process works _much_ better if we respect the opinions
of others -- even when we "know" they're wrong.

> Since you've made this a formal process point,

   Pete has _not_ done this.

> I'll ask you to substantiate it carefully and also formally...

   I see no reason Pete has any obligation to do so. If he chooses
to, I ask him to not do it on this list. ("Please don't feed the
troll" comes to mind.)

> A bit of edge is warranted for such wasteful, distracting and 
> destabilizing consumption of IETF resources...

   Dave's opinion. (I happen to not share it.)

   Consensus process _also_ works better if we respect Dave's
opinion here.

   I suggest we all remember that we don't have to change others'
opinions here (were such a thing possible). We have only to bring
them to the point where they agree they can live with the result.

--
John Leslie <john@jlc.net>

From scott@kitterman.com  Wed Aug 21 20:20:39 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38AF411E818C for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 20:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 AbgWnPlcTsdO for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 20:20:30 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id C4BA711E8179 for <ietf@ietf.org>; Wed, 21 Aug 2013 20:20:30 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id AD8FE20E40FD; Wed, 21 Aug 2013 23:20:28 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377141628; bh=rl4vRDm+wMLK5AUcYfxXMW6x0HWK8k0BNm+ulYZvH2Q=; h=From:To:Subject:Date:In-Reply-To:References:From; b=J+VAdFX2/QLKrOgm5dRn4d4yiapVXXOWjwOQwvZCL9nfjD10RTFbRDt0n21ZYZndY 2p+JiY7AkzoCPiJ8MKNInvH+S2fBlm3A8IX6+a0jQpkUcLq+RyhB7aQ98vNrnplomi HlwPW26U16v4jvq/vh3UKb8tyK9D3GDj7fkN8ebI=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 959CC20E40C2;  Wed, 21 Aug 2013 23:20:28 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 21 Aug 2013 23:20:25 -0400
Message-ID: <1810406.ESMbiX16Oo@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821233103.39C5338C0A87@drugs.dv.isc.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com> <20130821233103.39C5338C0A87@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 03:20:39 -0000

On Thursday, August 22, 2013 09:31:03 Mark Andrews wrote:
> In message <0c3746c3-dac1-471f-bd07-8faf20481337@email.android.com>, Scott 
Kitterman writes:
> > Mark Andrews <marka@isc.org> wrote:
> > >In message <20130821214832.1C92538C0230@drugs.dv.isc.org>, Mark Andrews
> > >
> > >writes:
> > >> > It's primarily an issue for applications.  To the DNS, it's exactly
> > >
> > >what it
> > >
> > >> > is, a TXT record.
> > >
> > >I can hand update of A and AAAA records to the machine.
> > >I can hand update of MX records to the mail adminstrator.
> > >I can hand update of SPF records to the mail adminstrator.
> > >I can hand update of TXT records to ??????
> > 
> > No one because it has multiple uses.  This is true whether SPF exists or
> > not.  SPF use of RRTYPE TXT for SPF records mak es that neither better
> > nor worse.
> > 
> > You could publish:
> > 
> > example.com IN TXT v=spf1 redirect=_spf.example.com
> > _spf.example. com IN TXT v=spf1 [actual content here]
> > 
> > Then delegate _spf.example.com to the mail administrator.  Problem solved.
> 
> No, it is NOT solved.  You have to trust *everyone* with the ability
> to update TXT not to remove / alter that record.  You can't give someone
> you don't trust the ability to update TXT.
> 
> With a published SPF record and SPF lookup first stopping on success
> or lookup failure (SERVFAIL) you can give update control of TXT to
> someone you don't trust enough to not remove / alter the SPF TXT
> record.
> 
> You keep telling us the TXT is just another record in the DNS.  Well
> the DNS is managed at the granuality of the TYPE.  4408bis is forcing
> sub-type management to be developed and deployed to maintain the
> status quo.  TXT is no longer "just another record in the DNS" with
> 4408bis as it currently stands.
> 
> And to Google your motto is "Do No Evil".  Publishing a TXT SPF record
> without publish a SPF SPF record is "Evil" as it encourages other to
> do the same.

Your goal seems to be pretty much the opposite of the task the working group 
was given.  You say so even more clearly here:

http://www.ietf.org/mail-archive/web/spfbis/current/msg03948.html

Unless you come with something new, I think I'm done.

Scott K

From sm@elandsys.com  Wed Aug 21 21:16:49 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AEDC11E822F for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 21:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4CRmKMCITWgy for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 21:16: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 AA67D11E8218 for <ietf@ietf.org>; Wed, 21 Aug 2013 21:16:47 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.102]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7M4GU9e022730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Aug 2013 21:16:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377145004; bh=BxESsB8t0KNs8xWtkg6OeoWg1rdaoGFglUoTJxsTuL4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0EONlIAHdezMv60HW+hm6aj94WnZytvEg0prxxNI2QXAe9C/g4f4vQtPr3FBLWrMz KaGkXxPYn6fuvQEtD9ObSpBlMAhbx5JNI8YfMmnDOZ2WD5bb3cjr0aVe4OrE9Vgk38 AmQxKvBE/7o14ZP1PtVJ9r5ohYhYhC0XbPyWYLw0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377145004; i=@elandsys.com; bh=BxESsB8t0KNs8xWtkg6OeoWg1rdaoGFglUoTJxsTuL4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=A7abJUGj7IYSIOrbv6UfcmRrC1J+UpxNZVuypFfqraRiz2jWMioWcJ1SnwQYe3mtw D5PN8gXhdpIq3DkzIIiPlY9MXmhzP1uFLv4F+Onw1e1j/jNEG2kbVUZAijSZhd8JDt +d/CrCP+Dec8DGQ1QLdQMNJy/iXe3i691hSQ/Q/0=
Message-Id: <6.2.5.6.2.20130821201038.0cb55b40@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 21 Aug 2013 21:12:37 -0700
To: John Leslie <john@jlc.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130822030202.GP68553@verdi>
References: <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <20130822030202.GP68553@verdi>
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, 22 Aug 2013 04:16:49 -0000

Hi John,
At 20:02 21-08-2013, John Leslie wrote:
>    If this is the sort of response given to somewhat-valid questions
>raised about the draft being proposed, Pete will eventually have to
>say there _is_ no consensus. :^(

An Area Director may say that. :-(

Regards,
S. Moonesamy 


From scott@kitterman.com  Wed Aug 21 21:24:04 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A86B11E8218 for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 21:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m27PH0vkJ0PB for <ietf@ietfa.amsl.com>; Wed, 21 Aug 2013 21:23:59 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 458C811E81FF for <ietf@ietf.org>; Wed, 21 Aug 2013 21:23:59 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 53BC020E40FD; Thu, 22 Aug 2013 00:23:57 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377145437; bh=q8hVqdyu1wdJmFbFTQCCffrjtD6LV0sRziaxjdfp4QE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=APARBMObYVUZMmNVmHvw5CMhlAbPBf5LlISRI4h6SSjaoAOsiQa3Mb1s1b0kGS1Vb KOpZzf9DHYt+kNiZmDDdEJZ8Pf6qsrvhs05MBn2NJTF/b0GEGVqQnlUbMqScE77jaN 3bJWIblRLiBRb6lTlJ1tI8f9m2aIbqzpg1aHZLF4=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 3866D20E40C2;  Thu, 22 Aug 2013 00:23:56 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Thu, 22 Aug 2013 00:23:56 -0400
Message-ID: <47490907.LpnmdQ5uG4@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <20130821222635.GJ30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <1978913.hEkO1ZYpDI@scott-latitude-e6320> <20130821222635.GJ30516@besserwisser.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 04:24:04 -0000

On Thursday, August 22, 2013 00:26:35 M=E5ns Nilsson wrote:
...
> SPF is a flagship case for the "use a TXT record and continue to IPO"=

> fast and sloppy crowd. It needs correcting. Badly.

Which IPO was that?

BTW, in 2003 the choice was use TXT or nothing.  So it was a crowd that=
 wanted=20
to accomplish something and did it the only way it was possible.  Consi=
dering=20
use of TXT wasn't an important factor in the DKIM last call, I conclude=
 that=20
this isn't really about using TXT.

Scott K

From sustrik@250bpm.com  Thu Aug 22 00:44:37 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D72C211E80F3 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 00:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3kBrH5eZC-F for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 00:44:30 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3B3D121F9425 for <ietf@ietf.org>; Thu, 22 Aug 2013 00:44:30 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id EB3FA1803555; Thu, 22 Aug 2013 09:44:27 +0200 (CEST)
Message-ID: <5215C15B.3000008@250bpm.com>
Date: Thu, 22 Aug 2013 09:44:27 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com> <5214D8E7.50002@isi.edu> <5214DD54.60009@250bpm.com> <5214F219.6000506@isi.edu>
In-Reply-To: <5214F219.6000506@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 07:44:37 -0000

On 21/08/13 19:00, Joe Touch wrote:

>> So what would you use for muxing, if TCPMUX is not a good idea?
>
> You need to roll your own. The requirements of systems vary widely, as
> do the costs/benefits of different approaches.
>
> I listed a few before, but here's a more comprehensive list:
>      - service per message
>          demux based on message ID
>          use IPC (interprocess comm) to handoff internal
>          to your system
>
>      - service per connection
>          demux based on the first message in an
>          association (TCP or UDP), and either continue to
>          forward messages to a different process or handoff
>          the connection

So, if I proceed with this option why not use RFC1078 to implement it? 
Why write a new RFC if there's an old one that fits the bill?

>
>      - subservice on different ports
>          determine what subservice you want to initiate,
>          start it on an ephemeral port, and indicate the
>          port number in-band (e.g., as with FTP and others)

Martin


From sustrik@250bpm.com  Thu Aug 22 00:47:08 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D53511E80F9 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 00:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFjot6pxl1AA for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 00:46:55 -0700 (PDT)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8585121F9425 for <ietf@ietf.org>; Thu, 22 Aug 2013 00:46:55 -0700 (PDT)
Received: from [192.168.0.100] (ip66.bbxnet.sk [91.219.133.66]) by mail.moloch.sk (Postfix) with ESMTPSA id BF1151803555; Thu, 22 Aug 2013 09:46:54 +0200 (CEST)
Message-ID: <5215C1EE.9030208@250bpm.com>
Date: Thu, 22 Aug 2013 09:46:54 +0200
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130804 Thunderbird/17.0.8
MIME-Version: 1.0
To: Bob Braden <braden@isi.edu>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <521500DB.9040203@isi.edu>
In-Reply-To: <521500DB.9040203@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 07:47:08 -0000

On 21/08/13 20:03, Bob Braden wrote:

> Indeed, TCPMUX is quite historic... it represents a Road Not Taken. My
> memory is a bit hazy after 30+ years,
> but I think there was a serious discussion around 1979 of using strings
> instead of contact port numbers
> for opening TCP connections. Here is the hazy part... I *think* that
> Chaosnet used strings, and two
> well known MIT Daves introduced a proposal to adopt this mechanism for
> TCP. (Also, maybe XNS
> used strings? Not sure about that...) The internet working group
> ultimately rejected the idea, I think when Jon Postel argued that
> contact ports provided greater conceptual economy.

Hi Bob, thanks for historic insight. Btw, do you remember why TCPMUX was 
even defined given the above sentiment?

> Maybe I got this wrong, but in any case I hope that someone else who was
> in the room then will correct me. Jack? Vint? Dave?  Danny?

Martin


From mansaxel@besserwisser.org  Thu Aug 22 01:01:05 2013
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 697DE11E815C for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 01:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3nTQjeZGuEi for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 01:01:05 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id DD8F011E810D for <ietf@ietf.org>; Thu, 22 Aug 2013 01:01:04 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 3B2AE9E99; Thu, 22 Aug 2013 10:01:03 +0200 (CEST)
Date: Thu, 22 Aug 2013 10:01:03 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Message-ID: <20130822080102.GK30516@besserwisser.org>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <1978913.hEkO1ZYpDI@scott-latitude-e6320> <20130821222635.GJ30516@besserwisser.org> <47490907.LpnmdQ5uG4@scott-latitude-e6320>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vbzKE9fGfpHIBC6T"
Content-Disposition: inline
In-Reply-To: <47490907.LpnmdQ5uG4@scott-latitude-e6320>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 08:01:05 -0000

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

Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender=
 Policy?Framework (SPF) for Authorizing Use of Domains in Email, Version 1)=
 to Proposed Standard Date: Thu, Aug 22, 2013 at 12:23:56AM -0400 Quoting S=
cott Kitterman (scott@kitterma
> On Thursday, August 22, 2013 00:26:35 M=C3=A5ns Nilsson wrote:
> ...
> > SPF is a flagship case for the "use a TXT record and continue to IPO"
> > fast and sloppy crowd. It needs correcting. Badly.
>=20
> Which IPO was that?
>=20
> BTW, in 2003 the choice was use TXT or nothing.  So it was a crowd that w=
anted=20
> to accomplish something and did it the only way it was possible.  Conside=
ring=20
> use of TXT wasn't an important factor in the DKIM last call, I conclude t=
hat=20
> this isn't really about using TXT.

It indeed is -- but SPF is as I wrote above a flagship case. SPF was the
first, is the most deployed (as its supporters repeatedly assert, wringing
their hands, trying to sound apologetical and/or defa=C3=AEtistic) case of
tragedy in the commons that is "automated data processing of content
in comments" and when its proponents try to codify the behaviour of
stampeding into the commons by removing the SPF rrtype, enough is enough.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Are we THERE yet?

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

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

iEYEARECAAYFAlIVxT4ACgkQ02/pMZDM1cV1GgCeIvmgzBqDdrGXQdclxqw+9HvL
SmgAn0rAcJnm1eyduL/p/94K+sQ4qT0H
=Mnhr
-----END PGP SIGNATURE-----

--vbzKE9fGfpHIBC6T--

From Jelte.Jansen@sidn.nl  Thu Aug 22 01:36:37 2013
Return-Path: <Jelte.Jansen@sidn.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 E1B0811E8138 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 01:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.715
X-Spam-Level: 
X-Spam-Status: No, score=-0.715 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T89dahY0BJkG for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 01:36:33 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id C0B5111E80E9 for <ietf@ietf.org>; Thu, 22 Aug 2013 01:36:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=QdAJ21k/ei9KnSnCSRNqKGev4LvIEl2uBw1bAbjUNRs=; b=xh0yL/kkoHPQnNwWCxdYVoEqzftY28HZ/4H7aWtZ6ZJi2xezWTrlfjPtWUYCZG3FrLzYaYOj9Ok6EAr15LR6AbpKQIsbwSam94YtsDoBs2Qp6pfm/tHc7sSbHuWicCnZzfc0TtEGeXQ2JE5nCRELbuKDpsA9b8I6HdcWN5KYoGU=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by ede1-kamx.sidn.nl  with ESMTP id r7M8aTBU027705-r7M8aTBW027705 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Thu, 22 Aug 2013 10:36:29 +0200
Received: from [94.198.152.217] (94.198.152.217) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Thu, 22 Aug 2013 10:36:29 +0200
Message-ID: <5215CD8D.3080302@sidn.nl>
Date: Thu, 22 Aug 2013 10:36:29 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info> <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com>
In-Reply-To: <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.217]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 08:36:38 -0000

On 08/21/2013 08:44 PM, Olafur Gudmundsson wrote:
> 
> Most of the recent arguments against SPF type have come down to the following (as far as I can tell): 
> 	a) I can not add SPF RRtype  via my provisioning system into my DNS servers
> 	b) My firewall doesl not let SPF Records through 
> 	c) My DNS library does not return SPF records through or does not understand it, thus the application can not receive it.
> 	d) Looking up SPF is a waste of time as they do not get through, thus we only look up TXT
> 
> So what I have taken from this is that the DNS infrastructure is agnostic to RRtype=99 but the 
> edges have problems. 
> As to the arguments 7 years is not long enough to reach conclusion and force the changes through the
> infrastructure and to the edges. The "need" for SPF has been blunted by the "DUAL SPF/TXT" strategy and 
> thus we are basically in the place where the path of lowest-resistence has taken us. 
> 
> What I want the IESG to add a note to the document is that says something like the following: 
> "The retirement of SPF from specification is not to be taken that new RRtypes can not be used by applications, 
> the retirement is consequence of the dual "quick-deploy" strategy. The IETF will continue to advocate application 
> specific RRtypes applications/firewalls/libraries SHOULD support that approach."
> 

So what makes you think the above 4 points will not be a problem for the
next protocol that comes along and needs (apex) RR data? And the one
after that?

While I appreciate the argument 'this works now, and it is used'
(running code, and all that), I am very worried that we'll end up with
what is essentially a free-form blob containing data for several
protocols at the zone apexes instead of a structured DNS.

So if this approach is taken, I suggest the wording be much stronger, in
the hope this chicken/egg problem (with 5 levels of eggs. or chickens)
will be somewhat mitigated at some point. Preferably with some
higher-level strategy to support that goal.

Jelte

From presnick@qti.qualcomm.com  Thu Aug 22 07:26:20 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9655511E81BA for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:26:20 -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 X50+M06HEUvH for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:26:16 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 405D011E81B8 for <ietf@ietf.org>; Thu, 22 Aug 2013 07:26:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377181576; x=1408717576; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=0YXxSdhQegdO6A3doklH1EkF4IxyCjFuq5m8lARFoV8=; b=tuZprFczgFoZpXZLGBIcXcAS3Ao4X6wOabP5GkksTkdvFaYGa2MuHBt7 e/yeFnl/2PU2ZQVMxtweVIAzr+DNunpM8/PHhXDnu2bRVwBGW2VcvkaYg tBjq1T7GuYABjlmAxgXSnKvX43NuqD6AVbWQheeoGn34jrAPs4PzEhR+q s=;
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="50105150"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 22 Aug 2013 07:26:15 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="499940068"
Received: from nasanexhc01.na.qualcomm.com ([172.30.48.25]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Aug 2013 07:26:14 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC01.na.qualcomm.com (172.30.48.25) with Microsoft SMTP Server (TLS) id 14.3.146.2; Thu, 22 Aug 2013 07:22:41 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.146.2; Thu, 22 Aug 2013 07:22:41 -0700
Message-ID: <52161EB1.6010506@qti.qualcomm.com>
Date: Thu, 22 Aug 2013 09:22:41 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <dcrocker@bbiw.net>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>	<52150722.1070307@dcrocker.net>	<52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>	<52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net>
In-Reply-To: <521533DB.4040001@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 14:26:20 -0000

On 8/21/13 4:40 PM, Dave Crocker wrote:
> On 8/21/2013 12:46 PM, Pete Resnick wrote:
>> It is not your complaint about the imposition of new requirements that
>> is problematic, or your point that it is not useful to continue that
>> line of discussion. Talk about the utility of a comment all that you
>> want. It is the sarcasm and the rudeness that I am saying is
>> unreasonable. Especially coming from a senior member of the community,
>
> OK.  No sarcasm in IETF postings.  Good luck with that.

Luckily, again, that's not what I said or intended.

Some evidence to the contrary, the IETF is a human endeavor. It involves 
interactions among people. So there will be sarcasm, and humor, and loss 
of temper, and comments with all sorts of embedded meanings. Sometimes 
these things lighten the mood, make the conversation more interesting, 
cause people to think about things in different ways, and contribute to 
the interaction. Sometimes they can have seriously problematic effects. 
Sometimes it will be unclear. And, even though some of our ranks appear 
to want it to be otherwise, there are no nice engineering specs for 
this. It's all very contextual, and is going to depend on the speakers 
and the listeners and the topic of conversation. Social interactions are 
complicated that way.

But there is something going on in the present thread, and in particular 
the mode of communication I objected to here, that I think warrants 
pushback:

> More seriously...
>
> You might have noticed that there have been a variety of folk making 
> unrealistic or misguided suggestions and that they have been receiving 
> entirely muted and exploratory -- albeit negative -- responses.
>
> The implication that I think you've missed here is the obligation that 
> should hold for a 'senior' participant who is lodging concerns.  The 
> current thread is being tenaciously pursued by another "senior" member 
> and former AD and the line of objections and requirements being put 
> forward are studiously ignoring the considerable efforts of the 
> working group and the considerable practical field history.
>
> As such, they represent their own form of disrespect.

I used the word "bullying" with regard to your particular message for a 
very specific reason. Bullying is normally using one's position of power 
to intimidate. I want to circle back a bit to the particulars of the SPF 
discussion:

The SPFBIS WG came to the conclusion regarding deprecating the use of RR 
99 through a very long discussion. There was an extensive review of 
data. (Indeed, there was some initial reluctance in the WG to do as much 
research into the numbers as was eventually done, and I think in the end 
everyone was glad that the WG did do as much work as it did on the 
topic.) There was an extensive discussion of the implications of all of 
the choices. And, with some rough edges, the WG pretty solidly convinced 
itself that it had chosen the right path. And not just that: The WG 
convinced both chairs that they had chosen the right path (one of the 
chairs being the chair of DNSEXT). And they convinced the responsible 
AD. And during WGLC they even convinced the responsible AD for DNSEXT, 
who was originally quite opposed, that the decision was well-considered 
and the correct one in the end. And I believe none of these folks were 
convinced because opposing views were kicked out of the conversation; 
data was presented and explanations were made, and they were convinced. 
Solid consensus was reached, such that as the eventual consensus caller, 
I am quite sure that I'm going to have to see a very carefully reasoned 
new argument in order for me to think that something was missed by this 
WG. Anyone currently outside of the consensus has a pretty high bar to 
clear; they are at a significant disadvantage in the conversation if 
they have an important point to make.

So, now at the point of IETF LC, the correct thing to happen is to let 
folks make their objections, point them to places in the prior 
conversation where the WG, the chairs, the ADs, and assorted other folks 
became convinced, and see if their arguments have some new subtlety that 
was missed earlier. And try to explain. Remember, these folks are 
already at a disadvantage; they've got an uphill climb to convince 
anyone else (especially, me and the rest of the IESG) that this 
long-considered conclusion is incorrect. IMO, that's the time to cut 
them as much slack as possible, because if they do have a serious 
objection hidden in among things that we've seen before, we *all* should 
want to hear it.

But that's not what's gone on. Some folks have simply dismissively said, 
"Go read the archive", without pointers. I found that 
less-than-collegial, and the more dismissive folks I dropped a private 
note asking them to cool it. The dismissiveness AFAICT simply encourages 
people to post more comments without looking at the previous 
conversation. But your note went above and beyond. The sarcasm was sharp 
and directed. It seemed intent on ridiculing. And coming from someone 
who is already on the side of the called consensus (the side that "has 
already won", though I dislike that formulation), directed to another 
senior member of the community with a great deal more experience in the 
DNS end of the world who has (perhaps unjustified or poorly-informed) 
worries that something was missed, I think it was pretty seriously 
ill-spirited and bullying. The *presumption* was that the person was 
"studiously ignorant", that he was being willfully blind of the prior 
conversation and refused to see the obvious. And the response has the 
side effect that anyone else who thinks they may see something that was 
missed had better back off lest they suffer similar attack.

Yes, coming to consensus on contentious issues is hard work. And now in 
the days of the IETF stovepiping, with cross area review not happening 
like it did in the past, contentious issues that cross areas and WGs are 
all the harder to get consensus around. And all I say is, "Tough." We 
have a Last Call process because we expect that not everyone can 
participate cross-area as much as we'd like, and we do want to do a 
final raking-over-the-coals to make sure nothing was missed. We need to 
figure out how to do that better, not use intimidation tactics that will 
cause the final review to not take place at all.

So, I think there's a significant difference between the time used 
(perhaps wasted) by people who are not up to speed and the "disrespect" 
that that implies, and the use of argument tactics by folks who have the 
presumption of having "won the argument". I'm much more willing to cut 
the former more slack.

---

That's all I really want to say on this topic. I won't begrudge you if 
you want to answer any of the above and defend yourself publicly, but 
I'll take any other comments I have to private email. I need to spend 
some time now going through the thread and make sure that all of the 
arguments being brought up *have* in fact been previously answered (a 
job made more difficult because folks were dismissive instead of 
providing pointers to early WG discussion where the arguments were 
answered) and summarize some conclusions. That way the people who think 
they still have objections have a chance to say, "No, Pete, you missed 
my point. There *is* a new argument hiding in there." And then I can 
make some judgments on that. That is, push the discussion to conclusion, 
not just shut it down.

pr

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


From hsantos@isdg.net  Thu Aug 22 07:30:02 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 892C711E80F0 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.311
X-Spam-Level: 
X-Spam-Status: No, score=-102.311 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IT8+1UKV51UL for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:29:56 -0700 (PDT)
Received: from listserv.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2FC11E81D7 for <ietf@ietf.org>; Thu, 22 Aug 2013 07:29:54 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1494; t=1377181784; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Q3cu9KKT3mTJbZxXrX2LyZWwVK4=; b=oWVfuo7dtHzStROtZDqq X78f1/uK9gL4M0CA27yP/U9O4a/4OnCpoxp8jPG9kaGd8sAVKE0AH0vjjmf+Ib4U xYDOtz8Bnwzrb/Y710EooRpJGKiopMPdz9NUvYHn3JMrq+v8n4ELhc6v4m4RnMLu USxCKA+zSf4QX7i40hLSDWc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 22 Aug 2013 10:29:44 -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 3644299109.1759.2856; Thu, 22 Aug 2013 10:29:43 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1494; t=1377181474; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=DHliyEq HXQ1ddZo415vzVLVPztFknB9hso/BE86HZJU=; b=KjkEfTnkzbIkPU17JhRmYWL WARbiAMxTmbplXwX0fBj1yjxP4kO7rZHpxpQx7JhUMhdpOhMIZd0T3T3YY22ZA8V HJ4Cw+kcioaxoxarBXYsH5+WtRcvQrLWp8+Zfm4Ia/1dW2bCNHPXgGzmq8qyQ5OQ Eq5WzjnDadGpNd6t3wk4=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 22 Aug 2013 10:24:34 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3090722268.9.4936; Thu, 22 Aug 2013 10:24:33 -0400
Message-ID: <52162051.6060702@isdg.net>
Date: Thu, 22 Aug 2013 10:29:37 -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: S Moonesamy <sm+ietf@elandsys.com>
Subject: SPFBIS LAST CALL: SenderID Framework (PRA, SUBMITTER) 
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, IETF General 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, 22 Aug 2013 14:30:02 -0000

Hi SM,

Besides the SPF type issue, I believe there are still a number of 
integrated protocol issues to address.  How does the following RFCs 
play into SPFBIS output, the SPF type and the overall BIS document? 
Should RFC4408BIS update any of these documents?

[1] RFC4405  SUBMITTER SMTP Service Extension
[2] RFC4406  Sender ID: Authenticating E-Mail
[3] RFC4407  Purported Responsible Address (PRA)

For example:

In RFC 4406 (SenderID), section 3.1 says:

    This section replaces the definition of the version identifier in
    Section 4.5 of [RFC4408] and adds the concept of SPF record scopes.

In section 4.4, item 1:

    1. If any records of type SPF are in the set, then all records of
       type TXT are discarded.

Overall,

1) Do SenderID publishers need to drop the SPF type as well?

2) Do PRA/SUBMITTER compliant receivers need to also drop SPF type 
queries?

3) Do SMTP vendors need to begin dropping SUBMITTER as well?

Procedurally, does SPFBIS need to address or take over these multiple 
protocols integration concerns (including SMTP SUBMITTER receivers) or 
should it just remain silent and allow vendors make a guess at all 
this?  What is the SPF summary in this regard for the application 
integrator?

Should the IETF consider a new SenderID WG to discuss what are the 
repercussions the SPFBIS results have on it?


--
HLS

[1] http://tools.ietf.org/html/rfc4405
[2] http://tools.ietf.org/html/rfc4406
[3] http://tools.ietf.org/html/rfc4407



From ogud@ogud.com  Thu Aug 22 07:39:58 2013
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7B511E81CE for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 906u6RXbnLWc for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:39:53 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) by ietfa.amsl.com (Postfix) with ESMTP id 8FBEB11E81D7 for <ietf@ietf.org>; Thu, 22 Aug 2013 07:39:48 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 42BD11401CD; Thu, 22 Aug 2013 10:39:47 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id DB4721400DA;  Thu, 22 Aug 2013 10:39:40 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <5215CD8D.3080302@sidn.nl>
Date: Thu, 22 Aug 2013 10:39:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAF76B13-BAFF-44B8-9D71-64C9AF1FAED1@ogud.com>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info> <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com> <5215CD8D.3080302@sidn.nl>
To: Jelte Jansen <jelte.jansen@sidn.nl>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 14:39:58 -0000

On Aug 22, 2013, at 4:36 AM, Jelte Jansen <jelte.jansen@sidn.nl> wrote:

> On 08/21/2013 08:44 PM, Olafur Gudmundsson wrote:
>>=20
>> Most of the recent arguments against SPF type have come down to the =
following (as far as I can tell):=20
>> 	a) I can not add SPF RRtype  via my provisioning system into my =
DNS servers
>> 	b) My firewall doesl not let SPF Records through=20
>> 	c) My DNS library does not return SPF records through or does =
not understand it, thus the application can not receive it.
>> 	d) Looking up SPF is a waste of time as they do not get through, =
thus we only look up TXT
>>=20
>> So what I have taken from this is that the DNS infrastructure is =
agnostic to RRtype=3D99 but the=20
>> edges have problems.=20
>> As to the arguments 7 years is not long enough to reach conclusion =
and force the changes through the
>> infrastructure and to the edges. The "need" for SPF has been blunted =
by the "DUAL SPF/TXT" strategy and=20
>> thus we are basically in the place where the path of =
lowest-resistence has taken us.=20
>>=20
>> What I want the IESG to add a note to the document is that says =
something like the following:=20
>> "The retirement of SPF from specification is not to be taken that new =
RRtypes can not be used by applications,=20
>> the retirement is consequence of the dual "quick-deploy" strategy. =
The IETF will continue to advocate application=20
>> specific RRtypes applications/firewalls/libraries SHOULD support that =
approach."
>>=20
>=20
> So what makes you think the above 4 points will not be a problem for =
the
> next protocol that comes along and needs (apex) RR data? And the one
> after that?
>=20

There are two reasons, mail is a legacy application with lots of old =
cruft around it.=20
New protocols on the other hand can start with clean slate, and the use =
of the protocol is
optional unlike email.=20
With a new protocol you can tell someone "you can not use Vendor X as it =
does not support Y"=20
and they will put up a system that works, for email there is installed =
base and enterprise policies to use
Vendor X then SPF RR can not be used.=20


> While I appreciate the argument 'this works now, and it is used'
> (running code, and all that), I am very worried that we'll end up with
> what is essentially a free-form blob containing data for several
> protocols at the zone apexes instead of a structured DNS.
>=20
> So if this approach is taken, I suggest the wording be much stronger, =
in
> the hope this chicken/egg problem (with 5 levels of eggs. or chickens)
> will be somewhat mitigated at some point. Preferably with some
> higher-level strategy to support that goal.
>=20
> Jelte


I agree=20

	Olafur


From fluffy@cisco.com  Thu Aug 22 07:53:59 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38A0D21F8C65; Thu, 22 Aug 2013 07:53:59 -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 hRnuKol527+9; Thu, 22 Aug 2013 07:53:54 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC4911E814C; Thu, 22 Aug 2013 07:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8522; q=dns/txt; s=iport; t=1377183233; x=1378392833; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=f+RmQwZtHNuntTRrbzz1nY1goo82KHanVN/FKGv9lwA=; b=eoR3I9OM/LNm5eQQsHcvB5EO1dAkUDzOicWMWYF4DLHzTcXPh/5xVo+c /TYNbnyUvGo+J2+Emn3HZAM5tNqnESDCMH4xApEidecD3lPMip+8DWRJl mOjdNmam8Qf7v2szfU8iGteoCsa1MiT2RRLzWQjwgAkiYWsgeKAPXtpZf c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao0FANwlFlKtJXG//2dsb2JhbABOAwmDBTVRwAiBHBZtB4IkAQEBAwEBAQEaHR8VCwULAgEIIgISECcLJQIEDgMCCAESh28GDK8PjxgBBAcDBoEGAjEHgxt7A5NMQZUzgx9AgSkCBxcCBBw
X-IronPort-AV: E=Sophos;i="4.89,934,1367971200"; d="scan'208";a="250458678"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 22 Aug 2013 14:53:39 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r7MErdno007150 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 22 Aug 2013 14:53:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.221]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Thu, 22 Aug 2013 09:53:38 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: WG Review: Secure Telephone Identity Revisited (stir)
Thread-Topic: WG Review: Secure Telephone Identity Revisited (stir)
Thread-Index: AQHOn0diLpFeqm1CkkWDY3sxz5Amcg==
Date: Thu, 22 Aug 2013 14:53:38 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11491F2E2@xmb-aln-x02.cisco.com>
References: <20130821175202.24713.10458.idtracker@ietfa.amsl.com>
In-Reply-To: <20130821175202.24713.10458.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D4FE62ADDE630C41A76CDB4E49BF950A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: stir WG <stir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 14:53:59 -0000

This looks reasonable to me and given how much effort it has taken to get a=
greement on theses words, I am not keen on any of the material changes I ha=
ve seen proposed.


On Aug 21, 2013, at 11:52 AM, The IESG <iesg-secretary@ietf.org> wrote:

> A new IETF working group has been proposed in the Real-time Applications
> and Infrastructure Area. The IESG has not made any determination yet. The
> following draft charter was submitted, and is provided for informational
> purposes only. Please send your comments to the IESG mailing list (iesg
> at ietf.org) by 2013-08-28.
>=20
> Secure Telephone Identity Revisited (stir)
> ------------------------------------------------
> Current Status: Proposed WG
>=20
> Chairs:
>  TBD
>=20
> Assigned Area Director:
>  Richard Barnes <rlb@ipv.sx>
>=20
> Mailing list
>  Address: stir@ietf.org
>  To Subscribe: https://www.ietf.org/mailman/listinfo/stir
>  Archive: http://www.ietf.org/mail-archive/web/stir/
>=20
> Charter:
>=20
> The STIR working group will specify Internet-based mechanisms that allow=
=20
> verification of the calling party's authorization to use a particular=20
> telephone number for an incoming call.  Since it has  become fairly easy=
=20
> to present an incorrect source telephone number, a growing set of=20
> problems have emerged over the last decade.  As with email, the claimed=20
> source identity of a SIP request is not verified, permitting unauthorized
>=20
> use of the source identity as part of deceptive and coercive activities,=
=20
> such as robocalling (bulk unsolicited commercial communications), vishing
>=20
> (voicemail hacking, and impersonating banks) and swatting (impersonating=
=20
> callers to emergency services to stimulate unwarranted large scale law=20
> enforcement deployments).  In addition, use of an incorrect source=20
> telephone number facilitates wire fraud or can lead to a return call at=20
> premium rates. =20
>=20
> SIP is one of the main VoIP technologies used by parties that want to
> present an incorrect origin, in this context an origin telephone number.
> Several previous efforts have tried to secure the origins of SIP
> communications, including RFC 3325, RFC 4474, and the VIPR working group.
> To date, however, true validation of the source of SIP calls has not seen
> any appreciable deployment.  Several factors contributed to this lack of
> success, including: failure of the problem to be seen as critical at the
> time; lack of any technical means of producing a proof of authorization
> to
> use telephone numbers; misalignment of the mechanisms proposed by RFC
> 4474
> with the complex deployment environment that has emerged for SIP; lack of
> end-to-end SIP session establishment; and inherent operational problems
> with a transitive trust model.  To make deployment of this solution more
> likely, consideration must be given to latency, real-time performance,
> computational overhead, and administrative overhead for the legitimate
> call source and all verifiers.
>=20
> As its priority mechanism work item, the working group will specify a SIP
> header-based mechanism for verification that the originator of a SIP=20
> session is authorized to use the claimed source telephone number, where=20
> the session is established with SIP end to end.  This is called an
> in-band=20
> mechanism. The mechanism will use a canonical telephone number=20
> representation specified by the working group, including any mappings
> that=20
> might be needed between the SIP header fields and the canonical telephone
>=20
> number representation.  The working group will consider choices for=20
> protecting identity information and credentials used.  This protection=20
> will likely be based on a digital signature mechanism that covers a set=20
> of information in the SIP header fields, and verification will employ a=20
> credential that contains the public key that is associated with the one=20
> or more telephone numbers.  Credentials used with this mechanism will be=
=20
> derived from existing telephone number assignment and delegation models.=
=20
>=20
> That is, when a telephone number or range of telephone numbers is=20
> delegated to an entity, relevant credentials will be generated (or=20
> modified) to reflect such delegation.  The mechanism must allow a=20
> telephone number holder to further delegate and revoke use of a telephone
>=20
> number without compromising the global delegation scheme.
>=20
> In addition to its priority mechanism work item, the working group will
> consider a mechanism for verification of the originator during session
> establishment in an environment with one or more non-SIP hops, most
> likely requiring an out-of-band authorization mechanism.  However, the
> in-band and the out-of-band mechanisms should share as much in common as
> possible, especially the credentials.  The in-band mechanism must be sent
> to the IESG for approval and publication prior to the out-of-band
> mechanism.
>=20
> Expansion of the authorization mechanism to identities using the
> user@domain form is out of scope.  The work of this group is limited to
> developing a solution for telephone numbers.
>=20
> The working group will coordinate with the Security Area on credential
> management.
>=20
> The working group will coordinate with other working groups in the RAI
> Area regarding signaling through existing deployments.
>=20
> The working group welcomes input from potential implementors or operators
>=20
> of technologies developed by this working group.  For example, national=20
> numbering authorities might consider acting as credential authorities for
>=20
> telephone numbers within their purview.
>=20
> It is important to note that while the main focus of this working group
> is telephone numbers, the STIR working group will not develop any
> mechanisms that require changes to circuit-switched technologies.
>=20
> Authentication and authorization of identity is closely linked to
> privacy, and these security features sometimes come at the cost of
> privacy.  Anonymous calls are already defined in SIP standards, and this
> working group will not propose changes to these standards.  In order to
> support anonymity, the working group will provide a solution in which the
> called party receives an indication that the source telephone number is
> unavailable.  This working group, to the extent feasible, will specify
> privacy-friendly mechanisms that do not reveal any more information to
> user agents or third parties than a call that does not make use of secure
> telephone identification mechanisms.
>=20
> Input to working group discussions shall include:
>=20
>  - Private Extensions to the Session Initiation Protocol (SIP)
>    for Asserted Identity within Trusted Networks
>    [RFC 3325]
>=20
>  - Enhancements for Authenticated Identity Management in the
>    Session Initiation Protocol (SIP)
>    [RFC 4474]
>=20
>  - Secure Call Origin Identification
>    [draft-cooper-iab-secure-origin-00]
>=20
>  - Secure Origin Identification: Problem Statement, Requirements,
>    and Roadmap
>    [draft-peterson-secure-origin-ps-00]
>=20
>  - Authenticated Identity Management in the Session Initiation
>    Protocol (SIP)
>    [draft-jennings-dispatch-rfc4474bis-00]
>=20
> The working group will deliver the following:
>=20
>  - A problem statement detailing the deployment environment and
>    situations that motivate work on secure telephone identity
>=20
>  - A threat model for the secure telephone identity mechanisms
>=20
>  - A privacy analysis of the secure telephone identity mechanisms
>=20
>  - A document describing the SIP in-band mechanism for telephone
>    number-based identities during call setup
>=20
>  - A document describing the credentials required to support
>    telephone number identity authentication
>=20
>  - A document describing the out-of-band mechanism for telephone
>    number-based identities during call setup
>=20
> Milestones
>=20
> Sep 2013   Submit problem statement for Informational
> Nov 2013   Submit threat model for Informational
> Nov 2013   Submit in-band mechanism for Proposed Standard
> Feb 2014   Submit credential specification for Proposed Standard
> Apr 2014   Submit Privacy analysis for Informational
> Jun 2014   Submit out-of-band mechanism for Proposed Standard
>=20


From scott.brim@gmail.com  Thu Aug 22 07:54:20 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A52E211E80FB for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.245
X-Spam-Level: 
X-Spam-Status: No, score=-101.245 tagged_above=-999 required=5 tests=[AWL=1.354, 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 VeIl6wp125EN for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 07:54:20 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id A5A2C11E81D9 for <ietf@ietf.org>; Thu, 22 Aug 2013 07:54:15 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id er7so3812046obc.31 for <ietf@ietf.org>; Thu, 22 Aug 2013 07:54:15 -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=xXV8IQjxCQqjIcfTprFxsZt1UZQrxI3VCjADO5fCSPM=; b=G325NukWonJQc3lJYFbTp6xqisEvB4PILgnBObnQ4+DAlomFzus004nCLa8YlSqIc+ IxygwsyjXwz//8Hmy1cr2yfwZN/GTUkk04M8mhWXcYgLFYURiNUR54sclA3QYNXPZy4c x+VHYgjh1FG/Ivdrfu4NktBHwsmbb0CyIzbB8jsr6J+EIduqNP7I0emtlAe+RW1c2Otg lDKx8t2DpDzVE4hJrDDynB+l6eQTydPXbUyH9bpb/Uf1cgdYq1nU9u5XceC0fm33KXqG mW9tgjkYsAQuh8C7QFAIZi/Ehssrf+wvOxHmBsGsgUf/1BWDAecFlCu+y0mangIh/FuQ ka9w==
X-Received: by 10.60.161.136 with SMTP id xs8mr3036385oeb.77.1377183255134; Thu, 22 Aug 2013 07:54:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Thu, 22 Aug 2013 07:53:55 -0700 (PDT)
In-Reply-To: <52161EB1.6010506@qti.qualcomm.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 22 Aug 2013 10:53:55 -0400
Message-ID: <CAPv4CP-hRRU21-fLNDJaFGSaBoWHwyhoACta+3xSoTiJtOdxkA@mail.gmail.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,  Version 1) to Proposed Standard)
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e01183a18b6903c04e48a762d
Cc: Crocker Dave <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 14:54:20 -0000

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

On Thu, Aug 22, 2013 at 10:22 AM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> Some folks have simply dismissively said, "Go read the archive", without
> pointers.


Pete, I like your position, but I believe "go read the archive" or the
equivalent will continue to be a standard response unless someone is
responsible for giving a more thorough response. Who do you think that
should be?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Aug 22, 2013 at 10:22 AM, Pete Resnick <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">presnick@qti.qualc=
omm.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">Some folks have simply dismissively said, &q=
uot;Go read the archive&quot;, without pointers. </blockquote></div><br>Pet=
e, I like your position, but I believe &quot;go read the archive&quot; or t=
he equivalent will continue to be a standard response unless someone is res=
ponsible for giving a more thorough response. Who do you think that should =
be?</div>

</div>

--089e01183a18b6903c04e48a762d--

From narten@us.ibm.com  Thu Aug 22 08:01:53 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6901511E81AF for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:01:53 -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 g-nlfH55e6xb for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:01:46 -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 85ECF11E80D5 for <ietf@ietf.org>; Thu, 22 Aug 2013 08:01:46 -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>; Thu, 22 Aug 2013 16:01:41 +0100
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 22 Aug 2013 16:01:39 +0100
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 76DF138C8027 for <ietf@ietf.org>; Thu, 22 Aug 2013 11:01:36 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7MF1bU7105488 for <ietf@ietf.org>; Thu, 22 Aug 2013 11:01:37 -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 r7MF1bRW009695 for <ietf@ietf.org>; Thu, 22 Aug 2013 12:01:37 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-65-36-34.mts.ibm.com [9.65.36.34]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7MF1Zwu009543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 12:01:36 -0300
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r7MF140K015920; Thu, 22 Aug 2013 11:01:04 -0400
Message-Id: <201308221501.r7MF140K015920@cichlid.raleigh.ibm.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
In-reply-to: <CAC4RtVDM4N9=cGyP+RGkv39=qBuJN04PLUubHMwUDfsqM7uJng@mail.gmail.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <CAC4RtVDM4N9=cGyP+RGkv39=qBuJN04PLUubHMwUDfsqM7uJng@mail.gmail.com>
Comments: In-reply-to Barry Leiba <barryleiba@computer.org> message dated "Wed, 21 Aug 2013 18:13:06 -0400."
Date: Thu, 22 Aug 2013 11:01:04 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13082215-0320-0000-0000-000000C4E2DD
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, 22 Aug 2013 15:01:53 -0000

Barry Leiba <barryleiba@computer.org> writes:

> The general point is that the new people whom we want
> to draw in as productive participants will be watching how we treat
> each other and deciding whether they want to wade into that pool.

It's not just new people watching and being turned off.  There are
plenty of old timers who get turned off and I doubt I'm alone in
thinking very carefully these days whether I want to wade into any
particular discussion.

Thomas


From presnick@qti.qualcomm.com  Thu Aug 22 08:02:49 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4E821F9C34 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:02:49 -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 AN3ZI6iIDHYq for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:02:44 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id B1E3521F898A for <ietf@ietf.org>; Thu, 22 Aug 2013 08:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377183756; x=1408719756; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bwj5NvuCtOoasxK91aUqwi6u3nHFQnCfv9aSd3OG3ao=; b=SFyg3LBk0+s1VW5Gb7yxq+wXGkH/ZOl6dGh977fCbk6pBH1Cne6klxs8 QeH4EBFpUFQxo+RqY+1y4pBp2/RoyWYcg6emBzBc5GqUQy99NnlB5szOa DKoAzsed3+odbsasRY8M0EeTxncVDnTBgt1gq7J+HJpbc3teR+7hfRWCk s=;
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="50106935"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 22 Aug 2013 08:02:20 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7174"; a="18358622"
Received: from nasanexhc16.na.qualcomm.com ([10.45.158.213]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Aug 2013 08:02:20 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc16.na.qualcomm.com (10.45.158.213) with Microsoft SMTP Server (TLS) id 14.3.146.2; Thu, 22 Aug 2013 08:02:19 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.146.2; Thu, 22 Aug 2013 08:02:19 -0700
Message-ID: <521627FC.5010900@qti.qualcomm.com>
Date: Thu, 22 Aug 2013 10:02:20 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,  Version 1) to Proposed Standard)
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>	<52150722.1070307@dcrocker.net>	<52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>	<52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net>	<52161EB1.6010506@qti.qualcomm.com> <CAPv4CP-hRRU21-fLNDJaFGSaBoWHwyhoACta+3xSoTiJtOdxkA@mail.gmail.com>
In-Reply-To: <CAPv4CP-hRRU21-fLNDJaFGSaBoWHwyhoACta+3xSoTiJtOdxkA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 15:02:49 -0000

OK, direct question; I'll take the (short) time to give a direct answer.

On 8/22/13 9:53 AM, Scott Brim wrote:
> Pete, I like your position, but I believe "go read the archive" or the 
> equivalent will continue to be a standard response unless someone is 
> responsible for giving a more thorough response. Who do you think that 
> should be?

It would be a bummer if it is entirely left to the AD/consensus caller 
or the chair/shepherd, but unfortunately "the buck stops here", as they 
say. Eventually, it should be everyone's responsibility to help their 
colleagues. But obviously my rose-colored glasses are especially rosy 
today, other evidence to the contrary notwithstanding.

pr

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


From touch@isi.edu  Thu Aug 22 08:02:50 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B415E21F9D5F for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:02:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.39
X-Spam-Level: 
X-Spam-Status: No, score=-106.39 tagged_above=-999 required=5 tests=[AWL=0.209, 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 Hozg7-zICXcb for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:02:44 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 35D5521F9A4C for <ietf@ietf.org>; Thu, 22 Aug 2013 08:02:44 -0700 (PDT)
Received: from [192.168.1.92] (pool-71-105-85-4.lsanca.dsl-w.verizon.net [71.105.85.4]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7MEvjU9029185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 22 Aug 2013 07:57:54 -0700 (PDT)
Message-ID: <521626EC.8070706@isi.edu>
Date: Thu, 22 Aug 2013 07:57:48 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: TCPMUX (RFC 1078) status
References: <5205D2FB.8010205@250bpm.com> <52069498.1000604@mti-systems.com> <520D3779.4050106@isi.edu> <520D7F0D.10905@mti-systems.com> <520DBABA.2000506@250bpm.com> <520E6A55.6010802@isi.edu> <52136288.6090408@250bpm.com> <521384B8.9020505@isi.edu> <52147135.9060705@250bpm.com> <5214D8E7.50002@isi.edu> <5214DD54.60009@250bpm.com> <5214F219.6000506@isi.edu> <5215C15B.3000008@250bpm.com>
In-Reply-To: <5215C15B.3000008@250bpm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: draft-ietf-tcpm-tcp-rfc4614bis@tools.ietf.org, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 15:02:50 -0000

On 8/22/2013 12:44 AM, Martin Sustrik wrote:
> On 21/08/13 19:00, Joe Touch wrote:
>
>>> So what would you use for muxing, if TCPMUX is not a good idea?
>>
>> You need to roll your own. The requirements of systems vary widely, as
>> do the costs/benefits of different approaches.
>>
>> I listed a few before, but here's a more comprehensive list:
>>      - service per message
>>          demux based on message ID
>>          use IPC (interprocess comm) to handoff internal
>>          to your system
>>
>>      - service per connection
>>          demux based on the first message in an
>>          association (TCP or UDP), and either continue to
>>          forward messages to a different process or handoff
>>          the connection
>
> So, if I proceed with this option why not use RFC1078 to implement it?
> Why write a new RFC if there's an old one that fits the bill?

There are two cases to consider:

	- you're creating your own set of services, at which point
	you'll need to roll your own dispatch mechanism

	- you want to use TCPMUX, either for your own services or for
	all services
		you should already realize why that's a dead-end.
		any sysadmin that blocks *any* ports will always
		block TCPMUX

One final reason TCPMUX isn't deployed is that it changes the semantics 
of many existing services, many of which are defined as "if the 
connection opens, then the service is there".

If you roll your own version, you can define your services to accept 
those semantics.

Joe

From ek@google.com  Thu Aug 22 04:22:04 2013
Return-Path: <ek@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B74C511E819E for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 04:22:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 2SF2HeSoAdZp for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 04:22:04 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6035311E81A4 for <ietf@ietf.org>; Thu, 22 Aug 2013 04:22:03 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id ta17so3338088obb.32 for <ietf@ietf.org>; Thu, 22 Aug 2013 04:22:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=bvc1TOFiJ2nJx4hEUrNwPJxXXfm1lVnMtoMnldBnr90=; b=GGRupLOYPz/u+0gQJ+HXsUPUIYPQG9tbFDiRx0uJz0c6LBSugvZxNdmvuUbKQVeiT7 Q8ecqQBGIIgWHsYRKY8GFh6ARDA62czq5xCBGlag+ogzgM7XwxhG8cdmmBc9tovZp3yP RESDflEmR1J0V17PZzle5L8rysoEZ3BK5AdbIT9gbi1ef5fcD4CiGndJjlqZVfl8X+K7 8mahYrXFPO9I+KbeJEbDPxHeRZ91xlzsmoFJNVeAA88keW/916QkJwCxaviqtiCP/WMt EVnACCPdL9/SlrpI/oMqY5YM/qSy/WCdWmMx+Ni3M662wGpdFrMcooTrFc5RfMCA8Hxa lWOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=bvc1TOFiJ2nJx4hEUrNwPJxXXfm1lVnMtoMnldBnr90=; b=oaiiFwOmgWKKw7RAeL4LrySyQkXdgCiwHOX3wPOUOv169kYDO+l7YoX/B48Ow4P0w6 gLwKK6Crxyv+M+szo/rUxw2p64BO6XQ+N5poiCn/AsnfaS5luCWM769k6Ccq2866zr+j bxROyxyIzswKuPyJlMe6oD15hq6pQC53MgI1cGNrFhBLdW/GjV1gjWEglhEcRfILamoH ouNxr/xSSFT7Hpwq/gbj43e8B5T0a0+k/DjNVAufAda+2h37UHm4yvu1YsJfGpP/ofdf Y99ybViKMyHeo0zZ81VBMghxGdr3OUQJ1Ove9a+auFq6J5FQEcX2R9aU496uZ1lsgs4W c83w==
X-Gm-Message-State: ALoCoQn0YMtXS1aybB77my4wgd5t7vbSXQbfV/JGclMWO1zd4hUaxa1vpv+XT0pNd/fdo/LqhnlEXKWL5G6m7s5t9m4xvom+1bInm+koaOFFKxgFqzfXS3JKgNYGYTYTmXTbngDAY7cRb+KBH2GphNv3mz29jXPp9PezYHL9GX6BvdRrQm0yXWh/KEWtw0UKxDqWNhSJ2qkD
X-Received: by 10.60.120.69 with SMTP id la5mr1511908oeb.86.1377170520458; Thu, 22 Aug 2013 04:22:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.56.226 with HTTP; Thu, 22 Aug 2013 04:21:38 -0700 (PDT)
In-Reply-To: <E52BC6E6-DB55-49A5-B3AA-6D57451676ED@delong.com>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com> <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com> <A4B538DE-16B9-45D4-89F3-51441984B12F@apple.com> <E52BC6E6-DB55-49A5-B3AA-6D57451676ED@delong.com>
From: Erik Kline <ek@google.com>
Date: Thu, 22 Aug 2013 20:21:38 +0900
Message-ID: <CAAedzxqsCox1rRo620MzFziBPpq1dAmzN6ZA1bcE0AXJCh_2Lg@mail.gmail.com>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
To: Owen DeLong <owen@delong.com>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Thu, 22 Aug 2013 08:15:29 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 11:22:04 -0000

REQ 1:
    6434 5.9.1 is already a MUST.  This does not need to be repeated.
    6434 5.8 is already a MUST.  Unless you want to make multipart
ICMP a MUST (why?) as well, this too can be removed.

REQ 6:
    re 6434 12.2, this MUST does not appear to be stronger than 12.2's MUST
    frankly even 5.2 reads like MUST for 3GPP, but it does SHOULD so
this MUST appears stronger.  Bizarre, though, I never noticed that "ND
SHOULD" before.

REQ 10:
    this reads kind weird.  In REQ 9 you require 6106 support, but in
REQ 10 you say "if 6106 is not supported."  I think you mean something
like "if the network to which the mobile node is attaching does not
support 6016".

From mohamed.boucadair@orange.com  Thu Aug 22 05:06:03 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A6111E8161; Thu, 22 Aug 2013 05:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.231
X-Spam-Level: 
X-Spam-Status: No, score=-2.231 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 SYpKh815kKAr; Thu, 22 Aug 2013 05:05:58 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 0E16621F9F40; Thu, 22 Aug 2013 05:05:57 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 961293B49A3; Thu, 22 Aug 2013 14:05:56 +0200 (CEST)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 7B80E35C045; Thu, 22 Aug 2013 14:05:56 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.12]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Thu, 22 Aug 2013 14:05:56 +0200
From: <mohamed.boucadair@orange.com>
To: Erik Kline <ek@google.com>
Date: Thu, 22 Aug 2013 14:05:54 +0200
Subject: RE: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
Thread-Index: Ac6fKfikkRu/iW5IQDuqYqlyPwJbBAAA6mxQ
Message-ID: <94C682931C08B048B7A8645303FDC9F36EEEE4E5C7@PUEXCB1B.nanterre.francetelecom.fr>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com> <CAKD1Yr1VpJne1h-Q5xbNMYRhpr_n0Wmn6UqfeG3vEg2MY6ms1g@mail.gmail.com> <A4B538DE-16B9-45D4-89F3-51441984B12F@apple.com> <E52BC6E6-DB55-49A5-B3AA-6D57451676ED@delong.com> <CAAedzxqsCox1rRo620MzFziBPpq1dAmzN6ZA1bcE0AXJCh_2Lg@mail.gmail.com>
In-Reply-To: <CAAedzxqsCox1rRo620MzFziBPpq1dAmzN6ZA1bcE0AXJCh_2Lg@mail.gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.7.26.63617
X-Mailman-Approved-At: Thu, 22 Aug 2013 08:15:36 -0700
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 12:06:03 -0000

Hi Erik,

Thank you for the review.=20

Please see inline.

Cheers,
Med

>-----Message d'origine-----
>De=A0: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] De la part d=
e
>Erik Kline
>Envoy=E9=A0: jeudi 22 ao=FBt 2013 13:22
>=C0=A0: Owen DeLong
>Cc=A0: v6ops@ietf.org; IETF Discussion
>Objet=A0: Re: [v6ops] Last Call: <draft-ietf-v6ops-mobile-device-profile-
>04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile
>Devices) to Informational RFC
>
>REQ 1:
>    6434 5.9.1 is already a MUST.  This does not need to be repeated.

[Med] Because some requirements are stronger in this document than what is =
documented in RFC6434, we had two way to implement this in the document:
(a) Indicate RFC6434 must be supported with the exceptions in the language =
for some requirements listed in this document.
(b) Call out explicitly the requirements from RFC6434 that are mandatory + =
indicate which requirements are stronger than rfc6434.
We decided to go for (b) as it provides a comprehensive list of requirement=
s for 3GPP mobile devices grouped in one single document. IMHO, this is jus=
t a matter of presentation.=20

This rationale is explained in the introduction.


>    6434 5.8 is already a MUST.  Unless you want to make multipart
>ICMP a MUST (why?) as well, this too can be removed.
>
>REQ 6:
>    re 6434 12.2, this MUST does not appear to be stronger than 12.2's MUS=
T
>    frankly even 5.2 reads like MUST for 3GPP, but it does SHOULD so
>this MUST appears stronger.  Bizarre, though, I never noticed that "ND
>SHOULD" before.

[Med] The language is stronger compared to the SHOULD in Section 5.2 of RFC=
6434.

>
>REQ 10:
>    this reads kind weird.  In REQ 9 you require 6106 support, but in
>REQ 10 you say "if 6106 is not supported."  I think you mean something
>like "if the network to which the mobile node is attaching does not
>support 6016".

[Med] Yes, agree. As mentioned in the document,

"   Some of the features listed in this profile document require to
   activate dedicated functions at the network side."

This will be fixed.

From sm@elandsys.com  Thu Aug 22 08:53:57 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B105C11E8211 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lKNUYHkffqUI for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 08:53:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C435311E821C for <ietf@ietf.org>; Thu, 22 Aug 2013 08:53:56 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.102]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7MFrcJG002001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 08:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377186835; bh=ScWBFCMqBAabxTGP5Vd6gZ0s8Fv2F1D/OSnWMdOXZHQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HqzgpMR4WWBdO/8C20oKBa8un3876Rm5MdM2KN/hc1D8nj3JchPk6d5s/nnwVOxDv oFcGHOCrn62zG2r/n+5x5iPrVTRO6fYrmUSg3HVMBM3/YvGdS95uWsjEL/ZQG4EPmZ A8s9Zuna6DG3qe0NMYMJRGsgpZXmiXY96Zu/w8Sc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377186835; i=@elandsys.com; bh=ScWBFCMqBAabxTGP5Vd6gZ0s8Fv2F1D/OSnWMdOXZHQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=X7ijToMULSbv4FhNV8Q7DkRaMVedf2Ae2g/QxUoHyxlW2Mw4yT5In3P8kT0AfR/lO s7ZxozYRIhifSWFl+NvgkT2kSGfi8/IqlPP7RYeHmMOM2T+DXwBHCqICPXXWjo/hln sboK8zPx/UMCMZyf704jfiDofCmM4CLvbhGn2K78=
Message-Id: <6.2.5.6.2.20130822074501.0b7e66b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 22 Aug 2013 08:38:49 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: SPFBIS LAST CALL: SenderID Framework (PRA, SUBMITTER) 
In-Reply-To: <52162051.6060702@isdg.net>
References: <52162051.6060702@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Pete Resnick <presnick@qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 15:53:57 -0000

Hi Hector,
At 07:29 22-08-2013, Hector Santos wrote:
>Besides the SPF type issue, I believe there are still a number of 
>integrated protocol issues to address.  How does the following RFCs 
>play into SPFBIS output, the SPF type and the overall BIS document? 
>Should RFC4408BIS update any of these documents?
>
>[1] RFC4405  SUBMITTER SMTP Service Extension
>[2] RFC4406  Sender ID: Authenticating E-Mail
>[3] RFC4407  Purported Responsible Address (PRA)

I would say no as the above RFCs are not related to 
draft-ietf-spfbis-4408bis-19.  I'll mention the following text from RFC 6686:

   "The experiments comprising the series of RFCs defining the
    SUBMITTER SMTP extension (RFC4405), the Sender ID mechanism
    (RFC4406), the Purported Responsible Address algorithm (RFC4407),
     and SPF (RFC4408), should be considered concluded.

That is the official position of the IETF.  I can state that the text 
reflects the consensus of the SPFBIS WG as I verified whether there 
was working group agreement before requesting the publication of RFC 
6686.  The following text is from RFC 6686:

   "This document is a product of the Internet Engineering Task Force
    (IETF).  It represents the consensus of the IETF community.  It has
    received public review and has been approved for publication by the
    Internet Engineering Steering Group (IESG)."

 From an IETF perspective that's the answer that will be given.

>For example:
>
>In RFC 4406 (SenderID), section 3.1 says:
>
>    This section replaces the definition of the version identifier in
>    Section 4.5 of [RFC4408] and adds the concept of SPF record scopes.
>
>In section 4.4, item 1:
>
>    1. If any records of type SPF are in the set, then all records of
>       type TXT are discarded.
>
>Overall,
>
>1) Do SenderID publishers need to drop the SPF type as well?
>
>2) Do PRA/SUBMITTER compliant receivers need to also drop SPF type queries?
>
>3) Do SMTP vendors need to begin dropping SUBMITTER as well?

Somebody can submit a draft which answers those questions and have it 
discussed in the IETF.  The SPFBIS WG Chairs have mentioned that once 
the work on draft-ietf-spfbis-4408bis is completed the SPFBIS WG will 
be ready to close ( 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg10124.html 
).  I don't think that the SPFBIS WG will take on the draft.  The 
person submitting the draft can contact the Application Area 
Directors to find out where to discuss the draft.

>Procedurally, does SPFBIS need to address or take over these 
>multiple protocols integration concerns (including SMTP SUBMITTER 
>receivers) or should it just remain silent and allow vendors make a 
>guess at all this?  What is the SPF summary in this regard for the 
>application integrator?

Procedurally, the SPFBIS WG does not need to address that (see above 
comments).  SPFBIS will remain silent and allow vendors to make a 
guess.  The SPF summary is that it is out of scope for 
draft-ietf-spfbis-4408bis-19.

>Should the IETF consider a new SenderID WG to discuss what are the 
>repercussions the SPFBIS results have on it?

The above question is about a SenderID BoF.  I personally do not 
think that there is currently interest in having that BoF (see RFC 5434).

Regards,
S. Moonesamy 


From Aaron.Ding@cl.cam.ac.uk  Thu Aug 22 09:20:56 2013
Return-Path: <Aaron.Ding@cl.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 525BD11E80ED for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 09:20:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NoKrXVBX-FeT for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 09:20:48 -0700 (PDT)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 4D43A11E8100 for <ietf@ietf.org>; Thu, 22 Aug 2013 09:20:47 -0700 (PDT)
X-Cam-AntiVirus: not scanned (internal relaying)
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from webmail-2b.csi.cam.ac.uk ([131.111.9.35]:40461) by ppsw-42.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtp id 1VCXcr-0007VJ-6r (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Thu, 22 Aug 2013 17:20:45 +0100
Received: from [127.0.0.1] (helo=webmail-2.hermes.cam.ac.uk) by webmail-2b.csi.cam.ac.uk with esmtp id 1VCXcr-000qk0-1t (Exim 4.80_167-5a66dd3) (return-path <Aaron.Ding@cl.cam.ac.uk>); Thu, 22 Aug 2013 17:20:45 +0100
Received: from add.cl.cam.ac.uk ([128.232.64.12]) by webmail-2.hermes.cam.ac.uk with HTTP (HTTP/1.1 POST); Thu, 22 Aug 2013 17:20:45 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-User: ad707
Date: Thu, 22 Aug 2013 17:20:45 +0100
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: narten@us.ibm.com
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt>
Organization: Cambridge University
Message-ID: <f6159afb59766a8b79dcc7d80eb2378f@cam.ac.uk>
X-Sender: Aaron.Ding@cl.cam.ac.uk
User-Agent: Roundcube Webmail/0.9.2
Cc: barryleiba@computer.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 16:20:56 -0000

On 22/08/13 16:01, Thomas Narten wrote:
> Barry Leiba <barryleiba@computer.org> writes:
> 
>> The general point is that the new people whom we want
>> to draw in as productive participants will be watching how we treat
>> each other and deciding whether they want to wade into that pool.
> 
> It's not just new people watching and being turned off.  There are
> plenty of old timers who get turned off and I doubt I'm alone in
> thinking very carefully these days whether I want to wade into any
> particular discussion.


Thanks for pointing out this sensitive spot. It does exist, not just 
turning off, but even driving people away. Happen to know a such senior 
ietfer..

The line between being Rude and being Upfront is tricky and highly 
context dependent.

Aaron


> 
> Thomas
> 

From superuser@gmail.com  Thu Aug 22 10:15:59 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D00D321F9DFC for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 10:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.215
X-Spam-Level: 
X-Spam-Status: No, score=-1.215 tagged_above=-999 required=5 tests=[AWL=-1.217, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_10_20=2.601, 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 gWIwdPL7KDPM for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 10:15:58 -0700 (PDT)
Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 52A2E21F9950 for <ietf@ietf.org>; Thu, 22 Aug 2013 10:15:58 -0700 (PDT)
Received: by mail-wg0-f53.google.com with SMTP id c11so1877627wgh.8 for <ietf@ietf.org>; Thu, 22 Aug 2013 10:15: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:date:message-id:subject:from:to :cc:content-type; bh=YhbkEtwnw4WVzn+OnB/UN3eyi/Gr2Dg897x4vXPuF3k=; b=JtB1otvVm/KZrgUiLJ3mjOy2xZiHJ2AwWa7xoe9eJ4BOobY2higHmHbYGtEpW04hs5 CUBK6OrSekNrSoEhgK0uEoGByQieJOCOZA2+hvND1gVNTbfZ63mbYeJjUJVYgcqruTho nBTCKCKvntztgmt3m5VWzrmQbDtIZkgK/W84S44lBrZYM83F8bT814wQDYVmiMgtD4Ji GS7/io09Qr2j+i+a/6bEqFyIfWYYrl77GXPLLFFxBTyt9xFe7zCEpP65Z0PjnurGW1UP A+JHKk7veeyTnBXnAObTUR4yJ0+nbTvWFV/pzF91DGbOZj/4XgtSLGxjXxRTiZMj/SHY JJRg==
MIME-Version: 1.0
X-Received: by 10.180.184.107 with SMTP id et11mr21878886wic.60.1377191756931;  Thu, 22 Aug 2013 10:15:56 -0700 (PDT)
Received: by 10.180.125.36 with HTTP; Thu, 22 Aug 2013 10:15:56 -0700 (PDT)
In-Reply-To: <5215CD8D.3080302@sidn.nl>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org> <20130819200802.GI19481@mx1.yitter.info> <521284A4.4050901@qti.qualcomm.com> <5212862F.3080507@qti.qualcomm.com> <5212873B.1010007@dcrocker.net> <CAL0qLwaPJSEXbEadyxcExDSbHg7RMDZ-YzfLztkHkvNF6WOOAQ@mail.gmail.com> <20130819214139.GB19946@mx1.yitter.info> <7D0CBAC9-1E0C-4F07-997E-E98942802884@ogud.com> <5215CD8D.3080302@sidn.nl>
Date: Thu, 22 Aug 2013 10:15:56 -0700
Message-ID: <CAL0qLwaaDarXWKWmOv7Q1EkYn+7q8AckP9Xjyxqvr-0aUZkW3g@mail.gmail.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Jelte Jansen <jelte.jansen@sidn.nl>
Content-Type: multipart/alternative; boundary=001a11c227ee75ab7804e48c7175
Cc: ietf <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.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, 22 Aug 2013 17:15:59 -0000

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

On Thu, Aug 22, 2013 at 1:36 AM, Jelte Jansen <jelte.jansen@sidn.nl> wrote:

> While I appreciate the argument 'this works now, and it is used'
> (running code, and all that), I am very worried that we'll end up with
> what is essentially a free-form blob containing data for several
> protocols at the zone apexes instead of a structured DNS.
>

With or without SPF, we're long past the point where worrying about that is
worthwhile.  Try a TXT lookup for ut.edu or banctec.com, for example.

When I did one of the surveys for RFC6686, it recorded the TXT RRs returned
for various domain queries.  The top ten in terms of record counts returned
back then (most have been cleaned up now):

+-----------+----------------------+
| count(id) | domain               |
+-----------+----------------------+
|        43 | wncy.com             |
|        43 | b93radio.com         |
|        43 | wtaq.com             |
|        29 | dealdirectsendz.info |
|        23 | voamn.org            |
|        18 | ut.edu               |
|        15 | aaronline.com        |
|        10 | dwgsecurity.com      |
|         9 | emergogroup.com      |
|         9 | banctec.com          |
+-----------+----------------------+

The top three were loaded with "google-site-verification=<hash>" records.
ut.edu and banctec.com have a mix of things.

-MSK

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

<div dir=3D"ltr">On Thu, Aug 22, 2013 at 1:36 AM, Jelte Jansen <span dir=3D=
"ltr">&lt;<a href=3D"mailto:jelte.jansen@sidn.nl" target=3D"_blank">jelte.j=
ansen@sidn.nl</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">While I appreciate the ar=
gument &#39;this works now, and it is used&#39;<br>
(running code, and all that), I am very worried that we&#39;ll end up with<=
br>
what is essentially a free-form blob containing data for several<br>
protocols at the zone apexes instead of a structured DNS.<br></blockquote><=
div><br></div><div>With or without SPF, we&#39;re long past the point where=
 worrying about that is worthwhile.=A0 Try a TXT lookup for <a href=3D"http=
://ut.edu">ut.edu</a> or <a href=3D"http://banctec.com">banctec.com</a>, fo=
r example.<br>
<br></div><div>When I did one of the surveys for RFC6686, it recorded the T=
XT RRs returned for various domain queries.=A0 The top ten in terms of reco=
rd counts returned back then (most have been cleaned up now):<br><br>+-----=
------+----------------------+<br>
| count(id) | domain=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>+------=
-----+----------------------+<br>|=A0=A0=A0=A0=A0=A0=A0 43 | <a href=3D"htt=
p://wncy.com">wncy.com</a>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | <br>|=A0=
=A0=A0=A0=A0=A0=A0 43 | <a href=3D"http://b93radio.com">b93radio.com</a>=A0=
=A0=A0=A0=A0=A0=A0=A0 | <br>
|=A0=A0=A0=A0=A0=A0=A0 43 | <a href=3D"http://wtaq.com">wtaq.com</a>=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | <br>|=A0=A0=A0=A0=A0=A0=A0 29 | <a href=3D=
"http://dealdirectsendz.info">dealdirectsendz.info</a> | <br>|=A0=A0=A0=A0=
=A0=A0=A0 23 | <a href=3D"http://voamn.org">voamn.org</a>=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 | <br>
|=A0=A0=A0=A0=A0=A0=A0 18 | <a href=3D"http://ut.edu">ut.edu</a>=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 | <br>|=A0=A0=A0=A0=A0=A0=A0 15 | <a href=
=3D"http://aaronline.com">aaronline.com</a>=A0=A0=A0=A0=A0=A0=A0 | <br>|=A0=
=A0=A0=A0=A0=A0=A0 10 | <a href=3D"http://dwgsecurity.com">dwgsecurity.com<=
/a>=A0=A0=A0=A0=A0 | <br>
|=A0=A0=A0=A0=A0=A0=A0=A0 9 | <a href=3D"http://emergogroup.com">emergogrou=
p.com</a>=A0=A0=A0=A0=A0 | <br>|=A0=A0=A0=A0=A0=A0=A0=A0 9 | <a href=3D"htt=
p://banctec.com">banctec.com</a>=A0=A0=A0=A0=A0=A0=A0=A0=A0 | <br>+--------=
---+----------------------+<br><br></div><div>The top three were loaded wit=
h &quot;google-site-verification=3D&lt;hash&gt;&quot; records.=A0 <a href=
=3D"http://ut.edu">ut.edu</a> and <a href=3D"http://banctec.com">banctec.co=
m</a> have a mix of things.<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c227ee75ab7804e48c7175--

From johnl@iecc.com  Thu Aug 22 10:19:18 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3037811E80ED for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 10:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.686
X-Spam-Level: 
X-Spam-Status: No, score=-102.686 tagged_above=-999 required=5 tests=[AWL=-0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xFp1m2PvVp+T for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 10:19:14 -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 D04DF11E810D for <ietf@ietf.org>; Thu, 22 Aug 2013 10:19:12 -0700 (PDT)
Received: (qmail 3973 invoked from network); 22 Aug 2013 17:19:11 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 22 Aug 2013 17:19:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5216480f.xn--hew.k1308; i=johnl@user.iecc.com; bh=rVUm8uUaBOGhVQoz1q0pEAEybkF0lrNyttStnY/r8Qo=; b=rs1KQC1NQLxf+V7cc6Vce3peIdVUK9DUuqnNRUZR/Z2k5ChCqyHQV6tobCPQ1iQop1nSlazZ5ICglgUVqC4LqpouaabvAH8NGYrUiUKkRFEe1cVCVyc99sym7AGAZhdlnFAuQz8RNRqofbuyAI1vlamzRtgKJrRuja6ahb5sZE8G3J+DiFPyDA2z/QE2xTIfUCB+Jw+a9jGu6cyrbXqJq46d4t3CZMJahAsQR3Y48w4bDytJl+ofD+SuUuMxu+uS
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5216480f.xn--hew.k1308; olt=johnl@user.iecc.com; bh=rVUm8uUaBOGhVQoz1q0pEAEybkF0lrNyttStnY/r8Qo=; b=q2Ez9Ot9EvCDkaEe7GpDHGSgYMlaZFx7McwXjvBMFSr8qEpMKlWZTgXS8/QHRdslzn99/pcPCnTpIp09SgcWBT4ZRQtQmOi+yAQ3NvK+k9KJojyed+0clA2rOOXAVyXyrgnXvBk2Ofwe1xWQrKVnr9mAWABdAo5bLK+Ax++hsPim6KmeIJEUnIzOw+QzJQ2weORZ8yOAXOK19XPe2UUNROr1wH+ZNSPQZafp4WAcKAsUtnnhBirH1HFHNKx7EHF1
Date: 22 Aug 2013 17:18:49 -0000
Message-ID: <20130822171849.5154.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <5215CD8D.3080302@sidn.nl>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 17:19:18 -0000

In article <5215CD8D.3080302@sidn.nl> you write:
>So what makes you think the above 4 points will not be a problem for the
>next protocol that comes along and needs (apex) RR data? And the one
>after that?

SPF is ten years old now.  It would be helpful if you could give us a
list of other protocols that have had a similar issue with a TXT
record at the apex during the past decade.

R's,
John

From iad@ietf.org  Thu Aug 22 12:05:28 2013
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 C1CE311E80F8; Thu, 22 Aug 2013 12:05:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.111
X-Spam-Level: 
X-Spam-Status: No, score=-101.111 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 KKBzR2AU8cxr; Thu, 22 Aug 2013 12:05:28 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0532521F9E5A; Thu, 22 Aug 2013 12:05:28 -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: New IETF Trust Chair
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130822190527.13563.17128.idtracker@ietfa.amsl.com>
Date: Thu, 22 Aug 2013 12:05:27 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 19:05:28 -0000

The IETF Trust Trustees are pleased to announce that Ole Jacobsen has been =
selected as the IETF Trust =

Chair.  Ole was selected following the resignation of Chris Griffiths as Ch=
air, who assumed the =

chairmanship of the IAOC.   This will be Ole's second stint as Chair as he =
succeeded Marshall Eubanks =

when Marshall resigned from the IAOC.  =


Congratulations Ole!  =


Ray Pelletier
Trustee
IAD
http://trustee.ietf.org/

From barryleiba.mailing.lists@gmail.com  Thu Aug 22 12:23:07 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF5111E815C for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 12:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.961
X-Spam-Level: 
X-Spam-Status: No, score=-101.961 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zzm+YD4I+S9w for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 12:23:06 -0700 (PDT)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5A411E8108 for <ietf@ietf.org>; Thu, 22 Aug 2013 12:23:05 -0700 (PDT)
Received: by mail-ve0-f178.google.com with SMTP id ox1so1980681veb.9 for <ietf@ietf.org>; Thu, 22 Aug 2013 12:23: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:message-id:subject :from:to:cc:content-type; bh=uWIU2ld/8fpCGrO+jwGbXRGcFtuVRBEJzctKbYM5USU=; b=e1aaSSD/RqkAIbeH5qWc9nra6hSi/FkT6v4OCJwINhooeeyA6zrzNH96Uv3e8ZRcbw vlejrizWXmkfZkKeNCrT00Qofk0AzijXEvjzclmHHXYvu39c4sZshdCg4bjqRclaMumC rkE6ydBfnRN3ScHdF6WCxdIDFeRgU1BRkBo/2Xt8fKr25wv0QGIEAnnecgCo7961tqbL aUO8CaFPRG/FkteuQNE+9UDbL/ib9YRuH2nZAy3Y0Gc3EwKKupcH5ohjIiSnfRPj+uOX skysSBb/UTPSGiOrP3afTIuWNV3mWMNHECZa+gvz0hsGEkI5QPLeI2hOevf2Ne7Fd12Y /7+A==
MIME-Version: 1.0
X-Received: by 10.220.164.202 with SMTP id f10mr2925958vcy.25.1377199382918; Thu, 22 Aug 2013 12:23:02 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.215.16 with HTTP; Thu, 22 Aug 2013 12:23:02 -0700 (PDT)
In-Reply-To: <CAPv4CP-hRRU21-fLNDJaFGSaBoWHwyhoACta+3xSoTiJtOdxkA@mail.gmail.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <CAPv4CP-hRRU21-fLNDJaFGSaBoWHwyhoACta+3xSoTiJtOdxkA@mail.gmail.com>
Date: Thu, 22 Aug 2013 15:23:02 -0400
X-Google-Sender-Auth: cWvkQv_5VlZhZz7tF4YxVylzG80
Message-ID: <CAC4RtVCtm6yMj557E3dh5RDtzj5qqBwj=a_GyYydepXSFruHjg@mail.gmail.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,  Version 1) to Proposed Standard)
From: Barry Leiba <barryleiba@computer.org>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Crocker Dave <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 19:23:07 -0000

> Pete, I like your position, but I believe "go read the archive" or the
> equivalent will continue to be a standard response unless someone is
> responsible for giving a more thorough response. Who do you think that
> should be?

If you've had the most fleeting look at this:
https://datatracker.ietf.org/doc/draft-leiba-extended-doc-shepherd/

... then you'll know what *my* answer to that question is.  Happily,
this document has an excellent shepherd (see the Most Excellent(tm)
shepherd report:
https://datatracker.ietf.org/doc/draft-ietf-spfbis-4408bis/shepherdwriteup/
), who has been posting summaries and pointers throughout the
conversation.

Perhaps said shepherd could give even better pointers; if so, a quiet
message to him asking for specifics would surely be met with cheerful
diligence.

Barry

From david.black@emc.com  Thu Aug 22 12:51:07 2013
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 83EAA11E811E; Thu, 22 Aug 2013 12:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.425
X-Spam-Level: 
X-Spam-Status: No, score=-102.425 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVOVbWK7J3D8; Thu, 22 Aug 2013 12:51:03 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id EB34F11E8117; Thu, 22 Aug 2013 12:51:02 -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 r7MJocLW001146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 15:50:39 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 22 Aug 2013 15:50:28 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7MJoBsN001185; Thu, 22 Aug 2013 15:50:20 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Thu, 22 Aug 2013 15:50:12 -0400
From: "Black, David" <david.black@emc.com>
To: Eric McMurry <emcmurry@computer.org>
Date: Thu, 22 Aug 2013 15:50:10 -0400
Subject: RE: Gen-ART review of draft-ietf-dime-overload-reqs-10
Thread-Topic: Gen-ART review of draft-ietf-dime-overload-reqs-10
Thread-Index: Ac6faozXVsVQVwMSQy+X8V1n0OAyZAAA9Z1g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489C55@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com> <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org>
In-Reply-To: <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.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-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "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, 22 Aug 2013 19:51:07 -0000

Hi Eric,

This looks good - comments follow ...

> > a) I assume that overload control development work will derive more spe=
cific
> > security requirements - e.g., as REQ 27 is stated at a rather high leve=
l.
> > The discussion in security considerations section seems reasonable.
>=20
> We agree with this.  The thinking here was that we didn't want to specify=
 this
> in a way that would be specific to a particular type of mechanism.  It mi=
ght
> not hurt to state that assumption, either as a note on Req 27 or in the s=
ec
> considerations.

That would be good to add as a note on REQ 27.

> The intent was very much as you say, where requirements on individual nod=
e
> capabilities are hoped to result in better overall system behaviors. Ther=
e are
> also some requirements that are stated more at the system level (e.g. 7 a=
nd
> 17.) Also the text in section 2.2 that discusses Figure 5 talks about how
> insufficient server capacity at a cluster of servers behind a Diameter ag=
ent
> can be treated as if the agent itself was overloaded.
>=20
> On the other hand, any mechanism we design will have to focus on actions =
of
> individual nodes, so the numbered requirements tend to focus on that. I'm=
 not
> sure where to change the balance here--do you have specific suggestions?

I noted this as editorial rather than a minor issue, as I was mostly concer=
ned
that the actual design work will be informed by a sufficient architectural =
"clue"
that the goal is "better overall system behaviors", which your response ind=
icates
will definitely be the case ;-).

Rather than edit individual requirements, how about adding the following se=
ntence
immediately following the introductory sentence in Section 7?:

	These requirements are stated primarily in terms of individual node
	behavior to inform the design of the improved mechanism;
	that design effort should keep in mind that the overall goal is
	improved overall system behavior across all the nodes involved,=20
	not just improved behavior from specific individual nodes.

> > This inadequacy may, in turn, contribute to broader congestion collapse
> >
> > "collapse" is not the right word here - I suggest "issues", "impacts",
> > "effects" or "problems".
>=20
> We are fine with any of those alternatives.  How about impacts.

That's fine.  FWIW, "congestion collapse" has a specific (rather severe)
meaning over in the Transport Area, and that meaning was not intended here.

> 23.843 is the least stable reference.  I don't have any issue with pointi=
ng
> that out.  The part of it we are referencing is historical front matter
> though.

I'd note the reference as work in progress, and put the statement about sta=
ble
front matter (historical is a bad work to use here) in the body of the draf=
t
that cites the reference.
=20
> I tried the web and downloaded versions of 2.12.17 and was not able to ge=
t the
> warnings you saw (about the references).  What did it say?

Sorry, I didn't mean to send you on a wild goose chase :-).  The idnits con=
fusion
manifested right at the top of the output, where everyone ignores it ...

   Attempted to download rfc272 state...
   Failure fetching the file, proceeding without it.

You didn't reference RFC 272, so that output's apparently courtesy of idnit=
s
misinterpreting this reference:

1195	   [TS29.272]
1196	              3GPP, "Evolved Packet System (EPS); Mobility Management
1197	              Entity (MME) and Serving GPRS Support Node (SGSN) relate=
d
1198	              interfaces based on Diameter protocol", TS 29.272 11.4.0=
,
1199	              September 2012.

I was amused :-).

Thanks,
--David

> -----Original Message-----
> From: Eric McMurry [mailto:emcmurry@computer.org]
> Sent: Thursday, August 22, 2013 3:06 PM
> To: Black, David
> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>=20
> Hi David,
>=20
> Thank you for the review.  Your time and comments are appreciated!
>=20
> comments/questions inline.
>=20
>=20
> Eric
>=20
>=20
>=20
> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> wrote:
>=20
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-dime-overload-reqs-10
> > Reviewer: David L. Black
> > Review Date: August 17, 2013
> > IETF LC End Date: August 16, 2013
> > IESG Telechat date: (if known)
> >
> > Summary:
> > This draft is basically ready for publication, but has nits that should=
 be
> > fixed before publication.
> >
> > This draft describes scenarios in which Diameter overload can occur and=
 provides
> > requirements for development of new overload control functionality in D=
iameter.
> > It is well written, and the inclusion of scenarios in which overload ca=
n occur,
> > both in terms of the relationships among types of Diameter nodes and ac=
tual mobile
> > network experience is very helpful.
> >
> > I apologize for this review being a day late, as I've been on vacation =
for most
> > of this draft's IETF Last Call period.
> >
> > Major issues: (none)
> >
> > Minor issues: (none)
> >
> > Nits/editorial comments:
> >
> > The following two comments could be minor issues, but I'm going to trea=
t them
> > as editorial, as I expect that they will be addressed in development of=
 the
> > actual overload functionality:
> >
> > a) I assume that overload control development work will derive more spe=
cific
> > security requirements - e.g., as REQ 27 is stated at a rather high leve=
l.
> > The discussion in security considerations section seems reasonable.
>=20
> We agree with this.  The thinking here was that we didn't want to specify=
 this
> in a way that would be specific to a particular type of mechanism.  It mi=
ght
> not hurt to state that assumption, either as a note on Req 27 or in the s=
ec
> considerations.
>=20
> >
> > b) The draft, and especially its requirements in Section 7 are strongly
> > focused on individual Diameter node overload.  That's necessary, but ov=
erload
> > conditions can be broader, affecting an entire service or application, =
or
> > multiple instances of either/both, even if not every individual Diamete=
r node
> > involved is overloaded.  A number of the requirements, starting with RE=
Q 22
> > could be generalized to cover broader overload conditions.
> >
> > This (b) has implications for other requirements, e.g., REQ 13 should a=
lso be
> > generalized beyond a single node to avoid increased traffic in an overl=
oad
> > situation, even from a node that is not overloaded by itself.  There ar=
e limits
> > on what is reasonable here, as the desired overload functionality is TC=
P/SCTP-
> > like reaction to congestion where individual actions taken by nodes bas=
ed on
> > the information they have (which is not the complete state of the netwo=
rk)
> > results in an overall reduction of load.
>=20
> The intent was very much as you say, where requirements on individual nod=
e
> capabilities are hoped to result in better overall system behaviors. Ther=
e are
> also some requirements that are stated more at the system level (e.g. 7 a=
nd
> 17.) Also the text in section 2.2 that discusses Figure 5 talks about how
> insufficient server capacity at a cluster of servers behind a Diameter ag=
ent
> can be treated as if the agent itself was overloaded.
>=20
> On the other hand, any mechanism we design will have to focus on actions =
of
> individual nodes, so the numbered requirements tend to focus on that. I'm=
 not
> sure where to change the balance here--do you have specific suggestions?
>=20
> >
> > Section 1.2, 2nd paragraph:
> >
> >   as network congestion, network congestion can reduce a Diameter nodes
> >
> > "nodes" -> "node's"
>=20
> good catch.
>=20
> >
> > Section 5, 1st paragraph:
> >
> > This inadequacy may, in turn, contribute to broader congestion collapse
> >
> > "collapse" is not the right word here - I suggest "issues", "impacts",
> > "effects" or "problems".
>=20
> We are fine with any of those alternatives.  How about impacts.
>=20
> >
> > Section 7
> >
> > The long enumerated list of requirements is not an easy read.  It would=
 be
> > better if these could somehow be grouped by functional category, e.g.,
> > security, transport interactions, operational/administrative, etc.
>=20
> agree.  It is actually in sections in the XML (denoted by comments), we j=
ust
> did not promote those to visible sections in the txt.  I recall there bei=
ng
> some issue with xml2rfc and numbering, but now that the numbers are set, =
this
> would not be hard to do.
>=20
>=20
> >
> > idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this is =
fine,
> > as the boilerplate has been appropriately modified for this draft that
> > expresses requirements (as opposed to a draft that specifies a protocol=
).
> >
> > idnits 2.12.17 got confused by the 3GPP and GSMA Informative References=
.
> > I assume that they're all sufficiently stable to be informative referen=
ces.
> > However, [TR23.843] is a work in progress, and should be noted as such =
in
> > its reference - is this needed for any of the other 3GPP or GSMA refere=
nces?
>=20
> 23.843 is the least stable reference.  I don't have any issue with pointi=
ng
> that out.  The part of it we are referencing is historical front matter
> though.
>=20
>=20
> I tried the web and downloaded versions of 2.12.17 and was not able to ge=
t the
> warnings you saw (about the references).  What did it say?
>=20
>=20
> >
> > 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        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
> >
>=20


From ben@nostrum.com  Thu Aug 22 13:50:25 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F067811E820D; Thu, 22 Aug 2013 13:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 OXc8-2JcpDCq; Thu, 22 Aug 2013 13:50:24 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF54411E812C; Thu, 22 Aug 2013 13:50:23 -0700 (PDT)
Received: from [10.0.1.9] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7MKoAjg003176 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 22 Aug 2013 15:50:10 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489C55@MX15A.corp.emc.com>
Date: Thu, 22 Aug 2013 15:50:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <731F5428-B21C-411E-AC44-EEAD241202C4@nostrum.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com> <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org> <8D3D17ACE214DC429325B2B98F3AE7129C489C55@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Eric McMurry <emcmurry@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 20:50:25 -0000

Hi David,

We agree on all your points, and will make the updates in the next =
version, pending shepherd instructions.

Thanks!

Ben.

On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> wrote:

> Hi Eric,
>=20
> This looks good - comments follow ...
>=20
>>> a) I assume that overload control development work will derive more =
specific
>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>> The discussion in security considerations section seems reasonable.
>>=20
>> We agree with this.  The thinking here was that we didn't want to =
specify this
>> in a way that would be specific to a particular type of mechanism.  =
It might
>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>> considerations.
>=20
> That would be good to add as a note on REQ 27.
>=20
>> The intent was very much as you say, where requirements on individual =
node
>> capabilities are hoped to result in better overall system behaviors. =
There are
>> also some requirements that are stated more at the system level (e.g. =
7 and
>> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>> can be treated as if the agent itself was overloaded.
>>=20
>> On the other hand, any mechanism we design will have to focus on =
actions of
>> individual nodes, so the numbered requirements tend to focus on that. =
I'm not
>> sure where to change the balance here--do you have specific =
suggestions?
>=20
> I noted this as editorial rather than a minor issue, as I was mostly =
concerned
> that the actual design work will be informed by a sufficient =
architectural "clue"
> that the goal is "better overall system behaviors", which your =
response indicates
> will definitely be the case ;-).
>=20
> Rather than edit individual requirements, how about adding the =
following sentence
> immediately following the introductory sentence in Section 7?:
>=20
> 	These requirements are stated primarily in terms of individual =
node
> 	behavior to inform the design of the improved mechanism;
> 	that design effort should keep in mind that the overall goal is
> 	improved overall system behavior across all the nodes involved,=20=

> 	not just improved behavior from specific individual nodes.
>=20
>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>=20
>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>> "effects" or "problems".
>>=20
>> We are fine with any of those alternatives.  How about impacts.
>=20
> That's fine.  FWIW, "congestion collapse" has a specific (rather =
severe)
> meaning over in the Transport Area, and that meaning was not intended =
here.
>=20
>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>> that out.  The part of it we are referencing is historical front =
matter
>> though.
>=20
> I'd note the reference as work in progress, and put the statement =
about stable
> front matter (historical is a bad work to use here) in the body of the =
draft
> that cites the reference.
>=20
>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>> warnings you saw (about the references).  What did it say?
>=20
> Sorry, I didn't mean to send you on a wild goose chase :-).  The =
idnits confusion
> manifested right at the top of the output, where everyone ignores it =
...
>=20
>   Attempted to download rfc272 state...
>   Failure fetching the file, proceeding without it.
>=20
> You didn't reference RFC 272, so that output's apparently courtesy of =
idnits
> misinterpreting this reference:
>=20
> 1195	   [TS29.272]
> 1196	              3GPP, "Evolved Packet System (EPS); Mobility =
Management
> 1197	              Entity (MME) and Serving GPRS Support Node (SGSN) =
related
> 1198	              interfaces based on Diameter protocol", TS 29.272 =
11.4.0,
> 1199	              September 2012.
>=20
> I was amused :-).
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Eric McMurry [mailto:emcmurry@computer.org]
>> Sent: Thursday, August 22, 2013 3:06 PM
>> To: Black, David
>> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
>> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>=20
>> Hi David,
>>=20
>> Thank you for the review.  Your time and comments are appreciated!
>>=20
>> comments/questions inline.
>>=20
>>=20
>> Eric
>>=20
>>=20
>>=20
>> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> =
wrote:
>>=20
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>>=20
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>=20
>>> Please resolve these comments along with any other Last Call =
comments
>>> you may receive.
>>>=20
>>> Document: draft-ietf-dime-overload-reqs-10
>>> Reviewer: David L. Black
>>> Review Date: August 17, 2013
>>> IETF LC End Date: August 16, 2013
>>> IESG Telechat date: (if known)
>>>=20
>>> Summary:
>>> This draft is basically ready for publication, but has nits that =
should be
>>> fixed before publication.
>>>=20
>>> This draft describes scenarios in which Diameter overload can occur =
and provides
>>> requirements for development of new overload control functionality =
in Diameter.
>>> It is well written, and the inclusion of scenarios in which overload =
can occur,
>>> both in terms of the relationships among types of Diameter nodes and =
actual mobile
>>> network experience is very helpful.
>>>=20
>>> I apologize for this review being a day late, as I've been on =
vacation for most
>>> of this draft's IETF Last Call period.
>>>=20
>>> Major issues: (none)
>>>=20
>>> Minor issues: (none)
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> The following two comments could be minor issues, but I'm going to =
treat them
>>> as editorial, as I expect that they will be addressed in development =
of the
>>> actual overload functionality:
>>>=20
>>> a) I assume that overload control development work will derive more =
specific
>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>> The discussion in security considerations section seems reasonable.
>>=20
>> We agree with this.  The thinking here was that we didn't want to =
specify this
>> in a way that would be specific to a particular type of mechanism.  =
It might
>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>> considerations.
>>=20
>>>=20
>>> b) The draft, and especially its requirements in Section 7 are =
strongly
>>> focused on individual Diameter node overload.  That's necessary, but =
overload
>>> conditions can be broader, affecting an entire service or =
application, or
>>> multiple instances of either/both, even if not every individual =
Diameter node
>>> involved is overloaded.  A number of the requirements, starting with =
REQ 22
>>> could be generalized to cover broader overload conditions.
>>>=20
>>> This (b) has implications for other requirements, e.g., REQ 13 =
should also be
>>> generalized beyond a single node to avoid increased traffic in an =
overload
>>> situation, even from a node that is not overloaded by itself.  There =
are limits
>>> on what is reasonable here, as the desired overload functionality is =
TCP/SCTP-
>>> like reaction to congestion where individual actions taken by nodes =
based on
>>> the information they have (which is not the complete state of the =
network)
>>> results in an overall reduction of load.
>>=20
>> The intent was very much as you say, where requirements on individual =
node
>> capabilities are hoped to result in better overall system behaviors. =
There are
>> also some requirements that are stated more at the system level (e.g. =
7 and
>> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>> can be treated as if the agent itself was overloaded.
>>=20
>> On the other hand, any mechanism we design will have to focus on =
actions of
>> individual nodes, so the numbered requirements tend to focus on that. =
I'm not
>> sure where to change the balance here--do you have specific =
suggestions?
>>=20
>>>=20
>>> Section 1.2, 2nd paragraph:
>>>=20
>>>  as network congestion, network congestion can reduce a Diameter =
nodes
>>>=20
>>> "nodes" -> "node's"
>>=20
>> good catch.
>>=20
>>>=20
>>> Section 5, 1st paragraph:
>>>=20
>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>=20
>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>> "effects" or "problems".
>>=20
>> We are fine with any of those alternatives.  How about impacts.
>>=20
>>>=20
>>> Section 7
>>>=20
>>> The long enumerated list of requirements is not an easy read.  It =
would be
>>> better if these could somehow be grouped by functional category, =
e.g.,
>>> security, transport interactions, operational/administrative, etc.
>>=20
>> agree.  It is actually in sections in the XML (denoted by comments), =
we just
>> did not promote those to visible sections in the txt.  I recall there =
being
>> some issue with xml2rfc and numbering, but now that the numbers are =
set, this
>> would not be hard to do.
>>=20
>>=20
>>>=20
>>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this =
is fine,
>>> as the boilerplate has been appropriately modified for this draft =
that
>>> expresses requirements (as opposed to a draft that specifies a =
protocol).
>>>=20
>>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
>>> I assume that they're all sufficiently stable to be informative =
references.
>>> However, [TR23.843] is a work in progress, and should be noted as =
such in
>>> its reference - is this needed for any of the other 3GPP or GSMA =
references?
>>=20
>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>> that out.  The part of it we are referencing is historical front =
matter
>> though.
>>=20
>>=20
>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>> warnings you saw (about the references).  What did it say?
>>=20
>>=20
>>>=20
>>> 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        Mobile: +1 (978) 394-7754
>>> ----------------------------------------------------
>>>=20
>>=20
>=20


From marka@isc.org  Thu Aug 22 14:24:04 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7840A11E8124; Thu, 22 Aug 2013 14:24:04 -0700 (PDT)
X-Quarantine-ID: <XrHH6sO84jlI>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -2.317
X-Spam-Level: 
X-Spam-Status: No, score=-2.317 tagged_above=-999 required=5 tests=[AWL=0.282,  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 XrHH6sO84jlI; Thu, 22 Aug 2013 14:23:59 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 6359E11E812C; Thu, 22 Aug 2013 14:23:59 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id A47D3C9493; Thu, 22 Aug 2013 21:23:40 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377206633; bh=6KKfpPBjhSaiOPRkYIxPTo7dJTBcBL3q9H2GzwTmq7U=; h=To:Cc:cc:From:References:Subject:In-reply-to:Date; b=R0Q5ByvjfsPkFFJMTk+C2bOFbRsJyJ9fMoTIS+2Gl8fY2Y449sohxdsHeJpXuV0Ig v3bSYWlVgqIqURUGTGiqFdc0Mw0OB2nT8AhZk5hV3NJtJFvdfb/RvXaFH09j8Y3iiX CjxxJLpzoSmI5jZMGwhbqQhSNeLm2mYCZC+Mn/8g=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Thu, 22 Aug 2013 21:23:40 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id BA1F31602E9; Thu, 22 Aug 2013 21:23:56 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 8AC831602B4; Thu, 22 Aug 2013 21:23:56 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B37A838CBDA2; Fri, 23 Aug 2013 07:23:37 +1000 (EST)
To: Phillip Hallam-Baker <hallam@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20130819222037.GA55876@mx1.yitter.info> <20130822184610.2640.qmail@joyce.lan> <CAMm+Lwj5nTOqTA8ZL7smzW2Q28ARw9NTcbHpxKY-RXZ40-7ZLA@mail.gmail.com>
Subject: Re: [dnsext] Deprecating SPF
In-reply-to: Your message of "Thu, 22 Aug 2013 20:14:33 +0100." <CAMm+Lwj5nTOqTA8ZL7smzW2Q28ARw9NTcbHpxKY-RXZ40-7ZLA@mail.gmail.com>
Date: Fri, 23 Aug 2013 07:23:37 +1000
Message-Id: <20130822212337.B37A838CBDA2@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: John Levine <johnl@taugh.com>, "dnsext@ietf.org" <dnsext@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 21:24:04 -0000

Part of the question is whether the IETF is going to work with ICANN, IANA
and the ccTLD to audit delegations for servers that are not RFC 103[45]
compliant and suspend delegations where the servers are not compliant.

	* no responding to queries based on query type
	* not having a NS rrset at the delegation point

Enforcing that ccTLD and ICANN TLD regularly audit delegations and
have mismatches corrected.  This is REQUIRED by RFC 1034 in part to
stop the sorts of problems we are seeing today.

We don't have to put up people putting up misconfigured / broken servers.

For the non responding servers I have written
draft-andrews-dns-no-response-issue to try to capture the issues.
It was on the dnsop agenda for Berlin but didn't get covered as time
ran out.  I would like everyone to read it and comment on it.

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

From l.wood@surrey.ac.uk  Thu Aug 22 17:56:59 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E48F811E82B3 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 17:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfHUXtWDRqDx for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 17:56:54 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.161]) by ietfa.amsl.com (Postfix) with ESMTP id F1D4E11E82AB for <ietf@ietf.org>; Thu, 22 Aug 2013 17:56:53 -0700 (PDT)
Received: from [195.245.230.131:26198] by server-1.bemta-3.messagelabs.com id 4D/44-17041-253B6125; Fri, 23 Aug 2013 00:56:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-78.messagelabs.com!1377219410!33293621!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10080 invoked from network); 23 Aug 2013 00:56:50 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-6.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 23 Aug 2013 00:56:50 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 23 Aug 2013 01:56:49 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>
Date: Fri, 23 Aug 2013 01:52:54 +0100
Subject: RE: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt>	(Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,	Version 1) to Proposed Standard)
Thread-Topic: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt>	(Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,	Version 1) to Proposed Standard)
Thread-Index: Ac6evXL+5OdJwJ8eTGG3fD6Ew9KUsQA3ablQ
Message-ID: <290E20B455C66743BE178C5C84F124082240607509@EXMB01CMS.surrey.ac.uk>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <CAC4RtVDM4N9=cGyP+RGkv39=qBuJN04PLUubHMwUDfsqM7uJng@mail.gmail.com>, <52153E42.1090703@cs.tcd.ie>
In-Reply-To: <52153E42.1090703@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 00:57:00 -0000

> I can't myself think of a good justification for sarcasm, (well, maybe [1=
]:-)

good sarcasm is like good protocol design - many can recognise it, some can=
 appreciate it, few can truly understand its nuances, and even fewer can cr=
eate it.

You're just not one of them.

Lloyd Wood
http://sat-net.com/L.Wood/

From dhc@dcrocker.net  Thu Aug 22 20:13:28 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE9411E8196 for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 20:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.542
X-Spam-Level: 
X-Spam-Status: No, score=-6.542 tagged_above=-999 required=5 tests=[AWL=0.057,  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 GbidmlSXvqxo for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 20:13:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9C111E8193 for <ietf@ietf.org>; Thu, 22 Aug 2013 20:13:22 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7N3DGlr027418 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 22 Aug 2013 20:13:19 -0700
Message-ID: <5216D331.8070502@dcrocker.net>
Date: Thu, 22 Aug 2013 20:12:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: The Last Call social contract (was - Re: Rude responses)
References: <20130819150521.GB21088@besserwisser.org>	<20130819160549.61542.qmail@joyce.lan>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>	<52150722.1070307@dcrocker.net>	<52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>	<52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com>
In-Reply-To: <52161EB1.6010506@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 22 Aug 2013 20:13:22 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 03:13:28 -0000

Pete, et al,


On 8/22/2013 7:22 AM, Pete Resnick wrote:
> So, now at the point of IETF LC, the correct thing to happen is to
> let folks make their objections, point them to places in the prior
> conversation where the WG, the chairs, the ADs, and assorted other
> folks became convinced, and see if their arguments have some new
> subtlety that was missed earlier. And try to explain. Remember,
> these folks are already at a disadvantage; they've got an uphill
> climb to convince anyone else (especially, me and the rest of the
> IESG) that this long-considered conclusion is incorrect. IMO, that's
> the time to cut them as much slack as possible, because if they do
> have a serious objection hidden in among things that we've seen
> before, we *all* should want to hear it.
...
> So, now at the point of IETF LC, the correct thing to happen is to
> let folks make their objections, point them to places in the prior
> conversation where the WG, the chairs, the ADs, and assorted other
> folks became convinced, and see if their arguments have some new
> subtlety that was missed earlier. And try to explain.


That's certainly a kind and gentle view of the obligations for handling
LC comments.  Kind and gentle on the folks making the comments.  Not so
kind or gentle or useful on the folks who have been spending months (or
years) doing the work of developing the document.

Therefore, I'm going to posit that your model is, in fact, critically
flawed.  (And on review I see there's an apt pun in that wording...)

In pragmatic terms, the current operational model for a LC (and IESG)
review tends to enforce no rules or limits to what can be challenged or
suggested, while simultaneously expecting those who have been doing the
work to then be responsible for educating the commenter and defending
decisions in the document, at the level of re-arguing resolved issues.
Your admonition that "these folks are already at a disadvantage"
encourages this sense of obligation.

However this is direct contradiction to our published rules for Last Call:

    RFC 2418, Working Group Guidelines and Procedures
    Section 8, Review of documents

    "It is important to note
    that a Last-Call is intended as a brief, final check with the
    Internet community, to make sure that no important concerns have been
    missed or misunderstood. The Last-Call should not serve as a more
    general, in-depth review."

Note that last sentence.  It's the essential point, if we are to have
any real /respect/ for the extended effort already put into developing
the document.  It contrasts completely from the burden that is regularly
placed on such folk these days.

In other words, those making comments have obligations too, but that is
not being discussed here, except to make excuses for them.  And it is
the fundamental flaw with your line of thinking.

In practical terms, that thinking suggests that rather than treat it as
a joke, we take seriously and tolerate behavior matching the cliche "I
haven't read the spec, but I have some criticisms of your work."

Besides mostly being incredibly wasteful, to the point of abuse, your
model serves as its own disincentive for bringing work to the IETF; the
hassle factor is just too damn high and, worse, the outcome too damn
unpredictable.

For all that we tout the occasional bit of added insight -- and I'm
entirely in favor of those rare moments -- they are drowned out by the
more predictable and dominant demands to re-explore old topics or new
silly ones or to argue religious technical preferences.


> But that's not what's gone on. Some folks have simply dismissively
> said, "Go read the archive", without pointers.

Last Call is for catching oversights and errors.  It is not for
educating folk who chose not to track the working group. If someone
cares enough to press for specific choices, they need to show up when
the work is being done.  If they don't care that much, then I'm sorry
but "we discussed that" or "go read the archives" is in fact an entirely
sufficient and complete response.  That is, if the IETF has any real
respect for the work that was done developing the document.

[For completeness, I'll note that this is an issue where it makes sense
to handle Individual Submissions quite differently.  Here there is no
archive of IETF group work, and so it is reasonable to demand of the
authors a handling of Last Call comments that really does look more like
education and marketing. But not for working group documents.]


> The dismissiveness AFAICT simply encourages people to post more
> comments without looking at the previous conversation. But your note
> went above and beyond. The sarcasm was sharp and directed. It seemed
> intent on ridiculing.

That's quite a lot to lay onto my brief "very constructive" statement.
Which isn't to say you are wrong; although the intensity of your
reaction really goes considerably beyond the worth of such a single,
brief comment, particularly one lacking an explicitly ad hominem
component and especially given that it really was in response to a
strikingly inappropriate and unconstructive demand.

But let's look at the specifics of the current situation.

Comments during last call can come from folk who either have or lack
knowledge about the IETF and/or the document's topic.  The comments can
be exploratory, in the sense of seriously seeking improvement, or they
can be pushing the speaker's agenda, with no concern other than for
winning their point.  That last is typically marked by a lack of
responsiveness to points of substance, along with an effort to look for
any line of attack that might win.

In all cases, of course, starting with moderated and serious responses
is appropriate.  And, of course, one would always wish that that
continues.

However, by and large, all of the comments to the SPFbis effort have
been either naive, or represented an agenda, or both.

And in this case that prompted my sarcasm, we had a highly knowledgeable
critic refraining from serious discussion and, instead, pressing a very
old and sustained and counter-productive agenda about DNS RRs. And he
did it through several iterations.  In other words, it was a religious
effort, not a technical exploration, jumping around to find any line of
attack that would prevent deprecating a patently useless RR (and one, in
fact, that has been deemed to create an interoperability problem.)

My sarcasm was prompted by the degree of disrespect and silliness in
that final suggestion.  From a highly experienced IETF participant.


> And coming from someone who is already on the side of the called
> consensus (the side that "has already won", though I dislike that
> formulation)

You /should/ dislike it, because it entirely misses the style of attack
against the work that is quite common during LC.

And since it is by now easy to forget my earlier statement, I'll repeat
that I am entirely in favor of LC and the constructive comments that do
get made there.  I am not criticizing the construct of LC but rather the
unreasonable demands on document creators that result from LCs' current
lack of limits on critics.

LC should not be treated as a right of passage, to test the patience of
folks who have developed a document.

It should be exactly what RFC 2418 says it should be.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From l.wood@surrey.ac.uk  Thu Aug 22 20:22:38 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3803C21F9C7A for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 20:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Level: 
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Knq5XKeiueAz for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 20:22:32 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.145]) by ietfa.amsl.com (Postfix) with ESMTP id 9F27011E80FC for <ietf@ietf.org>; Thu, 22 Aug 2013 20:22:27 -0700 (PDT)
Received: from [85.158.136.51:12168] by server-9.bemta-5.messagelabs.com id 32/59-24493-175D6125; Fri, 23 Aug 2013 03:22:25 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-49.messagelabs.com!1377228144!22671176!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6590 invoked from network); 23 Aug 2013 03:22:25 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-16.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 23 Aug 2013 03:22:25 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Fri, 23 Aug 2013 04:22:24 +0100
From: <l.wood@surrey.ac.uk>
To: <dcrocker@bbiw.net>, <presnick@qti.qualcomm.com>
Date: Fri, 23 Aug 2013 04:21:55 +0100
Subject: RE: The Last Call social contract (was - Re: Rude responses)
Thread-Topic: The Last Call social contract (was - Re: Rude responses)
Thread-Index: Ac6frtvgDYQLg8XxReamfi8X2qoQ/gAAQ90w
Message-ID: <290E20B455C66743BE178C5C84F12408224060750A@EXMB01CMS.surrey.ac.uk>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net>	<52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net>	<52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com>,<5216D331.8070502@dcrocker.net>
In-Reply-To: <5216D331.8070502@dcrocker.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 03:22:38 -0000

> LC should not be treated as a right of passage, to test the patience of
> folks who have developed a document.

rite?

Lloyd Wood
http://sat-net.com/L.Wood/



From narten@us.ibm.com  Thu Aug 22 21:53:16 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BEA11E80FF for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.144
X-Spam-Level: 
X-Spam-Status: No, score=-108.144 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_ADOBE2=2.455, 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 zP1urdcTGrYF for <ietf@ietfa.amsl.com>; Thu, 22 Aug 2013 21:53:09 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 97D5021F9A10 for <ietf@ietf.org>; Thu, 22 Aug 2013 21:53:09 -0700 (PDT)
Received: from /spool/local by e32.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, 22 Aug 2013 22:53:08 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 22 Aug 2013 22:53:05 -0600
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 0E2ED1FF001D for <ietf@ietf.org>; Thu, 22 Aug 2013 22:47:37 -0600 (MDT)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7N4r47m182388 for <ietf@ietf.org>; Thu, 22 Aug 2013 22:53:04 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r7N4r4tj008756 for <ietf@ietf.org>; Thu, 22 Aug 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7N4r39t008728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 22 Aug 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r7N4r3wG030723 for <ietf@ietf.org>; Fri, 23 Aug 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r7N4r2LW030682 for ietf@ietf.org; Fri, 23 Aug 2013 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201308230453.r7N4r2LW030682@rotala.raleigh.ibm.com>
Date: Fri, 23 Aug 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13082304-5406-0000-0000-00000BB22A4C
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 04:53:16 -0000

Total of 272 messages in the last 7 days.
 
script run at: Fri Aug 23 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.88% |   16 |  5.06% |   118905 | dhc@dcrocker.net
  5.51% |   15 |  5.10% |   119919 | scott@kitterman.com
  4.78% |   13 |  4.71% |   110859 | hadriel.kaplan@oracle.com
  4.41% |   12 |  4.14% |    97312 | sm+ietf@elandsys.com
  4.04% |   11 |  4.03% |    94724 | presnick@qti.qualcomm.com
  3.68% |   10 |  2.77% |    65248 | paf@frobbit.se
  2.94% |    8 |  2.96% |    69522 | john-ietf@jck.com
  3.31% |    9 |  2.41% |    56561 | johnl@taugh.com
  2.94% |    8 |  2.73% |    64211 | marka@isc.org
  2.94% |    8 |  2.65% |    62387 | mansaxel@besserwisser.org
  2.57% |    7 |  2.92% |    68721 | superuser@gmail.com
  2.94% |    8 |  2.15% |    50470 | ajs@anvilwalrusden.com
  2.21% |    6 |  2.42% |    57003 | hsantos@isdg.net
  2.57% |    7 |  1.99% |    46750 | touch@isi.edu
  2.57% |    7 |  1.96% |    46054 | sustrik@250bpm.com
  2.21% |    6 |  2.26% |    53090 | hallam@gmail.com
  1.84% |    5 |  2.36% |    55546 | david.black@emc.com
  1.10% |    3 |  2.99% |    70357 | adrian@olddog.co.uk
  2.21% |    6 |  1.86% |    43651 | sm@resistor.net
  1.84% |    5 |  1.67% |    39285 | drc@virtualized.org
  1.10% |    3 |  2.37% |    55685 | lionel.morand@orange.com
  1.47% |    4 |  1.70% |    40054 | jgunn6@csc.com
  1.10% |    3 |  1.98% |    46464 | stefan.winter@restena.lu
  0.37% |    1 |  2.41% |    56657 | sginoza@amsl.com
  1.10% |    3 |  1.52% |    35764 | stephen.farrell@cs.tcd.ie
  1.10% |    3 |  1.26% |    29653 | yaronf.ietf@gmail.com
  1.10% |    3 |  1.13% |    26577 | lear@cisco.com
  1.10% |    3 |  1.03% |    24218 | moore@network-heretics.com
  1.10% |    3 |  0.93% |    21961 | ted.lemon@nominum.com
  1.10% |    3 |  0.86% |    20116 | arturo.servin@gmail.com
  0.74% |    2 |  1.03% |    24151 | ben@nostrum.com
  0.74% |    2 |  0.86% |    20259 | vinayakh@gmail.com
  0.74% |    2 |  0.81% |    19089 | morrowc.lists@gmail.com
  0.74% |    2 |  0.70% |    16537 | narten@us.ibm.com
  0.74% |    2 |  0.68% |    15909 | ogud@ogud.com
  0.37% |    1 |  1.01% |    23832 | zhangfatai@huawei.com
  0.74% |    2 |  0.64% |    14977 | barryleiba@computer.org
  0.74% |    2 |  0.63% |    14901 | cabo@tzi.org
  0.74% |    2 |  0.63% |    14884 | jelte.jansen@sidn.nl
  0.74% |    2 |  0.58% |    13716 | housley@vigilsec.com
  0.37% |    1 |  0.95% |    22357 | carter@qosient.com
  0.74% |    2 |  0.56% |    13284 | l.wood@surrey.ac.uk
  0.74% |    2 |  0.56% |    13095 | hgs@cs.columbia.edu
  0.74% |    2 |  0.55% |    12920 | kaduk@mit.edu
  0.74% |    2 |  0.54% |    12636 | hartmans-ietf@mit.edu
  0.37% |    1 |  0.60% |    14113 | fluffy@cisco.com
  0.37% |    1 |  0.59% |    13830 | gk@ninebynine.org
  0.37% |    1 |  0.53% |    12564 | sant9442@gmail.com
  0.37% |    1 |  0.51% |    11888 | lorenzo@google.com
  0.37% |    1 |  0.48% |    11270 | brian.e.carpenter@gmail.com
  0.37% |    1 |  0.46% |    10716 | ron.even.tlv@gmail.com
  0.37% |    1 |  0.44% |    10451 | petithug@acm.org
  0.37% |    1 |  0.44% |    10329 | hannes.tschofenig@gmx.net
  0.37% |    1 |  0.42% |     9832 | andy@yumaworks.com
  0.37% |    1 |  0.40% |     9429 | dotzero@gmail.com
  0.37% |    1 |  0.37% |     8698 | mbaugher@cisco.com
  0.37% |    1 |  0.36% |     8564 | turchanyi.geza@gmail.com
  0.37% |    1 |  0.36% |     8497 | tony@att.com
  0.37% |    1 |  0.36% |     8370 | bmanning@isi.edu
  0.37% |    1 |  0.35% |     8218 | jmh@joelhalpern.com
  0.37% |    1 |  0.34% |     8006 | aallen@blackberry.com
  0.37% |    1 |  0.33% |     7828 | mohamed.boucadair@orange.com
  0.37% |    1 |  0.33% |     7784 | paul.hoffman@vpnc.org
  0.37% |    1 |  0.32% |     7619 | scott.brim@gmail.com
  0.37% |    1 |  0.32% |     7531 | khalil.yacoub@atecgrp.com
  0.37% |    1 |  0.30% |     7094 | hildjj@cursive.net
  0.37% |    1 |  0.30% |     7084 | dot@dotat.at
  0.37% |    1 |  0.30% |     7083 | john@jlc.net
  0.37% |    1 |  0.30% |     7049 | ietfdbh@comcast.net
  0.37% |    1 |  0.30% |     7013 | ek@google.com
  0.37% |    1 |  0.29% |     6800 | carlosm3011@gmail.com
  0.37% |    1 |  0.29% |     6785 | nico@cryptonector.com
  0.37% |    1 |  0.29% |     6750 | melinda.shore@gmail.com
  0.37% |    1 |  0.28% |     6535 | aservin@lacnic.net
  0.37% |    1 |  0.28% |     6521 | bertietf@bwijnen.net
  0.37% |    1 |  0.27% |     6460 | jhw@apple.com
  0.37% |    1 |  0.27% |     6313 | rpelletier@isoc.org
  0.37% |    1 |  0.27% |     6300 | owen@delong.com
  0.37% |    1 |  0.27% |     6295 | jhutz@cmu.edu
  0.37% |    1 |  0.27% |     6260 | uma.chunduri@ericsson.com
  0.37% |    1 |  0.26% |     6192 | masinter@adobe.com
  0.37% |    1 |  0.26% |     6050 | dwm@xpasc.com
  0.37% |    1 |  0.25% |     5951 | braden@isi.edu
  0.37% |    1 |  0.25% |     5920 | vesely@tana.it
  0.37% |    1 |  0.25% |     5833 | kathleen.moriarty@emc.com
  0.37% |    1 |  0.25% |     5797 | aaron.ding@cl.cam.ac.uk
  0.37% |    1 |  0.24% |     5589 | rjsparks@nostrum.com
  0.37% |    1 |  0.21% |     4888 | randy@psg.com
  0.37% |    1 |  0.20% |     4704 | bob.hinden@gmail.com
  0.37% |    1 |  0.20% |     4695 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |  272 |100.00% |  2351769 | Total


From dave@cridland.net  Fri Aug 23 00:37:38 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB5B1F0ED5 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 00:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.512
X-Spam-Level: 
X-Spam-Status: No, score=-1.512 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7I22NeyznkU2 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 00:37:25 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 425141F0ED3 for <ietf@ietf.org>; Fri, 23 Aug 2013 00:37:25 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd6so345502obb.5 for <ietf@ietf.org>; Fri, 23 Aug 2013 00:37:24 -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=15WuqEIoveh/o+XHIdlRGaQo0gB7sVxGusO5Mi7U65g=; b=eYHVYyOCfkn5DVp6LzQqzIJRdLDHHuZN7EsRKiQUdoznsaOVcdaeHsKmPHemNndjAh 0V2ecWmEgw1lit13r9MfewXDtEeivAMYggzlRJ4OAcUGRrW2D4VB6cvJyQOHn/vvPPgZ gCh7mdBf0zyqVvaFUdQjgbTGawTmFsVdZLLgo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=15WuqEIoveh/o+XHIdlRGaQo0gB7sVxGusO5Mi7U65g=; b=HfaSLBz7xiAKsts1HyZ+96TIWV7pW9HIIt+ynoLkiPzEkQSQHTNOIKvOOkbGCcaDJH c7dkGILDEL81X5F6vwL0uqyBJr0o9T+mk6C8pmD58j9r3Zgj41/n4lJZrD/0ThItqsp8 VU0itozxeYcoGlmfSxN+MzHsP3nuQwsWYGpTSKlHpC1AoY3oYKQwOuF1lmAH0gmcI+M4 h6xLSIGocIx5gx8qHVAyMOE8IftcR2Nz31OQg2MK/KsenDZh3idJugIh/tySCXGaufFa SNdjp7kuGNxOf3GFCHl4xFwEipnnxnBmLjpsXmx+bJaGyKLgnepVyjDCDfp/OE2PwIoB XSAg==
X-Gm-Message-State: ALoCoQl+9Aeg/0SAYFrhd1fV5fgjeUQKG+vikgX4E289Ve1nWMFgFGE5EdKF76+YdnMAIus2XS1+
MIME-Version: 1.0
X-Received: by 10.182.143.103 with SMTP id sd7mr60025obb.70.1377243444624; Fri, 23 Aug 2013 00:37:24 -0700 (PDT)
Received: by 10.60.121.97 with HTTP; Fri, 23 Aug 2013 00:37:24 -0700 (PDT)
Received: by 10.60.121.97 with HTTP; Fri, 23 Aug 2013 00:37:24 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F12408224060750A@EXMB01CMS.surrey.ac.uk>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <5216D331.8070502@dcrocker.net> <290E20B455C66743BE178C5C84F12408224060750A@EXMB01CMS.surrey.ac.uk>
Date: Fri, 23 Aug 2013 08:37:24 +0100
Message-ID: <CAKHUCzxL1t=EAEFCvQJrD4zb+FxUhUrx4xnWNA4AmdYEUYdZaw@mail.gmail.com>
Subject: RE: The Last Call social contract (was - Re: Rude responses)
From: Dave Cridland <dave@cridland.net>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=e89a8ff1ce9e49569104e4987ae4
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Discussion" <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: Fri, 23 Aug 2013 07:37:38 -0000

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

On 23 Aug 2013 04:22, <l.wood@surrey.ac.uk> wrote:
>
> > LC should not be treated as a right of passage, to test the patience of
> > folks who have developed a document.
>
> rite?
>

Right - right or rite?

> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>

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

<p dir="ltr"><br>
On 23 Aug 2013 04:22, &lt;<a href="mailto:l.wood@surrey.ac.uk">l.wood@surrey.ac.uk</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; LC should not be treated as a right of passage, to test the patience of<br>
&gt; &gt; folks who have developed a document.<br>
&gt;<br>
&gt; rite?<br>
&gt;</p>
<p dir="ltr">Right - right or rite?</p>
<p dir="ltr">&gt; Lloyd Wood<br>
&gt; <a href="http://sat-net.com/L.Wood/">http://sat-net.com/L.Wood/</a><br>
&gt;<br>
&gt;<br>
</p>

--e89a8ff1ce9e49569104e4987ae4--

From Jelte.Jansen@sidn.nl  Fri Aug 23 02:17:46 2013
Return-Path: <Jelte.Jansen@sidn.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 AE4B921F9AEB for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 02:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.715
X-Spam-Level: 
X-Spam-Status: No, score=-0.715 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DNCNdOcATht3 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 02:17:42 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id D7FDC21F9B03 for <ietf@ietf.org>; Fri, 23 Aug 2013 02:17:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=vIvjvyFvOSjVlZcLYc0SXCQnIgsSlFxuPpHJwrI4qUg=; b=y/byZLF372SzM/wO7G9B5IM+vxuJdFMf3no2geqWGhHE0Ca4d61yHco2GLdUYwD3P7kFPLrhbp07NLJQxwSdIzdiRNDNbzG6kWxSWYfnJ8mM8V5WFbFd7nRwU7675lzKD0ABJB3iu7OoL5ONDthYTU45pIyFS61Iqivfhpb7lAo=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r7N9HeKv024967-r7N9HeKx024967 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Fri, 23 Aug 2013 11:17:40 +0200
Received: from [94.198.152.214] (94.198.152.214) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Fri, 23 Aug 2013 11:17:40 +0200
Message-ID: <521728B4.5070302@sidn.nl>
Date: Fri, 23 Aug 2013 11:17:40 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130822171849.5154.qmail@joyce.lan>
In-Reply-To: <20130822171849.5154.qmail@joyce.lan>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 09:17:46 -0000

On 08/22/2013 07:18 PM, John Levine wrote:
> In article <5215CD8D.3080302@sidn.nl> you write:
>> So what makes you think the above 4 points will not be a problem for the
>> next protocol that comes along and needs (apex) RR data? And the one
>> after that?
> 
> SPF is ten years old now.  It would be helpful if you could give us a
> list of other protocols that have had a similar issue with a TXT
> record at the apex during the past decade.
> 

I don't know of any (at least ones that are used in the global dns
namespace), and I would like to still not know of any in 2033.

SPF may be a lost cause, let's try and make that the only one.

Jelte


From cabo@tzi.org  Fri Aug 23 03:32:10 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB2711E819D for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 03:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.139
X-Spam-Level: 
X-Spam-Status: No, score=-106.139 tagged_above=-999 required=5 tests=[AWL=0.110, 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 E5Myu8OISWQt for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 03:32:05 -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 86C9821F9C17 for <ietf@ietf.org>; Fri, 23 Aug 2013 03:32:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r7NAVfHL017126; Fri, 23 Aug 2013 12:31:41 +0200 (CEST)
Received: from [192.168.217.105] (p548921DA.dip0.t-ipconnect.de [84.137.33.218]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3AEACA11; Fri, 23 Aug 2013 12:31:41 +0200 (CEST)
Subject: Visibility of shepherd writeup
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAC4RtVCtm6yMj557E3dh5RDtzj5qqBwj=a_GyYydepXSFruHjg@mail.gmail.com>
Date: Fri, 23 Aug 2013 12:31:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A1A7F2C-9E05-41EA-AB89-87D046558C41@tzi.org>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <CAPv4CP-hRRU21-fLNDJaFGSaBoWHwyhoACta+3xSoTiJtOdxkA@mail.gmail.com> <CAC4RtVCtm6yMj557E3dh5RDtzj5qqB wj=a_GyYydepXSFruHjg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1508)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Crocker Dave <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 10:32:10 -0000

On Aug 22, 2013, at 21:23, Barry Leiba <barryleiba@computer.org> wrote:

> Most Excellent(tm)
> shepherd report:
> =
https://datatracker.ietf.org/doc/draft-ietf-spfbis-4408bis/shepherdwriteup=
/

(This may not have helped much in this case, but:)

Why is it that IETF last-calls do not contain a direct reference the =
shepherd writeup?
Shouldn't those be required first reading for anyone commenting?

Gr=FC=DFe, Carsten

PS.: The last-call does contain a direct reference to
http://datatracker.ietf.org/doc/draft-ietf-spfbis-4408bis/ballot/
which is 404 at this point in the procedure.


From iad@ietf.org  Fri Aug 23 06:59:07 2013
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 E29E111E819E; Fri, 23 Aug 2013 06:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.111
X-Spam-Level: 
X-Spam-Status: No, score=-101.111 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 UFvJDhJS5iss; Fri, 23 Aug 2013 06:59:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA6111E8161; Fri, 23 Aug 2013 06:59:06 -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: Huawei to Host IETF 88 in Vancouver!
X-Test-IDTracker: no
X-IETF-IDTracker: 4.70.p1
Message-ID: <20130823135906.27066.3431.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 06:59:06 -0700
Cc: wgchairs@ietf.org, ietf@ietf.org, iaoc@ietf.org, rfc-interest@rfc-editor.org, iab@iab.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 13:59:07 -0000

Announce Huawei Host Vancouver

The IAOC is pleased to announce that Huawei will be the Host for IETF 88 in=
 Vancouver.  =


Huawei has been a long time supporter of the IETF through its participation=
 and sponsorships =

at IETF meetings, but this is their first time as the Host of an IETF meeti=
ng.  Congratulations, =

welcome and Thank You!

Registration is now open for IETF 88 at: http://www.ietf.org/meetings/88/

Many sponsorship opportunities are still available:  =

http://iaoc.ietf.org/documents/IETF-Sponsorship-Opportunities-20132002.pdf

If interested contact Andrew Dvorshak, dvorshak@isoc.org.

Once again, thank you Huawei!.  =


See you in Vancouver in 71 days.

Ray
IAD

2014 Meeting Venues

IETF 89	London	Hilton Metropole		March 2-7
IETF 90	Toronto	Fairmont Royal York	        July 20 - 25
IETF 91	Honolulu	Hilton Hawaiian Village	November 9 - 14

From johnl@iecc.com  Fri Aug 23 07:34:30 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C032211E80FF for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 07:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.665
X-Spam-Level: 
X-Spam-Status: No, score=-102.665 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rG2rALKyfymd for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 07:34: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 3E5F011E80D3 for <ietf@ietf.org>; Fri, 23 Aug 2013 07:34:25 -0700 (PDT)
Received: (qmail 95951 invoked from network); 23 Aug 2013 14:34:25 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 Aug 2013 14:34: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; s=521772f1.xn--i8sz2z.k1308; i=johnl@user.iecc.com; bh=mOG68JQayN0jlL7RU93DpotkUVG+qV4bRLbetOBvQ9g=; b=JcPn7OnAImWbvH/uzJ350tnljx/mPYxletIe9vhGaINGazhW7CiRnDom9zkA0d15l/Q5KSoTMdEg+H49cliIqxxTIYJMZXdLss07DkOim3YU9XrJCyCasGHWXfmatOvhA0CNnEF2KgvonH1wxNpoNleeUaEk4V4G+J2vkSetglWyJU+issCTnHODMGEQwpq39Rkh6vw5Ns3xA7tL48UkV0mZsdqVmhPUKa2cyzsJdPUy0z+q67CGkCKxc7i/+cUS
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=521772f1.xn--i8sz2z.k1308; olt=johnl@user.iecc.com; bh=mOG68JQayN0jlL7RU93DpotkUVG+qV4bRLbetOBvQ9g=; b=STx2C/mkcOkxkQVrNsNPtPEpkhEr+5OhrFWTBKxIBfugdnuoToK8gn4ojqk7qLoNUroYe6c712iwugwmM1Pc/bjmgGDTS5XbuonzIaFBKHadwDRrA8dfPOyyqxo/ckohLU4yc4jzV/ww9kCBEA0fy82wc5qLnT3lvLKp4//gYZJqL1qTJq1bdt80q/xXuIsP7AsuOOmts+1y63zbuyr2ANJdIyZ2QWW0BMjwHxvN7rUzz4dZDgpbF8hfV/PDE6+U
Date: 23 Aug 2013 14:34:02 -0000
Message-ID: <20130823143402.49936.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <521728B4.5070302@sidn.nl>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 14:34:30 -0000

>> SPF is ten years old now.  It would be helpful if you could give us a
>> list of other protocols that have had a similar issue with a TXT
>> record at the apex during the past decade.
>
>I don't know of any (at least ones that are used in the global dns
>namespace), and I would like to still not know of any in 2033.
>
>SPF may be a lost cause, let's try and make that the only one.

Since we agree that the issue you're worried about has not arisen even
once in the past decade, could you clarify what problem needs to be
solved here?

R's,
John

From sanjay.mishra@verizon.com  Fri Aug 23 07:49:30 2013
Return-Path: <sanjay.mishra@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7911511E82EE for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 07:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, 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 SBgyPo-0o0Ko for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 07:49:25 -0700 (PDT)
Received: from omzsmtpe03.verizonbusiness.com (omzsmtpe03.verizonbusiness.com [199.249.25.208]) by ietfa.amsl.com (Postfix) with ESMTP id 9C98D11E80E6 for <ietf@ietf.org>; Fri, 23 Aug 2013 07:49:25 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe03.verizonbusiness.com with ESMTP; 23 Aug 2013 14:49:23 +0000
From: "Mishra, Sanjay" <sanjay.mishra@verizon.com>
X-IronPort-AV: E=Sophos;i="4.89,941,1367971200"; d="scan'208";a="542520372"
Received: from fhdp1lumxc7hb01.verizon.com (HELO FHDP1LUMXC7HB01.us.one.verizon.com) ([166.68.59.188]) by fldsmtpi01.verizon.com with ESMTP; 23 Aug 2013 14:49:23 +0000
Received: from fhdp1lumxc7v23.us.one.verizon.com ([166.68.59.159]) by FHDP1LUMXC7HB01.us.one.verizon.com ([166.68.59.188]) with mapi; Fri, 23 Aug 2013 10:49:23 -0400
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 23 Aug 2013 10:49:22 -0400
Subject: RE: [Recentattendees] IETF 88 - Registration Now Open!
Thread-Topic: [Recentattendees] IETF 88 - Registration Now Open!
Thread-Index: Ac6gDQ7FrZLTQIyoQO+O/UopcOyoCQAAqGqA
Message-ID: <900A1E2059ADB149B905E3C8FA0046A62C7967DC95@FHDP1LUMXC7V23.us.one.verizon.com>
References: <20130823142554.29105.99013.idtracker@ietfa.amsl.com>
In-Reply-To: <20130823142554.29105.99013.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 14:49:30 -0000

The URL below is missing letter "g" in the word "meeting".

http://www.ietf.org/meetin/88/hotel.html

-----Original Message-----
From: recentattendees-bounces@ietf.org [mailto:recentattendees-bounces@ietf=
.org] On Behalf Of IETF Secretariat
Sent: Friday, August 23, 2013 10:26 AM
To: recentattendees@ietf.org
Subject: [Recentattendees] IETF 88 - Registration Now Open!

88th IETF Meeting
Vancouver, BC, Canada
November 3-8, 2013
Host: Huawei

Meeting venue:  Hyatt Regency Vancouver: http://vancouver.hyatt.com/en/hote=
l/home.html

Register online at: http://www.ietf.org/meetings/88/

1.  Registration
2.  Visas & Letters of Invitation
3.  Accommodations
4.  Companion Program


1. Registration
 A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October 2013 UTC=
 24:00  B. After Early-Bird cutoff - USD 800.00  C. Full-time Student Regis=
trations - USD 150.00 (with proper ID)  D. One Day Pass Registration - USD =
350.00
 E. Registration Cancellation  =20
             Cut-off for registration cancellation is Monday,
             28 October 2013 at UTC 24:00.
             Cancellations are subject to a 10% (ten percent)
             cancellation fee if requested by that date and time.
 F. Online Registration and Payment ends Friday, 1 November 2013, 1700 loca=
l Vancouver time.
 G. On-site Registration starting Sunday, 3 November 2013 at 1100 local Van=
couver time.

2. Visas & Letters of Invitation:
 Information on Visiting Canada, please visit:
http://www.cic.gc.ca/english/visit/index.asp

 After you complete the registration process, you can request an electronic=
 IETF letter of invitation as well. The registration system also allows for=
 you to request a hard copy IETF letter of invitation. You may also request=
 one at a later time by following the link provided in the confirmation ema=
il.

 Please note that the IETF Letter of Invitation may not be sufficient for o=
btaining a visa to enter Canada.

3.  Accommodations
 The IETF is holding a block of guest rooms at the Hyatt Regency Vancouver,=
 the meeting venue, as well as at the overflow hotel Fairmont Hotel Vancouv=
er, which is located across the street from the Hyatt.
 Room Rates include in room high-speed Internet access. Taxes of 16.5% (hot=
el room tax, GST and Destination Management Fee) are excluded from the gues=
troom rate and are subject to change. Room rates DO NOT include daily break=
fast.

 Reservations Cut off Date:=20
	Hyatt Regency Vancouver - 20 October 2013
	Fairmont Hotel Vancouver - 11 October 2013

For additional information on rates and policies, please visit: http://www.=
ietf.org/meetin/88/hotel.html

4.  Companion Program
If you are traveling with a friend or family member over 18 years of age yo=
u can register them for the IETF Companion Program for only USD 25.00

Benefits include:
- A special welcome reception for companions from 1630-1730 on Sunday, 3 No=
vember
- Ability to attend the official Welcome Reception from 1700-1900 on Sunday=
, 3 November
- A distinctive meeting badge that grants access to the venue (not to be us=
ed to attend working sessions)
- Participation in a separate companion email list if you choose to help co=
mmunicate and make plans with other IETF Companions.

You can register your companion at any time via the IETF website or onsite =
at the meeting.

To join the 88 companions mailing list only see:
https://www.ietf.org/mailman/listinfo/88companions

Only 71 days until the Vancouver IETF!
_______________________________________________
Recentattendees mailing list
Recentattendees@ietf.org
https://www.ietf.org/mailman/listinfo/recentattendees

From cjbc@it.uc3m.es  Thu Aug 22 18:29:00 2013
Return-Path: <cjbc@it.uc3m.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C14F11E82B0; Thu, 22 Aug 2013 18:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 kPMFsyXErRkA; Thu, 22 Aug 2013 18:28:54 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB1A11E8141; Thu, 22 Aug 2013 18:28:53 -0700 (PDT)
Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 1F90310BCE9E; Fri, 23 Aug 2013 03:28:53 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [163.117.203.84] (unknown [163.117.203.84]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp03.uc3m.es) by smtp03.uc3m.es (Postfix) with ESMTPSA id 7B5791079375; Fri, 23 Aug 2013 03:28:52 +0200 (CEST)
Message-ID: <1377221316.4148.8.camel@acorde.it.uc3m.es>
Subject: Re: Last Call: <draft-ietf-netext-update-notifications-07.txt> (Update Notifications for Proxy Mobile IPv6) to Proposed Standard
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: ietf@ietf.org
In-Reply-To: <20130815183238.16338.76789.idtracker@ietfa.amsl.com>
References: <20130815183238.16338.76789.idtracker@ietfa.amsl.com>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 23 Aug 2013 03:28:36 +0200
Mime-Version: 1.0
X-Mailer: Evolution 3.4.4-3 
Content-Transfer-Encoding: 7bit
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-7.0.0.1014-20098.003
X-TM-AS-Result: No--40.936-7.0-31-1
X-imss-scan-details: No--40.936-7.0-31-1
X-Mailman-Approved-At: Fri, 23 Aug 2013 08:03:36 -0700
Cc: netext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 01:29:00 -0000

Hi,

I've taken a look at the current version of the draft and I think it is
in good shape.

I have a couple of comments:

- I think it might be useful to include an additional NR
Code for obtaining Updated Access Network Identifier (ANI) parameters.
The LMA would send a UPN message to the MAG with
NR=Updated-ANI-Parameters and then the MAG would send the PBU with the
updated ANI parameters.

- In the last NETEXT session we discussed about using the update
notifications for the flow mobility solution draft
(draft-ietf-netext-pmipv6-flowmob). I think it might be good to add a
Notification Reason related to flow mobility updates, or at least a
reference to the flowmob document (we can also define the Notification
Reason in draft-ietf-netext-pmipv6-flowmob).

Thanks,

Carlos

On Thu, 2013-08-15 at 11:32 -0700, The IESG wrote:
> The IESG has received a request from the Network-Based Mobility
> Extensions WG (netext) to consider the following document:
> - 'Update Notifications for Proxy Mobile IPv6'
>   <draft-ietf-netext-update-notifications-07.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-08-29. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document specifies protocol enhancements for allowing the local
>    mobility anchor in a Proxy Mobile IPv6 domain to asynchronously
>    notify the mobile access gateway about changes related to a mobility
>    session.  These update notification messages are exchanged using a
>    new Mobility Header message type specifically designed for this
>    purpose.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-netext-update-notifications/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-netext-update-notifications/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 



From david.black@emc.com  Thu Aug 22 15:35:05 2013
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 D38F811E8215; Thu, 22 Aug 2013 15:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.947
X-Spam-Level: 
X-Spam-Status: No, score=-102.947 tagged_above=-999 required=5 tests=[AWL=-0.948, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKnpJQGr3JaM; Thu, 22 Aug 2013 15:35:01 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 2767911E81C7; Thu, 22 Aug 2013 15:35:00 -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 r7MMYkK8009837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 22 Aug 2013 18:34:46 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Thu, 22 Aug 2013 18:34:37 -0400
Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r7MMYa2Y015790; Thu, 22 Aug 2013 18:34:37 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Thu, 22 Aug 2013 18:34:36 -0400
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "ldunbar@huawei.com" <ldunbar@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "igor@yahoo-inc.com" <igor@yahoo-inc.com>, General Area Review Team <gen-art@ietf.org>
Date: Thu, 22 Aug 2013 18:34:35 -0400
Subject: Gen-ART review of draft-ietf-trill-directory-framework-07
Thread-Topic: Gen-ART review of draft-ietf-trill-directory-framework-07
Thread-Index: Ac6fh8c0o2/+z0qDRW228DSyR4uVuQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C489C9C@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, 23 Aug 2013 08:04:00 -0700
Cc: "Black, David" <david.black@emc.com>, "trill@ietf.org" <trill@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 22:35:06 -0000

The -07 version is also ready for publication as an Informational RFC

Thanks,
--David

> -----Original Message-----
> From: gen-art-bounces@ietf.org [mailto:gen-art-bounces@ietf.org] On Behal=
f Of
> Black, David
> Sent: Monday, July 29, 2013 7:20 AM
> To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; igor@yahoo-
> inc.com; General Area Review Team
> Cc: Ted Lemon; ietf@ietf.org; trill@ietf.org
> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-trill-directory-frame=
work-
> 06
>=20
> The -06 version of this draft resolves all of the concerns raised by the =
Gen- ART
> review of the -05 version - the -06 version is ready for publication as a=
n
> Informational RFC.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Wednesday, July 17, 2013 7:54 PM
> > To: ldunbar@huawei.com; Donald Eastlake; Radia@alum.mit.edu; igor@yahoo=
-
> > inc.com; General Area Review Team
> > Cc: trill@ietf.org; ietf@ietf.org; Black, David; Ted Lemon
> > Subject: Gen-ART review of draft-ietf-trill-directory-framework-05
> >
> > Document: draft-ietf-trill-directory-framework-05
> > Reviewer: David L. Black
> > Review Date: July 17, 2013
> > IETF LC End Date: July 18, 2013
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the =
review.
> >
> > This draft describes a framework for using directory servers to provide
> > address mappings (address -> destination RBridge) to TRILL Rbridges as =
an
> > alternative to data plane learning and use of the TRILL ESADI protocol.
> >
> > The draft's generally well written and clear.  I found a couple of mino=
r
> > issues.
> >
> > Major issues: None.
> >
> > Minor issues:
> >
> > [1] The last bullet in Section 3.1 says:
> >
> >        - In an environment where VMs migrate, there is a higher chance
> >          of cached information becoming invalid, causing traffic to be
> >          black-holed by the ingress RBridge, that is, persistently sent
> >          to the wrong egress RBridge. If VMs do not flood gratuitous
> >          ARP/ND or VDP [802.1Qbg] messages upon arriving at new
> >          locations, the ingress nodes might not have MAC entries for th=
e
> >          MAC of the newly arrived VMs, causing unknown address flooding=
.
> >
> > This is incorrect in multiple ways and should just be removed:
> >
> > - Persistent black-holing is rare in practice because all common
> > 	VM migration implementations issue the gratuitous messages.
> > - VMs don't send the gratuitous messages, hypervisors do.
> > - VDP is not flooded.  The receiver's always a bridge.
> > - At least one common VM migration implementation actually uses a gratu=
itous
> > 	RARP, not ARP.
> > - Flooding is done by the bridges and Rbridges, not the VMs.
> >
> > [2] There are some unfortunate notation problems in Section 5.1 that ca=
rry
> > into the following sections, based on the logical data structure:
> >
> >    [{IP, MAC/VLAN, {list of attached RBridge nicknames}, {list of
> >    interested RBridges}]
> >
> > - The first open curly brace ('{') is unmatched.
> > - Subsequent text uses [IP or MAC/VLAN], IP/MAC/VLAN and MAC&VLAN,
> > 	none of which appear in that structure.
> >
> > Nits/editorial comments:
> >
> > Section 1 - item 1 in the numbered list does not explain why it makes
> > a directory approach attractive.  This should be added, as it is
> > present for the other three items .
> >
> > Section 2 - Say that IS-IS is a routing protocol.
> > The definition of Station should say that the node or virtual node
> > is on a network.  Also, please define or explain "virtual node".
> >
> > Section 3.2 - Add the number of entries to be learned to scenario #1
> > in order to parallel the scenario # 2 discussion.
> >
> > Section 4 - remove "(distributed model)" from first paragraph,
> > as it's not explained.
> >
> > Section 5.3, top of p.13:
> >
> >    therefore, there needs to be some mechanism by which RBridges that
> >    have pulled information that has not expired can be informed when
> >    that information changes or the like.
> >
> > "or the like" is vague.  I suggest "or becomes invalid for other
> >  reasons".
> >
> > idnits 2.12.17 didn't find any nits that need attention.
> >
> > 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
> > ----------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From emcmurry@computer.org  Thu Aug 22 12:05:51 2013
Return-Path: <emcmurry@computer.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 156D711E81FA; Thu, 22 Aug 2013 12:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.486
X-Spam-Level: 
X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ev-m0gFe5sN; Thu, 22 Aug 2013 12:05:45 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4204621F9F98; Thu, 22 Aug 2013 12:05:45 -0700 (PDT)
Received: from cpe-76-184-161-215.tx.res.rr.com ([76.184.161.215] helo=antikythera.casamcmurry.com) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from <emcmurry@computer.org>) id 1VCaCR-000GZK-Ol; Thu, 22 Aug 2013 19:05:39 +0000
Received: from localhost (localhost [127.0.0.1]) by antikythera.casamcmurry.com (Postfix) with ESMTP id 039731349AE7; Thu, 22 Aug 2013 14:05:38 -0500 (CDT)
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 76.184.161.215
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1+MrAzNsRukkmVX47ydeww6zOUrVBG7aRA=
X-Virus-Scanned: amavisd-new at casamcmurry.com
Received: from antikythera.casamcmurry.com ([127.0.0.1]) by localhost (antikythera.casamcmurry.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmEzOiU_Y3lK; Thu, 22 Aug 2013 14:05:37 -0500 (CDT)
Received: from ericlaptop.casamcmurry.com (ericlaptop.casamcmurry.com [192.168.111.91]) by antikythera.casamcmurry.com (Postfix) with ESMTPSA id 9494D1349AD9;  Thu, 22 Aug 2013 14:05:37 -0500 (CDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
From: Eric McMurry <emcmurry@computer.org>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com>
Date: Thu, 22 Aug 2013 14:05:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AEC7E92F-7370-4D76-B0DF-E9738FABCB86@computer.org>
References: <8D3D17ACE214DC429325B2B98F3AE7129C489319@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
X-Mailman-Approved-At: Fri, 23 Aug 2013 08:04:08 -0700
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Aug 2013 19:05:52 -0000

Hi David,

Thank you for the review.  Your time and comments are appreciated!

comments/questions inline.


Eric



On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> wrote:

>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-dime-overload-reqs-10
> Reviewer: David L. Black
> Review Date: August 17, 2013
> IETF LC End Date: August 16, 2013
> IESG Telechat date: (if known)
>=20
> Summary:
> This draft is basically ready for publication, but has nits that =
should be
> fixed before publication.
>=20
> This draft describes scenarios in which Diameter overload can occur =
and provides
> requirements for development of new overload control functionality in =
Diameter.
> It is well written, and the inclusion of scenarios in which overload =
can occur,
> both in terms of the relationships among types of Diameter nodes and =
actual mobile
> network experience is very helpful.
>=20
> I apologize for this review being a day late, as I've been on vacation =
for most
> of this draft's IETF Last Call period.
>=20
> Major issues: (none)
>=20
> Minor issues: (none)
>=20
> Nits/editorial comments:
>=20
> The following two comments could be minor issues, but I'm going to =
treat them
> as editorial, as I expect that they will be addressed in development =
of the
> actual overload functionality:
>=20
> a) I assume that overload control development work will derive more =
specific
> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
> The discussion in security considerations section seems reasonable.

We agree with this.  The thinking here was that we didn't want to =
specify this in a way that would be specific to a particular type of =
mechanism.  It might not hurt to state that assumption, either as a note =
on Req 27 or in the sec considerations.

>=20
> b) The draft, and especially its requirements in Section 7 are =
strongly
> focused on individual Diameter node overload.  That's necessary, but =
overload
> conditions can be broader, affecting an entire service or application, =
or
> multiple instances of either/both, even if not every individual =
Diameter node
> involved is overloaded.  A number of the requirements, starting with =
REQ 22
> could be generalized to cover broader overload conditions.
>=20
> This (b) has implications for other requirements, e.g., REQ 13 should =
also be
> generalized beyond a single node to avoid increased traffic in an =
overload
> situation, even from a node that is not overloaded by itself.  There =
are limits
> on what is reasonable here, as the desired overload functionality is =
TCP/SCTP-
> like reaction to congestion where individual actions taken by nodes =
based on
> the information they have (which is not the complete state of the =
network)
> results in an overall reduction of load.

The intent was very much as you say, where requirements on individual =
node capabilities are hoped to result in better overall system =
behaviors. There are also some requirements that are stated more at the =
system level (e.g. 7 and 17.) Also the text in section 2.2 that =
discusses Figure 5 talks about how insufficient server capacity at a =
cluster of servers behind a Diameter agent can be treated as if the =
agent itself was overloaded.

On the other hand, any mechanism we design will have to focus on actions =
of individual nodes, so the numbered requirements tend to focus on that. =
I'm not sure where to change the balance here--do you have specific =
suggestions?

>=20
> Section 1.2, 2nd paragraph:
>=20
>   as network congestion, network congestion can reduce a Diameter =
nodes
>=20
> "nodes" -> "node's"

good catch.

>=20
> Section 5, 1st paragraph:
>=20
> This inadequacy may, in turn, contribute to broader congestion =
collapse=20
>=20
> "collapse" is not the right word here - I suggest "issues", "impacts",
> "effects" or "problems".

We are fine with any of those alternatives.  How about impacts.

>=20
> Section 7
>=20
> The long enumerated list of requirements is not an easy read.  It =
would be
> better if these could somehow be grouped by functional category, e.g.,
> security, transport interactions, operational/administrative, etc.

agree.  It is actually in sections in the XML (denoted by comments), we =
just did not promote those to visible sections in the txt.  I recall =
there being some issue with xml2rfc and numbering, but now that the =
numbers are set, this would not be hard to do.

>=20
> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this is =
fine,
> as the boilerplate has been appropriately modified for this draft that
> expresses requirements (as opposed to a draft that specifies a =
protocol).
>=20
> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
> I assume that they're all sufficiently stable to be informative =
references.
> However, [TR23.843] is a work in progress, and should be noted as such =
in
> its reference - is this needed for any of the other 3GPP or GSMA =
references?

23.843 is the least stable reference.  I don't have any issue with =
pointing that out.  The part of it we are referencing is historical =
front matter though.


I tried the web and downloaded versions of 2.12.17 and was not able to =
get the warnings you saw (about the references).  What did it say?


>=20
> 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        Mobile: +1 (978) 394-7754
> ----------------------------------------------------
>=20


From sgundave@cisco.com  Thu Aug 22 21:17:41 2013
Return-Path: <sgundave@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 8E62921F9CAC; Thu, 22 Aug 2013 21:17:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 2QoYh5DI8TZJ; Thu, 22 Aug 2013 21:17:30 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id B918511E8197; Thu, 22 Aug 2013 21:17:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2767; q=dns/txt; s=iport; t=1377231449; x=1378441049; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=82veYRfABG1DwGKp2Aayfr0qQKpI6zAS0GvPpkIBytM=; b=Goq4FFQ5F+rG2/BlFqbO83yay/TcRTHQ2HfYJXagbC7X3PblPFQSf+DX voJ7AhpceQo6Kcowhdftue6+Tfg+5LVTAvaS8r278h+J4IqU5bUkZrQum row3+7Mo2gCbp/Ackc3RLnm1oUDmYLcOluJwq/RTrEasjIiyNt6XeaRT3 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAFLhFlKtJXHA/2dsb2JhbABagwc1UcAMgRwWdIIkAQEBBAEBAWsJAhIBCBgKGTILJQIEAQ0FCBOHdQy3FpAzAjEHgxt7A4h2kB2QLYFkgTuCKw
X-IronPort-AV: E=Sophos;i="4.89,938,1367971200"; d="scan'208";a="250839309"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 23 Aug 2013 04:17:28 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r7N4HRDv011951 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 23 Aug 2013 04:17:27 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.187]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.02.0318.004; Thu, 22 Aug 2013 23:17:27 -0500
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "cjbc@it.uc3m.es" <cjbc@it.uc3m.es>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [netext] Last Call: <draft-ietf-netext-update-notifications-07.txt> (Update Notifications for Proxy Mobile IPv6) to Proposed Standard
Thread-Topic: [netext] Last Call: <draft-ietf-netext-update-notifications-07.txt> (Update Notifications for Proxy Mobile IPv6) to Proposed Standard
Thread-Index: AQHOn7esRvgkdLK2yk2caW0kIeZhVA==
Date: Fri, 23 Aug 2013 04:17:19 +0000
Message-ID: <24C0F3E22276D9438D6F366EB89FAEA81169FEB9@xmb-aln-x03.cisco.com>
In-Reply-To: <1377221316.4148.8.camel@acorde.it.uc3m.es>
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.32.246.211]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <246BE10AB972EB48B4C4E8AB288766ED@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 23 Aug 2013 08:04:14 -0700
Cc: "netext@ietf.org" <netext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 04:17:41 -0000

Hi Carlos,

Thanks for your review comments. Please see inline.


On 8/22/13 6:28 PM, "Carlos Jes=FAs Bernardos Cano" <cjbc@it.uc3m.es> wrote=
:

>Hi,
>
>I've taken a look at the current version of the draft and I think it is
>in good shape.
>
>I have a couple of comments:
>
>- I think it might be useful to include an additional NR
>Code for obtaining Updated Access Network Identifier (ANI) parameters.
>The LMA would send a UPN message to the MAG with
>NR=3DUpdated-ANI-Parameters and then the MAG would send the PBU with the
>updated ANI parameters.


Yes. We discussed this, but we seem to have missed this comment. Will
include this NR  code.


>
>- In the last NETEXT session we discussed about using the update
>notifications for the flow mobility solution draft
>(draft-ietf-netext-pmipv6-flowmob). I think it might be good to add a
>Notification Reason related to flow mobility updates, or at least a
>reference to the flowmob document (we can also define the Notification
>Reason in draft-ietf-netext-pmipv6-flowmob).


Sure. Will add a reference to the spec.

Regards
Sri



>
>Thanks,
>
>Carlos
>
>On Thu, 2013-08-15 at 11:32 -0700, The IESG wrote:
>> The IESG has received a request from the Network-Based Mobility
>> Extensions WG (netext) to consider the following document:
>> - 'Update Notifications for Proxy Mobile IPv6'
>>   <draft-ietf-netext-update-notifications-07.txt> as Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-08-29. Exceptionally, comments may
>>be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>    This document specifies protocol enhancements for allowing the local
>>    mobility anchor in a Proxy Mobile IPv6 domain to asynchronously
>>    notify the mobile access gateway about changes related to a mobility
>>    session.  These update notification messages are exchanged using a
>>    new Mobility Header message type specifically designed for this
>>    purpose.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-netext-update-notifications/
>>=20
>> IESG discussion can be tracked via
>>=20
>>http://datatracker.ietf.org/doc/draft-ietf-netext-update-notifications/ba
>>llot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>
>
>_______________________________________________
>netext mailing list
>netext@ietf.org
>https://www.ietf.org/mailman/listinfo/netext


From hsantos@isdg.net  Fri Aug 23 09:59:20 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9EB11E81CE for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 09:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-4HF0w1024k for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 09:59:08 -0700 (PDT)
Received: from winserver.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id EFA2711E81C8 for <ietf@ietf.org>; Fri, 23 Aug 2013 09:59:07 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2488; t=1377277143; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=GEJLZwzb5r/6I6y0buXPCEY64bA=; b=oFYlAVpUt2Sfr3Ddwn0b SMa6YFwvBHkqag8Yi1wxzytUb9m0oeU9pNyf3R+1pA8YCKWfvaWGkRYOpf/pD0w6 9shkdtKJqeqHZXnScWzbIYWD5+CFa+5QvFiUxsBOvgGseW3sy/JT4xYj84oTVyGe 3K4fD/lw/K3zl1sVjgSUPmg=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 23 Aug 2013 12:59:03 -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 3739656530.3203.3460; Fri, 23 Aug 2013 12:59:02 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2488; t=1377276830; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=/zNgHic lvCsbdVMvsFcZkwhD7yiATIaoFj77jZmPw84=; b=3P+ffNlNKozJCUgqG61+UN2 647tevaW4kyO+4/+zT/Btal/dsBVT+pmzjq1Xyxiha104K1OuZlCbs4pFGbxOVCP 4G8GoebmzuNvzInBcSRaRaIYugfYv+Q/0g6QmlwotP9gySIiyNKxk+ws9I+8MTCM VT2uU4TpLNhUVNK5WDSU=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 23 Aug 2013 12:53:50 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3186077924.9.6440; Fri, 23 Aug 2013 12:53:49 -0400
Message-ID: <521794CE.7040002@isdg.net>
Date: Fri, 23 Aug 2013 12:58: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: Andras Salamon <andras@dns.net>
Subject: Re: [dnsext] full standards, Deprecating SPF
References: <20130822221515.GA35645@gaon.net>	<20130822235329.3752.qmail@joyce.lan> <20130823162514.GA38870@gaon.net>
In-Reply-To: <20130823162514.GA38870@gaon.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: dnsext@ietf.org, IETF General 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, 23 Aug 2013 16:59:20 -0000

Andras Salamon wrote:
> On Thu, Aug 22, 2013 at 11:53:29PM -0000, John Levine wrote:
>> If you think it's important to move it to full standard, why don't you
>> do somthing about it?  A quick look suggests that 3597 meets the
>> requirements in sec 2.2 of RFC 6410 I wouldn't think that it'd be hard
>> to persuade someone on the IESG to sponsor the required last call.
> 
> Ã“lafur Gudmundsson nominated RFC 3597 to advance from Proposed to
> Draft Standard in message <6.1.0.6.2.20040819092046.02d2dec0@localhost>
> of 19 Aug 2004.  This was based on -00 of Jakob Schlyter's draft,
> of which the most recent version is from May 2005:
>    http://tools.ietf.org/id/draft-ietf-dnsext-interop3597-02.txt
> 
> Since Jakob already did an important part of the work, I would
> first like to understand what happened to the advancement request,
> especially in light of the two revisions of the interoperability
> report after the request.  Does anyone have pointers?
> 
> (I know that PS/DS were merged a couple of years ago, but would still
> like to understand how the PS->DS process went, and if it failed, why.)

I appreciate this level of work to see why it fell through the cracks. 
I believe it is one of the IETF growing lack of diversity issues, 
i.e., improving electronic communications, collaborations and 
networking among industry peers.

This should be a project leader(s) responsibility to make sure the 
basic technology requirements are realistic or not, i.e., consult and 
get input from the DNS industry vendors, make them aware and/or to 
find out why this has not happen yet.

For example, why hasn't Microsoft supported RFC 3597 yet?  You will be 
surprise that a well respected Microsoft DNS Expert and MVP (Most 
Valuable Player) was unaware of such needs, nor was his microsoft 
contacts and the MSDNS beta team based on a discussion with him:

http://social.technet.microsoft.com/Forums/windowsserver/en-US/5841e884-db22-42a1-8530-615a375662cc/dns-server-support-for-new-or-unamed-rr-type-records

This was back in March/April 2012.

If Microsoft isn't going to bother to add direct support for the SPF 
type99 RR, nor support RFC 3597 at the very least, I believe this 
matter is decided and closed. TXT only is proper for SPFBIF and for 
future DNS applications as well.

I am sure there are key IETF decision makers with Microsoft DNS 
product manager contacts who can find out whats going on to help 
resolve this LC issue.

--
HLS




From bmanning@isi.edu  Fri Aug 23 10:46:13 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E65011E8308 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 10:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.299
X-Spam-Level: 
X-Spam-Status: No, score=-104.299 tagged_above=-999 required=5 tests=[AWL=-1.700, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugW4+6fUiVNw for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 10:46:09 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id CE7C811E8307 for <ietf@ietf.org>; Fri, 23 Aug 2013 10:46:07 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r7NHjDOM002650 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 23 Aug 2013 10:45:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Fwd: [dnsext] SPF isn't going to change, was Deprecating SPF
From: manning bill <bmanning@isi.edu>
Date: Fri, 23 Aug 2013 10:45:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <82E79956-CC08-41DB-A522-9B65520909F5@isi.edu>
References: <20130823170326.GA24644@vacation.karoshi.com.>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 17:46:13 -0000

Begin forwarded message:

> Resent-From: bmanning@vacation.karoshi.com
> From: bmanning@vacation.karoshi.com
> Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
> Date: August 23, 2013 10:03:26 PDT
> Resent-To: bmanning@isi.edu
> To: John Levine <johnl@taugh.com>
> Cc: dnsext@ietf.org
>=20
> On Fri, Aug 23, 2013 at 03:14:38PM -0000, John Levine wrote:
>> I counted my queries from a few days ago and got 7086 TXT, 263 SPF, =
or 3.7%.
>>=20
>> Nobody has argued that SPF usage is zero, and the reasons for
>> deprecating SPF have been described repeatedly here and on the ietf
>> list, so this exercise seems fairly pointless.
>=20
> 	the reasons for not deprecating SPF have been described here
> 	and on the ietf list repeatedly ... yet there has been little
> 	concrete data regarding deployment uptake. These published
> 	snapshots form a baseline - 201308, and it might be worthwhile
> 	to look again in six months to see if the magnitude and ratio=20
> 	have changed.  The results of a second look should bring into
> 	focus the prevaling trends and solidify the argument.
>=20
> 	Surely there is no compelling urgency to conclude the current=20
> 	LC - given the duration of this work a six month period to=20
> 	gain emperical insight would not be a bad thing.
>=20
> 	Would it?
>=20
> /bill
> =09
>>=20
>> R's,
>> John
>> _______________________________________________
>> dnsext mailing list
>> dnsext@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnsext
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext


From bmanning@isi.edu  Fri Aug 23 10:50:43 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 214B911E81AB; Fri, 23 Aug 2013 10:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.449
X-Spam-Level: 
X-Spam-Status: No, score=-107.449 tagged_above=-999 required=5 tests=[AWL=3.150, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pOgnDjitJP+F; Fri, 23 Aug 2013 10:50:39 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C71B221F9E68; Fri, 23 Aug 2013 10:50:38 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7NHn4FA002198 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 23 Aug 2013 10:49:13 -0700 (PDT)
Subject: Re: IETF 88 - Registration Now Open!
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20130823133657.18756.43809.idtracker@ietfa.amsl.com>
Date: Fri, 23 Aug 2013 10:49:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu>
References: <20130823133657.18756.43809.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: wgchairs@ietf.org, IETF Announcement List <ietf-announce@ietf.org>, irsg@irtf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 17:50:43 -0000

and the hotel is fully booked=85.

/bill


On 23August2013Friday, at 6:36, IETF Secretariat wrote:

> 88th IETF Meeting
> Vancouver, BC, Canada
> November 3-8, 2013
> Host: Huawei
>=20
> Meeting venue:  Hyatt Regency Vancouver: =
http://vancouver.hyatt.com/en/hotel/home.html
>=20
> Register online at: http://www.ietf.org/meetings/88/
>=20
> 1.  Registration
> 2.  Visas & Letters of Invitation
> 3.  Accommodations
> 4.  Companion Program
>=20
>=20
> 1. Registration
>  A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October =
2013 UTC 24:00
>  B. After Early-Bird cutoff - USD 800.00
>  C. Full-time Student Registrations - USD 150.00 (with proper ID)
>  D. One Day Pass Registration - USD 350.00
>  E. Registration Cancellation  =20
>              Cut-off for registration cancellation is Monday,
>              28 October 2013 at UTC 24:00.
>              Cancellations are subject to a 10% (ten percent)
>              cancellation fee if requested by that date and time.
>  F. Online Registration and Payment ends Friday, 1 November 2013, 1700 =
local Vancouver time.
>  G. On-site Registration starting Sunday, 3 November 2013 at 1100 =
local Vancouver time.
>=20
> 2. Visas & Letters of Invitation:
>  Information on Visiting Canada, please visit:
> http://www.cic.gc.ca/english/visit/index.asp
>=20
>  After you complete the registration process, you can request an =
electronic IETF letter of invitation as well. The registration system =
also allows for you to request a hard copy IETF letter of invitation. =
You may also request one at a later time by following the link provided =
in the confirmation email.
>=20
>  Please note that the IETF Letter of Invitation may not be sufficient =
for obtaining a visa to enter Canada.
>=20
> 3.  Accommodations
>  The IETF is holding a block of guest rooms at the Hyatt Regency =
Vancouver, the meeting venue, as well as at the overflow hotel Fairmont =
Hotel Vancouver, which is located across the street from the Hyatt.
>  Room Rates include in room high-speed Internet access. Taxes of 16.5% =
(hotel room tax, GST and Destination Management Fee) are excluded from =
the guestroom rate and are subject to change. Room rates DO NOT include =
daily breakfast.
>=20
>  Reservations Cut off Date:=20
> 	Hyatt Regency Vancouver - 20 October 2013
> 	Fairmont Hotel Vancouver - 11 October 2013
>=20
> For additional information on rates and policies, please visit: =
http://www.ietf.org/meetin/88/hotel.html
>=20
> 4.  Companion Program
> If you are traveling with a friend or family member over 18 years of =
age you can register them for the IETF Companion Program for only USD =
25.00
>=20
> Benefits include:
> - A special welcome reception for companions from 1630-1730 on Sunday, =
3 November
> - Ability to attend the official Welcome Reception from 1700-1900 on =
Sunday, 3 November
> - A distinctive meeting badge that grants access to the venue (not to =
be used to attend working sessions)
> - Participation in a separate companion email list if you choose to =
help communicate and make plans with other IETF Companions.
>=20
> You can register your companion at any time via the IETF website or =
onsite at the meeting.
>=20
> To join the 88 companions mailing list only see:
> https://www.ietf.org/mailman/listinfo/88companions
>=20
> Only 71 days until the Vancouver IETF!


From johnl@iecc.com  Fri Aug 23 11:04:39 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC83911E8104 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.622
X-Spam-Level: 
X-Spam-Status: No, score=-102.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1NuD8jAh0ST for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:04:35 -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 07A0211E80C5 for <ietf@ietf.org>; Fri, 23 Aug 2013 11:04:34 -0700 (PDT)
Received: (qmail 53851 invoked from network); 23 Aug 2013 18:04:33 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 Aug 2013 18:04:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5217a431.xn--30v786c.k1308; i=johnl@user.iecc.com; bh=YeXmuuHBDR2OHQqannxZ1NhnONvb3vAGdxPBYVO9HhQ=; b=T1RX/ABg/Qaj/v2lod638aeR+IpKJxkn9xgHjG5b8D0PO6dDsrblWyn6aWwshHZSoD/qiL51ZO7I24LxJZS1TSxWacr1JfEs2bYtNF8Sk2EPvo0vonYFCXPSg3JErqkgQZ6KBoDr+frsGgwtZ8wYxtG++fy6vc7NSy1zwX+y/tAZi7Wi2+xfMFR0qMTzqNuSl3jF5Zwkh30J57zl/vsiTRbJMg9ALRuQp1XH93mTqOm0qQYApPV3b3hJpO9d8WW0
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5217a431.xn--30v786c.k1308; olt=johnl@user.iecc.com; bh=YeXmuuHBDR2OHQqannxZ1NhnONvb3vAGdxPBYVO9HhQ=; b=Dzbj9vNIJEM4tsral/9RnYOBcPpUt96dymxypyyaYbOwjJ6CmdhTG8GOuQsQWSioalmlaX+isOZxbcmHOZDYUes9nvo5ZaxEg0zeHeXWczNpaMf81f7r2WgYdIPirOZS3NHwa9WSkdhGwJ8VQ3i5R0p+T9euxZ0Qn2C8YefYkDOlgW05nkHDtzZ0nbCPIWiYF+/DeJTdgxAcAsLwPbNWdI2andpUgD3Qx9Jsh3VS7nyF8bgqJMxUAz73/kBa+epX
Date: 23 Aug 2013 18:04:11 -0000
Message-ID: <20130823180411.50961.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Fwd: [dnsext] SPF isn't going to change, was Deprecating SPF
In-Reply-To: <82E79956-CC08-41DB-A522-9B65520909F5@isi.edu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: bmanning@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 18:04:39 -0000

>>> Nobody has argued that SPF usage is zero, and the reasons for
>>> deprecating SPF have been described repeatedly here and on the ietf
>>> list, so this exercise seems fairly pointless.
>> 
>> 	the reasons for not deprecating SPF have been described here
>> 	and on the ietf list repeatedly ... yet there has been little
>> 	concrete data regarding deployment uptake.

Sigh.  We have RFC 6686.  Since this is clearly an issue you consider
to be of vital importance, it is baffling that (as far as I can tell)
you did not contribute to or even comment on it when it was being
written and published.

Those of us in the mail community have a lot of anecdotal evidence,
too.  Most notably, none of the large providers that dominate the mail
world publish or check type 99, and the one that used to check type 99
(Yahoo) doesn't any more.  You don't have to like it, but it's silly
to deny it.

In any event, it's purely a strawman that "nobody" checks type 99.  A
few people do, the WG knows that, and we decided for well documented
reasons to deprecate it anyway.

R's,
John

From scott.brim@gmail.com  Fri Aug 23 11:06:58 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1BFB11E8121 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:06:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.697
X-Spam-Level: 
X-Spam-Status: No, score=-101.697 tagged_above=-999 required=5 tests=[AWL=0.903, 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 ri55CK2PZv8z for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:06:58 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7B49711E80C5 for <ietf@ietf.org>; Fri, 23 Aug 2013 11:06:57 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id i10so1142219oag.2 for <ietf@ietf.org>; Fri, 23 Aug 2013 11:06: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; bh=T6qE/5zfjmJGkOeCbOjqA5LvdT519oxFDORB9cR/hso=; b=Luv0FAx370tNBkg11IL0GyhDT874VCWY3uFlPlmfJKJv8JqfBOXHNMmohxn0I2M9BD Ov85z3tdeBPr1zKqVFsl6vwvRU6Kn9iUlyrO7yeeKizb3KfiebF0DymXhOgJQuuvwT0u COP/D9xC3x+oAiKb7SVKVonMOuG0kFyLgv04VBWZmF2xmrEEQ8g5H8YrfZItfavIwkNw iomefDd4epJyusFyszVYpYh6bSS+cZifK6KGVpNpfIPB/7bk1Re7RIdaVL10Y6wOADLH wf14NZ3WAH4QEvZir/7WrvXAFc0YsKnV3enF46sUioU45Y5GPW/ZwiyDyxSNCNBhQZZ5 sciA==
X-Received: by 10.60.47.230 with SMTP id g6mr759005oen.62.1377281216995; Fri, 23 Aug 2013 11:06:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Fri, 23 Aug 2013 11:06:36 -0700 (PDT)
In-Reply-To: <5216D331.8070502@dcrocker.net>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <5216D331.8070502@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 23 Aug 2013 14:06:36 -0400
Message-ID: <CAPv4CP_Yg=LKafmzXYHBLMkXAUQFG=mmODje4AyBXxpCKRzM7Q@mail.gmail.com>
Subject: Re: The Last Call social contract (was - Re: Rude responses)
To: Crocker Dave <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c2db58b1e7d004e4a14500
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 18:06:59 -0000

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

On Thu, Aug 22, 2013 at 11:12 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> In pragmatic terms, the current operational model for a LC (and IESG)
> review tends to enforce no rules or limits to what can be challenged or
> suggested, while simultaneously expecting those who have been doing the
> work to then be responsible for educating the commenter and defending
> decisions in the document, at the level of re-arguing resolved issues.
> Your admonition that "these folks are already at a disadvantage"
> encourages this sense of obligation.
>
> However this is direct contradiction to our published rules for Last Call:
>
>    RFC 2418, Working Group Guidelines and Procedures
>    Section 8, Review of documents
>
>    "It is important to note
>    that a Last-Call is intended as a brief, final check with the
>    Internet community, to make sure that no important concerns have been
>    missed or misunderstood. The Last-Call should not serve as a more
>    general, in-depth review."
>
> Note that last sentence.  It's the essential point, if we are to have
> any real /respect/ for the extended effort already put into developing
> the document.


Remember the discussion about how "last call" is more like the middle of a
document's evolution, and we should admit that in our process
documentation?  This is closely related.  If, in reality, people are
frustrated at the attempted rapid pace of last calls, then we should allow
for that.  We have time.  We don't have to be like the ones we all know who
sneer at anyone presuming to get in the way of their code going into
production.  Simple comments and questions -- your "educating everyone who
tracked the wrong group" -- can be dealt with easily through referral.
 Even substantial ones can be directed to specific discussion threads.
 Real issues can be considered.  It's only too late if we say it is, in our
processes, and if an issue is substantial, it should never be too late.

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

<div dir=3D"ltr">On Thu, Aug 22, 2013 at 11:12 PM, Dave Crocker <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcro=
cker.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">In pragmatic terms, the current operational =
model for a LC (and IESG)<br>
review tends to enforce no rules or limits to what can be challenged or<br>
suggested, while simultaneously expecting those who have been doing the<br>
work to then be responsible for educating the commenter and defending<br>
decisions in the document, at the level of re-arguing resolved issues.<br>
Your admonition that &quot;these folks are already at a disadvantage&quot;<=
br>
encourages this sense of obligation.<br>
<br>
However this is direct contradiction to our published rules for Last Call:<=
br>
<br>
=A0 =A0RFC 2418, Working Group Guidelines and Procedures<br>
=A0 =A0Section 8, Review of documents<br>
<br>
=A0 =A0&quot;It is important to note<br>
=A0 =A0that a Last-Call is intended as a brief, final check with the<br>
=A0 =A0Internet community, to make sure that no important concerns have bee=
n<br>
=A0 =A0missed or misunderstood. The Last-Call should not serve as a more<br=
>
=A0 =A0general, in-depth review.&quot;<br>
<br>
Note that last sentence. =A0It&#39;s the essential point, if we are to have=
<br>
any real /respect/ for the extended effort already put into developing<br>
the document. =A0</blockquote><div><br></div><div>Remember the discussion a=
bout how &quot;last call&quot; is more like the middle of a document&#39;s =
evolution, and we should admit that in our process documentation? =A0This i=
s closely related. =A0If, in reality, people are frustrated at the attempte=
d rapid pace of last calls, then we should allow for that. =A0We have time.=
 =A0We don&#39;t have to be like the ones we all know who sneer at anyone p=
resuming to get in the way of their code going into production. =A0Simple c=
omments and questions -- your &quot;educating everyone who tracked the wron=
g group&quot; -- can be dealt with easily through referral. =A0Even substan=
tial ones can be directed to specific discussion threads. =A0Real issues ca=
n be considered. =A0It&#39;s only too late if we say it is, in our processe=
s, and if an issue is substantial, it should never be too late.</div>

</div></div></div>

--001a11c2db58b1e7d004e4a14500--

From johnl@iecc.com  Fri Aug 23 11:06:59 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DF3911E80C5 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.622
X-Spam-Level: 
X-Spam-Status: No, score=-102.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30hgtyglzCNr for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:06: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 D3A8811E80ED for <ietf@ietf.org>; Fri, 23 Aug 2013 11:06:54 -0700 (PDT)
Received: (qmail 54550 invoked from network); 23 Aug 2013 18:06:54 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 Aug 2013 18:06: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; s=5217a4bd.xn--hew.k1308; i=johnl@user.iecc.com; bh=dgZZppH4LEHwI2NPEaCshLttR+7u+wAvLGX/VbeL1fU=; b=qbLWBMazsm6rtKt4AnJtw/QRgPFp0mUwJlQKrdT7z6d31LYcY9Gh3ax5wnkyD5E2Pw7PaZ6fUZpH00JHmVzoI3CZ/Qk/g9/tPfqVWT8LDweKMyNCcx6XIKjiYGUsMHMibnZ0EoHiOAvDPtg6EQ6tEfLFsQgGowwKAUaJsMr2D5GkYfdQ60/9UY2fzSUvqfFQnwQWsn6US6ECB/uDlIWPYQBH200UlnHS+EG2vxD3P9OtlYML9YvSHTM9oK6LV3rk
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5217a4bd.xn--hew.k1308; olt=johnl@user.iecc.com; bh=dgZZppH4LEHwI2NPEaCshLttR+7u+wAvLGX/VbeL1fU=; b=G6JEs2z2/V+fus40RQfcZfjf1n44v8VSMLdXB+gdFOQ+xt3oZb5zQ93HlN2p6EvqWW28iloGgw+Qh/xd8KymtQJApO8fifESupciouU2gnF9yy4PHGPlGMDxzZkDepO+qteAgK7WK5Ylqs+npHVzJkXx3zk2IOiE2XCH8MPAOgX9awTW9AIy741GhAh8bnhCBrV41IGuivLj1FSMgC9vkO2di4fmtfnIoVbg3rYBcAeWP13NBvUaFyyoFGdBUjRe
Date: 23 Aug 2013 18:06:31 -0000
Message-ID: <20130823180631.50990.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF 88 - Registration Now Open!
In-Reply-To: <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: bmanning@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 18:06:59 -0000

In article <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu> you write:
>and the hotel is fully booked….

Not if you use the link on the meeting hotel page.

http://www.ietf.org/meeting/88/hotel.html

R's,
John

From tjc@ecs.soton.ac.uk  Fri Aug 23 11:12:35 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 527A721F85EE; Fri, 23 Aug 2013 11:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcRKO2aNwCby; Fri, 23 Aug 2013 11:12:34 -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 CAFB311E80EC; Fri, 23 Aug 2013 11:12:33 -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 r7NICQXu016284;  Fri, 23 Aug 2013 19:12:26 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r7NICQXu016284
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1377281546; bh=0lijcads9KwGe1dzRTPkV8Hn+lw=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=dhszbpBHcJbUdk4+lgeWotqgAo/yt8eE/ZOGNGXrhrlRJEy3ILCO+l04QvwOMDUa9 NYxX9ibk/CcPaC6RntR+Yq15yfzL+M9fB6Ou/mC8pTFtOCGerC84arSdnIMUtnWqCf NQkPc6frUa3/BmULaIodWIHsS1a2tSogg8XKxOo4=
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 p7MJCQ05445469528B ret-id none; Fri, 23 Aug 2013 19:12:26 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r7NIBkcA027958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 23 Aug 2013 19:12:21 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: IETF 88 - Registration Now Open!
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu>
Date: Fri, 23 Aug 2013 19:12:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|81b379a0d8b8b62d08fdda835102184ap7MJCQ03tjc|ecs.soton.ac.uk|6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>
References: <20130823133657.18756.43809.idtracker@ietfa.amsl.com> <B4828B8F-B900-4DC1-AD3E-7E3044FB81FD@isi.edu> <6A33E98E-A5B1-4E98-9491-53065E54B515@ecs.soton.ac.uk>
To: manning bill <bmanning@isi.edu>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p7MJCQ054454695200; tid=p7MJCQ05445469528B; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r7NICQXu016284
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: wgchairs@ietf.org, ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>, irsg@irtf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 18:12:35 -0000

On 23 Aug 2013, at 18:49, manning bill <bmanning@isi.edu> wrote:

> and the hotel is fully booked=85.

I guess it got fixed Bill, though I only booked for the meeting week =
itself.

tim

>=20
> /bill
>=20
>=20
> On 23August2013Friday, at 6:36, IETF Secretariat wrote:
>=20
>> 88th IETF Meeting
>> Vancouver, BC, Canada
>> November 3-8, 2013
>> Host: Huawei
>>=20
>> Meeting venue:  Hyatt Regency Vancouver: =
http://vancouver.hyatt.com/en/hotel/home.html
>>=20
>> Register online at: http://www.ietf.org/meetings/88/
>>=20
>> 1.  Registration
>> 2.  Visas & Letters of Invitation
>> 3.  Accommodations
>> 4.  Companion Program
>>=20
>>=20
>> 1. Registration
>> A. Early-Bird Registration - USD 650.00 Pay by Friday, 25 October =
2013 UTC 24:00
>> B. After Early-Bird cutoff - USD 800.00
>> C. Full-time Student Registrations - USD 150.00 (with proper ID)
>> D. One Day Pass Registration - USD 350.00
>> E. Registration Cancellation  =20
>>             Cut-off for registration cancellation is Monday,
>>             28 October 2013 at UTC 24:00.
>>             Cancellations are subject to a 10% (ten percent)
>>             cancellation fee if requested by that date and time.
>> F. Online Registration and Payment ends Friday, 1 November 2013, 1700 =
local Vancouver time.
>> G. On-site Registration starting Sunday, 3 November 2013 at 1100 =
local Vancouver time.
>>=20
>> 2. Visas & Letters of Invitation:
>> Information on Visiting Canada, please visit:
>> http://www.cic.gc.ca/english/visit/index.asp
>>=20
>> After you complete the registration process, you can request an =
electronic IETF letter of invitation as well. The registration system =
also allows for you to request a hard copy IETF letter of invitation. =
You may also request one at a later time by following the link provided =
in the confirmation email.
>>=20
>> Please note that the IETF Letter of Invitation may not be sufficient =
for obtaining a visa to enter Canada.
>>=20
>> 3.  Accommodations
>> The IETF is holding a block of guest rooms at the Hyatt Regency =
Vancouver, the meeting venue, as well as at the overflow hotel Fairmont =
Hotel Vancouver, which is located across the street from the Hyatt.
>> Room Rates include in room high-speed Internet access. Taxes of 16.5% =
(hotel room tax, GST and Destination Management Fee) are excluded from =
the guestroom rate and are subject to change. Room rates DO NOT include =
daily breakfast.
>>=20
>> Reservations Cut off Date:=20
>> 	Hyatt Regency Vancouver - 20 October 2013
>> 	Fairmont Hotel Vancouver - 11 October 2013
>>=20
>> For additional information on rates and policies, please visit: =
http://www.ietf.org/meetin/88/hotel.html
>>=20
>> 4.  Companion Program
>> If you are traveling with a friend or family member over 18 years of =
age you can register them for the IETF Companion Program for only USD =
25.00
>>=20
>> Benefits include:
>> - A special welcome reception for companions from 1630-1730 on =
Sunday, 3 November
>> - Ability to attend the official Welcome Reception from 1700-1900 on =
Sunday, 3 November
>> - A distinctive meeting badge that grants access to the venue (not to =
be used to attend working sessions)
>> - Participation in a separate companion email list if you choose to =
help communicate and make plans with other IETF Companions.
>>=20
>> You can register your companion at any time via the IETF website or =
onsite at the meeting.
>>=20
>> To join the 88 companions mailing list only see:
>> https://www.ietf.org/mailman/listinfo/88companions
>>=20
>> Only 71 days until the Vancouver IETF!
>=20


From sm@elandsys.com  Fri Aug 23 12:34:44 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F6111E8106 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 12:34:43 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIfdQEeg8eC9 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 12:34:28 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1D911E80E4 for <ietf@ietf.org>; Fri, 23 Aug 2013 12:34:27 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.74]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7NJYBcu016847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 12:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377286465; bh=AS4/lTDoYW8d6M2mZXCKfYMAg/SMnqIL0GJWVDold1c=; h=Date:To:From:Subject:In-Reply-To:References; b=GpkuEvXbzZeNX1aCUDh7iJ+hc040O86ShLO5vnkZK/F7KJ2a7MfO8OQ4z6RcgJwJq awd+31VifC/8B0tLTCiYUMD4fWtRXAI5RyxxLnbVTBgL53hB2u4Zm7MCqd7qCUi0D3 0RXWN+O/TieOKSCcEzVMdFPddEJYBmvgQpxBdb3k=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377286465; i=@elandsys.com; bh=AS4/lTDoYW8d6M2mZXCKfYMAg/SMnqIL0GJWVDold1c=; h=Date:To:From:Subject:In-Reply-To:References; b=Qe43konT3hFiGUq2jLKhtI62MiXU1c01nBhSxmqK/X7LiTq75GQvR6BExXiiKkhTN 41TYGyFqacb850cBHAPrVnCIk9Wj6aYemcC9HhV91RDdgz6RAvW/iadrxKRKXKBiP3 Q/nR6vatlHAgN4D/6+4E8+XCV6ZIZINGEw1Pa0N4=
Message-Id: <6.2.5.6.2.20130823095122.0bae7920@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 23 Aug 2013 11:43:41 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130823143402.49936.qmail@joyce.lan>
References: <521728B4.5070302@sidn.nl> <20130823143402.49936.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 19:34:44 -0000

Hello,

This message has a Bcc to an IETF participant.

In my write-up for the Responsible Area Director I mentioned that:

   "There was an intermediate conclusion about the topic of whether the SPF
    protocol should use the SPF RRTYPE or the TXT resource record.  It was
    followed by an objection.  After discussion of the topic at the IETF 83
    SPFBIS WG session the conclusion reached was that the decision would be
    not to publish RRTYPE 99 and and not to query RRTYPE 99.  The WG
    consensus about the RRTYPE can be described as particularly rough.  The
    topic of obsoleting the SPF RRTYPE generated a lot of controversy near
    the end of the WGLC.  There were a very high number of messages about
    the topic on the SPFBIS mailing list and the DNSEXT mailing list as some
    DNSEXT WG participants were not aware of RFC 6686."

The WGLC announcement [1] for draft-ietf-spfbis-4408bis-14 was sent 
on April 9, 2013 and it was mentioned that the WGLC will close on 
April 24.  I posted my review as document shepherd on April 23 [2] 
and looked into the IANA Considerations Section of the draft as there 
is a question in the write-up about whether the IANA Considerations 
are clear and complete.  Something unusual occurred.  A very high 
number of messages were posted about on a thread about the DNS 
Parameters registry [3].  Most of the comments were submitted after 
the end of the WGLC.  On April 25, the Responsible Area Director [4] 
commented that:

   "This discussion should have happened at SPFBIS *chartering* time, as it is
    crystal clear from the charter that existing features currently 
in use in SPF
    are not going away. Indeed, the TXT record was specifically 
mentioned in the
    charter."

In another message he commented [5] that:

  "If you think SPFBIS was being superficial in its treatment of this topic
   and can identify an argument that was missed, fine."

The thread was left to run in case an argument was missed.  The 
SPFBIS WG Chairs [6] posted a message on April 30 about "the planned 
deprecation of the SPF RRTYPE and whether TXT is an appropriate thing 
to use and if it is whether the SPF use of it is ok".

There is the following text in the write-up:

  "Some WG participants have mentioned that they may express extreme
   discontent about the decision to obsolete the SPF RRTYPE during
   the Last Call."

That is a notification to the Responsible Area Director and the other 
members of the IESG about the matter.

I reviewed the discussion about the RRTYPE several times in doing the 
write-up and after that to determine whether the following is correct:

   "The WG consensus about the RRTYPE can be described as particularly rough."

I did not find any problem in the process followed to reach that 
conclusion.  I read the messages posted on the IETF mailing list [7]; 
there are around a 100 messages.  I didn't notice any messages about 
an issue with the above statement.

Regards,
S. Moonesamy (as document shepherd)

1. http://www.ietf.org/mail-archive/web/spfbis/current/msg03347.html
2. http://www.ietf.org/mail-archive/web/spfbis/current/msg03414.html
3. http://www.ietf.org/mail-archive/web/spfbis/current/msg03412.html
4. http://www.ietf.org/mail-archive/web/spfbis/current/msg03497.html
5. http://www.ietf.org/mail-archive/web/spfbis/current/msg03507.html
6. http://www.ietf.org/mail-archive/web/spfbis/current/msg03681.html
7. http://www.ietf.org/mail-archive/web/ietf/current/msg81609.html


From dhc@dcrocker.net  Fri Aug 23 12:47:12 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5991D11E810E for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 12:47:12 -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 sROlT4dHq9fW for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 12:47:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 59B7811E8106 for <ietf@ietf.org>; Fri, 23 Aug 2013 12:47:07 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7NJku6l011195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 23 Aug 2013 12:47:00 -0700
Message-ID: <5217BC14.6000000@dcrocker.net>
Date: Fri, 23 Aug 2013 12:46:28 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: The Last Call social contract (was - Re: Rude responses)
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <5216D331.8070502@dcrocker.net> <CAPv4CP_Yg=LKafmzXYHBLMkXAUQFG=mmODje4AyBXxpCKRzM7Q@mail.gmail.com>
In-Reply-To: <CAPv4CP_Yg=LKafmzXYHBLMkXAUQFG=mmODje4AyBXxpCKRzM7Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 23 Aug 2013 12:47:00 -0700 (PDT)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 19:47:12 -0000

On 8/23/2013 11:06 AM, Scott Brim wrote:
> We don't have to be like the ones we all know who sneer at anyone
> presuming to get in the way of their code going into production.


Since this is such a fundamental point, I'm sending this reply to emphasize:

    The concern I expressed had nothing at all to do with this.

What prompted my note that in turn prompted Pete's was a form of 
counter-productive LC behavior that I consider to be abusive and since 
it was from a highly experienced participant, inexcusable.

Serious questions and suggestions from serious reviewers/critics are 
/essential/ to IETF quality assurance and I have as little patience for 
the sneering you describe as anyone else.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From bmanning@isi.edu  Fri Aug 23 12:47:38 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF8021F962D; Fri, 23 Aug 2013 12:47:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.499
X-Spam-Level: 
X-Spam-Status: No, score=-106.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YZ0fjzn2VaJR; Fri, 23 Aug 2013 12:47:32 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C082511E81F6; Fri, 23 Aug 2013 12:47:28 -0700 (PDT)
Received: from [192.168.0.3] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7NJkSRw025210 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 23 Aug 2013 12:46:37 -0700 (PDT)
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20130823180411.50961.qmail@joyce.lan>
Date: Fri, 23 Aug 2013 12:46:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu>
References: <20130823180411.50961.qmail@joyce.lan>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: "ietf@ietf.org list" <ietf@ietf.org>, dnsext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 19:47:38 -0000

On 23August2013Friday, at 11:04, John Levine wrote:

>>>> Nobody has argued that SPF usage is zero, and the reasons for
>>>> deprecating SPF have been described repeatedly here and on the ietf
>>>> list, so this exercise seems fairly pointless.
>>>=20
>>> 	the reasons for not deprecating SPF have been described here
>>> 	and on the ietf list repeatedly ... yet there has been little
>>> 	concrete data regarding deployment uptake.
>=20
> Sigh.  We have RFC 6686.  Since this is clearly an issue you consider
> to be of vital importance, it is baffling that (as far as I can tell)
> you did not contribute to or even comment on it when it was being
> written and published.

work assignments occasionally take me away from active engagement in
IETF matters.  sorry for the few years absence. =20


> Those of us in the mail community have a lot of anecdotal evidence,
> too.  Most notably, none of the large providers that dominate the mail
> world publish or check type 99, and the one that used to check type 99
> (Yahoo) doesn't any more.  You don't have to like it, but it's silly
> to deny it.

	not sure why you think the DNS data presented is anecdotal.  =
Looked
	kind of empirical to me.   i've not seen a yahoo person describe =
what=20
	they have or have not done or why.  we have no data on why =
Microsoft
	may or may not support type 99 (see Jay's questions).   Much of =
the
	mail community data seems anecdotal=85  very little first hand, =
empirical=20
	stuff.  (and I thank you for your data)

> In any event, it's purely a strawman that "nobody" checks type 99.  A
> few people do, the WG knows that, and we decided for well documented
> reasons to deprecate it anyway.

	demuxing type 16 records is a choice.  using type 99,  which was =
specifically
	designed for this use, is a choice.  using application specific =
types have distinct
	technological advantages (see PHB comments).  They may be small, =
but are real
	and have an impact on the DNS and the application.

	regarding the specific claims regarding adoption, I was asking =
for a brief period
	to collect more empirical data to track the magnitude and ratio =
of type 99 v. type 16
	use (noting, as PAF has already noted, that not all type 16 =3D=3D=
 type 99, so for accurate
	understanding - someone needs to look at type 99 muxed into a =
type 16 format=85  if only
	to correctly understand the change in ratio.

	the question is not that "nobody" checks type 99, the question =
is "is the rate of adoption
	of type 99 -changing- in relation to type 16?

>=20
> R's,
> John


From doug.mtview@gmail.com  Fri Aug 23 13:07:57 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4FB21F9D70 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 13:07: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, 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 n79ZrnD1FYuK for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 13:07:56 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id C81EB21F9D3A for <ietf@ietf.org>; Fri, 23 Aug 2013 13:07:55 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so1071632pbb.19 for <ietf@ietf.org>; Fri, 23 Aug 2013 13:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:message-id:mime-version:date:subject:cc:to; bh=u+ey8YR5iucRKaHf19mge9mboZN2XF5wtxt4OGX+S9A=; b=Qj6pUI2bqJl4gHXZhOa2kO45bK7Od5WUOOUimjDomaZIXAlDRRh8Qtn7AJU3N4pSHt A0wfmtjHhLdQd1dZpvC5Vrvd4Kco8Bm6COj8Arlw1ecmGhzc32H6xhoVCibKUV0OmT4t 3h4zQTJu2ta1nDf6KLyaHmJhV2kdAisoRcX9VV6f36bZdFNBfCU8q2fl3uOxp/Yrp8XT zZvnpwiY970CVh8TW67K74PSZPwU8xVKixXWAkD8RG0x7a5iOij0XZVn2FT/RVeD8zZH lxWO8KxXb3yUtg7V3nNRz/AZESgmWqTyORKv11pgWn8o1uvwt2ugTDpuY/jlGMOIuPB7 YPew==
X-Received: by 10.68.189.229 with SMTP id gl5mr1486355pbc.77.1377288475431; Fri, 23 Aug 2013 13:07:55 -0700 (PDT)
Received: from ?IPv6:2601:9:7680:308:bd6e:fa53:5922:224c? ([2601:9:7680:308:bd6e:fa53:5922:224c]) by mx.google.com with ESMTPSA id dg3sm1565424pbc.24.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Aug 2013 13:07:54 -0700 (PDT)
From: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_01382BF1-C2EC-4C1C-9F19-8020B034F86A"
Message-Id: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Date: Fri, 23 Aug 2013 13:07:51 -0700
Subject: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
Cc: 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: Fri, 23 Aug 2013 20:07:57 -0000

--Apple-Mail=_01382BF1-C2EC-4C1C-9F19-8020B034F86A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


The SPFbis document improperly conflates DNS terminology with identical =
terms invented by this document. Examples are terms used to describe =
mechanisms having the same identifier differentiated between mechanisms =
and DNS resource records by using lower and upper case respectively.  =
References to SPF records are differentiated by a textual prefix and not =
by TYPE as defined by DNS.

In addition, the MARID WG NEVER reached consensus.  A follow-on group =
operating outside of the IETF required a promise of support to subscribe =
to their mailing list.  When one looks at how SPF is commonly used, the =
pre-existing APL resource record offered an effective alternative, but =
was oppose by a particular vendor unwilling to fully implement DNS.  =
Currently this vendor is seldom used to directly interface with MTAs on =
the Internet and no longer justifies the use of the TXT records.  As =
such, the SPF Resource Record should not have been deprecated.

This draft should be made Informational and not Standards Track.

Section 4.6.4 fails to offer a sufficiently clear warning about =
potential magnitudes of DNS transactions initiated by a single SPF =
evaluation where two are recommended to occur one for the separate =
identifiers.  In fact, this section appears to make assurances no more =
that 10 DNS queries will result and is widely misunderstood.=20

4.6.4.  DNS Lookup Limits

Was:
,--
SPF implementations MUST limit the total number of mechanisms and
modifiers ("terms") that cause any DNS query to 10 during SPF
evaluation.
'--

Change to:
,---
SPF evaluation must limit the number of mechanisms, and the modifier
term 'redirect' to occur in no more than10 instances within the
evaluation process.  The mechanisms 'ip4', ip6', and 'all' are
excluded from this instance limitation.  Each mechanism is permitted
to resolve subsequent resource record sets (RRsets) that MUST not
contain more than 10 resource records to complete a match check.
When the number of instances exceeds 10, or when subsequent
resolutions exceeds 10, check_host() MUST produce a =93permerror=94
result.

The maximum number of DNS transactions initiated by an SPF
evaluation is therefore 1 for the initial SPF resource record, 10 for
each mechanism times 10 transactions needed to complete a matching
process for a total of 111 DNS transactions.  This number excludes
those required by DNS to fulfill a request and those required by an
EXP modifier.

The recommended 20 second evaluation timeout imposes a maximum
network distance of less than 27,000 kilometers or a little more than
half the circumference of the Earth.  Even a 60 millisecond delay can
result in more than a 6.6 seconds consumed by the round trip
overhead needed for each SPF evaluation.

The overall resulting maximum number of DNS transactions for
both "HELO" and "MAIL FROM" is 222 DNS transactions.  Since
check_host() introduces macros and name expansions that
combine mechanisms and modifiers in a manner not directly
supported by DNS, the entire set and sequence of SPF based=20
DNS transactions is required for each evaluation.  While SPF now
has a 2 limit of void lookups, use of synthetic domains has become
a popular technique for tracking traffic which can be used by
malefactors to overcome this SPF void lookup limit.=20

Once DNSsec becomes a requirement, SPF will have created an=20
inordinate number of transactions and overall traffic per message
exchange that will impose a SIGNIFICANT reflected amplification risk.
'---

Related information:

<random-string>cdr-ds.metric.gstatic.com
<random-string>.g.vm.akamaistream.net
are domains on sizable networks that act as a wildcards.  In the second =
instance, the wildcard points to a CNAME that then resolves an A record. =
 Such use compared against =
http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01 produces a much =
larger amplification than the x320 gain estimated.  Use of DNSsec =
further increases this gain estimate.  Although details differ from case =
to case, the synthetic domain technique is seeing greater use.  One of =
the initial reasons for using TXT records without any prefix was to =
permit use of wildcards.  This dangerous feature means SPF allows =
malefactors to leverage any large TXT resource record that otherwise =
would not have been problematic.  Again this risk increases when DNSsec =
becomes required and represents another reason for not deprecating the =
SPF resource record type.=20

Remove this misleading paragraph within section 4.6.4:
,---
When evaluating the "mx" mechanism, the number of "MX" resource
records queried is included in the overall limit of 10 mechanisms/
modifiers that cause DNS lookups described above.  The evaluation of
each "MX" record MUST NOT result in querying more than 10 address
records, either "A" or "AAAA" resource records.  If this limit is
exceeded, the "mx" mechanism MUST produce a "permerror" result.
'---

MX resource records do not contain IP addresses.=20
Per RFC1035 the structure for an MX record is roughly as follows:

A 16 bit PREFERENCE (distance) value followed by an MTA hostname. =20

A DNS MX reply may offer A records for the hostnames in the Additional =
Section however per:
Per RFC2181 Section 5.4:
,---
Servers must never merge RRs from a response with RRs in their
cache to form an RRSet.  If a response contains data that would form
an RRSet with data in a server's cache the server must either ignore
the RRs in the response, or discard the entire RRSet currently in the
cache, as appropriate.
'---

This will not prove ideal for SPF with respect to effective use of DNS.

Also hostnames contained within MX resource record might be within any =
domain, and not necessarily the same domain as that of the base SPF =
record.

Per RFC2181 5.4.1. Ranking data
An authoritative answer from a reply should replace cached data that had =
been obtained from additional information in an earlier reply. However =
additional information from a reply will be ignored if the cache =
contains data from an authoritative answer or a zone file.


Mistake.

Section 3.4=20

Second paragraph:

Similarly, the sizes for replies to all queries related to SPF have to =
be evaluated to fit in a single 512 octet UDP packet.

s/UDP packet/DNS message/

Per RFC1035=20
Section 2.3.4. Size limits
UDP messages    512 octets or less


Section 4.2.1. UDP usage
Messages carried by UDP are restricted to 512 bytes (not counting the IP =
or UDP headers).

The DNS message size limitation is not the same as a UDP packet limit as =
suggested in Section 3.4.


The SPFbis WG charter permitted removal of unused protocol elements =
where the =93ptr=94 mechanism was deprecated and the SPF resource type =
was removed. Use of SPF=92s very dangerous macro feature currently has =
less than 0.053% of the domains making use of these macros and clearly =
falls below the WG removal threshold.  We have also been told by a few =
very large providers that SPF records containing any macro reference are =
ignored for reasons related to both efficiency and security.  Marcos =
also inhibit the primary use by large providers which is to compile the =
domain=92s IP address list.

The WG should have been told to focus on security and at better insuring =
interchange to achieve a safer stance moving forward.

Regards,
Douglas Otis=

--Apple-Mail=_01382BF1-C2EC-4C1C-9F19-8020B034F86A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br>
<div style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">The SPFbis document improperly conflates =
DNS terminology with identical terms invented by this document. Examples =
are terms used to describe mechanisms having the same identifier =
differentiated between mechanisms and DNS resource records by using =
lower and upper case respectively.&nbsp; References to SPF records are =
differentiated by a textual prefix and not by TYPE as defined by =
DNS.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">In =
addition, the MARID WG NEVER reached consensus.&nbsp; A follow-on group =
operating outside of the IETF required a promise of support to subscribe =
to their mailing list.&nbsp; When one looks at how SPF is commonly used, =
the pre-existing APL resource record offered an effective alternative, =
but was oppose by a particular vendor unwilling to fully implement =
DNS.&nbsp; Currently this vendor is seldom used to directly interface =
with MTAs on the Internet and no longer justifies the use of the TXT =
records.&nbsp; As such, the SPF Resource Record should not have been =
deprecated.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">This draft =
should be made Informational and not Standards Track.</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; min-height: =
15px; "><span style=3D"letter-spacing: 0.0px"></span><br></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Section 4.6.4 fails to offer a =
sufficiently clear warning about potential magnitudes of DNS =
transactions initiated by a single SPF evaluation where two are =
recommended to occur one for the separate identifiers.&nbsp; In fact, =
this section appears to make assurances no more that 10 DNS queries will =
result and is widely misunderstood.&nbsp;</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; min-height: =
15px; "><span style=3D"letter-spacing: 0.0px"></span><br></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">4.6.4.&nbsp; DNS Lookup =
Limits</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">Was:</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">,--</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">SPF =
implementations MUST limit the total number of mechanisms =
and</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">modifiers ("terms") that =
cause any DNS query to 10 during SPF</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">evaluation.</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">'--</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Change to:</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">,---</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">SPF evaluation must limit the number of =
mechanisms, and the modifier</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">term 'redirect' to occur in no more than10 instances within =
the</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">evaluation =
process.&nbsp; The mechanisms 'ip4', ip6', and 'all' =
are</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">excluded from this =
instance limitation.&nbsp; Each mechanism is permitted</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">to resolve subsequent resource record =
sets (RRsets) that MUST not</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">contain more than 10 resource records to complete a match =
check.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">When the =
number of instances exceeds 10, or when subsequent</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">resolutions exceeds 10, check_host() =
MUST produce a =93permerror=94</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">result.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">The maximum =
number of DNS transactions initiated by an SPF</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">evaluation is therefore 1 for the =
initial SPF resource record, 10 for</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">each mechanism times 10 transactions =
needed to complete a matching</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">process for a total of 111 DNS transactions.&nbsp; This number =
excludes</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">those =
required by DNS to fulfill a request and those required by =
an</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">EXP =
modifier.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">The =
recommended 20 second evaluation timeout imposes a =
maximum</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">network =
distance of less than 27,000 kilometers or a little more =
than</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">half the =
circumference of the Earth.&nbsp; Even a 60 millisecond delay =
can</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">result in more than a =
6.6 seconds consumed by the round trip</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">overhead needed for each SPF =
evaluation.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">The overall =
resulting maximum number of DNS transactions for</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">both "HELO" and "MAIL FROM" is 222 DNS =
transactions.&nbsp; Since</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">check_host() introduces macros and name expansions =
that</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">combine =
mechanisms and modifiers in a manner not directly</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">supported by DNS, the entire set and =
sequence of SPF based&nbsp;</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">DNS transactions is required for each evaluation.&nbsp; While SPF =
now</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">has a 2 limit of void =
lookups, use of synthetic domains has become</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">a popular technique for tracking traffic =
which can be used by</span></div><div style=3D"margin: 0px; font-size: =
11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">malefactors to overcome this SPF void lookup =
limit.&nbsp;</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Once DNSsec =
becomes a requirement, SPF will have created an&nbsp;</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">inordinate number of transactions and =
overall traffic per message</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">exchange that will impose a SIGNIFICANT reflected amplification =
risk.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">'---</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Related =
information:</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">&lt;random-string&gt;<a =
href=3D"http://cdr-ds.metric.gstatic.com">cdr-ds.metric.gstatic.com</a></s=
pan></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">&lt;random-string&gt;.<a =
href=3D"http://g.vm.akamaistream.net">g.vm.akamaistream.net</a></span></di=
v><div style=3D"margin: 0px; font-size: 11px; font-family: Monaco; =
"><span style=3D"letter-spacing: 0.0px">are domains on sizable networks =
that act as a wildcards.&nbsp; In the second instance, the wildcard =
points to a CNAME that then resolves an A record.&nbsp; Such use =
compared against <a =
href=3D"http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01"><span =
style=3D"letter-spacing: 0px; color: rgb(2, 30, 170); =
">http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01</span> =
</a>produces a much larger amplification than the x320 gain =
estimated.&nbsp; Use of DNSsec further increases this gain =
estimate.&nbsp; Although details differ from case to case, the synthetic =
domain technique is seeing greater use.&nbsp; One of the initial reasons =
for using TXT records without any prefix was to permit use of =
wildcards.&nbsp; This dangerous feature means SPF allows malefactors to =
leverage any large TXT resource record that otherwise would not have =
been problematic.&nbsp; Again this risk increases when DNSsec becomes =
required and represents another reason for not deprecating the SPF =
resource record type.&nbsp;</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Remove this misleading paragraph within =
section 4.6.4:</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">,---</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">When =
evaluating the "mx" mechanism, the number of "MX" =
resource</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">records =
queried is included in the overall limit of 10 =
mechanisms/</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">modifiers =
that cause DNS lookups described above.&nbsp; The evaluation =
of</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">each "MX" record MUST =
NOT result in querying more than 10 address</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">records, either "A" or "AAAA" resource =
records.&nbsp; If this limit is</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">exceeded, the "mx" mechanism MUST produce a "permerror" =
result.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">'---</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">MX resource =
records do not contain IP addresses.&nbsp;</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Per RFC1035 the structure for an MX =
record is roughly as follows:</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">A 16 bit PREFERENCE (distance) value =
followed by an MTA hostname. &nbsp;</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">A DNS MX reply may offer A records for =
the hostnames in the Additional Section however per:</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Per RFC2181 Section =
5.4:</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">,---</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Servers =
must never merge RRs from a response with RRs in their</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">cache to form an RRSet.&nbsp; If a =
response contains data that would form</span></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">an RRSet with data in a server's cache =
the server must either ignore</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">the RRs in the response, or discard the entire RRSet currently in =
the</span></div><div style=3D"margin: 0px; font-size: 11px; font-family: =
Monaco; "><span style=3D"letter-spacing: 0.0px">cache, as =
appropriate.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">'---</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">This will =
not prove ideal for SPF with respect to effective use of =
DNS.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Also =
hostnames contained within MX resource record might be within any =
domain, and not necessarily the same domain as that of the base SPF =
record.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Per RFC2181 =
5.4.1. Ranking data</span></div><div style=3D"margin: 0px; font-size: =
11px; font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">An =
authoritative answer from a reply should replace cached data that had =
been obtained from additional information in an earlier reply. However =
additional information from a reply will be ignored if the cache =
contains data from an authoritative answer or a zone =
file.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: =
0.0px">Mistake.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Section =
3.4&nbsp;</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Second =
paragraph:</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Similarly, =
the sizes for replies to all queries related to SPF have to be evaluated =
to fit in a single 512 octet UDP packet.</span></div><div style=3D"margin:=
 0px; font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">s/UDP packet/DNS =
message/</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Per =
RFC1035&nbsp;</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Section =
2.3.4. Size limits</span></div><div style=3D"margin: 0px; font-size: =
11px; font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">UDP =
messages&nbsp; &nbsp; 512 octets or less</span></div><div style=3D"margin:=
 0px; font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Section 4.2.1. UDP =
usage</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">Messages =
carried by UDP are restricted to 512 bytes (not counting the IP or UDP =
headers).</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">The DNS =
message size limitation is not the same as a UDP packet limit as =
suggested in Section 3.4.</span></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; min-height: 15px; "><span =
style=3D"letter-spacing: 0.0px"></span><br></div><div style=3D"margin: =
0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">The SPFbis WG charter permitted removal =
of unused protocol elements where the =93ptr=94 mechanism was deprecated =
and the SPF resource type was removed. Use of SPF=92s very dangerous =
macro feature currently has less than 0.053% of the domains making use =
of these macros and clearly falls below the WG removal threshold.&nbsp; =
We have also been told by a few very large providers that SPF records =
containing any macro reference are ignored for reasons related to both =
efficiency and security.&nbsp; Marcos also inhibit the primary use by =
large providers which is to compile the domain=92s IP address =
list.</span></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; min-height: 15px; "><span style=3D"letter-spacing: =
0.0px"></span><br></div><div style=3D"margin: 0px; font-size: 11px; =
font-family: Monaco; "><span style=3D"letter-spacing: 0.0px">The WG =
should have been told to focus on security and at better insuring =
interchange to achieve a safer stance moving forward.</span></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; min-height: =
15px; "><span style=3D"letter-spacing: 0.0px"></span><br></div><div =
style=3D"margin: 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Regards,</span></div><div style=3D"margin:=
 0px; font-size: 11px; font-family: Monaco; "><span =
style=3D"letter-spacing: 0.0px">Douglas Otis</span></div></body></html>=

--Apple-Mail=_01382BF1-C2EC-4C1C-9F19-8020B034F86A--

From hsantos@isdg.net  Fri Aug 23 13:23:45 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6C1011E810E for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 13:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.406
X-Spam-Level: 
X-Spam-Status: No, score=-102.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lew7nv5j5d4s for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 13:23:40 -0700 (PDT)
Received: from winserver.com (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3A311E8106 for <ietf@ietf.org>; Fri, 23 Aug 2013 13:23:39 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3457; t=1377289413; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=YjMlck1PLTYmYetymMP3kQcZMT8=; b=CDdA7DNp3t15aTtofYxu duKohociDUv/R1v3Py68O9TcGprpKVB4xVS7YDOPHqze7ARLAqrwF4+yLZeyGtXk hIpAPK+3ofeK6YgrgKpfIIFUlOu1iPhnoC3uWRpFwfJm+VsItAj8HE44gf1QE0GX uOfex6YwehK6o4Sc1shRvSU=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 23 Aug 2013 16:23:33 -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 3751927132.3203.3000; Fri, 23 Aug 2013 16:23:32 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3457; t=1377289100; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=NTAGSIU yjYiOq7xaDcBRO8GPImaaK1SqexubimfXy6s=; b=IZa/VCpcMlOMimI2ALXt8Iq dhOLa1RdmL0CgydfaaOgP5/BcY+n92y7gcTQFjd1karXoN4e80YmOai9YVHHTF3W 5dJO4PcqkYOMLVczm1TIw/UExheZVwJIk30ZOXr7KNhHthX4RPa99vvSZ9cGsyCu c6L2TK8YYzsXasXl85ig=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 23 Aug 2013 16:18:20 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3198347408.9.900; Fri, 23 Aug 2013 16:18:18 -0400
Message-ID: <5217C4BC.2030302@isdg.net>
Date: Fri, 23 Aug 2013 16:23:24 -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: dcrocker@bbiw.net
Subject: Re: The Last Call social contract (was - Re: Rude responses)
References: <20130819150521.GB21088@besserwisser.org>	<20130819190533.GA30516@besserwisser.org>	<4751241.GTNxysAlzm@scott-latitude-e6320>	<B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org>	<CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com>	<20130821040003.GL607@mx1.yitter.info>	<64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org>	<7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se>	<521495EB.7060207@cisco.com>	<1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se>	<5214A593.8030907@cisco.com>	<E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se>	<5214F97B.2080400@dcrocker.net>	<6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se>	<52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com>	<5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com>	<521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com>	<5216D331.8070502@dcrocker.net>	<CAPv4CP_Yg=LKafmzXYHBLMkXAUQFG=mmODje4AyBXxpCKRzM7Q@mail.gmail.com> <5217BC14.6000000@dcrocker.net>
In-Reply-To: <5217BC14.6000000@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 20:23:45 -0000

Dave Crocker wrote:
> On 8/23/2013 11:06 AM, Scott Brim wrote:
>> We don't have to be like the ones we all know who sneer at anyone
>> presuming to get in the way of their code going into production.
> 
> 
> Since this is such a fundamental point, I'm sending this reply to 
> emphasize:
> 
>    The concern I expressed had nothing at all to do with this.
> 
> What prompted my note that in turn prompted Pete's was a form of 
> counter-productive LC behavior that I consider to be abusive and since 
> it was from a highly experienced participant, inexcusable.
> 
> Serious questions and suggestions from serious reviewers/critics are 
> /essential/ to IETF quality assurance and I have as little patience for 
> the sneering you describe as anyone else.
> 
> d/

My particular concern is that you using this "abusive" argument 
increasingly against people leading to a next public suggestion to 
justify invoking IETF moderation, if necessary.

Once a well respected senior member as yourself speaks as such, people 
do listen and its extremely intimidating to constantly see this 
threatening form of excommunications and moderation against folks.  If 
one responds, then they are risk of getting labeled abusive, and hence 
moderation is invoked.

In my opinion, I don't see highly debated issues like the SPF typ99e 
issue all the time with last calls. At least I don't or I don't get 
involved with it if its not related to my work.  This rarity suggest 
that the IETF LC system still works and that we are simply 
experiencing a real divided technical infrastructure design issue that 
was highly predictable to be a conflict outside the working group. 
Pete suggested as much with fewer cross area reviews occurring within 
the IETF.  I agree that this is one of those diversity improvements 
areas.  Not enough cross area peer review before the WGLC and IETF LC 
takes place.  The goal is to minimizes these contentious engineering 
issues.

I have been involved with the SPF protocol before MARID, during MARID, 
an early adopter and also involved in the SPFBIS efforts.  It is my 
assessment the SPFBIS WG
did not receive adequate cross area reviews and DNS industry input 
*before* the removal decision was made, which was practically 
immediate and expected before the first draft was even written. 
Instead, the same "already discussed" arguments was used and the 
removal decision was implemented in the draft.

In my opinion, there was significant concerns about the removal within 
the WG and outside the WG, yet the decision was made to pull it anyway 
at the IETF meeting.  This immediately put the burden on everyone to 
reverse or at least get a better discussion going about keeping the 
migration path and also get a better handle of whats going on with the 
dearth in the supportive infrastructure for the handling of unknown RR 
types.

In my opinion, it would be better to seek the input from DNS vendors 
to see what the future is regarding new RR types and passthru handling 
of unknown types (RFC 3597). I request reaching out to folks in 
Microsoft DNS product management to determine what has fell through 
the cracks.  If there is continued lack of interest, then the SPF 
type99 removal is reasonable to me.

You seem to think that this was already done. I don't think so. 
Perhaps you believe that the infrastructure will never be ready to 
support new RR types.  If so, that is important to know.

--
HLS





From sm@elandsys.com  Fri Aug 23 15:01:36 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B727811E812C for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 15:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zoNKlxO3S8Ur for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 15:01:35 -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 AECF111E8123 for <ietf@ietf.org>; Fri, 23 Aug 2013 15:01:33 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.74]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7NM16Tq008474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 23 Aug 2013 15:01:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377295280; bh=mRBDktiO8lSmg9Rj7pnrmrDHR/Wfugv6fTOJZyl92/o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TNSNcnrdey76I8ifm/i121xqxQGHmBLqGJqcklSi8versp/bw82Z9X+LamMZL2qNA Okr4LQDR+s+2QNWAI2dBosajm9lE3JIr7GLI/73UvAwZ/pq/jAZsD9X9oaHn+YClUc HLPy10hg6+7U1/gQQU9to8o4D/rZ+CZhITgzDfyA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377295280; i=@elandsys.com; bh=mRBDktiO8lSmg9Rj7pnrmrDHR/Wfugv6fTOJZyl92/o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rTkcuygS6ztC/fHENoVFq9G5uuRT1w9WfL0Umnx8mqt2IK7/JKunQVbbxee8UX9Ht 22ovKvGXqrVH6SKgpRkxsNmNGLU0AMOiqa8Tah6Y8BEGwIkuhSP1GRi6PeT2NgLo0+ QAbdSZACvvdsSRqkBptDv0NFQDo45wdc7t4d8XkE=
Message-Id: <6.2.5.6.2.20130823134125.0da55800@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 23 Aug 2013 14:42:10 -0700
To: dcrocker@bbiw.net
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The Last Call social contract (was - Re: Rude responses)
In-Reply-To: <5217BC14.6000000@dcrocker.net>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <5216D331.8070502@dcrocker.net> <CAPv4CP_Yg=LKafmzXYHBLMkXAUQFG=mmODje4AyBXxpCKRzM7Q@mail.gmail.com> <5217BC14.6000000@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 22:01:36 -0000

Hi Dave,

I read the messages on this thread.  I suggested to the participant 
to comment.  I am okay with the comments which were made.  I had an 
off-list exchange before the message that generated the other 
thread.  The exchange was not antagonistic.

Some people read "please read the archives" as a requirement.  That 
led to a misunderstanding.  During a Last Call someone has to figure 
out what the issues are and whether they have been addressed or 
not.  The misunderstandings do not make the work easier.

Regards,
S. Moonesamy


From hallam@gmail.com  Fri Aug 23 16:09:56 2013
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 252B721F9BB6 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 16:09:56 -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, 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 1SeKABHpL3yP for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 16:09:55 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 6D38F21F9974 for <ietf@ietf.org>; Fri, 23 Aug 2013 16:09:54 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id t61so1108012wes.28 for <ietf@ietf.org>; Fri, 23 Aug 2013 16:09:53 -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=RActKm3dqrHbu1vJWfMsE/B8HzJvGoNFL+gx0te/uWM=; b=VYsMkFQRFgMfGK2wr5J9rvb4sj76vm4fvJcCx7Dkwk2arHgy2fQPEBOGtdIR08KUKM 1gOoeo0r68X/AQ8HQVLXlhBGqiQdRnGrjp/1PzKcV87NFlIMehZBzWp9D8aEUlq1NOpE 2xredPTJIQ3KlvbZpgFA8Q0MJu4Xa+vQMJjVL46vCDXjLJJfDiZR2tL8GiY7qTohN9aA aWR9oDExsxwvuA3LO6UhIEpXZiXqgBkbrI6hPMYUzUJHRen3e9MtkdqpRZKG1hIvwKKM aIWXid7g4nlK2S73Re2XjvgM3x91Csc9i6x8UuVz+xrKmdPiTWB3OlOmZOJowdVmsQ35 0Yaw==
MIME-Version: 1.0
X-Received: by 10.194.241.228 with SMTP id wl4mr1580286wjc.2.1377299393530; Fri, 23 Aug 2013 16:09:53 -0700 (PDT)
Received: by 10.194.6.67 with HTTP; Fri, 23 Aug 2013 16:09:53 -0700 (PDT)
In-Reply-To: <5217BC14.6000000@dcrocker.net>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com> <521533DB.4040001@dcrocker.net> <52161EB1.6010506@qti.qualcomm.com> <5216D331.8070502@dcrocker.net> <CAPv4CP_Yg=LKafmzXYHBLMkXAUQFG=mmODje4AyBXxpCKRzM7Q@mail.gmail.com> <5217BC14.6000000@dcrocker.net>
Date: Fri, 23 Aug 2013 19:09:53 -0400
Message-ID: <CAMm+LwhmYtsQin1swAdxr_c6nkVYjLVrKKUzNNpf9wRTZ6Tx4w@mail.gmail.com>
Subject: Re: The Last Call social contract (was - Re: Rude responses)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e01493c3219d2f704e4a58186
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Aug 2013 23:09:56 -0000

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

On Fri, Aug 23, 2013 at 3:46 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 8/23/2013 11:06 AM, Scott Brim wrote:
>
>> We don't have to be like the ones we all know who sneer at anyone
>> presuming to get in the way of their code going into production.
>>
>
>
> Since this is such a fundamental point, I'm sending this reply to
> emphasize:
>
>    The concern I expressed had nothing at all to do with this.
>
> What prompted my note that in turn prompted Pete's was a form of
> counter-productive LC behavior that I consider to be abusive and since it
> was from a highly experienced participant, inexcusable.
>
> Serious questions and suggestions from serious reviewers/critics are
> /essential/ to IETF quality assurance and I have as little patience for the
> sneering you describe as anyone else.


I think you were out of line because the type of issues being raised are
precisely the type of issues that are appropriate to raise in IETF last
call, indeed are the reason for having an IETF wide last call in the first
place.

If I see a WG railroading a scheme that I think is botched architecturally
then of course IETF LC is the place to raise it. Adding in a requirement,
sure.

In this case the issues being raised are a repeat of the arguments made
from ten years ago and I don't have much sympathy for them given the way
the folk raising them behaved then and in particular their total lack of
concern for the deployment issues raised by the group.

But I don't criticize them on the process question, IETF LC is exactly the
place to raise this issue. It is one area kibitzing on the work of another.
That is an IETF layer issue for sure.




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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 23, 2013 at 3:46 PM, Dave Crocker <span dir=3D"ltr">&lt=
;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 8/23/2013 11:06 AM, Sco=
tt Brim wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We don&#39;t have to be like the ones we all know who sneer at anyone<br>
presuming to get in the way of their code going into production.<br>
</blockquote>
<br>
<br></div>
Since this is such a fundamental point, I&#39;m sending this reply to empha=
size:<br>
<br>
=A0 =A0The concern I expressed had nothing at all to do with this.<br>
<br>
What prompted my note that in turn prompted Pete&#39;s was a form of counte=
r-productive LC behavior that I consider to be abusive and since it was fro=
m a highly experienced participant, inexcusable.<br>
<br>
Serious questions and suggestions from serious reviewers/critics are /essen=
tial/ to IETF quality assurance and I have as little patience for the sneer=
ing you describe as anyone else.</blockquote><div><br></div><div>I think yo=
u were out of line because the type of issues being raised are precisely th=
e type of issues that are appropriate to raise in IETF last call, indeed ar=
e the reason for having an IETF wide last call in the first place.</div>
<div><br></div><div>If I see a WG railroading a scheme that I think is botc=
hed architecturally then of course IETF LC is the place to raise it. Adding=
 in a requirement, sure.</div><div><br></div><div>In this case the issues b=
eing raised are a repeat of the arguments made from ten years ago and I don=
&#39;t have much sympathy for them given the way the folk raising them beha=
ved then and in particular their total lack of concern for the deployment i=
ssues raised by the group.=A0</div>
<div><br></div><div>But I don&#39;t criticize them on the process question,=
 IETF LC is exactly the place to raise this issue. It is one area kibitzing=
 on the work of another. That is an IETF layer issue for sure.</div><div>
<br></div><div><br></div><div><br></div><div>=A0</div></div>-- <br>Website:=
 <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e01493c3219d2f704e4a58186--

From sm@elandsys.com  Sat Aug 24 03:18:19 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6BD421F9D56 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 03:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j33z6k3GaPrP for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 03:18:18 -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 4F8E321F9D39 for <ietf@ietf.org>; Sat, 24 Aug 2013 03:18:16 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.232.200]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7OAHtGX021244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 24 Aug 2013 03:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377339489; bh=xXWOHuDWquXiff+5gplidPIIEx2uZQH8bHKdOainAC8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QHm1bZ9cURbYPY/l0MD7D3SxGTs5f6xUXcEnKBi3fBh8DSP4ArH34MRmdCjapoBaR kOGCjPh2CCyl4gpgMCbg8rO09r6N0A4/Ne8MSAImcKRG5TRPC/B4phlXUDeF2F2nmH oV+ugcOzhHl2CJWMHqvgWaeVF4o6RQe1Zn3o1CEA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377339489; i=@elandsys.com; bh=xXWOHuDWquXiff+5gplidPIIEx2uZQH8bHKdOainAC8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gMCZful4Z0LmpOBHKJ7fbuOCe5F1iDSMzxuXSlKe71yFxomeoLZlePTRwkwBLS/eF VBvr4ee7695UKEyNpUlJCUNQwSd1XZHqY4F37XVvJcCyzdM2+aSis1KDDJxb3vaR1y mWGeR1CzLojLncS0gFbiZ7kB5yzfnB/2MCrT8hMY=
Message-Id: <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 24 Aug 2013 03:16:30 -0700
To: Douglas Otis <doug.mtview@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@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: Sat, 24 Aug 2013 10:18:19 -0000

Hi Doug,
At 13:07 23-08-2013, Douglas Otis wrote:
>The SPFbis document improperly conflates DNS terminology with 
>identical terms invented by this document. Examples are terms used 
>to describe mechanisms having the same identifier differentiated 
>between mechanisms and DNS resource records by using lower and upper 
>case respectively.  References to SPF records are differentiated by 
>a textual prefix and not by TYPE as defined by DNS.

Could you provide some examples of the above as I would like to 
clearly understand the argument?

>In addition, the MARID WG NEVER reached consensus.  A follow-on 
>group operating outside of the IETF required a promise of support to 
>subscribe to their mailing list.  When one looks at how SPF is 
>commonly used, the pre-existing APL resource record offered an 
>effective alternative, but was oppose by a particular vendor 
>unwilling to fully implement DNS.  Currently this vendor is seldom 
>used to directly interface with MTAs on the Internet and no longer 
>justifies the use of the TXT records.  As such, the SPF Resource 
>Record should not have been deprecated.

There are other messages on the Last Call about the SPF Resource 
Record.  I'll take up the above together with the other comments.

>This draft should be made Informational and not Standards Track.

I suggest providing arguments for that.

>Section 4.6.4 fails to offer a sufficiently clear warning about 
>potential magnitudes of DNS transactions initiated by a single SPF 
>evaluation where two are recommended to occur one for the separate 
>identifiers.  In fact, this section appears to make assurances no 
>more that 10 DNS queries will result and is widely misunderstood.

There is a discussion about Section 4.6.4 at 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html

>4.6.4.  DNS Lookup Limits
>
>Was:
>,--
>SPF implementations MUST limit the total number of mechanisms and
>modifiers ("terms") that cause any DNS query to 10 during SPF
>evaluation.
>'--
>
>Change to:
>,---
>SPF evaluation must limit the number of mechanisms, and the modifier
>term 'redirect' to occur in no more than10 instances within the
>evaluation process.  The mechanisms 'ip4', ip6', and 'all' are
>excluded from this instance limitation.  Each mechanism is permitted
>to resolve subsequent resource record sets (RRsets) that MUST not
>contain more than 10 resource records to complete a match check.
>When the number of instances exceeds 10, or when subsequent
>resolutions exceeds 10, check_host() MUST produce a "permerror"
>result.
>
>The maximum number of DNS transactions initiated by an SPF
>evaluation is therefore 1 for the initial SPF resource record, 10 for
>each mechanism times 10 transactions needed to complete a matching
>process for a total of 111 DNS transactions.  This number excludes
>those required by DNS to fulfill a request and those required by an
>EXP modifier.

I'll list the above as not addressed yet.

>The recommended 20 second evaluation timeout imposes a maximum
>network distance of less than 27,000 kilometers or a little more than
>half the circumference of the Earth.  Even a 60 millisecond delay can
>result in more than a 6.6 seconds consumed by the round trip
>overhead needed for each SPF evaluation.

During the WGLC Murray Kucherawy asked a question about the 20 second 
evaluation timeout ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03700.html 
).  The answer was that the timeout is already in RFC 4408.

>The overall resulting maximum number of DNS transactions for
>both "HELO" and "MAIL FROM" is 222 DNS transactions.  Since
>check_host() introduces macros and name expansions that
>combine mechanisms and modifiers in a manner not directly
>supported by DNS, the entire set and sequence of SPF based
>DNS transactions is required for each evaluation.  While SPF now
>has a 2 limit of void lookups, use of synthetic domains has become
>a popular technique for tracking traffic which can be used by
>malefactors to overcome this SPF void lookup limit.

The draft agenda for the IETF 83 session was posted to the SPFBIS 
mailing list on March 14, 2012. One of the items on that agenda was 
"DNS amplification attacks" ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg01021.html 
).  It would have been good more discussion of the issue (Issue #24) 
from a DNS perspective.  As there has been numerous comments about 
the DNS angle during this Last Call, maybe an IETF participant will 
be able to provide some input about the above.

>Once DNSsec becomes a requirement, SPF will have created an
>inordinate number of transactions and overall traffic per message
>exchange that will impose a SIGNIFICANT reflected amplification risk.

draft-ietf-spfbis-4408bis-19 does not have any DNSSEC requirement.

>'---
>
>Related information:
>
><random-string>cdr-ds.metric.gstatic.com
><random-string>.g.vm.akamaistream.net
>are domains on sizable networks that act as a wildcards.  In the 
>second instance, the wildcard points to a CNAME that then resolves 
>an A record.  Such use compared against 
>http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01 produces a 
>much larger amplification than the x320 gain estimated.  Use of 
>DNSsec further increases this gain estimate.  Although details 
>differ from case to case, the synthetic domain technique is seeing 
>greater use.  One of the initial reasons for using TXT records 
>without any prefix was to permit use of wildcards.  This dangerous 
>feature means SPF allows malefactors to leverage any large TXT 
>resource record that otherwise would not have been 
>problematic.  Again this risk increases when DNSsec becomes required 
>and represents another reason for not deprecating the SPF resource record type.

I welcome comments from other IETF participants about the above.

>Remove this misleading paragraph within section 4.6.4:
>,---
>When evaluating the "mx" mechanism, the number of "MX" resource
>records queried is included in the overall limit of 10 mechanisms/
>modifiers that cause DNS lookups described above.  The evaluation of
>each "MX" record MUST NOT result in querying more than 10 address
>records, either "A" or "AAAA" resource records.  If this limit is
>exceeded, the "mx" mechanism MUST produce a "permerror" result.
>'---
>
>MX resource records do not contain IP addresses.
>Per RFC1035 the structure for an MX record is roughly as follows:
>
>A 16 bit PREFERENCE (distance) value followed by an MTA hostname.
>
>A DNS MX reply may offer A records for the hostnames in the 
>Additional Section however per:
>Per RFC2181 Section 5.4:
>,---
>Servers must never merge RRs from a response with RRs in their
>cache to form an RRSet.  If a response contains data that would form
>an RRSet with data in a server's cache the server must either ignore
>the RRs in the response, or discard the entire RRSet currently in the
>cache, as appropriate.
>'---
>
>This will not prove ideal for SPF with respect to effective use of DNS.
>
>Also hostnames contained within MX resource record might be within 
>any domain, and not necessarily the same domain as that of the base SPF record.
>
>Per RFC2181 5.4.1. Ranking data
>An authoritative answer from a reply should replace cached data that 
>had been obtained from additional information in an earlier reply. 
>However additional information from a reply will be ignored if the 
>cache contains data from an authoritative answer or a zone file.

I agree that MX resource records do not contain IP addresses.  There 
is a thread at 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html 
about reasonable DNS error limits.  I could not spot the problem in 
the paragraph that is described as misleading.  An example to 
illustrate the problem might make it clearer.

>Mistake.
>
>Section 3.4
>
>Second paragraph:
>
>Similarly, the sizes for replies to all queries related to SPF have 
>to be evaluated to fit in a single 512 octet UDP packet.
>
>s/UDP packet/DNS message/

My understanding of the working group discussion is that the intent 
is to have the DNS reply fit within a UDP packet.

>Per RFC1035
>Section 2.3.4. Size limits
>UDP messages    512 octets or less
>
>
>Section 4.2.1. UDP usage
>Messages carried by UDP are restricted to 512 bytes (not counting 
>the IP or UDP headers).
>
>The DNS message size limitation is not the same as a UDP packet 
>limit as suggested in Section 3.4.

I am not sure whether the above refers to the "450 octets".  I'll 
note a comment from Andrew Sullivan ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03103.html ) 
so that I don't have to search for it again.

>The SPFbis WG charter permitted removal of unused protocol elements 
>where the "ptr" mechanism was deprecated and the SPF resource type 
>was removed. Use of SPF's very dangerous macro feature currently has 
>less than 0.053% of the domains making use of these macros and 
>clearly falls below the WG removal threshold.  We have also been 
>told by a few very large providers that SPF records containing any 
>macro reference are ignored for reasons related to both efficiency 
>and security.  Marcos also inhibit the primary use by large 
>providers which is to compile the domain's IP address list.

There was an appeal about the meaning of the word "unused" ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg02167.html 
).  I'll highlight a comment from Pete Resnick:

   "There's also the comment from Doug Otis about the local-part
    macro. I'm inclined to declare that out of scope, maybe after a
    recharter. That's not documenting current practice, but is an overt
    change."

There are some threads about local part macros:

http://www.ietf.org/mail-archive/web/spfbis/current/msg00911.html
http://www.ietf.org/mail-archive/web/spfbis/current/msg01870.html

There is a short thread and a few other threads about the "ptr" 
mechanism ( 
http://www.ietf.org/mail-archive/web/spfbis/current/msg00808.html 
http://www.ietf.org/mail-archive/web/spfbis/current/msg00811.html 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03184.html ).

There is the following text in the write-up:

    "There was some controversy about whether the use of macros was a
     security risk and whether to deprecate the PTR feature.  There was a
     formal appeal of the SPFBIS WG chair' interpretation of the charter,
     specifically regarding the removal of "unused" features.  The two
     features in particular which drove the appeal were the PTR feature
     and the local-part macro feature.  These features were not removed
     from the document given that the appeal was denied by the Responsible
     Area Director."

I hope that the above explains the decision.

>The WG should have been told to focus on security and at better 
>insuring interchange to achieve a safer stance moving forward.

The working group was reminded about BCP 72.

Regards,
S. Moonesamy (as document shepherd) 


From hallam@gmail.com  Sat Aug 24 05:39:39 2013
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 D250311E80EE; Sat, 24 Aug 2013 05:39:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  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 T43lPVvtSyE3; Sat, 24 Aug 2013 05:39:39 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BBFB911E80E9; Sat, 24 Aug 2013 05:39:38 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id r12so302604lbi.1 for <multiple recipients>; Sat, 24 Aug 2013 05:39: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=NA1OMCFbmP/wiUbmMqFk3MYYnlvqvUiuOXFfRnq0BDY=; b=N6IL5x0bRxJcj48fFiiUrJRlS+0v91AU9YFLrFQvG3RFgHQtgeTJnwD6PxOq331DXp LaVnbTP6/N+vQVf0uQ8Pe2SjqZzhtblCN7oi+fCWzBIVt77Ptttpj7iC98mITjMM1LSq wCtEyVGeWlrpnlmrPJYrS0FbLjET8j2IotXOb6+kc3xcWgy9Tic0vqJSQbFFOwHtrksU OBqJOQKhpYXRv0Q02lBimugHuPycxFmyQXJeYkA44/8jjRCb7SdyJn1TyEPPrlvFORPg jeah2MzDA91834NqVQK2mTSkI7vxjzNI92AMyq7MkpfQT5zW7J7RpBZLTm+4i7igMSqU DNlQ==
MIME-Version: 1.0
X-Received: by 10.152.6.97 with SMTP id z1mr1519639laz.26.1377347976423; Sat, 24 Aug 2013 05:39:36 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Sat, 24 Aug 2013 05:39:36 -0700 (PDT)
In-Reply-To: <5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu>
References: <20130823180411.50961.qmail@joyce.lan> <5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu>
Date: Sat, 24 Aug 2013 08:39:36 -0400
Message-ID: <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com>
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
From: Phillip Hallam-Baker <hallam@gmail.com>
To: manning bill <bmanning@isi.edu>
Content-Type: multipart/alternative; boundary=089e01493964ddef0704e4b0d0a1
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org list" <ietf@ietf.org>, "dnsext@ietf.org" <dnsext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 12:39:40 -0000

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

On Fri, Aug 23, 2013 at 3:46 PM, manning bill <bmanning@isi.edu> wrote:

>
>         the question is not that "nobody" checks type 99, the question is
> "is the rate of adoption
>         of type 99 -changing- in relation to type 16?
>

As John pointed out, support for checking type 99 has decreased and
continues to decrease rather than increase. So waiting longer is not going
to solve the issue.

Putting a statement in an RFC does not mean that the world will
automatically advance towards that particular end state.

Forcing a WG to adopt a position to suit another constituency is not going
to lead them to advocate for that position in deployment constituencies.
Particularly when the original constituency does nothing to advance
deployment.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 23, 2013 at 3:46 PM, manning bill <span dir=3D"ltr">&lt=
;<a href=3D"mailto:bmanning@isi.edu" target=3D"_blank">bmanning@isi.edu</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br></div>
=A0 =A0 =A0 =A0 the question is not that &quot;nobody&quot; checks type 99,=
 the question is &quot;is the rate of adoption<br>
=A0 =A0 =A0 =A0 of type 99 -changing- in relation to type 16?<br></blockquo=
te><div><br></div><div>As John pointed out, support for checking type 99 ha=
s decreased and continues to decrease rather than increase. So waiting long=
er is not going to solve the issue.</div>
<div><br></div><div>Putting a statement in an RFC does not mean that the wo=
rld will automatically advance towards that particular end state.</div><div=
><br></div><div>Forcing a WG to adopt a position to suit another constituen=
cy is not going to lead them to advocate for that position in deployment co=
nstituencies. Particularly when the original constituency does nothing to a=
dvance deployment.=A0</div>
</div><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://ha=
llambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e01493964ddef0704e4b0d0a1--

From hsantos@isdg.net  Sat Aug 24 09:27:10 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B337711E8134 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 09:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7K40MqQFi0Ji for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 09:27:05 -0700 (PDT)
Received: from dkim.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 35D5211E8133 for <ietf@ietf.org>; Sat, 24 Aug 2013 09:27:04 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2368; t=1377361620; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=R/y9uqWIBRyn/0CeTsN7Qo0niEg=; b=Q2lwBq0YZ009hBJw4a4W u3aUmMCY+Rf4k5zJWFk1n0B5Tn1M6I4AVjNCvRz7d8pHoFjovyK0e4Cc55fFm6BJ ixr4gaErTawYgDqBFTZcyzVhwoozbY9p8fztBjgciESCksOzazhpNmRAJrhWa5TH vFvN0F4jrZp1cKYo/a7A2Ts=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 12:27:00 -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 3824133053.4187.5800; Sat, 24 Aug 2013 12:26:59 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2368; t=1377361304; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=J1j3wK8 Fy/YnffF0cjgInHDB9Qtkn/81cStws6Ztq1Y=; b=nVZ4dooV75iqPP7Pp5Qps+0 wA95BVlEvReXA9nZ6+W+d4R6QQWj5aofdV+pf5Nb4dvyLjBxUPpPSgMHVN4VHK/d HdVg5gGJGLahoNqELcp7t7jWP4faRDdWSkeOqb6hyXBFNGDvKm/HE+j7IS0+ZElP s/KgGSmir4AWXkezUg+Q=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 12:21:44 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3270551502.9.2168; Sat, 24 Aug 2013 12:21:42 -0400
Message-ID: <5218DEC9.3070600@isdg.net>
Date: Sat, 24 Aug 2013 12:26:49 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
References: <20130823180411.50961.qmail@joyce.lan>	<5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu> <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com>
In-Reply-To: <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@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
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "dnsext@ietf.org" <dnsext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 16:27:10 -0000

Phillip Hallam-Baker wrote:
> On Fri, Aug 23, 2013 at 3:46 PM, manning bill <bmanning@isi.edu> wrote:
> 
>>         the question is not that "nobody" checks type 99, the question is
>> "is the rate of adoption
>>         of type 99 -changing- in relation to type 16?
>>
> 
> As John pointed out, support for checking type 99 has decreased and
> continues to decrease rather than increase. So waiting longer is not going
> to solve the issue.

However, the interest never disappeared.  The issue is what are we 
waiting for now?  The DNS infrastructure support?  Why it that such a 
problem?  Who goes to these IETF meetings?  Where are the Microsoft 
DNS product managers in these discussions?  What do they have to say?

>
> Putting a statement in an RFC does not mean that the world will
> automatically advance towards that particular end state.

Thats correct. No one is forced to support RFC 4408bis.  From my 
perspective, there are four basic major changes to BIS - all optional:

   1 - Add Authentication-Result: 5322.header.
   2 - Relax SPF HardFail Policy rejections to Accept-Mark operations.
   3 - If 2 is perform, then add code to separate user failed messages.
   4 - Remove any support for SPF type99 queries and publishing.

For our SPF implementation, we never did #4 for lack of infrastructure 
readiness but are ready to support once the the backbone is ready for 
it. We will probably will do #1 for all non-HARDFAIL result but we 
won't do #2 because it will cause a high redesign cost with #3.  Not 
performing #3 would be a major security loophole is you begin to 
support #2. Until we are ready to do #3 and close that security 
loophole, #2 won't happen.

> Forcing a WG to adopt a position to suit another constituency is not going
> to lead them to advocate for that position in deployment constituencies.
> Particularly when the original constituency does nothing to advance
> deployment.

+1, but the decision makers really haven't ask the main DNS 
constituencies why they have not advanced their (DNS) software or made 
it flexible enough for another operators and administrators to 
add/manage new RR types or capable of passive and transparent handling 
of unknown type recursive passthru queries.

To me, this should be a project leadership responsibility to make sure 
the protocol requirements are realistic are not.

--
HLS



From hsantos@isdg.net  Sat Aug 24 09:40:13 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8BD11E80D2 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 09:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.034
X-Spam-Level: 
X-Spam-Status: No, score=-102.034 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-TsP+ahgrzl for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 09:40:08 -0700 (PDT)
Received: from dkim.winserver.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0CBE211E80F6 for <ietf@ietf.org>; Sat, 24 Aug 2013 09:40:07 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1752; t=1377362400; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=IbVsgFoxWMyYYfh9FPB8rbQms00=; b=tcV7WjedM52MJR8zQLrj IYLe0Y+6usXnV/MJf90+UG72QWTu9P2xnZmVJ6GnBFefrrNdwjYiYTfQaKIBstPw 9jGyCdyyfk3U4kuxGujR1gaBjZwLQG6B4BvCpVq6YrqtMWEye2V+/UNn2quo+fQ5 aCMqw1ewHVhyArwiiOMQHsg=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 12:40:00 -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 3824913307.4187.5780; Sat, 24 Aug 2013 12:39:59 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1752; t=1377362087; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=DXr0Xkr ZlLPx2lpc5ynV081kfcTdgogGFqnm4Qr3KmU=; b=yX2GMnxM1zsF1jo8ipQyrJq bmaxMhtGQw1wSblcQoZJc/cGDXxpfpf7Ou+9o3h1MO0dPx/FsZSkVgTH+VjG4YyT 1QZUgHaCN9QIEWapM1Qq73A5kd8dCd8TwYsR77+REpoiQTHOcKdL1SBh4SyOLBhY /sy6f+rwhjvuGL/yX2oc=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 12:34:47 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3271335237.9.2208; Sat, 24 Aug 2013 12:34:46 -0400
Message-ID: <5218E1D8.9000604@isdg.net>
Date: Sat, 24 Aug 2013 12:39:52 -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: [dnsext] SPF isn't going to change, was Deprecating SPF
References: <20130823180411.50961.qmail@joyce.lan>	<5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu>	<CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com> <5218DEC9.3070600@isdg.net>
In-Reply-To: <5218DEC9.3070600@isdg.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dnsext@ietf.org" <dnsext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 16:40:13 -0000

Hector Santos wrote:
> Phillip Hallam-Baker wrote:
>> Putting a statement in an RFC does not mean that the world will
>> automatically advance towards that particular end state.
> 
> Thats correct. No one is forced to support RFC 4408bis.  From my 
> perspective, there are four basic major changes to BIS - all optional:
> 
>   1 - Add Authentication-Result: 5322.header.
>   2 - Relax SPF HardFail Policy rejections to Accept-Mark operations.
>   3 - If 2 is perform, then add code to separate user failed messages.
>   4 - Remove any support for SPF type99 queries and publishing.
> 
> For our SPF implementation, we never did #4 for lack of infrastructure 
> readiness but are ready to support once the the backbone is ready for 
> it. We will probably will do #1 for all non-HARDFAIL result but we won't 
> do #2 because it will cause a high redesign cost with #3.  Not 
> performing #3 would be a major security loophole is you begin to support 
> #2. Until we are ready to do #3 and close that security loophole, #2 
> won't happen.

I should add:

     5- Deprecate PTR by removing PTR publishing support

We won't advocate this because for our small to mid size market, this 
is the lowest cost setup for them - using a PTR.  For all our domains, 
we use PTR as well.  No need to change it. This is one of those "Set 
it and Forget it" SPF record setups. Using the PTR was the default 
arrangement for most small/mid operations provided by most if not all 
the SPF Web Wizards.  This was removed in Scott's popular SPF wizard 
but not in other SPF wizards.  Note: The overhead concerns are passe 
with the trend of SMTP receivers doing PTR lookups, thus any 
transaction SPF validator will not contribute to any PTR network overhead.

--
HLS



From scott@kitterman.com  Sat Aug 24 09:54:04 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4104111E8103 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 09:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bmrhKTJE1Kw6 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 09:54:03 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id 25E1711E80D2 for <ietf@ietf.org>; Sat, 24 Aug 2013 09:54:02 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 85470D04085; Sat, 24 Aug 2013 12:53:54 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377363234; bh=InJZ7/ApGOpvXPhyoPI3x+V+LshNGgKMrodgNyDHF2s=; h=In-Reply-To:References:Subject:From:Date:To:From; b=kCMQf8gexsBBCJlotfLN/HV6T3qzmhBc6ztPKQ5cXpkpY3bO8x2AhC2Fse6vKNDhh kpqtRv3Jwhghywi+Pt41HLL/zXMAYLfI8giSmUKog9wRoZbn3gvFDbwZBLnqyMbctl IJ+LyFmn3T7cbDSmFI4iXwq2W0lCYNP+6njGnrzc=
Received: from [192.168.111.106] (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 3B831D04056;  Sat, 24 Aug 2013 12:53:54 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <5218E1D8.9000604@isdg.net>
References: <20130823180411.50961.qmail@joyce.lan> <5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu> <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com> <5218DEC9.3070600@isdg.net> <5218E1D8.9000604@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
From: Scott Kitterman <scott@kitterman.com>
Date: Sat, 24 Aug 2013 12:53:59 -0400
To: ietf@ietf.org
Message-ID: <9c35d474-9967-4d0d-a4a0-49cf650e4829@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 16:54:04 -0000

Hector Santos <hsantos@isdg.net> wrote:
>Hector Santos wrote:
>> Phillip Hallam-Baker wrote:
>>> Putting a statement in an RFC does not mean that the world will
>>> automatically advance towards that particular end state.
>> 
>> Thats correct. No one is forced to support RFC 4408bis.  From my 
>> perspective, there are four basic major changes to BIS - all
>optional:
>> 
>>   1 - Add Authentication-Result: 5322.header.
>>   2 - Relax SPF HardFail Policy rejections to Accept-Mark operations.
>>   3 - If 2 is perform, then add code to separate user failed
>messages.
>>   4 - Remove any support for SPF type99 queries and publishing.
>> 
>> For our SPF implementation, we never did #4 for lack of
>infrastructure 
>> readiness but are ready to support once the the backbone is ready for
>
>> it. We will probably will do #1 for all non-HARDFAIL result but we
>won't 
>> do #2 because it will cause a high redesign cost with #3.  Not 
>> performing #3 would be a major security loophole is you begin to
>support 
>> #2. Until we are ready to do #3 and close that security loophole, #2 
>> won't happen.
>
>I should add:
>
>     5- Deprecate PTR by removing PTR publishing support
>
>We won't advocate this because for our small to mid size market, this 
>is the lowest cost setup for them - using a PTR.  For all our domains, 
>we use PTR as well.  No need to change it. This is one of those "Set 
>it and Forget it" SPF record setups. Using the PTR was the default 
>arrangement for most small/mid operations provided by most if not all 
>the SPF Web Wizards.  This was removed in Scott's popular SPF wizard 
>but not in other SPF wizards.  Note: The overhead concerns are passe 
>with the trend of SMTP receivers doing PTR lookups, thus any 
>transaction SPF validator will not contribute to any PTR network
>overhead.

That's not correct.  PTR is not removed from the protocol, so software support shouldn't change.

I don't run an SPF wizard. 

It's not just about overhead. 

Scott K

From hsantos@isdg.net  Sat Aug 24 10:10:39 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDD9C11E8139 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 10:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.032
X-Spam-Level: 
X-Spam-Status: No, score=-102.032 tagged_above=-999 required=5 tests=[AWL=-0.297, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gjOCEwx1Fhjz for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 10:10:34 -0700 (PDT)
Received: from mail.santronics.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 934B211E8103 for <ietf@ietf.org>; Sat, 24 Aug 2013 10:10:34 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1708; t=1377364220; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=MdgWPcDTGgbrd8DX/irnLhtgSeQ=; b=Y5eEsr0F8ksISgyLSlyA wmPmGD2+otHVfxKp92sFXRZ4QEMExswht4QjQW2J9U8WrKkJJDOGMVZB9/LgX6wF xF6+ZOnUrmOw8AsJf6PWzTEnX1HNMByaYhC4r0worltDkehiZFmYgF1pRzOpIt4B 0/3A8e5xZLtOIo1HT60d7zc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 13:10: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 3826733621.4187.2924; Sat, 24 Aug 2013 13:10:20 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1708; t=1377363902; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Ewwd31H DZ3ZK7p2yGWycFyfXlYj7jYG4fH7TWqNfUmE=; b=eG8RKvxX0Az+1SQhoUQvqXV nxHqQxzsH0TcyyNVv02PYbGTjOO+2ohdFirU2FPmVp2y5EEdcrfZPv/rdqG1g5Cv QwBjvKrLGDwCv1tTFaO9SZgJ8UPN7/r8MQ2O7EkmN2F8k13/mt2P6nIs8/BNlPqP uigkX5Wt3HFMoojyGuIA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 13:05:02 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3273150393.9.2196; Sat, 24 Aug 2013 13:05:01 -0400
Message-ID: <5218E8F1.8090505@isdg.net>
Date: Sat, 24 Aug 2013 13:10:09 -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: SPF PTR Support [was SPF isn't going to change]
References: <20130823180411.50961.qmail@joyce.lan>	<5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu>	<CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com>	<5218DEC9.3070600@isdg.net> <5218E1D8.9000604@isdg.net> <9c35d474-9967-4d0d-a4a0-49cf650e4829@email.android.com>
In-Reply-To: <9c35d474-9967-4d0d-a4a0-49cf650e4829@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 17:10:39 -0000

Scott Kitterman wrote:
> Hector Santos <hsantos@isdg.net> wrote:

>> I should add:
>>
>>     5- Deprecate PTR by removing PTR publishing support
>>
>> We won't advocate this because for our small to mid size market, this 
>> is the lowest cost setup for them - using a PTR.  For all our domains, 
>> we use PTR as well.  No need to change it. This is one of those "Set 
>> it and Forget it" SPF record setups. Using the PTR was the default 
>> arrangement for most small/mid operations provided by most if not all 
>> the SPF Web Wizards.  This was removed in Scott's popular SPF wizard 
>> but not in other SPF wizards.  Note: The overhead concerns are passe 
>> with the trend of SMTP receivers doing PTR lookups, thus any 
>> transaction SPF validator will not contribute to any PTR network
>> overhead.
> 
> That's not correct.  PTR is not removed from the protocol, so 
> software support shouldn't change.

I believe I stated deprecate above which is the current draft 
recommendations for not recommending PTR publishing in SPF records. 
Is this still incorrect?

> I don't run an SPF wizard. 

I thought you managed this SPF wizard at http://openspf.org/tools ?? 
You don't? Ok I see it was taking down. Ok, sorry, well, you know what 
I mean - it did have the PTR publishing as part of a natural default 
setup and if not all the SPF wizards did as well. Is that not correct?

> It's not just about overhead. 

So why was PTR deprecated?

--
HLS

PS: I am not trying to change anything about the PTR 4408BIS status. 
Just pointing out that a change was made that does touch base with 
operations and thus not supporting (or delaying, forever) this part of 
4408BIS is highly possible.




From scott@kitterman.com  Sat Aug 24 17:25:17 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EEB311E81B5 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 17:25: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=[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 dfYAyRgwqvJ8 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 17:25:13 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2778111E81AC for <ietf@ietf.org>; Sat, 24 Aug 2013 17:25:13 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 53AA620E40D2; Sat, 24 Aug 2013 20:24:58 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377390310; bh=po2knj4u9ir4yvIEuM0wPB/o5qAIQFxoFif3EfgpYhY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=XMH9CcMUSgMdWqOk+MdzsAwNwZPHaCogUVEGY7pwCusqB4oAOkyb69K+/im368VLy mtHUCnjrjjMEahhzkKXzJOMT/gTy38p+g/Zdfh8wTSjZnYYILw9fgu4mQBnCVxeLxm QYdB6HFt/LbscalwzrbF8AcGVQIQFPwLEjGXwpbg=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 38BB720E4085;  Sat, 24 Aug 2013 20:24:57 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: SPF PTR Support [was SPF isn't going to change]
Date: Sat, 24 Aug 2013 20:24:56 -0400
Message-ID: <2972438.Fr2RSkezE0@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <5218E8F1.8090505@isdg.net>
References: <20130823180411.50961.qmail@joyce.lan> <9c35d474-9967-4d0d-a4a0-49cf650e4829@email.android.com> <5218E8F1.8090505@isdg.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 00:25:17 -0000

On Saturday, August 24, 2013 13:10:09 Hector Santos wrote:
> Scott Kitterman wrote:
> > Hector Santos <hsantos@isdg.net> wrote:
> >> I should add:
> >>     5- Deprecate PTR by removing PTR publishing support
> >> 
> >> We won't advocate this because for our small to mid size market, this
> >> is the lowest cost setup for them - using a PTR.  For all our domains,
> >> we use PTR as well.  No need to change it. This is one of those "Set
> >> it and Forget it" SPF record setups. Using the PTR was the default
> >> arrangement for most small/mid operations provided by most if not all
> >> the SPF Web Wizards.  This was removed in Scott's popular SPF wizard
> >> but not in other SPF wizards.  Note: The overhead concerns are passe
> >> with the trend of SMTP receivers doing PTR lookups, thus any
> >> transaction SPF validator will not contribute to any PTR network
> >> overhead.
> > 
> > That's not correct.  PTR is not removed from the protocol, so
> > software support shouldn't change.
> 
> I believe I stated deprecate above which is the current draft
> recommendations for not recommending PTR publishing in SPF records.
> Is this still incorrect?
> 
> > I don't run an SPF wizard.
> 
> I thought you managed this SPF wizard at http://openspf.org/tools ??
> You don't? Ok I see it was taking down. Ok, sorry, well, you know what
> I mean - it did have the PTR publishing as part of a natural default
> setup and if not all the SPF wizards did as well. Is that not correct?

It did.  That's part of why it was taken down.  It made poor recommendations 
and several people finally concluded having nothing was better than continuing 
to provide that one.

> > It's not just about overhead.
> 
> So why was PTR deprecated?

See http://tools.ietf.org/wg/spfbis/trac/ticket/27 and the ML archives.  The 
ticket can give you an idea of the time frame to look in the archives.  Note 
that the final language doesn't use the word "deprecated". 

> --
> HLS
> 
> PS: I am not trying to change anything about the PTR 4408BIS status.
> Just pointing out that a change was made that does touch base with
> operations and thus not supporting (or delaying, forever) this part of
> 4408BIS is highly possible.

You might change what you recommend people publish, but nothing in 4408bis 
should affect the code related to PTR.  

Scott K

From hsantos@isdg.net  Sat Aug 24 18:39:33 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 023C311E81C9 for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 18:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.446
X-Spam-Level: 
X-Spam-Status: No, score=-102.446 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 w1kY8Zx00cnA for <ietf@ietfa.amsl.com>; Sat, 24 Aug 2013 18:39:27 -0700 (PDT)
Received: from ntbbs.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCE111E81C7 for <ietf@ietf.org>; Sat, 24 Aug 2013 18:39:26 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1508; t=1377394757; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=ad8Gt4jiA6zoZ30vfPzjhPGe9hE=; b=Y/ajD38cn4zaEM/60Hbu RjznQ3gt29K45xLarv9mAbKHbpO7JEe5a/oe6nT2twUw3EQvKxwWSvqAm8s3N4Oz NsOQ2GPB6+9uVE2Ej+xMLO9v99AepwjD98NL8WaO0s5XL7EnUwMIz6HHStTLm42+ OOmt2mCqMtOeeZIt65yJhKg=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 21:39:17 -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 3857269100.4187.3692; Sat, 24 Aug 2013 21:39:15 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1508; t=1377394440; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=6Ku1tLP ZlZ7PZM3jcuU8vQ5Sq2ezutQtBrO8ZEJjwJQ=; b=hKHrJtsUvsoQ3sExhgT6nnp WfNBSiPriVyCieZ0OzcOPFBljnD16coQ/f1cl51pxPqDj4EO1LxEuO1nOfuzgxs1 tWO6v/LIfZ7R4nAAf8XjzsxgjuMInkl6lNc0pL3c06LekEa1o4PS8q4cOl5IPkZ+ ru+T0AauSwwx7CeoO3sc=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 24 Aug 2013 21:34:00 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3303687737.9.1580; Sat, 24 Aug 2013 21:33:58 -0400
Message-ID: <5219603A.50007@isdg.net>
Date: Sat, 24 Aug 2013 21:39:06 -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: SPF PTR Support [was SPF isn't going to change]
References: <20130823180411.50961.qmail@joyce.lan>	<9c35d474-9967-4d0d-a4a0-49cf650e4829@email.android.com>	<5218E8F1.8090505@isdg.net> <2972438.Fr2RSkezE0@scott-latitude-e6320>
In-Reply-To: <2972438.Fr2RSkezE0@scott-latitude-e6320>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 01:39:33 -0000

Scott Kitterman wrote:

>> PS: I am not trying to change anything about the PTR 4408BIS status.
>> Just pointing out that a change was made that does touch base with
>> operations and thus not supporting (or delaying, forever) this part of
>> 4408BIS is highly possible.
> 
> You might change what you recommend people publish, but nothing in 4408bis 
> should affect the code related to PTR.  
> 

True, I was among the group of WG participants who felt a full PTR 
deprecation would be incorrect. As it was originally drafted, new 
SPFBIS parsers did not need to code the rDNS logic.

draft-ietf-spfbis-4408bis-00:

    5.5.  "ptr"
    ...
    This mechanism is deprecated and SHOULD NOT be used.


After debates, updated to draft-ietf-spfbis-4408bis-15:

    5.5.  "ptr" (do not use)
    ...
    This mechanism SHOULD NOT be used.  See below for discussion.

After more debates, finally changed by rev 15 as it stands now with 
draft-ietf-spfbis-4408bis-19:

    5.5   "ptr" (do not use)
    ...
    This mechanism SHOULD NOT be published.  See below for discussion.

With other text in the spec codifying it MUST be part of the 
processor, I think its fine. But it could still can give new future 
readers/developers of SPF parsers the idea that it doesn't need to 
parsed.  Just consider relaxed policies are still accepted messages. 
Decreasing amount of records seen with a PTR with anything less than a 
-ALL policy could provide optimizing material to punk on the PTR 
processing.  Just saying.

--
HLS



From hallam@gmail.com  Sun Aug 25 02:07:28 2013
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 6D68611E823A; Sun, 25 Aug 2013 02:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.222
X-Spam-Level: 
X-Spam-Status: No, score=-2.222 tagged_above=-999 required=5 tests=[AWL=-0.223, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_22=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ak59UIajZ960; Sun, 25 Aug 2013 02:07:27 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6A911E8247; Sun, 25 Aug 2013 02:07:24 -0700 (PDT)
Received: by mail-la0-f42.google.com with SMTP id ep20so1610992lab.29 for <multiple recipients>; Sun, 25 Aug 2013 02:07:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GF7O9bDgJGxfSIhbNd69tTabyBQxFp365iaVLctyt/I=; b=xk/QCKc23gjXhsP1SGKmohafuMMt1F+nm9pawUpEUe9c+NqWUxcrC+CGkeC/SEa/2o 3QWE4ek7cOJYnkBfbJ8tpnOduSarwM1YbuPtiWKsVY9q2cqozjlXgeYIrgbN5Y2YCOTA VIeBnW3Oe/mUho6CxZtNKkyRYngODPjiTJg6Ao2U0ucAxWp+GpRFwrYxjKBMWWENHmJ8 8iOJDXnEwGfJ2f6q56GynFEdDYtcJP3vdvjXfOHqubT9/Tqkg4f2nggHCGICUVTfA0df 3QIM6Q++j9gdMDhqjvs59Z3OYMfuUHf2VD6HPC+3MGPSV5O4BvoMSqFqB6QPPieN272U KTWg==
MIME-Version: 1.0
X-Received: by 10.112.168.170 with SMTP id zx10mr7265185lbb.0.1377421643352; Sun, 25 Aug 2013 02:07:23 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Sun, 25 Aug 2013 02:07:23 -0700 (PDT)
In-Reply-To: <5218f0c0.030a0f0a.103a.fffff6f1SMTPIN_ADDED_BROKEN@mx.google.com>
References: <20130823180411.50961.qmail@joyce.lan> <5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu> <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com> <5218f0c0.030a0f0a.103a.fffff6f1SMTPIN_ADDED_BROKEN@mx.google.com>
Date: Sun, 25 Aug 2013 10:07:23 +0100
Message-ID: <CAMm+LwhApK==Ovq86bmVV=CsY_FnmfNAWfVDUOJ-cYAwSrJWjQ@mail.gmail.com>
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "bmanning@vacation.karoshi.com" <bmanning@vacation.karoshi.com>
Content-Type: multipart/alternative; boundary=001a11c23c88c210c404e4c1f71d
Cc: "dnsext@ietf.org" <dnsext@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, manning bill <bmanning@isi.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 09:07:28 -0000

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

On Sat, Aug 24, 2013 at 6:43 PM, <bmanning@vacation.karoshi.com> wrote:

> On Sat, Aug 24, 2013 at 08:39:36AM -0400, Phillip Hallam-Baker wrote:
> > On Fri, Aug 23, 2013 at 3:46 PM, manning bill <bmanning@isi.edu> wrote:
> >
> > >
> > >         the question is not that "nobody" checks type 99, the question
> is
> > > "is the rate of adoption
> > >         of type 99 -changing- in relation to type 16?
> > >
> >
> > As John pointed out, support for checking type 99 has decreased and
> > continues to decrease rather than increase. So waiting longer is not
> going
> > to solve the issue.
>
>         that is unclear...  we have second hand reports, but only actual
>         data from very recent DNS logs.   did those numbers increase or
>         decrease?  No evidence has been presented.


We have statements from people who are involved in the industry concerned
and no reason to believe that they are lying.

This is not a reasonable objection and it is really not at all surprising
that people are getting rude when people are refusing to accept what the WG
considers established facts.



> > Putting a statement in an RFC does not mean that the world will
> > automatically advance towards that particular end state.
>
>         ain't it the truth.  -BUT- its still worthwhile documenting the
>         best technical path and why it was abandoned.   The issues wrt
>         wildcards (thanks), DNSSEC considerations,  and code overhead to
>         demux type 16  vs.  the temporary problem of two lookups -IF- type
>         99 is not used, plus past guidance from the IAB and the IESG really
>         need to make it into a document in the RFC cannon.


I don't think it was ever about the right technical path. It was about the
DNSEXT group not caring to bother to get their DNSSEC infrastructure
adopted by the constituencies they needed buy in from then trying to make
that effort the problem of the SPF people.


> Forcing a WG to adopt a position to suit another constituency is not going
> > to lead them to advocate for that position in deployment constituencies.
> > Particularly when the original constituency does nothing to advance
> > deployment.
>
>         Dorthy Parker said: "You can lead a whore to culture, but you
> can't make her think".
>         Point the bias arrow either way youd like.  And as stated
> elsewhere, if Yahoo, Google,
>         Microsoft, AOL, et.al.  were simply waiting for the IETF to
> settle on a solution,
>         I'll raise O'Dells law;  "The installed base does not matter"
>

Its a stupid and wrong 'law'.

The deployed base is all that matters because before you get to the 'viral
marketing' network effects give you the 'chicken and egg problem'.

The reason HTTP and the Web took off was because we actually designed it to
take off fast. Meanwhile IPv6 and DNSSEC are still in the same state they
were 15 years ago, on the cusp of deployment in 5 years time. A large part
of the reason has been that the people pushing those initiatives have acted
as if deployment was inevitable.

I ran simulation studies of adoption to work out how to sell the Web.


The companies you cite have no stake in DNSSEC deployment. So why expect
them to favor a technical measure designed to facilitate DNSSEC deployment?

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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Aug 24, 2013 at 6:43 PM,  <span dir=3D"ltr">&lt;<a href=3D"=
mailto:bmanning@vacation.karoshi.com" target=3D"_blank">bmanning@vacation.k=
aroshi.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Sat, Aug 24, 2013 at 08=
:39:36AM -0400, Phillip Hallam-Baker wrote:<br>
&gt; On Fri, Aug 23, 2013 at 3:46 PM, manning bill &lt;<a href=3D"mailto:bm=
anning@isi.edu">bmanning@isi.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 =A0 =A0 the question is not that &quot;nobody&quot; check=
s type 99, the question is<br>
&gt; &gt; &quot;is the rate of adoption<br>
&gt; &gt; =A0 =A0 =A0 =A0 of type 99 -changing- in relation to type 16?<br>
&gt; &gt;<br>
&gt;<br>
&gt; As John pointed out, support for checking type 99 has decreased and<br=
>
&gt; continues to decrease rather than increase. So waiting longer is not g=
oing<br>
&gt; to solve the issue.<br>
<br>
</div>=A0 =A0 =A0 =A0 that is unclear... =A0we have second hand reports, bu=
t only actual<br>
=A0 =A0 =A0 =A0 data from very recent DNS logs. =A0 did those numbers incre=
ase or<br>
=A0 =A0 =A0 =A0 decrease? =A0No evidence has been presented.</blockquote><d=
iv><br></div><div>We have statements from people who are involved in the in=
dustry concerned and no reason to believe that they are lying.=A0</div><div=
><br></div>
<div>This is not a reasonable objection and it is really not at all surpris=
ing that people are getting rude when people are refusing to accept what th=
e WG considers established facts.</div><div><br></div><div>=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div class=3D"im">
&gt; Putting a statement in an RFC does not mean that the world will<br>
&gt; automatically advance towards that particular end state.<br>
<br>
</div>=A0 =A0 =A0 =A0 ain&#39;t it the truth. =A0-BUT- its still worthwhile=
 documenting the<br>
=A0 =A0 =A0 =A0 best technical path and why it was abandoned. =A0 The issue=
s wrt<br>
=A0 =A0 =A0 =A0 wildcards (thanks), DNSSEC considerations, =A0and code over=
head to<br>
=A0 =A0 =A0 =A0 demux type 16 =A0vs. =A0the temporary problem of two lookup=
s -IF- type<br>
=A0 =A0 =A0 =A0 99 is not used, plus past guidance from the IAB and the IES=
G really<br>
=A0 =A0 =A0 =A0 need to make it into a document in the RFC cannon.</blockqu=
ote><div><br></div><div>I don&#39;t think it was ever about the right techn=
ical path. It was about the DNSEXT group not caring to bother to get their =
DNSSEC infrastructure adopted by the constituencies they needed buy in from=
 then trying to make that effort the problem of the SPF people.</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"=
im">
&gt; Forcing a WG to adopt a position to suit another constituency is not g=
oing<br>
&gt; to lead them to advocate for that position in deployment constituencie=
s.<br>
&gt; Particularly when the original constituency does nothing to advance<br=
>
&gt; deployment.<br>
<br>
</div>=A0 =A0 =A0 =A0 Dorthy Parker said: &quot;You can lead a whore to cul=
ture, but you can&#39;t make her think&quot;.<br>
=A0 =A0 =A0 =A0 Point the bias arrow either way youd like. =A0And as stated=
 elsewhere, if Yahoo, Google,<br>
=A0 =A0 =A0 =A0 Microsoft, AOL, <a href=3D"http://et.al" target=3D"_blank">=
et.al</a>. =A0were simply waiting for the IETF to settle on a solution,<br>
=A0 =A0 =A0 =A0 I&#39;ll raise O&#39;Dells law; =A0&quot;The installed base=
 does not matter&quot;<br></blockquote><div><br></div><div>Its a stupid and=
 wrong &#39;law&#39;.</div><div><br></div><div>The deployed base is all tha=
t matters because before you get to the &#39;viral marketing&#39; network e=
ffects give you the &#39;chicken and egg problem&#39;.</div>
<div><br></div><div>The reason HTTP and the Web took off was because we act=
ually designed it to take off fast. Meanwhile IPv6 and DNSSEC are still in =
the same state they were 15 years ago, on the cusp of deployment in 5 years=
 time. A large part of the reason has been that the people pushing those in=
itiatives have acted as if deployment was inevitable.</div>
<div><br></div><div>I ran simulation studies of adoption to work out how to=
 sell the Web.=A0</div></div><br clear=3D"all"><div><br></div><div>The comp=
anies you cite have no stake in DNSSEC deployment. So why expect them to fa=
vor a technical measure designed to facilitate DNSSEC deployment?</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--001a11c23c88c210c404e4c1f71d--

From abdussalambaryun@gmail.com  Sun Aug 25 04:27:05 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01D4721F9BD5 for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 04:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74sfbmcGr8QI for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 04:27:03 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id A739621F9BD1 for <ietf@ietf.org>; Sun, 25 Aug 2013 04:27:03 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so2377060pad.0 for <ietf@ietf.org>; Sun, 25 Aug 2013 04:27:03 -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=uJ9KtIAfxggYtG+0R8FFNUBddenuL6Sjz96IPg4vQQI=; b=Ve8/Ja0ZRqaiPgKbRPTXvOhNh+WqU5/LxNXBo6K1DqlCdmDtf4g5XC+jNB4ob3KdJk yUR/u2ccnXwvmRzsW/Pf58hFEFyOxEO7Y4gymy+pZS9nWEzKgrdjAzWIOdxWwxPq/dyr Kn+Bo2W70BOLzBhnhVDSa7eOidYvCyXyFFH0CsoZymylvt0mVaib6WtVCKSrXjOQ1bXH EZS6lXgih2tmGl2TDozq/C8iegGcznNmb1LjPsyMye5RXM7N2U97lFs61GmZr/SipACW o0FLaUSNEB0eRXqnUKvncduunZh3OZeX+cRaLVLHevuIPU/Ip/Fb1Lmo9MSJsq6llCRG i+Kw==
MIME-Version: 1.0
X-Received: by 10.66.175.133 with SMTP id ca5mr9015059pac.40.1377430023261; Sun, 25 Aug 2013 04:27:03 -0700 (PDT)
Received: by 10.68.195.168 with HTTP; Sun, 25 Aug 2013 04:27:03 -0700 (PDT)
In-Reply-To: <52151903.4030402@qti.qualcomm.com>
References: <20130819150521.GB21088@besserwisser.org> <20130819160549.61542.qmail@joyce.lan> <20130819190533.GA30516@besserwisser.org> <4751241.GTNxysAlzm@scott-latitude-e6320> <B443E973-858A-4958-964B-B0F0FBDF5A7A@virtualized.org> <CAMm+LwhcHOeUv0iqZmZ6wX-jOD1r-mRR0x8sbxaKrsU3k4CNBQ@mail.gmail.com> <20130821040003.GL607@mx1.yitter.info> <64700EE4-85B3-4179-904A-885770C6BBF4@virtualized.org> <7F8D4DA5-F80B-432B-8231-5B40ADB61783@frobbit.se> <521495EB.7060207@cisco.com> <1C40FB10-3705-4E80-8DEB-D14B63D24C97@frobbit.se> <5214A593.8030907@cisco.com> <E3B3B6B0-F17F-44D0-ACD1-53BDBAC6F2CB@frobbit.se> <5214F97B.2080400@dcrocker.net> <6D6829DE-1242-4877-BB5E-8ECD08D88CB2@frobbit.se> <52150722.1070307@dcrocker.net> <52150DF0.6070800@qti.qualcomm.com> <5215123E.5080203@dcrocker.net> <52151903.4030402@qti.qualcomm.com>
Date: Sun, 25 Aug 2013 21:27:03 +1000
Message-ID: <CADnDZ88qqzsJx573n6nyXcKt3Es=fSrgO6MwMvxdoL1MXJpiMw@mail.gmail.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,  Version 1) to Proposed Standard)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=047d7bdca3fe3d52b004e4c3ebc5
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 11:27:05 -0000

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

I experienced rude respondings in IETF list and in  one WG list, I don't
beleive that it is culture of IETF participants, but it seems that some
people should understand to be polite and reasonable in such organisation
business. Finally, the rude responding is not controled by the chair of
thoes lists, therefore, thoes lists can be rude lists from time to time.

AB

On Thu, Aug 22, 2013 at 5:46 AM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 8/21/13 2:17 PM, Dave Crocker wrote:
>
>> On 8/21/2013 11:58 AM, Pete Resnick wrote:
>>
>>> AD hat squarely on my head.
>>>
>>> On 8/21/13 1:29 PM, Dave Crocker wrote:
>>>
>>> Oh.  Now I understand.
>>>>
>>>> You are trying to impose new requirements on the original work, many
>>>> years after the IETF approved it.
>>>>
>>>> Thanks.  Very helpful.
>>>>
>>>
>>> That's not an appropriate response. It is certainly not helpful to me as
>>> the consensus caller. And it is rude.
>>>
>>
>> Since you've made this a formal process point, I'll ask you to
>> substantiate it carefully and also formally.  The implication of your
>> assessment is that IETF participants must not comment on the utility of
>> comments by others.
>>
>
> That's not what I said, and in fact if you look at the line immediately
> following what you quoted, you will see that I said:
>
>  It's perfectly reasonable to say, "This would constitute a new
>>> requirement and I don't think there is a good justification to pursue that
>>> line."
>>>
>>
> It is not your complaint about the imposition of new requirements that is
> problematic, or your point that it is not useful to continue that line of
> discussion. Talk about the utility of a comment all that you want. It is
> the sarcasm and the rudeness that I am saying is unreasonable. Especially
> coming from a senior member of the community, the only purpose it seems to
> serve is to bully others into not participating in the conversation. If you
> think that the conversation has gone on too long, you're perfectly within
> rights to ask the manager of the thread (in this case, myself or the
> chairs), in public if you like, to make a call and say that the issue is
> closed. But again, the tactics displayed above are not professional and not
> reasonable rhetorical mode.
>
> I don't recall that being a proscribed behavior, since it has nothing to
>> do with personalities.  So, please explain this in a way that does not
>> sound like Procrustean political correctness.
>>
>
> I am not sure what the first sentence means. And I'm sorry that you
> believe that my stance on this is Procrustean. But the fact is that rude
> comments of this sort do not contribute to consensus-building in the least.
>
> For the record, I entirely acknowledge that my note has an edge to it and
>> yes, of course alternate wording was possible.  However the thread is
>> attempting to reverse extensive and careful working group effort and to
>> ignore widely deployed and essential operational realities, including
>> published research data.
>>
>
> I appreciate your input that you believe that some or all of the objectors
> are ignoring operational realities. Perhaps they are. But the fact is that
> Last Call is a time for the community to take a last look at WG output. If
> senior members of the community (among which there are several in this
> thread) are suspicious of the output, it *is* important to make sure that
> their concerns are addressed. Maybe they simply don't have all of the
> information. But maybe the WG has missed something essential in all that
> careful work. Both have historically happened many times.
>
> A bit of edge is warranted for such wasteful, distracting and
>> destabilizing consumption of IETF resources.  In fact an important problem
>> with the alternate wording, such as you offered, is that it implies a
>> possible utility in the thread that does not exist.
>>
>
> It is far more distracting and destabilizing for the IETF to come out of a
> Last Call with experienced members of the community suspicious that a bad
> result has occurred, especially if the tactic used to end the discussion
> was sarcasm to chase people away from the discussion. You are looking at
> only the little picture. The consensus might end up on the rough side, but
>  having the conversation has utility in and of itself.
>
> I find your "edge" much more disruptive to the conversation, making it
> much more adversarial than explanatory, and damaging the consensus that
> might be built. I think that lowers the utility of the output tremendously.
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.**com/~presnick/<http://www.qualcomm.com/~presnick/>
> >
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><div>I experienced rude respondings in IETF list and in=A0=
 one WG list, I don&#39;t beleive that it is culture of IETF participants, =
but it seems that some people should understand to be polite and reasonable=
 in such organisation business. Finally, the rude responding is not control=
ed by the chair of thoes lists, therefore, thoes lists can be rude lists fr=
om time to time. </div>

<div>=A0</div>
<div>AB<br><br></div>
<div class=3D"gmail_quote">On Thu, Aug 22, 2013 at 5:46 AM, Pete Resnick <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"=
_blank">presnick@qti.qualcomm.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">On 8/21/13 2:17 PM, Dave Crocker wrot=
e:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">On 8/21/2013 11:58 AM, Pete Resnick w=
rote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">AD hat squarely on my head.<br><br>On=
 8/21/13 1:29 PM, Dave Crocker wrote:<br><br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">Oh. =A0Now I understand.<br><br>You a=
re trying to impose new requirements on the original work, many<br>years af=
ter the IETF approved it.<br>
<br>Thanks. =A0Very helpful.<br></blockquote><br>That&#39;s not an appropri=
ate response. It is certainly not helpful to me as<br>the consensus caller.=
 And it is rude.<br></blockquote><br>Since you&#39;ve made this a formal pr=
ocess point, I&#39;ll ask you to substantiate it carefully and also formall=
y. =A0The implication of your assessment is that IETF participants must not=
 comment on the utility of comments by others.<br>
</blockquote><br>That&#39;s not what I said, and in fact if you look at the=
 line immediately following what you quoted, you will see that I said:<br><=
br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">It&#39;s perfectly reasonable to say,=
 &quot;This would constitute a new requirement and I don&#39;t think there =
is a good justification to pursue that line.&quot;<br>
</blockquote></blockquote><br>It is not your complaint about the imposition=
 of new requirements that is problematic, or your point that it is not usef=
ul to continue that line of discussion. Talk about the utility of a comment=
 all that you want. It is the sarcasm and the rudeness that I am saying is =
unreasonable. Especially coming from a senior member of the community, the =
only purpose it seems to serve is to bully others into not participating in=
 the conversation. If you think that the conversation has gone on too long,=
 you&#39;re perfectly within rights to ask the manager of the thread (in th=
is case, myself or the chairs), in public if you like, to make a call and s=
ay that the issue is closed. But again, the tactics displayed above are not=
 professional and not reasonable rhetorical mode.<br>
<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">I don&#39;t recall that being a prosc=
ribed behavior, since it has nothing to do with personalities. =A0So, pleas=
e explain this in a way that does not sound like Procrustean political corr=
ectness.<br>
</blockquote><br>I am not sure what the first sentence means. And I&#39;m s=
orry that you believe that my stance on this is Procrustean. But the fact i=
s that rude comments of this sort do not contribute to consensus-building i=
n the least.<br>
<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">For the record, I entirely acknowledg=
e that my note has an edge to it and yes, of course alternate wording was p=
ossible. =A0However the thread is attempting to reverse extensive and caref=
ul working group effort and to ignore widely deployed and essential operati=
onal realities, including published research data.<br>
</blockquote><br>I appreciate your input that you believe that some or all =
of the objectors are ignoring operational realities. Perhaps they are. But =
the fact is that Last Call is a time for the community to take a last look =
at WG output. If senior members of the community (among which there are sev=
eral in this thread) are suspicious of the output, it *is* important to mak=
e sure that their concerns are addressed. Maybe they simply don&#39;t have =
all of the information. But maybe the WG has missed something essential in =
all that careful work. Both have historically happened many times.<br>
<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">A bit of edge is warranted for such w=
asteful, distracting and destabilizing consumption of IETF resources. =A0In=
 fact an important problem with the alternate wording, such as you offered,=
 is that it implies a possible utility in the thread that does not exist.<b=
r>
</blockquote><br>It is far more distracting and destabilizing for the IETF =
to come out of a Last Call with experienced members of the community suspic=
ious that a bad result has occurred, especially if the tactic used to end t=
he discussion was sarcasm to chase people away from the discussion. You are=
 looking at only the little picture. The consensus might end up on the roug=
h side, but =A0having the conversation has utility in and of itself.<br>
<br>I find your &quot;edge&quot; much more disruptive to the conversation, =
making it much more adversarial than explanatory, and damaging the consensu=
s that might be built. I think that lowers the utility of the output tremen=
dously.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>pr<br><br>-- <br>Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~pr=
esnick/" target=3D"_blank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt=
;<br>Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478"=
 target=3D"_blank" value=3D"+18586514478">+1 (858)651-4478</a><br>
<br></font></span></blockquote></div><br></div>

--047d7bdca3fe3d52b004e4c3ebc5--

From abdussalambaryun@gmail.com  Sun Aug 25 04:33:16 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51AC321F944C for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 04:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 jpGukhQ+DABZ for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 04:33:16 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id E70B621F8D20 for <ietf@ietf.org>; Sun, 25 Aug 2013 04:33:15 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id uo5so2368537pbc.37 for <ietf@ietf.org>; Sun, 25 Aug 2013 04:33:15 -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=sht5K8l3lo9LiI2m9EMqXBww/BCzSvRnR7TYCj9d7/w=; b=zWp4Hx232SIej6CqtsuGVi3IEq7f64JdAOFG2kcyBXQXXG3CfbKMsJeMTN/gSvtxE4 6gallLDMehFpcWNu31mdjNXf5zqODp2gSliRDo+LE5dSuhl6r6MXm8hGgz/LQKKVUKBn gtOWvm0b0zipI9SMqjoNZocdS/dlZz9CterWSoOXoRY1AegTvcUL2qdZRyCDhLLV1pPA MkWAD6RoYkHtjn19wQpIkrblo8XKBTQunGCkDMMEDRihlkNN4pg0XMmBYdxg9IenkKAX 7tjyXknRl6nyUXPoZUFRcEnNlTefBOKomT32HiePfRr+tw0GquEZxs4t4VCHNCCrBIQS nLoQ==
MIME-Version: 1.0
X-Received: by 10.67.3.103 with SMTP id bv7mr8878501pad.15.1377430394504; Sun, 25 Aug 2013 04:33:14 -0700 (PDT)
Received: by 10.68.195.168 with HTTP; Sun, 25 Aug 2013 04:33:14 -0700 (PDT)
In-Reply-To: <f6159afb59766a8b79dcc7d80eb2378f@cam.ac.uk>
References: <f6159afb59766a8b79dcc7d80eb2378f@cam.ac.uk>
Date: Sun, 25 Aug 2013 21:33:14 +1000
Message-ID: <CADnDZ8-DWZSW0MzAUSydOQEUtHL1-o=DdxSO1DsNqGX2oQ5cBA@mail.gmail.com>
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.txt>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
Content-Type: multipart/alternative; boundary=e89a8f503ade5e0dea04e4c4014c
Cc: narten@us.ibm.com, barryleiba@computer.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 11:33:16 -0000

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

Hi Aaron,

I will add that it depends on that is there some one stopping rude actions
in IETF, or is it just free to post any respond. I know that the procedure
of IETF does mention such actions, but I don't see practicings so far,

AB
On Fri, Aug 23, 2013 at 2:20 AM, Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>wrote:
>
>
>
> The line between being Rude and being Upfront is tricky and highly context
> dependent.
>
> Aaron
>
>
>
>> Thomas
>>
>>

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

<div dir=3D"ltr"><div>Hi Aaron,</div>
<div><br>I will add that it depends on that is there some one stopping rude=
 actions in IETF, or is it just free to post any respond. I know that the p=
rocedure of IETF does mention such actions, but I don&#39;t see practicings=
 so far,</div>

<div>=A0</div>
<div>AB<br></div>
<div class=3D"gmail_quote">On Fri, Aug 23, 2013 at 2:20 AM, Aaron Yi DING <=
span dir=3D"ltr">&lt;<a href=3D"mailto:Aaron.Ding@cl.cam.ac.uk" target=3D"_=
blank">Aaron.Ding@cl.cam.ac.uk</a>&gt;</span> wrote:=20
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br><br>The line between being Rude a=
nd being Upfront is tricky and highly context dependent.<br><br>Aaron<br><b=
r>
<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br>Thomas<br><br></blockquote></bloc=
kquote></div><br></div>

--e89a8f503ade5e0dea04e4c4014c--

From abdussalambaryun@gmail.com  Sun Aug 25 05:39:53 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6464021F9CBF for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 05:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=0.278,  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 B5WwPn30yPRx for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 05:39:52 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3B67121F9CC3 for <ietf@ietf.org>; Sun, 25 Aug 2013 05:39:48 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id wz12so2395363pbc.11 for <ietf@ietf.org>; Sun, 25 Aug 2013 05:39:48 -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=YGfKVrwxn7JzCmZNCQrWFHFqP4zlGeqlkJC4pVGBuTc=; b=gvgEI3Jb7mlWOwYC+5oJtm5ifOvlPzAnHpFIpTWeK9/heD1KW41+uOttJWnURGvvSP RN2BEQ1wj0fLho9eLc0P+m4ez2rUPmgZGzUWKWYLiCFb6Ogpite1wHgcbivw2fpywISb OB5MGBExBwQGTaHnFLIv4GrNsgcKN+BHrrD+y2ebtOpEGCez3ehK0Oi0kvQ7wUrd1kbc glg7B1uwGIGvlL+4F4cDS+wOYPV3kCkGAQgMIIe++opqCFkUTsEeX/liw6TlLo8CkUB2 vv8YvLJXIaEPym2YN/V1L/BuYXtBpoxHdENz4u/7JlrsVpz1SkBj9c4TL0wh8Szv9rJ0 K61g==
MIME-Version: 1.0
X-Received: by 10.68.175.33 with SMTP id bx1mr9998910pbc.21.1377434388636; Sun, 25 Aug 2013 05:39:48 -0700 (PDT)
Received: by 10.68.195.168 with HTTP; Sun, 25 Aug 2013 05:39:48 -0700 (PDT)
In-Reply-To: <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com>
Date: Sun, 25 Aug 2013 22:39:48 +1000
Message-ID: <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com>
Subject: Re: Charging remote participants
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Content-Type: multipart/alternative; boundary=047d7bd6b2ae7008d804e4c4efbf
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 12:39:53 -0000

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

Hi Hadriel,

I agree that charging IETF participants with any money is not a good idea,
but charging participants with some effort/work/contribution to do is
needed. For example, participants SHOULD do some work in IETF, either
review, authoring, attending-meetings, commenting on lists, etc. Otherwise
the IETF will not develop. If someone just subscribe to the list with no
contribution, that I will not call a participant. The reward/motivation
from IETF to participants is to acknowledge in writting their efforts,
which I think still the IETF management still does not motivate/encourage.

IETF Remote Participants (IETFRP) SHOULD charge the IETF not the other way,
because still the IETF ignores some IETFRP efforts (or even hides
information that should be provided to the diverse community).

AB

On Fri, Aug 16, 2013 at 11:10 PM, Hadriel Kaplan
<hadriel.kaplan@oracle.com>wrote:

>
> Since the topic keeps getting raised... I think that charging remote
> participants any fee is a really terrible idea.  One of the really great
> things about the IETF is its open and free (as in beer) participation
> policy.  The real work is supposed to be done on mailing lists, and there's
> no charge or restriction on who can send emails.  That policy is actually
> quite rare for standards bodies, and makes our output better not worse.
>
> Obviously we discuss things and do real work at physical meetings too, and
> they're not simply social occasions.  At the end of the day we actually
> want people to come to the physical meetings, but the realities of life
> make that impossible for many.  But charging remote participants for better
> tools/experience isn't the answer.  At least for me, whenever I'm
> discussing a draft mechanism I actually *want* input from remote
> participants.  I don't want it to be only from folks who can afford to
> provide input.  I want it from people who can't get approval for even a
> $100 expense, from people who are between jobs, people from academia, and
> even from just plain ordinary users rather than just vendors or big corps.
>  At one time we worried that free remote participation would lead to too
> many random participants to get work done, but that hasn't become a problem
> afaict.  Please don't whittle it down further to only those who can afford
> it.
>
> I would do anything whatsoever to avoid charging remote participants, even
> if it means raising the fee for f2f attendees to subsidize
> remote-participant tooling costs.
>
> In that vein, I think a lot of the f2f attendees get our reg-fee paid by
> our employer and another $50 or even $100 isn't going to make a bit of
> difference for us - for those whom it would make a difference, I'd create
> another category of f2f registration fee like 'Self-paying Attendee' or
> some such.  Selecting the new category would drop your fee by the $50 or
> $100, but wouldn't change what gets displayed on your badge or anything.
>  It would be purely optional, with no guilt attached for not paying it and
> no visible difference to anyone else.  Just put some words on the
> registration form page saying something like "If you cannot expense your
> registration fee, please select the 'Self-paying Attendee' category" or
> something like that.  Or make it some checkbox thingy.  I believe the
> majority of folks who can expense it will not have difficulty expensing a
> 'Regular Attendee' charge so long as it doesn't say we opted to pay more.
>
> -hadriel
>
> p.s. Even from a purely practical standpoint, charging remote participants
> raises a lot of issues - we debate incessantly just about the f2f day-pass,
> and that's nothing compared to this.  For example: if things break during
> the meeting session, do we re-imburse them?  Do we pro-rate the
> re-imbursement based on how many of their meetings had technical issues
> with audio or video?  Do we charge a flat fee for the whole week of
> meetings, or just charge per meeting session, or depending on how long the
> session is?  Do we charge students a different rate, like we do f2f
> reg-fees?  Do we need to provide tech support with a specific SLA?  This
> while thing is a can of worms.  It's not worth it.
>
>

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

<div dir=3D"ltr"><div>Hi Hadriel,</div>
<div>=A0</div>
<div>I agree that charging IETF participants with any money is not a good i=
dea, but charging participants with some effort/work/contribution to do is =
needed. For example, participants SHOULD do some work in IETF, either revie=
w, authoring, attending-meetings, commenting on lists, etc. Otherwise the I=
ETF will not develop. If someone just subscribe to the list with no contrib=
ution, that I will not call a participant. The reward/motivation from IETF =
to participants is to acknowledge in writting their efforts, which I think =
still the IETF management still does not motivate/encourage. </div>

<div>=A0</div>
<div>IETF Remote Participants (IETFRP) SHOULD charge the=A0IETF not the oth=
er way, because still the IETF ignores some IETFRP efforts (or even hides i=
nformation that should be provided to the diverse community).</div>
<div>=A0</div>
<div>AB<br><br></div>
<div class=3D"gmail_quote">On Fri, Aug 16, 2013 at 11:10 PM, Hadriel Kaplan=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:hadriel.kaplan@oracle.com" target=
=3D"_blank">hadriel.kaplan@oracle.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br>Since the topic keeps getting rai=
sed... I think that charging remote participants any fee is a really terrib=
le idea. =A0One of the really great things about the IETF is its open and f=
ree (as in beer) participation policy. =A0The real work is supposed to be d=
one on mailing lists, and there&#39;s no charge or restriction on who can s=
end emails. =A0That policy is actually quite rare for standards bodies, and=
 makes our output better not worse.<br>
<br>Obviously we discuss things and do real work at physical meetings too, =
and they&#39;re not simply social occasions. =A0At the end of the day we ac=
tually want people to come to the physical meetings, but the realities of l=
ife make that impossible for many. =A0But charging remote participants for =
better tools/experience isn&#39;t the answer. =A0At least for me, whenever =
I&#39;m discussing a draft mechanism I actually *want* input from remote pa=
rticipants. =A0I don&#39;t want it to be only from folks who can afford to =
provide input. =A0I want it from people who can&#39;t get approval for even=
 a $100 expense, from people who are between jobs, people from academia, an=
d even from just plain ordinary users rather than just vendors or big corps=
. =A0At one time we worried that free remote participation would lead to to=
o many random participants to get work done, but that hasn&#39;t become a p=
roblem afaict. =A0Please don&#39;t whittle it down further to only those wh=
o can afford it.<br>
<br>I would do anything whatsoever to avoid charging remote participants, e=
ven if it means raising the fee for f2f attendees to subsidize remote-parti=
cipant tooling costs.<br><br>In that vein, I think a lot of the f2f attende=
es get our reg-fee paid by our employer and another $50 or even $100 isn&#3=
9;t going to make a bit of difference for us - for those whom it would make=
 a difference, I&#39;d create another category of f2f registration fee like=
 &#39;Self-paying Attendee&#39; or some such. =A0Selecting the new category=
 would drop your fee by the $50 or $100, but wouldn&#39;t change what gets =
displayed on your badge or anything. =A0It would be purely optional, with n=
o guilt attached for not paying it and no visible difference to anyone else=
. =A0Just put some words on the registration form page saying something lik=
e &quot;If you cannot expense your registration fee, please select the &#39=
;Self-paying Attendee&#39; category&quot; or something like that. =A0Or mak=
e it some checkbox thingy. =A0I believe the majority of folks who can expen=
se it will not have difficulty expensing a &#39;Regular Attendee&#39; charg=
e so long as it doesn&#39;t say we opted to pay more.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>-hadriel<br></font></spa=
n><br>p.s. Even from a purely practical standpoint, charging remote partici=
pants raises a lot of issues - we debate incessantly just about the f2f day=
-pass, and that&#39;s nothing compared to this. =A0For example: if things b=
reak during the meeting session, do we re-imburse them? =A0Do we pro-rate t=
he re-imbursement based on how many of their meetings had technical issues =
with audio or video? =A0Do we charge a flat fee for the whole week of meeti=
ngs, or just charge per meeting session, or depending on how long the sessi=
on is? =A0Do we charge students a different rate, like we do f2f reg-fees? =
=A0Do we need to provide tech support with a specific SLA? =A0This while th=
ing is a can of worms. =A0It&#39;s not worth it.<br>
<br></blockquote></div><br></div>

--047d7bd6b2ae7008d804e4c4efbf--

From hadriel.kaplan@oracle.com  Sun Aug 25 07:42:43 2013
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E30621F9A10 for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 07:42:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.512
X-Spam-Level: 
X-Spam-Status: No, score=-6.512 tagged_above=-999 required=5 tests=[AWL=0.087,  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 p99v3sjJZaLm for <ietf@ietfa.amsl.com>; Sun, 25 Aug 2013 07:42:37 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id EFC4221F9991 for <ietf@ietf.org>; Sun, 25 Aug 2013 07:42:36 -0700 (PDT)
Received: from ucsinet22.oracle.com (ucsinet22.oracle.com [156.151.31.94]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7PEgZNP019756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 25 Aug 2013 14:42:35 GMT
Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7PEgYdg022744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 25 Aug 2013 14:42:35 GMT
Received: from abhmt109.oracle.com (abhmt109.oracle.com [141.146.116.61]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7PEgYmt008967; Sun, 25 Aug 2013 14:42:34 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 25 Aug 2013 07:42:33 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Charging remote participants
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com>
Date: Sun, 25 Aug 2013 10:42:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD41D627-1B7E-410D-850D-E6FCCE698CF1@oracle.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet22.oracle.com [156.151.31.94]
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Aug 2013 14:42:43 -0000

On Aug 25, 2013, at 8:39 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> I agree that charging IETF participants with any money is not a good =
idea, but charging participants with some effort/work/contribution to do =
is needed. For example, participants SHOULD do some work in IETF, either =
review, authoring, attending-meetings, commenting on lists, etc. =
Otherwise the IETF will not develop. If someone just subscribe to the =
list with no contribution, that I will not call a participant.

When I and others have been using the word "participants", we've been =
talking about the ones who do actively contribute - by reviewing the =
drafts and providing their input in email or at the mic or in jabber, or =
by submitting their own drafts, or providing text, etc. =20

Of course there are plenty of folks who merely monitor, and that's fine =
too, but yeah it's not useful for improving our drafts.  But those =
aren't the "remote participants" I was talking about.


> The reward/motivation from IETF to participants is to acknowledge in =
writting their efforts, which I think still the IETF management still =
does not motivate/encourage.

For the WG's I've been involved in, the WG drafts often do acknowledge =
major contributors in the "Acknowledgements" section.  But yeah it's not =
always done, or people are sometimes left out.  Having authored a few =
myself, I find it's actually quite hard to keep track of contributors.  =
And I always feel bad if I forget someone. :(

If we really feel that's a problem there are some simple solutions to it =
- the same problem occurs for open source software and they have simple =
solutions for it.  But I'm not sure it really is a problem worth fixing. =
 My belief is the motivation to participate should be: for the benefit =
of everyone; and for the benefit of the contributor in using or =
implementing it, by making the mechanism/protocol work better for them =
and their needs.

Putting names in the RFC doesn't feel to me like a thing we should use =
for the purpose of motivation, but rather just to acknowledge those who =
went above-and-beyond and were major contributors.  No?


> IETF Remote Participants (IETFRP) SHOULD charge the IETF not the other =
way, because still the IETF ignores some IETFRP efforts (or even hides =
information that should be provided to the diverse community).

I have never seen the IETF "hide information that should be provided to =
the diverse community".  That's a pretty serious charge, and you'll have =
to provide some examples to back it up, because I don't believe it.

The only way to do that would be to prevent postings on our mailing =
lists.  I know we have blocked/removed some mailing list subscribers in =
the past, but those were very rare occasions and debated quite a bit =
before-hand in an open manner (see RFC 3683).  For some obvious cases we =
don't need to discuss it before-hand (see RFC 3005).  The IETF is not =
lacking for paranoia regarding such things... so I don't think we're in =
danger of doing what you fear.

-hadriel


From l.wood@surrey.ac.uk  Mon Aug 26 00:36:11 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51EAA21F9E67 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 00:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TgrgoXW7xrj3 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 00:36:05 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.137]) by ietfa.amsl.com (Postfix) with ESMTP id 89A2B21F9FC8 for <ietf@ietf.org>; Mon, 26 Aug 2013 00:36:03 -0700 (PDT)
Received: from [195.245.231.67:6420] by server-1.bemta-5.messagelabs.com id 8C/7D-26518-2650B125; Mon, 26 Aug 2013 07:36:02 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-82.messagelabs.com!1377502561!28014009!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1768 invoked from network); 26 Aug 2013 07:36:02 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-5.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 26 Aug 2013 07:36:02 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Mon, 26 Aug 2013 08:36:01 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>
Date: Mon, 26 Aug 2013 08:36:01 +0100
Subject: RE: Rude responses
Thread-Topic: Rude responses
Thread-Index: AQHOoi7pIoXSC6pShEuIi5qj4dwrWQ==
Message-ID: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 07:36:12 -0000

> I experienced rude respondings in IETF list

That would be when you tried to get April 1 RFCs discontinued.

> in  one WG list

That would be MANET, when you lobbied for an acknowledgement on a draft you=
 didn't write or contribute significantly to.

Have you considered that being polite and reasonable on organisation busine=
ss means both not making unreasonable requests, and first making an effort =
to understand the organisation whose business you are attempting to conduct=
? Your requests come from a clear lack of understanding of the IETF or how =
it works.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Abdussalam=
 Baryun [abdussalambaryun@gmail.com]
Sent: 25 August 2013 12:27
To: Pete Resnick
Cc: dcrocker@bbiw.net; ietf@ietf.org
Subject: Re: Rude responses (Was: Last Call: <draft-ietf-spfbis-4408bis-19.=
txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email=
,         Version 1) to Proposed Standard)

I experienced rude respondings in IETF list and in  one WG list, I don't be=
leive that it is culture of IETF participants, but it seems that some peopl=
e should understand to be polite and reasonable in such organisation busine=
ss. Finally, the rude responding is not controled by the chair of thoes lis=
ts, therefore, thoes lists can be rude lists from time to time.

AB




From Jelte.Jansen@sidn.nl  Mon Aug 26 01:50:53 2013
Return-Path: <Jelte.Jansen@sidn.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 55D3221E804C for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 01:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.69
X-Spam-Level: 
X-Spam-Status: No, score=-0.69 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bxaZAKEngeQv for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 01:50:44 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 83C9F21F9AD2 for <ietf@ietf.org>; Mon, 26 Aug 2013 01:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=y5ClKAFs94fMa38wNTgkqjjLiNXo8nlphranbhSF6wc=; b=sWXdcrSox3e/E145E6KJbLjqPtcGZgg2EeGtlcXH5piwvcdbFeStfY7sFDzK1YCes7OZvclwjuVdF/dkcU/9sxijBGtoOpc49mPaosghemJLxj2E+LpkGNzS3oR7+gRhpt1Xtlq1xXmqpbs3G3zQ7e0hYu017QjNcNBlTEECuso=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r7Q8mUls022224-r7Q8mUlu022224 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Mon, 26 Aug 2013 10:48:30 +0200
Received: from [94.198.152.214] (94.198.152.214) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 26 Aug 2013 10:48:30 +0200
Message-ID: <521B165C.9000809@sidn.nl>
Date: Mon, 26 Aug 2013 10:48:28 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130823143402.49936.qmail@joyce.lan>
In-Reply-To: <20130823143402.49936.qmail@joyce.lan>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 08:50:55 -0000

On 08/23/2013 04:34 PM, John Levine wrote:
>>
>> I don't know of any (at least ones that are used in the global dns
>> namespace), and I would like to still not know of any in 2033.
>>
> 
> Since we agree that the issue you're worried about has not arisen even
> once in the past decade, could you clarify what problem needs to be
> solved here?
> 

prevented, not solved. I would like to prevent someone from having to
submit a draft specifying that in the case of TXT, the (name, class,
type)-tuple should be extended with the first X octets from the RDATA
fields, somewhere in the future, because client-side demuxing is getting
too buggy and it seems like a good idea to select specific records in
the DNS itself.

Jelte

From mcr@sandelman.ca  Mon Aug 26 06:46:58 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72FEA11E819C; Mon, 26 Aug 2013 06:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.543
X-Spam-Level: 
X-Spam-Status: No, score=-1.543 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, 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 I4IRna9a51I0; Mon, 26 Aug 2013 06:46:50 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4AB11E819D; Mon, 26 Aug 2013 06:46:46 -0700 (PDT)
Received: from sandelman.ca (unknown [209.87.252.140]) by relay.sandelman.ca (Postfix) with ESMTPS id 628EE22079; Mon, 26 Aug 2013 09:46:45 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 82CE8CA0D5; Sun, 25 Aug 2013 21:04:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org" <ietf@ietf.org>
Subject: GST/PST and IETF 88 
In-reply-to: <900A1E2059ADB149B905E3C8FA0046A62C7967DC95@FHDP1LUMXC7V23.us.one.verizon.com>
References: <20130823142554.29105.99013.idtracker@ietfa.amsl.com> <900A1E2059ADB149B905E3C8FA0046A62C7967DC95@FHDP1LUMXC7V23.us.one.verizon.com>
Comments: In-reply-to "Mishra, Sanjay" <sanjay.mishra@verizon.com> message dated "Fri, 23 Aug 2013 10:49:22 -0400."
X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.2.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 25 Aug 2013 21:04:25 -0400
Message-ID: <5691.1377479065@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 13:46:59 -0000

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


Mishra, Sanjay <sanjay.mishra@verizon.com> wrote:
    > 1. Registration A. Early-Bird Registration - USD 650.00 Pay by Friday,

Since the last Vancouver IETF, the province of BC has "rescinded" it's
harmonization of provincial and federal sales taxes. (I think the decision =
is
totally moronic, but, I don't live there).  This change does not change the
crux of my question, just the amount, and it affects the details.

My question is:
   Is ISOC doing GST (the federal VAT) processing?
   Is ISOC doing PST (the provincial tax, not value-added, last I checked..=
.)?
   My understanding is that attendees to Berlin received a revised statement
   indicating the amount of German VAT that was included in the USD650.

   While I wasn't there, and I'm not EC, I am in Canada, and my company does
   process GST, which means that I should be able to claim the GST part bac=
k.

I don't know what the new BC PST is, but it was around 8% before.
Will the base price be 650 / 1.15, or 650/1.05 ?

=2D-=20
Michael Richardson
=2Dat the cottage-


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

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

iQEcBAEBAgAGBQJSGqmUAAoJEKD0KQ7Gj3P28DIH/R2FT4n+AKygL0/+komKIzHf
gTJ4S0zyNon5ys4OVczziTu9rW3pBlswNYH/8AGVpANtLmTnBFKWNWzyKjsc2c6t
ew7xp4NXBnet17IwOa/zXGfnXyzar/WCirmKEF/UCESLyCI7PXoBOxVdOSTWqWAn
6eyZcNEEueFcVzyVvYwifxkTbxvw0RzaRvAcEXIq+hXn5PGs0qeAkfqbMSaTfdPj
mDoHVwIukPTIVtRk0CqAtDW1ZdCKvw7Hhr9vVRRE+//0AOclWCbu9LOU5jXgUA91
QIasvL2BZgZTPr807hdNOxmer/6PYapGZGUcyXJ3RuMlPr5dBzE+KR8wUUQAOI8=
=E37r
-----END PGP SIGNATURE-----
--=-=-=--

From johnl@taugh.com  Mon Aug 26 07:08:40 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BF7E11E819E for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level: 
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.006,  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 chCsX5PNufwo for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:08:39 -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 6D1E911E8197 for <ietf@ietf.org>; Mon, 26 Aug 2013 07:08:39 -0700 (PDT)
Received: (qmail 41841 invoked from network); 26 Aug 2013 14:08:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=a370.521b6165.k1308; bh=gDzCPAPQHXC/302YyvZQOnv30NBHVIzWwT2Wwb2wQnc=; b=WbAngZX2sg7+mTk7LIMPNocHTW9m7rPUP2YeAX1mD1mbvPXZZ103K06roOeQDrzDNkvY8h7GulErlHpNUYZqtZ3WxZcn00gqgoZq3u8Cmr8wS9+u1IqckuvVm46DGU4+St8fON57+ECtClTY7Qd0wbCKa+8OOmwrB6bSZ7AKyb0jK9IZ2SwYzig2mwrTHt0BdVlU4YXGAMf/8BjEIkyKcFpJAN0DGdPI4xCbbr94Ahabsz+kOx9ft6ibwj9eCK+6
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=a370.521b6165.k1308; bh=gDzCPAPQHXC/302YyvZQOnv30NBHVIzWwT2Wwb2wQnc=; b=gS3ZR5tUdVqLBSGnXJ17z3+M+F65H/+jemQGErBH6J8zYt47aaGBqdv886OKlxcxLnCqWgiRtZuSzqVrPsh5NqmiRNMgBYfl6Pwc0f3X3sBG/uLQunBotR58k91ycEgHinkqP5LHKoUj6fHJ17ezoqh4kTc3VTl5wpdAsdaa9uKzQGOxIEvQK7QChw/714Uyj8C1+X28uURTBm68G76R16Qes+G6SfEzjVdeqyekpOnfFPw3DzbeA1mVg4LPbatB
Received: (ofmipd 127.0.0.1); 26 Aug 2013 14:08:15 -0000
Date: 26 Aug 2013 10:08:37 -0400
Message-ID: <alpine.BSF.2.00.1308261005360.76238@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Jelte Jansen" <jelte.jansen@sidn.nl>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <521B165C.9000809@sidn.nl>
References: <20130823143402.49936.qmail@joyce.lan> <521B165C.9000809@sidn.nl>
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: Mon, 26 Aug 2013 14:08:40 -0000

> prevented, not solved. I would like to prevent someone from having to
> submit a draft specifying that in the case of TXT, the (name, class,
> type)-tuple should be extended with the first X octets from the RDATA
> fields, somewhere in the future, because client-side demuxing is getting
> too buggy and it seems like a good idea to select specific records in
> the DNS itself.

Could you point to anyone, anywhere, who has ever said that the odd 
history of the SPF TXT record means that it is perfectly fine to do
something similar in the future?

On the other hand, please look at all of the stuff that people outside 
of the IETF do with apex TXT records, and try and say with a straight face 
that SPF as as much as 1% of the multiplexing problem.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From Jelte.Jansen@sidn.nl  Mon Aug 26 07:44:21 2013
Return-Path: <Jelte.Jansen@sidn.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 B304D21E8083 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBiq23gGWsE4 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:44:17 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 1732721E8053 for <ietf@ietf.org>; Mon, 26 Aug 2013 07:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=dwDJ99SKRzQOgfxohGyiAMkzyUrkU7IkHgWVzZeuxYs=; b=ZsuMB7sdPmPAIyw8gdKghIzDT/IWF/jr9A0hKFqI3S/BqEFLbwNNJOngSTf0njn3OCvlKJ0Eo7TQYBM4TX0GWe8AV8gq1BQJP8l8z/KMXq7DozHuFfgxGGhjCe5D976VK8q00dnesu/I07jjMn2EkRRfAVt5165/JpRHzeZykAs=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r7QEi0aC001460-r7QEi0aE001460 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Mon, 26 Aug 2013 16:44:00 +0200
Received: from [94.198.152.214] (94.198.152.214) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 26 Aug 2013 16:44:00 +0200
Message-ID: <521B69AD.5020108@sidn.nl>
Date: Mon, 26 Aug 2013 16:43:57 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130823143402.49936.qmail@joyce.lan> <521B165C.9000809@sidn.nl> <alpine.BSF.2.00.1308261005360.76238@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1308261005360.76238@joyce.lan>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 14:44:21 -0000

On 08/26/2013 04:08 PM, John R Levine wrote:
> 
> Could you point to anyone, anywhere, who has ever said that the odd
> history of the SPF TXT record means that it is perfectly fine to do
> something similar in the future?
> 

Three of the four points on the list that triggered my first message in
this particular thread were:

- no <this new rrtype> support in my provisioning system
- no <this new rrtype> support in my firewall
- no <this new rrtype> support in my DNS Library

Those aren't things that'll magically disappear, even with universal
deployment of 3597.

Some, and maybe all of these, might be generally solved if
draft-levine-dnsextlang takes off, though I have serious doubts about
the second, and some doubts about the first.

Until such time, I'd personally prefer to see some explicit notion that
the odd history of the SPF TXT record should not be seen as a precedent
and best practice, rather than hope that this is implicit.


> On the other hand, please look at all of the stuff that people outside
> of the IETF do with apex TXT records, and try and say with a straight
> face that SPF as as much as 1% of the multiplexing problem.
> 

There may be a reason those are not standardized. And not just because
there are too many grumpy people here shouting 'get off my lawn'. Or at
least not all of them :)

Jelte

From bmanning@karoshi.com  Sat Aug 24 10:43:44 2013
Return-Path: <bmanning@karoshi.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A77911E8159; Sat, 24 Aug 2013 10:43:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.149
X-Spam-Level: 
X-Spam-Status: No, score=-6.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l2uOC9tbBETP; Sat, 24 Aug 2013 10:43:40 -0700 (PDT)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by ietfa.amsl.com (Postfix) with ESMTP id 685CB11E80E3; Sat, 24 Aug 2013 10:43:36 -0700 (PDT)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id r7OHhDdr031921; Sat, 24 Aug 2013 17:43:23 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id r7OHhAXi031920; Sat, 24 Aug 2013 17:43:10 GMT
Date: Sat, 24 Aug 2013 17:43:10 +0000
From: bmanning@vacation.karoshi.com
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
Message-ID: <20130824174310.GB31770@vacation.karoshi.com.>
References: <20130823180411.50961.qmail@joyce.lan> <5D4CC1CD-D897-4F46-91A7-02B8176F762A@isi.edu> <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwhM6=m1wKKayeY2Z5VBosGi=WtGHk3Ob9myog0Y+rYyHw@mail.gmail.com>
User-Agent: Mutt/1.4.1i
X-Mailman-Approved-At: Mon, 26 Aug 2013 07:48:30 -0700
Cc: "dnsext@ietf.org" <dnsext@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, manning bill <bmanning@isi.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Aug 2013 17:43:44 -0000

On Sat, Aug 24, 2013 at 08:39:36AM -0400, Phillip Hallam-Baker wrote:
> On Fri, Aug 23, 2013 at 3:46 PM, manning bill <bmanning@isi.edu> wrote:
> 
> >
> >         the question is not that "nobody" checks type 99, the question is
> > "is the rate of adoption
> >         of type 99 -changing- in relation to type 16?
> >
> 
> As John pointed out, support for checking type 99 has decreased and
> continues to decrease rather than increase. So waiting longer is not going
> to solve the issue.

	that is unclear...  we have second hand reports, but only actual
	data from very recent DNS logs.   did those numbers increase or 
	decrease?  No evidence has been presented.

> Putting a statement in an RFC does not mean that the world will
> automatically advance towards that particular end state.

	ain't it the truth.  -BUT- its still worthwhile documenting the 
	best technical path and why it was abandoned.   The issues wrt
	wildcards (thanks), DNSSEC considerations,  and code overhead to 
	demux type 16  vs.  the temporary problem of two lookups -IF- type 
	99 is not used, plus past guidance from the IAB and the IESG really 
	need to make it into a document in the RFC cannon.
	

> Forcing a WG to adopt a position to suit another constituency is not going
> to lead them to advocate for that position in deployment constituencies.
> Particularly when the original constituency does nothing to advance
> deployment.

	Dorthy Parker said: "You can lead a whore to culture, but you can't make her think".
	Point the bias arrow either way youd like.  And as stated elsewhere, if Yahoo, Google,
	Microsoft, AOL, et.al.  were simply waiting for the IETF to settle on a solution,
	I'll raise O'Dells law;  "The installed base does not matter".

	End of the day, the SPFBIS wg is adament in their choice, document, explain
	and move on.  

	Robert Heinlein: Never try to teach a pig to sing; it wastes your time and it
	annoys the pig.

	I think the SPFBIS folks are annoyed enough...


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

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


From damascene.joachimpillai@verizon.com  Fri Aug 23 11:32:34 2013
Return-Path: <damascene.joachimpillai@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 603E411E8121 for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1g-KlBFImkaJ for <ietf@ietfa.amsl.com>; Fri, 23 Aug 2013 11:32:29 -0700 (PDT)
Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) by ietfa.amsl.com (Postfix) with ESMTP id EB68011E80C5 for <ietf@ietf.org>; Fri, 23 Aug 2013 11:32:28 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi01.verizon.com) ([166.68.71.143]) by omzsmtpe02.verizonbusiness.com with ESMTP; 23 Aug 2013 18:32:28 +0000
From: "Joachimpillai, Damascene M" <damascene.joachimpillai@verizon.com>
X-IronPort-AV: E=Sophos;i="4.89,943,1367971200"; d="scan'208";a="542691039"
Received: from fhdp1lumxc7hb02.verizon.com (HELO FHDP1LUMXC7HB02.us.one.verizon.com) ([166.68.59.189]) by fldsmtpi01.verizon.com with ESMTP; 23 Aug 2013 18:32:27 +0000
Received: from FHDP1LUMXC7V31.us.one.verizon.com ([166.68.125.32]) by FHDP1LUMXC7HB02.us.one.verizon.com ([166.68.59.189]) with mapi; Fri, 23 Aug 2013 14:32:27 -0400
To: Discussion IETF <ietf@ietf.org>
Date: Fri, 23 Aug 2013 14:32:27 -0400
Subject: RE: [Recentattendees] Huawei is the Host for IETF 88 in Vancouver
Thread-Topic: [Recentattendees] Huawei is the Host for IETF 88 in Vancouver
Thread-Index: Ac6gLUgH+Mf8K6q6SwGnUZoyz1UdDgAAdHBw
Message-ID: <689CE984BDBA8B4CAF3EA6E2CDC5CACB01230DB6E0@FHDP1LUMXC7V31.us.one.verizon.com>
References: <19512979-1651-497A-AFC6-20090375A0CF@isoc.org>
In-Reply-To: <19512979-1651-497A-AFC6-20090375A0CF@isoc.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-Mailman-Approved-At: Mon, 26 Aug 2013 07:48:41 -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, 23 Aug 2013 18:32:34 -0000

Thanks

-- DJ

-----Original Message-----
From: recentattendees-bounces@ietf.org [mailto:recentattendees-bounces@ietf=
.org] On Behalf Of Ray Pelletier
Sent: Friday, August 23, 2013 2:19 PM
To: recentattendees@ietf.org
Subject: [Recentattendees] Huawei is the Host for IETF 88 in Vancouver

The IAOC is pleased to announce that Huawei will be the Host for IETF 88 in=
 Vancouver. =20

Huawei has been a long time supporter of the IETF through its participation=
 and sponsorships at IETF meetings, but this is their first time as the Hos=
t of an IETF meeting. =20
Congratulations, welcome and Thank You!

Registration is now open for IETF 88 at: http://www.ietf.org/meetings/88/

Many sponsorship opportunities are still available: =20
http://iaoc.ietf.org/documents/IETF-Sponsorship-Opportunities-20132002.pdf

If interested contact Andrew Dvorshak, dvorshak@isoc.org.

Once again, thank you Huawei!. =20

See you in Vancouver in 71 days.

Ray
IAD

2014 Meeting Venues

IETF 89	London		Hilton Metropole			March 2-7
IETF 90	Toronto		Fairmont Royal York		July 20 - 25
IETF 91	Honolulu	Hilton Hawaiian Village	November 9 - 14




_______________________________________________
Recentattendees mailing list
Recentattendees@ietf.org
https://www.ietf.org/mailman/listinfo/recentattendees

From johnl@taugh.com  Mon Aug 26 07:49:03 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F03521F9A81 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level: 
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.006,  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 EJUj3cllJxXD for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:49:02 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 44D3821F9A7D for <ietf@ietf.org>; Mon, 26 Aug 2013 07:49:02 -0700 (PDT)
Received: (qmail 53184 invoked from network); 26 Aug 2013 14:49:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=cfbe.521b6add.k1308; bh=RtKNLPJ3GJyvi8MMWHXJYiO363bw+g4AYCDrx5+egB0=; b=ruJ3gdPA4UmHBMxw+QeQdnlB8K4InmCT1mmZ03yDoBYsFLclM402l4nthlvqTQcJuR6W8Z/Kak0CWVh0t0bvUvMfQkJRkO/qabVhfoumLAU9Lgd0CkYJ0gvMS6jzs8zKoL2OrtNY+ItBtdeDmEwwkEKy18Ad4fAqqJoEL9v+TjjcLsZYx7N2hYEvL0XSryb3c+Ztm0/v8isvTtqtCHMc4JMzLYp8GfQiRvIb76U9ddv7JnKnxsaiedlAeF+KeUqA
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=cfbe.521b6add.k1308; bh=RtKNLPJ3GJyvi8MMWHXJYiO363bw+g4AYCDrx5+egB0=; b=RCwnAr+USfSTp6EABK6ftk/2L8vsFG2P1TuoSUTuGP7xSRKfBjmoc24RM6M24zRLFWZRnVEn+BE1h/R1Gx8yTnJxI8FCwccZ4psLVEa/7i8Tpllt9WOD0LR3Gd0ADHJPwr+GYpUV8zTYvMQfRixYKtBot8kN+h6pfdOTwg5xXPdPcyDP4GgZ72rtrZelkQ5Emys22Mi8gkrEDGhhOstFMkefsnwjidi1zz25J7QNnVVS4stpf5q5HWxODPDvAdis
Received: (ofmipd 127.0.0.1); 26 Aug 2013 14:48:39 -0000
Date: 26 Aug 2013 10:49:01 -0400
Message-ID: <alpine.BSF.2.00.1308261046100.76616@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Jelte Jansen" <jelte.jansen@sidn.nl>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <521B69AD.5020108@sidn.nl>
References: <20130823143402.49936.qmail@joyce.lan> <521B165C.9000809@sidn.nl> <alpine.BSF.2.00.1308261005360.76238@joyce.lan> <521B69AD.5020108@sidn.nl>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1344551477-1377528541=:76616"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 14:49:03 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1344551477-1377528541=:76616
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

Sorry if that last one came across as dismissive.

> Until such time, I'd personally prefer to see some explicit notion that
> the odd history of the SPF TXT record should not be seen as a precedent
> and best practice, rather than hope that this is implicit.

I'd have thought that the debate here and elsewhere already documented 
that.  Since it's not specific to SPF, perhaps we could do a draft on 
"overloaded TXT considered harmful" to get it into the RFC record.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
--3825401791-1344551477-1377528541=:76616
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJCQYJKoZIhvcNAQcCoIII+jCCCPYCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBjowggY2MIIFHqADAgECAgMGLywwDQYJKoZIhvcNAQEFBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMzAzMTYxOTQ0MDdaFw0xNDAzMTgxMjI4MzVaMFUxGTAX
BgNVBA0TEHFaMXRuOTBuMkdVODZzemYxGDAWBgNVBAMMD2pvaG5sQHRhdWdo
LmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2guY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAve/4NFMbuvtD6QSuXAoYQ0SkaO9s
DiNHA4saJNV0OIXd6dtM87w7OETKWWVq24Ab6vQaYh218oCF1GDdLv6EiRB8
oL1k9sK2v70iAVT83vEnmaj6/hQVcBI6mZJH6LXyCgYSP2e5yBQqJu+hgLte
bdg7kOKW2tb937jDn9KYRVFIlEU0/iu/b/Buwq3ahg2BsG3vg92Zk+Dv5VON
QDLE8x8wdi1cor7qBY/RERw4O3LXo3644OU0t6KS3aQxLrXEvWZHHvLhsAu1
BjYbC+qdSddDT1t+adEnZq9/wMhNGhPWCd/uFDZanSpyM913b7eI1Q2aNgA0
cccjEgBsp8IipwIDAQABo4IC1TCCAtEwCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSL
djRDW8NpGZJjlhjZ0SLge0hCvjAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6W
NU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0YXVnaC5jb20wggFMBgNVHSAE
ggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIw
geowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqB
vlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhl
IENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0
Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVk
IHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBv
YmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5Bggr
BgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv
Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNv
bS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYY
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQCM
pgcOpxRJazPzEBYnhGENuQqzXeLyA3a8XL7YaxaAJwV7ucDVkyQHu35PUEkh
vVgIKnxq6N9WxHiO6GK/imdwS3LrUBbs+0v+95m6YhJv6ZfvAHTyTLqrozXU
ohR5NRFeL0p1OfK1llnl/I71Fe/JNgxJHDn1puzsFoJD3zYCKgNdST3FPNIb
2v/xIiubuB85tiJSWUlc56OkCdBK3ZgBnwYV8LxFmpOlwedaHC6sxIk1rsuX
BHbRIJwLFy2LqVtNm0M5NzBVyPQf72lPn/aaJLbqY5DDm4/lSy94R+CKXabE
6lWan7xmbqdDDlMxGbpMRWV2Cxi5ONp4uNgNcwI6MYIClzCCApMCAQEwgZQw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDBi8sMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwODI2MTQ0OTAxWjAjBgkqhkiG
9w0BCQQxFgQU32onmXT+SakDJz3W5QgQ7IpL0b0weQYJKoZIhvcNAQkPMWww
ajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4D
AgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAbZxmEjne86nk
QpNXs/OYCRsfHCWcouPVkrOXudHNgRUjxJN79xMu+VWSsDJtMzKkIToMrGr0
Bexnlr4EPNowNxmtRxtNdJy1OU6tyUczZgl9/glhU6p7nXrKlGjKuqDYGOJQ
HCDSsWGbkVO05+IlUkJbox2VcqpvZ+q13y5vuIJNxlQJAslYuVI1SvEaeYZF
dWsBbTmIxachC/rQfS4EaoNDatZ6jih3eNHcLxcHd8Rbe7at0iFNCtYdbbS8
pc/8RXBVkInQD42mzGmJNvlXLr7Gvp0qo9Ahxp9btuDsh53aLG8dGMfJ0+V5
/tgwsBXC7jyvxV4G0J4/QcVDW3kjyw==

--3825401791-1344551477-1377528541=:76616--

From Jelte.Jansen@sidn.nl  Mon Aug 26 07:55:55 2013
Return-Path: <Jelte.Jansen@sidn.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 DE7F311E81AF for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.696
X-Spam-Level: 
X-Spam-Status: No, score=-0.696 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXLd3BwuNp0L for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 07:55:50 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 2499E21F9FE7 for <ietf@ietf.org>; Mon, 26 Aug 2013 07:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=PBKzbMENZ6NkUo6tDGrD2HO0V6AmL+CmH0yLNesEQno=; b=EyR46M+GWe5cmfGvoNewYNBgLRl394sjO01nF3b03+fIyH5igKu4bXY+MCTN5lpwfg/4HNbhPdKPmpNg5ucQgVMsyF/aTgaIwnXjlEFxZ7xfprzGcda2uyDjE2u91NOlAOh7OjfTRx1RdVCegW8HyoRWxUhzWehMWK5NIj/L/ns=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r7QEtnHU001987-r7QEtnHW001987 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Mon, 26 Aug 2013 16:55:49 +0200
Received: from [94.198.152.214] (94.198.152.214) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 26 Aug 2013 16:55:48 +0200
Message-ID: <521B6C72.4010905@sidn.nl>
Date: Mon, 26 Aug 2013 16:55:46 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130823143402.49936.qmail@joyce.lan> <521B165C.9000809@sidn.nl> <alpine.BSF.2.00.1308261005360.76238@joyce.lan> <521B69AD.5020108@sidn.nl> <alpine.BSF.2.00.1308261046100.76616@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1308261046100.76616@joyce.lan>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 14:55:55 -0000

On 08/26/2013 04:49 PM, John R Levine wrote:
> Sorry if that last one came across as dismissive.
> 
>> Until such time, I'd personally prefer to see some explicit notion that
>> the odd history of the SPF TXT record should not be seen as a precedent
>> and best practice, rather than hope that this is implicit.
> 
> I'd have thought that the debate here and elsewhere already documented
> that.  Since it's not specific to SPF, perhaps we could do a draft on
> "overloaded TXT considered harmful" to get it into the RFC record.
> 

It certainly documents there are some persistent people walking around
the dns world ;)

That draft may not be a bad idea.

Jelte


From Jelte.Jansen@sidn.nl  Mon Aug 26 08:16:09 2013
Return-Path: <Jelte.Jansen@sidn.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 339B321E8086 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 08:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_EQ_IP_ADDR=1.119]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H87JXcK3ZxZS for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 08:16:04 -0700 (PDT)
Received: from ede1-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id 85E0421F9D28 for <ietf@ietf.org>; Mon, 26 Aug 2013 08:16:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=+ioKLV/xIZzbVA1kiUwlrM+G0CWC0rAB/1ZTjHQRWXc=; b=ULdIjm4cgJVKwqWhXdIYAlvj+G5zBa+MVVQWkBK8kidjWcYoT0M1G7uDXSuVvrRi0tOQdReDgEV6fTGlofwfN8wtKzsy4lo0Xe+SBu3gpO//e1rWt4OxGmln3n5xtil/zdzD2e/GgFT1SOtXn4Ntv9Yk7VBq+XR+jaZ+ldB9MXs=
Received: from kahubcasn02.SIDN.local ([192.168.2.74]) by ede1-kamx.sidn.nl  with ESMTP id r7QFG2O9002776-r7QFG2OB002776 (version=TLSv1 cipher=AES128-SHA bits=128 verify=CAFAIL); Mon, 26 Aug 2013 17:16:02 +0200
Received: from [94.198.152.214] (94.198.152.214) by kahubcasn02.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.2.328.9; Mon, 26 Aug 2013 17:16:02 +0200
Message-ID: <521B712F.2040703@sidn.nl>
Date: Mon, 26 Aug 2013 17:15:59 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130823143402.49936.qmail@joyce.lan> <521B165C.9000809@sidn.nl> <alpine.BSF.2.00.1308261005360.76238@joyce.lan> <521B69AD.5020108@sidn.nl> <alpine.BSF.2.00.1308261046100.76616@joyce.lan> <521B6C72.4010905@sidn.nl>
In-Reply-To: <521B6C72.4010905@sidn.nl>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.214]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 15:16:09 -0000

On 08/26/2013 04:55 PM, Jelte Jansen wrote:
>>
>> I'd have thought that the debate here and elsewhere already documented
>> that.  Since it's not specific to SPF, perhaps we could do a draft on
>> "overloaded TXT considered harmful" to get it into the RFC record.
>>
> 
> That draft may not be a bad idea.
> 

It has been pointed out to me that rfc5507 already exists. I'll shut up now.

Jelte

From rpelletier@isoc.org  Mon Aug 26 08:16:28 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C107121E8056 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 08:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ENp3okWgcI3 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 08:16:24 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) by ietfa.amsl.com (Postfix) with ESMTP id 243AD21E808D for <ietf@ietf.org>; Mon, 26 Aug 2013 08:16:24 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id E14D6140177; Mon, 26 Aug 2013 11:16:22 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 79A4914013D;  Mon, 26 Aug 2013 11:16:22 -0400 (EDT)
Subject: Re: [IAOC] GST/PST and IETF 88
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <5691.1377479065@sandelman.ca>
Date: Mon, 26 Aug 2013 11:16:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D614CD7-0B02-4B3D-9D26-B90B479DECF8@isoc.org>
References: <20130823142554.29105.99013.idtracker@ietfa.amsl.com> <900A1E2059ADB149B905E3C8FA0046A62C7967DC95@FHDP1LUMXC7V23.us.one.verizon.com> <5691.1377479065@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1085)
Cc: iaoc@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 15:16:28 -0000

Michael,

Thanks for asking.  We have consulted with Canadian tax experts on this =
matter.

The federal Goods and Services Tax (GST) does not apply to Admissions to
"foreign conventions", which is what the IETF meeting is as Canadians =
make up fewer
than 25% of the attendees. Maybe you can work on that.

The Provincial Sales Tax (PST) does not apply to the "right of access to =
an event", thus the=20
registration fee will not be taxed. =20

So, the Early-Bird registration fee will be $650 USD. =20

Registration is open here:  https://www.ietf.org/meeting/88/index.html

Ray
IAD


On Aug 25, 2013, at 9:04 PM, Michael Richardson wrote:

>=20
> Mishra, Sanjay <sanjay.mishra@verizon.com> wrote:
>> 1. Registration A. Early-Bird Registration - USD 650.00 Pay by =
Friday,
>=20
> Since the last Vancouver IETF, the province of BC has "rescinded" it's
> harmonization of provincial and federal sales taxes. (I think the =
decision is
> totally moronic, but, I don't live there).  This change does not =
change the
> crux of my question, just the amount, and it affects the details.
>=20
> My question is:
>   Is ISOC doing GST (the federal VAT) processing?
>   Is ISOC doing PST (the provincial tax, not value-added, last I =
checked...)?
>   My understanding is that attendees to Berlin received a revised =
statement
>   indicating the amount of German VAT that was included in the USD650.
>=20
>   While I wasn't there, and I'm not EC, I am in Canada, and my company =
does
>   process GST, which means that I should be able to claim the GST part =
back.
>=20
> I don't know what the new BC PST is, but it was around 8% before.
> Will the base price be 650 / 1.15, or 650/1.05 ?
>=20
> --=20
> Michael Richardson
> -at the cottage-
>=20


From shem_waw@operamail.com  Mon Aug 26 08:21:42 2013
Return-Path: <shem_waw@operamail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B887421E8091 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 08:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level: 
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_50=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 KZiirV4SYJpi for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 08:21:38 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 657B521E8089 for <ietf@ietf.org>; Mon, 26 Aug 2013 08:21:37 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A27C7204E8 for <ietf@ietf.org>; Mon, 26 Aug 2013 11:21:37 -0400 (EDT)
Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Mon, 26 Aug 2013 11:21:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=operamail.com; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:subject:date:references; s=mesmtp; bh=vhrQr1qwaOnd PRbVUaZswcX+oGw=; b=p4+VyuZx7t6bGlv9y1duwXNoJs+C3Ks5p2loAENvT72w wkLvuc2cATM9x+2uM3oalm5MW0EfWrb3JwEzznVGDKt1xWVeLUfe27KgFQWsP40N mWo0IF94RoQR0tp/NvayMBEUWzR/GYULgVrBNip4JYjlozb5RQA3lG3iRJ8+ays=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:references; s=smtpout; bh=vhrQr1qwaOndPRbVUaZswcX+oGw=; b=ee5QrKa0dGiICBM+E 4LG+eJE1VWo3By1iX4UQyTJX7kPgkMESZ+CjPYb110HIW0jpxCHGMf2JQ3f7WvUo vSl+hPl+/HDFMebQ+b+H2QC0Cx1GoSCvTM1t1RPtprf+90D+ZjQGUG6PoEu8STUY njwL0gDxFOWd6vKHtI8qg0qPCI=
Received: by web2.nyi.mail.srv.osa (Postfix, from userid 99) id 823B3540354; Mon, 26 Aug 2013 11:21:37 -0400 (EDT)
Message-Id: <1377530497.1332.14262381.3D84F15F@webmail.messagingengine.com>
X-Sasl-Enc: BbG8Wp4EkSSXR9wl7prZRfIvcYt5MmPQ187fpBmXi7Qt 1377530497
From: Casey Farrell <shem_waw@operamail.com>
To: ietf@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-be0d4992
Subject: Fwd: Fred MacMurray's
Date: Mon, 26 Aug 2013 08:21:37 -0700
References: <1377530480.1194.14250285.19ED8B5E@webmail.messagingengine.com>
X-Mailman-Approved-At: Mon, 26 Aug 2013 08:23:56 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 15:21:43 -0000

-- 
  Casey Farrell
  shem_waw@operamail.com

----- Original message -----
From: Casey Farrell <shem_waw@operamail.com>
To: wine@sfchronicle.com
Subject: Fred MacMurray's
Date: Mon, 26 Aug 2013 08:21:21 -0700



-- 
 Casey Farrell, designer/author
1824 Rancho
Nicasio, CA 
  shem_waw@operamail.com



RE: Fred MacMurray's favorite pasttime


   I thoroughly eenjoyed this Sunday's Chronicle WINE section (and the
   rest of the paper, too!) but was wondering

while I came across various announcements if anyone at The Chron
remembers what Fred MacMurray's hobby was?

  He enjoyed rewriting newscopy in BRITIC ( a phonetic spelling system) 
  which had been a fad in England after WWII.

And all that great material yesterday out of which to create a sampler,
I am sure he would have typed up these-

  SUNQMU     TREFEXEN     STAGZ LIIP     LWWIS MARTINI    MAWNT VIIDUR  
   WINDZUR      QKVIL    RUXURFURD

IAWNTVIL   BQIW   MONDOVI    GALQ   GURNVIL    TCIIZ   BIIF   BRED  
SALUD   OLIV OIL etc

 The point is that spelling reform, which is the cheapest and best
 renovator of any economy...has yet to occur in the USA.

It occured in Germany while the war raged; the German script was changed
over from Gothic to Roman. Very dramatic.

 The changes necessary for recalibration of ENGLISH & FRENCH spelling (
 didn't I mention that? Sorry, FRENCH is also 'skewed'!)

are easy and can be done right now with practiically any alternative
spelling system. The only resistors have always been the 

corporate 'brand name' holders who do not understand the legal
difference between LOGO & TRADEMARK in the first place...

but it is a legitimate question...what happens if I change the spelling?
(but it is pronounced the same) You'll then be "Kosher"!

Others who've enjoyed this hobby (civic betterment) include Ben
Franklin, Mark Twain, President Teddy Roosevelt, G, B, Shaw,

Claire Trevor, Paul Harvey, Linda Darnel, WIlliam Barnes, Prince Lucien
Bonaparte, Piaf, Mary Austen, Jack London, Lola Montez,

Jackie Gleason, Clifton Webb, Dr. Sun Yet Sen, President Thomas
Jefferson, Allen Ginsberg, Mary Pickford & Rosalind Russell.

  The savings in time & materials when switiching over to a phontic
  spelling was shown by the 1918 Bloshevik Inner Committee to

be an austounding 35% reduction just in the use of newspaper ink! With
TEXTING it is thought that 'virtually free' NEW MEDIA

will create a revenue stream that will produce what will be needed for
our Social Security payments in the near future. 

Casey Farrell

-- 
http://www.fastmail.fm - The professional email service


-- 
http://www.fastmail.fm - Faster than the air-speed velocity of an
                          unladen european swallow


From jgunn6@csc.com  Mon Aug 26 08:57:18 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDD4011E81C9; Mon, 26 Aug 2013 08:57:18 -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, 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 zN8O+RaQxcud; Mon, 26 Aug 2013 08:57:12 -0700 (PDT)
Received: from mail85.messagelabs.com (mail85.messagelabs.com [216.82.241.211]) by ietfa.amsl.com (Postfix) with ESMTP id 7602521E8091; Mon, 26 Aug 2013 08:57:06 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-6.tower-85.messagelabs.com!1377532624!42040340!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3364 invoked from network); 26 Aug 2013 15:57:04 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-6.tower-85.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Aug 2013 15:57:04 -0000
Received: from amer-gw09.amer.csc.com (cscmail.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r7QFpO2L010028; Mon, 26 Aug 2013 11:51:24 -0400
In-Reply-To: <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com>	<OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com>	<OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi>	<272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
MIME-Version: 1.0
Subject: Re: Charging remote participants
X-KeepSent: F09180C5:6763EA0F-85257BD3:00561D37; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com>
Date: Mon, 26 Aug 2013 11:57:07 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/26/2013 11:50:24 AM, Serialize complete at 08/26/2013 11:50:24 AM
Content-Type: multipart/alternative; boundary="=_alternative 0057A0AF85257BD3_="
Cc: ietf-bounces@ietf.org, 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: Mon, 26 Aug 2013 15:57:19 -0000

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

> From: Abdussalam Baryun <abdussalambaryun@gmail.com>
> Date: 08/25/2013 08:40 AM
> 
> ...
> The reward/motivation from IETF to participants is to 
> acknowledge in writting their efforts, which I think still the IETF 
> management still does not motivate/encourage. 

I COMPLETELY disagree with this.  The reward/motivation for participation 
(remotely or in person) is to have your comments, ideas, suggestions,... 
TAKEN SERIOUSLY, even if the eventual decision goes "against you".

Of course, that presupposes that  your comments are sensible, and show 
that you understand the context.

It is the specific authors, and not "the IETF" that determines who gets 
mentioned in the "Acknowledgements" section.  In the working groups I am 
involved with, I have found the authors to be very generous with 
acknowledgements.  Sometimes I have been acknowledged when my comments 
were primarily editorial and clarification, without actually adding any 
new ideas.  Of course, there have been one or two  times that I have 
thought I made a contribution, but didn't get mentioned.  That is the 
author's choice.

As my mother used to say "What you lose on the roundabouts you gain on the 
swings"

>  
> IETF Remote Participants (IETFRP) SHOULD charge the IETF not the 
> other way, because still the IETF ignores some IETFRP efforts (or 
> even hides information that should be provided to the diverse 
community).

 
I have never felt "ignored" as a remote participant.  Sometimes 
misunderstood because there is little opportunity to expand and explain 
when you are remote.  But never ignored.

I have no idea what you mean by "hides information".  Are you suggesting 
that someone is censoring mailing list posts?

Janet
--=_alternative 0057A0AF85257BD3_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2><br>
&gt; From: Abdussalam Baryun &lt;abdussalambaryun@gmail.com&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 08/25/2013 08:40 AM</font></tt>
<br><tt><font size=2>&gt; </font></tt>
<br><tt><font size=2>&gt; ...</font></tt>
<br><tt><font size=2>&gt; The reward/motivation from IETF to participants
is to <br>
&gt; acknowledge in writting their efforts, which I think still the IETF
<br>
&gt; management still does not motivate/encourage. </font></tt>
<br>
<br><tt><font size=2>I COMPLETELY disagree with this. &nbsp;The reward/motivation
for participation (remotely or in person) is to have your comments, ideas,
suggestions,... &nbsp;TAKEN SERIOUSLY, even if the eventual decision goes
&quot;against you&quot;.</font></tt>
<br>
<br><tt><font size=2>Of course, that presupposes that &nbsp;your comments
are sensible, and show that you understand the context.</font></tt>
<br>
<br><tt><font size=2>It is the specific authors, and not &quot;the IETF&quot;
that determines who gets mentioned in the &quot;Acknowledgements&quot;
section. &nbsp;In the working groups I am involved with, I have found the
authors to be very generous with acknowledgements. &nbsp;Sometimes I have
been acknowledged when my comments were primarily editorial and clarification,
without actually adding any new ideas. &nbsp;Of course, there have been
one or two &nbsp;times that I have thought I made a contribution, but didn't
get mentioned. &nbsp;That is the author's choice.</font></tt>
<br>
<br><tt><font size=2>As my mother used to say &quot;What you lose on the
roundabouts you gain on the swings&quot;</font></tt>
<br>
<br><tt><font size=2>&gt; &nbsp;</font></tt>
<br><tt><font size=2>&gt; IETF Remote Participants (IETFRP) SHOULD charge
the&nbsp;IETF not the <br>
&gt; other way, because still the IETF ignores some IETFRP efforts (or
<br>
&gt; even hides information that should be provided to the diverse community).</font></tt>
<br>
<br><tt><font size=2>&nbsp;</font></tt>
<br><tt><font size=2>I have never felt &quot;ignored&quot; as a remote
participant. &nbsp;Sometimes misunderstood because there is little opportunity
to expand and explain when you are remote. &nbsp;But never ignored.</font></tt>
<br>
<br><tt><font size=2>I have no idea what you mean by &quot;hides information&quot;.
&nbsp;Are you suggesting that someone is censoring mailing list posts?</font></tt>
<br>
<br><tt><font size=2>Janet</font></tt>
--=_alternative 0057A0AF85257BD3_=--

From swmike@swm.pp.se  Mon Aug 26 09:44:56 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5C021F9E63 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 09:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o25MYHvVrTeh for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 09:44:55 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 5E71821F9E5A for <ietf@ietf.org>; Mon, 26 Aug 2013 09:44:55 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 851E79C; Mon, 26 Aug 2013 18:44:52 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7C2D19A for <ietf@ietf.org>; Mon, 26 Aug 2013 18:44:52 +0200 (CEST)
Date: Mon, 26 Aug 2013 18:44:52 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Charging remote participants
In-Reply-To: <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com>
Message-ID: <alpine.DEB.2.02.1308261842060.15239@uplift.swm.pp.se>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com> <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 16:44:56 -0000

On Mon, 26 Aug 2013, Janet P Gunn wrote:

> I have never felt "ignored" as a remote participant.  Sometimes 
> misunderstood because there is little opportunity to expand and explain 
> when you are remote.  But never ignored.
>
> I have no idea what you mean by "hides information".  Are you suggesting
> that someone is censoring mailing list posts?

It's my experience that different WG mailing lists handle remote 
participation very differently. I have put it down to a difference in 
common working method of the people participating in different WGs. Some 
WGs tend to accumulate people who are very used to remote participation 
and discussion, others seem to accumulate people who have a different 
history so they tend to handle posts very differently.

Perhaps that's why the view on how well this works is so different between 
different people?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From davearonson@gmail.com  Mon Aug 26 09:55:33 2013
Return-Path: <davearonson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7046A11E81D0 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 09:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_32=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVtD1YUNSJyD for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 09:55:31 -0700 (PDT)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id AE04111E81C8 for <ietf@ietf.org>; Mon, 26 Aug 2013 09:55:31 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id g10so3677707pdj.2 for <ietf@ietf.org>; Mon, 26 Aug 2013 09:55:31 -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:from:date:message-id :subject:to:content-type; bh=MtHmJWkDT88xpGVwP3sOu+z6M8ZSSnOvhJo+KN7A0Ts=; b=sOAohRyrVAHVW1U9sqZfuu7MPJv4lgFpkzOr7U+zovPHsfIn4+ojn/IOViBuf2uCTx 7mAuZ63GdXMJjIr0HTDdJojJ4J2V8eP7nfLB33GxdP0uGT1ORKHUUtFS9ks0mFuoDs8v bg+ejreLv1kkBz48UOEpOJFQsEBcuiEvorP0iHurQIFtmj728B0h7+DRm3BWAh0/Bkdo FDq7RKuLXQD5TSIOJ4AjI3C1SkqtBHbl0xWGc1DhHEIRpgzXAMmNQDy5Vz45MfaSOlfD gkBecoXqli8qIxh64AcTi7XBH/ZJvWnuQ8OES9PFAy8r9XMTjHckShSZrZqLAtvZ5x/G Am9A==
X-Received: by 10.68.244.168 with SMTP id xh8mr16327888pbc.3.1377536131302; Mon, 26 Aug 2013 09:55:31 -0700 (PDT)
MIME-Version: 1.0
Sender: davearonson@gmail.com
Received: by 10.68.58.195 with HTTP; Mon, 26 Aug 2013 09:54:51 -0700 (PDT)
In-Reply-To: <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com> <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com>
From: Dave Aronson <ietf2dave@davearonson.com>
Date: Mon, 26 Aug 2013 12:54:51 -0400
X-Google-Sender-Auth: sCdPscGS2Ax8GMfLSL-I3IT4aZg
Message-ID: <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@mail.gmail.com>
Subject: Re: Charging remote participants
To: IETF Discussion Mailing List <ietf@ietf.org>, Janet P Gunn <jgunn6@csc.com>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 16:55:33 -0000

On Mon, Aug 26, 2013 at 11:57 AM, Janet P Gunn <jgunn6@csc.com> wrote:

>> From: Abdussalam Baryun <abdussalambaryun@gmail.com>
>> Date: 08/25/2013 08:40 AM
>>
>> ...
>> The reward/motivation from IETF to participants is to
>> acknowledge in writting their efforts, which I think still the IETF
>> management still does not motivate/encourage.
>
> I COMPLETELY disagree with this.  The reward/motivation for participation
> (remotely or in person) is to have your comments, ideas, suggestions,...
> TAKEN SERIOUSLY, even if the eventual decision goes "against you".

Amen.  It also fits very well with the standard "engineer mentality",
especially those tired of banging heads against managerial brick walls
at day-jobs.

I've also participated in assorted WGs because I wanted to *learn*
what an upcoming standard was (probably) going to look like.
Sometimes I didn't have ideas to contribute, sometimes I didn't even
fully grok the context... but I still consider myself (to have been) a
"remote participant", at least for keeping up on it and being willing
(if not always able) to offer ideas.

As for being acked in writing, I'll grant Abdussalam that it's nice.
It was a fun little ego-boost (and resume-boost!) when I was credited
in a draft, and especially when that became an RFC.  However, that's
not at all why I did it.  It was more like "I've been tasked to
implement something using this standard, let's see what it says, oh
the IETF is debating the next version, let's see what they're
saying"... and when I couldn't help opening my fat trap, they liked
what I said.  Who'da thunk it?  <:*)

> As my mother used to say "What you lose on the roundabouts
> you gain on the swings"

I had to go Google that.  To save others the trouble: it seems to
refer to rides at a carnival, and mean "whatever losses you suffer in
one place, you usually make up elsewhere", implying that it all
balances out in the end.

-Dave

-- 
Dave Aronson, the T. Rex of Codosaurus LLC,
secret-cleared freelance software developer
taking contracts in or near NoVa or remote.
See information at http://www.Codosaur.us/.

From randy_presuhn@mindspring.com  Mon Aug 26 10:20:37 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5451511E81DA for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 10:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.74
X-Spam-Level: 
X-Spam-Status: No, score=-100.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcZ+oTizzF-G for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 10:20:32 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 4308421F9EA9 for <ietf@ietf.org>; Mon, 26 Aug 2013 10:20:32 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=GX+wNwV5Q3rIWKgPYCsD4/AlS9yg0AkdCVlqtudHupEhsPdFZtOVU6ub+CMQNK3b; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.53.23] (helo=oemcomputer) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1VE0Sr-00072l-E8 for ietf@ietf.org; Mon, 26 Aug 2013 13:20:29 -0400
Message-ID: <005201cea280$a5fa9720$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF Discussion Mailing List" <ietf@ietf.org>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com><OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com><CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com><OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com><20130812200621.GB68553@verdi><272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com><F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com><CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com><OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com> <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@mail.gmail.com>
Subject: Re: Charging remote participants
Date: Mon, 26 Aug 2013 10:21:05 -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: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888ba196d48fc2e3f08c816538d725966e77c3b60145c2c3190350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.53.23
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 17:20:37 -0000

Hi -

> From: "Dave Aronson" <ietf2dave@davearonson.com>
> To: "IETF Discussion Mailing List" <ietf@ietf.org>; "Janet P Gunn" <jgunn6@csc.com>
> Sent: Monday, August 26, 2013 9:54 AM
> Subject: Re: Charging remote participants
... 
> I had to go Google that.  To save others the trouble: it seems to
> refer to rides at a carnival, and mean "whatever losses you suffer in
> one place, you usually make up elsewhere", implying that it all
> balances out in the end.

I had to google it as well.  The word "roundabout" (in the
sense of "traffic circle") led me to mistakenly think it
had something to do with navigating British streets, but
this seems to be where the idiom comes from:
http://www.oldpoetry.com/Patrick_R_Chalmers/Roundabouts_and_Swings

Randy


From jgunn6@csc.com  Mon Aug 26 11:57:09 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1FFF11E81FD for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 11:57:09 -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 eFfiFOeXa9jZ for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 11:56:57 -0700 (PDT)
Received: from mail170.messagelabs.com (mail170.messagelabs.com [216.82.253.227]) by ietfa.amsl.com (Postfix) with ESMTP id D075721F9EA9 for <ietf@ietf.org>; Mon, 26 Aug 2013 11:56:56 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-12.tower-170.messagelabs.com!1377543412!19181141!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11922 invoked from network); 26 Aug 2013 18:56:54 -0000
Received: from amer-mta101.csc.com (HELO amer-mta101.csc.com) (20.137.2.87) by server-12.tower-170.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Aug 2013 18:56:54 -0000
Received: from amer-gw09.amer.csc.com (cscmail.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r7QIpBfF025786 for <ietf@ietf.org>; Mon, 26 Aug 2013 14:51:12 -0400
In-Reply-To: <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@mail.gmail.com>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com> <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com> <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@mail.gmail.com>
To: Dave Aronson <ietf2dave@davearonson.com>
MIME-Version: 1.0
Subject: Re: Charging remote participants
X-KeepSent: 565D73B3:9F585AF8-85257BD3:0066E5AA; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF565D73B3.9F585AF8-ON85257BD3.0066E5AA-85257BD3.00681712@csc.com>
Date: Mon, 26 Aug 2013 14:56:50 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/26/2013 02:50:12 PM, Serialize complete at 08/26/2013 02:50:12 PM
Content-Type: multipart/alternative; boundary="=_alternative 006816DB85257BD3_="
Cc: davearonson@gmail.com, 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: Mon, 26 Aug 2013 18:57:10 -0000

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

> 
> > As my mother used to say "What you lose on the roundabouts
> > you gain on the swings"
> 
> I had to go Google that.  To save others the trouble: it seems to
> refer to rides at a carnival, and mean "whatever losses you suffer in
> one place, you usually make up elsewhere", implying that it all
> balances out in the end.

Oh dear, I didn't realize it was that obscure.

Yes, "you win some, you lose some, but in the end it balances out"

Or "sometimes you are the dog, and sometimes you are the fire hydrant"

It refers to carnivals or fairs.

Roundabouts are merry-go-rounds.

Swings are aka swingboats. and do a full 360 degree rotation.  Wikipedia 
calls them Pirate Ship (Ride) 
http://en.wikipedia.org/wiki/Pirate_ship_(ride)

Janet
--=_alternative 006816DB85257BD3_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2><br>
&gt; <br>
&gt; &gt; As my mother used to say &quot;What you lose on the roundabouts<br>
&gt; &gt; you gain on the swings&quot;<br>
&gt; <br>
&gt; I had to go Google that. &nbsp;To save others the trouble: it seems
to<br>
&gt; refer to rides at a carnival, and mean &quot;whatever losses you suffer
in<br>
&gt; one place, you usually make up elsewhere&quot;, implying that it all<br>
&gt; balances out in the end.<br>
</font></tt>
<br><tt><font size=2>Oh dear, I didn't realize it was that obscure.</font></tt>
<br>
<br><tt><font size=2>Yes, &quot;you win some, you lose some, but in the
end it balances out&quot;</font></tt>
<br>
<br><tt><font size=2>Or &quot;sometimes you are the dog, and sometimes
you are the fire hydrant&quot;</font></tt>
<br>
<br><tt><font size=2>It refers to carnivals or fairs.</font></tt>
<br>
<br><tt><font size=2>Roundabouts are merry-go-rounds.</font></tt>
<br>
<br><tt><font size=2>Swings are aka swingboats. and do a full 360 degree
rotation. &nbsp;Wikipedia calls them Pirate Ship (Ride) </font></tt><a href=http://en.wikipedia.org/wiki/Pirate_ship_(ride)><tt><font size=2>http://en.wikipedia.org/wiki/Pirate_ship_(ride)</font></tt></a>
<br>
<br><tt><font size=2>Janet</font></tt>
--=_alternative 006816DB85257BD3_=--

From jgunn6@csc.com  Mon Aug 26 12:08:49 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D8D11E820A; Mon, 26 Aug 2013 12:08:49 -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 nXSQSORKjU0O; Mon, 26 Aug 2013 12:08:43 -0700 (PDT)
Received: from mail171.messagelabs.com (mail171.messagelabs.com [216.82.253.243]) by ietfa.amsl.com (Postfix) with ESMTP id B4B7911E81FB; Mon, 26 Aug 2013 12:08:43 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-10.tower-171.messagelabs.com!1377544117!24301082!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.9.11; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23370 invoked from network); 26 Aug 2013 19:08:39 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-10.tower-171.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 26 Aug 2013 19:08:39 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (8.13.8/8.13.8) with ESMTP id r7QJ4K4e011046; Mon, 26 Aug 2013 15:04:21 -0400
In-Reply-To: <005201cea280$a5fa9720$6b01a8c0@oemcomputer>
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com><OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com><CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com><OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com><20130812200621.GB68553@verdi><272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com><F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com><CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com><OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com> <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@mail.gmail.com> <005201cea280$a5fa9720$6b01a8c0@oemcomputer>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>
MIME-Version: 1.0
Subject: Re: Charging remote participants
X-KeepSent: E3F6ACD7:7D40EB9D-85257BD3:0068F27A; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OFE3F6ACD7.7D40EB9D-ON85257BD3.0068F27A-85257BD3.0069298F@csc.com>
Date: Mon, 26 Aug 2013 15:08:33 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 08/26/2013 03:01:55 PM, Serialize complete at 08/26/2013 03:01:55 PM
Content-Type: multipart/alternative; boundary="=_alternative 0069295285257BD3_="
Cc: ietf-bounces@ietf.org, 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: Mon, 26 Aug 2013 19:08:49 -0000

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

> From: "Randy Presuhn" <randy_presuhn@mindspring.com>

> 
> I had to google it as well.  The word "roundabout" (in the
> sense of "traffic circle") led me to mistakenly think it
> had something to do with navigating British streets, but
> this seems to be where the idiom comes from:
> http://www.oldpoetry.com/Patrick_R_Chalmers/Roundabouts_and_Swings
> 
> Randy

I am pretty sure that the usage of "roundabout" to refer to a traffic 
circle is derived from its usage as a carnival ride, which in the US would 
be called a  "merry-go-round".

Janet

--=_alternative 0069295285257BD3_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2><br>
&gt; From: &quot;Randy Presuhn&quot; &lt;randy_presuhn@mindspring.com&gt;</font></tt>
<br><tt><font size=2><br>
&gt; <br>
&gt; I had to google it as well. &nbsp;The word &quot;roundabout&quot;
(in the<br>
&gt; sense of &quot;traffic circle&quot;) led me to mistakenly think it<br>
&gt; had something to do with navigating British streets, but<br>
&gt; this seems to be where the idiom comes from:<br>
&gt; </font></tt><a href=http://www.oldpoetry.com/Patrick_R_Chalmers/Roundabouts_and_Swings><tt><font size=2>http://www.oldpoetry.com/Patrick_R_Chalmers/Roundabouts_and_Swings</font></tt></a><tt><font size=2><br>
&gt; <br>
&gt; Randy<br>
</font></tt>
<br><tt><font size=2>I am pretty sure that the usage of &quot;roundabout&quot;
to refer to a traffic circle is derived from its usage as a carnival ride,
which in the US would be called a &nbsp;&quot;merry-go-round&quot;.</font></tt>
<br>
<br><tt><font size=2>Janet<br>
</font></tt>
--=_alternative 0069295285257BD3_=--

From arturo.servin@gmail.com  Mon Aug 26 15:25:17 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DD5311E80DF for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:25: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=[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 DnsAUuzU7-C2 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:25:15 -0700 (PDT)
Received: from mail-ye0-x22f.google.com (mail-ye0-x22f.google.com [IPv6:2607:f8b0:4002:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 4514411E80D5 for <ietf@ietf.org>; Mon, 26 Aug 2013 15:25:15 -0700 (PDT)
Received: by mail-ye0-f175.google.com with SMTP id r10so999305yen.20 for <ietf@ietf.org>; Mon, 26 Aug 2013 15:25:14 -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=9Tc6wux2Iv2iMo6RN5I1ajGSdyPHRS46Yy7Bcv5vK18=; b=CDuumCVkVSBgvtKtuD1VDXqbc5+ArvoZ2FCxhmNS3lVXpnYyJLYmdFWJdmU048yjVp m829FJlcibLdZZVXyzi+DCc0GcHSzpFw+dk4UlP9I6ggL5wRXAovpopmkLf0ReOGiXR/ sFSAPSoqf7PaOOUMkqqVkhI8hkLWHpnCKi60Pi2ZU8Ct7LkTWaR5cv5SthN93AKcwRby cx9DPDEv5stwka3ysPAzODHo3poKNK4GyDJ8o5npq6sFr5GhFN+M9WcT74rNMiyoEzt9 j8bH1d0iVbpsX8KDjtAs3C2+7FOrx7+0lwEoki7/irxjatqKn9TbItzG5+KBoscQKmlo HzVQ==
X-Received: by 10.236.128.45 with SMTP id e33mr16763044yhi.11.1377555914720; Mon, 26 Aug 2013 15:25:14 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (host50.181-15-118.telecom.net.ar. [181.15.118.50]) by mx.google.com with ESMTPSA id v22sm20594087yhn.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 Aug 2013 15:25:13 -0700 (PDT)
Message-ID: <521BD5C6.8070106@gmail.com>
Date: Mon, 26 Aug 2013 19:25:10 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Charging remote participants
References: <CAKe6YvPb2byEp7ic_J+CR-8UBycepKQ8uszOchXTk6RqehbBeg@mail.gmail.com> <OFF816F7EA.E9F0330D-ON85257BC5.0051D5AD-85257BC5.0053BC91@csc.com> <CAKe6YvN6DSDJGU-MDtMPce_TM=639rorMAdnr-vtCwC+2AUnng@mail.gmail.com> <OF2FB45330.E1DCDB32-ON85257BC5.0056B5ED-85257BC5.0056EEC6@csc.com> <20130812200621.GB68553@verdi> <272672C2-F883-4364-A493-FB32FC0DCC17@gmail.com> <F8682AA6-B487-4137-86B8-5AD6EA86626D@oracle.com> <CADnDZ899+obhaJs9N5F3vvaKw7R--tJrNme-vpCWknx9bJx3tA@mail.gmail.com> <OFF09180C5.6763EA0F-ON85257BD3.00561D37-85257BD3.0057A0F5@csc.com> <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@mail.gmail.com>
In-Reply-To: <CAHxKQijsLiJU7F0UjKpocs=AmseknrPP5=89p_cq+WzAPgYzQQ@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: Mon, 26 Aug 2013 22:25:17 -0000

	Now I get it!!

	A Spanglish translation would be "It depends how the rides in the
carnival goes for you" ("Depende como te va en la feria")

	
/as

<sorry for the offtopic>

On 8/26/13 1:54 PM, Dave Aronson wrote:
>> As my mother used to say "What you lose on the roundabouts
>> > you gain on the swings"
> I had to go Google that.  To save others the trouble: it seems to
> refer to rides at a carnival, and mean "whatever losses you suffer in
> one place, you usually make up elsewhere", implying that it all
> balances out in the end.

From marka@isc.org  Mon Aug 26 15:25:56 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB1FD11E823E for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.189
X-Spam-Level: 
X-Spam-Status: No, score=-2.189 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, SARE_URI_DIGITS4=0.415]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rqjQzkvUFRu5 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:25:52 -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 3F4C811E823D for <ietf@ietf.org>; Mon, 26 Aug 2013 15:25:52 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 9B783C9492 for <ietf@ietf.org>; Mon, 26 Aug 2013 22:25:30 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377555951; bh=o+c4cOfFDhIVlcOIY/G386UkAbbFWT7T6+nSXEUNqQ0=; h=To:From:Subject:Date; b=N5jllAnu5LZvw3FPk5Be6wwN/wPRC7e64Ur7aFFkxkKNDUsJaJ5OWQQhx2B+hIFp+ SJ54Mqof3DGGahiVp0B3lYshitNn9XmWbY2GDvsOTP+d11Lo2zRBdyHYzOZQpLkgzM gWt6s7XTnud4kqOB4Wfi4XJoOue1I7XNDcSloOb4=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP for <ietf@ietf.org>; Mon, 26 Aug 2013 22:25:30 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 5C946160459 for <ietf@ietf.org>; Mon, 26 Aug 2013 22:26:04 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id DD7CB16043C for <ietf@ietf.org>; Mon, 26 Aug 2013 22:26:03 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id BCF5038E3A9B for <ietf@ietf.org>; Tue, 27 Aug 2013 08:25:25 +1000 (EST)
To: ietf@ietf.org
From: Mark Andrews <marka@isc.org>
Subject: Fwd: Re: [dnsext] Deprecating SPF
Date: Tue, 27 Aug 2013 08:25:25 +1000
Message-Id: <20130826222525.BCF5038E3A9B@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 22:25:56 -0000

------- Forwarded Message

To: Michael Richardson <mcr@sandelman.ca>
From: Mark Andrews <marka@isc.org>
References: <20130819222037.GA55876@mx1.yitter.info> <20130822184610.2640.qmail@joyce.lan> <CAMm+Lwj5nTOqTA8ZL7smzW2Q28ARw9NTcbHpxKY-RXZ40-7ZLA@mail.gmail.com> <20130822212337.B37A838CBDA2@drugs.dv.isc.org> <5559.1377478600@sandelman.ca>
Subject: Re: [dnsext] Deprecating SPF
In-reply-to: Your message of "Sun, 25 Aug 2013 20:56:40 -0400."
             <5559.1377478600@sandelman.ca>
Date: Tue, 27 Aug 2013 07:56:55 +1000


In message <5559.1377478600@sandelman.ca>, Michael Richardson writes:
> 
> Mark, I think that the ietf@ietf.org readers (myself included) might be
> confused by how your message about lame ccTLD delegations relates to 
> "Deprecating SPF"

Part of the reason the spf wg wants to deprecate SPF is that there
are nameservers or nameserver/loadbalancer or nameserver/firewall
combinations that drop SPF queries.  The failure to respond causes
more timeouts in processing than there are with TXT records.

These are not traditional lame delegations.  The servers still
respond the A queries.  They sometimes respond to other queries.
These two queries were done straight after each other.


; <<>> DiG 9.10.0pre-alpha <<>> cnrs-orleans.fr @admin.cnrs-orleans.fr spf +norec
;; global options: +cmd
;; connection timed out; no servers could be reached



; <<>> DiG 9.10.0pre-alpha <<>> cnrs-orleans.fr @admin.cnrs-orleans.fr a +norec
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64936
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;cnrs-orleans.fr.		IN	A

;; AUTHORITY SECTION:
cnrs-orleans.fr.	7200	IN	SOA	admin.cnrs-orleans.fr. Postmaster.cnrs-orleans.fr. 2013082001 21600 3600 3600000 7200

;; Query time: 413 msec
;; SERVER: 163.9.1.2#53(163.9.1.2)
;; WHEN: Tue Aug 27 07:55:08 EST 2013
;; MSG SIZE  rcvd: 97


Then there are the servers that don't return the correct NS RRset
and/or don't return the correct SOA record with negative answers.
Testing for NS keeps one withing the RFC 103[45] set of types.

Note the correst SOA record should be for 2957.com.  I have in the
past received email proporting to be from 2957.com which is why it
is in my test set.

; <<>> DiG 9.10.0pre-alpha <<>> 2957.com spf @ns1.dsredirection.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5484
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;2957.com.			IN	SPF

;; AUTHORITY SECTION:
com.			3600	IN	SOA	ns1.dsredirection.com. hostmaster.oversee.net. 2013060601 43200 7200 1209600 3600

;; Query time: 238 msec
;; SERVER: 204.13.160.143#53(204.13.160.143)
;; WHEN: Tue Aug 27 07:29:55 EST 2013
;; MSG SIZE  rcvd: 113

they do actually respon to the NS query though the record come from a
wildcard delegation.  Note the lack for "aa".

; <<>> DiG 9.10.0pre-alpha <<>> +norec 2957.com ns @ns1.dsredirection.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31997
;; flags: qr; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 3

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;2957.com.			IN	NS

;; ANSWER SECTION:
2957.com.		3600	IN	NS	ns1.dsredirection.com.
2957.com.		3600	IN	NS	ns2.dsredirection.com.

;; ADDITIONAL SECTION:
ns2.dsredirection.com.	7200	IN	A	204.13.161.145
ns1.dsredirection.com.	7200	IN	A	204.13.160.143

;; Query time: 183 msec
;; SERVER: 204.13.160.143#53(204.13.160.143)
;; WHEN: Tue Aug 27 07:34:51 EST 2013
;; MSG SIZE  rcvd: 119

Mark

> Mark Andrews <marka@isc.org> wrote:
>     > Part of the question is whether the IETF is going to work with ICANN,
>     > IANA and the ccTLD to audit delegations for servers that are not RFC
>     > 103[45] compliant and suspend delegations where the servers are not
>     > compliant.
> 
>     > * no responding to queries based on query type
>     > * not having a NS rrset at the delegation point
> 
>     > Enforcing that ccTLD and ICANN TLD regularly audit delegations and have
>     > mismatches corrected.  This is REQUIRED by RFC 1034 in part to stop the
>     > sorts of problems we are seeing today.
> 
>     > We don't have to put up people putting up misconfigured / broken
>     > servers.
> 
>     > For the non responding servers I have written
>     > draft-andrews-dns-no-response-issue to try to capture the issues.  It
>     > was on the dnsop agenda for Berlin but didn't get covered as time ran
>     > out.  I would like everyone to read it and comment on it.
> 
>     > Mark
>     > -- 
>     > Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia
>     > PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
- -- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

------- End of Forwarded Message

From doug.mtview@gmail.com  Mon Aug 26 15:42:40 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4112C11E8210 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, 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 rH0bGh1dK5u4 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:42:36 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 1595E11E80F5 for <ietf@ietf.org>; Mon, 26 Aug 2013 15:42:36 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so3989757pad.19 for <ietf@ietf.org>; Mon, 26 Aug 2013 15:42:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=xhPVhXl2lGVTK63FEA7hgM1M3N2b6nPo0aXIosLsErw=; b=Dd4CMk9xfyzFrs/xC5lkognpG1eDCyX3f/ldXlwo3SUYZimDKwem5VPU9MLEUeOd3M ax2sk4fcm3gkBUGMyWxsGD3yCFkeq3MfnbJhATPXndCtzK9N+1+ouwQ50yw7+zajgmWy D0LZBtJRvW9umdfGUNPPii6tBNEgTKfBcOm96RyFB+PII05oEf+FbOHLfQzaqTFhbOc4 oY5QKyPptPu12XdjTdMhMxlYJ088ryL2Q8W1/Hoqvh6SNzHAi/A8EopPLNPowyJtutSa LbGsDq9seECkt9Cbgy/p1mCEngcH8RMkYt49xt4+Acz/uhcPSgMr1/Jngp9PG/DxlT+R 3gxg==
X-Received: by 10.68.130.71 with SMTP id oc7mr17934198pbb.10.1377556955691; Mon, 26 Aug 2013 15:42:35 -0700 (PDT)
Received: from [192.168.2.247] (c-24-6-103-174.hsd1.ca.comcast.net. [24.6.103.174]) by mx.google.com with ESMTPSA id qf7sm22449970pac.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 Aug 2013 15:42:34 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0A314A68-4E20-4604-A80E-A4244CB8D752"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com>
Date: Mon, 26 Aug 2013 15:42:41 -0700
Message-Id: <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 22:42:40 -0000

--Apple-Mail=_0A314A68-4E20-4604-A80E-A4244CB8D752
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 24, 2013, at 3:16 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Doug,
> At 13:07 23-08-2013, Douglas Otis wrote:
>> The SPFbis document improperly conflates DNS terminology with =
identical terms invented by this document. Examples are terms used to =
describe mechanisms having the same identifier differentiated between =
mechanisms and DNS resource records by using lower and upper case =
respectively.  References to SPF records are differentiated by a textual =
prefix and not by TYPE as defined by DNS.
>=20
> Could you provide some examples of the above as I would like to =
clearly understand the argument?

Dear SM,

Thank you for your questions.  Sorry for the delay while helping a sick =
friend and colleague.

When the SPF document refers to "Sender Policy Framework (SPF) records" =
or "SPF records" this conflicts with DNS's record definition.  It is =
wrong to refer to these as "records".  RFC1034 defines resource records =
as TTL and RDATA that is selected by Owner (domain), Type (16 bit =
value), and Class (16 bit value).  No such selection is possible for =
SPF.   SPF uses a subclass of TXT resource records using a non-standard =
prefix that has no registry, nor is a registry practical at this point.

Terminology used by SPF sounds "as if" it refers directly to DNS =
elements.  It does not.  This poor terminology is misleading and makes =
properly expressing security concerns difficult where this confusion =
seems to be by design.

>> In addition, the MARID WG NEVER reached consensus.  A follow-on group =
operating outside of the IETF required a promise of support to subscribe =
to their mailing list.  When one looks at how SPF is commonly used, the =
pre-existing APL resource record offered an effective alternative, but =
was oppose by a particular vendor unwilling to fully implement DNS.  =
Currently this vendor is seldom used to directly interface with MTAs on =
the Internet and no longer justifies the use of the TXT records.  As =
such, the SPF Resource Record should not have been deprecated.
>=20
> There are other messages on the Last Call about the SPF Resource =
Record.  I'll take up the above together with the other comments.
>=20
>> This draft should be made Informational and not Standards Track.
>=20
> I suggest providing arguments for that.

The SPF protocol was an effort that ignored concerns expressed within =
the DNS community about the effect of overloading TXT and use of dynamic =
macro query names modified by email elements wholly unconstrained by a =
sender's infrastructure.  The SPF macro scheme can greatly amplify the =
impact of an already large number of DNS transactions.  By overloading =
TXT, updating SPF is improbable.  By rarely being the target of a DDoS =
attack, it becomes easy to speak in derogatory terms as this issue being =
the fault of DNS. =20

The primary use of SPF today is to define email outbound address space.  =
The policy aspects related to the "all" mechanism is largely ignored due =
to a high number of required exceptions.  Rather than using the existing =
APL Resource Record in the form of _email.<domain> APL <CIDRs> in binary =
form, the group devised a macro language to authorize various email =
elements using text to accommodate a vendor that since became =
practically irrelevant for Internet email exchange.  Although most large =
providers now ignore SPF macros, very few domains publish them as well.  =
Macros interfere with a provider's effort at mapping a domain's address =
space.  Most consider the authorization for email-address local parts =
the sender's role.  Nevertheless, the WG failed to warn of this issue by =
either deprecating or advising against macro publication.  Macros =
inhibit effective caching, imperil SMTP server security, and degrade =
interchange. This is not a good candidate for standardization if this =
category is expected to retain any value or the IETF is to offer helpful =
guidance.

Simply because SPF did not stipulate DNSSEC does not mean DNSSEC can be =
ignored.  Not considering DNSSEC is an example of a failed =
consideration.  Must the world wait for SPF to change before DNSSEC can =
be safely deployed?  Overloading of TXT resource records at the zone =
apex along with macro scripts able to leverage email elements to direct =
reflected attacks from cached resource records is an example why this =
document should not be deemed a standard.=20

>> Section 4.6.4 fails to offer a sufficiently clear warning about =
potential magnitudes of DNS transactions initiated by a single SPF =
evaluation where two are recommended to occur one for the separate =
identifiers.  In fact, this section appears to make assurances no more =
that 10 DNS queries will result and is widely misunderstood.
>=20
> There is a discussion about Section 4.6.4 at =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html

There is a trend by large providers to switch over to using wildcards on =
enormous networks to track users instead of using cookies.  The impact =
this has on the past conversations is enormous.  This eliminates the =
effect of the void response limit while also increasing the amount of =
the resulting traffic.

  <random-string>cdr-ds.metric.gstatic.com
 <random-string>.g.vm.akamaistream.net

>> 4.6.4.  DNS Lookup Limits
>>=20
>> Was:
>> ,--
>> SPF implementations MUST limit the total number of mechanisms and
>> modifiers ("terms") that cause any DNS query to 10 during SPF
>> evaluation.
>> '--
>>=20
>> Change to:
>> ,---
>> SPF evaluation must limit the number of mechanisms, and the modifier
>> term 'redirect' to occur in no more than10 instances within the
>> evaluation process.  The mechanisms 'ip4', ip6', and 'all' are
>> excluded from this instance limitation.  Each mechanism is permitted
>> to resolve subsequent resource record sets (RRsets) that MUST not
>> contain more than 10 resource records to complete a match check.
>> When the number of instances exceeds 10, or when subsequent
>> resolutions exceeds 10, check_host() MUST produce a "permerror"
>> result.
>>=20
>> The maximum number of DNS transactions initiated by an SPF
>> evaluation is therefore 1 for the initial SPF resource record, 10 for
>> each mechanism times 10 transactions needed to complete a matching
>> process for a total of 111 DNS transactions.  This number excludes
>> those required by DNS to fulfill a request and those required by an
>> EXP modifier.
>=20
> I'll list the above as not addressed yet.

Please also note that the PTR RR is not constrained in the current =
specification and can create erratic results.  It would be far safer to =
Perm error when overflowing on the number of PTR records.  There is no =
upper limit as some represent web farms hosting thousands of domains.=20

>=20
>> The recommended 20 second evaluation timeout imposes a maximum
>> network distance of less than 27,000 kilometers or a little more than
>> half the circumference of the Earth.  Even a 60 millisecond delay can
>> result in more than a 6.6 seconds consumed by the round trip
>> overhead needed for each SPF evaluation.
>=20
> During the WGLC Murray Kucherawy asked a question about the 20 second =
evaluation timeout ( =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03700.html ).  =
The answer was that the timeout is already in RFC 4408.

This timeout is not likely problematic after ensuring against macros =
where then caching can be effective at overcoming this constraint.

>> The overall resulting maximum number of DNS transactions for
>> both "HELO" and "MAIL FROM" is 222 DNS transactions.  Since
>> check_host() introduces macros and name expansions that
>> combine mechanisms and modifiers in a manner not directly
>> supported by DNS, the entire set and sequence of SPF based
>> DNS transactions is required for each evaluation.  While SPF now
>> has a 2 limit of void lookups, use of synthetic domains has become
>> a popular technique for tracking traffic which can be used by
>> malefactors to overcome this SPF void lookup limit.
>=20
> The draft agenda for the IETF 83 session was posted to the SPFBIS =
mailing list on March 14, 2012. One of the items on that agenda was "DNS =
amplification attacks" ( =
http://www.ietf.org/mail-archive/web/spfbis/current/msg01021.html ).  It =
would have been good more discussion of the issue (Issue #24) from a DNS =
perspective.  As there has been numerous comments about the DNS angle =
during this Last Call, maybe an IETF participant will be able to provide =
some input about the above.
>=20
>> Once DNSsec becomes a requirement, SPF will have created an
>> inordinate number of transactions and overall traffic per message
>> exchange that will impose a SIGNIFICANT reflected amplification risk.
>=20
> draft-ietf-spfbis-4408bis-19 does not have any DNSSEC requirement.

That does not mean DNSSEC will not be used.  One hopes just the opposite =
is true.

>> Related information:
>>=20
>> <random-string>cdr-ds.metric.gstatic.com
>> <random-string>.g.vm.akamaistream.net
>> are domains on sizable networks that act as a wildcards.  In the =
second instance, the wildcard points to a CNAME that then resolves an A =
record.  Such use compared against =
http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01 produces a much =
larger amplification than the x320 gain estimated.  Use of DNSsec =
further increases this gain estimate.  Although details differ from case =
to case, the synthetic domain technique is seeing greater use.  One of =
the initial reasons for using TXT records without any prefix was to =
permit use of wildcards.  This dangerous feature means SPF allows =
malefactors to leverage any large TXT resource record that otherwise =
would not have been problematic.  Again this risk increases when DNSsec =
becomes required and represents another reason for not deprecating the =
SPF resource record type.
>=20
> I welcome comments from other IETF participants about the above.
>=20
>> Remove this misleading paragraph within section 4.6.4:
>> ,---
>> When evaluating the "mx" mechanism, the number of "MX" resource
>> records queried is included in the overall limit of 10 mechanisms/
>> modifiers that cause DNS lookups described above.  The evaluation of
>> each "MX" record MUST NOT result in querying more than 10 address
>> records, either "A" or "AAAA" resource records.  If this limit is
>> exceeded, the "mx" mechanism MUST produce a "permerror" result.
>> '---
>>=20
>> MX resource records do not contain IP addresses.
>> Per RFC1035 the structure for an MX record is roughly as follows:
>>=20
>> A 16 bit PREFERENCE (distance) value followed by an MTA hostname.
>>=20
>> A DNS MX reply may offer A records for the hostnames in the =
Additional Section however per:
>> Per RFC2181 Section 5.4:
>> ,---
>> Servers must never merge RRs from a response with RRs in their
>> cache to form an RRSet.  If a response contains data that would form
>> an RRSet with data in a server's cache the server must either ignore
>> the RRs in the response, or discard the entire RRSet currently in the
>> cache, as appropriate.
>> '---
>>=20
>> This will not prove ideal for SPF with respect to effective use of =
DNS.
>>=20
>> Also hostnames contained within MX resource record might be within =
any domain, and not necessarily the same domain as that of the base SPF =
record.
>>=20
>> Per RFC2181 5.4.1. Ranking data
>> An authoritative answer from a reply should replace cached data that =
had been obtained from additional information in an earlier reply. =
However additional information from a reply will be ignored if the cache =
contains data from an authoritative answer or a zone file.
>=20
> I agree that MX resource records do not contain IP addresses.  There =
is a thread at =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html about =
reasonable DNS error limits.  I could not spot the problem in the =
paragraph that is described as misleading.  An example to illustrate the =
problem might make it clearer.
>=20
>> Mistake.
>>=20
>> Section 3.4
>>=20
>> Second paragraph:
>>=20
>> Similarly, the sizes for replies to all queries related to SPF have =
to be evaluated to fit in a single 512 octet UDP packet.
>>=20
>> s/UDP packet/DNS message/
>=20
> My understanding of the working group discussion is that the intent is =
to have the DNS reply fit within a UDP packet.

The permitted size of the UDP packet is NOT 512 octets.  That is the =
permitted size of the DNS Message.  DNS Message is not the same thing as =
a UDP packet.

>=20
>> Per RFC1035
>> Section 2.3.4. Size limits
>> UDP messages    512 octets or less
>>=20
>>=20
>> Section 4.2.1. UDP usage
>> Messages carried by UDP are restricted to 512 bytes (not counting the =
IP or UDP headers).
>>=20
>> The DNS message size limitation is not the same as a UDP packet limit =
as suggested in Section 3.4.
>=20
> I am not sure whether the above refers to the "450 octets".  I'll note =
a comment from Andrew Sullivan ( =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03103.html ) so =
that I don't have to search for it again.

A reduction to 450 octets would be a reasonable recommendation for the =
DNS _message_, not the UDP _packet_.  The packet still needs to carry =
the IP and UDP headers.

>> The SPFbis WG charter permitted removal of unused protocol elements =
where the "ptr" mechanism was deprecated and the SPF resource type was =
removed. Use of SPF's very dangerous macro feature currently has less =
than 0.053% of the domains making use of these macros and clearly falls =
below the WG removal threshold.  We have also been told by a few very =
large providers that SPF records containing any macro reference are =
ignored for reasons related to both efficiency and security.  Marcos =
also inhibit the primary use by large providers which is to compile the =
domain's IP address list.
>=20
> There was an appeal about the meaning of the word "unused" ( =
http://www.ietf.org/mail-archive/web/spfbis/current/msg02167.html ).  =
I'll highlight a comment from Pete Resnick:
>=20
>  "There's also the comment from Doug Otis about the local-part
>   macro. I'm inclined to declare that out of scope, maybe after a
>   recharter. That's not documenting current practice, but is an overt
>   change."
>=20
> There are some threads about local part macros:
>=20
> http://www.ietf.org/mail-archive/web/spfbis/current/msg00911.html
> http://www.ietf.org/mail-archive/web/spfbis/current/msg01870.html
>=20
> There is a short thread and a few other threads about the "ptr" =
mechanism ( =
http://www.ietf.org/mail-archive/web/spfbis/current/msg00808.html =
http://www.ietf.org/mail-archive/web/spfbis/current/msg00811.html =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03184.html ).
>=20
> There is the following text in the write-up:
>=20
>   "There was some controversy about whether the use of macros was a
>    security risk and whether to deprecate the PTR feature.  There was =
a
>    formal appeal of the SPFBIS WG chair' interpretation of the =
charter,
>    specifically regarding the removal of "unused" features.  The two
>    features in particular which drove the appeal were the PTR feature
>    and the local-part macro feature.  These features were not removed
>    from the document given that the appeal was denied by the =
Responsible
>    Area Director."

There should be some type of warning at minimum as the macro issue is =
likely to affect interchange now and going forward.  The IETF should not =
consider protocols outside larger concerns of the well being of the =
Internet infrastructure and proper interchange.  This issue should not =
be controversial. =20

Regards,
Douglas Otis


>=20
> I hope that the above explains the decision.
>=20
>> The WG should have been told to focus on security and at better =
insuring interchange to achieve a safer stance moving forward.
>=20
> The working group was reminded about BCP 72.
>=20
> Regards,
> S. Moonesamy (as document shepherd)=20


--Apple-Mail=_0A314A68-4E20-4604-A80E-A4244CB8D752
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 24, 2013, at 3:16 AM, S Moonesamy &lt;<a =
href=3D"mailto:sm+ietf@elandsys.com">sm+ietf@elandsys.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Hi Doug,<br>At 13:07 23-08-2013, Douglas Otis =
wrote:<br><blockquote type=3D"cite">The SPFbis document improperly =
conflates DNS terminology with identical terms invented by this =
document. Examples are terms used to describe mechanisms having the same =
identifier differentiated between mechanisms and DNS resource records by =
using lower and upper case respectively. &nbsp;References to SPF records =
are differentiated by a textual prefix and not by TYPE as defined by =
DNS.<br></blockquote><br>Could you provide some examples of the above as =
I would like to clearly understand the =
argument?<br></blockquote><div><br></div><div>Dear =
SM,</div><div><br></div><div>Thank you for your questions. &nbsp;Sorry =
for the delay while helping a sick friend and =
colleague.</div><div><br></div><div>When the SPF document refers to =
"Sender Policy Framework (SPF) records" or "SPF records" this conflicts =
with DNS's record definition. &nbsp;It is wrong to refer to these as =
"records". &nbsp;RFC1034 defines resource records as TTL and RDATA that =
is selected by Owner (domain), Type (16 bit value), and Class (16 bit =
value). &nbsp;No such selection is possible for SPF. &nbsp; SPF uses a =
subclass of TXT resource records using a non-standard prefix that has no =
registry, nor is a registry practical at this =
point.</div><div><br></div><div>Terminology used by SPF sounds "as if" =
it refers directly to DNS elements. &nbsp;It does not. &nbsp;This poor =
terminology is misleading and makes properly expressing security =
concerns difficult where this confusion seems to be by =
design.</div><br><blockquote type=3D"cite"><blockquote type=3D"cite">In =
addition, the MARID WG NEVER reached consensus. &nbsp;A follow-on group =
operating outside of the IETF required a promise of support to subscribe =
to their mailing list. &nbsp;When one looks at how SPF is commonly used, =
the pre-existing APL resource record offered an effective alternative, =
but was oppose by a particular vendor unwilling to fully implement DNS. =
&nbsp;Currently this vendor is seldom used to directly interface with =
MTAs on the Internet and no longer justifies the use of the TXT records. =
&nbsp;As such, the SPF Resource Record should not have been =
deprecated.<br></blockquote><br>There are other messages on the Last =
Call about the SPF Resource Record. &nbsp;I'll take up the above =
together with the other comments.</blockquote><blockquote =
type=3D"cite"><br><blockquote type=3D"cite">This draft should be made =
Informational and not Standards Track.<br></blockquote><br>I suggest =
providing arguments for that.<br></blockquote><div><br></div><div>The =
SPF protocol was an effort that ignored concerns expressed within the =
DNS community about the effect of overloading TXT and use of dynamic =
macro&nbsp;query names modified by email elements wholly unconstrained =
by a sender's infrastructure. &nbsp;The SPF macro scheme can greatly =
amplify the impact of&nbsp;an already large number of DNS transactions. =
&nbsp;By overloading TXT, updating SPF is improbable.&nbsp;&nbsp;By =
rarely being the target of a DDoS attack, it becomes easy to speak in =
derogatory terms as this issue being the fault of DNS. =
&nbsp;</div><div><br></div><div>The primary use of SPF today is to =
define email outbound address space. &nbsp;The policy aspects related to =
the "all" mechanism is largely ignored due to a high number of required =
exceptions. &nbsp;Rather than using the existing APL Resource Record in =
the form of _email.&lt;domain&gt; APL &lt;CIDRs&gt; in binary form, the =
group devised a macro language to authorize various email elements using =
text to accommodate a vendor that since became practically irrelevant =
for Internet email exchange. &nbsp;Although most large providers now =
ignore SPF macros, very few domains publish them as well. &nbsp;Macros =
interfere with a provider's effort at mapping a domain's address space. =
&nbsp;Most consider the authorization for email-address local parts the =
sender's role. &nbsp;Nevertheless, the WG failed to warn of this issue =
by either deprecating or advising against macro publication. =
&nbsp;Macros inhibit effective caching, imperil SMTP server security, =
and degrade interchange. This is not a good candidate for =
standardization if this category is expected to retain any value or the =
IETF is to offer helpful guidance.</div><div><br></div><div>Simply =
because SPF did not stipulate DNSSEC does not mean DNSSEC can be =
ignored. &nbsp;Not considering DNSSEC is an example of a failed =
consideration. &nbsp;Must the world wait for SPF to change before DNSSEC =
can be safely deployed? &nbsp;Overloading of TXT resource records at the =
zone apex along with macro scripts able to leverage email elements to =
direct reflected attacks from cached resource records is an example why =
this document should not be deemed a =
standard.&nbsp;</div><br><blockquote type=3D"cite"><blockquote =
type=3D"cite">Section 4.6.4 fails to offer a sufficiently clear warning =
about potential magnitudes of DNS transactions initiated by a single SPF =
evaluation where two are recommended to occur one for the separate =
identifiers. &nbsp;In fact, this section appears to make assurances no =
more that 10 DNS queries will result and is widely =
misunderstood.<br></blockquote><br>There is a discussion about Section =
4.6.4 at <a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html</a><br>=
</blockquote><div><br></div><div>There is a trend by large providers to =
switch over to using wildcards on enormous networks to track users =
instead of using cookies. &nbsp;The impact this has on the past =
conversations is enormous. &nbsp;This eliminates the effect of the void =
response limit while also increasing the amount of the resulting =
traffic.</div><div><br></div><div><span style=3D"letter-spacing: 0px; =
">&nbsp;&nbsp;</span><span style=3D"letter-spacing: 0px; font-family: =
Monaco; font-size: 11px; ">&lt;random-string&gt;</span><a =
href=3D"http://cdr-ds.metric.gstatic.com/" style=3D"letter-spacing: 0px; =
font-family: Monaco; font-size: 11px; =
">cdr-ds.metric.gstatic.com</a></div><div style=3D"margin: 0px; =
font-size: 11px; font-family: Monaco; "><span style=3D"letter-spacing: =
0px; ">&nbsp;&lt;random-string&gt;.<a =
href=3D"http://g.vm.akamaistream.net/">g.vm.akamaistream.net</a></span></d=
iv><div style=3D"margin: 0px; font-size: 11px; font-family: Monaco; =
"><br></div><blockquote type=3D"cite"><blockquote type=3D"cite">4.6.4. =
&nbsp;DNS Lookup Limits<br><br>Was:<br>,--<br>SPF implementations MUST =
limit the total number of mechanisms and<br>modifiers ("terms") that =
cause any DNS query to 10 during SPF<br>evaluation.<br>'--<br><br>Change =
to:<br>,---<br>SPF evaluation must limit the number of mechanisms, and =
the modifier<br>term 'redirect' to occur in no more than10 instances =
within the<br>evaluation process. &nbsp;The mechanisms 'ip4', ip6', and =
'all' are<br>excluded from this instance limitation. &nbsp;Each =
mechanism is permitted<br>to resolve subsequent resource record sets =
(RRsets) that MUST not<br>contain more than 10 resource records to =
complete a match check.<br>When the number of instances exceeds 10, or =
when subsequent<br>resolutions exceeds 10, check_host() MUST produce a =
"permerror"<br>result.<br><br>The maximum number of DNS transactions =
initiated by an SPF<br>evaluation is therefore 1 for the initial SPF =
resource record, 10 for<br>each mechanism times 10 transactions needed =
to complete a matching<br>process for a total of 111 DNS transactions. =
&nbsp;This number excludes<br>those required by DNS to fulfill a request =
and those required by an<br>EXP modifier.<br></blockquote><br>I'll list =
the above as not addressed =
yet.<br></blockquote><div><br></div><div>Please also note that the PTR =
RR is not constrained in the current specification and can create =
erratic results. &nbsp;It would be far safer to Perm error when =
overflowing on the number of PTR records. &nbsp;There is no upper limit =
as some represent web farms hosting thousands of =
domains.&nbsp;</div><br><blockquote type=3D"cite"><br><blockquote =
type=3D"cite">The recommended 20 second evaluation timeout imposes a =
maximum<br>network distance of less than 27,000 kilometers or a little =
more than<br>half the circumference of the Earth. &nbsp;Even a 60 =
millisecond delay can<br>result in more than a 6.6 seconds consumed by =
the round trip<br>overhead needed for each SPF =
evaluation.<br></blockquote><br>During the WGLC Murray Kucherawy asked a =
question about the 20 second evaluation timeout ( <a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg03700.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg03700.html</a> =
). &nbsp;The answer was that the timeout is already in RFC =
4408.<br></blockquote><div><br></div><div>This timeout is not likely =
problematic after ensuring against macros where then caching can be =
effective at overcoming this constraint.</div><br><blockquote =
type=3D"cite"><blockquote type=3D"cite">The overall resulting maximum =
number of DNS transactions for<br>both "HELO" and "MAIL FROM" is 222 DNS =
transactions. &nbsp;Since<br>check_host() introduces macros and name =
expansions that<br>combine mechanisms and modifiers in a manner not =
directly<br>supported by DNS, the entire set and sequence of SPF =
based<br>DNS transactions is required for each evaluation. &nbsp;While =
SPF now<br>has a 2 limit of void lookups, use of synthetic domains has =
become<br>a popular technique for tracking traffic which can be used =
by<br>malefactors to overcome this SPF void lookup =
limit.<br></blockquote><br>The draft agenda for the IETF 83 session was =
posted to the SPFBIS mailing list on March 14, 2012. One of the items on =
that agenda was "DNS amplification attacks" ( <a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg01021.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg01021.html</a> =
). &nbsp;It would have been good more discussion of the issue (Issue =
#24) from a DNS perspective. &nbsp;As there has been numerous comments =
about the DNS angle during this Last Call, maybe an IETF participant =
will be able to provide some input about the above.<br><br><blockquote =
type=3D"cite">Once DNSsec becomes a requirement, SPF will have created =
an<br>inordinate number of transactions and overall traffic per =
message<br>exchange that will impose a SIGNIFICANT reflected =
amplification risk.<br></blockquote><br>draft-ietf-spfbis-4408bis-19 =
does not have any DNSSEC =
requirement.<br></blockquote><div><br></div><div>That does not mean =
DNSSEC will not be used. &nbsp;One hopes just the opposite is =
true.</div><div><br></div><blockquote type=3D"cite"><blockquote =
type=3D"cite">Related information:<br><br>&lt;random-string&gt;<a =
href=3D"http://cdr-ds.metric.gstatic.com">cdr-ds.metric.gstatic.com</a><br=
>&lt;random-string&gt;.<a =
href=3D"http://g.vm.akamaistream.net">g.vm.akamaistream.net</a><br>are =
domains on sizable networks that act as a wildcards. &nbsp;In the second =
instance, the wildcard points to a CNAME that then resolves an A record. =
&nbsp;Such use compared against <a =
href=3D"http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01">http://t=
ools.ietf.org/html/draft-otis-spf-dos-exploit-01</a> produces a much =
larger amplification than the x320 gain estimated. &nbsp;Use of DNSsec =
further increases this gain estimate. &nbsp;Although details differ from =
case to case, the synthetic domain technique is seeing greater use. =
&nbsp;One of the initial reasons for using TXT records without any =
prefix was to permit use of wildcards. &nbsp;This dangerous feature =
means SPF allows malefactors to leverage any large TXT resource record =
that otherwise would not have been problematic. &nbsp;Again this risk =
increases when DNSsec becomes required and represents another reason for =
not deprecating the SPF resource record type.<br></blockquote><br>I =
welcome comments from other IETF participants about the =
above.<br><br><blockquote type=3D"cite">Remove this misleading paragraph =
within section 4.6.4:<br>,---<br>When evaluating the "mx" mechanism, the =
number of "MX" resource<br>records queried is included in the overall =
limit of 10 mechanisms/<br>modifiers that cause DNS lookups described =
above. &nbsp;The evaluation of<br>each "MX" record MUST NOT result in =
querying more than 10 address<br>records, either "A" or "AAAA" resource =
records. &nbsp;If this limit is<br>exceeded, the "mx" mechanism MUST =
produce a "permerror" result.<br>'---<br><br>MX resource records do not =
contain IP addresses.<br>Per RFC1035 the structure for an MX record is =
roughly as follows:<br><br>A 16 bit PREFERENCE (distance) value followed =
by an MTA hostname.<br><br>A DNS MX reply may offer A records for the =
hostnames in the Additional Section however per:<br>Per RFC2181 Section =
5.4:<br>,---<br>Servers must never merge RRs from a response with RRs in =
their<br>cache to form an RRSet. &nbsp;If a response contains data that =
would form<br>an RRSet with data in a server's cache the server must =
either ignore<br>the RRs in the response, or discard the entire RRSet =
currently in the<br>cache, as appropriate.<br>'---<br><br>This will not =
prove ideal for SPF with respect to effective use of DNS.<br><br>Also =
hostnames contained within MX resource record might be within any =
domain, and not necessarily the same domain as that of the base SPF =
record.<br><br>Per RFC2181 5.4.1. Ranking data<br>An authoritative =
answer from a reply should replace cached data that had been obtained =
from additional information in an earlier reply. However additional =
information from a reply will be ignored if the cache contains data from =
an authoritative answer or a zone file.<br></blockquote><br>I agree that =
MX resource records do not contain IP addresses. &nbsp;There is a thread =
at <a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg03305.html</a> =
about reasonable DNS error limits. &nbsp;I could not spot the problem in =
the paragraph that is described as misleading. &nbsp;An example to =
illustrate the problem might make it clearer.<br><br><blockquote =
type=3D"cite">Mistake.<br><br>Section 3.4<br><br>Second =
paragraph:<br><br>Similarly, the sizes for replies to all queries =
related to SPF have to be evaluated to fit in a single 512 octet UDP =
packet.<br><br>s/UDP packet/DNS message/<br></blockquote><br>My =
understanding of the working group discussion is that the intent is to =
have the DNS reply fit within a UDP =
packet.<br></blockquote><div><br></div><div>The permitted size of the =
UDP packet is NOT 512 octets. &nbsp;That is the permitted size of the =
DNS Message. &nbsp;DNS Message is not the same thing as a UDP =
packet.</div><br><blockquote type=3D"cite"><br><blockquote =
type=3D"cite">Per RFC1035<br>Section 2.3.4. Size limits<br>UDP messages =
&nbsp;&nbsp;&nbsp;512 octets or less<br><br><br>Section 4.2.1. UDP =
usage<br>Messages carried by UDP are restricted to 512 bytes (not =
counting the IP or UDP headers).<br><br>The DNS message size limitation =
is not the same as a UDP packet limit as suggested in Section =
3.4.<br></blockquote><br>I am not sure whether the above refers to the =
"450 octets". &nbsp;I'll note a comment from Andrew Sullivan ( <a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg03103.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg03103.html</a> ) =
so that I don't have to search for it =
again.<br></blockquote><div><br></div><div>A reduction to 450 octets =
would be a reasonable recommendation for the DNS _message_, not the UDP =
_packet_. &nbsp;The packet still needs to carry the IP and UDP =
headers.</div><div><br></div><blockquote type=3D"cite"><blockquote =
type=3D"cite">The SPFbis WG charter permitted removal of unused protocol =
elements where the "ptr" mechanism was deprecated and the SPF resource =
type was removed. Use of SPF's very dangerous macro feature currently =
has less than 0.053% of the domains making use of these macros and =
clearly falls below the WG removal threshold. &nbsp;We have also been =
told by a few very large providers that SPF records containing any macro =
reference are ignored for reasons related to both efficiency and =
security. &nbsp;Marcos also inhibit the primary use by large providers =
which is to compile the domain's IP address =
list.<br></blockquote><br>There was an appeal about the meaning of the =
word "unused" ( <a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg02167.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg02167.html</a> =
). &nbsp;I'll highlight a comment from Pete Resnick:<br><br> =
&nbsp;"There's also the comment from Doug Otis about the local-part<br> =
&nbsp;&nbsp;macro. I'm inclined to declare that out of scope, maybe =
after a<br> &nbsp;&nbsp;recharter. That's not documenting current =
practice, but is an overt<br> &nbsp;&nbsp;change."<br><br>There are some =
threads about local part macros:<br><br><a =
href=3D"http://www.ietf.org/mail-archive/web/spfbis/current/msg00911.html"=
>http://www.ietf.org/mail-archive/web/spfbis/current/msg00911.html</a><br>=
http://www.ietf.org/mail-archive/web/spfbis/current/msg01870.html<br><br>T=
here is a short thread and a few other threads about the "ptr" mechanism =
( http://www.ietf.org/mail-archive/web/spfbis/current/msg00808.html =
http://www.ietf.org/mail-archive/web/spfbis/current/msg00811.html =
http://www.ietf.org/mail-archive/web/spfbis/current/msg03184.html =
).<br><br>There is the following text in the write-up:<br><br> =
&nbsp;&nbsp;"There was some controversy about whether the use of macros =
was a<br> &nbsp;&nbsp;&nbsp;security risk and whether to deprecate the =
PTR feature. &nbsp;There was a<br> &nbsp;&nbsp;&nbsp;formal appeal of =
the SPFBIS WG chair' interpretation of the charter,<br> =
&nbsp;&nbsp;&nbsp;specifically regarding the removal of "unused" =
features. &nbsp;The two<br> &nbsp;&nbsp;&nbsp;features in particular =
which drove the appeal were the PTR feature<br> &nbsp;&nbsp;&nbsp;and =
the local-part macro feature. &nbsp;These features were not removed<br> =
&nbsp;&nbsp;&nbsp;from the document given that the appeal was denied by =
the Responsible<br> &nbsp;&nbsp;&nbsp;Area =
Director."<br></blockquote><div><br></div><div>There should be some type =
of warning at minimum as the macro issue is likely to affect interchange =
now and going forward. &nbsp;The IETF should not consider protocols =
outside larger concerns of the well being of the Internet infrastructure =
and proper interchange. &nbsp;This issue should not be controversial. =
&nbsp;</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><br><blockquote type=3D"cite"><br>I hope that =
the above explains the decision.<br><br><blockquote type=3D"cite">The WG =
should have been told to focus on security and at better insuring =
interchange to achieve a safer stance moving =
forward.<br></blockquote><br>The working group was reminded about BCP =
72.<br><br>Regards,<br>S. Moonesamy (as document shepherd) =
<br></blockquote></div><br></body></html>=

--Apple-Mail=_0A314A68-4E20-4604-A80E-A4244CB8D752--

From scott@kitterman.com  Mon Aug 26 15:48:27 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C79B111E80F7 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:48: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 X8Okk+FG7XfZ for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 15:48:06 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id E2FE711E8248 for <ietf@ietf.org>; Mon, 26 Aug 2013 15:48:05 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 4317820E40F6; Mon, 26 Aug 2013 18:48:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377557285; bh=lr69s2Iut5swtvMaYM7SvKvuZgaFPgYtFv9ad/ZyzBY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lBgEVZGRYnGFIs3FkS4gOk40CBT8Oc7sDxcMk8C+/u0xJt7k+yBwjy14sO3lu4gkv zGbNGRIVWf1YOdTgeExgzReiIasyfzCTDwgzx7CWpnP+fAHqn2x/aUROBgg+EWTYVB rXdSPMIzzfMRsy6BYWoeMCAaimVZMo95HThqeYKk=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 2D14520E4043;  Mon, 26 Aug 2013 18:48:04 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Mon, 26 Aug 2013 18:48:04 -0400
Message-ID: <1973922.OgEpFZ84lJ@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 22:48:27 -0000

On Monday, August 26, 2013 15:42:41 Douglas Otis wrote:
> Please also note that the PTR RR is not constrained in the current
> specification and can create erratic results.  It would be far safer to
> Perm error when overflowing on the number of PTR records.  There is no
> upper limit as some represent web farms hosting thousands of domains. 

This exact issue was the subject of working group discussion.  Since the 
number of PTR records is an attribute of the connect IP, it is under the 
control of the sending party, not the domain owner.  A cap that resulted in an 
error would, as a result, enable the sender to arbitrarily get an SPF 
permerror in place of a fail if desired.  The WG considered that not a good 
idea.

Scott K

From doug.mtview@gmail.com  Mon Aug 26 16:28:24 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1BB11E8226 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvHFLEWc9zHs for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:28:07 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id CDFB711E820D for <ietf@ietf.org>; Mon, 26 Aug 2013 16:28:07 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id up15so4022531pbc.40 for <ietf@ietf.org>; Mon, 26 Aug 2013 16:28:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1k4p8MgcfqZq+Bh3XBatEask6P9o7DuHYk77zYM/R+Y=; b=ytQtjhibfJCpLH+j/CvVGTVn8d0qCrLj1gbSKWLpnRqpr7ROWBhVYx3EmmRne486+2 WdJ5Mk3f3xTnULnkJ7FEOXsISSnbBq0ZFZccthzLMgApFrTMFLY2dR+CDrYO31JcJxkn 082fSRQ67Wvoc9ih47mKAXH8lmbWRwQx66Lu8uzIHOVu3R41f4ZkD+noIxNxUqtfTX37 nQGyTznutji5HdZVhaCCFTylFIMKUF9z0aHnwzzel/gJcWrySDiol+fIZhsx7bHugQFI +QCJr4HmaR5hcEP9/e5OHumc/DhK378XS3c/w0lgLgnJq7n2sbFUNfEhFMfVTo+aeacY R/iA==
X-Received: by 10.68.244.73 with SMTP id xe9mr17732825pbc.119.1377559686536; Mon, 26 Aug 2013 16:28:06 -0700 (PDT)
Received: from [192.168.2.247] (c-24-6-103-174.hsd1.ca.comcast.net. [24.6.103.174]) by mx.google.com with ESMTPSA id kd1sm22599477pab.20.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 Aug 2013 16:28:05 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <1973922.OgEpFZ84lJ@scott-latitude-e6320>
Date: Mon, 26 Aug 2013 16:28:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE72B4FF-2948-4EB4-9A91-D026FC493B4F@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <1973922.OgEpFZ84lJ@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 23:28:24 -0000

On Aug 26, 2013, at 3:48 PM, Scott Kitterman <scott@kitterman.com> =
wrote:

> On Monday, August 26, 2013 15:42:41 Douglas Otis wrote:
>> Please also note that the PTR RR is not constrained in the current
>> specification and can create erratic results.  It would be far safer =
to
>> Perm error when overflowing on the number of PTR records.  There is =
no
>> upper limit as some represent web farms hosting thousands of domains.=20=

>=20
> This exact issue was the subject of working group discussion.  Since =
the=20
> number of PTR records is an attribute of the connect IP, it is under =
the=20
> control of the sending party, not the domain owner.  A cap that =
resulted in an=20
> error would, as a result, enable the sender to arbitrarily get an SPF=20=

> permerror in place of a fail if desired.  The WG considered that not a =
good=20
> idea.


Dear Scott,

It is within the control of the Domain owner about whether to make use =
of the ptr mechanism in their SPF TXT.  Random ordering or responses is =
also controlled by the IP address owner and not the Domain owner.  The =
ptr mechanism may offer intermittent results that will be difficult to =
troubleshoot.  By offering a Perm error on a ptr overflow, the domain =
owner is quickly notified this mechanism should not be used and are not =
fooled by it working some of the time.  The greater concern is in regard =
to the over all response sizes when DNSSEC is used.  In that case, =
response sizes can grow significantly.  Allowing large responses to =
occur without producing an error seems like a risky strategy from the =
DDoS perspective.  That is also another reason for worrying about the =
use of TXT RRs.  How many large wildcard TXT RR exist, and if they do, =
who would be at fault when this becomes a problem for SPF?

Regards,
Douglas Otis



From scott@kitterman.com  Mon Aug 26 16:29:43 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF4221F9655 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 AGpau2UKlVC7 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:29:38 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id D55C611E820D for <ietf@ietf.org>; Mon, 26 Aug 2013 16:29:38 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 50BF620E40F6; Mon, 26 Aug 2013 19:29:38 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377559778; bh=+t2jAtIQe2+bIwXayslk2gGeGl1XJwTxkwnRghZvUcs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hM/ba7nxDBsAVPIb/YUjTkvBAjLN/LQAk+4/RBiqqDhlUnL4hkMpXn2dM3BRtzU/K qLppcEP33wqoAOHgDDsDDBL2W61rJayJgNAgCFRlvXF4qGc1Rv1xoscmd07UErfa2U 7CI80NYOz4Uor7OdQDr2rd/Ee4U+N4G66TA1fMl8=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 3962620E4043;  Mon, 26 Aug 2013 19:29:37 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Mon, 26 Aug 2013 19:29:36 -0400
Message-ID: <5564260.oH8aR0Fh9U@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <BE72B4FF-2948-4EB4-9A91-D026FC493B4F@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <1973922.OgEpFZ84lJ@scott-latitude-e6320> <BE72B4FF-2948-4EB4-9A91-D026FC493B4F@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 23:29:44 -0000

On Monday, August 26, 2013 16:28:03 Douglas Otis wrote:
> On Aug 26, 2013, at 3:48 PM, Scott Kitterman <scott@kitterman.com> wrote:
> > On Monday, August 26, 2013 15:42:41 Douglas Otis wrote:
> >> Please also note that the PTR RR is not constrained in the current
> >> specification and can create erratic results.  It would be far safer to
> >> Perm error when overflowing on the number of PTR records.  There is no
> >> upper limit as some represent web farms hosting thousands of domains.
> > 
> > This exact issue was the subject of working group discussion.  Since the
> > number of PTR records is an attribute of the connect IP, it is under the
> > control of the sending party, not the domain owner.  A cap that resulted
> > in an error would, as a result, enable the sender to arbitrarily get an
> > SPF permerror in place of a fail if desired.  The WG considered that not
> > a good idea.
> 
> Dear Scott,
> 
> It is within the control of the Domain owner about whether to make use of
> the ptr mechanism in their SPF TXT.  Random ordering or responses is also
> controlled by the IP address owner and not the Domain owner.  The ptr
> mechanism may offer intermittent results that will be difficult to
> troubleshoot.  By offering a Perm error on a ptr overflow, the domain owner
> is quickly notified this mechanism should not be used and are not fooled by
> it working some of the time.  The greater concern is in regard to the over
> all response sizes when DNSSEC is used.  In that case, response sizes can
> grow significantly.  Allowing large responses to occur without producing an
> error seems like a risky strategy from the DDoS perspective.  That is also
> another reason for worrying about the use of TXT RRs.  How many large
> wildcard TXT RR exist, and if they do, who would be at fault when this
> becomes a problem for SPF?

Your conclusion is different than the one the working group reached.

Scott K

From doug.mtview@gmail.com  Mon Aug 26 16:32:29 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0458B11E8257 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VnxxmQi7J7ag for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:32:28 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 82E8F11E824E for <ietf@ietf.org>; Mon, 26 Aug 2013 16:32:28 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id p10so4052278pdj.4 for <ietf@ietf.org>; Mon, 26 Aug 2013 16:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=f9ber8kgJWeAwK3Y6R+PoYJUysOI1hRiTEER30AVeFI=; b=azr837X0rJnAoBmtJzWlTuVX+nIAp8kRKmSmEoxBds7Uv6ldCZT0f778XaoAP+hSxS DPqHO77mh/DtqQKZh+3wJdYCvdycFPrcre4VZe1qJMfDwUyTdfiOHe3sPoE6k/8toLyF h0hDx7/tvR/v4WShK5nWf8QSuCBR9IZwwxaFlQdexKi3pop/a64yIlCNEgEwSnMvBLQD x2aq7vV88PFKaqNLVFVU+PS44p+DvgTjp7tqBbyyUT5IUN74eAlphodq/vn3WMI9DHOP RiEp9Ahssb1UJ3eVvy3i7bCWkW1LNBf/RYlfS/pKe1uofnTzuxN+l9BTS+rLpBEhvDsh DaAw==
X-Received: by 10.68.189.70 with SMTP id gg6mr17910356pbc.123.1377559948273; Mon, 26 Aug 2013 16:32:28 -0700 (PDT)
Received: from [192.168.2.247] (c-24-6-103-174.hsd1.ca.comcast.net. [24.6.103.174]) by mx.google.com with ESMTPSA id uw6sm20524400pbc.8.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 26 Aug 2013 16:32:27 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <5564260.oH8aR0Fh9U@scott-latitude-e6320>
Date: Mon, 26 Aug 2013 16:32:25 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E537808-7B01-42FA-9109-3C8B8F26C1F4@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <1973922.OgEpFZ84lJ@scott-latitude-e6320> <BE72B4FF-2948-4EB4-9A91-D026FC493B4F@gmail.com> <5564260.oH8aR0Fh9U@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 23:32:29 -0000

On Aug 26, 2013, at 4:29 PM, Scott Kitterman <scott@kitterman.com> =
wrote:

> On Monday, August 26, 2013 16:28:03 Douglas Otis wrote:
>> On Aug 26, 2013, at 3:48 PM, Scott Kitterman <scott@kitterman.com> =
wrote:
>>> On Monday, August 26, 2013 15:42:41 Douglas Otis wrote:
>>>> Please also note that the PTR RR is not constrained in the current
>>>> specification and can create erratic results.  It would be far =
safer to
>>>> Perm error when overflowing on the number of PTR records.  There is =
no
>>>> upper limit as some represent web farms hosting thousands of =
domains.
>>>=20
>>> This exact issue was the subject of working group discussion.  Since =
the
>>> number of PTR records is an attribute of the connect IP, it is under =
the
>>> control of the sending party, not the domain owner.  A cap that =
resulted
>>> in an error would, as a result, enable the sender to arbitrarily get =
an
>>> SPF permerror in place of a fail if desired.  The WG considered that =
not
>>> a good idea.
>>=20
>> Dear Scott,
>>=20
>> It is within the control of the Domain owner about whether to make =
use of
>> the ptr mechanism in their SPF TXT.  Random ordering or responses is =
also
>> controlled by the IP address owner and not the Domain owner.  The ptr
>> mechanism may offer intermittent results that will be difficult to
>> troubleshoot.  By offering a Perm error on a ptr overflow, the domain =
owner
>> is quickly notified this mechanism should not be used and are not =
fooled by
>> it working some of the time.  The greater concern is in regard to the =
over
>> all response sizes when DNSSEC is used.  In that case, response sizes =
can
>> grow significantly.  Allowing large responses to occur without =
producing an
>> error seems like a risky strategy from the DDoS perspective.  That is =
also
>> another reason for worrying about the use of TXT RRs.  How many large
>> wildcard TXT RR exist, and if they do, who would be at fault when =
this
>> becomes a problem for SPF?
>=20
> Your conclusion is different than the one the working group reached.

Dear Scott,=20

Do you recall whether DNSSEC had been considered?

Regards,
Douglas Otis=

From scott@kitterman.com  Mon Aug 26 16:56:57 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3930811E8107 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:56: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=[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 AY8P++epgf+3 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 16:56:50 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA6221F991F for <ietf@ietf.org>; Mon, 26 Aug 2013 16:56:47 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id D940E956001; Mon, 26 Aug 2013 19:56:46 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377561406; bh=lxtn0SAuWvfZ1GN236WGWG9fkcjyQY5+Ow8Wgh5Ut68=; h=In-Reply-To:References:Subject:From:Date:To:From; b=oZOqB0cqwtc3d4fktcVbQdPEsWjwR0xTrN3Sf9QbtnAOSdW/NwPfEocu2X0MEDjYr ryWkNfOETcHqZHQ/C5nXmzEIIaQyiY0Ogvh/RkCQIzNa+EcwwwZcOBR6VPBEDVsWZY HYB9DMbMU+vmOKTz69xH8x32u+/fyLkiSbWQ2xjo=
Received: from [192.168.111.106] (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 8C710D0401E;  Mon, 26 Aug 2013 19:56:46 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <5E537808-7B01-42FA-9109-3C8B8F26C1F4@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <1973922.OgEpFZ84lJ@scott-latitude-e6320> <BE72B4FF-2948-4EB4-9A91-D026FC493B4F@gmail.com> <5564260.oH8aR0Fh9U@scott-latitude-e6320> <5E537808-7B01-42FA-9109-3C8B8F26C1F4@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Scott Kitterman <scott@kitterman.com>
Date: Mon, 26 Aug 2013 19:56:53 -0400
To: ietf@ietf.org
Message-ID: <ba997e72-0255-4b8d-984f-03736b8b2d53@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2013 23:56:57 -0000

Douglas Otis <doug.mtview@gmail.com> wrote:
>
>On Aug 26, 2013, at 4:29 PM, Scott Kitterman <scott@kitterman.com>
>wrote:
>
>> On Monday, August 26, 2013 16:28:03 Douglas Otis wrote:
>>> On Aug 26, 2013, at 3:48 PM, Scott Kitterman <scott@kitterman.com>
>wrote:
>>>> On Monday, August 26, 2013 15:42:41 Douglas Otis wrote:
>>>>> Please also note that the PTR RR is not constrained in the current
>>>>> specification and can create erratic results.  It would be far
>safer to
>>>>> Perm error when overflowing on the number of PTR records.  There
>is no
>>>>> upper limit as some represent web farms hosting thousands of
>domains.
>>>> 
>>>> This exact issue was the subject of working group discussion. 
>Since the
>>>> number of PTR records is an attribute of the connect IP, it is
>under the
>>>> control of the sending party, not the domain owner.  A cap that
>resulted
>>>> in an error would, as a result, enable the sender to arbitrarily
>get an
>>>> SPF permerror in place of a fail if desired.  The WG considered
>that not
>>>> a good idea.
>>> 
>>> Dear Scott,
>>> 
>>> It is within the control of the Domain owner about whether to make
>use of
>>> the ptr mechanism in their SPF TXT.  Random ordering or responses is
>also
>>> controlled by the IP address owner and not the Domain owner.  The
>ptr
>>> mechanism may offer intermittent results that will be difficult to
>>> troubleshoot.  By offering a Perm error on a ptr overflow, the
>domain owner
>>> is quickly notified this mechanism should not be used and are not
>fooled by
>>> it working some of the time.  The greater concern is in regard to
>the over
>>> all response sizes when DNSSEC is used.  In that case, response
>sizes can
>>> grow significantly.  Allowing large responses to occur without
>producing an
>>> error seems like a risky strategy from the DDoS perspective.  That
>is also
>>> another reason for worrying about the use of TXT RRs.  How many
>large
>>> wildcard TXT RR exist, and if they do, who would be at fault when
>this
>>> becomes a problem for SPF?
>> 
>> Your conclusion is different than the one the working group reached.
>
>Dear Scott, 
>
>Do you recall whether DNSSEC had been considered?

My recollection is that it was discussed. I believe it was concluded that SPF would benefit from the enhanced security associated with DNSSEC.  SPF doesn't seem to suffer from any unique problems associated with the potential for a larger payload. 

Scott K


From sm@elandsys.com  Mon Aug 26 19:35:55 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B91311E8127 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 19:35:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level: 
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqimWpeYoKRG for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 19:35:54 -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 0B57811E8121 for <ietf@ietf.org>; Mon, 26 Aug 2013 19:35:51 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.139.183]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7R2ZXcK008315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 26 Aug 2013 19:35:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377570945; bh=Mo4yHL8p867y6+jEsXWVftFMZxuZdu8r9iPc0cg81ko=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pfMQdq3NQvPAkBYcECsGMVHe1bdBwQg9QVRxomMjZS4wBFRrpd6soqLkTdqtvCv4J sFb8EUcsjQ7/KVw/R3vV9pFGWZOpBTJ8f33gO2yCv8tZICHiM5teaHXGryL7IgGCjb w2sy4Yij+UTut/yfU7smzVdSjwVu7lnHPjvQkjoY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377570945; i=@elandsys.com; bh=Mo4yHL8p867y6+jEsXWVftFMZxuZdu8r9iPc0cg81ko=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=U0puHmB1bW2ibzO57a2+ZLzyPN+E/QdGWXMLpWWaEgkd7IEcFaLhkqznRXwqzNbNO mvg9d+0xRQk/0TOSc1zlSccwVttJ0aXQh0tDCXEVIKwTWEJG4VQvbjfywtUTjXc9F4 gXXpxGGdcfWhRej7j0iYekgDeffXnz5C3WnlGKdc=
Message-Id: <6.2.5.6.2.20130826182352.0cac3298@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 26 Aug 2013 19:28:25 -0700
To: Douglas Otis <doug.mtview@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 02:35:55 -0000

Hi Doug,
At 15:42 26-08-2013, Douglas Otis wrote:
>When the SPF document refers to "Sender Policy Framework (SPF) 
>records" or "SPF records" this conflicts with DNS's record 
>definition.  It is wrong to refer to these as "records".  RFC1034 
>defines resource records as TTL and RDATA that is selected by Owner 
>(domain), Type (16 bit value), and Class (16 bit value).  No such 
>selection is possible for SPF.   SPF uses a subclass of TXT resource 
>records using a non-standard prefix that has no registry, nor is a 
>registry practical at this point.
>
>Terminology used by SPF sounds "as if" it refers directly to DNS 
>elements.  It does not.  This poor terminology is misleading and 
>makes properly expressing security concerns difficult where this 
>confusion seems to be by design.

As there is an ongoing Last Call the IETF can comment about the 
above.  I'll leave it to the IESG to evaluate whether the terminology 
used in the draft needs to be reconsidered if there aren't any comments.

>The SPF protocol was an effort that ignored concerns expressed 
>within the DNS community about the effect of overloading TXT and use 
>of dynamic macro query names modified by email elements wholly 
>unconstrained by a sender's infrastructure.  The SPF macro scheme 
>can greatly amplify the impact of an already large number of DNS 
>transactions.  By overloading TXT, updating SPF is improbable.  By 
>rarely being the target of a DDoS attack, it becomes easy to speak 
>in derogatory terms as this issue being the fault of DNS.

There has been comments about overloading TXT during the Last 
Call.  I'll keep it separate from the use of dynamic macro query names.

>The primary use of SPF today is to define email outbound address 
>space.  The policy aspects related to the "all" mechanism is largely 
>ignored due to a high number of required exceptions.  Rather than 
>using the existing APL Resource Record in the form of 
>_email.<domain> APL <CIDRs> in binary form, the group devised a 
>macro language to authorize various email elements using text to 
>accommodate a vendor that since became practically irrelevant for 
>Internet email exchange.  Although most large providers now ignore 
>SPF macros, very few domains publish them as well.  Macros interfere 
>with a provider's effort at mapping a domain's address space.  Most 
>consider the authorization for email-address local parts the 
>sender's role.  Nevertheless, the WG failed to warn of this issue by 
>either deprecating or advising against macro publication.  Macros 
>inhibit effective caching, imperil SMTP server security, and degrade 
>interchange. This is not a good candidate for standardization if 
>this category is expected to retain any value or the IETF is to 
>offer helpful guidance.
>
>Simply because SPF did not stipulate DNSSEC does not mean DNSSEC can 
>be ignored.  Not considering DNSSEC is an example of a failed 
>consideration.  Must the world wait for SPF to change before DNSSEC 
>can be safely deployed?  Overloading of TXT resource records at the 
>zone apex along with macro scripts able to leverage email elements 
>to direct reflected attacks from cached resource records is an 
>example why this document should not be deemed a standard.

Thanks for providing the arguments.  I'll leave the question of 
whether the document should or should not be a good candidate for 
standardization to IESG evaluation.

>There is a trend by large providers to switch over to using 
>wildcards on enormous networks to track users instead of using 
>cookies.  The impact this has on the past conversations is 
>enormous.  This eliminates the effect of the void response limit 
>while also increasing the amount of the resulting traffic.
>
>   <random-string><http://cdr-ds.metric.gstatic.com/>cdr-ds.metric.gstatic.com
>  <random-string>.<http://g.vm.akamaistream.net/>g.vm.akamaistream.net

The above can be considered together with the other arguments about the TXT RR.

>Please also note that the PTR RR is not constrained in the current 
>specification and can create erratic results.  It would be far safer 
>to Perm error when overflowing on the number of PTR records.  There 
>is no upper limit as some represent web farms hosting thousands of domains.

The title of Section 5.5 is: ""ptr" (do not use)".  There is a note 
in Section 5.5 about the mechanism.  There is some discussion of PTR 
at http://www.ietf.org/mail-archive/web/spfbis/current/msg01883.html

>This timeout is not likely problematic after ensuring against macros 
>where then caching can be effective at overcoming this constraint.

I'll list this one as a non-issue.

>That does not mean DNSSEC will not be used.  One hopes just the 
>opposite is true.

I took a quick look at draft-ietf-spfbis-4408bis-19.  I did not see 
any mention of DNSSEC.

>The permitted size of the UDP packet is NOT 512 octets.  That is the 
>permitted size of the DNS Message.  DNS Message is not the same 
>thing as a UDP packet.


>>>Per RFC1035
>>>Section 2.3.4. Size limits
>>>UDP messages    512 octets or less

I'll suggest UDP message.

>A reduction to 450 octets would be a reasonable recommendation for 
>the DNS _message_, not the UDP _packet_.  The packet still needs to 
>carry the IP and UDP headers.

Yes.  I misunderstood your previous arguments.

>There should be some type of warning at minimum as the macro issue 
>is likely to affect interchange now and going forward.  The IETF 
>should not consider protocols outside larger concerns of the well 
>being of the Internet infrastructure and proper interchange.  This 
>issue should not be controversial.

I'll consider the "macro" issue as addressed.

Regards,
S. Moonesamy (as document shepherd)



From john-ietf@jck.com  Mon Aug 26 23:21:31 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB8F11E8125 for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 23:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0+PTItFvQgG for <ietf@ietfa.amsl.com>; Mon, 26 Aug 2013 23:21:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 313AB11E813A for <ietf@ietf.org>; Mon, 26 Aug 2013 23:21:25 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VECeU-000CqD-3T; Tue, 27 Aug 2013 02:21:18 -0400
Date: Tue, 27 Aug 2013 02:21:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: John R Levine <johnl@taugh.com>, Jelte Jansen <jelte.jansen@sidn.nl>
Subject: Overloaded TXT harmful (was" Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender	Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard)
Message-ID: <E30070F220FC128EEF0A59CA@JcK-HP8200.jck.com>
In-Reply-To: <alpine.BSF.2.00.1308261046100.76616@joyce.lan>
References: <20130823143402.49936.qmail@joyce.lan> <521B165C.9000809@sidn.nl> <alpine.BSF.2.00.1308261005360.76238@joyce.lan> <521B69AD.5020108@sidn.nl> <alpine.BSF.2.00.1308261046100.76616@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 06:21:31 -0000

--On Monday, August 26, 2013 10:49 -0400 John R Levine
<johnl@taugh.com> wrote:

> Sorry if that last one came across as dismissive.
> 
>> Until such time, I'd personally prefer to see some explicit
>> notion that the odd history of the SPF TXT record should not
>> be seen as a precedent and best practice, rather than hope
>> that this is implicit.
> 
> I'd have thought that the debate here and elsewhere already
> documented that.  Since it's not specific to SPF, perhaps we
> could do a draft on "overloaded TXT considered harmful" to get
> it into the RFC record.

With the help of a few others, I've got a I-D in the pipe whose
function is to create an IANA registry of structured protocol
uses for TXT RR data and how to recognize them.  I hope it will
be posted later this week.  Its purpose is to lower the odds of
"overloaded" sliding into "different uses for forms that are not
easily distinguished".  Other than inspiration, its only
relationship to the current SPF discussion is that some
SPF-related information is a candidate for registration (whether
as an active use or as a deprecated one).

It already contains some text that warns that overloading TXT is
a bad idea but that, because it happens and has happened,
identifying those uses is appropriate.  Once it is posted, I/we
would appreciate any discussion that would lead to consensus
about just how strong that warning should be and how it should
be stated.

best,
   john






From abdussalambaryun@gmail.com  Tue Aug 27 02:50:06 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A51421E80C8 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 02:50:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  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 nO1POqXdbap9 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 02:50:05 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7796D11E816E for <ietf@ietf.org>; Tue, 27 Aug 2013 02:50:05 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb4so4616686pbc.22 for <ietf@ietf.org>; Tue, 27 Aug 2013 02:50: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=tPbjf63USo+ICk7Pr308KXYycpRVEu7lIJH9fq1+V+Y=; b=Tx1auVl0VIq/w9thgYDNpHi86YOcrxqP3205fbWVLlAf9Xt/jc0WrGZmW8mup6ZFs7 izBGYy9kjjPWxBb/1WLT6XLL9NQa6xXifrgIasUIZm1p9iVhvoIrr9PW4AnB+/RG1d0B Gae9T4oUd5cDXUtDcjkkk5oOJYLqQCLgVGyr78M0Rh/tRq7WdjqKV4T7vySya1r6ZJCs yHfOuvpmegKnPEJBlTVL4ofMYcgNHRFBTA7NRkQB2iEvcnYMjzXZ0gTKg5YpbZBS5b7b GwG2QrplwEDsB8Pz+pzPM+Ye+lYG2UUmpTlYbhUZah0NEp/qMIWOsxg17WGPD2as3Wxt Gn2g==
MIME-Version: 1.0
X-Received: by 10.68.111.35 with SMTP id if3mr7698079pbb.181.1377597005040; Tue, 27 Aug 2013 02:50:05 -0700 (PDT)
Received: by 10.68.195.168 with HTTP; Tue, 27 Aug 2013 02:50:04 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk>
Date: Tue, 27 Aug 2013 19:50:04 +1000
Message-ID: <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com>
Subject: Re: Rude responses
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=047d7b67692821146504e4eaccf8
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, 27 Aug 2013 09:50:06 -0000

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

On Mon, Aug 26, 2013 at 5:36 PM, <l.wood@surrey.ac.uk> wrote:

> > I experienced rude respondings in IETF list
>
> That would be when you tried to get April 1 RFCs discontinued.
>

No, I experienced rude response from some participants including you, and
regarding yours I received a private email from one director that he ask me
not to reply to you because he wants to handle it with you privately. I
request that the IETF Chair to stop you from sending me any further emails,
because you are changing the subject to personal issues.

AB


>
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun [abdussalambaryun@gmail.com]
> Sent: 25 August 2013 12:27
> To: Pete Resnick
> Cc: dcrocker@bbiw.net; ietf@ietf.org
> Subject: Re: Rude responses (Was: Last Call:
> <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for
> Authorizing Use of Domains in Email,         Version 1) to Proposed
> Standard)
>
> I experienced rude respondings in IETF list and in  one WG list, I don't
> beleive that it is culture of IETF participants, but it seems that some
> people should understand to be polite and reasonable in such organisation
> business. Finally, the rude responding is not controled by the chair of
> thoes lists, therefore, thoes lists can be rude lists from time to time.
>
> AB
>
>
>
>

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

<div dir=3D"ltr">On Mon, Aug 26, 2013 at 5:36 PM,  <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:l.wood@surrey.ac.uk" target=3D"_blank">l.wood@surrey.ac.uk<=
/a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex">
&gt; I experienced rude respondings in IETF list<br>
<br>
That would be when you tried to get April 1 RFCs discontinued.<br></blockqu=
ote><div><br></div>No, I experienced rude response from some participants i=
ncluding you, and regarding yours I=A0received=A0a private email from one d=
irector that he ask me not to reply to you because he wants to handle it wi=
th you privately. I request that the IETF Chair to stop you from sending me=
 any further emails, because you are changing the subject to personal issue=
s.</div>
<div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">AB<br><div>=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">

<br>
<br>
________________________________________<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [<=
a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] On Behal=
f Of Abdussalam Baryun [<a href=3D"mailto:abdussalambaryun@gmail.com">abdus=
salambaryun@gmail.com</a>]<br>

Sent: 25 August 2013 12:27<br>
To: Pete Resnick<br>
Cc: <a href=3D"mailto:dcrocker@bbiw.net">dcrocker@bbiw.net</a>; <a href=3D"=
mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: Rude responses (Was: Last Call: &lt;draft-ietf-spfbis-4408bis-=
19.txt&gt; (Sender Policy Framework (SPF) for Authorizing Use of Domains in=
 Email, =A0 =A0 =A0 =A0 Version 1) to Proposed Standard)<br>
<br>
I experienced rude respondings in IETF list and in =A0one WG list, I don&#3=
9;t beleive that it is culture of IETF participants, but it seems that some=
 people should understand to be polite and reasonable in such organisation =
business. Finally, the rude responding is not controled by the chair of tho=
es lists, therefore, thoes lists can be rude lists from time to time.<br>

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

--047d7b67692821146504e4eaccf8--

From tjc@ecs.soton.ac.uk  Tue Aug 27 03:51:40 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1826F11E824D for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 03:51: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 iFzn11Lh55q4 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 03:51:39 -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 108CD11E81AF for <ietf@ietf.org>; Tue, 27 Aug 2013 03:51:38 -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 r7RApWOq008636 for <ietf@ietf.org>; Tue, 27 Aug 2013 11:51:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r7RApWOq008636
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1377600693; bh=5vgx1nkw9u18+o+07ZjCbJ40FlE=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=3GbFlVrLPeuYf/bNU/gx0wkaPoxMDgbxRuncHif4GKFjYPx3p+FRE+Mc3ZNi7Kst0 kGkV0IvNRKYZseAREtulkdDJ3rdHiQIfPczePur6IOd5iIQ716qWRJTCpfDaHXF2sQ aJeoQTeiXaQjcEeM/r+cGeqlUi5cgUuTuy89yZjo=
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 p7QBpW0544507328hK ret-id none; Tue, 27 Aug 2013 11:51:33 +0100
Received: from dhcp-204-58.wireless.soton.ac.uk (dhcp-204-58.wireless.soton.ac.uk [152.78.204.58]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r7RApV8K028921 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 27 Aug 2013 11:51:31 +0100
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Rude responses (sergeant-at-arms?)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com>
Date: Tue, 27 Aug 2013 11:51:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>
To: ietf <ietf@ietf.org>
X-Mailer: Apple Mail (2.1508)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p7QBpW054450732800; tid=p7QBpW0544507328hK; 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: r7RApWOq008636
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, 27 Aug 2013 10:51:40 -0000

Isn't there supposed to be a sergeant-at-arms to handle inappropriate =
behaviour on this list?

Though the last I recall that was Jordi, and that was probably ten years =
ago...

Though it would be preferable if everyone were a bit more respectful of =
other posters, whether new or veteran.

Tim=

From abdussalambaryun@gmail.com  Tue Aug 27 04:05:23 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98AED11E8291; Tue, 27 Aug 2013 04:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119,  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 DrN20Lb3xosL; Tue, 27 Aug 2013 04:05:22 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 3A98511E8184; Tue, 27 Aug 2013 04:05:22 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so4683661pab.41 for <multiple recipients>; Tue, 27 Aug 2013 04:05: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:date:message-id:subject:from:to :cc:content-type; bh=VlByFy4T2cgiuaWQD+JoVqZszIDEHJe42A76L/OYdPI=; b=VBGfehRXiWM0PAMGIg8BmmVN42+R3naAORkRS6S1vacbqQUdVjl04ODYCyXWMhqnee EDCrszL/PUc+E6DdOdiWTq5f4/kOnzICDrvXDhZT9QS5mtWqnqUgsCdBLI8Y4ZE+yKVl tQdifpMogL2HjBaW4qiSAZikGcMPLLC8AIdSZnvPhmSYi7IVaIOZBagC65nb8OLpwnYW ECvoJcri732pQLRu/93WB5VlRdNfI9vZmUC9jBwe+5SbMPmaM7tYJeTQHydI0mY6lH3R /urFuzScE6iD9X3FxjC1mmAvLSn2gujS+Pc41RG45y2RFeVVz7ZH6cH4s8K5uSUM18aJ Zw8g==
MIME-Version: 1.0
X-Received: by 10.66.218.166 with SMTP id ph6mr20124296pac.28.1377601521748; Tue, 27 Aug 2013 04:05:21 -0700 (PDT)
Received: by 10.68.195.168 with HTTP; Tue, 27 Aug 2013 04:05:21 -0700 (PDT)
In-Reply-To: <20130819135219.8236.40060.idtracker@ietfa.amsl.com>
References: <20130819135219.8236.40060.idtracker@ietfa.amsl.com>
Date: Tue, 27 Aug 2013 21:05:21 +1000
Message-ID: <CADnDZ8_jfLdPk482KYy0=BYsqS1=XsFSi2OP3MXaGYoNvkwxBw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-v6ops-mobile-device-profile-04.txt> (Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b5db49a589f3604e4ebd9d6
Cc: v6ops@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, 27 Aug 2013 11:05:24 -0000

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

Reviewer: Abdussalam Baryun
Date: 26.08.2013

As per the IESG request for review dated 19.08.2013
++++++++++++++++++++++++++++++++++++

I support the draft, thanks, below are my comments,

Overall> The draft is about 3GPP Mobile Devices but the draft has no
normative reference to such device. The title of the draft SHOULD mention
that it is general profile or a proposal, where the abstract says
*specifies an IPv6 profile* which means not general, so the title SHOULD
say *An IPv6 profile*. Also the draft does not consider Mobile IP issues
nor RFC5213 into requirements. From the doc the reviewer is not sure does
the draft consider MANET issues or not needed for such devices or such
connections?



Abstract> This document specifies an IPv6 profile for 3GPP mobile devices.



AB> suggest> this document defines an IPv6 profile....

The document is missing an applicability statement section, which may be
found in one paragraph in section 1.1, but the reviewer would like more
details because the document is some how saying it is general requirements.

AB


On Mon, Aug 19, 2013 at 11:52 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices'
>   <draft-ietf-v6ops-mobile-device-profile-04.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-09-02. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document specifies an IPv6 profile for 3GPP mobile devices.  It
>    lists the set of features a 3GPP mobile device is to be compliant
>    with to connect to an IPv6-only or dual-stack wireless network
>    (including 3GPP cellular network and IEEE 802.11 network).
>
>    This document defines a different profile than the one for general
>    connection to IPv6 cellular networks defined in
>    [I-D.ietf-v6ops-rfc3316bis].  In particular, this document identifies
>    also features to deliver IPv4 connectivity service over an IPv6-only
>    transport.
>
>    Both hosts and devices with capability to share their WAN (Wide Area
>    Network) connectivity are in scope.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/
>
> IESG discussion can be tracked via
>
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-profile/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

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

<div dir=3D"ltr"><div style>Reviewer: Abdussalam Baryun</div><div style>Dat=
e: 26.08.2013</div><div style><br></div><div style>As per the IESG request =
for review dated 19.08.2013</div><div style>+++++++++++++++++++++++++++++++=
+++++</div>
<div style><br></div><div style>I support the draft, thanks, below are my c=
omments,</div><div style><br></div><div style>Overall&gt; The draft is abou=
t 3GPP Mobile Devices but the draft has no normative reference to such devi=
ce. The title of the draft SHOULD mention that it is general profile or a p=
roposal, where the abstract says *specifies an IPv6 profile* which means no=
t general, so the title SHOULD say *An IPv6 profile*. Also the draft does n=
ot consider Mobile IP issues nor RFC5213 into requirements. From the doc th=
e reviewer is not sure does the draft consider MANET issues or not needed f=
or such devices or such connections?</div>
<div><pre style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb=
(0,0,0)"><br></pre><pre style=3D"font-size:1em;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)"><br></pre><pre style=3D"font-size:1em;margin-top:0px=
;margin-bottom:0px;color:rgb(0,0,0)">
Abstract&gt; This document specifies an IPv6 profile for 3GPP mobile device=
s.</pre><pre style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:=
rgb(0,0,0)"><br></pre><pre style=3D"font-size:1em;margin-top:0px;margin-bot=
tom:0px;color:rgb(0,0,0)">
<br></pre></div><div style>AB&gt; suggest&gt; this document defines an IPv6=
 profile....</div><div style><br></div><div style>The document is missing a=
n applicability statement section, which may be found in one paragraph in s=
ection 1.1, but the reviewer would like more details because the document i=
s some how saying it is general requirements.</div>
<div style><br></div><div style>AB</div></div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Mon, Aug 19, 2013 at 11:52 PM, The IESG=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D=
"_blank">iesg-secretary@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"><br>
The IESG has received a request from the IPv6 Operations WG (v6ops) to<br>
consider the following document:<br>
- &#39;Internet Protocol Version 6 (IPv6) Profile for 3GPP Mobile Devices&#=
39;<br>
=A0 &lt;draft-ietf-v6ops-mobile-device-profile-04.txt&gt; as Informational =
RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-09=
-02. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=A0 =A0This document specifies an IPv6 profile for 3GPP mobile devices. =A0=
It<br>
=A0 =A0lists the set of features a 3GPP mobile device is to be compliant<br=
>
=A0 =A0with to connect to an IPv6-only or dual-stack wireless network<br>
=A0 =A0(including 3GPP cellular network and IEEE 802.11 network).<br>
<br>
=A0 =A0This document defines a different profile than the one for general<b=
r>
=A0 =A0connection to IPv6 cellular networks defined in<br>
=A0 =A0[I-D.ietf-v6ops-rfc3316bis]. =A0In particular, this document identif=
ies<br>
=A0 =A0also features to deliver IPv4 connectivity service over an IPv6-only=
<br>
=A0 =A0transport.<br>
<br>
=A0 =A0Both hosts and devices with capability to share their WAN (Wide Area=
<br>
=A0 =A0Network) connectivity are in scope.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-p=
rofile/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-v6ops=
-mobile-device-profile/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-v6ops-mobile-device-p=
rofile/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-iet=
f-v6ops-mobile-device-profile/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
</blockquote></div><br></div>

--047d7b5db49a589f3604e4ebd9d6--

From prvs=1951a59a84=jordi.palet@consulintel.es  Tue Aug 27 05:33:05 2013
Return-Path: <prvs=1951a59a84=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5662321F9EB6 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 05:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kuQmCMCJlqND for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 05:33:00 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id A975921F9E9F for <ietf@ietf.org>; Tue, 27 Aug 2013 05:32:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1377606768; x=1378211568; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=qWnlTUiVHSz/lCA42VrBHF1w+ xywBYt1L13baFauWnk=; b=NkzhRDhejzT6Sm8zZoAECujskDx+8ky9/MYZZP8kK eWff4n1+LASCL0e3TrDe2CTyk+GTzOCL6KOZZDcdlDAlffUPBDsdM7wmnBpLxsxz qokj12HbaQvSEiMycDqdvP25DUcm4b3rX7DKdv3Sxin+gc6O0UGCdhv5sn/K1WAh OQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=aDCrsofayHaD7DwZR9rNFzsQktWyHJN52BXHnuW3iwrQ3iMM3y1Oj8A+94nL r7PFiwT3wy57/VdUExloHj2fqKpbR14AQY9904jvxhUiD2vCF4CL390li h5+naTH56k7gw0JupEmezB6rAsmpGoRxvYkUTz1NAyMF+PEKaPL7gk=;
X-MDAV-Processed: consulintel.es, Tue, 27 Aug 2013 14:32:48 +0200
Received: from [107.17.147.216] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004466316.msg for <ietf@ietf.org>; Tue, 27 Aug 2013 14:32:48 +0200
X-Spam-Processed: consulintel.es, Tue, 27 Aug 2013 14:32:48 +0200 (not processed: message from trusted or authenticated source)
X-MDPtrLookup-Result: hardfail ip=107.17.147.216 (no PTR records found) (consulintel.es)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:130827:md50004466316::n0MmpamJo5jCYnlE:00006EAB
X-MDRemoteIP: 107.17.147.216
X-Return-Path: prvs=1951a59a84=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 27 Aug 2013 08:32:24 -0400
Subject: Re: Rude responses
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <abdussalambaryun@gmail.com>, <l.wood@surrey.ac.uk>
Message-ID: <CE421436.B3A0D%jordi.palet@consulintel.es>
Thread-Topic: Rude responses
In-Reply-To: <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 12:33:05 -0000

As Seargeant-at-arms, this is my first and last warning.

If this goes on, I will ask the secretariat to avoid further postings.

Regards,
Jordi






-----Mensaje original-----
De: Abdussalam Baryun <abdussalambaryun@gmail.com>
Responder a: <abdussalambaryun@gmail.com>
Fecha: martes, 27 de agosto de 2013 05:50
Para: <l.wood@surrey.ac.uk>
CC: ietf <ietf@ietf.org>
Asunto: Re: Rude responses

>On Mon, Aug 26, 2013 at 5:36 PM,  <l.wood@surrey.ac.uk> wrote:
>
>> I experienced rude respondings in IETF list
>
>That would be when you tried to get April 1 RFCs discontinued.
>
>
>
>No, I experienced rude response from some participants including you, and
>regarding yours I received a private email from one director that he ask
>me not to reply to you because he wants to handle it with you privately.
>I request that the IETF Chair to stop you from sending me any further
>emails, because you are changing the subject to personal issues.
>
>AB
> 
>
>
>
>________________________________________
>From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of
>Abdussalam Baryun [abdussalambaryun@gmail.com]
>
>Sent: 25 August 2013 12:27
>To: Pete Resnick
>Cc: dcrocker@bbiw.net; ietf@ietf.org
>Subject: Re: Rude responses (Was: Last Call:
><draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for
>Authorizing Use of Domains in Email,         Version 1) to Proposed
>Standard)
>
>I experienced rude respondings in IETF list and in  one WG list, I don't
>beleive that it is culture of IETF participants, but it seems that some
>people should understand to be polite and reasonable in such organisation
>business. Finally, the rude responding is not controled by the chair of
>thoes lists, therefore, thoes lists can be rude lists from time to time.
>
>AB
>
>
>
>
>
>
>
>
>



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From prvs=1951a59a84=jordi.palet@consulintel.es  Tue Aug 27 05:34:20 2013
Return-Path: <prvs=1951a59a84=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E7AA21F94FF for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 05:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0dM6JJT4vaC for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 05:34:15 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id B625B21F9C12 for <ietf@ietf.org>; Tue, 27 Aug 2013 05:33:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1377606834; x=1378211634; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=SS02uhQvOyPFs50S/3Xd2F32x fqP3lACbQeuoMhB/Is=; b=FvU0gUTrvBeJDmGgwIxc/0bXRuKBxQY+srZplMuyB xOOaxYLBPTsyJcVnXNjeUnMdn2VlvmUo+PO9JCg5iqVLARTnMzEbx2O2mjUfvP6d z5Yxo9syNCgAeExKYjPjBBCCgbmaVQn5w2ldhnO1sgqX/5nI0GP1nKiN0VYvlwKc XA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=EQVQfU32SfsXdu5yRGUorXmjMTWZAEW8+VA/O6QZU4qaEQZ0gyo6DsVj0Z1J KvQWS+LwaLbFN3Z6DW1tqkztQcWWqKRyx7UG6U2n5gEK9JdP3yKin7Leg 1mPhpfyQf5euWR8liX/a/kF4Xgoo4UnKHi6Nu03EAZ/vuhtFXYFjsw=;
X-MDAV-Processed: consulintel.es, Tue, 27 Aug 2013 14:33:54 +0200
Received: from [107.17.147.216] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004466317.msg for <ietf@ietf.org>; Tue, 27 Aug 2013 14:33:53 +0200
X-Spam-Processed: consulintel.es, Tue, 27 Aug 2013 14:33:53 +0200 (not processed: message from trusted or authenticated source)
X-MDPtrLookup-Result: hardfail ip=107.17.147.216 (no PTR records found) (consulintel.es)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:130827:md50004466317::Ol+cV404aFTiDR6Y:00006zgK
X-MDRemoteIP: 107.17.147.216
X-Return-Path: prvs=1951a59a84=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 27 Aug 2013 08:33:18 -0400
Subject: Re: Rude responses (sergeant-at-arms?)
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <tjc@ecs.soton.ac.uk>
Message-ID: <CE4214A7.B3A12%jordi.palet@consulintel.es>
Thread-Topic: Rude responses (sergeant-at-arms?)
In-Reply-To: <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>
Mime-version: 1.0
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
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 12:34:20 -0000

I'm =8A I was traveling and not having access to email =8A

Regards,
Jordi






-----Mensaje original-----
De: Tim Chown <tjc@ecs.soton.ac.uk>
Responder a: <tjc@ecs.soton.ac.uk>
Fecha: martes, 27 de agosto de 2013 06:51
Para: ietf <ietf@ietf.org>
Asunto: Re: Rude responses (sergeant-at-arms?)

>Isn't there supposed to be a sergeant-at-arms to handle inappropriate
>behaviour on this list?
>
>Though the last I recall that was Jordi, and that was probably ten years
>ago...
>
>Though it would be preferable if everyone were a bit more respectful of
>other posters, whether new or veteran.
>
>Tim



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From mary.h.barnes@gmail.com  Tue Aug 27 07:28:19 2013
Return-Path: <mary.h.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 31CD311E8354 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 07:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, 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 JFymKcAD3OU3 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 07:28:18 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5D02E11E81A8 for <ietf@ietf.org>; Tue, 27 Aug 2013 07:28:18 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id ij15so3012617vcb.2 for <ietf@ietf.org>; Tue, 27 Aug 2013 07:28: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=XswmZSseMMb/HJMmsv6946/JYfZKh9zua7ssvJB7xEw=; b=sDy06ME13XTR3Nzwa+PeIGA1cynr9oyHwYZcNeqJMvFj01kD3CBz85+/WfWD1jiLwK /Gze41ayBvt0UJxhNePa0BKNo3iAztwuarNwMQiGVbTvEaKXLuvrDobXAfX7H8S4fTzL dw4UpRfXSu/zL6jcLlv7MTGmMbaFk2XxpXaIWyPixWrhQLfjZSkxHcjzg3QJ3v5aQsSu +7P2ZsL+k9fU6U0CyHmoKcyMTXp0nVSvlHJnSfdh/guW/L7d/DZFFkLriL0ftGahkgn/ vi2rB+T+KZ4wCGon8rTzWUM6hdDO15VpcBesgyoQU3E47LjbkNYGPAdcc/+zQWOisWyR QZ0w==
MIME-Version: 1.0
X-Received: by 10.220.164.202 with SMTP id f10mr1758500vcy.25.1377613696779; Tue, 27 Aug 2013 07:28:16 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Tue, 27 Aug 2013 07:28:16 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130721070808.0c808140@elandnews.com>
References: <6.2.5.6.2.20130720193906.06cdd008@resistor.net> <BBF5DDFE515C3946BC18D733B20DAD2338DD2606@XMB104ADS.rim.net> <6.2.5.6.2.20130721070808.0c808140@elandnews.com>
Date: Tue, 27 Aug 2013 09:28:16 -0500
Message-ID: <CABmDk8nmQLY1mBbpECjo7KLULXyEvXYNgDiOVjuH6mgy-sDL9w@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Mary Barnes <mary.h.barnes@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=001a11c1e98008c97b04e4eeaffc
Cc: John C Klensin <john@jck.com>, Mary Barnes <mary.ietf.barnes@gmail.com>, tbray@textuality.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, 27 Aug 2013 14:28:19 -0000

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

SM,

As far as the IPR, as the shepherd and DISPATCH WG co-chair, I posted a
note to the DISPATCH WG mailing list before progressing this document to
see if anyone had any concerns about the IPR disclosures, which had been
discussed in the past and were updated when I asked the authors the
requisite questions about IPR while doing the PROTO write-up.  No concerns
were raised with regards to the updated IPR disclosures (i.e., no one
responded to that email).     And, you can google  "draft montemurro ietf
ipr archives" to find past discussions such as this one:  draft montemurro
ietf ipr archives

Regards,
Mary.


On Sun, Jul 21, 2013 at 11:38 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> At 00:03 21-07-2013, Andrew Allen wrote:
>
>> The reason why the IMEI namespace is being registered as a GSMA namespace
>> and not as part of the 3GPP namespace is that the GSMA has the
>> responsibility for IMEI assignment and hence in maintaining uniqueness of
>> the namespace. It has nothing to do with IPR which was extensively
>> discussed on the dispatch list.
>>
>
> I read the dispatch mailing list.  I did not see the extensive discussion.
>  I saw the following comment "Surely that is just trying to turn the IETF
> into the policeman".
>
>
>  The primary purpose of the IMEI is for preventing use of stolen mobile
>> phones and enabling emergency calls to be made from mobiles that don't have
>> a valid subscription.
>>
>
> From what I read the main purpose of the IMEI is to be able to take
> measures against stolen phones and against equipment which the use cannot
> be accepted for technical or safety reasons.  The secondary purpose is the
> tracing of malicious calls.
>
> There is an apps which sends the IMEI in a cryptographically-protected
> form over the network.  For what it is worth, it's MD5.
>
> There has been some work in the IETF on emergency calls (see service URN).
>
>
> At 00:12 21-07-2013, Andrew Allen wrote:
>
>> As John pointed out having the sub namespace reviewed by IETF provides
>> the opportunity to add text to address privacy concerns with any
>> inappropriate usage.
>>
>
> I don't think that it is the role of the IETF to determine whether the
> usage of a sub-namespace is appropriate or not as it can cause namespace
> management issues.
>
> I tried the explain the subtlety between privacy concerns and privacy
> considerations.  The IMEI can also be used as a customer identifier.
>
> Regards,
> S. Moonesamy
>

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

<div dir=3D"ltr">SM,=A0<div><br></div><div>As far as the IPR, as the shephe=
rd and DISPATCH WG co-chair, I posted a note to the DISPATCH WG mailing lis=
t before progressing this document to see if anyone had any concerns about =
the IPR disclosures, which had been discussed in the past and were updated =
when I asked the authors the requisite questions about IPR while doing the =
PROTO write-up. =A0No concerns were raised with regards to the updated IPR =
disclosures (i.e., no one responded to that email). =A0 =A0 And, you can go=
ogle =A0&quot;draft montemurro ietf ipr archives&quot; to find past discuss=
ions such as this one: =A0draft montemurro ietf ipr archives</div>
<div><br></div><div>Regards,<br></div><div>Mary. =A0</div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun, Jul 21, 2013 at=
 11:38 AM, S Moonesamy <span dir=3D"ltr">&lt;<a href=3D"mailto:sm+ietf@elan=
dsys.com" target=3D"_blank">sm+ietf@elandsys.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">At 00:03 21-07-2013, Andre=
w Allen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The reason why the IMEI namespace is being registered as a GSMA namespace a=
nd not as part of the 3GPP namespace is that the GSMA has the responsibilit=
y for IMEI assignment and hence in maintaining uniqueness of the namespace.=
 It has nothing to do with IPR which was extensively discussed on the dispa=
tch list.<br>

</blockquote>
<br></div>
I read the dispatch mailing list. =A0I did not see the extensive discussion=
. =A0I saw the following comment &quot;Surely that is just trying to turn t=
he IETF into the policeman&quot;.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The primary purpose of the IMEI is for preventing use of stolen mobile phon=
es and enabling emergency calls to be made from mobiles that don&#39;t have=
 a valid subscription.<br>
</blockquote>
<br></div>
>From what I read the main purpose of the IMEI is to be able to take measure=
s against stolen phones and against equipment which the use cannot be accep=
ted for technical or safety reasons. =A0The secondary purpose is the tracin=
g of malicious calls.<br>

<br>
There is an apps which sends the IMEI in a cryptographically-protected form=
 over the network. =A0For what it is worth, it&#39;s MD5.<br>
<br>
There has been some work in the IETF on emergency calls (see service URN).<=
div class=3D"im"><br>
<br>
At 00:12 21-07-2013, Andrew Allen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
As John pointed out having the sub namespace reviewed by IETF provides the =
opportunity to add text to address privacy concerns with any inappropriate =
usage.<br>
</blockquote>
<br></div>
I don&#39;t think that it is the role of the IETF to determine whether the =
usage of a sub-namespace is appropriate or not as it can cause namespace ma=
nagement issues.<br>
<br>
I tried the explain the subtlety between privacy concerns and privacy consi=
derations. =A0The IMEI can also be used as a customer identifier.<br>
<br>
Regards,<br>
S. Moonesamy =A0<br>
</blockquote></div><br></div>

--001a11c1e98008c97b04e4eeaffc--

From jabley@hopcount.ca  Tue Aug 27 08:59:46 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 351A521E80F0 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 08:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Level: 
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6LEt2xu4WNn for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 08:59:43 -0700 (PDT)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id A7C7C11E81A2 for <ietf@ietf.org>; Tue, 27 Aug 2013 08:59:43 -0700 (PDT)
Received: by mail-qa0-f54.google.com with SMTP id bn16so1184354qab.20 for <ietf@ietf.org>; Tue, 27 Aug 2013 08:59:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CgJjNsLuGYSj55CL2vsIwYQsbadOSrT09jJ/hys+SFE=; b=TaVPEcu77f2V8B8ttaj6/P9fLBs3tsMNTHWWjL9tkOnc85unzhQyf7ntcqY3Yt0UiT 9hBEo0q99i+no7gs1Nj+OtU/I5nRq8GfhWmXO2t2QHZwvFmPMzjdImt54IBmUzJ+qi10 qSuZtELxboTmxblAJvd5pZHzzSIs2qOygBV90=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=CgJjNsLuGYSj55CL2vsIwYQsbadOSrT09jJ/hys+SFE=; b=Ac8qPkDnU8tYawKqNN+y0ohN73xV+DMOKW7YCjMwq8eiY5gEN/sdc5BgFQit8CUUNT Ib8gdnQESQjj72lYJMoWewf00dr+8MqhBFlWOajcnP6RrNQRUA9JkHzxizO+4UHRBMSW TP1wYrxXzFdzZ6iBz7vcYsecMmq05qpMTCpxOX1HJSsD/z3VBskwiagFCJCoxTKEPjuC oorqAqIKuPZxWzE9xAnhc5/3s0MyCMP55oH7UVJ1Mcz9bISCY3Z/OKjWu13KUXRkLiRI RE5nHP/RDEUuw59mfVGL7RztuYvbcCEfFFtCa0fJi4sk1WtJqNOLzaoeE3AQPx784bNB uCqg==
X-Gm-Message-State: ALoCoQkfRK6zItkYoSGlOx3UnHsRzYMqfadZ8Pl7I4JAlerf99UqmR3EdwcVIoF3txZmAAipKATN
X-Received: by 10.224.74.4 with SMTP id s4mr23966072qaj.51.1377619183022; Tue, 27 Aug 2013 08:59:43 -0700 (PDT)
Received: from [199.212.90.52] ([135.23.68.78]) by mx.google.com with ESMTPSA id g3sm30144545qas.6.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 08:59:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6.2.5.6.2.20130826182352.0cac3298@elandnews.com>
Date: Tue, 27 Aug 2013 11:59:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 15:59:46 -0000

On 2013-08-26, at 22:28, S Moonesamy <sm+ietf@elandsys.com> wrote:

>> The permitted size of the UDP packet is NOT 512 octets.  That is the =
permitted size of the DNS Message.  DNS Message is not the same thing as =
a UDP packet.
>=20
>>>> Per RFC1035
>>>> Section 2.3.4. Size limits
>>>> UDP messages    512 octets or less
>=20
> I'll suggest UDP message.

The consistent word for this in 1035 is simply "message". "DNS Message" =
is in more common use today, I would say.

The text you quoted from 1035 is most usefully interpreted as a =
contraction of "messages sent over UDP"; "UDP message" really doesn't =
have a well-understood meaning, and is easily conflated with "UDP =
datagram" which does not have a size limitation of 512 bytes.


Joe


From david.black@emc.com  Tue Aug 27 09:41:40 2013
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 5870C11E81C0; Tue, 27 Aug 2013 09:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.934
X-Spam-Level: 
X-Spam-Status: No, score=-102.934 tagged_above=-999 required=5 tests=[AWL=-0.562, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IiqZ6gQLqXav; Tue, 27 Aug 2013 09:41:32 -0700 (PDT)
Received: from mexforward.lss.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0555511E8261; Tue, 27 Aug 2013 09:41:29 -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 r7RGf9PK002555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 12:41:12 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd06.lss.emc.com [10.254.222.130]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 27 Aug 2013 12:40:54 -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 r7RGeMR0007155; Tue, 27 Aug 2013 12:40:52 -0400
Received: from mx15a.corp.emc.com ([169.254.1.99]) by mxhub07.corp.emc.com ([128.222.70.204]) with mapi; Tue, 27 Aug 2013 12:40:49 -0400
From: "Black, David" <david.black@emc.com>
To: Ben Campbell <ben@nostrum.com>
Date: Tue, 27 Aug 2013 12:40:47 -0400
Subject: Gen-ART review of draft-ietf-dime-overload-reqs-11
Thread-Topic: Gen-ART review of draft-ietf-dime-overload-reqs-11
Thread-Index: Ac6jRC6xkQX5gZxLRrufngsSRaWGvQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7129C675453@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "Black, David" <david.black@emc.com>, Eric McMurry <emcmurry@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 16:41:41 -0000

The -11 version of this draft addresses all of the nits and editorial comme=
nts
noted in the Gen-ART review of the -10 version.  It's ready for publication=
 as
an Informational RFC.

Thanks,
--David

> -----Original Message-----
> From: Ben Campbell [mailto:ben@nostrum.com]
> Sent: Thursday, August 22, 2013 4:50 PM
> To: Black, David
> Cc: Eric McMurry; General Area Review Team (gen-art@ietf.org); ietf@ietf.=
org;
> dime@ietf.org; bclaise@cisco.com
> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>=20
> Hi David,
>=20
> We agree on all your points, and will make the updates in the next versio=
n,
> pending shepherd instructions. =20
>=20
> Thanks!
>=20
> Ben.
>=20
> On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> wrote:
>=20
> > Hi Eric,
> >
> > This looks good - comments follow ...
> >
> >>> a) I assume that overload control development work will derive more
> specific
> >>> security requirements - e.g., as REQ 27 is stated at a rather high le=
vel.
> >>> The discussion in security considerations section seems reasonable.
> >>
> >> We agree with this.  The thinking here was that we didn't want to spec=
ify this
> >> in a way that would be specific to a particular type of mechanism.  It=
 might
> >> not hurt to state that assumption, either as a note on Req 27 or in th=
e sec
> >> considerations.
> >
> > That would be good to add as a note on REQ 27.
> >
> >> The intent was very much as you say, where requirements on individual =
node
> >> capabilities are hoped to result in better overall system behaviors. T=
here are
> >> also some requirements that are stated more at the system level (e.g. =
7 and
> >> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
> >> insufficient server capacity at a cluster of servers behind a Diameter=
 agent
> >> can be treated as if the agent itself was overloaded.
> >>
> >> On the other hand, any mechanism we design will have to focus on actio=
ns of
> >> individual nodes, so the numbered requirements tend to focus on that. =
I'm not
> >> sure where to change the balance here--do you have specific suggestion=
s?
> >
> > I noted this as editorial rather than a minor issue, as I was mostly co=
ncerned
> > that the actual design work will be informed by a sufficient architectu=
ral "clue"
> > that the goal is "better overall system behaviors", which your response=
 indicates
> > will definitely be the case ;-).
> >
> > Rather than edit individual requirements, how about adding the followin=
g sentence
> > immediately following the introductory sentence in Section 7?:
> >
> > 	These requirements are stated primarily in terms of individual node
> > 	behavior to inform the design of the improved mechanism;
> > 	that design effort should keep in mind that the overall goal is
> > 	improved overall system behavior across all the nodes involved,
> > 	not just improved behavior from specific individual nodes.
> >
> >>> This inadequacy may, in turn, contribute to broader congestion collap=
se
> >>>
> >>> "collapse" is not the right word here - I suggest "issues", "impacts"=
,
> >>> "effects" or "problems".
> >>
> >> We are fine with any of those alternatives.  How about impacts.
> >
> > That's fine.  FWIW, "congestion collapse" has a specific (rather severe=
)
> > meaning over in the Transport Area, and that meaning was not intended h=
ere.
> >
> >> 23.843 is the least stable reference.  I don't have any issue with poi=
nting
> >> that out.  The part of it we are referencing is historical front matte=
r
> >> though.
> >
> > I'd note the reference as work in progress, and put the statement about=
 stable
> > front matter (historical is a bad work to use here) in the body of the =
draft
> > that cites the reference.
> >
> >> I tried the web and downloaded versions of 2.12.17 and was not able to=
 get the
> >> warnings you saw (about the references).  What did it say?
> >
> > Sorry, I didn't mean to send you on a wild goose chase :-).  The idnits=
 confusion
> > manifested right at the top of the output, where everyone ignores it ..=
.
> >
> >   Attempted to download rfc272 state...
> >   Failure fetching the file, proceeding without it.
> >
> > You didn't reference RFC 272, so that output's apparently courtesy of i=
dnits
> > misinterpreting this reference:
> >
> > 1195	   [TS29.272]
> > 1196	              3GPP, "Evolved Packet System (EPS); Mobility Managem=
ent
> > 1197	              Entity (MME) and Serving GPRS Support Node (SGSN) re=
lated
> > 1198	              interfaces based on Diameter protocol", TS 29.272 11=
.4.0,
> > 1199	              September 2012.
> >
> > I was amused :-).
> >
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Eric McMurry [mailto:emcmurry@computer.org]
> >> Sent: Thursday, August 22, 2013 3:06 PM
> >> To: Black, David
> >> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
> >> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
> >> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
> >>
> >> Hi David,
> >>
> >> Thank you for the review.  Your time and comments are appreciated!
> >>
> >> comments/questions inline.
> >>
> >>
> >> Eric
> >>
> >>
> >>
> >> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> wrote:
> >>
> >>>
> >>> I am the assigned Gen-ART reviewer for this draft. For background on
> >>> Gen-ART, please see the FAQ at
> >>>
> >>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>>
> >>> Please resolve these comments along with any other Last Call comments
> >>> you may receive.
> >>>
> >>> Document: draft-ietf-dime-overload-reqs-10
> >>> Reviewer: David L. Black
> >>> Review Date: August 17, 2013
> >>> IETF LC End Date: August 16, 2013
> >>> IESG Telechat date: (if known)
> >>>
> >>> Summary:
> >>> This draft is basically ready for publication, but has nits that shou=
ld be
> >>> fixed before publication.
> >>>
> >>> This draft describes scenarios in which Diameter overload can occur a=
nd
> provides
> >>> requirements for development of new overload control functionality in
> Diameter.
> >>> It is well written, and the inclusion of scenarios in which overload =
can
> occur,
> >>> both in terms of the relationships among types of Diameter nodes and
> actual mobile
> >>> network experience is very helpful.
> >>>
> >>> I apologize for this review being a day late, as I've been on vacatio=
n for
> most
> >>> of this draft's IETF Last Call period.
> >>>
> >>> Major issues: (none)
> >>>
> >>> Minor issues: (none)
> >>>
> >>> Nits/editorial comments:
> >>>
> >>> The following two comments could be minor issues, but I'm going to tr=
eat
> them
> >>> as editorial, as I expect that they will be addressed in development =
of
> the
> >>> actual overload functionality:
> >>>
> >>> a) I assume that overload control development work will derive more
> specific
> >>> security requirements - e.g., as REQ 27 is stated at a rather high le=
vel.
> >>> The discussion in security considerations section seems reasonable.
> >>
> >> We agree with this.  The thinking here was that we didn't want to spec=
ify
> this
> >> in a way that would be specific to a particular type of mechanism.  It
> might
> >> not hurt to state that assumption, either as a note on Req 27 or in th=
e sec
> >> considerations.
> >>
> >>>
> >>> b) The draft, and especially its requirements in Section 7 are strong=
ly
> >>> focused on individual Diameter node overload.  That's necessary, but
> overload
> >>> conditions can be broader, affecting an entire service or application=
, or
> >>> multiple instances of either/both, even if not every individual Diame=
ter
> node
> >>> involved is overloaded.  A number of the requirements, starting with =
REQ
> 22
> >>> could be generalized to cover broader overload conditions.
> >>>
> >>> This (b) has implications for other requirements, e.g., REQ 13 should=
 also
> be
> >>> generalized beyond a single node to avoid increased traffic in an ove=
rload
> >>> situation, even from a node that is not overloaded by itself.  There =
are
> limits
> >>> on what is reasonable here, as the desired overload functionality is
> TCP/SCTP-
> >>> like reaction to congestion where individual actions taken by nodes b=
ased
> on
> >>> the information they have (which is not the complete state of the net=
work)
> >>> results in an overall reduction of load.
> >>
> >> The intent was very much as you say, where requirements on individual =
node
> >> capabilities are hoped to result in better overall system behaviors. T=
here
> are
> >> also some requirements that are stated more at the system level (e.g. =
7 and
> >> 17.) Also the text in section 2.2 that discusses Figure 5 talks about =
how
> >> insufficient server capacity at a cluster of servers behind a Diameter
> agent
> >> can be treated as if the agent itself was overloaded.
> >>
> >> On the other hand, any mechanism we design will have to focus on actio=
ns of
> >> individual nodes, so the numbered requirements tend to focus on that. =
I'm
> not
> >> sure where to change the balance here--do you have specific suggestion=
s?
> >>
> >>>
> >>> Section 1.2, 2nd paragraph:
> >>>
> >>>  as network congestion, network congestion can reduce a Diameter node=
s
> >>>
> >>> "nodes" -> "node's"
> >>
> >> good catch.
> >>
> >>>
> >>> Section 5, 1st paragraph:
> >>>
> >>> This inadequacy may, in turn, contribute to broader congestion collap=
se
> >>>
> >>> "collapse" is not the right word here - I suggest "issues", "impacts"=
,
> >>> "effects" or "problems".
> >>
> >> We are fine with any of those alternatives.  How about impacts.
> >>
> >>>
> >>> Section 7
> >>>
> >>> The long enumerated list of requirements is not an easy read.  It wou=
ld be
> >>> better if these could somehow be grouped by functional category, e.g.=
,
> >>> security, transport interactions, operational/administrative, etc.
> >>
> >> agree.  It is actually in sections in the XML (denoted by comments), w=
e
> just
> >> did not promote those to visible sections in the txt.  I recall there =
being
> >> some issue with xml2rfc and numbering, but now that the numbers are se=
t,
> this
> >> would not be hard to do.
> >>
> >>
> >>>
> >>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - this i=
s
> fine,
> >>> as the boilerplate has been appropriately modified for this draft tha=
t
> >>> expresses requirements (as opposed to a draft that specifies a protoc=
ol).
> >>>
> >>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative Referenc=
es.
> >>> I assume that they're all sufficiently stable to be informative
> references.
> >>> However, [TR23.843] is a work in progress, and should be noted as suc=
h in
> >>> its reference - is this needed for any of the other 3GPP or GSMA
> references?
> >>
> >> 23.843 is the least stable reference.  I don't have any issue with poi=
nting
> >> that out.  The part of it we are referencing is historical front matte=
r
> >> though.
> >>
> >>
> >> I tried the web and downloaded versions of 2.12.17 and was not able to=
 get
> the
> >> warnings you saw (about the references).  What did it say?
> >>
> >>
> >>>
> >>> 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        Mobile: +1 (978) 394-7754
> >>> ----------------------------------------------------
> >>>
> >>
> >
>=20


From Ted.Lemon@nominum.com  Tue Aug 27 10:11:42 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FF5C21E8056 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.287
X-Spam-Level: 
X-Spam-Status: No, score=-106.287 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, 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 xJk895wDwKR5 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:11:35 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id B3F4021E808D for <ietf@ietf.org>; Tue, 27 Aug 2013 10:11:31 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUhzdvpe89Mgr1c89A/hGnMJT7qECzjWB@postini.com; Tue, 27 Aug 2013 10:11:31 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 36FD51B82C0 for <ietf@ietf.org>; Tue, 27 Aug 2013 10:11:26 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2E48519006C; Tue, 27 Aug 2013 10:11:26 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 27 Aug 2013 10:11:26 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: Rude responses (sergeant-at-arms?)
Thread-Topic: Rude responses (sergeant-at-arms?)
Thread-Index: AQHOoxN06q2ItRANekqU0K4uK4hKvZmpwB4A
Date: Tue, 27 Aug 2013 17:11:25 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <9EBD9FDAB74877448812B83FD40C1915@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:11:42 -0000

FWIW, if we are going to go down that road, it would be worth noting that t=
here are various kinds of rudeness that can occur on IETF mailing lists.   =
To my mind, the most harmful of these is not outright rudeness.   Outright =
rudeness is to be avoided, certainly.

But the most rude behavior that ever occurs on IETF mailing lists is not li=
stening.   Not trying to understand what the person who is speaking to you =
has said.   Not trying to figure out if what they said meaningfully contrad=
icts your own position, and not making a sincere effort to determine if the=
y might be correct in contradicting your position.

We have seen some incredible rudeness of this type in the recent spfbis dis=
cussion, with various supposedly smart people in our community utterly igno=
ring what their opponents are saying, and simply re-asserting their own pos=
ition in a variety of ways.

I would expect the sergeant-at-arms to be reining in that sort of rudeness =
before reining in the sort of supposed overt rudeness that we are discussin=
g here.   The endless litany of repeats of already-addressed discussion poi=
nts raised on the spfbis mailing list has been incredibly harmful to discou=
rse on the ietf mailing list.   This exchange between l.wood and Abdussalam=
 Baryun pales in comparison.

Furthermore, I would also point out that criticism of someone's behavior is=
 not rudeness, if that criticism is accurate.   I don't think the IETF shou=
ld be a context in which people ought to feel safe in behaving badly, as lo=
ng as they behave badly in ways that are subtle enough not to be considered=
 impolite.  Nor should it be a context in which failure to behave according=
 to some culturally-relative standard of politeness in itself invalidates a=
n otherwise valid statement.


From ben@nostrum.com  Tue Aug 27 10:18:15 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4016521E8085; Tue, 27 Aug 2013 10:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level: 
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, 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 Acw0vuiredUW; Tue, 27 Aug 2013 10:18:14 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id C1B4021E8056; Tue, 27 Aug 2013 10:18:13 -0700 (PDT)
Received: from [10.0.1.27] (cpe-76-187-89-238.tx.res.rr.com [76.187.89.238]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r7RHI271080461 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 27 Aug 2013 12:18:03 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-11
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
Date: Tue, 27 Aug 2013 12:18:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E777B5F-BF39-4F12-BB93-5E55342BA93A@nostrum.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Received-SPF: pass (shaman.nostrum.com: 76.187.89.238 is authenticated by a trusted mechanism)
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Eric McMurry <emcmurry@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:18:15 -0000

Thanks, David!

On Aug 27, 2013, at 11:40 AM, "Black, David" <david.black@emc.com> =
wrote:

> The -11 version of this draft addresses all of the nits and editorial =
comments
> noted in the Gen-ART review of the -10 version.  It's ready for =
publication as
> an Informational RFC.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, August 22, 2013 4:50 PM
>> To: Black, David
>> Cc: Eric McMurry; General Area Review Team (gen-art@ietf.org); =
ietf@ietf.org;
>> dime@ietf.org; bclaise@cisco.com
>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>=20
>> Hi David,
>>=20
>> We agree on all your points, and will make the updates in the next =
version,
>> pending shepherd instructions. =20
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>> On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> =
wrote:
>>=20
>>> Hi Eric,
>>>=20
>>> This looks good - comments follow ...
>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify this
>>>> in a way that would be specific to a particular type of mechanism.  =
It might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>=20
>>> That would be good to add as a note on REQ 27.
>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>=20
>>> I noted this as editorial rather than a minor issue, as I was mostly =
concerned
>>> that the actual design work will be informed by a sufficient =
architectural "clue"
>>> that the goal is "better overall system behaviors", which your =
response indicates
>>> will definitely be the case ;-).
>>>=20
>>> Rather than edit individual requirements, how about adding the =
following sentence
>>> immediately following the introductory sentence in Section 7?:
>>>=20
>>> 	These requirements are stated primarily in terms of individual =
node
>>> 	behavior to inform the design of the improved mechanism;
>>> 	that design effort should keep in mind that the overall goal is
>>> 	improved overall system behavior across all the nodes involved,
>>> 	not just improved behavior from specific individual nodes.
>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>=20
>>> That's fine.  FWIW, "congestion collapse" has a specific (rather =
severe)
>>> meaning over in the Transport Area, and that meaning was not =
intended here.
>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>=20
>>> I'd note the reference as work in progress, and put the statement =
about stable
>>> front matter (historical is a bad work to use here) in the body of =
the draft
>>> that cites the reference.
>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>>>> warnings you saw (about the references).  What did it say?
>>>=20
>>> Sorry, I didn't mean to send you on a wild goose chase :-).  The =
idnits confusion
>>> manifested right at the top of the output, where everyone ignores it =
...
>>>=20
>>>  Attempted to download rfc272 state...
>>>  Failure fetching the file, proceeding without it.
>>>=20
>>> You didn't reference RFC 272, so that output's apparently courtesy =
of idnits
>>> misinterpreting this reference:
>>>=20
>>> 1195	   [TS29.272]
>>> 1196	              3GPP, "Evolved Packet System (EPS); =
Mobility Management
>>> 1197	              Entity (MME) and Serving GPRS Support Node =
(SGSN) related
>>> 1198	              interfaces based on Diameter protocol", TS =
29.272 11.4.0,
>>> 1199	              September 2012.
>>>=20
>>> I was amused :-).
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>> -----Original Message-----
>>>> From: Eric McMurry [mailto:emcmurry@computer.org]
>>>> Sent: Thursday, August 22, 2013 3:06 PM
>>>> To: Black, David
>>>> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
>>>> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
>>>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>>>=20
>>>> Hi David,
>>>>=20
>>>> Thank you for the review.  Your time and comments are appreciated!
>>>>=20
>>>> comments/questions inline.
>>>>=20
>>>>=20
>>>> Eric
>>>>=20
>>>>=20
>>>>=20
>>>> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> =
wrote:
>>>>=20
>>>>>=20
>>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>>> Gen-ART, please see the FAQ at
>>>>>=20
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>=20
>>>>> Please resolve these comments along with any other Last Call =
comments
>>>>> you may receive.
>>>>>=20
>>>>> Document: draft-ietf-dime-overload-reqs-10
>>>>> Reviewer: David L. Black
>>>>> Review Date: August 17, 2013
>>>>> IETF LC End Date: August 16, 2013
>>>>> IESG Telechat date: (if known)
>>>>>=20
>>>>> Summary:
>>>>> This draft is basically ready for publication, but has nits that =
should be
>>>>> fixed before publication.
>>>>>=20
>>>>> This draft describes scenarios in which Diameter overload can =
occur and
>> provides
>>>>> requirements for development of new overload control functionality =
in
>> Diameter.
>>>>> It is well written, and the inclusion of scenarios in which =
overload can
>> occur,
>>>>> both in terms of the relationships among types of Diameter nodes =
and
>> actual mobile
>>>>> network experience is very helpful.
>>>>>=20
>>>>> I apologize for this review being a day late, as I've been on =
vacation for
>> most
>>>>> of this draft's IETF Last Call period.
>>>>>=20
>>>>> Major issues: (none)
>>>>>=20
>>>>> Minor issues: (none)
>>>>>=20
>>>>> Nits/editorial comments:
>>>>>=20
>>>>> The following two comments could be minor issues, but I'm going to =
treat
>> them
>>>>> as editorial, as I expect that they will be addressed in =
development of
>> the
>>>>> actual overload functionality:
>>>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify
>> this
>>>> in a way that would be specific to a particular type of mechanism.  =
It
>> might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>>=20
>>>>>=20
>>>>> b) The draft, and especially its requirements in Section 7 are =
strongly
>>>>> focused on individual Diameter node overload.  That's necessary, =
but
>> overload
>>>>> conditions can be broader, affecting an entire service or =
application, or
>>>>> multiple instances of either/both, even if not every individual =
Diameter
>> node
>>>>> involved is overloaded.  A number of the requirements, starting =
with REQ
>> 22
>>>>> could be generalized to cover broader overload conditions.
>>>>>=20
>>>>> This (b) has implications for other requirements, e.g., REQ 13 =
should also
>> be
>>>>> generalized beyond a single node to avoid increased traffic in an =
overload
>>>>> situation, even from a node that is not overloaded by itself.  =
There are
>> limits
>>>>> on what is reasonable here, as the desired overload functionality =
is
>> TCP/SCTP-
>>>>> like reaction to congestion where individual actions taken by =
nodes based
>> on
>>>>> the information they have (which is not the complete state of the =
network)
>>>>> results in an overall reduction of load.
>>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There
>> are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter
>> agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm
>> not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>>=20
>>>>>=20
>>>>> Section 1.2, 2nd paragraph:
>>>>>=20
>>>>> as network congestion, network congestion can reduce a Diameter =
nodes
>>>>>=20
>>>>> "nodes" -> "node's"
>>>>=20
>>>> good catch.
>>>>=20
>>>>>=20
>>>>> Section 5, 1st paragraph:
>>>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>>=20
>>>>>=20
>>>>> Section 7
>>>>>=20
>>>>> The long enumerated list of requirements is not an easy read.  It =
would be
>>>>> better if these could somehow be grouped by functional category, =
e.g.,
>>>>> security, transport interactions, operational/administrative, etc.
>>>>=20
>>>> agree.  It is actually in sections in the XML (denoted by =
comments), we
>> just
>>>> did not promote those to visible sections in the txt.  I recall =
there being
>>>> some issue with xml2rfc and numbering, but now that the numbers are =
set,
>> this
>>>> would not be hard to do.
>>>>=20
>>>>=20
>>>>>=20
>>>>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - =
this is
>> fine,
>>>>> as the boilerplate has been appropriately modified for this draft =
that
>>>>> expresses requirements (as opposed to a draft that specifies a =
protocol).
>>>>>=20
>>>>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
>>>>> I assume that they're all sufficiently stable to be informative
>> references.
>>>>> However, [TR23.843] is a work in progress, and should be noted as =
such in
>>>>> its reference - is this needed for any of the other 3GPP or GSMA
>> references?
>>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>>=20
>>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get
>> the
>>>> warnings you saw (about the references).  What did it say?
>>>>=20
>>>>=20
>>>>>=20
>>>>> 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        Mobile: +1 (978) 394-7754
>>>>> ----------------------------------------------------
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20


From scott.brim@gmail.com  Tue Aug 27 10:21:02 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55AFF21E809F for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.922
X-Spam-Level: 
X-Spam-Status: No, score=-101.922 tagged_above=-999 required=5 tests=[AWL=0.677, 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 QNGaA6HPgqG1 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:21:00 -0700 (PDT)
Received: from mail-ea0-x236.google.com (mail-ea0-x236.google.com [IPv6:2a00:1450:4013:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id A722621E809B for <ietf@ietf.org>; Tue, 27 Aug 2013 10:20:59 -0700 (PDT)
Received: by mail-ea0-f182.google.com with SMTP id o10so2453936eaj.27 for <ietf@ietf.org>; Tue, 27 Aug 2013 10:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=SPpku6MFg9bmJGX45uNZRn6nxZMkhYVdbgmlngUmWHY=; b=WggsHL11SZyuek+nWKvZl2UqSgFEVn7/sGwqt9KiUqQRURjuXscnbX4yDY2biDKDX/ UpE06S1mIqq96/Nfu7fPBsOHKCPq3wiB+IvZo8k3R/KuhEvoPkwlHQX22HTNKK49Lkil Kdc1sOPblVwe+QIk/P4iSPRabYH8T7NNGM0z4um9ecDiN/uFphZ340AwrDfvPVBeXdiL umoS6WuyvWHBQez0aerg+5ok9vkEk1D5zr2ssqkgi77PIoBgc6/7OA498Xs2++Y+Ot9J +NiaXbzsNl+twOH+ZC5sQ7jJxITd0Hra4hQcKa1Y5xOP8Ev1lC6KnXY9sXAYS91dWts9 KySA==
X-Received: by 10.15.75.73 with SMTP id k49mr35735693eey.36.1377624058826; Tue, 27 Aug 2013 10:20:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.218.1 with HTTP; Tue, 27 Aug 2013 10:20:38 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 27 Aug 2013 13:20:38 -0400
Message-ID: <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com>
Subject: Re: Rude responses (sergeant-at-arms?)
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c1af4ca9347d04e4f118f9
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:21:02 -0000

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

On Tue, Aug 27, 2013 at 1:11 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> But the most rude behavior that ever occurs on IETF mailing lists is not
> listening.   Not trying to understand what the person who is speaking to
> you has said.   Not trying to figure out if what they said meaningfully
> contradicts your own position, and not making a sincere effort to determine
> if they might be correct in contradicting your position.
>
> We have seen some incredible rudeness of this type in the recent spfbis
> discussion, with various supposedly smart people in our community utterly
> ignoring what their opponents are saying, and simply re-asserting their own
> position in a variety of ways.
>
> I would expect the sergeant-at-arms to be reining in that sort of rudeness
> before reining in the sort of supposed overt rudeness that we are
> discussing here.   The endless litany of repeats of already-addressed
> discussion points raised on the spfbis mailing list has been incredibly
> harmful to discourse on the ietf mailing list.


IMHO that's not a job for the sergeant at arms.  The SAA is responsible for
how things are said.  The shepherd -- or supershepherd or whatever -- would
be responsible for the substance.

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

<div dir=3D"ltr">On Tue, Aug 27, 2013 at 1:11 PM, Ted Lemon <span dir=3D"lt=
r">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon=
@nominum.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">But the most rude behavior that ever occurs =
on IETF mailing lists is not listening. =A0 Not trying to understand what t=
he person who is speaking to you has said. =A0 Not trying to figure out if =
what they said meaningfully contradicts your own position, and not making a=
 sincere effort to determine if they might be correct in contradicting your=
 position.<br>


<br>
We have seen some incredible rudeness of this type in the recent spfbis dis=
cussion, with various supposedly smart people in our community utterly igno=
ring what their opponents are saying, and simply re-asserting their own pos=
ition in a variety of ways.<br>


<br>
I would expect the sergeant-at-arms to be reining in that sort of rudeness =
before reining in the sort of supposed overt rudeness that we are discussin=
g here. =A0 The endless litany of repeats of already-addressed discussion p=
oints raised on the spfbis mailing list has been incredibly harmful to disc=
ourse on the ietf mailing list. =A0=A0</blockquote>

<div><br></div><div>IMHO that&#39;s not a job for the sergeant at arms. =A0=
The SAA is responsible for how things are said. =A0The shepherd -- or super=
shepherd or whatever -- would be responsible for the substance.=A0</div></d=
iv>

</div></div>

--001a11c1af4ca9347d04e4f118f9--

From sm@elandsys.com  Tue Aug 27 10:28:28 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 991FB11E8243 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLHEpZ-Zs3En for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:28:28 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D4E11E81CC for <ietf@ietf.org>; Tue, 27 Aug 2013 10:28:26 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.139.183]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7RHS6NF017540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 10:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377624499; bh=D+fenJjiqSI+UyptUKXdSsf7ZnRnxHDMlZr5J5y/3OE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=H7Tla303wGRokLFyPkLEdFcnyvIBPsVGhN8dWtbQpsC1QgXEKeGfJrTT0Jh64Gbva v4ox7vfE+BAeDRxBjBRYDDr9aSv9WKvPfp6OOBEgBafvIshfOCwetxtOSbVJhpIw8t Y9t6wicfHNSS6hBIRCpIKNYPMSJzXxZ34/4YJcCM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377624499; i=@elandsys.com; bh=D+fenJjiqSI+UyptUKXdSsf7ZnRnxHDMlZr5J5y/3OE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=J1ezLFZYXMTAmlR9xE2YT+5TQKCtUkNumOn2kdTUlOn1kla4icX6DzlHVw9qpwUu6 8DX08A5U8BITG7FERenQXuQ8+F57lhLQfLdJv6ksGvBCHkow6n7bdFSAnM08q5ZioR 0VzWwTSiSu8IWquZXU/cXndMbMvyGrSoMyV3UiYU=
Message-Id: <6.2.5.6.2.20130827080040.0d579578@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 27 Aug 2013 08:20:54 -0700
To: Mary Barnes <mary.h.barnes@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
In-Reply-To: <CABmDk8nmQLY1mBbpECjo7KLULXyEvXYNgDiOVjuH6mgy-sDL9w@mail.g mail.com>
References: <6.2.5.6.2.20130720193906.06cdd008@resistor.net> <BBF5DDFE515C3946BC18D733B20DAD2338DD2606@XMB104ADS.rim.net> <6.2.5.6.2.20130721070808.0c808140@elandnews.com> <CABmDk8nmQLY1mBbpECjo7KLULXyEvXYNgDiOVjuH6mgy-sDL9w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john@jck.com>, tbray@textuality.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, 27 Aug 2013 17:28:28 -0000

Hi Mary,
At 07:28 27-08-2013, Mary Barnes wrote:
>As far as the IPR, as the shepherd and DISPATCH WG co-chair, I 
>posted a note to the DISPATCH WG mailing list before progressing 
>this document to see if anyone had any concerns about the IPR 
>disclosures, which had been discussed in the past and were updated 
>when I asked the authors the requisite questions about IPR while 
>doing the PROTO write-up.  No concerns were raised with regards to 
>the updated IPR disclosures (i.e., no one responded to that 
>email).     And, you can google  "draft montemurro ietf ipr 
>archives" to find past discussions such as this one:  draft 
>montemurro ietf ipr archives

Thanks for the feedback.  Somebody commented that:

   "It has nothing to do with IPR which was extensively discussed on
    the dispatch list."

I read the DISPATCH mailing list archives.  I did not see that 
extensive discussion.  My comment was about that.  I do not have any 
problem with the document shepherd comments.

Regards,
S. Moonesamy 


From sm@elandsys.com  Tue Aug 27 10:28:43 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD9811E8348 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IrgEoCoaa3IZ for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:28:42 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA69011E81CD for <ietf@ietf.org>; Tue, 27 Aug 2013 10:28:40 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.139.183]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7RHS6NJ017540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 10:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377624508; bh=aqoOdAUyQ6AgYyMYEcoa6zT2TSp/9bgtVNMQN/+lYD8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=P5q6sqzIvwEBCE5+eDkWwNYN7ws2lAEym2kB9hLWg+rC0YBBp/v+JP9nNjOU3NyU7 G1gIW34gzjAeEG9Hh7AEYjIR7EfcADr+8V9Z9Ug1Vc3hwlyka2Ry17kC97bQTxqf47 IGLDLJXedyRAnzuD1BbSaAyxJG9WuLLDdZDgkTwU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377624508; i=@elandsys.com; bh=aqoOdAUyQ6AgYyMYEcoa6zT2TSp/9bgtVNMQN/+lYD8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vQuWeUpvoiG5Jffw/t/sDiZ3pUfpY4OUdLGylDKrwDkCtbRENZd9sCJblyeIrXnxa 9GD41kHKE6stw2xyAF8OsQKwGLx8yL3kjy9kojFx/UPMk2yF8DHW86GGoD3LisuR7g Q9bFHXh2/KTNBPB/ioOLIng+MKQmem/k/FnBs1vI=
Message-Id: <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 27 Aug 2013 09:43:49 -0700
To: Joe Abley <jabley@hopcount.ca>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca>
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, 27 Aug 2013 17:28:44 -0000

Hi Joe,
At 08:59 27-08-2013, Joe Abley wrote:
>The consistent word for this in 1035 is simply "message". "DNS 
>Message" is in more common use today, I would say.
>
>The text you quoted from 1035 is most usefully interpreted as a 
>contraction of "messages sent over UDP"; "UDP message" really 
>doesn't have a well-understood meaning, and is easily conflated with 
>"UDP datagram" which does not have a size limitation of 512 bytes.

Thanks for explaining this.  Please note that I personally agree with 
what you wrote.

My understanding is that the text in Section 3.4 is trying to say DNS 
messages over UDP.  There was some discussion about that (see 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03088.html 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03090.html 
http://www.ietf.org/mail-archive/web/spfbis/current/msg03109.html ).

Regards,
S. Moonesamy (as document shepherd) 


From melinda.shore@gmail.com  Tue Aug 27 10:31:33 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 837D211E81CD for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ftt3cl4-d53a for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:31:32 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0B80821F9F2D for <ietf@ietf.org>; Tue, 27 Aug 2013 10:31:22 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id mc17so5133764pbc.32 for <ietf@ietf.org>; Tue, 27 Aug 2013 10:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XO6wlo8y3kbsrZUcN14IYgBx8he4X/QGMeMG3kT9FNc=; b=RHJ+ulGOfdBQem2BzSZlkg8Z7A9BQjOYO9tXlKvjt1KK1r73Pqkpnj59FBbzxgd5ta NekGt4/m+oUgloXmVuvmngKaMKBqphcaw4SdZqgL1jeSxQyUgaZKsgQprbKbJs5J5v0g RCVQxfhTEWcIpAseQTgjb79h9Ubr6zk8OO1TxGrmegydz7u8MCgxe9B09VrMDcry6psx lSVOIod4QiuiQ4DXN/SQL86epTd+HKX0aomckuu2sMZXKKZo68CXjzwD4aLytLwBNzUV EviPJXhAUHA1eMyfttuH6OGFaoSXigwMcRqk0buz1MH4TLV0yPW6B8vzPg3+EOuOD0xK Vb3g==
X-Received: by 10.68.241.198 with SMTP id wk6mr22700872pbc.122.1377624678223;  Tue, 27 Aug 2013 10:31:18 -0700 (PDT)
Received: from spandex.local (66-230-84-31-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.84.31]) by mx.google.com with ESMTPSA id ta10sm28223925pab.5.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 10:31:17 -0700 (PDT)
Message-ID: <521CE263.3090209@gmail.com>
Date: Tue, 27 Aug 2013 09:31:15 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Rude responses (sergeant-at-arms?)
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:31:34 -0000

On 8/27/13 9:11 AM, Ted Lemon wrote:
> I would expect the sergeant-at-arms to be reining in that sort of
> rudeness before reining in the sort of supposed overt rudeness that
> we are discussing here.  

That suggestion makes me want to say something a little rude.
Managing the discussion is the chair's job, not the sergeant-
at-arms's.

Melinda

From Ted.Lemon@nominum.com  Tue Aug 27 10:33:07 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C5011E82A4 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:33:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQmfehgO7Buh for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 10:33:00 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 680F911E824D for <ietf@ietf.org>; Tue, 27 Aug 2013 10:32:58 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUhziyrhd1Zkwpi60XQDLfr8yd9MSKkSm@postini.com; Tue, 27 Aug 2013 10:32:58 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 079C31B82D4 for <ietf@ietf.org>; Tue, 27 Aug 2013 10:32:58 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F3B1419006C; Tue, 27 Aug 2013 10:32:57 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 27 Aug 2013 10:32:58 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Rude responses (sergeant-at-arms?)
Thread-Topic: Rude responses (sergeant-at-arms?)
Thread-Index: AQHOoxN06q2ItRANekqU0K4uK4hKvZmpwB4AgAACkgCAAANxgA==
Date: Tue, 27 Aug 2013 17:32:56 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com> <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com>
In-Reply-To: <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5A6C11BF7EFF5D4DAD062A8B00A7C9AE@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 17:33:07 -0000

On Aug 27, 2013, at 1:20 PM, Scott Brim <scott.brim@gmail.com> wrote:
> IMHO that's not a job for the sergeant at arms.  The SAA is responsible f=
or how things are said.  The shepherd -- or supershepherd or whatever -- wo=
uld be responsible for the substance.=20

I think it should be fairly obvious even to one not practiced in the art th=
at a lot of the postings to the ietf mailing list recently have been simple=
 repeats of points previously made, with no additional substance, which, we=
ll intentioned or not, purely have the effect of making it harder to evalua=
te consensus.   But sure, the responsible AD could also intervene.


From aallen@blackberry.com  Tue Aug 27 11:30:07 2013
Return-Path: <aallen@blackberry.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4BDD11E8134 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 11:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.203
X-Spam-Level: 
X-Spam-Status: No, score=-5.203 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 iAXsICPKxRwc for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 11:30:02 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8F06711E81D5 for <ietf@ietf.org>; Tue, 27 Aug 2013 11:30:02 -0700 (PDT)
X-AuditID: 0a41282f-b7f8b6d000004656-31-521cf01c3445
Received: from XCT102ADS.rim.net (xct102ads.rim.net [10.67.111.43]) by mhs060cnc.rim.net (SBG) with SMTP id 67.3F.18006.D10FC125; Tue, 27 Aug 2013 13:29:49 -0500 (CDT)
Received: from XMB104ADS.rim.net ([fe80::2494:a63d:e3:723b]) by XCT102ADS.rim.net ([fe80::4806:2e1d:2b7c:cfdf%22]) with mapi id 14.03.0123.003; Tue, 27 Aug 2013 13:29:48 -0500
From: Andrew Allen <aallen@blackberry.com>
To: "sm+ietf@elandsys.com" <sm+ietf@elandsys.com>, "mary.h.barnes@gmail.com" <mary.h.barnes@gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Topic: Last call: draft-montemurro-gsma-imei-urn-16.txt
Thread-Index: AQHOozkF4fYTwuVTOkCw8MDTXs0bMZmpYGAN
Date: Tue, 27 Aug 2013 18:29:48 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD2338E0636E@XMB104ADS.rim.net>
In-Reply-To: <6.2.5.6.2.20130827080040.0d579578@elandnews.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.110.252]
Content-Type: text/plain; charset="iso-8859-1"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrJKsWRmVeSWpSXmKPExsXC5ZyvrSv7QSbI4PB/dotnG+ezWFw+uYbd Yu+t38wWr/pvslos/TOfxYHV496bj0weO2fdZfdYsuQnk8flla+ZPS4tncwcwBrVwGiTmJeX X5JYkqqQklqcbKvkk5qemKMQUJRZlphcqeCSWZyck5iZm1qkpJCZYqtkoqRQkJOYnJqbmldi q5RYUJCal6Jkx6WAAWyAyjLzFFLzkvNTMvPSbZU8g/11LSxMLXUNlex0kUDCP+6M/j97mArW 8VR8eHqdtYGxi6uLkZNDQsBE4s6W6UwQtpjEhXvr2boYuTiEBFYySqz4tQDK2cwoMfvlNXaQ KjYBLYn9hyE6RAQyJDZvfwcWZxYoljhy9xobiC0sYCtx+fQfRogaO4nvBy+xQNhGEhfnrQGz WQRUJdrOrwar4RXwkLi66C4ziM0JVD9vwzaw+YwCshK7z15ngpgvLnHryXyoSwUkluw5zwxh i0q8fPyPFcJWlHjc0s0CUa8ncWPqFDYIW1ti2cLXzBC7BCVOznzCMoFRdBaSsbOQtMxC0jIL ScsCRpZVjIK5GcUGZgbJecl6RZm5enmpJZsYQcnEUUN/B+Pb9xaHGAU4GJV4eJc/lwkSYk0s K67MPcQowcGsJMJ74DRQiDclsbIqtSg/vqg0J7X4EKMrMCQmMktxJ+cDE11eSbyxgQFujpI4 r6vKh0AhgXRgUspOTS1ILYKZw8TBKdXAGLv0ROej14Ze5qzqBzI4Nx+95GT6cIGO36n3E7dV SnxxOmtpIhUtU840vYbv20XXG38i3xVeiu6YG/1m47XJ8t9fTr9/4/KaNOsV000Wtmk+0RA6 /+7yUceLlg5dD5ZmMftdMtdXnMXe7db57YXz9BaJiRaps2fmnbiivGH5hCOe/u/8Hr3WclBi Kc5INNRiLipOBAD7ZGTGTAMAAA==
Cc: "john@jck.com" <john@jck.com>, "tbray@textuality.com" <tbray@textuality.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, 27 Aug 2013 18:30:08 -0000

SM

The past discussions on this took place a couple of years ago involving prim=
arily Cullen Jennings, Dale Worley and myself.

Andrew 

----- Original Message -----
From: S Moonesamy [mailto:sm+ietf@elandsys.com]
Sent: Tuesday, August 27, 2013 10:20 AM Central Standard Time=0A=
To: Mary Barnes <mary.h.barnes@gmail.com>
Cc: John C Klensin <john@jck.com>; tbray@textuality.com <tbray@textuality.co=
m>; ietf@ietf.org <ietf@ietf.org>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

Hi Mary,
At 07:28 27-08-2013, Mary Barnes wrote:
>As far as the IPR, as the shepherd and DISPATCH WG co-chair, I 
>posted a note to the DISPATCH WG mailing list before progressing 
>this document to see if anyone had any concerns about the IPR 
>disclosures, which had been discussed in the past and were updated 
>when I asked the authors the requisite questions about IPR while 
>doing the PROTO write-up.  No concerns were raised with regards to 
>the updated IPR disclosures (i.e., no one responded to that 
>email).     And, you can google  "draft montemurro ietf ipr 
>archives" to find past discussions such as this one:  draft 
>montemurro ietf ipr archives

Thanks for the feedback.  Somebody commented that:

   "It has nothing to do with IPR which was extensively discussed on
    the dispatch list."

I read the DISPATCH mailing list archives.  I did not see that 
extensive discussion.  My comment was about that.  I do not have any 
problem with the document shepherd comments.

Regards,
S. Moonesamy 


---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential infor=
mation, privileged material (including material protected by the solicitor-c=
lient or other applicable privileges), or constitute non-public information.=
 Any use of this information by anyone other than the intended recipient is=
 prohibited. If you have received this transmission in error, please immedia=
tely reply to the sender and delete this information from your system. Use,=
 dissemination, distribution, or reproduction of this transmission by uninte=
nded recipients is not authorized and may be unlawful.

From john@jlc.net  Tue Aug 27 12:09:03 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FEE521F9C6B for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 12:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.291
X-Spam-Level: 
X-Spam-Status: No, score=-106.291 tagged_above=-999 required=5 tests=[AWL=0.308, 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 mh94wHQAJA5L for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 12:08:58 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 08BAE21F967A for <ietf@ietf.org>; Tue, 27 Aug 2013 12:08:58 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 628ED33C2A; Tue, 27 Aug 2013 15:08:57 -0400 (EDT)
Date: Tue, 27 Aug 2013 15:08:57 -0400
From: John Leslie <john@jlc.net>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Rude responses (sergeant-at-arms?)
Message-ID: <20130827190857.GA48013@verdi>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com> <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com>
User-Agent: Mutt/1.4.1i
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, 27 Aug 2013 19:09:03 -0000

Ted Lemon <Ted.Lemon@nominum.com> wrote:
> 
> I think it should be fairly obvious even to one not practiced in the art
> that a lot of the postings to the ietf mailing list recently have been
> simple repeats of points previously made, with no additional substance,

   +1

   Alas, that statement applies to both posts which raise issues and
posts which refute issues.

> which, well intentioned or not, purely have the effect of making it
> harder to evaluate consensus.

   I feel sorry for Ted, who _does_ have to evaluate consensus here.

   For better or worse, current RFCs in standards track have boilerplate
saying
" 
" This document is a product of the Internet Engineering Task Force
" (IETF).  It represents the consensus of the IETF community...

   Unless and until this boilerplate changes, IESG members have an
obligation to try to decide whether that statement is true.

   I'm _very_ glad I don't have that obligation!

--
John Leslie <john@jlc.net>

From sm@elandsys.com  Tue Aug 27 12:35:40 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584B611E8175 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 12:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GbHeGwAzFrlQ for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 12:35:32 -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 34C6911E8159 for <ietf@ietf.org>; Tue, 27 Aug 2013 12:35:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.139.183]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7RJYIOj014122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 12:34:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377632071; bh=4J2yecjbuIVu9QCuQkcfdo8wKfgZJyl0w7FsWw5dAkE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3dfQu6Z2AQj7rSH+ugWNOSszpo/2flI+S3LtDG84NCxYrG7sMTmVkoDGPfOpvggJu 5cOZkRwd6s9YBLlZSfbLfDWl1voMv4BKpSTHcNBXGx60akyohVu1c/lbB+q9V8uWwr JHNPOHvWea/TPBYo6Ul0i0QRsZFOIjW4rpzUJsv4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377632071; i=@elandsys.com; bh=4J2yecjbuIVu9QCuQkcfdo8wKfgZJyl0w7FsWw5dAkE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cUl0WTZONb34kgpoAYx16Tab86AEJUifX3xCJGfzUJwJ6ENIkGOKkqV59/0iLc30+ thUMV+kNxF5sHHZ6IuHe2+VIYikv4e29IYS776tbhgC1TK8fZ8cyWIdu4pwa3kN/Zk tq3z6Jgm3hCeE1tU8aiHDabbfn6HECRAZA9tRjrw=
Message-Id: <6.2.5.6.2.20130827104331.0b8b2cb0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 27 Aug 2013 11:40:11 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>, Scott Brim <scott.brim@gmail.com>, John Leslie <john@jlc.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Rude responses (sergeant-at-arms?)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominu m.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 27 Aug 2013 19:35:40 -0000

At 10:11 27-08-2013, Ted Lemon wrote:
>But the most rude behavior that ever occurs on IETF mailing lists is 
>not listening.   Not trying to understand what the person who is 
>speaking to you has said.   Not trying to figure out if what they 
>said meaningfully contradicts your own position, and not making a 
>sincere effort to determine if they might be correct in 
>contradicting your position.

Yes.

>We have seen some incredible rudeness of this type in the recent 
>spfbis discussion, with various supposedly smart people in our 
>community utterly ignoring what their opponents are saying, and 
>simply re-asserting their own position in a variety of ways.

I'll add the message from Scott Brim below and comment.

At 10:20 27-08-2013, Scott Brim wrote:
>IMHO that's not a job for the sergeant at arms.  The SAA is 
>responsible for how things are said.  The shepherd -- or 
>supershepherd or whatever -- would be responsible for the substance.

The shepherd would have to request PR-action on the grounds that 
there has been a BCP violation.  That would cause other process 
issues.  The community will remain quiet and the shepherd will take the fall.

At 12:08 27-08-2013, John Leslie wrote:
>    I feel sorry for Ted, who _does_ have to evaluate consensus here.

Me too.

Regards,
S. Moonesamy  


From brian.e.carpenter@gmail.com  Tue Aug 27 12:48:39 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53BD011E81E6; Tue, 27 Aug 2013 12:48:39 -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 qCOe2eewRQTa; Tue, 27 Aug 2013 12:48:38 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id C291F11E81E3; Tue, 27 Aug 2013 12:48:38 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so5270174pbb.41 for <multiple recipients>; Tue, 27 Aug 2013 12:48:38 -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=Tt2BJ4asv/tNbPEYeJqogfkelhNcZRqJbpisEBMu1E4=; b=ldZ2Ysaklay8YD6IPYT5ea0CaGCjw1h5KdMQDkAw3rCZzbunc5C/t5vIpAFbYgtx6e Gj6HjLZnat8/Xgk4CSvoMyQ1kB15oZag2qRMpYPWXTWQGebwxqcK/+Phx6xHSBUQxBQx RDgWzqkY3UE0GVpxurOD9+mNl2yYUd+Q7RHK0rfodkXGkDSUuY888SVkdOUpcEGVjNtq Pjq0zDJMB5QgjA233BJ2ZSI8MtiMEPQYsJyRGnzB5fa4MRpCsXKmS2EOFY+e9xI5MxIR G9EIR+iUYToHCvwxROnkIJfN4O23Kw5kBOzSxAVoio3zVa/tMVBRVfk6LrnsKZ7yazsX i3IA==
X-Received: by 10.66.150.41 with SMTP id uf9mr22557898pab.108.1377632918543; Tue, 27 Aug 2013 12:48:38 -0700 (PDT)
Received: from [192.168.178.20] (69.195.69.111.dynamic.snap.net.nz. [111.69.195.69]) by mx.google.com with ESMTPSA id ht5sm26374887pbb.29.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 12:48:37 -0700 (PDT)
Message-ID: <521D0298.7020801@gmail.com>
Date: Wed, 28 Aug 2013 07:48:40 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-sweet-uri-zoneid-00.txt
References: <20130827155532.31994.88167.idtracker@ietfa.amsl.com>
In-Reply-To: <20130827155532.31994.88167.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 19:48:39 -0000

I am *not* an author of this draft, which Michael Sweet
produced on his own. I have not read the draft and have no
idea whether I agree with it.

(I believe this was an honest mistake on his part but I don't
want there to be any misunderstanding.)

Regards
   Brian Carpenter

On 28/08/2013 03:55, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
> 	Title           : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
> 	Author(s)       : Michael Sweet
>                           Brian Carpenter
>                           Stuart Cheshire
>                           Robert M. Hinden
> 	Filename        : draft-sweet-uri-zoneid-00.txt
> 	Pages           : 11
> 	Date            : 2013-08-27
> 
> Abstract:
>    This document describes how the zone identifier of an IPv6 scoped
>    address, defined as <zone_id> in the IPv6 Scoped Address Architecture
>    (RFC 4007), can be represented in a literal IPv6 address and in a
>    Uniform Resource Identifier that includes such a literal address.  It
>    updates the URI Generic Syntax specification (RFC 3986) accordingly.
> 
>    [ Editor's note: This draft adds the IPvFuture format used by CUPS
>    since 2005, addresses some misconceptions of how zoneid's are not
>    useful to HTTP servers, and is intended to replace RFC 6874. ]
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-sweet-uri-zoneid
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-sweet-uri-zoneid-00
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 

From Ted.Lemon@nominum.com  Tue Aug 27 12:53:22 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 698F211E81D6 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 12:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8+5uIOJuO3z for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 12:53:15 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id AF70411E81E3 for <ietf@ietf.org>; Tue, 27 Aug 2013 12:53:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUh0DqzH4ZwD4FRVxLzr0Djze6+yrs+Nh@postini.com; Tue, 27 Aug 2013 12:53:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3BBA51B82C0 for <ietf@ietf.org>; Tue, 27 Aug 2013 12:53:15 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2112919006C; Tue, 27 Aug 2013 12:53:15 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 27 Aug 2013 12:53:15 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John Leslie <john@jlc.net>
Subject: Re: Rude responses (sergeant-at-arms?)
Thread-Topic: Rude responses (sergeant-at-arms?)
Thread-Index: AQHOoxN06q2ItRANekqU0K4uK4hKvZmpwB4AgAACkgCAAANxgIAAGtOAgAAMXwA=
Date: Tue, 27 Aug 2013 19:53:14 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775267BF5@mbx-01.win.nominum.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com> <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com> <20130827190857.GA48013@verdi>
In-Reply-To: <20130827190857.GA48013@verdi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <E9F0D0D921A26548A83FDAEDAE0592D6@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 19:53:22 -0000

On Aug 27, 2013, at 3:08 PM, John Leslie <john@jlc.net> wrote:
>   I feel sorry for Ted, who _does_ have to evaluate consensus here.

Actually no, I don't=97spfbis is apps area, not int area.   Lucky me... :)


From jouni.nospam@gmail.com  Tue Aug 27 13:26:55 2013
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 587A711E81C8; Tue, 27 Aug 2013 13:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.296
X-Spam-Level: 
X-Spam-Status: No, score=-2.296 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4EDIgc1VYY2; Tue, 27 Aug 2013 13:26:54 -0700 (PDT)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6F86511E81BC; Tue, 27 Aug 2013 13:26:53 -0700 (PDT)
Received: by mail-ee0-f48.google.com with SMTP id l10so2466690eei.7 for <multiple recipients>; Tue, 27 Aug 2013 13:26:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=znDVBMXGyKlkBXQRv8j2FXcQjkoReAui0jeiK0GTZ1M=; b=vOHw3z52ZF6zHZu0Me+fyZ/LOFEfpOE5HpM/ahzdjlZ+0dPUC+pLL0FhpXagDGoPhZ x1mp+z96Gs3LWQ/XZ3WL7opAwzPDfgaP2AMjHV+CYWdX4jmzgCnH1n+97K3O98WB+8Ue 5pQxu59VTYGtm3CraQXwkKiNDGvfYG4ULpvYz3EUa1wFGBFhexXjUdIGFr5fhqiwf2ez SadYrnhaNUIwU0KWggWCTcyh+K8N9eYVab0U0/eYm2/TN/G9g0Z3YrNlcZEC7zOjkRu/ QSw+ZVtmBX0pbppK8JeZyh6b/sGVYJONAAb0gJfaZ0PhA05+KwjCpt5iZrp7a+OAQMZG 1nGw==
X-Received: by 10.15.83.2 with SMTP id b2mr37325764eez.28.1377635211120; Tue, 27 Aug 2013 13:26:51 -0700 (PDT)
Received: from ?IPv6:2001:1bc8:101:f101:fc5e:23e4:7126:ddab? ([2001:1bc8:101:f101:fc5e:23e4:7126:ddab]) by mx.google.com with ESMTPSA id h52sm31777998eez.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 13:26:47 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-11
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
Date: Tue, 27 Aug 2013 23:26:45 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <26019E7F-3973-460A-94F1-C7076FD80D0F@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE7129C675453@MX15A.corp.emc.com>
To: "Black, David" <david.black@emc.com>
X-Mailer: Apple Mail (2.1508)
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "dime@ietf.org" <dime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Eric McMurry <emcmurry@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 20:26:55 -0000

Great. Thanks!


- Jouni


On Aug 27, 2013, at 7:40 PM, "Black, David" <david.black@emc.com> wrote:

> The -11 version of this draft addresses all of the nits and editorial =
comments
> noted in the Gen-ART review of the -10 version.  It's ready for =
publication as
> an Informational RFC.
>=20
> Thanks,
> --David
>=20
>> -----Original Message-----
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, August 22, 2013 4:50 PM
>> To: Black, David
>> Cc: Eric McMurry; General Area Review Team (gen-art@ietf.org); =
ietf@ietf.org;
>> dime@ietf.org; bclaise@cisco.com
>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>=20
>> Hi David,
>>=20
>> We agree on all your points, and will make the updates in the next =
version,
>> pending shepherd instructions. =20
>>=20
>> Thanks!
>>=20
>> Ben.
>>=20
>> On Aug 22, 2013, at 2:50 PM, "Black, David" <david.black@emc.com> =
wrote:
>>=20
>>> Hi Eric,
>>>=20
>>> This looks good - comments follow ...
>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify this
>>>> in a way that would be specific to a particular type of mechanism.  =
It might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>=20
>>> That would be good to add as a note on REQ 27.
>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>=20
>>> I noted this as editorial rather than a minor issue, as I was mostly =
concerned
>>> that the actual design work will be informed by a sufficient =
architectural "clue"
>>> that the goal is "better overall system behaviors", which your =
response indicates
>>> will definitely be the case ;-).
>>>=20
>>> Rather than edit individual requirements, how about adding the =
following sentence
>>> immediately following the introductory sentence in Section 7?:
>>>=20
>>> 	These requirements are stated primarily in terms of individual =
node
>>> 	behavior to inform the design of the improved mechanism;
>>> 	that design effort should keep in mind that the overall goal is
>>> 	improved overall system behavior across all the nodes involved,
>>> 	not just improved behavior from specific individual nodes.
>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>=20
>>> That's fine.  FWIW, "congestion collapse" has a specific (rather =
severe)
>>> meaning over in the Transport Area, and that meaning was not =
intended here.
>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>=20
>>> I'd note the reference as work in progress, and put the statement =
about stable
>>> front matter (historical is a bad work to use here) in the body of =
the draft
>>> that cites the reference.
>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get the
>>>> warnings you saw (about the references).  What did it say?
>>>=20
>>> Sorry, I didn't mean to send you on a wild goose chase :-).  The =
idnits confusion
>>> manifested right at the top of the output, where everyone ignores it =
...
>>>=20
>>>  Attempted to download rfc272 state...
>>>  Failure fetching the file, proceeding without it.
>>>=20
>>> You didn't reference RFC 272, so that output's apparently courtesy =
of idnits
>>> misinterpreting this reference:
>>>=20
>>> 1195	   [TS29.272]
>>> 1196	              3GPP, "Evolved Packet System (EPS); =
Mobility Management
>>> 1197	              Entity (MME) and Serving GPRS Support Node =
(SGSN) related
>>> 1198	              interfaces based on Diameter protocol", TS =
29.272 11.4.0,
>>> 1199	              September 2012.
>>>=20
>>> I was amused :-).
>>>=20
>>> Thanks,
>>> --David
>>>=20
>>>> -----Original Message-----
>>>> From: Eric McMurry [mailto:emcmurry@computer.org]
>>>> Sent: Thursday, August 22, 2013 3:06 PM
>>>> To: Black, David
>>>> Cc: ben@nostrum.com; General Area Review Team (gen-art@ietf.org);
>>>> ietf@ietf.org; dime@ietf.org; bclaise@cisco.com
>>>> Subject: Re: Gen-ART review of draft-ietf-dime-overload-reqs-10
>>>>=20
>>>> Hi David,
>>>>=20
>>>> Thank you for the review.  Your time and comments are appreciated!
>>>>=20
>>>> comments/questions inline.
>>>>=20
>>>>=20
>>>> Eric
>>>>=20
>>>>=20
>>>>=20
>>>> On Aug 17, 2013, at 9:18 , "Black, David" <david.black@emc.com> =
wrote:
>>>>=20
>>>>>=20
>>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>>> Gen-ART, please see the FAQ at
>>>>>=20
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>>=20
>>>>> Please resolve these comments along with any other Last Call =
comments
>>>>> you may receive.
>>>>>=20
>>>>> Document: draft-ietf-dime-overload-reqs-10
>>>>> Reviewer: David L. Black
>>>>> Review Date: August 17, 2013
>>>>> IETF LC End Date: August 16, 2013
>>>>> IESG Telechat date: (if known)
>>>>>=20
>>>>> Summary:
>>>>> This draft is basically ready for publication, but has nits that =
should be
>>>>> fixed before publication.
>>>>>=20
>>>>> This draft describes scenarios in which Diameter overload can =
occur and
>> provides
>>>>> requirements for development of new overload control functionality =
in
>> Diameter.
>>>>> It is well written, and the inclusion of scenarios in which =
overload can
>> occur,
>>>>> both in terms of the relationships among types of Diameter nodes =
and
>> actual mobile
>>>>> network experience is very helpful.
>>>>>=20
>>>>> I apologize for this review being a day late, as I've been on =
vacation for
>> most
>>>>> of this draft's IETF Last Call period.
>>>>>=20
>>>>> Major issues: (none)
>>>>>=20
>>>>> Minor issues: (none)
>>>>>=20
>>>>> Nits/editorial comments:
>>>>>=20
>>>>> The following two comments could be minor issues, but I'm going to =
treat
>> them
>>>>> as editorial, as I expect that they will be addressed in =
development of
>> the
>>>>> actual overload functionality:
>>>>>=20
>>>>> a) I assume that overload control development work will derive =
more
>> specific
>>>>> security requirements - e.g., as REQ 27 is stated at a rather high =
level.
>>>>> The discussion in security considerations section seems =
reasonable.
>>>>=20
>>>> We agree with this.  The thinking here was that we didn't want to =
specify
>> this
>>>> in a way that would be specific to a particular type of mechanism.  =
It
>> might
>>>> not hurt to state that assumption, either as a note on Req 27 or in =
the sec
>>>> considerations.
>>>>=20
>>>>>=20
>>>>> b) The draft, and especially its requirements in Section 7 are =
strongly
>>>>> focused on individual Diameter node overload.  That's necessary, =
but
>> overload
>>>>> conditions can be broader, affecting an entire service or =
application, or
>>>>> multiple instances of either/both, even if not every individual =
Diameter
>> node
>>>>> involved is overloaded.  A number of the requirements, starting =
with REQ
>> 22
>>>>> could be generalized to cover broader overload conditions.
>>>>>=20
>>>>> This (b) has implications for other requirements, e.g., REQ 13 =
should also
>> be
>>>>> generalized beyond a single node to avoid increased traffic in an =
overload
>>>>> situation, even from a node that is not overloaded by itself.  =
There are
>> limits
>>>>> on what is reasonable here, as the desired overload functionality =
is
>> TCP/SCTP-
>>>>> like reaction to congestion where individual actions taken by =
nodes based
>> on
>>>>> the information they have (which is not the complete state of the =
network)
>>>>> results in an overall reduction of load.
>>>>=20
>>>> The intent was very much as you say, where requirements on =
individual node
>>>> capabilities are hoped to result in better overall system =
behaviors. There
>> are
>>>> also some requirements that are stated more at the system level =
(e.g. 7 and
>>>> 17.) Also the text in section 2.2 that discusses Figure 5 talks =
about how
>>>> insufficient server capacity at a cluster of servers behind a =
Diameter
>> agent
>>>> can be treated as if the agent itself was overloaded.
>>>>=20
>>>> On the other hand, any mechanism we design will have to focus on =
actions of
>>>> individual nodes, so the numbered requirements tend to focus on =
that. I'm
>> not
>>>> sure where to change the balance here--do you have specific =
suggestions?
>>>>=20
>>>>>=20
>>>>> Section 1.2, 2nd paragraph:
>>>>>=20
>>>>> as network congestion, network congestion can reduce a Diameter =
nodes
>>>>>=20
>>>>> "nodes" -> "node's"
>>>>=20
>>>> good catch.
>>>>=20
>>>>>=20
>>>>> Section 5, 1st paragraph:
>>>>>=20
>>>>> This inadequacy may, in turn, contribute to broader congestion =
collapse
>>>>>=20
>>>>> "collapse" is not the right word here - I suggest "issues", =
"impacts",
>>>>> "effects" or "problems".
>>>>=20
>>>> We are fine with any of those alternatives.  How about impacts.
>>>>=20
>>>>>=20
>>>>> Section 7
>>>>>=20
>>>>> The long enumerated list of requirements is not an easy read.  It =
would be
>>>>> better if these could somehow be grouped by functional category, =
e.g.,
>>>>> security, transport interactions, operational/administrative, etc.
>>>>=20
>>>> agree.  It is actually in sections in the XML (denoted by =
comments), we
>> just
>>>> did not promote those to visible sections in the txt.  I recall =
there being
>>>> some issue with xml2rfc and numbering, but now that the numbers are =
set,
>> this
>>>> would not be hard to do.
>>>>=20
>>>>=20
>>>>>=20
>>>>> idnits 2.12.17 noticed the non-standard RFC 2119 boilerplate - =
this is
>> fine,
>>>>> as the boilerplate has been appropriately modified for this draft =
that
>>>>> expresses requirements (as opposed to a draft that specifies a =
protocol).
>>>>>=20
>>>>> idnits 2.12.17 got confused by the 3GPP and GSMA Informative =
References.
>>>>> I assume that they're all sufficiently stable to be informative
>> references.
>>>>> However, [TR23.843] is a work in progress, and should be noted as =
such in
>>>>> its reference - is this needed for any of the other 3GPP or GSMA
>> references?
>>>>=20
>>>> 23.843 is the least stable reference.  I don't have any issue with =
pointing
>>>> that out.  The part of it we are referencing is historical front =
matter
>>>> though.
>>>>=20
>>>>=20
>>>> I tried the web and downloaded versions of 2.12.17 and was not able =
to get
>> the
>>>> warnings you saw (about the references).  What did it say?
>>>>=20
>>>>=20
>>>>>=20
>>>>> 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        Mobile: +1 (978) 394-7754
>>>>> ----------------------------------------------------
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20


From presnick@qti.qualcomm.com  Tue Aug 27 13:34:08 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABBC621F91AB; Tue, 27 Aug 2013 13:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdbNDF3qDmxw; Tue, 27 Aug 2013 13:34:04 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 0798C21E8084; Tue, 27 Aug 2013 13:33:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377635638; x=1409171638; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=2tIRNLVDj2/eKQRC5D78Bhuxa+FSE76aGXKKBHk9dM0=; b=YoIHwwTOeu0eEIgIFlQL8iS3hSTVGhGX3S6u4m91501XAULwmhpJAeJm bLd075xjhwkoSkThx3zsaMR5kS2nXmiT95OIi3C6XMx2eLXpsg0rsowFh VxJBKXToZYuU61bg3PtaGoaFs4lVpZdiiHthGJ4KKaO35NAmTY40gfYem 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7180"; a="50428746"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP; 27 Aug 2013 13:33:57 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7180"; a="538012734"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Aug 2013 13:33:57 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 27 Aug 2013 13:33:57 -0700
Message-ID: <521D0D32.3000406@qti.qualcomm.com>
Date: Tue, 27 Aug 2013 15:33:54 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: [spfbis] Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com> <20130819150521.GB21088@besserwisser.org>
In-Reply-To: <20130819150521.GB21088@besserwisser.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: spfbis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 20:34:08 -0000

I probably should have sent out this message over the weekend, but I was 
hoping I would complete a bigger message soon. Since I'm still working 
on that, a quick note to level set:

I have been reading all of the Last Call responses as they have come in. 
I am in the process of reviewing the comments and making a summary of 
the issues and responses. I have asked SM as document shepherd to do the 
same. (Being far more diligent than I, SM has completed his review 
already and is waiting on me.) We will be comparing notes and posting a 
summary of the issues and how they were addressed, along with whether we 
think they are resolved. That will give folks who disagree with my 
assessment one last chance to say, "Pete, you completely misunderstood 
what my objection / response was saying and you should re-evaluate your 
consensus determination on this issue." After that all shakes out, I'll 
make the final call on consensus.

An important thing to note is that I am seeing scant little I would call 
a "new argument" since late last week, so I would suggest that you are 
probably not adding to my understanding of the consensus by continuing 
to post. I'd like to think that everyone would be able to notice that 
things have gotten repetitive, both the folks who are repeating things 
as well as the folks who think they have to keep answering, but there 
does seem to be a bit of "getting the last word in" going on. Doing so 
isn't likely to add to my understanding or sway my opinion of the 
consensus (since I'm making a list of independent issues and their 
answers, not counting posts), but it does make it take longer for me to 
get through my review. So I'd recommend posting judiciously, at least 
until you see my summary.

Thanks,

pr

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


From presnick@qti.qualcomm.com  Tue Aug 27 13:42:57 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4CD11E81F8 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 13:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjTmpaKO0tXJ for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 13:42:53 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id EFD2D11E81F0 for <ietf@ietf.org>; Tue, 27 Aug 2013 13:42:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1377636172; x=1409172172; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WcVzF8y0okt8XNl/FqgYqzFz3QGWvF0n47JT34Yftxo=; b=VyuIidMXFHXgfhSKUe5PTlF6x6olX3EF8SSIbljepi0+jzrp3X8AkF6f PKpi0rnW9htv7tTlx659NoWBvDX/EMVhLVPZvZkWFjvvV4+H5HaZhIcGt WldjO/IadSJ8a0RgBf8lEpjtWFtOku9YlEzgBBC8b+FPsAoZiq88txZeC Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,7180"; a="50429181"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP; 27 Aug 2013 13:42:35 -0700
X-IronPort-AV: E=McAfee;i="5400,1158,7180"; a="591640836"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Aug 2013 13:42:35 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.146.2; Tue, 27 Aug 2013 13:42:34 -0700
Message-ID: <521D0F39.4040201@qti.qualcomm.com>
Date: Tue, 27 Aug 2013 15:42:33 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Rude responses (sergeant-at-arms?)
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk>	<CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com>	<38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>	<EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk>	<8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com>	<CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com>	<8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com>	<20130827190857.GA48013@verdi> <8D23D4052ABE7A4490E77B1A012B630775267BF5@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630775267BF5@mbx-01.win.nominum.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.48.1]
Cc: John Leslie <john@jlc.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: Tue, 27 Aug 2013 20:42:57 -0000

On 8/27/13 2:53 PM, Ted Lemon wrote:
> On Aug 27, 2013, at 3:08 PM, John Leslie<john@jlc.net>  wrote:
>    
>>    I feel sorry for Ted, who _does_ have to evaluate consensus here.
>>      
> Actually no, I don't—spfbis is apps area, not int area.   Lucky me... :)
>    

See the message I just posted. Yes, the additional repetitions make it 
take longer, but really it's not so hard to say, "Yep, that's already on 
my list of issues" and toss the repetitious message aside.

On 8/27/13 12:20 PM, Scott Brim wrote:
> On 8/27/13 9:11 AM, Ted Lemon wrote:
>    
>> I would expect the sergeant-at-arms to be reining in that sort of
>> rudeness before reining in the sort of supposed overt rudeness that
>> we are discussing here.
>>      
> IMHO that's not a job for the sergeant at arms.  The SAA is responsible
> for how things are said.  The shepherd -- or supershepherd or whatever
> -- would be responsible for the substance.

On 8/27/13 12:31 PM, Melinda Shore wrote:

> That suggestion makes me want to say something a little rude.
> Managing the discussion is the chair's job, not the sergeant-
> at-arms's.
>    

Yeah, again, that's me. Also see my recent message.

That said, I do wish it didn't take intervention on my part. I wish 
people would realize they're being repetitive. I wish people would stop 
responding to the repetition. (Neither is going to change my opinion of 
the consensus.) But then again, I also wish I had a pony.

pr

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


From bernard_aboba@hotmail.com  Tue Aug 27 13:51:10 2013
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 7484B21F9E48 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 13:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.077, 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 rMNR6yiWrdRP for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 13:51:05 -0700 (PDT)
Received: from blu0-omc2-s20.blu0.hotmail.com (blu0-omc2-s20.blu0.hotmail.com [65.55.111.95]) by ietfa.amsl.com (Postfix) with ESMTP id B8B1A11E81D0 for <ietf@ietf.org>; Tue, 27 Aug 2013 13:51:01 -0700 (PDT)
Received: from BLU169-W65 ([65.55.111.71]) by blu0-omc2-s20.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 27 Aug 2013 13:51:01 -0700
X-TMN: [w/kMeNTBdO/ydOuT0gxQXTEN6kv5eeWq]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU169-W655C037E2AF656036E79B3934A0@phx.gbl>
Content-Type: multipart/alternative; boundary="_5a8988dc-c36f-4162-880a-87e0e460c0fd_"
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: charging remote participants
Date: Tue, 27 Aug 2013 13:51:00 -0700
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 27 Aug 2013 20:51:01.0597 (UTC) FILETIME=[23AF40D0:01CEA367]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 20:51:10 -0000

--_5a8988dc-c36f-4162-880a-87e0e460c0fd_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hadriel said:=20
"I agree. My proposal for how/what/where to get more revenue (and not from =
remote participants) was only in case we actually need it to pay for enhanc=
ing remote participation. It's not clear we have such a need any time soon=
=2C but I was only trying to provide an alternative model to charging remot=
e participants. " [BA]  It appears quite possible to significantly enhance =
remote participation in the IETF with minimal funding.  The load pattern of=
 the IETF (heavy during physical meetings=2C much lower in between)=2C acco=
mmodates itself well to the use of cloud services. - making it possible for=
 the IETF to avoid having to purchase hardware to handle the peak load=2C i=
nstead being able to scale up/down capacity as needed.   From what I can te=
ll=2C the breadth and depth of services obtainable for a few thousand $/yea=
r of expenditure is pretty impressive.  As an example=2C the cost of puttin=
g up an audio conferencing service supporting Opus (usable by any WG that n=
eeded it for virtual or design team meetings) would only be a few hundred $=
/year=2C excluding the cost of PSTN connectivity.   Even small scale video =
conferencing doesn't appear to be very expensive.  If there are only a few =
video participants=2C it is possible to mix on the peer=2C and for centrali=
zed conferencing=2C a "small instance" virtual machine (e.g. one core=2C 1 =
GB RAM) appears capable of handling half a dozen participants using softwar=
e such as jitsi-videobridge=2C without breaking a sweat.  So=2C a thousand =
$/year might cover it (assuming that we aren't attempting to provide telepr=
esence-quality video). Even if money were *really* tight=2C we could easily=
 obtain donations to cover costs in that ballpark.=20
IMHO=2C the hard problems relate to engineering=2C not finance.  In particu=
lar=2C the challenge is to provide a system with low administrative overhea=
d and good ease-of-use=2C integrated with IETF processes.  To advance the s=
tate of the art=2C IAOC RPS committee (see http://iaoc.ietf.org/committees.=
html#rps) will continue to sponsor ongoing experiments at meetings=2C as we=
ll as pilot tests.   		 	   		  =

--_5a8988dc-c36f-4162-880a-87e0e460c0fd_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Hadriel said:&nbsp=3B<div><br></=
div><div><span style=3D"font-family: tahoma=2C verdana=2C arial=2C helvetic=
a=2C sans-serif=3B font-size: 11px=3B line-height: 16px=3B">"I agree. My pr=
oposal for how/what/where to get more revenue (and not from remote particip=
ants) was only in case we actually need it to pay for enhancing&nbsp=3B</sp=
an><br style=3D"font-family: tahoma=2C verdana=2C arial=2C helvetica=2C san=
s-serif=3B font-size: 11px=3B line-height: 16px=3B"><span style=3D"font-fam=
ily: tahoma=2C verdana=2C arial=2C helvetica=2C sans-serif=3B font-size: 11=
px=3B line-height: 16px=3B">remote participation. It's not clear we have su=
ch a need any time soon=2C but I was only trying to provide an alternative =
model to charging remote&nbsp=3B</span><br style=3D"font-family: tahoma=2C =
verdana=2C arial=2C helvetica=2C sans-serif=3B font-size: 11px=3B line-heig=
ht: 16px=3B"><span style=3D"font-family: tahoma=2C verdana=2C arial=2C helv=
etica=2C sans-serif=3B font-size: 11px=3B line-height: 16px=3B">participant=
s. "</span><br style=3D"font-family: tahoma=2C verdana=2C arial=2C helvetic=
a=2C sans-serif=3B font-size: 11px=3B line-height: 16px=3B"><span style=3D"=
font-family: tahoma=2C verdana=2C arial=2C helvetica=2C sans-serif=3B font-=
size: 11px=3B line-height: 16px=3B">&nbsp=3B</span><br style=3D"font-family=
: tahoma=2C verdana=2C arial=2C helvetica=2C sans-serif=3B font-size: 11px=
=3B line-height: 16px=3B"><font face=3D"tahoma=2C verdana=2C arial=2C helve=
tica=2C sans-serif"><span style=3D"font-size: 11px=3B line-height: 16px=3B"=
>[BA] &nbsp=3BIt appears quite possible to significantly enhance remote par=
ticipation in the IETF with minimal funding. &nbsp=3BThe load pattern of th=
e IETF (heavy during physical meetings=2C much lower in between)=2C accommo=
dates itself well to the use of cloud services. - making it possible for th=
e IETF to avoid having to purchase hardware to handle the peak load=2C inst=
ead being able to scale up/down capacity as needed. &nbsp=3B From what I ca=
n tell=2C the breadth and depth of services obtainable for a few thousand $=
/year of expenditure is pretty impressive. &nbsp=3BAs an example=2C the cos=
t of putting up an audio conferencing service supporting Opus (usable by an=
y WG that needed it for virtual or design team meetings) would only be a fe=
w hundred $/year=2C excluding the cost of PSTN connectivity. &nbsp=3B Even =
small scale video conferencing doesn't appear to be very expensive. &nbsp=
=3BIf there are only a few video participants=2C it is possible to mix on t=
he peer=2C and for centralized conferencing=2C a "small instance" virtual m=
achine (e.g. one core=2C 1 GB RAM) appears capable of handling half a dozen=
 participants using software such as jitsi-videobridge=2C without breaking =
a sweat. &nbsp=3BSo=2C a thousand $/year might cover it (assuming that we a=
ren't attempting to provide telepresence-quality video).&nbsp=3B</span></fo=
nt><span style=3D"font-family: tahoma=2C verdana=2C arial=2C helvetica=2C s=
ans-serif=3B font-size: 11px=3B line-height: 16px=3B">Even if money were *r=
eally* tight=2C we could easily obtain donations to cover costs in that bal=
lpark.&nbsp=3B</span></div><div><span style=3D"font-family: tahoma=2C verda=
na=2C arial=2C helvetica=2C sans-serif=3B font-size: 11px=3B line-height: 1=
6px=3B"><br></span></div><div><span style=3D"font-family: tahoma=2C verdana=
=2C arial=2C helvetica=2C sans-serif=3B font-size: 11px=3B line-height: 16p=
x=3B">IMHO=2C the hard problems relate to engineering=2C not finance. &nbsp=
=3BIn particular=2C the challenge is to provide a system with</span><span s=
tyle=3D"font-family: tahoma=2C verdana=2C arial=2C helvetica=2C sans-serif=
=3B font-size: 11px=3B line-height: 16px=3B">&nbsp=3Blow administrative ove=
rhead and good ease-of-use=2C integrated with IETF processes. &nbsp=3B</spa=
n><span style=3D"font-family: tahoma=2C verdana=2C arial=2C helvetica=2C sa=
ns-serif=3B font-size: 11px=3B line-height: 16px=3B">To advance the state o=
f the art=2C IAOC RPS committee (see http://iaoc.ietf.org/committees.html#r=
ps) will continue to sponsor ongoing experiments at meetings=2C as well as =
pilot tests. &nbsp=3B</span></div> 		 	   		  </div></body>
</html>=

--_5a8988dc-c36f-4162-880a-87e0e460c0fd_--

From bob.hinden@gmail.com  Tue Aug 27 13:58:55 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7730B21F8503 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 13:58:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.71
X-Spam-Level: 
X-Spam-Status: No, score=-102.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mqk8phxyf3fE for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 13:58:54 -0700 (PDT)
Received: from mail-gh0-x235.google.com (mail-gh0-x235.google.com [IPv6:2607:f8b0:4002:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC0421F84EF for <ietf@ietf.org>; Tue, 27 Aug 2013 13:58:54 -0700 (PDT)
Received: by mail-gh0-f181.google.com with SMTP id z12so1341272ghb.26 for <ietf@ietf.org>; Tue, 27 Aug 2013 13:58:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iUQ2U6bPdALPw5YjPBRvSnqhGRjII975AcmbRElIKTI=; b=NZvsmeZ0G9oZj2P6YBsPBW/Sr1YD4alzhJcLzLa/OcRMvrzmOnyUWRm+vk1ZISnNC9 5gBOIIKZ0Lgm0khmTRPlA1D+S5H3fsmT9rycM33RH2LiWkG50/UjNPMTCVtpoO3s9HGf 4sNPCJ9hDwvyrALV83OE2aAGLGT2dtD3px4VYsUU4m78JUfc/y5UmKnr3qAs1D4OyViW xXh00wPpfNIDzxLEnKDN6KDLAyW8n1S03iQd4Nz718ueJVQfAhDPlTmw1ptC7ekFKlAf yftEQchm0VOu5FcIsVpo7nA1W7kQgnu6HvVf887R+SfoVCkSBwi/mCqz1ihp1FCYWsst 22mg==
X-Received: by 10.236.139.198 with SMTP id c46mr2182684yhj.78.1377637133565; Tue, 27 Aug 2013 13:58:53 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id g47sm26727188yhb.21.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 27 Aug 2013 13:58:51 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: I-D Action: draft-sweet-uri-zoneid-00.txt
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <521D0298.7020801@gmail.com>
Date: Tue, 27 Aug 2013 13:58:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4829511B-C600-4DBE-8B5E-95BCF263102B@gmail.com>
References: <20130827155532.31994.88167.idtracker@ietfa.amsl.com> <521D0298.7020801@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1508)
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: Tue, 27 Aug 2013 20:58:55 -0000

On Aug 27, 2013, at 12:48 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> I am *not* an author of this draft, which Michael Sweet
> produced on his own. I have not read the draft and have no
> idea whether I agree with it.
>=20
> (I believe this was an honest mistake on his part but I don't
> want there to be any misunderstanding.)

I am in the same situation and like Brian I do not know if I support =
this or not. =20

Bob


>=20
> Regards
>   Brian Carpenter
>=20
> On 28/08/2013 03:55, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>>=20
>>=20
>> 	Title           : Representing IPv6 Zone Identifiers in Address =
Literals and Uniform Resource Identifiers
>> 	Author(s)       : Michael Sweet
>>                          Brian Carpenter
>>                          Stuart Cheshire
>>                          Robert M. Hinden
>> 	Filename        : draft-sweet-uri-zoneid-00.txt
>> 	Pages           : 11
>> 	Date            : 2013-08-27
>>=20
>> Abstract:
>>   This document describes how the zone identifier of an IPv6 scoped
>>   address, defined as <zone_id> in the IPv6 Scoped Address =
Architecture
>>   (RFC 4007), can be represented in a literal IPv6 address and in a
>>   Uniform Resource Identifier that includes such a literal address.  =
It
>>   updates the URI Generic Syntax specification (RFC 3986) =
accordingly.
>>=20
>>   [ Editor's note: This draft adds the IPvFuture format used by CUPS
>>   since 2005, addresses some misconceptions of how zoneid's are not
>>   useful to HTTP servers, and is intended to replace RFC 6874. ]
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-sweet-uri-zoneid
>>=20
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-sweet-uri-zoneid-00
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of =
submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>=20


From hallam@gmail.com  Tue Aug 27 15:53:57 2013
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 95C1E11E8245 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 15:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  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 ICotaO+6YrpF for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 15:53:54 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE2F11E838E for <ietf@ietf.org>; Tue, 27 Aug 2013 15:53:51 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id eo20so4164153lab.3 for <ietf@ietf.org>; Tue, 27 Aug 2013 15:53: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=hTk5upJcF0a7yB5seuWKBH+MIBWDB7zVFSh23j99s8I=; b=HDmLT8ukFfrsBziq6EqlVJHXJ22qSDXph2XNoWAHXXLlGFbwUBBxsCTgJw5ydCwdBt Ryil2ZEjHcsDH/WkChTCzPVzOTqD0zo7f7XMI3an7fZgHTbhRxGulnlepZd5fyBOvXD2 mO7bYQeI94L8dDHOU8M/9KyVtZ/NaZIVdJJQNOf5XA6APZhMN5YqwUXe95s1A9k/hN2V 6YGkgPQKSWvF95w0oIYFT55DJpPd2wVX1Puc9JJAyORGccl8w2j4GLQp/r0uNeMN7bX9 s/72eT9EFjOPRFBLgDyIypvhW0xwnNJcSjCj5UnI7BOKGlt6ZddboxlcyQTMcZQLT81j rd7g==
MIME-Version: 1.0
X-Received: by 10.152.29.201 with SMTP id m9mr20939994lah.6.1377644029698; Tue, 27 Aug 2013 15:53:49 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 27 Aug 2013 15:53:49 -0700 (PDT)
In-Reply-To: <521D0F39.4040201@qti.qualcomm.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com> <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com> <20130827190857.GA48013@verdi> <8D23D4052ABE7A4490E77B1A012B630775267BF5@mbx-01.win.nominum.com> <521D0F39.4040201@qti.qualcomm.com>
Date: Tue, 27 Aug 2013 18:53:49 -0400
Message-ID: <CAMm+LwhekZdQ2gej-raCD_oGr5ErU577sOwcMxq_eg-6kaF0UA@mail.gmail.com>
Subject: Re: Rude responses (sergeant-at-arms?)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e0158cb9204697e04e4f5bffc
Cc: ietf <ietf@ietf.org>, John Leslie <john@jlc.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 22:53:58 -0000

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

Sometimes there is a need for sarcasm.

I find it very rude when people begin by lecturing a Working Group on the
'fact' that nobody understands the subject matter. This is not the
exhibition of modesty etc. that it pretends to be, it is actually a trap
designed to gull the WG into agreeing that they know nothing about the
problem whereupon the original proposer will gladly provide the poor naifs
with their pearls of wisdom.

The correct response in such situations is in my book, 'you may speak for
yourself and your own level of expertise but do not accuse others of
sharing your inabilities'.


I also find it very rude when people try to cut short a discussion with
recourse to bogus points of processor try to trump a discussion with
recourse to an authority that I know from private conversations to hold the
exact opposite opinion to the one being attributed to them.

What I found incredibly rude was when an AD and Working Group chair
actually hissed when I gave my company name at the mic.


But what I found worst was the fact that nobody seemed to be taking any
notice at all of the four women who raised diversity issues at the mic in
Orlando until I got up to the mic and mansplained the issue for you all.

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

<div dir=3D"ltr">Sometimes there is a need for sarcasm.<div><br></div><div>=
I find it very rude when people begin by lecturing a Working Group on the &=
#39;fact&#39; that nobody understands the subject matter. This is not the e=
xhibition of modesty etc. that it pretends to be, it is actually a trap des=
igned to gull the WG into agreeing that they know nothing about the problem=
 whereupon the original proposer will gladly provide the poor naifs with th=
eir pearls of wisdom.</div>
<div><br></div><div>The correct response in such situations is in my book, =
&#39;you may speak for yourself and your own level of expertise but do not =
accuse others of sharing your inabilities&#39;.</div><div><br></div><div>
<br></div><div>I also find it very rude when people try to cut short a disc=
ussion with recourse to bogus points of processor try to trump a discussion=
 with recourse to an authority that I know from private conversations to ho=
ld the exact opposite opinion to the one being attributed to them.</div>
<div><br></div><div>What I found incredibly rude was when an AD and Working=
 Group chair actually hissed when I gave my company name at the mic. =A0<br=
></div><div><br></div><div><br></div><div>But what I found worst was the fa=
ct that nobody seemed to be taking any notice at all of the four women who =
raised diversity issues at the mic in Orlando until I got up to the mic and=
 mansplained the issue for you all.</div>
</div>

--089e0158cb9204697e04e4f5bffc--

From sm@elandsys.com  Tue Aug 27 17:29:18 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555AF21F90A7 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 17:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tTcArE4vsFFK for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 17:29: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 7F27521F8E7C for <ietf@ietf.org>; Tue, 27 Aug 2013 17:29:16 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.239]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7S0SuhM017062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Aug 2013 17:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377649748; bh=4fUPGoRkH3+i19HJbGFju+J+JceDZHkSukHsFFeWeEc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YxqpQnH5z+B8Pfr1SyU2dOJqdiFX284YfmtNI2F9zPmetEYklJOcoG5DEQ+GW0rNM sSK4tePFz5MlFHfun+nmFU0a1LUn8FL2rqUNJGoBSRnWtJZPy8EpiPE9G1k0DHz8OG /7hZhb4rR4p3P6uFS793Y+NiFRBsE3rl907PNz0A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377649748; i=@elandsys.com; bh=4fUPGoRkH3+i19HJbGFju+J+JceDZHkSukHsFFeWeEc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gEgYTGClXDWlL6N5qY5YVo52Q0StGrpq5D3qqQkE8/v5sGq7iJeOc5+OjTgPnylMi BooOkbMxq3dAFcWRE2frIjTTAcKE1ukW8sXEu3yCI9ZRKk4logUZ3mKlQ5nhLQIMhg VnkAsBYeiFpm29D+Hweti9I2X46DWNUNXSJVcbTI=
Message-Id: <6.2.5.6.2.20130827171456.0d7e1e48@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 27 Aug 2013 17:28:29 -0700
To: Phillip Hallam-Baker <hallam@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Rude responses (sergeant-at-arms?)
In-Reply-To: <CAMm+LwhekZdQ2gej-raCD_oGr5ErU577sOwcMxq_eg-6kaF0UA@mail.g mail.com>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com> <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com> <20130827190857.GA48013@verdi> <8D23D4052ABE7A4490E77B1A012B630775267BF5@mbx-01.win.nominum.com> <521D0F39.4040201@qti.qualcomm.com> <CAMm+LwhekZdQ2gej-raCD_oGr5ErU577sOwcMxq_eg-6kaF0UA@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, 28 Aug 2013 00:29:18 -0000

Hi Phillip,
At 15:53 27-08-2013, Phillip Hallam-Baker wrote:
>What I found incredibly rude was when an AD and Working Group chair 
>actually hissed when I gave my company name at the mic.

I submitted draft-moonesamy-ietf-conduct-3184bis  During the 
discussions (see thread at 
http://www.ietf.org/mail-archive/web/diversity/current/msg00201.html 
)about the draft it was suggested there should be consequences of not 
following the code of conduct.  What action would you suggest against:

  (i)  the Area Director in a case such as the above?

  (ii) the Working Group chair in a case such as the above?

Regards,
S. Moonesamy 


From hallam@gmail.com  Tue Aug 27 18:13:23 2013
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 CE2C321E80FD for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 18:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.514
X-Spam-Level: 
X-Spam-Status: No, score=-2.514 tagged_above=-999 required=5 tests=[AWL=0.085,  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 aBGbF5sRZvaO for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 18:13:23 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A1FA721E80FB for <ietf@ietf.org>; Tue, 27 Aug 2013 18:13:14 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id r11so3199301lbi.18 for <ietf@ietf.org>; Tue, 27 Aug 2013 18:13: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=y1CaVzoWuXo4LGPJTclRpDXcSimtlHDl2JX5xCKfGvc=; b=PN+ANZ8VlL3Ty2ESja1SSu10161cvivQxZV6WSnmvqYg3ZLbHmVXZhXCUZ3U7uciHd HSRkVJjImrhWTzeaOwA5zoX4sdq8Ex8egZbpEOru9pEaCRLo8yE+Uux4TaAgNK6B46j3 r3ozdRC6EAB6c3hQXPF0ql8VkWcQ7y+2DTy/w7ka+Zrcfd5lNIdGdOb613tcYp5HA7P9 iJy1DqTi6HcTkRZrOVRFeMXqbVopjAwK8mJNJGpOLhinN92WkHpA86XFAsYCLo/aW52C 1dALBrxoSbPJQhDD4YtqyIuAGgyRILEziMPfeojq8f3AjLLb3kiWF9OpxqlYqgIK8EHN uSFQ==
MIME-Version: 1.0
X-Received: by 10.112.198.39 with SMTP id iz7mr19624081lbc.24.1377652393499; Tue, 27 Aug 2013 18:13:13 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Tue, 27 Aug 2013 18:13:13 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130827171456.0d7e1e48@resistor.net>
References: <290E20B455C66743BE178C5C84F12408224060750E@EXMB01CMS.surrey.ac.uk> <CADnDZ891f9z=snhx2mP1oqZK+iPih79LDhHrFHu1gjT4mkMbhw@mail.gmail.com> <38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <EMEW3|1ad6c5e007d1f092769939d09c0615b9p7QBpW03tjc|ecs.soton.ac.uk|38BAB050-5B83-4530-84E8-FBF27E822C7F@ecs.soton.ac.uk> <8D23D4052ABE7A4490E77B1A012B630775267379@mbx-01.win.nominum.com> <CAPv4CP8ORvFQXsRV2vZqk46S4+ZkLm+GeV3wxdUvcmZ96yyEVA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630775267681@mbx-01.win.nominum.com> <20130827190857.GA48013@verdi> <8D23D4052ABE7A4490E77B1A012B630775267BF5@mbx-01.win.nominum.com> <521D0F39.4040201@qti.qualcomm.com> <CAMm+LwhekZdQ2gej-raCD_oGr5ErU577sOwcMxq_eg-6kaF0UA@mail.gmail.com> <6.2.5.6.2.20130827171456.0d7e1e48@resistor.net>
Date: Tue, 27 Aug 2013 21:13:13 -0400
Message-ID: <CAMm+LwgiyPLfwoQjx7dhK7TzWj4kBjdb1YoHs03Hh19BZJDD0g@mail.gmail.com>
Subject: Re: Rude responses (sergeant-at-arms?)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=001a11c233ea89dfb904e4f7b1cf
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: Wed, 28 Aug 2013 01:13:23 -0000

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

On Tue, Aug 27, 2013 at 8:28 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Phillip,
>
> At 15:53 27-08-2013, Phillip Hallam-Baker wrote:
>
>> What I found incredibly rude was when an AD and Working Group chair
>> actually hissed when I gave my company name at the mic.
>>
>
> I submitted draft-moonesamy-ietf-conduct-**3184bis  During the
> discussions (see thread at http://www.ietf.org/mail-**
> archive/web/diversity/current/**msg00201.html<http://www.ietf.org/mail-archive/web/diversity/current/msg00201.html>)about the draft it was suggested there should be consequences of not
> following the code of conduct.  What action would you suggest against:
>
>  (i)  the Area Director in a case such as the above?
>
>  (ii) the Working Group chair in a case such as the above?
>

In that case they were the same person. Which I think was a major
structural problem in that nobody on the IESG was prepared to stand up to
him.

So I would start off by not allowing that situation to occur in the first
place.


But in general where you have a WG chair that shows blatant bias you have
to get rid of that WG chair.

If DNSSEC had been my product I would have pushed VeriSign to do more than
appeal the Opt-in debacle, I would have litigated.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Aug 27, 2013 at 8:28 PM, S Moonesamy <span dir=3D"ltr">&lt;=
<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf@elandsys.=
com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Phillip,<div class=3D"im"><br>
At 15:53 27-08-2013, Phillip Hallam-Baker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
What I found incredibly rude was when an AD and Working Group chair actuall=
y hissed when I gave my company name at the mic.<br>
</blockquote>
<br></div>
I submitted draft-moonesamy-ietf-conduct-<u></u>3184bis =A0During the discu=
ssions (see thread at <a href=3D"http://www.ietf.org/mail-archive/web/diver=
sity/current/msg00201.html" target=3D"_blank">http://www.ietf.org/mail-<u><=
/u>archive/web/diversity/current/<u></u>msg00201.html</a> )about the draft =
it was suggested there should be consequences of not following the code of =
conduct. =A0What action would you suggest against:<br>

<br>
=A0(i) =A0the Area Director in a case such as the above?<br>
<br>
=A0(ii) the Working Group chair in a case such as the above?<br></blockquot=
e><div><br></div><div>In that case they were the same person. Which I think=
 was a major structural problem in that nobody on the IESG was prepared to =
stand up to him.</div>
<div><br></div><div>So I would start off by not allowing that situation to =
occur in the first place.</div><div><br></div><div><br></div><div>But in ge=
neral where you have a WG chair that shows blatant bias you have to get rid=
 of that WG chair.</div>
<div><br></div><div>If DNSSEC had been my product I would have pushed VeriS=
ign to do more than appeal the Opt-in debacle, I would have litigated.</div=
><div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://hall=
ambaker.com/">http://hallambaker.com/</a><br>

</div></div>

--001a11c233ea89dfb904e4f7b1cf--

From spromano@unina.it  Wed Aug 28 02:58:23 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 605B711E8183 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 02:58:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X0HHof25-zuF for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 02:58:18 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 668D811E81B6 for <ietf@ietf.org>; Wed, 28 Aug 2013 02:58:10 -0700 (PDT)
Received: from node-1ym.pool-1-4.dynamic.totbb.net ([94.167.110.125]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r7S9vset009322 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 28 Aug 2013 11:57:56 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <BLU169-W655C037E2AF656036E79B3934A0@phx.gbl>
References: <BLU169-W655C037E2AF656036E79B3934A0@phx.gbl>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----PYSUVKFHAX9CAEMW4G13RHMBR2GHGF"
Subject: Re: charging remote participants
From: Simon Pietro Romano <spromano@unina.it>
Date: Wed, 28 Aug 2013 11:57:46 +0200
To: Bernard Aboba <bernard_aboba@hotmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <aaed307e-5016-4c75-a754-63618a38cc4a@email.android.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, 28 Aug 2013 09:58:23 -0000

------PYSUVKFHAX9CAEMW4G13RHMBR2GHGF
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi Bernard,

I'm afraid that, as it usually happens with 'software', we are overly underestimating the huge development effort (in terms of human resources and brain cycles) that is needed before arriving at a 'few hundred $ per year' product. When it comes to the IETF, let me also add that, in my honest opinion, no existing product can simply be taken from the market and brought to our community. There's a significant effort associated with the integration with a whole bunch of tools (meeting materials page, agenda, etc.) which are already available. Not to mention the deep knowledge of all IETF procedures and mechanisms required in order to organize and conduct a successful meeting. If you take all these things into account, you'll probably arrive at a much higher funding level than the one you envisage. I also believe that the time is probably ripe to stop the experiment-only phase and start to take seriously into account the fact that remote participation is in all respects a 'servic!
 e' that
the IETF is going to offer to the community. Experiments have a well-defined time-frame; after such a period, they have to be declared either a success or a failure.

Just my 2 cents,

Simon

Bernard Aboba <bernard_aboba@hotmail.com> ha scritto:
>Hadriel said: 
>"I agree. My proposal for how/what/where to get more revenue (and not
>from remote participants) was only in case we actually need it to pay
>for enhancing remote participation. It's not clear we have such a need
>any time soon, but I was only trying to provide an alternative model to
>charging remote participants. " [BA]  It appears quite possible to
>significantly enhance remote participation in the IETF with minimal
>funding.  The load pattern of the IETF (heavy during physical meetings,
>much lower in between), accommodates itself well to the use of cloud
>services. - making it possible for the IETF to avoid having to purchase
>hardware to handle the peak load, instead being able to scale up/down
>capacity as needed.   From what I can tell, the breadth and depth of
>services obtainable for a few thousand $/year of expenditure is pretty
>impressive.  As an example, the cost of putting up an audio
>conferencing service supporting Opus (usable by any WG that needed it
>for virtual or design team meetings) would only be a few hundred
>$/year, excluding the cost of PSTN connectivity.   Even small scale
>video conferencing doesn't appear to be very expensive.  If there are
>only a few video participants, it is possible to mix on the peer, and
>for centralized conferencing, a "small instance" virtual machine (e.g.
>one core, 1 GB RAM) appears capable of handling half a dozen
>participants using software such as jitsi-videobridge, without breaking
>a sweat.  So, a thousand $/year might cover it (assuming that we aren't
>attempting to provide telepresence-quality video). Even if money were
>*really* tight, we could easily obtain donations to cover costs in that
>ballpark. 
>IMHO, the hard problems relate to engineering, not finance.  In
>particular, the challenge is to provide a system with low
>administrative overhead and good ease-of-use, integrated with IETF
>processes.  To advance the state of the art, IAOC RPS committee (see
>http://iaoc.ietf.org/committees.html#rps) will continue to sponsor
>ongoing experiments at meetings, as well as pilot tests.   		 	   		  

------PYSUVKFHAX9CAEMW4G13RHMBR2GHGF
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head><style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head><body class="hmmessage">Hi Bernard,<br>
<br>
I&#39;m afraid that, as it usually happens with &#39;software&#39;, we are overly underestimating the huge development effort (in terms of human resources and brain cycles) that is needed before arriving at a &#39;few hundred $ per year&#39; product. When it comes to the IETF, let me also add that, in my honest opinion, no existing product can simply be taken from the market and brought to our community. There&#39;s a significant effort associated with the integration with a whole bunch of tools (meeting materials page, agenda, etc.) which are already available. Not to mention the deep knowledge of all IETF procedures and mechanisms required in order to organize and conduct a successful meeting. If you take all these things into account, you&#39;ll probably arrive at a much higher funding level than the one you envisage. I also believe that the time is probably ripe to stop the experiment-only phase and start to take seriously into account the fact that remote participation !
 is in
all respects a &#39;service&#39; that the IETF is going to offer to the community. Experiments have a well-defined time-frame; after such a period, they have to be declared either a success or a failure.<br>
<br>
Just my 2 cents,<br>
<br>
Simon<br><br><div class="gmail_quote">Bernard Aboba &lt;bernard_aboba@hotmail.com&gt; ha scritto:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">



<div dir="ltr">Hadriel said:&nbsp;<div><br /></div><div><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">"I agree. My proposal for how/what/where to get more revenue (and not from remote participants) was only in case we actually need it to pay for enhancing&nbsp;</span><br style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;" /><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">remote participation. It's not clear we have such a need any time soon, but I was only trying to provide an alternative model to charging remote&nbsp;</span><br style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;" /><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">participants. "</span><br style="font-family: tahoma, verdan!
 a,
arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;" /><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">&nbsp;</span><br style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;" /><font face="tahoma, verdana, arial, helvetica, sans-serif"><span style="font-size: 11px; line-height: 16px;">[BA] &nbsp;It appears quite possible to significantly enhance remote participation in the IETF with minimal funding. &nbsp;The load pattern of the IETF (heavy during physical meetings, much lower in between), accommodates itself well to the use of cloud services. - making it possible for the IETF to avoid having to purchase hardware to handle the peak load, instead being able to scale up/down capacity as needed. &nbsp; From what I can tell, the breadth and depth of services obtainable for a few thousand $/year of expenditure is pretty impressive. &nbsp;As an example, the !
 cost of
putting up an audio conferencing service supporting Opus (usable by any WG that needed it for virtual or design team meetings) would only be a few hundred $/year, excluding the cost of PSTN connectivity. &nbsp; Even small scale video conferencing doesn't appear to be very expensive. &nbsp;If there are only a few video participants, it is possible to mix on the peer, and for centralized conferencing, a "small instance" virtual machine (e.g. one core, 1 GB RAM) appears capable of handling half a dozen participants using software such as jitsi-videobridge, without breaking a sweat. &nbsp;So, a thousand $/year might cover it (assuming that we aren't attempting to provide telepresence-quality video).&nbsp;</span></font><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">Even if money were *really* tight, we could easily obtain donations to cover costs in that ballpark.&nbsp;</span></div><div><span style="font-family: tahom!
 a,
verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;"><br /></span></div><div><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">IMHO, the hard problems relate to engineering, not finance. &nbsp;In particular, the challenge is to provide a system with</span><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">&nbsp;low administrative overhead and good ease-of-use, integrated with IETF processes. &nbsp;</span><span style="font-family: tahoma, verdana, arial, helvetica, sans-serif; font-size: 11px; line-height: 16px;">To advance the state of the art, IAOC RPS committee (see http://iaoc.ietf.org/committees.html#rps) will continue to sponsor ongoing experiments at meetings, as well as pilot tests. &nbsp;</span></div>            </div>
</blockquote></div></body></html>
------PYSUVKFHAX9CAEMW4G13RHMBR2GHGF--


From sm@elandsys.com  Wed Aug 28 05:28:55 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B03811E8165 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 05:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.397
X-Spam-Level: 
X-Spam-Status: No, score=-102.397 tagged_above=-999 required=5 tests=[AWL=-0.098, 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 nElMjZIYX9l2 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 05:28:54 -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 8D94921E805A for <ietf@ietf.org>; Wed, 28 Aug 2013 05:28:51 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.239]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7SCSNkW010829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 28 Aug 2013 05:28:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377692924; bh=tcf9LYZ6hLC8ezv4+PFwlAsJdddtrrEsBYHpLsuINB8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cW3e6XnpBtjZLYjYXYwoWtWeHfnhkWe2dbQn5oV8sHcOFi/fDG05leQFimCKa7WlU taIpGpGv4KX5rou0DeJy1vW6mU6urOnVIuFkzFrvNj+dxLtBwMyXiDdPs+VM4Sz8VE ITX1cwb37FyTW7JQor+TIFL+2iJJ+7IrU9UNHI18=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377692924; i=@elandsys.com; bh=tcf9LYZ6hLC8ezv4+PFwlAsJdddtrrEsBYHpLsuINB8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Cpz4hGXtbAgqZhPi9zxB4K6JcFwU0S4c5dnwFWfgzqAA76hET+43To7rh+x+S31kV jmFnpCmhxPCznBpGx7RvHVA7+MrZqs6Jrtyfe8Y9v8dEuvD6PeEA8MGMDq5Tha8C6K ilwEUuoxK9x6wKOp48pNKJNKoIj+8OVBx8FIbevk=
Message-Id: <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 28 Aug 2013 05:24:48 -0700
To: Mark Andrews <marka@isc.org>, Jelte Jansen <jelte.jansen@sidn.nl>, bmanning@vacation.karoshi.com, Olafur Gudmundsson <ogud@ogud.com>, mansaxel@besserwisser.org, David Conrad <drc@virtualized.org>, Patrik  =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.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, 28 Aug 2013 12:28:55 -0000

Hello,

It's difficult, some might say impossible, to get agreement on 
draft-ietf-spfbis-4408bis.  I would like to ask each of you, and 
anyone else, to provide your opinion about the following:

RFC 5507 primarily raises three concerns about TXT records:

   1.  The data in TXT is unstructured and subject to 
misinterpretation by other
       applications.

   2.  Wildcard issues.

   3.  Size issues.

The draft addresses (3) by discussing size considerations, and 
tangentially addresses (1) in Section 3.4.

I would like to ask everyone not to turn this into a debate by not 
discussing about the opinion stated by someone else.

Regards,
S. Moonesamy (as document shepherd)



From ron.even.tlv@gmail.com  Wed Aug 28 06:09:04 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46E3321E8050; Wed, 28 Aug 2013 06:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 8JzL-e8fZu2i; Wed, 28 Aug 2013 06:09:03 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id BDF1411E818B; Wed, 28 Aug 2013 06:09:01 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q54so5234987wes.33 for <multiple recipients>; Wed, 28 Aug 2013 06:09:00 -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 :thread-index:content-language; bh=TjoJ5THm/b/sHaxDZ2zkbVL7Fq+zQZWsmGZmeyIdRmw=; b=ssCBw3J3T6rKfySaciQjl/semwm+3ZhXdQxhb+EvrIddlfTp8+Lm+QAdAhG9Kgoz/j uq7OGmXn90z4KSk1GBsM/A/aacjnKtrjGSAAHdFFPfaIH/7O2r0tOEBTV9WE4TKtFr2H YUtDJGwNDHyajX3lHIlJ87o6Ga52LP09c0/InqODL9iXDo3Qv3s68TmGHsmL9gp0APS0 yrie10E0UET36Uj5RdNZT8IH2hBavXwnm2jyQ9nJj263NEcTtZqhd7qYQEqpbwWZa/wI Dsgcxouql64EtZgAgg9M3kAKCJvR589aumHqpBAt6Xtnes06erLyEZ+ah2gqJTiT7anN 8ZXg==
X-Received: by 10.194.94.201 with SMTP id de9mr1846225wjb.78.1377695339756; Wed, 28 Aug 2013 06:08:59 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id om9sm4957786wic.8.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 28 Aug 2013 06:08:58 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Wed, 28 Aug 2013 16:06:28 +0300
Message-ID: <041001cea3ef$6a931b60$3fb95220$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0411_01CEA408.8FE116B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6j72iTQaEc2KyVR6aJXw9+GJi+Ew==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 13:09:04 -0000
X-List-Received-Date: Wed, 28 Aug 2013 13:09:04 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0411_01CEA408.8FE116B0
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-mpls-return-path-specified-lsp-ping-12

Reviewer: Roni Even

Review Date:2013-8-28

IETF LC End Date: 2013-9-4

IESG Telechat date: 

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

Minor issues:

I am not clear on the sub-TLV in section 6.2

1.	If a new sub-TLV is defined for TLV type 1 do they need also to be
added to TLV type 21. This should be clear, and if there is some relation I
think it should be reflected in the IANA registry for TLV type 1
2.	For the vendor or private use why a difference policy than the rest
of the sub-TLV registry 

 

Nits/editorial comments:

1.	In section 3.4 I assume that "TC" is traffic class. It will be good
to expand and have reference.

 


------=_NextPart_000_0411_01CEA408.8FE116B0
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:2001153705;
	mso-list-type:hybrid;
	mso-list-template-ids:811757280 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:2027515742;
	mso-list-type:hybrid;
	mso-list-template-ids:-121760254 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mpls-return-path-specified-lsp-ping-12</span><o:p></o:p>=
</p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-9&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>I am =
not clear on the sub-TLV in section 6.2<o:p></o:p></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo1'>If a new sub-TLV is defined for TLV =
type 1 do they need also to be added to TLV type 21. This should be =
clear, and if there is some relation I think it should be reflected in =
the IANA registry for TLV type 1<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l1 level1 lfo1'>For the vendor or private use why a =
difference policy than the rest of the sub-TLV registry =
<o:p></o:p></li></ol><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'mso-list:l0 level1 lfo2'>In section 3.4 I assume that =
&#8220;TC&#8221; is traffic class. It will be good to expand and have =
reference.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0411_01CEA408.8FE116B0--


From paf@frobbit.se  Wed Aug 28 06:48:00 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4817A11E81BA for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 06:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBt8ZYQF1pA8 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 06:47:59 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 4E24D11E819E for <ietf@ietf.org>; Wed, 28 Aug 2013 06:47:59 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::12] (unknown [IPv6:2a02:80:3ffc::12]) by mail.frobbit.se (Postfix) with ESMTPA id 44180265E2; Wed, 28 Aug 2013 15:47:52 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_F406CC14-F94F-4A40-8ED3-CEB570C13F8A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
Date: Wed, 28 Aug 2013 15:47:51 +0200
Message-Id: <75046795-D03D-46F1-82CC-36F577735070@frobbit.se>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org, bmanning@vacation.karoshi.com, mansaxel@besserwisser.org, Olafur Gudmundsson <ogud@ogud.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, 28 Aug 2013 13:48:00 -0000

--Apple-Mail=_F406CC14-F94F-4A40-8ED3-CEB570C13F8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 28 aug 2013, at 14:24, S Moonesamy <sm+ietf@elandsys.com> wrote:

> It's difficult, some might say impossible, to get agreement on =
draft-ietf-spfbis-4408bis.  I would like to ask each of you, and anyone =
else, to provide your opinion about the following:
>=20
> RFC 5507 primarily raises three concerns about TXT records:

As the main editor of RFC5507 I might have a different view of what RFC =
5507 says than others...but...that said, here are my comments.

RFC5507 first of all lists a number of prerequisites that should always =
be taken into account when extending the functionality of the domain =
name system. The intention was that the alternatives in section 3 where =
to be taken seriously as a way to solve the main problem, that the =
client when querying the DNS should be able to do a selection of what =
records the client needs by including the selector inside the triple =
{owner, type, class}. To solve that, there are a number of possible =
solutions.

Then there are specific discussions about the TXT resource record as you =
say, and those issues are included in the three issues you list below.

>  1.  The data in TXT is unstructured and subject to misinterpretation =
by other
>      applications.

The data is in fact structured, in the form of a series of strings, each =
one of them max 255 bytes long. But you are correct in the fact that =
RFC5507 does not go into those details. But, the SPF specification do =
not use this structuring that do exist, although it do (which is good) =
explicitly say that multiple such strings should first be concatenated =
before progressing with parsing the SPF record.

There is though no registry for the various formal uses of TXT records, =
and because of that there might be confusion among the various uses. =
Note that I am not saying that it is harder to write parsers, as for =
example an attacker can intentionally try to feed whatever data into =
whatever format a resource record do have. The parser must be robust =
regardless of the format.

Whether the SPF format itself is too complicated (I see various =
theoretical calculations on hundreds of RRSets be needed to get one SPF =
resolution correct) or not, that is *NOT* something I am evaluating =
here.

>  2.  Wildcard issues.

Correct.

>  3.  Size issues.

Correct, in two ways. It explicitly talks about the size of the TXT =
record, but RFC5507 also talks about the size of a Resource Record Set, =
which is what is returned to the client that queries. One also have to =
think about the size of the transaction, and specifically the complete =
response sent from the server, that contain multiple resource record =
sets.

I.e. we have:

3.1. The size limit 255 bytes for one string in the TXT record
3.2. The size of one TXT resource record (because the data is stored as =
text and not binary)
3.3. The size of a resource record set with the same owner, type and =
class
3.4. The size of a response to a query for a specific owner, type and =
class

> The draft addresses (3) by discussing size considerations, and =
tangentially addresses (1) in Section 3.4.

If we take the size issue first (3) it sort of looks at all of =
(3.1)-(3.4) above but not in a very clear way. The discussion in =
specifically section 3.4 is very confusing. It mixes up DNS response =
size with UDP payload size with MTU size. Because the text is not clear =
in its assumptions, it is very hard to say whether one agree or not with =
the conclusions. In turn, that leads to it being even harder to decide =
whether one agree or not with the conclusions on being as backward =
compatible with "old implementations" as is claimed being a necessity. =
I.e. there are a lot of claims in 3.4 based on unclear assumptions.

Further, if 3.4 is looking at the full response size, then it should =
also look at the response size in a similar way that has been done for =
DNSSEC, where also DNSSEC material is part of the response size (but =
then of course EDNS0 is in use).

Regarding the structure of the data, (1) above, it touches on it in =
section 3.3 and 3.4, but in reality the structure is really up to the =
parser and I think that is for this discussion sort of a non-issue.

I am more worried over (3.3) above, which is the core of RFC5507 that is =
really a problem, specifically together with the lack of a registry for =
the selectors that is part of the RDATA. If we compare with the other =
experience we do have, NAPTR, where this problem is a fact, we at least =
have a registry for the selectors so that we do know there will not be =
any collisions.

Yes, I do know SPF syntax do have an ability to refer to a record with a =
prefix, but that does not really help as the large RRSet is sent back in =
the response already to the first query.

> I would like to ask everyone not to turn this into a debate by not =
discussing about the opinion stated by someone else.
>=20
> Regards,
> S. Moonesamy (as document shepherd)

   Patrik



--Apple-Mail=_F406CC14-F94F-4A40-8ED3-CEB570C13F8A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlId/4gACgkQrMabGguI182XrgCfdhlqlhgyrn2wCJpdyLfhnXzm
/boAn1q8yOYoeY8Gs3DJ48jRAAQcmlvS
=padr
-----END PGP SIGNATURE-----

--Apple-Mail=_F406CC14-F94F-4A40-8ED3-CEB570C13F8A--

From loa@pi.nu  Wed Aug 28 07:20:17 2013
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5506211E813A; Wed, 28 Aug 2013 07:20:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48JZT6KHO0rk; Wed, 28 Aug 2013 07:20:12 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 794B911E811F; Wed, 28 Aug 2013 07:20:12 -0700 (PDT)
Received: from [192.168.5.58] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id B6CD918033E4; Wed, 28 Aug 2013 16:20:11 +0200 (CEST)
Message-ID: <521E071F.7050607@pi.nu>
Date: Wed, 28 Aug 2013 16:20:15 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
References: <041001cea3ef$6a931b60$3fb95220$@gmail.com>
In-Reply-To: <041001cea3ef$6a931b60$3fb95220$@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: gen-art@ietf.org, draft-ietf-mpls-return-path-specified-lsp-ping.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: Wed, 28 Aug 2013 14:20:17 -0000

Roni,

Thanks for an insightful review, you have captured much of what we
been struggling with when it comes to the IANA allocations.

On 2013-08-28 15:06, Roni Even wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> Summary: This draft is almost ready for publication as a standard track RFC.
>
> Major issues:
>
> Minor issues:
>
> I am not clear on the sub-TLV in section 6.2
>
>  1. If a new sub-TLV is defined for TLV type 1 do they need also to be
>     added to TLV type 21.

Yes the document says "Directly copied from TLV Type 1, MUST NOT be
assigned" the intention is that this applies to future sub-TLVs also.
I guess it could be changed to "Directly copied from TLV Type 1
(including future allocations for TLV Type 1, MUST NOT be assigned"
if that makes thing clearer.

>     This should be clear, and if there is some
>     relation I think it should be reflected in the IANA registry for TLV
>     type 1

I guess that makes sense - but it has not been the what we've done 
earlier - I think we could add this where needed by directly
communicate  this to IANA.

>  2. For the vendor or private use why a difference policy than the rest
>     of the sub-TLV registry

We don't assign vendor private use at all, so by default it is
different. I don't see that it could be different.

/Loa
>
> Nits/editorial comments:
>
>  1. In section 3.4 I assume that “TC” is traffic class. It will be good
>     to expand and have reference.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From dhc@dcrocker.net  Wed Aug 28 07:21:28 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C4B11E813A for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 07:21:27 -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 qbxiPKea9hE6 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 07:21:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 287FE11E811F for <ietf@ietf.org>; Wed, 28 Aug 2013 07:21:21 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7SELHdx032577 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Wed, 28 Aug 2013 07:21:20 -0700
Message-ID: <521E0759.7090504@dcrocker.net>
Date: Wed, 28 Aug 2013 07:21:13 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
In-Reply-To: <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 28 Aug 2013 07:21:20 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 14:21:28 -0000

On 8/28/2013 5:24 AM, S Moonesamy wrote:
> It's difficult, some might say impossible, to get agreement on
> draft-ietf-spfbis-4408bis.  I would like to ask each of you, and anyone
> else, to provide your opinion about the following:
>
> RFC 5507 primarily raises three concerns about TXT records:


RFC 5507 is irrelevant to consideration of the SPFbis draft.

Really.

RFC 5507 concerns approaches to design.  However the SPFbis draft is not 
designing a new capability.  It is documenting a mechanism that has 
existed for quite a long time, is very widely deployed, and has become 
an essential part of Internet Mail's operational infrastructure that 
works to counter abuse.

Internet Mail already relies on SPF and has for many years.

To consider RFC 5507 with respect to SPFbis is to treat the current 
draft as a matter of new work, which it isn't.

No one is arguing that SPF's use of the TXT record is preferable.  All 
newer uses of the TXT record use a scoping mechanism (through an 
underscore-based node name) to avoid all of the classic TXT record 
ambiguity concerns.

My professional assessment of SPF is that there are many ways it could 
have been designed better.  My other professional assessment is that the 
design quality of SPF ceased to be a relevant consideration, as soon as 
it gained widespread traction.

Wide deployment equals very large-scale consensus and quite a lot of 
running code.  The IETF says it cares about those two attributes.

If IETF technical work is to have any relation to the operational 
Internet, it needs to treat solid, real-world deployment as having 
higher priority than theoretical technical perfection.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott@kitterman.com  Wed Aug 28 07:39:28 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A901C21F9A96 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 07:39: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 IIhtOga4VEUV for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 07:39:23 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id A5F8621F8F9A for <ietf@ietf.org>; Wed, 28 Aug 2013 07:39:11 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 3850220E410F; Wed, 28 Aug 2013 10:39:11 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1377700751; bh=3hfrzh07ELYI7m2hR7TPQcWrKRWY2e+DijIcakDSzIQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=o7Rb9tFSyD+2jRuuN+VJzcjztvL9WbcaiYymFf2zU2c/Ztlr+5auwkXiaXhRPZTzO gnavl0K/DyRGv+8TMOzhsypwoWN7N1RIgnsam0pis9DKJ7sZHHyqcmPZVH5kh9HeTv sOk5hQbVDZkYEj9pLIE7J+KbR7HAz3SwesCj7KW8=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 1C9FA20E40CB;  Wed, 28 Aug 2013 10:39:10 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
Date: Wed, 28 Aug 2013 10:39:10 -0400
Message-ID: <5302045.mhsSG3B5bL@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <521E0759.7090504@dcrocker.net>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net> <521E0759.7090504@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2013 14:39:28 -0000

On Wednesday, August 28, 2013 07:21:13 Dave Crocker wrote:
> On 8/28/2013 5:24 AM, S Moonesamy wrote:
> > It's difficult, some might say impossible, to get agreement on
> > draft-ietf-spfbis-4408bis.  I would like to ask each of you, and anyone
> > else, to provide your opinion about the following:
> 
> > RFC 5507 primarily raises three concerns about TXT records:
> RFC 5507 is irrelevant to consideration of the SPFbis draft.
> 
> Really.
> 
> RFC 5507 concerns approaches to design.  However the SPFbis draft is not
> designing a new capability.  It is documenting a mechanism that has
> existed for quite a long time, is very widely deployed, and has become
> an essential part of Internet Mail's operational infrastructure that
> works to counter abuse.
> 
> Internet Mail already relies on SPF and has for many years.
> 
> To consider RFC 5507 with respect to SPFbis is to treat the current
> draft as a matter of new work, which it isn't.
> 
> No one is arguing that SPF's use of the TXT record is preferable.  All
> newer uses of the TXT record use a scoping mechanism (through an
> underscore-based node name) to avoid all of the classic TXT record
> ambiguity concerns.
> 
> My professional assessment of SPF is that there are many ways it could
> have been designed better.  My other professional assessment is that the
> design quality of SPF ceased to be a relevant consideration, as soon as
> it gained widespread traction.
> 
> Wide deployment equals very large-scale consensus and quite a lot of
> running code.  The IETF says it cares about those two attributes.
> 
> If IETF technical work is to have any relation to the operational
> Internet, it needs to treat solid, real-world deployment as having
> higher priority than theoretical technical perfection.

Yes.  Please.

Scott K

From marka@isc.org  Wed Aug 28 07:52:51 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 979E211E81B6 for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 07:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[AWL=0.198,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzVxNF04T5Na for <ietf@ietfa.amsl.com>; Wed, 28 Aug 2013 07:52:46 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id F0D3311E819F for <ietf@ietf.org>; Wed, 28 Aug 2013 07:52:45 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id C9478C94A8; Wed, 28 Aug 2013 14:52:32 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1377701565; bh=wcZlIs+kRLyfUWC79Q8507XIv+VqdekiPMrlBSCUBII=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=HLCoVG6z2KCLmIybt8CL57fMZkzY4WBoFHFhetn3A7SX96RLYnPrtBVc3n+W8XmgX TiRbyRcVi3Ai6Kyse3lJM0IteT6iwYu7gMlMYGaOemLhSDWXPRD+f9XQh1Umqnr1dj l9jJ0fvD1Tmt5pFb0VFVMgl9SoVZorMgpyIrN1i0=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Wed, 28 Aug 2013 14:52:32 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id E2A76160459; Wed, 28 Aug 2013 14:53:13 +0000 (UTC)
Received: from drugs.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id AF45C160446; Wed, 28 Aug 2013 14:53:13 +0000 (UTC)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 93D4F38F1E0F; Thu, 29 Aug 2013 00:52:20 +1000 (EST)
To: S Moonesamy <sm+ietf@elandsys.com>
From: Mark Andrews <marka@isc.org>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-reply-to: Your message of "Wed, 28 Aug 2013 05:24:48 -0700." <6.2.5.6.2.20130828044224.06ee3980@resistor.net>
Date: Thu, 29 Aug 2013 00:52:20 +1000
Message-Id: <20130828145220.93D4F38F1E0F@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: ietf@ietf.org, bmanning@vacation.karoshi.com, Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>, mansaxel@besserwisser.org, Olafur Gudmundsson <ogud@ogud.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, 28 Aug 2013 14:52:51 -0000

In message <6.2.5.6.2.20130828044224.06ee3980@resistor.net>, S Moonesamy writes
:
> Hello,
> 
> It's difficult, some might say impossible, to get agreement on 
> draft-ietf-spfbis-4408bis.  I would like to ask each of you, and 
> anyone else, to provide your opinion about the following:
> 
> RFC 5507 primarily raises three concerns about TXT records:
> 
>    1.  The data in TXT is unstructured and subject to 
> misinterpretation by other
>        applications.
> 
>    2.  Wildcard issues.
> 
>    3.  Size issues.
> 
> The draft addresses (3) by discussing size considerations, and 
> tangentially addresses (1) in Section 3.4.
> 
> I would like to ask everyone not to turn this into a debate by not 
> discussing about the opinion stated by someone else.
> 
> Regards,
> S. Moonesamy (as document shepherd)

I would start by saying that the list of issues identified by RFC
5507 is not complete.  RFC 5507 addresses selection of data to be
returned by the nameserver.

It fails to address the issues of updating data in the server using
RFC 2136 + RFC 2845.  For prefix, suffix and a new types this is
pretty straight forward as you have a <name,type,class> tuple that
is unique to the application and nameservers have access control
mechanisms that are designed to allow / disallow updates at this
level so you can hand out the ability to update records without
having unintended consequences.

When you place selectors inside records which have a shared purpose
you lose the ability to hand out selective update without risking
unintended consequences or you require nameserver vendors to develop
new access control mechanisms which work on the record contents in
addition to the <name,type,class> tuple.

You can't say delete all records of this type at this name then add
this replacement set in a single transaction.

It becomes read the data at the tuple, workout what to delete, send
a update message that selectively deletes then adds records.  This
introduces race conditions etc.

As for wildards.  Spf is often used to say that names generated by
wildcards do not send email.  This essentially precludes the use
of a prefix.

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

From ron.even.tlv@gmail.com  Wed Aug 28 08:25:25 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A09FC11E81FE; Wed, 28 Aug 2013 08:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Dii-V+9ZX1HA; Wed, 28 Aug 2013 08:25:25 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id E896E11E81BD; Wed, 28 Aug 2013 08:25:23 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e11so2350211wgh.33 for <multiple recipients>; Wed, 28 Aug 2013 08:25:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=OPIjaM97TcBH5tn4aWo8b40YpCiRSaDFfIGQfT3oMnA=; b=RMwsWjxf6jxqgru7jPTsjfcF5pXc+8uQkn274aR89e78uEr0JcBcKoW2bYhUmaV3Ix Zi1CbpQWoVQpv5mTn+ChMM3x2gHTkqyb7QBZtAqIht8eQoDZjoHpaI3W9EMp9VpwD9h7 DitT1oXm2l0ZPVygnkW9fya1cc4uU1VGPezRlCNIIjh9PB78ZayXS7FmgaMtQYGEkq+D sw5TFtgqUpYSFNl/Mx1lIEt9IFYCzbaizAR/RlnXkGnu732pe9pUWQBLWCmF7lkEakNr vAtALy/dhQsyEpJ65fZQdLRFhsSduMKKpdKDD/lHBCQmJTgnhRNfKzzDjzgqBfge5oaa S5aA==
X-Received: by 10.194.250.69 with SMTP id za5mr2967820wjc.80.1377703521719; Wed, 28 Aug 2013 08:25:21 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id iz19sm5825241wic.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 28 Aug 2013 08:25:21 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Loa Andersson'" <loa@pi.nu>
References: <041001cea3ef$6a931b60$3fb95220$@gmail.com> <521E071F.7050607@pi.nu>
In-Reply-To: <521E071F.7050607@pi.nu>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Wed, 28 Aug 2013 18:22:52 +0300
Message-ID: <042801cea402$77bf5200$673df600$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI9zAalsB4SCJWxv5dBStZUqxRAeQE/hjT7mMJs2uA=
Content-Language: en-us
Cc: gen-art@ietf.org, draft-ietf-mpls-return-path-specified-lsp-ping.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: Wed, 28 Aug 2013 15:25:25 -0000

Hi Loa,
See inline
Roni

> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: 28 August, 2013 5:20 PM
> To: Roni Even
> Cc: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org;
gen-
> art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Roni,
> 
> Thanks for an insightful review, you have captured much of what we been
> struggling with when it comes to the IANA allocations.
> 
> On 2013-08-28 15:06, Roni Even wrote:
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > Summary: This draft is almost ready for publication as a standard track
RFC.
> >
> > Major issues:
> >
> > Minor issues:
> >
> > I am not clear on the sub-TLV in section 6.2
> >
> >  1. If a new sub-TLV is defined for TLV type 1 do they need also to be
> >     added to TLV type 21.
> 
> Yes the document says "Directly copied from TLV Type 1, MUST NOT be
> assigned" the intention is that this applies to future sub-TLVs also.
> I guess it could be changed to "Directly copied from TLV Type 1 (including
> future allocations for TLV Type 1, MUST NOT be assigned"
> if that makes thing clearer.
> 
> >     This should be clear, and if there is some
> >     relation I think it should be reflected in the IANA registry for TLV
> >     type 1
> 
> I guess that makes sense - but it has not been the what we've done earlier
- I
> think we could add this where needed by directly communicate  this to
IANA.


[Roni Even] I think that the directive for future allocation must be clear
both in the IANA registry and the document for example look at
http://tools.ietf.org/html/rfc6426#section-7.3 
I also think that is this case this document updates RFC4379 .

> 
> >  2. For the vendor or private use why a difference policy than the rest
> >     of the sub-TLV registry
> 
> We don't assign vendor private use at all, so by default it is different.
I don't
> see that it could be different.> 
[Roni Even] RFC4379 says 
"If a TLV or sub-TLV has a Type that falls in the range for Vendor
   Private Use, the Length MUST be at least 4, and the first four octets
   MUST be that vendor's SMI Private Enterprise Number, in network octet
   order.  The rest of the Value field is private to the vendor."

> /Loa
> >
> > Nits/editorial comments:
> >
> >  1. In section 3.4 I assume that "TC" is traffic class. It will be good
> >     to expand and have reference.
> >
> 
> --
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64


From mach.chen@huawei.com  Thu Aug 29 01:33:08 2013
Return-Path: <mach.chen@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1553F21F9E51; Thu, 29 Aug 2013 01:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 oZiGKUDQU57P; Thu, 29 Aug 2013 01:33:04 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B4B121F9E83; Thu, 29 Aug 2013 01:33:01 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AWR89767; Thu, 29 Aug 2013 08:33:01 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 09:32:11 +0100
Received: from SZXEML448-HUB.china.huawei.com (10.82.67.191) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 09:33:00 +0100
Received: from szxeml558-mbs.china.huawei.com ([169.254.8.196]) by szxeml448-hub.china.huawei.com ([10.82.67.191]) with mapi id 14.01.0323.007; Thu, 29 Aug 2013 16:32:53 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org" <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Thread-Index: Ac6j72iTQaEc2KyVR6aJXw9+GJi+EwAZqLIAAA8JaoA=
Date: Thu, 29 Aug 2013 08:32:53 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.96.176]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 08:33:08 -0000

Hi Roni,

Thanks for your detailed review and comments!

Please see my reply inline...

> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> Sent: Wednesday, August 28, 2013 9:06 PM
> To: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: Gen-ART LC review of=20
> draft-ietf-mpls-return-path-specified-lsp-ping-12
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on=20
> Gen-ART, please see the FAQ at=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> Please resolve these comments along with any other Last Call comments=20
> you may receive.
> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> Reviewer: Roni Even
> Review Date:2013-8-28
> IETF LC End Date: 2013-9-4
> IESG Telechat date:
>=20
> Summary: This draft is almost ready for publication as a standard track R=
FC.
>=20
>=20
> Major issues:
> Minor issues:
> I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV is=20
> defined for TLV type 1 do they need also to be added to TLV type 21.=20
> This should be clear, and if there is some relation I think it should=20
> be reflected in the IANA registry for TLV type 1

Yes, type 21 TLV intends to reuse existing and future defined sub-TLVs for =
type TLV 1. And in Section 3.3, it has already stated this, it says:

"The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
   identify a specific return path.  The Reply Path TLV can carry any
   sub-TLV defined for use in the Target FEC Stack TLV that can be
   registered."

So, for Section 6.2, to make it cleaner and more explicit, how about this c=
hange:

Old:

" No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
   are made directly for TLV Type 21, sub-TLVs in these ranges are
   copied from the assignments made for TLV Type 1. Assignments of sub-..."

New:

" No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
   are made directly for TLV Type 21, sub-TLVs in these ranges are
   copied from the assignments (including existing and future allocations)
   made for TLV Type 1. Assignments of sub-..."


> 2. For the vendor or private use why a difference policy than the rest=20
> of the sub-TLV registry

This document does not make any changes to the "Vendor and Private use" def=
inition, range and policy as defined in RFC4379. In RFC4379, it's policy is=
 defined different from other ranges.=20

>=20
> Nits/editorial comments:
> 1. In section 3.4 I assume that "TC" is traffic class. It will be good=20
> to expand and have reference.

OK, will fix it when all last call comments received.

Best regards,
Mach


From ron.even.tlv@gmail.com  Thu Aug 29 02:23:58 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B0F11E810C; Thu, 29 Aug 2013 02:23: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=[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 oCjqZLUbQV-H; Thu, 29 Aug 2013 02:23:57 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9E02B11E8109; Thu, 29 Aug 2013 02:23:56 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e11so161647wgh.33 for <multiple recipients>; Thu, 29 Aug 2013 02:23:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=Tgj7/CB4UuBexTphdsz6va6OccZY4hz9+AIA+fSYiV4=; b=JBqEdgQU2mXnbcXgOKEBEZYQ6pGHrnmM10IrymaRzjqH36lVFMgSRBSf+TcET17GMl qpHhtQZH3MHnzfHjrsL0zqvX/0YdaoTZu0DRPSyvTC6KsPkIEK8ZE+FFGCeoC9qdAeoi U19M3gsJyt2BBGaZWST67rnE95TvUuIxZ1sfgrdwRPFk+UVjwd+y4VF3aNG9j9XCug3q T46wv1BpwMB1JhMz8NiDQX9lLQH5cRqP3CSsDekv3IHfEKuus1DwwHhD6R20cqZ0W9NU gBg68swPYIpgd6F2e4Ao8jDUgiagQQqkgeis13EmlIJolcxfc20OnQuyWJBnCnomzGyz 1mJQ==
X-Received: by 10.194.176.163 with SMTP id cj3mr4408016wjc.8.1377768233925; Thu, 29 Aug 2013 02:23:53 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id mb7sm10953960wic.10.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 02:23:53 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mach Chen'" <mach.chen@huawei.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Thu, 29 Aug 2013 12:21:23 +0300
Message-ID: <04cf01cea499$22eb4a80$68c1df80$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSmphrvgA=
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, 29 Aug 2013 09:23:58 -0000

Hi,
I am not sure you responded to my latest email.

Having the policy for TLV type 1 here is not enough in my view since I only
look at RFC4379 and create a new TLV type I will not know that I have to
register it also for the type 21 if it will not be mentioned

As for the vendor specific see my other email
Roni

> -----Original Message-----
> From: Mach Chen [mailto:mach.chen@huawei.com]
> Sent: 29 August, 2013 11:33 AM
> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Hi Roni,
> 
> Thanks for your detailed review and comments!
> 
> Please see my reply inline...
> 
> > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > Sent: Wednesday, August 28, 2013 9:06 PM
> > To: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-ping-12
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > Reviewer: Roni Even
> > Review Date:2013-8-28
> > IETF LC End Date: 2013-9-4
> > IESG Telechat date:
> >
> > Summary: This draft is almost ready for publication as a standard track
RFC.
> >
> >
> > Major issues:
> > Minor issues:
> > I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV is
> > defined for TLV type 1 do they need also to be added to TLV type 21.
> > This should be clear, and if there is some relation I think it should
> > be reflected in the IANA registry for TLV type 1
> 
> Yes, type 21 TLV intends to reuse existing and future defined sub-TLVs for
> type TLV 1. And in Section 3.3, it has already stated this, it says:
> 
> "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
>    identify a specific return path.  The Reply Path TLV can carry any
>    sub-TLV defined for use in the Target FEC Stack TLV that can be
>    registered."
> 
> So, for Section 6.2, to make it cleaner and more explicit, how about this
> change:
> 
> Old:
> 
> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>    are made directly for TLV Type 21, sub-TLVs in these ranges are
>    copied from the assignments made for TLV Type 1. Assignments of
sub-..."
> 
> New:
> 
> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>    are made directly for TLV Type 21, sub-TLVs in these ranges are
>    copied from the assignments (including existing and future allocations)
>    made for TLV Type 1. Assignments of sub-..."
> 
> 
> > 2. For the vendor or private use why a difference policy than the rest
> > of the sub-TLV registry
> 
> This document does not make any changes to the "Vendor and Private use"
> definition, range and policy as defined in RFC4379. In RFC4379, it's
policy is
> defined different from other ranges.
> 
> >
> > Nits/editorial comments:
> > 1. In section 3.4 I assume that "TC" is traffic class. It will be good
> > to expand and have reference.
> 
> OK, will fix it when all last call comments received.
> 
> Best regards,
> Mach


From jari.arkko@piuha.net  Thu Aug 29 02:59:23 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8AC21F9EF4; Thu, 29 Aug 2013 02:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.475
X-Spam-Level: 
X-Spam-Status: No, score=-101.475 tagged_above=-999 required=5 tests=[AWL=-1.176, BAYES_00=-2.599, MANGLED_LIST=2.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 cd8bq78UQHAW; Thu, 29 Aug 2013 02:59:12 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E1EAE21F9F19; Thu, 29 Aug 2013 02:59:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5C4382CC54; Thu, 29 Aug 2013 12:59:07 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIAn2P32oVi9; Thu, 29 Aug 2013 12:59:06 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 55A9B2CC50; Thu, 29 Aug 2013 12:59:06 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-geopriv-res-gw-lis-discovery-05
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CE1EC68E.5B19%peter@akayla.com>
Date: Thu, 29 Aug 2013 12:59:06 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <65B21C40-435C-45DB-8E64-CEE73E728037@piuha.net>
References: <CE1EC68E.5B19%peter@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1508)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-geopriv-res-gw-lis-discovery.all@tools.ietf.org, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 09:59:24 -0000

Peter: Thank you very much for your review.=20

Based on this review and my own review, I am recommending the approval =
of this draft in today's telechat. (Note that other ADs have raised a =
number of other issues, some of which I agree with, but I did not want =
to repeat their comments.)

Jari

On Jul 31, 2013, at 11:50 PM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-geopriv-res-gw-lis-discovery-05
> Reviewer: Peter Yee
> Review Date: Jul-31-2013
> IETF LC End Date: Jul-31-2013
> IESG Telechat date: TBD
>=20
> Summary: This draft is basically ready for publication, but has nits =
that
> should be fixed before publication. [Ready with nits.]
>=20
> The draft describes a means by which Devices behind a residential =
gateway
> may discover the correct Location Information Server on the access =
network
> providing Internet access to residential gateway.  The Device may =
thereby
> gain access to certain location-based services.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits:
>=20
> Section 1, 1st paragraph, 2nd sentence: should "data" be appended
> after "location"?  The wording is otherwise odd.
>=20
> Page 7, 3rd paragraph: change "which" to "that".
>=20
> Page 9, section 4.2, 2nd paragraph, 1st sentence: I'll admit my =
ignorance
> of the finer points of the DNS and inquire what this sentence is =
supposed
> to mean.  To what are the additional domain names added and how does =
this
> allow a DNS record to cover a larger set of addresses?  Perhaps it's =
just
> the wording or my lack of knowledge, but I didn't follow this point =
fully.
>=20
> Page 9, section 4.2, 2nd bullet item: change "sucessively" to
> "successively".
>=20
> Page 11, section 4.6, 1st paragraph, 4th sentence: insert "a" before
> "STUN server" or change "server" to "servers" depending on how many
> need to be configured.
>=20
> Page 12, 1st sentence: delete "a".
>=20
> Page 12, 1st sentence: What about /56 for IPv6?
>=20
> Page 14, 3rd paragraph, 2nd sentence: delete "a" before
> "IP addresses" or change "addresses" to "address" depending on
> how many false addresses you mean.
>=20
> Page 14, 6th paragraph, last sentence: Are there any concrete
> suggestions on who a device might determine accuracy?
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From mach.chen@huawei.com  Thu Aug 29 03:05:43 2013
Return-Path: <mach.chen@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4794321F9FB1; Thu, 29 Aug 2013 03:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 zBOdid8HmWI5; Thu, 29 Aug 2013 03:05:38 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EE05821F8411; Thu, 29 Aug 2013 03:05:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AWR99230; Thu, 29 Aug 2013 10:05:35 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 11:04:28 +0100
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 29 Aug 2013 11:05:17 +0100
Received: from szxeml558-mbs.china.huawei.com ([169.254.8.196]) by szxeml408-hub.china.huawei.com ([10.82.67.95]) with mapi id 14.01.0323.007; Thu, 29 Aug 2013 18:05:13 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org" <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Thread-Index: Ac6j72iTQaEc2KyVR6aJXw9+GJi+EwAZqLIAAA8JaoD//4fDgP//cOtg
Date: Thu, 29 Aug 2013 10:05:12 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com>
In-Reply-To: <04cf01cea499$22eb4a80$68c1df80$@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.96.176]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 10:05:43 -0000

Hi Roni,

How about this:

" No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
    are made directly for TLV Type 21, sub-TLVs in these ranges are=20
    copied from the assignments made for TLV Type 1 and kept the same
    as that for TLV Type 1. All sub-TLVs in these ranges (include existing
    and future defined) defined for TLV Type 1 apply to TLV Type 21.=20
    Assignments of sub-..."

Best regards,
Mach

> -----Original Message-----
> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> Sent: Thursday, August 29, 2013 5:21 PM
> To: Mach Chen; draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.i=
etf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-ping-12
>=20
> Hi,
> I am not sure you responded to my latest email.
>=20
> Having the policy for TLV type 1 here is not enough in my view since I on=
ly
> look at RFC4379 and create a new TLV type I will not know that I have to
> register it also for the type 21 if it will not be mentioned
>=20
> As for the vendor specific see my other email
> Roni
>=20
> > -----Original Message-----
> > From: Mach Chen [mailto:mach.chen@huawei.com]
> > Sent: 29 August, 2013 11:33 AM
> > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-
> > ping-12
> >
> > Hi Roni,
> >
> > Thanks for your detailed review and comments!
> >
> > Please see my reply inline...
> >
> > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > To: draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: Gen-ART LC review of
> > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > >
> > > I am the assigned Gen-ART reviewer for this draft. For background on
> > > Gen-ART, please see the FAQ at
> > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > Please resolve these comments along with any other Last Call comments
> > > you may receive.
> > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > Reviewer: Roni Even
> > > Review Date:2013-8-28
> > > IETF LC End Date: 2013-9-4
> > > IESG Telechat date:
> > >
> > > Summary: This draft is almost ready for publication as a standard tra=
ck
> RFC.
> > >
> > >
> > > Major issues:
> > > Minor issues:
> > > I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV is
> > > defined for TLV type 1 do they need also to be added to TLV type 21.
> > > This should be clear, and if there is some relation I think it should
> > > be reflected in the IANA registry for TLV type 1
> >
> > Yes, type 21 TLV intends to reuse existing and future defined sub-TLVs =
for
> > type TLV 1. And in Section 3.3, it has already stated this, it says:
> >
> > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
> >    identify a specific return path.  The Reply Path TLV can carry any
> >    sub-TLV defined for use in the Target FEC Stack TLV that can be
> >    registered."
> >
> > So, for Section 6.2, to make it cleaner and more explicit, how about th=
is
> > change:
> >
> > Old:
> >
> > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> >    copied from the assignments made for TLV Type 1. Assignments of
> sub-..."
> >
> > New:
> >
> > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> >    copied from the assignments (including existing and future allocatio=
ns)
> >    made for TLV Type 1. Assignments of sub-..."
> >
> >
> > > 2. For the vendor or private use why a difference policy than the res=
t
> > > of the sub-TLV registry
> >
> > This document does not make any changes to the "Vendor and Private use"
> > definition, range and policy as defined in RFC4379. In RFC4379, it's
> policy is
> > defined different from other ranges.
> >
> > >
> > > Nits/editorial comments:
> > > 1. In section 3.4 I assume that "TC" is traffic class. It will be goo=
d
> > > to expand and have reference.
> >
> > OK, will fix it when all last call comments received.
> >
> > Best regards,
> > Mach


From ron.even.tlv@gmail.com  Thu Aug 29 03:27:12 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A4521F9B8A; Thu, 29 Aug 2013 03:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Kr5GP1oKVUmE; Thu, 29 Aug 2013 03:27:11 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC8A21F9CA8; Thu, 29 Aug 2013 03:27:09 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id q58so234827wes.11 for <multiple recipients>; Thu, 29 Aug 2013 03:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=12I2Qk2wcGdRuI2OutOi0wUwTaUYNePL/nsso8VHbiA=; b=l8iztrY4b8nYHJAPu4iqImgmE1Z4QHPCqLjneLbF6iK9BdHpwOyaZ+CjzwSl8389eu aBQo4oQ3eaUIhi9QAsdI54/8CWgmLzHaXRnn2pUMB1feX8E0ArKVxgssxPqvIpvpINWG zU7WESvgkP3/nAUXr+R89Md2kmdk+HE+CzgO7UgJillwg9rFHToBslgdKt04Ai/yYSXG j15/xJBZEKJyEtV1Z6xhHk42HUa49eLwHeAknbhEaN2bEkQwh1ymp1afykUUBvfh5JFb P+IBHnyq/ePZs84GrYqPLRmvCvb++vlK1IZ647EGYLZ9KTI85ovGy1CmgY4F06kLDhIl Otkg==
X-Received: by 10.194.109.68 with SMTP id hq4mr4967067wjb.12.1377772028762; Thu, 29 Aug 2013 03:27:08 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id i8sm11388391wib.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 03:27:08 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mach Chen'" <mach.chen@huawei.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com>
In-Reply-To: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Thu, 29 Aug 2013 13:24:38 +0300
Message-ID: <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSAxjw2zQBgMlGEZpzr4RQ
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, 29 Aug 2013 10:27:12 -0000

Hi,
This text is OK if one wants to implement this draft.
My concern was about the consistency of the IANA registration so that if
someone defines a new TLV type 1 based on RFC4379, IANA will know that it
must update also the registry for TLV type 21. If you see no such problem, I
have no concerns
Roni

> -----Original Message-----
> From: Mach Chen [mailto:mach.chen@huawei.com]
> Sent: 29 August, 2013 1:05 PM
> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Hi Roni,
> 
> How about this:
> 
> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>     are made directly for TLV Type 21, sub-TLVs in these ranges are
>     copied from the assignments made for TLV Type 1 and kept the same
>     as that for TLV Type 1. All sub-TLVs in these ranges (include existing
>     and future defined) defined for TLV Type 1 apply to TLV Type 21.
>     Assignments of sub-..."
> 
> Best regards,
> Mach
> 
> > -----Original Message-----
> > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > Sent: Thursday, August 29, 2013 5:21 PM
> > To: Mach Chen;
> > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-ping-12
> >
> > Hi,
> > I am not sure you responded to my latest email.
> >
> > Having the policy for TLV type 1 here is not enough in my view since I
> > only look at RFC4379 and create a new TLV type I will not know that I
> > have to register it also for the type 21 if it will not be mentioned
> >
> > As for the vendor specific see my other email Roni
> >
> > > -----Original Message-----
> > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > Sent: 29 August, 2013 11:33 AM
> > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-
> > > ping-12
> > >
> > > Hi Roni,
> > >
> > > Thanks for your detailed review and comments!
> > >
> > > Please see my reply inline...
> > >
> > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > > To:
> > > > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > Subject: Gen-ART LC review of
> > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > >
> > > > I am the assigned Gen-ART reviewer for this draft. For background
> > > > on Gen-ART, please see the FAQ at
> > > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > > Please resolve these comments along with any other Last Call
> > > > comments you may receive.
> > > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > Reviewer: Roni Even
> > > > Review Date:2013-8-28
> > > > IETF LC End Date: 2013-9-4
> > > > IESG Telechat date:
> > > >
> > > > Summary: This draft is almost ready for publication as a standard
> > > > track
> > RFC.
> > > >
> > > >
> > > > Major issues:
> > > > Minor issues:
> > > > I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV
> > > > is defined for TLV type 1 do they need also to be added to TLV type
21.
> > > > This should be clear, and if there is some relation I think it
> > > > should be reflected in the IANA registry for TLV type 1
> > >
> > > Yes, type 21 TLV intends to reuse existing and future defined
> > > sub-TLVs for type TLV 1. And in Section 3.3, it has already stated
this, it
> says:
> > >
> > > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
> > >    identify a specific return path.  The Reply Path TLV can carry any
> > >    sub-TLV defined for use in the Target FEC Stack TLV that can be
> > >    registered."
> > >
> > > So, for Section 6.2, to make it cleaner and more explicit, how about
> > > this
> > > change:
> > >
> > > Old:
> > >
> > > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> > >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> > >    copied from the assignments made for TLV Type 1. Assignments of
> > sub-..."
> > >
> > > New:
> > >
> > > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> > >    are made directly for TLV Type 21, sub-TLVs in these ranges are
> > >    copied from the assignments (including existing and future
allocations)
> > >    made for TLV Type 1. Assignments of sub-..."
> > >
> > >
> > > > 2. For the vendor or private use why a difference policy than the
> > > > rest of the sub-TLV registry
> > >
> > > This document does not make any changes to the "Vendor and Private
> use"
> > > definition, range and policy as defined in RFC4379. In RFC4379, it's
> > policy is
> > > defined different from other ranges.
> > >
> > > >
> > > > Nits/editorial comments:
> > > > 1. In section 3.4 I assume that "TC" is traffic class. It will be
> > > > good to expand and have reference.
> > >
> > > OK, will fix it when all last call comments received.
> > >
> > > Best regards,
> > > Mach


From loa@pi.nu  Thu Aug 29 04:46:25 2013
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AF321F9D9C; Thu, 29 Aug 2013 04:46:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3PssOf5XD6XP; Thu, 29 Aug 2013 04:46:20 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3814A21F9D99; Thu, 29 Aug 2013 04:46:20 -0700 (PDT)
Received: from [192.168.5.58] (81-229-83-119-no65.business.telia.com [81.229.83.119]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8E89118033E4; Thu, 29 Aug 2013 13:46:18 +0200 (CEST)
Message-ID: <521F3489.1060600@pi.nu>
Date: Thu, 29 Aug 2013 13:46:17 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
In-Reply-To: <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-mpls-return-path-specified-lsp-ping.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, 29 Aug 2013 11:46:25 -0000

Roni,

tnx - the authors should add words in the IANA section requesting that
IANA add this the pointed in the registry; they normally do anyway, but
writing it down should not be a problem.

As for "Vendor Private" RFC 4379 says:

   "Values from "Vendor Private" ranges MUST NOT be registered with IANA;
    however, the message MUST contain an enterprise code as registered
    with the IANA SMI Private Network Management Private Enterprise
    Numbers.  For each name space that has a Vendor Private range, it
    must be specified where exactly the SMI Private Enterprise Number
    resides; see below for examples.  In this way, several enterprises
    (vendors) can use the same code point without fear of collision."

The way I read this is that the paragraph does two things (1) defines
the allocation policy (in this case that "vendor private" won't be
assigned by IANA) and (2) put a restriction on the "vendor private"
(sub-)TLVs; they must contain a "private enterprise number".

Up to now I've thought the restriction on the format was global for
all "vendor private" sub-TLVs that are used by TLV for LSP Ping.
However we put words to the same effect in e.g. 6424, wo there is no
reason not to do it here also. A pointer to RFC4379 should be enough
e.g.:

"For the vendor private sub-TLVs defined for this document, the
same allocation policies and requirement on the sub-TLV format that is
specified for vendor private sub-TLVs in RFC4379 [RFC4379] appliacable."

Would that cover you concern?

/Loa



On 2013-08-29 12:24, Roni Even wrote:
> Hi,
> This text is OK if one wants to implement this draft.
> My concern was about the consistency of the IANA registration so that if
> someone defines a new TLV type 1 based on RFC4379, IANA will know that it
> must update also the registry for TLV type 21. If you see no such problem, I
> have no concerns
> Roni
>
>> -----Original Message-----
>> From: Mach Chen [mailto:mach.chen@huawei.com]
>> Sent: 29 August, 2013 1:05 PM
>> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
>> ping.all@tools.ietf.org
>> Cc: ietf@ietf.org; gen-art@ietf.org
>> Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-
>> ping-12
>>
>> Hi Roni,
>>
>> How about this:
>>
>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>>      are made directly for TLV Type 21, sub-TLVs in these ranges are
>>      copied from the assignments made for TLV Type 1 and kept the same
>>      as that for TLV Type 1. All sub-TLVs in these ranges (include existing
>>      and future defined) defined for TLV Type 1 apply to TLV Type 21.
>>      Assignments of sub-..."
>>
>> Best regards,
>> Mach
>>
>>> -----Original Message-----
>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>> Sent: Thursday, August 29, 2013 5:21 PM
>>> To: Mach Chen;
>>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
>>> Cc: ietf@ietf.org; gen-art@ietf.org
>>> Subject: RE: Gen-ART LC review of
>>> draft-ietf-mpls-return-path-specified-lsp-ping-12
>>>
>>> Hi,
>>> I am not sure you responded to my latest email.
>>>
>>> Having the policy for TLV type 1 here is not enough in my view since I
>>> only look at RFC4379 and create a new TLV type I will not know that I
>>> have to register it also for the type 21 if it will not be mentioned
>>>
>>> As for the vendor specific see my other email Roni
>>>
>>>> -----Original Message-----
>>>> From: Mach Chen [mailto:mach.chen@huawei.com]
>>>> Sent: 29 August, 2013 11:33 AM
>>>> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
>>>> ping.all@tools.ietf.org
>>>> Cc: ietf@ietf.org; gen-art@ietf.org
>>>> Subject: RE: Gen-ART LC review of
>>> draft-ietf-mpls-return-path-specified-lsp-
>>>> ping-12
>>>>
>>>> Hi Roni,
>>>>
>>>> Thanks for your detailed review and comments!
>>>>
>>>> Please see my reply inline...
>>>>
>>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
>>>>> Sent: Wednesday, August 28, 2013 9:06 PM
>>>>> To:
>>>>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
>>>>> Cc: ietf@ietf.org; gen-art@ietf.org
>>>>> Subject: Gen-ART LC review of
>>>>> draft-ietf-mpls-return-path-specified-lsp-ping-12
>>>>>
>>>>> I am the assigned Gen-ART reviewer for this draft. For background
>>>>> on Gen-ART, please see the FAQ at
>>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>> Please resolve these comments along with any other Last Call
>>>>> comments you may receive.
>>>>> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
>>>>> Reviewer: Roni Even
>>>>> Review Date:2013-8-28
>>>>> IETF LC End Date: 2013-9-4
>>>>> IESG Telechat date:
>>>>>
>>>>> Summary: This draft is almost ready for publication as a standard
>>>>> track
>>> RFC.
>>>>>
>>>>>
>>>>> Major issues:
>>>>> Minor issues:
>>>>> I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV
>>>>> is defined for TLV type 1 do they need also to be added to TLV type
> 21.
>>>>> This should be clear, and if there is some relation I think it
>>>>> should be reflected in the IANA registry for TLV type 1
>>>>
>>>> Yes, type 21 TLV intends to reuse existing and future defined
>>>> sub-TLVs for type TLV 1. And in Section 3.3, it has already stated
> this, it
>> says:
>>>>
>>>> "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
>>>>     identify a specific return path.  The Reply Path TLV can carry any
>>>>     sub-TLV defined for use in the Target FEC Stack TLV that can be
>>>>     registered."
>>>>
>>>> So, for Section 6.2, to make it cleaner and more explicit, how about
>>>> this
>>>> change:
>>>>
>>>> Old:
>>>>
>>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
>>>>     copied from the assignments made for TLV Type 1. Assignments of
>>> sub-..."
>>>>
>>>> New:
>>>>
>>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
>>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
>>>>     copied from the assignments (including existing and future
> allocations)
>>>>     made for TLV Type 1. Assignments of sub-..."
>>>>
>>>>
>>>>> 2. For the vendor or private use why a difference policy than the
>>>>> rest of the sub-TLV registry
>>>>
>>>> This document does not make any changes to the "Vendor and Private
>> use"
>>>> definition, range and policy as defined in RFC4379. In RFC4379, it's
>>> policy is
>>>> defined different from other ranges.
>>>>
>>>>>
>>>>> Nits/editorial comments:
>>>>> 1. In section 3.4 I assume that "TC" is traffic class. It will be
>>>>> good to expand and have reference.
>>>>
>>>> OK, will fix it when all last call comments received.
>>>>
>>>> Best regards,
>>>> Mach
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From daedulus@btconnect.com  Thu Aug 29 04:57:52 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B9B21F8DA3 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 04:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AkCCCZYd1sVJ for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 04:57:39 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe006.messaging.microsoft.com [216.32.180.189]) by ietfa.amsl.com (Postfix) with ESMTP id 7162121F9B4B for <ietf@ietf.org>; Thu, 29 Aug 2013 04:57:36 -0700 (PDT)
Received: from mail198-co1-R.bigfish.com (10.243.78.226) by CO1EHSOBE004.bigfish.com (10.243.66.67) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 11:57:35 +0000
Received: from mail198-co1 (localhost [127.0.0.1])	by mail198-co1-R.bigfish.com (Postfix) with ESMTP id A33B5B400C7	for <ietf@ietf.org>; Thu, 29 Aug 2013 11:57:35 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.197; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -11
X-BigFish: PS-11(z56f4kz9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dc1h1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail198-co1 (localhost.localdomain [127.0.0.1]) by mail198-co1 (MessageSwitch) id 1377777453537557_28178; Thu, 29 Aug 2013 11:57:33 +0000 (UTC)
Received: from CO1EHSMHS002.bigfish.com (unknown [10.243.78.249])	by mail198-co1.bigfish.com (Postfix) with ESMTP id 81009720201	for <ietf@ietf.org>; Thu, 29 Aug 2013 11:57:33 +0000 (UTC)
Received: from DB3PRD0711HT001.eurprd07.prod.outlook.com (157.56.254.197) by CO1EHSMHS002.bigfish.com (10.243.66.12) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 11:57:32 +0000
Received: from DBXPRD0611HT003.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.183.34) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 11:57:20 +0000
Message-ID: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ietf <ietf@ietf.org>
Subject: "Deprecate"
Date: Thu, 29 Aug 2013 12:56:24 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 11:57:53 -0000

I recently saw 'deprecate' used in an IANA Considerations and turned to
"IANA Considerations" [RFC5226] to see how it was defined only to find
no mention of it there.  I am used to the term from SMI, as quoted
below, but that seems not quite right, in that a deprecated IANA entry
never disappears, as in
http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
s-5

Are there other, perhaps better definitions of the term 'deprecated' in
use outside SMI (and yes, I know about praying nuns!)?

Tom Petch

----- Original Message -----
From: "Fred Baker (fred)" <fred@cisco.com>
To: "IPv6 Maintanence" <ipv6@ietf.org>
Sent: Monday, July 29, 2013 3:32 PM
Subject: "Deprecate"


> At the mike a moment ago, I referred to an existing formal definition
of "deprecate". For the record, the reference is to RFC 1158, which
reads:
>
> 3.1.  Deprecated Objects
>
>    In order to better prepare implementors for future changes in the
>    MIB, a new term "deprecated" may be used when describing an object.
>    A deprecated object in the MIB is one which must be supported, but
>    one which will most likely be removed from the next version of the
>    MIB (e.g., MIB-III).
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



From adrian@olddog.co.uk  Thu Aug 29 05:22:47 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D6221E808F for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 05:22:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8paTwtIlQgHg for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 05:22:22 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id D5A6C21E8094 for <ietf@ietf.org>; Thu, 29 Aug 2013 05:22:21 -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 r7TCMHAq006872;  Thu, 29 Aug 2013 13:22:17 +0100
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [10.12.10.176]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMHaI006865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Aug 2013 13:22:17 +0100
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMHrL020013;  Thu, 29 Aug 2013 13:22:17 +0100
Received: from 950129200 ([50.95.132.233]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TCMEE8019976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 29 Aug 2013 13:22:15 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'t.p.'" <daedulus@btconnect.com>, "'ietf'" <ietf@ietf.org>
References: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.net>
In-Reply-To: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.net>
Subject: RE: "Deprecate"
Date: Thu, 29 Aug 2013 13:22:13 +0100
Message-ID: <071401cea4b2$66250840$326f18c0$@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: AQJgXz2YP9EIHcOzrUDi8tDD5n58r5iIpglg
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 12:22:47 -0000

Tom,

Not a complete answer but look in RFC 4020 (especially 3.3) and
draft-cotton-rfc4020bis (currently in IETF last call).

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of t.p.
> Sent: 29 August 2013 12:56
> To: ietf
> Subject: "Deprecate"
> 
> I recently saw 'deprecate' used in an IANA Considerations and turned to
> "IANA Considerations" [RFC5226] to see how it was defined only to find
> no mention of it there.  I am used to the term from SMI, as quoted
> below, but that seems not quite right, in that a deprecated IANA entry
> never disappears, as in
> http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-
> number
> s-5
> 
> Are there other, perhaps better definitions of the term 'deprecated' in
> use outside SMI (and yes, I know about praying nuns!)?
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Fred Baker (fred)" <fred@cisco.com>
> To: "IPv6 Maintanence" <ipv6@ietf.org>
> Sent: Monday, July 29, 2013 3:32 PM
> Subject: "Deprecate"
> 
> 
> > At the mike a moment ago, I referred to an existing formal definition
> of "deprecate". For the record, the reference is to RFC 1158, which
> reads:
> >
> > 3.1.  Deprecated Objects
> >
> >    In order to better prepare implementors for future changes in the
> >    MIB, a new term "deprecated" may be used when describing an object.
> >    A deprecated object in the MIB is one which must be supported, but
> >    one which will most likely be removed from the next version of the
> >    MIB (e.g., MIB-III).
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >



From chris.dearlove@baesystems.com  Thu Aug 29 05:23:28 2013
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 A065011E80F5 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 05:23:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.468
X-Spam-Level: 
X-Spam-Status: No, score=-10.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 hly74PEqp3BA for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 05:23:24 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id BFD3321E8099 for <ietf@ietf.org>; Thu, 29 Aug 2013 05:23:16 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,983,1367967600"; d="scan'208";a="368406317"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 29 Aug 2013 13:23:07 +0100
X-IronPort-AV: E=Sophos;i="4.89,983,1367967600"; d="scan'208";a="25689567"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasmds017.greenlnk.net with ESMTP; 29 Aug 2013 13:22:55 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.167]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 13:22:55 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: t.p. <daedulus@btconnect.com>, ietf <ietf@ietf.org>
Subject: RE: "Deprecate"
Thread-Topic: "Deprecate"
Thread-Index: AQHOpK8MflEosozqrkuNGBrMiI8cTZmsGcLg
Date: Thu, 29 Aug 2013 12:22:55 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0A61@GLKXM0002V.GREENLNK.net>
References: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.net>
In-Reply-To: <001301cea4ae$ccde2b60$4001a8c0@gateway.2wire.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"
MIME-Version: 1.0
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: Thu, 29 Aug 2013 12:23:28 -0000

It's definitely an ISO term, I see it used for features of C++.

There's then discussion even there of what it means. It is, I think, meant =
to be used for "we don't think you should use this, there's something bette=
r, and this is a warning that it may get removed in a future version". In t=
he case of computer languages there is an additional possibility of "your c=
ompiler may emit a warning if you persist in using it".

But the only major feature (export) removed in the last C++ version went st=
raight from "part of the standard, but only one compiler ever implemented i=
t, and thus found out it was a bad realisation of an idea" to removed, with=
 no intermediate deprecated stage. And other features just hang around depr=
ecated. So it really doesn't guarantee anything in that instance, neither t=
han if deprecated will go, not if not deprecated won't go.

-- =

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 t.p.
Sent: 29 August 2013 12:56
To: ietf
Subject: "Deprecate"

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

I recently saw 'deprecate' used in an IANA Considerations and turned to
"IANA Considerations" [RFC5226] to see how it was defined only to find
no mention of it there.  I am used to the term from SMI, as quoted
below, but that seems not quite right, in that a deprecated IANA entry
never disappears, as in
http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
s-5

Are there other, perhaps better definitions of the term 'deprecated' in
use outside SMI (and yes, I know about praying nuns!)?

Tom Petch

----- Original Message -----
From: "Fred Baker (fred)" <fred@cisco.com>
To: "IPv6 Maintanence" <ipv6@ietf.org>
Sent: Monday, July 29, 2013 3:32 PM
Subject: "Deprecate"


> At the mike a moment ago, I referred to an existing formal definition
of "deprecate". For the record, the reference is to RFC 1158, which
reads:
>
> 3.1.  Deprecated Objects
>
>    In order to better prepare implementors for future changes in the
>    MIB, a new term "deprecated" may be used when describing an object.
>    A deprecated object in the MIB is one which must be supported, but
>    one which will most likely be removed from the next version of the
>    MIB (e.g., MIB-III).
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



********************************************************************
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 ron.even.tlv@gmail.com  Thu Aug 29 05:51:45 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7633721F9F50; Thu, 29 Aug 2013 05:51:45 -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 RqD3BstNMqy2; Thu, 29 Aug 2013 05:51:44 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id E5EAC21F9F23; Thu, 29 Aug 2013 05:51:43 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id c11so370134wgh.3 for <multiple recipients>; Thu, 29 Aug 2013 05:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=NSNHutGeSCDbwOw4EiFesN2iJUHusMjEDKPGOP4qRq0=; b=nYJ4VSPfngbaH7A+pH7D+lF+mJNBPoE9p6Sq/sANrczhoK9infBoBkcgJh0jKlUVNX 9durBlWrvOw5kco99xbaX0n1y52YOek1rxGDCC6hzj6soJfnGfCnJxXknWd5YFQWv4xs lKkd7gJkF3HkpFMVFQDtKGkYDJXEsXRYbpkKBOQtEO/Uy7CY/v6HhCzaTEodsGzjg5e1 5F0TRjHFsxODX5cRmjVROpuQBpA6rp+yQi+9UYLG4PQQSqvG0AjU3+j718pC1rouXvok 3hujde3EnnfWEPnyRGxuTbv2K6EXSl+yEENS/R11BkzBR/Hwa+5E0WZidraJ1+TTpqqS PeBQ==
X-Received: by 10.194.123.164 with SMTP id mb4mr2716426wjb.84.1377780701483; Thu, 29 Aug 2013 05:51:41 -0700 (PDT)
Received: from RoniE (bzq-109-67-221-133.red.bezeqint.net. [109.67.221.133]) by mx.google.com with ESMTPSA id v9sm12246255wiw.8.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 05:51:40 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Loa Andersson'" <loa@pi.nu>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com> <04cf01cea499$22eb4a80$68c1df80$@gmail.com> <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com> <521F3489.1060600@pi.nu>
In-Reply-To: <521F3489.1060600@pi.nu>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Thu, 29 Aug 2013 15:49:03 +0300
Message-ID: <04f301cea4b6$2a282440$7e786cc0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSAxjw2zQBgMlGEQLYu/AFAg83QJWaTJj8EA==
Content-Language: en-us
Cc: draft-ietf-mpls-return-path-specified-lsp-ping.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, 29 Aug 2013 12:51:45 -0000

Hi,
This is OK . I have no concerns
Roni

> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.nu]
> Sent: 29 August, 2013 2:46 PM
> To: Roni Even
> Cc: 'Mach Chen'; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org; gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review of
draft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Roni,
> 
> tnx - the authors should add words in the IANA section requesting that
IANA
> add this the pointed in the registry; they normally do anyway, but writing
it
> down should not be a problem.
> 
> As for "Vendor Private" RFC 4379 says:
> 
>    "Values from "Vendor Private" ranges MUST NOT be registered with IANA;
>     however, the message MUST contain an enterprise code as registered
>     with the IANA SMI Private Network Management Private Enterprise
>     Numbers.  For each name space that has a Vendor Private range, it
>     must be specified where exactly the SMI Private Enterprise Number
>     resides; see below for examples.  In this way, several enterprises
>     (vendors) can use the same code point without fear of collision."
> 
> The way I read this is that the paragraph does two things (1) defines the
> allocation policy (in this case that "vendor private" won't be assigned by
> IANA) and (2) put a restriction on the "vendor private"
> (sub-)TLVs; they must contain a "private enterprise number".
> 
> Up to now I've thought the restriction on the format was global for all
> "vendor private" sub-TLVs that are used by TLV for LSP Ping.
> However we put words to the same effect in e.g. 6424, wo there is no
reason
> not to do it here also. A pointer to RFC4379 should be enough
> e.g.:
> 
> "For the vendor private sub-TLVs defined for this document, the same
> allocation policies and requirement on the sub-TLV format that is
specified
> for vendor private sub-TLVs in RFC4379 [RFC4379] appliacable."
> 
> Would that cover you concern?
> 
> /Loa
> 
> 
> 
> On 2013-08-29 12:24, Roni Even wrote:
> > Hi,
> > This text is OK if one wants to implement this draft.
> > My concern was about the consistency of the IANA registration so that
> > if someone defines a new TLV type 1 based on RFC4379, IANA will know
> > that it must update also the registry for TLV type 21. If you see no
> > such problem, I have no concerns Roni
> >
> >> -----Original Message-----
> >> From: Mach Chen [mailto:mach.chen@huawei.com]
> >> Sent: 29 August, 2013 1:05 PM
> >> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> >> ping.all@tools.ietf.org
> >> Cc: ietf@ietf.org; gen-art@ietf.org
> >> Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-
> >> ping-12
> >>
> >> Hi Roni,
> >>
> >> How about this:
> >>
> >> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >>      are made directly for TLV Type 21, sub-TLVs in these ranges are
> >>      copied from the assignments made for TLV Type 1 and kept the same
> >>      as that for TLV Type 1. All sub-TLVs in these ranges (include
existing
> >>      and future defined) defined for TLV Type 1 apply to TLV Type 21.
> >>      Assignments of sub-..."
> >>
> >> Best regards,
> >> Mach
> >>
> >>> -----Original Message-----
> >>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >>> Sent: Thursday, August 29, 2013 5:21 PM
> >>> To: Mach Chen;
> >>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> >>> Cc: ietf@ietf.org; gen-art@ietf.org
> >>> Subject: RE: Gen-ART LC review of
> >>> draft-ietf-mpls-return-path-specified-lsp-ping-12
> >>>
> >>> Hi,
> >>> I am not sure you responded to my latest email.
> >>>
> >>> Having the policy for TLV type 1 here is not enough in my view since
> >>> I only look at RFC4379 and create a new TLV type I will not know
> >>> that I have to register it also for the type 21 if it will not be
> >>> mentioned
> >>>
> >>> As for the vendor specific see my other email Roni
> >>>
> >>>> -----Original Message-----
> >>>> From: Mach Chen [mailto:mach.chen@huawei.com]
> >>>> Sent: 29 August, 2013 11:33 AM
> >>>> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> >>>> ping.all@tools.ietf.org
> >>>> Cc: ietf@ietf.org; gen-art@ietf.org
> >>>> Subject: RE: Gen-ART LC review of
> >>> draft-ietf-mpls-return-path-specified-lsp-
> >>>> ping-12
> >>>>
> >>>> Hi Roni,
> >>>>
> >>>> Thanks for your detailed review and comments!
> >>>>
> >>>> Please see my reply inline...
> >>>>
> >>>>> From: Roni Even [mailto:ron.even.tlv@gmail.com]
> >>>>> Sent: Wednesday, August 28, 2013 9:06 PM
> >>>>> To:
> >>>>> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> >>>>> Cc: ietf@ietf.org; gen-art@ietf.org
> >>>>> Subject: Gen-ART LC review of
> >>>>> draft-ietf-mpls-return-path-specified-lsp-ping-12
> >>>>>
> >>>>> I am the assigned Gen-ART reviewer for this draft. For background
> >>>>> on Gen-ART, please see the FAQ at
> >>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >>>>> Please resolve these comments along with any other Last Call
> >>>>> comments you may receive.
> >>>>> Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> >>>>> Reviewer: Roni Even
> >>>>> Review Date:2013-8-28
> >>>>> IETF LC End Date: 2013-9-4
> >>>>> IESG Telechat date:
> >>>>>
> >>>>> Summary: This draft is almost ready for publication as a standard
> >>>>> track
> >>> RFC.
> >>>>>
> >>>>>
> >>>>> Major issues:
> >>>>> Minor issues:
> >>>>> I am not clear on the sub-TLV in section 6.2 1. If a new sub-TLV
> >>>>> is defined for TLV type 1 do they need also to be added to TLV
> >>>>> type
> > 21.
> >>>>> This should be clear, and if there is some relation I think it
> >>>>> should be reflected in the IANA registry for TLV type 1
> >>>>
> >>>> Yes, type 21 TLV intends to reuse existing and future defined
> >>>> sub-TLVs for type TLV 1. And in Section 3.3, it has already stated
> > this, it
> >> says:
> >>>>
> >>>> "The Target FEC sub-TLVs defined in [RFC4379] provide a good way to
> >>>>     identify a specific return path.  The Reply Path TLV can carry
any
> >>>>     sub-TLV defined for use in the Target FEC Stack TLV that can be
> >>>>     registered."
> >>>>
> >>>> So, for Section 6.2, to make it cleaner and more explicit, how
> >>>> about this
> >>>> change:
> >>>>
> >>>> Old:
> >>>>
> >>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
> >>>>     copied from the assignments made for TLV Type 1. Assignments of
> >>> sub-..."
> >>>>
> >>>> New:
> >>>>
> >>>> " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >>>>     are made directly for TLV Type 21, sub-TLVs in these ranges are
> >>>>     copied from the assignments (including existing and future
> > allocations)
> >>>>     made for TLV Type 1. Assignments of sub-..."
> >>>>
> >>>>
> >>>>> 2. For the vendor or private use why a difference policy than the
> >>>>> rest of the sub-TLV registry
> >>>>
> >>>> This document does not make any changes to the "Vendor and Private
> >> use"
> >>>> definition, range and policy as defined in RFC4379. In RFC4379,
> >>>> it's
> >>> policy is
> >>>> defined different from other ranges.
> >>>>
> >>>>>
> >>>>> Nits/editorial comments:
> >>>>> 1. In section 3.4 I assume that "TC" is traffic class. It will be
> >>>>> good to expand and have reference.
> >>>>
> >>>> OK, will fix it when all last call comments received.
> >>>>
> >>>> Best regards,
> >>>> Mach
> >
> 
> --
> 
> 
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64


From daedulus@btconnect.com  Thu Aug 29 07:42:36 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B11621E805A for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 07:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level: 
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ei5cu9fjupwz for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 07:42:30 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4DD11E8117 for <ietf@ietf.org>; Thu, 29 Aug 2013 07:42:25 -0700 (PDT)
Received: from mail11-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE002.bigfish.com (10.43.70.52) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 14:42:24 +0000
Received: from mail11-ch1 (localhost [127.0.0.1])	by mail11-ch1-R.bigfish.com (Postfix) with ESMTP id 47751340370; Thu, 29 Aug 2013 14:42:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -15
X-BigFish: PS-15(zz9371I542I1432I1418Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail11-ch1 (localhost.localdomain [127.0.0.1]) by mail11-ch1 (MessageSwitch) id 1377787342421187_26607; Thu, 29 Aug 2013 14:42:22 +0000 (UTC)
Received: from CH1EHSMHS029.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.236])	by mail11-ch1.bigfish.com (Postfix) with ESMTP id 6392F1C0075;	Thu, 29 Aug 2013 14:42:22 +0000 (UTC)
Received: from DBXPRD0711HT004.eurprd07.prod.outlook.com (157.56.254.181) by CH1EHSMHS029.bigfish.com (10.43.70.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 14:42:18 +0000
Received: from DBXPRD0611HT003.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.178.37) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 14:41:53 +0000
Message-ID: <005a01cea4c5$c9d030a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20130827215216.30701.52572.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation ofStandards Track Code Points) to Best Current Practice
Date: Thu, 29 Aug 2013 15:39:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 14:42:36 -0000

This I-D uses the term 'deprecated' without defining it nor is the term
defined in "IANA Considerations" [RFC5226] " (It does however already
appear in the IANA Registry).

I am familiar with the SMI definition but that seems not quite right for
this context; some of the IANA uses of this have been there for decades
and are unlikely ever to be removed.  I think that this I-D needs a
definition and, since I have seen disagreement on WG Lists as to what
the term means, I think that that definition should be agree on the ietf
list before this I-D is approved by the IESG.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Sent: Tuesday, August 27, 2013 10:52 PM
>
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Early IANA Allocation of Standards Track Code Points'
>   <draft-cotton-rfc4020bis-01.txt> as Best Current Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-09-24. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>    This memo describes the process for early allocation of code points
>    by IANA from registries for which "Specification Required", "RFC
>    Required", "IETF Review", or "Standards Action" policies apply.
This
>    process can be used to alleviate the problem where code point
>    allocation is needed to facilitate desired or required
implementation
>    and deployment experience prior to publication of an RFC that would
>    normally trigger code point allocation.
>
>    This document obsoletes RFC 4020.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-cotton-rfc4020bis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>



From michelle.cotton@icann.org  Thu Aug 29 07:53:22 2013
Return-Path: <michelle.cotton@icann.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C21E721E8098 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 07:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HyoGBm8qMcFQ for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 07:53:18 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id 58E4121E80A1 for <ietf@ietf.org>; Thu, 29 Aug 2013 07:53:18 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Thu, 29 Aug 2013 07:53:16 -0700
From: Michelle Cotton <michelle.cotton@icann.org>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, t.p. <daedulus@btconnect.com>, ietf <ietf@ietf.org>
Date: Thu, 29 Aug 2013 07:53:13 -0700
Subject: Re: "Deprecate"
Thread-Topic: "Deprecate"
Thread-Index: Ac6kx34KcSr1yrUjQgWn+GIbRynCAA==
Message-ID: <CE44ADE0.E6DD3%michelle.cotton@icann.org>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0A61@GLKXM0002V.GREENLNK.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3460607593_2839245"
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, 29 Aug 2013 14:53:24 -0000

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

We are working on 5226bis right now and have a plans to discuss the term
in there.

--Michelle Cotton

Michelle Cotton
Manager, IANA Services
ICANN



On 8/29/13 5:22 AM, "Dearlove, Christopher (UK)"
<chris.dearlove@baesystems.com> wrote:

>It's definitely an ISO term, I see it used for features of C++.
>
>There's then discussion even there of what it means. It is, I think,
>meant to be used for "we don't think you should use this, there's
>something better, and this is a warning that it may get removed in a
>future version". In the case of computer languages there is an additional
>possibility of "your compiler may emit a warning if you persist in using
>it".
>
>But the only major feature (export) removed in the last C++ version went
>straight from "part of the standard, but only one compiler ever
>implemented it, and thus found out it was a bad realisation of an idea"
>to removed, with no intermediate deprecated stage. And other features
>just hang around deprecated. So it really doesn't guarantee anything in
>that instance, neither than if deprecated will go, not if not deprecated
>won't go.
>
>-- 
>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
>t.p.
>Sent: 29 August 2013 12:56
>To: ietf
>Subject: "Deprecate"
>
>----------------------! 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.
>--------------------------------------------------------
>
>I recently saw 'deprecate' used in an IANA Considerations and turned to
>"IANA Considerations" [RFC5226] to see how it was defined only to find
>no mention of it there.  I am used to the term from SMI, as quoted
>below, but that seems not quite right, in that a deprecated IANA entry
>never disappears, as in
>http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
>s-5
>
>Are there other, perhaps better definitions of the term 'deprecated' in
>use outside SMI (and yes, I know about praying nuns!)?
>
>Tom Petch
>
>----- Original Message -----
>From: "Fred Baker (fred)" <fred@cisco.com>
>To: "IPv6 Maintanence" <ipv6@ietf.org>
>Sent: Monday, July 29, 2013 3:32 PM
>Subject: "Deprecate"
>
>
>> At the mike a moment ago, I referred to an existing formal definition
>of "deprecate". For the record, the reference is to RFC 1158, which
>reads:
>>
>> 3.1.  Deprecated Objects
>>
>>    In order to better prepare implementors for future changes in the
>>    MIB, a new term "deprecated" may be used when describing an object.
>>    A deprecated object in the MIB is one which must be supported, but
>>    one which will most likely be removed from the next version of the
>>    MIB (e.g., MIB-III).
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>
>
>********************************************************************
>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.
>********************************************************************
>

--B_3460607593_2839245
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIITugYJKoZIhvcNAQcCoIITqzCCE6cCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EYYwggb2MIIF3qADAgECAhAFLoNW3qD4JhFZyohPBtNqMA0GCSqGSIb3DQEBBQUAMGIxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xITAfBgNVBAMTGERpZ2lDZXJ0IEFzc3VyZWQgSUQgQ0EtMTAeFw0xMzAzMjAwMDAw
MDBaFw0xNjAzMjAxMjAwMDBaMIGfMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p
YTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0aW9u
IGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczENMAsGA1UECxMESUFOQTEYMBYGA1UE
AxMPTWljaGVsbGUgQ290dG9uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxWwq
bCL/Xkl+g9mKzyjxA8YKyTJgMKkfuNPm2Pi5iWmUGpAHkSCUX/YKf1rninFM8JkzffVgInmx
juZQRW7lP2796RU0UAUdEsbfDcE5l4dj8h7omA2HkiwvKgxBwegr8VHjzUxOzSetAio5Y2qA
Fs7EY97BX6aulzP+tyKi5+7GSBRq+SguiLYETk4FZo8nmyK8E0210+ozwlUQ0VSfkpWluyc/
wQtRo/vQYoM0DPgVaxkE9r20ReyqaE+mxN2pqKl8qoiNMUAnbJIVUSfZhIxS4yoVKNLsOJzo
CYSrD6JgNOmzbEOfrTMWMAhh1RCqp5bcaZ4Zlq2lbrIGHzPgSwIDAQABo4IDaDCCA2QwHwYD
VR0jBBgwFoAUFQASKxOYspkH7R7for5XDStnAs0wHQYDVR0OBBYEFFcRyKFrxJAiHzozbxx0
fzjeiYmeMCQGA1UdEQQdMBuBGW1pY2hlbGxlLmNvdHRvbkBpY2Fubi5vcmcwDgYDVR0PAQH/
BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjB9BgNVHR8EdjB0MDigNqA0
hjJodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDA4
oDagNIYyaHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEQ0EtMS5j
cmwwggHFBgNVHSAEggG8MIIBuDCCAbQGCmCGSAGG/WwEAQIwggGkMDoGCCsGAQUFBwIBFi5o
dHRwOi8vd3d3LmRpZ2ljZXJ0LmNvbS9zc2wtY3BzLXJlcG9zaXRvcnkuaHRtMIIBZAYIKwYB
BQUHAgIwggFWHoIBUgBBAG4AeQAgAHUAcwBlACAAbwBmACAAdABoAGkAcwAgAEMAZQByAHQA
aQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMAdABpAHQAdQB0AGUAcwAgAGEAYwBjAGUAcAB0AGEA
bgBjAGUAIABvAGYAIAB0AGgAZQAgAEQAaQBnAGkAQwBlAHIAdAAgAEMAUAAvAEMAUABTACAA
YQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkAaQBuAGcAIABQAGEAcgB0AHkAIABBAGcAcgBlAGUA
bQBlAG4AdAAgAHcAaABpAGMAaAAgAGwAaQBtAGkAdAAgAGwAaQBhAGIAaQBsAGkAdAB5ACAA
YQBuAGQAIABhAHIAZQAgAGkAbgBjAG8AcgBwAG8AcgBhAHQAZQBkACAAaABlAHIAZQBpAG4A
IABiAHkAIAByAGUAZgBlAHIAZQBuAGMAZQAuMHcGCCsGAQUFBwEBBGswaTAkBggrBgEFBQcw
AYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEEGCCsGAQUFBzAChjVodHRwOi8vY2FjZXJ0
cy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNydDAMBgNVHRMBAf8EAjAA
MA0GCSqGSIb3DQEBBQUAA4IBAQAzABp5GDSqoV3ty0YLFXRO8ZlHtgsLOP+5AmAS9P0mDEny
uO6xbrWK/Oi+9/UfcnYKYUGkFvukHBFLowWakQngPhHLjEhNl2QYC4dbQWLd9z4gZWBWYVzs
EreLwUSbRbE3G1r/lkUK3EYO5xAAWtFcv0I4Ixd3//0zxg0ohWW7fm22ypXr8HIBffpptim+
6oO6X55ME5789phHZZDQt6haEHyMnAQNW2SL6e8cgSL30lPcpStRCXriyXBdoSI+oW83+9u3
SvhjG9WXw8sso9oWMBWo8BhSTERNzLYbxQMazYHW5L/BUBUICTR6l3W96+rjpPZDZVpd9wgR
AG54dZ+mMIIGzTCCBbWgAwIBAgIQBv35A5YDreoACus/J7u6GzANBgkqhkiG9w0BAQUFADBl
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln
aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwHhcNMDYx
MTEwMDAwMDAwWhcNMjExMTEwMDAwMDAwWjBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDogi2Z
+crCQpWlgHNAcNKeVlRcqcTSQQaPyTP8TUWRXIGf7Syc+BZZ3561JBXCmLm0d0ncicQK2q/L
XmvtrbBxMevPOkAMRk2T7It6NggDqww0/hhJgv7HxzFIgHweog+SDlDJxofrNj/YMMP/pvf7
os1vcyP+rFYFkPAyIRaJxnCI+QWXfaPHQ90C6Ds97bFBo+0/vtuVSMTuHrPyvAwrmdDGXRJC
geGDboJzPyZLFJCuWWYKxI2+0s4Grq2Eb0iEm09AufFM8q+Y+/bOQF1c9qjxL6/siSLyaxhl
scFzrdfx2M8eCnRcQrhofrfVdwonVnwPYqQ/MhRglf0HBKIJAgMBAAGjggN6MIIDdjAOBgNV
HQ8BAf8EBAMCAYYwOwYDVR0lBDQwMgYIKwYBBQUHAwEGCCsGAQUFBwMCBggrBgEFBQcDAwYI
KwYBBQUHAwQGCCsGAQUFBwMIMIIB0gYDVR0gBIIByTCCAcUwggG0BgpghkgBhv1sAAEEMIIB
pDA6BggrBgEFBQcCARYuaHR0cDovL3d3dy5kaWdpY2VydC5jb20vc3NsLWNwcy1yZXBvc2l0
b3J5Lmh0bTCCAWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQA
aABpAHMAIABDAGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMA
IABhAGMAYwBlAHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQA
IABDAFAALwBDAFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIA
dAB5ACAAQQBnAHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkA
YQBiAGkAbABpAHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUA
ZAAgAGgAZQByAGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjALBglghkgBhv1s
AxUwEgYDVR0TAQH/BAgwBgEB/wIBADB5BggrBgEFBQcBAQRtMGswJAYIKwYBBQUHMAGGGGh0
dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2NhY2VydHMuZGln
aWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNydDCBgQYDVR0fBHoweDA6oDig
NoY0aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNy
bDA6oDigNoY0aHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9v
dENBLmNybDAdBgNVHQ4EFgQUFQASKxOYspkH7R7for5XDStnAs0wHwYDVR0jBBgwFoAUReui
r/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQEFBQADggEBAEZQPsm3KCSnOB22WymvUs9S
6TFHq1Zce9UNC0Gz7+x1H3Q48rJcYaKclcNQ5IK5I9G6OoZyrTh4rHVdFxc0ckeFlFbR67s2
hHfMJKXzBBlVqefj56tizfuLLZDCwNK1lL1eT7EF0g49GqkUW6aGMWKoqDPkmzmnxPXOHXh2
lCVz5Cqrz5x2S+1fwksW5EtwTACJHvzFebxMElf+X+EevAJdqP77BzhPDcZdkbkPZ0XN1oPt
55INjbFpjE/7WeAjD9KqrgB87pxCDs+R1ye3Fu4Pw718CqDuLAhVhSK46xgaTfwqIa1JMYNH
lXdx3LEbS0scEJx3FMGdTy9alQgpECYwggO3MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5
MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBaFw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfzt2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWV
MmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ
/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OMM9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X
8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJfDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk
2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwOsLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Y
d08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGGMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYE
FEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1UdIwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgP
MA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/M
zhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbGeasS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLi
l4Qf6WXvh+DfwWdJs13rsgkq6ybteL59PyvztyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6
ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR
34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdhAbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6
CkUvovDyMYIB/DCCAfgCAQEwdjBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQg
SW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2VydCBBc3N1
cmVkIElEIENBLTECEAUug1beoPgmEVnKiE8G02owCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJ
BDEWBBQBJ+NVhbgYK4VIWi7eKqfrma2h9DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xMzA4MjkxNDUzMTNaMA0GCSqGSIb3DQEBAQUABIIBAFNUc6cXLp/m
ERs2ZzWBj1R7XUEXQdjkls5fx57/e/HN6H2z7lQwv7u0PZwRc/eNXAdrSVUAUUCEc5i0a0fO
lIQXspZXaSz08wGFVSEWLWdX7xp7UGUv5IhxToAg8UoGdwUKx8ZLsvPiN9HVtg2QU/c46+us
dGS+YfePoWyrFjA+Ya+9nEnjGhlwZ+W2WYQMlbPOGQaSYIUpp59LDiiQzb7VjzU8oFKs6RMD
yAneJYZsGhUhrBd4K/kQ4q5L6Q8HPLS+PS/qaFFGvcF2MgSpVBCxOkI2QoIuHRynhbvQrtKY
+RnYiBmrZwafoEsBgt7sqzfFAqKvSarydoFwJRacMxI=

--B_3460607593_2839245--

From adrian@olddog.co.uk  Thu Aug 29 08:16:11 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927E311E8123 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 08:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jeZ+hp3CeAXk for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 08:16:07 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5195711E811B for <ietf@ietf.org>; Thu, 29 Aug 2013 08:16:02 -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 r7TFDnvq005704;  Thu, 29 Aug 2013 16:13:49 +0100
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [10.12.10.176]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TFDn3j005695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Aug 2013 16:13:49 +0100
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TFDmIk023736;  Thu, 29 Aug 2013 16:13:48 +0100
Received: from 950129200 (westford-nat.juniper.net [66.129.232.2]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r7TFDkBj023703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 29 Aug 2013 16:13:47 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Michelle Cotton'" <michelle.cotton@icann.org>, "'Dearlove, Christopher \(UK\)'" <chris.dearlove@baesystems.com>, "'t.p.'" <daedulus@btconnect.com>, "'ietf'" <ietf@ietf.org>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0A61@GLKXM0002V.GREENLNK.net> <CE44ADE0.E6DD3%michelle.cotton@icann.org>
In-Reply-To: <CE44ADE0.E6DD3%michelle.cotton@icann.org>
Subject: RE: "Deprecate"
Date: Thu, 29 Aug 2013 16:13:46 +0100
Message-ID: <077801cea4ca$5ca1cde0$15e569a0$@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: AQFjVHWDZsFWMy4k7oWKjNkNomQ0AJqC66Zw
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 15:16:11 -0000

That would be great.

Should 4020bis have a gating normative reference on 5226bis?

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Michelle Cotton
> Sent: 29 August 2013 15:53
> To: Dearlove, Christopher (UK); t.p.; ietf
> Subject: Re: "Deprecate"
> 
> We are working on 5226bis right now and have a plans to discuss the term
> in there.
> 
> --Michelle Cotton
> 
> Michelle Cotton
> Manager, IANA Services
> ICANN
> 
> 
> 
> On 8/29/13 5:22 AM, "Dearlove, Christopher (UK)"
> <chris.dearlove@baesystems.com> wrote:
> 
> >It's definitely an ISO term, I see it used for features of C++.
> >
> >There's then discussion even there of what it means. It is, I think,
> >meant to be used for "we don't think you should use this, there's
> >something better, and this is a warning that it may get removed in a
> >future version". In the case of computer languages there is an additional
> >possibility of "your compiler may emit a warning if you persist in using
> >it".
> >
> >But the only major feature (export) removed in the last C++ version went
> >straight from "part of the standard, but only one compiler ever
> >implemented it, and thus found out it was a bad realisation of an idea"
> >to removed, with no intermediate deprecated stage. And other features
> >just hang around deprecated. So it really doesn't guarantee anything in
> >that instance, neither than if deprecated will go, not if not deprecated
> >won't go.
> >
> >--
> >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
> >t.p.
> >Sent: 29 August 2013 12:56
> >To: ietf
> >Subject: "Deprecate"
> >
> >----------------------! 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.
> >--------------------------------------------------------
> >
> >I recently saw 'deprecate' used in an IANA Considerations and turned to
> >"IANA Considerations" [RFC5226] to see how it was defined only to find
> >no mention of it there.  I am used to the term from SMI, as quoted
> >below, but that seems not quite right, in that a deprecated IANA entry
> >never disappears, as in
> >http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-
> number
> >s-5
> >
> >Are there other, perhaps better definitions of the term 'deprecated' in
> >use outside SMI (and yes, I know about praying nuns!)?
> >
> >Tom Petch
> >
> >----- Original Message -----
> >From: "Fred Baker (fred)" <fred@cisco.com>
> >To: "IPv6 Maintanence" <ipv6@ietf.org>
> >Sent: Monday, July 29, 2013 3:32 PM
> >Subject: "Deprecate"
> >
> >
> >> At the mike a moment ago, I referred to an existing formal definition
> >of "deprecate". For the record, the reference is to RFC 1158, which
> >reads:
> >>
> >> 3.1.  Deprecated Objects
> >>
> >>    In order to better prepare implementors for future changes in the
> >>    MIB, a new term "deprecated" may be used when describing an object.
> >>    A deprecated object in the MIB is one which must be supported, but
> >>    one which will most likely be removed from the next version of the
> >>    MIB (e.g., MIB-III).
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >>
> >
> >
> >
> >*************************************************************
> *******
> >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 daedulus@btconnect.com  Thu Aug 29 08:34:38 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBCAF21E805A; Thu, 29 Aug 2013 08:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level: 
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[AWL=-0.474, 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 rll+h33EFdzL; Thu, 29 Aug 2013 08:34:22 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0250.outbound.messaging.microsoft.com [213.199.154.250]) by ietfa.amsl.com (Postfix) with ESMTP id 2637D21F9CD1; Thu, 29 Aug 2013 08:34:20 -0700 (PDT)
Received: from mail162-db9-R.bigfish.com (10.174.16.250) by DB9EHSOBE029.bigfish.com (10.174.14.92) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 15:34:19 +0000
Received: from mail162-db9 (localhost [127.0.0.1])	by mail162-db9-R.bigfish.com (Postfix) with ESMTP id 3069B4200C4; Thu, 29 Aug 2013 15:34:19 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zz9371I936eI542I1432I168aJzz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail162-db9 (localhost.localdomain [127.0.0.1]) by mail162-db9 (MessageSwitch) id 1377790456452990_6643; Thu, 29 Aug 2013 15:34:16 +0000 (UTC)
Received: from DB9EHSMHS022.bigfish.com (unknown [10.174.16.239])	by mail162-db9.bigfish.com (Postfix) with ESMTP id 4326A1C017A; Thu, 29 Aug 2013 15:34:16 +0000 (UTC)
Received: from DBXPRD0711HT001.eurprd07.prod.outlook.com (157.56.254.181) by DB9EHSMHS022.bigfish.com (10.174.14.32) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 15:34:13 +0000
Received: from DBXPRD0611HT004.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.178.34) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 15:34:11 +0000
Message-ID: <012001cea4cd$1845c680$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Roni Even <ron.even.tlv@gmail.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com><04cf01cea499$22eb4a80$68c1df80$@gmail.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com>
Subject: Re: Gen-ART LC review ofdraft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Thu, 29 Aug 2013 16:33:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 15:34:38 -0000

Roni

I find it difficult to know whether to agree with you or not since there
is another "gorilla" operating in this namespace, namely
draft-andersson-mpls-lsp-ping-upd-00
which sort of gives the option of taking out the sub-TLV types of a TLV
Type into a separate registry which can then be referenced by the
specifications of several TLV Types.  This I-D formally calls for no
action by IANA, except that it implies a reorganisation of the
registries which IANA might well already have executed - certainly, the
registries no longer look the same as they did a few months ago although
that might also be a coincidence.

You make reference to the registry set up by RFC6426 but you should be
aware that what is now in the IANA registries is not what was there when
that RFC was approved; rather, it has changed as alluded to above..

If
draft-andersson-mpls-lsp-ping-upd-00
is approved, and my perception is that IANA assumes it has been, then
this, return-path I-D would appear to be barking up the wrong tree and
needs revising to reflect the new IANA structure, namely that it needs
to update
the title which already exists
Sub-TLVs for TLV Types 1 and 16
to become
Sub-TLVs for TLV Types 1 and 16 and 21
whereupon things start to fall into place

draft-andersson-mpls-lsp-ping-upd-00
also updates RFC4379 which, if accepted, means, I think, that this I-D
need not.

All very technically sound but we seem to have our processes upside
down.

There is of course a lengthy history to this that is not material to the
current discussion.

Tom Petch

----- Original Message -----
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Mach Chen'" <mach.chen@huawei.com>;
<draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
Cc: <gen-art@ietf.org>; <ietf@ietf.org>
Sent: Thursday, August 29, 2013 11:24 AM
Subject: RE: Gen-ART LC review
ofdraft-ietf-mpls-return-path-specified-lsp-ping-12


> Hi,
> This text is OK if one wants to implement this draft.
> My concern was about the consistency of the IANA registration so that
if
> someone defines a new TLV type 1 based on RFC4379, IANA will know that
it
> must update also the registry for TLV type 21. If you see no such
problem, I
> have no concerns
> Roni
>
> > -----Original Message-----
> > From: Mach Chen [mailto:mach.chen@huawei.com]
> > Sent: 29 August, 2013 1:05 PM
> > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > ping.all@tools.ietf.org
> > Cc: ietf@ietf.org; gen-art@ietf.org
> > Subject: RE: Gen-ART LC review of
> draft-ietf-mpls-return-path-specified-lsp-
> > ping-12
> >
> > Hi Roni,
> >
> > How about this:
> >
> > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> >     are made directly for TLV Type 21, sub-TLVs in these ranges are
> >     copied from the assignments made for TLV Type 1 and kept the
same
> >     as that for TLV Type 1. All sub-TLVs in these ranges (include
existing
> >     and future defined) defined for TLV Type 1 apply to TLV Type 21.
> >     Assignments of sub-..."
> >
> > Best regards,
> > Mach
> >
> > > -----Original Message-----
> > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > Sent: Thursday, August 29, 2013 5:21 PM
> > > To: Mach Chen;
> > > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: RE: Gen-ART LC review of
> > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > >
> > > Hi,
> > > I am not sure you responded to my latest email.
> > >
> > > Having the policy for TLV type 1 here is not enough in my view
since I
> > > only look at RFC4379 and create a new TLV type I will not know
that I
> > > have to register it also for the type 21 if it will not be
mentioned
> > >
> > > As for the vendor specific see my other email Roni
> > >
> > > > -----Original Message-----
> > > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > > Sent: 29 August, 2013 11:33 AM
> > > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > > ping.all@tools.ietf.org
> > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > Subject: RE: Gen-ART LC review of
> > > draft-ietf-mpls-return-path-specified-lsp-
> > > > ping-12
> > > >
> > > > Hi Roni,
> > > >
> > > > Thanks for your detailed review and comments!
> > > >
> > > > Please see my reply inline...
> > > >
> > > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > > > To:
> > > > >
draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > > Subject: Gen-ART LC review of
> > > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > >
> > > > > I am the assigned Gen-ART reviewer for this draft. For
background
> > > > > on Gen-ART, please see the FAQ at
> > > > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > > > Please resolve these comments along with any other Last Call
> > > > > comments you may receive.
> > > > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > > Reviewer: Roni Even
> > > > > Review Date:2013-8-28
> > > > > IETF LC End Date: 2013-9-4
> > > > > IESG Telechat date:
> > > > >
> > > > > Summary: This draft is almost ready for publication as a
standard
> > > > > track
> > > RFC.
> > > > >
> > > > >
> > > > > Major issues:
> > > > > Minor issues:
> > > > > I am not clear on the sub-TLV in section 6.2 1. If a new
sub-TLV
> > > > > is defined for TLV type 1 do they need also to be added to TLV
type
> 21.
> > > > > This should be clear, and if there is some relation I think it
> > > > > should be reflected in the IANA registry for TLV type 1
> > > >
> > > > Yes, type 21 TLV intends to reuse existing and future defined
> > > > sub-TLVs for type TLV 1. And in Section 3.3, it has already
stated
> this, it
> > says:
> > > >
> > > > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way
to
> > > >    identify a specific return path.  The Reply Path TLV can
carry any
> > > >    sub-TLV defined for use in the Target FEC Stack TLV that can
be
> > > >    registered."
> > > >
> > > > So, for Section 6.2, to make it cleaner and more explicit, how
about
> > > > this
> > > > change:
> > > >
> > > > Old:
> > > >
> > > > " No assignments of sub-TLVs in the range of 0-16383 and
32768-49161
> > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
are
> > > >    copied from the assignments made for TLV Type 1. Assignments
of
> > > sub-..."
> > > >
> > > > New:
> > > >
> > > > " No assignments of sub-TLVs in the range of 0-16383 and
32768-49161
> > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
are
> > > >    copied from the assignments (including existing and future
> allocations)
> > > >    made for TLV Type 1. Assignments of sub-..."
> > > >
> > > >
> > > > > 2. For the vendor or private use why a difference policy than
the
> > > > > rest of the sub-TLV registry
> > > >
> > > > This document does not make any changes to the "Vendor and
Private
> > use"
> > > > definition, range and policy as defined in RFC4379. In RFC4379,
it's
> > > policy is
> > > > defined different from other ranges.
> > > >
> > > > >
> > > > > Nits/editorial comments:
> > > > > 1. In section 3.4 I assume that "TC" is traffic class. It will
be
> > > > > good to expand and have reference.
> > > >
> > > > OK, will fix it when all last call comments received.
> > > >
> > > > Best regards,
> > > > Mach
>
>



From daedulus@btconnect.com  Thu Aug 29 08:36:55 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F34221E809F for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 08:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.455
X-Spam-Level: 
X-Spam-Status: No, score=-3.455 tagged_above=-999 required=5 tests=[AWL=0.145,  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 cHxI3pfSKUKF for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 08:36:46 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id D933011E8118 for <ietf@ietf.org>; Thu, 29 Aug 2013 08:36:36 -0700 (PDT)
Received: from mail138-ch1-R.bigfish.com (10.43.68.239) by CH1EHSOBE020.bigfish.com (10.43.70.77) with Microsoft SMTP Server id 14.1.225.22; Thu, 29 Aug 2013 15:36:28 +0000
Received: from mail138-ch1 (localhost [127.0.0.1])	by mail138-ch1-R.bigfish.com (Postfix) with ESMTP id 27ADD380230; Thu, 29 Aug 2013 15:36:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL17326ah186068h1954cbh8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h304l1d11m1155h)
Received: from mail138-ch1 (localhost.localdomain [127.0.0.1]) by mail138-ch1 (MessageSwitch) id 1377790586694944_2642; Thu, 29 Aug 2013 15:36:26 +0000 (UTC)
Received: from CH1EHSMHS043.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.229])	by mail138-ch1.bigfish.com (Postfix) with ESMTP id 9BFD5220041;	Thu, 29 Aug 2013 15:36:26 +0000 (UTC)
Received: from AMSPRD0711HT004.eurprd07.prod.outlook.com (157.56.250.181) by CH1EHSMHS043.bigfish.com (10.43.69.252) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 29 Aug 2013 15:36:25 +0000
Received: from DBXPRD0611HT001.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.242.14.165) with Microsoft SMTP Server (TLS) id 14.16.353.4; Thu, 29 Aug 2013 15:36:23 +0000
Message-ID: <012e01cea4cd$66fb01a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <adrian@olddog.co.uk>, 'Michelle Cotton' <michelle.cotton@icann.org>, 'ietf' <ietf@ietf.org>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0A61@GLKXM0002V.GREENLNK.net> <CE44ADE0.E6DD3%michelle.cotton@icann.org> <077801cea4ca$5ca1cde0$15e569a0$@olddog.co.uk>
Subject: Re: "Deprecate"
Date: Thu, 29 Aug 2013 16:35:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 15:36:56 -0000

---- Original Message -----
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Michelle Cotton'" <michelle.cotton@icann.org>; "'Dearlove,
Christopher (UK)'" <chris.dearlove@baesystems.com>; "'t.p.'"
<daedulus@btconnect.com>; "'ietf'" <ietf@ietf.org>
Sent: Thursday, August 29, 2013 4:13 PM
Subject: RE: "Deprecate"


> That would be great.
>
> Should 4020bis have a gating normative reference on 5226bis?

Tricky;  it would mean we are approving 4020bis without knowing what it
means, until 5226bis is approved.

Tom Petch


>
> Adrian
>
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
> > Michelle Cotton
> > Sent: 29 August 2013 15:53
> > To: Dearlove, Christopher (UK); t.p.; ietf
> > Subject: Re: "Deprecate"
> >
> > We are working on 5226bis right now and have a plans to discuss the
term
> > in there.
> >
> > --Michelle Cotton
> >
> > Michelle Cotton
> > Manager, IANA Services
> > ICANN
> >
> >
> >
> > On 8/29/13 5:22 AM, "Dearlove, Christopher (UK)"
> > <chris.dearlove@baesystems.com> wrote:
> >
> > >It's definitely an ISO term, I see it used for features of C++.
> > >
> > >There's then discussion even there of what it means. It is, I
think,
> > >meant to be used for "we don't think you should use this, there's
> > >something better, and this is a warning that it may get removed in
a
> > >future version". In the case of computer languages there is an
additional
> > >possibility of "your compiler may emit a warning if you persist in
using
> > >it".
> > >
> > >But the only major feature (export) removed in the last C++ version
went
> > >straight from "part of the standard, but only one compiler ever
> > >implemented it, and thus found out it was a bad realisation of an
idea"
> > >to removed, with no intermediate deprecated stage. And other
features
> > >just hang around deprecated. So it really doesn't guarantee
anything in
> > >that instance, neither than if deprecated will go, not if not
deprecated
> > >won't go.
> > >
> > >--
> > >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
> > >t.p.
> > >Sent: 29 August 2013 12:56
> > >To: ietf
> > >Subject: "Deprecate"
> > >
> > >----------------------! 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.
> > >--------------------------------------------------------
> > >
> > >I recently saw 'deprecate' used in an IANA Considerations and
turned to
> > >"IANA Considerations" [RFC5226] to see how it was defined only to
find
> > >no mention of it there.  I am used to the term from SMI, as quoted
> > >below, but that seems not quite right, in that a deprecated IANA
entry
> > >never disappears, as in
> > >http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-
> > number
> > >s-5
> > >
> > >Are there other, perhaps better definitions of the term
'deprecated' in
> > >use outside SMI (and yes, I know about praying nuns!)?
> > >
> > >Tom Petch
> > >
> > >----- Original Message -----
> > >From: "Fred Baker (fred)" <fred@cisco.com>
> > >To: "IPv6 Maintanence" <ipv6@ietf.org>
> > >Sent: Monday, July 29, 2013 3:32 PM
> > >Subject: "Deprecate"
> > >
> > >
> > >> At the mike a moment ago, I referred to an existing formal
definition
> > >of "deprecate". For the record, the reference is to RFC 1158, which
> > >reads:
> > >>
> > >> 3.1.  Deprecated Objects
> > >>
> > >>    In order to better prepare implementors for future changes in
the
> > >>    MIB, a new term "deprecated" may be used when describing an
object.
> > >>    A deprecated object in the MIB is one which must be supported,
but
> > >>    one which will most likely be removed from the next version of
the
> > >>    MIB (e.g., MIB-III).
> >
>> --------------------------------------------------------------------
> > >> IETF IPv6 working group mailing list
> > >> ipv6@ietf.org
> > >> Administrative Requests:
https://www.ietf.org/mailman/listinfo/ipv6
> >
>> --------------------------------------------------------------------
> > >>
> > >
> > >
> > >
> > >*************************************************************
> > *******
> > >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 sm@resistor.net  Thu Aug 29 09:09:57 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD47A21F888F for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BcN219IsVyCu for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:09:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 001F821F9CF3 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:09:10 -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 r7TG8Y2m021339; Thu, 29 Aug 2013 09:08:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377792523; bh=N7HeyDppunzh05rxYC5Vk13so3wj5RIUIa+fgG+IyzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XdVrQVtrD7JNZIbrASusEIFOqPrSBc7iemD696+mREhgD0p9L7Ls/LNFuKlKRFt1s SLjy6g0Gf9Dzgiixt/hkq9tOkkcChe6nNJrfC+ct2MoahVPuBDcAtVDoMaHma6C9iL Ed9fDxCl1/daSJMNuw1XOHhyHJhMNm37ccqjz3NE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377792523; i=@resistor.net; bh=N7HeyDppunzh05rxYC5Vk13so3wj5RIUIa+fgG+IyzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=n4k4FVQJeLv/AJPDEeFBes76BBNwq6qXStDGKDGR91WddEo/ubzzc32fULWSPY/gL bsxq3aGBUBEzm7npl4y+LOh2DoCq3keW4SCbA+eLpwa83s2VPGf9AATji7T0jvnqv/ xvIn0/0+xMLTn0IKZQgyOAO4Sx4Ef+W/ZbPe8N08=
Message-Id: <6.2.5.6.2.20130829084632.0cef9ac8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Aug 2013 08:50:14 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-media-type-10.txt> (A Media Type for Reputation Interchange) to Proposed Standard
In-Reply-To: <CAL0qLwYFXkB5E-5u5PykJu5BztLdhutzJoC41B2k85Lce87cGQ@mail.g mail.com>
References: <20130815144419.712.35650.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815102618.0b86a4e0@resistor.net> <CAL0qLwYFXkB5E-5u5PykJu5BztLdhutzJoC41B2k85Lce87cGQ@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: Thu, 29 Aug 2013 16:09:57 -0000

Hi Murray,
At 00:05 21-08-2013, Murray S. Kucherawy wrote:
>As alluded to above, there can be quite a bit of information needed 
>for an application to be defined beyond the defaults assumed when a 
>name is registered.  There didn't seem to be any need to require 
>such definition to be in an IETF document, but it also seems as 
>though more information than what's needed with just FCFS or DE or 
>the other lesser rules is appropriate either.

I'll suggest Expert Review here as it is a lesser barrier.  I'll 
defer to you on this.

Regards,
-sm 


From sm@resistor.net  Thu Aug 29 09:09:57 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD26421F933B for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85aqxg7A8qlK for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:09:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0018221F9C52 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:09:10 -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 r7TG8Y2o021339; Thu, 29 Aug 2013 09:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377792526; bh=v1a3BQCSoeqP7GKnPrxL9HJ0lBQFCVgrgSaE01P+s1k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NXvt1gpNPGcPJsYQipzcma0nn4FUOvYoY7tMpeFHBSPYR7Sg4WyahwwWEzjehTF89 AWwkNV1jJbfwLO1LUIUx9NJQLkNzY3tAgjQWQvdEa3uX4FXXj00F2aa06gsQvCRfJQ 2TTEkejwCvLhASmWQzAHDvbJH1CuspeojFu5XYYg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377792526; i=@resistor.net; bh=v1a3BQCSoeqP7GKnPrxL9HJ0lBQFCVgrgSaE01P+s1k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=veuJRWf/fm+zTSVrPzP+/2DmCSgHLWGEh8xMSUmK6ruSesCmPzMm2d6oI+kYSUs5V mcHmYFRm/10zaoUn6prkhrcvVNaOQuCBPK+l3xINwftswlmW5B0mKa8a6Ib3/Zi/Aa CLykAZw2OCayY5abmEd4JvbPpqSZFSG8EC3oBvWI=
Message-Id: <6.2.5.6.2.20130829085018.0cef9ea0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Aug 2013 08:57:09 -0700
To: "Murray S. Kucherawy" <superuser@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
In-Reply-To: <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@mail.g mail.com>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com> <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net> <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@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, 29 Aug 2013 16:09:57 -0000

Hi Murray,
At 01:14 21-08-2013, Murray S. Kucherawy wrote:
>Ah.  I realize that CRLF is standard line termination for SMTP; is 
>it automatically the expected line termination for all line-oriented 
>protocols?  I don't know about others.

I would have to write a long answer to that question. :-)  I haven't 
had time to test what the draft specifies.  Thanks for addressing the comments.

Regards,
-sm  


From sm@resistor.net  Thu Aug 29 09:10:33 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8337421F9EB5 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 uDe6hyQsPp5N for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:10:33 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9643721F9D18 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:10:25 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7TG8Y2k021339; Thu, 29 Aug 2013 09:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377792519; bh=anmAUVbD1iXvzUr6mjTSeBfRGyXXF2bIQtg/4u2Xs84=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4zmGvGNNU38/BX1hE0uTJvYB3A62dxNWQyCVoQk+92lYkLWKnCqwMtP6I1mtWqWb9 9zH6IQI55xSPnN3VSkJi+ZAuE0VmUk+ElaWKhCHzhHU6VQypQ0MYpTu3kNDwWM23zI oRXegZCpPiJfyxBfaUY/UM60SeZURTbkZOWJgmUg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377792519; i=@resistor.net; bh=anmAUVbD1iXvzUr6mjTSeBfRGyXXF2bIQtg/4u2Xs84=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=j4ssH5DKE/ZH4PxmLkd3oAaEiMyhD5RdiRdW3uTooIHKQaIi1Gto6lIJVbtrWIL/a TIWt+QXwjmYoIh7u6Qtb7SkVLmQewaIoznrp7IGkWUwSAdQIqLDWMAzR0a5uJxmrpp Qo3Hft3OGvL/IqLEECMJR1cuRfx/4IYuNQHyIwBw=
Message-Id: <6.2.5.6.2.20130829083719.0cf0d4b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Aug 2013 08:44:02 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation of Standards Track Code Points) to Best Current Practice
In-Reply-To: <20130827215216.30701.52572.idtracker@ietfa.amsl.com>
References: <20130827215216.30701.52572.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 16:10:33 -0000

At 14:52 27-08-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Early IANA Allocation of Standards Track Code Points'
>   <draft-cotton-rfc4020bis-01.txt> as Best Current Practice
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-09-24. Exceptionally, comments may be

In Section 2:

   'a.  The code points must be from a space designated as "Specification
        Required" (where an RFC will be used as the stable reference),
        "RFC Required", "IETF Review", or "Standards Action".'

I suggest not having the comment (where) and leaving it to RFC 5226 
to define "Specification Required".

Regards,
-sm 


From chris.dearlove@baesystems.com  Thu Aug 29 09:16:51 2013
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 7FDE011E8124 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.424
X-Spam-Level: 
X-Spam-Status: No, score=-10.424 tagged_above=-999 required=5 tests=[AWL=0.175, 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 szANAmsNt6C6 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:16:40 -0700 (PDT)
Received: from ukmta1.baesystems.com (ukmta1.baesystems.com [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8B411E8123 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:16:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.89,984,1367967600"; d="scan'208";a="368500053"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 29 Aug 2013 17:16:39 +0100
X-IronPort-AV: E=Sophos;i="4.89,984,1367967600"; d="scan'208";a="25723363"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds017.greenlnk.net with ESMTP; 29 Aug 2013 17:16:38 +0100
Received: from GLKXM0002V.GREENLNK.net ([169.254.2.167]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.02.0328.009; Thu, 29 Aug 2013 17:16:39 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Michelle Cotton <michelle.cotton@icann.org>, t.p. <daedulus@btconnect.com>, ietf <ietf@ietf.org>
Subject: RE: "Deprecate"
Thread-Topic: "Deprecate"
Thread-Index: AQHOpK8MflEosozqrkuNGBrMiI8cTZmsGcLggAAbFICAACeD4A==
Date: Thu, 29 Aug 2013 16:16:39 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0B6F@GLKXM0002V.GREENLNK.net>
References: <B31EEDDDB8ED7E4A93FDF12A4EECD30D3DBD0A61@GLKXM0002V.GREENLNK.net> <CE44ADE0.E6DD3%michelle.cotton@icann.org>
In-Reply-To: <CE44ADE0.E6DD3%michelle.cotton@icann.org>
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: Thu, 29 Aug 2013 16:16:51 -0000

Do you intend the same basic meaning, i.e. please don't use this in anythin=
g new, we may remove it in the future (that's two points, not one)?

--=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: Michelle Cotton [mailto:michelle.cotton@icann.org]=20
Sent: 29 August 2013 15:53
To: Dearlove, Christopher (UK); t.p.; ietf
Subject: Re: "Deprecate"

We are working on 5226bis right now and have a plans to discuss the term
in there.

--Michelle Cotton

Michelle Cotton
Manager, IANA Services
ICANN



On 8/29/13 5:22 AM, "Dearlove, Christopher (UK)"
<chris.dearlove@baesystems.com> wrote:

>It's definitely an ISO term, I see it used for features of C++.
>
>There's then discussion even there of what it means. It is, I think,
>meant to be used for "we don't think you should use this, there's
>something better, and this is a warning that it may get removed in a
>future version". In the case of computer languages there is an additional
>possibility of "your compiler may emit a warning if you persist in using
>it".
>
>But the only major feature (export) removed in the last C++ version went
>straight from "part of the standard, but only one compiler ever
>implemented it, and thus found out it was a bad realisation of an idea"
>to removed, with no intermediate deprecated stage. And other features
>just hang around deprecated. So it really doesn't guarantee anything in
>that instance, neither than if deprecated will go, not if not deprecated
>won't go.
>
>--=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
>
>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
>t.p.
>Sent: 29 August 2013 12:56
>To: ietf
>Subject: "Deprecate"
>
>----------------------! 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.
>--------------------------------------------------------
>
>I recently saw 'deprecate' used in an IANA Considerations and turned to
>"IANA Considerations" [RFC5226] to see how it was defined only to find
>no mention of it there.  I am used to the term from SMI, as quoted
>below, but that seems not quite right, in that a deprecated IANA entry
>never disappears, as in
>http://www.iana.org/assignments/smi-numbers/smi-numbers.xhtml#smi-number
>s-5
>
>Are there other, perhaps better definitions of the term 'deprecated' in
>use outside SMI (and yes, I know about praying nuns!)?
>
>Tom Petch
>
>----- Original Message -----
>From: "Fred Baker (fred)" <fred@cisco.com>
>To: "IPv6 Maintanence" <ipv6@ietf.org>
>Sent: Monday, July 29, 2013 3:32 PM
>Subject: "Deprecate"
>
>
>> At the mike a moment ago, I referred to an existing formal definition
>of "deprecate". For the record, the reference is to RFC 1158, which
>reads:
>>
>> 3.1.  Deprecated Objects
>>
>>    In order to better prepare implementors for future changes in the
>>    MIB, a new term "deprecated" may be used when describing an object.
>>    A deprecated object in the MIB is one which must be supported, but
>>    one which will most likely be removed from the next version of the
>>    MIB (e.g., MIB-III).
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>
>
>
>********************************************************************
>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 john-ietf@jck.com  Thu Aug 29 09:31:51 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BAC211E8123 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-SdlVE2nQiC for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:31:40 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 83ECF11E8122 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:31:40 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VF58C-000Hxd-PU; Thu, 29 Aug 2013 12:31:36 -0400
Date: Thu, 29 Aug 2013 12:31:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy	Framework (SPF) for Authorizing Use of Domains in Email,	Version 1) to Proposed Standard
Message-ID: <33BAD063A63D81764705AC33@JcK-HP8200.jck.com>
In-Reply-To: <521E0759.7090504@dcrocker.net>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net> <521E0759.7090504@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 16:31:51 -0000

--On Wednesday, August 28, 2013 07:21 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

>> RFC 5507 primarily raises three concerns about TXT records:
> 
> RFC 5507 is irrelevant to consideration of the SPFbis draft.
> 
> Really.
> 
> RFC 5507 concerns approaches to design.  However the SPFbis
> draft is not designing a new capability.  It is documenting a
> mechanism that has existed for quite a long time, is very
> widely deployed, and has become an essential part of Internet
> Mail's operational infrastructure that works to counter abuse.
>...

Dave.

I may be violating my promise to myself to stay out of
SPF-specific issues, but this does not seem to me to be an
SPF-specific issue.  I suggest to you that the notions of IETF
change control and consensus of the IETF community are very
important to the integrity of how the IETF does things.  The
question of where and how the IETF adds value comes in there
too.  If some group --whether an IETF WG or some external
committee or body-- comes to the IETF and says "we have this
protocol, it is well-tested and well-deployed, and we think  the
community would benefit from the IETF publishing its
description" that is great, we publish as Informational RFC (or
the ISE does), and everyone is happy.   If that group can get
IETF community consensus for the idea that the spec should get a
gold star, someone writes an Applicability Statement that points
to the other document and says "Recommended", we push any
quibbles about downrefs out of the way, and we move on.

However, it seems to me that, for anything that is proposed to
be a normal standards track document, the community necessarily
ought to be able to take at least one whack at it on IETF LC.
That "one whack" principle suggests that one cannot say "this
was developed and deployed elsewhere and is being published as
Experimental" (which is what, IIR, was one thing that happened
in the discussion of 4408) and then say "now the design quality
of SPF is not a relevant consideration because it has been
considered elsewhere and widely deployed".  If the IETF doesn't
get a chance to evaluate design quality and even, if
appropriate, to consider the tradeoffs between letting a
possibly-odious specification be standardized and causing a fork
between deployed-SPF and IETF-SPF, then the IETF's statements
about what its standards mean become meaningless (at least in
this particular type of case).

Now I think it is perfectly reasonable to say, as you nearly did
later in your note, that SPF-as-documented-in-4408bis is
sufficiently deployed and would be sufficiently hard to change
that the community should swallow its design preferences and
standardize the thing.  One can debate that position, but it is
at least a reasonable position to take.    Modulo some quibbles,
it probably the position I'd take at this point if I were
willing to take a position, but it is different from saying
"can't discuss the design choices".

Things would also be very different if the present question
involved updating or replacing an existing Proposed Standard.
If design decisions were made in that earlier version (and that
went through IETF LC and got consensus), I think it would be
perfectly reasonable to say "the IETF community looked at that
before and it is now too late".  You've done that before, I've
done it before, and I don't think anyone who isn't prepared to
explain why, substantively and in terms of deployment, it isn't
too late should be able to object.  

But, in the absence of demonstrated and documented IETF
consensus --independent of WG consensus, implementation
consensus, deployment consensus, silent majority consensus, or
any other type of claim about broader community consensus-- I
don't think one can exclude a discussion of a specification's
relationship to various design considerations, if only because
"that may be deployed but the IETF should not endorse it in that
form by standardizing it" or even "if the community that is
advocating this won't allow design issues to be discussed, then
there is no IETF value-added and the IETF should decline to
standardize on that basis" have got to be possible IETF
community responses.

> To consider RFC 5507 with respect to SPFbis is to treat the
> current draft as a matter of new work, which it isn't.

No, it is to treat the current draft as a matter of work that
the IETF is being asked to standardize for the first time...
which, as far as I can tell, it is.

I think those distinctions about standardization (including the
value-added and change control ones) and what can reasonably be
raised on IETF LC are important to the IETF, even for those who
agree with you (entirely or in part) about what should happen
with this particular specification at this particular point.

YMMD.

best,
   john


From barryleiba.mailing.lists@gmail.com  Thu Aug 29 09:43:02 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD2F11E812C for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:43:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.904
X-Spam-Level: 
X-Spam-Status: No, score=-101.904 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, 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 Gb9H7zzEQi90 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:43:02 -0700 (PDT)
Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id DE73311E8128 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:43:01 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id 15so530612vea.29 for <ietf@ietf.org>; Thu, 29 Aug 2013 09:43:00 -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:message-id:subject :from:to:cc:content-type; bh=ZSiPHaHug5lipqWJcJHJt3xP5eUyEbJFf5P6EwM1jyU=; b=UF+qDf9H6jHNQm1kf/khCw9nmphqStKUhVqXdGhgqpVPHZth8a4KEC+zrN71AoNZU8 7gojMGOVFfAGwIoUUhgmkvdPzAYsfoANRjkAq0FjXvZO4jZYLkV7Ct0y2KQ8b2nmkNrY 0kv0YTK6DLdZOzYhpiJMxfFRS+pO/9o5xA7Hjfulu/JWGsBzomAR5oVLiTCH2mYw/VeP etlbuxdJiGN0Vkbsc0i4Q45k9lOXwz8KVG0w5nLjD17uquq8eK8cIkz1zviHShYReXI+ 9FlDBIpZvhD0qwVpc70IOIGc29pTVko+kjs4Ecin7YFaIMNDwS/TctsdEDX8ExnosEIl jtRw==
MIME-Version: 1.0
X-Received: by 10.221.27.73 with SMTP id rp9mr1615918vcb.29.1377794580326; Thu, 29 Aug 2013 09:43:00 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.215.16 with HTTP; Thu, 29 Aug 2013 09:43:00 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130829083719.0cf0d4b0@resistor.net>
References: <20130827215216.30701.52572.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130829083719.0cf0d4b0@resistor.net>
Date: Thu, 29 Aug 2013 12:43:00 -0400
X-Google-Sender-Auth: 0nIsd0vzx37qhai8gidrxp5dMWA
Message-ID: <CAC4RtVCFyiJbYZFYqz2cYcm3o=Ms0QRXLVTfXRSXt-rKQhWw2Q@mail.gmail.com>
Subject: Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation of Standards Track Code Points) to Best Current Practice
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
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, 29 Aug 2013 16:43:02 -0000

> In Section 2:
>
>   'a.  The code points must be from a space designated as "Specification
>        Required" (where an RFC will be used as the stable reference),
>        "RFC Required", "IETF Review", or "Standards Action".'
>
> I suggest not having the comment (where) and leaving it to RFC 5226 to
> define "Specification Required".

Yes, except that's not what this means.

I tripped over the same text, and I suggest rephrasing it this way:

NEW
   The code points must be from a space designated as "Specification
   Required" (in cases where an RFC will be used as the stable reference),
   "RFC Required", "IETF Review", or "Standards Action".

Barry

From sm@resistor.net  Thu Aug 29 10:12:36 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DAA111E8142 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level: 
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 XI1sSOsgLX-p for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:12:35 -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 0AEA211E8141 for <ietf@ietf.org>; Thu, 29 Aug 2013 10:12:34 -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 r7THCK77011969; Thu, 29 Aug 2013 10:12:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377796344; bh=wMkAKlZCM3Ct+XYtLJjXo/XZAzFRsICcfdIbyh0lw5A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yY1JY9jlW7xcdrb1n5UH2ns1UeMfCvjICLxxf+kQD2ORmZIc1X+Zacpo4yaAOCkRc +surdeDRdqBI7O0QJljPquztznOvOGyrbbxgwDhpXXudn8DPjSdMrx6X3XgNcrrQ8h lAmDPy8qIvCrE/SAiXp3JJSwePvnnyBhKwu0mKGU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377796344; i=@resistor.net; bh=wMkAKlZCM3Ct+XYtLJjXo/XZAzFRsICcfdIbyh0lw5A=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BkN+3IqHIm1A+R13gjlN42oYDhcqdV3QeGAwYnMzRKOl7gLOp6y/RD2QR9NMOwJ2q LByTO1GUflnc9ovTESAxA1t72VgJp8G+NYzYdkLwCH20Mo0rAwCzzV+CyEVJnsHmfJ CnQ7sbT3/YWnHYqmkCCEV0OzOVBNDB3+BvKi4vBs=
Message-Id: <6.2.5.6.2.20130829095350.0cf0db18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Aug 2013 09:56:34 -0700
To: Barry Leiba <barryleiba@computer.org>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA Allocation of Standards Track Code Points) to Best Current Practice
In-Reply-To: <CAC4RtVCFyiJbYZFYqz2cYcm3o=Ms0QRXLVTfXRSXt-rKQhWw2Q@mail.g mail.com>
References: <20130827215216.30701.52572.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130829083719.0cf0d4b0@resistor.net> <CAC4RtVCFyiJbYZFYqz2cYcm3o=Ms0QRXLVTfXRSXt-rKQhWw2Q@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, 29 Aug 2013 17:12:36 -0000

Hi Barry,
At 09:43 29-08-2013, Barry Leiba wrote:
>I tripped over the same text, and I suggest rephrasing it this way:
>
>NEW
>    The code points must be from a space designated as "Specification
>    Required" (in cases where an RFC will be used as the stable reference),
>    "RFC Required", "IETF Review", or "Standards Action".

That looks better.

Regards,
-sm  


From dean.willis@softarmor.com  Thu Aug 29 10:17:19 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7109E21F9DC6 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:17:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.977
X-Spam-Level: 
X-Spam-Status: No, score=-101.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 4ZMQJ9reaP6C for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:17:18 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 3D00721F9CB0 for <ietf@ietf.org>; Thu, 29 Aug 2013 10:17:18 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id ij15so545396vcb.30 for <ietf@ietf.org>; Thu, 29 Aug 2013 10:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=agLVfQE69su+y9BMwvzHTj9FB8vhvdPbXxR0qyAL0w8=; b=QCh2widBh+LNkKaxrCtriAHrajyr+foko96yjtJwnWnH8Iw56zJvdBj690d5bv0E5d 4tsLrml422m3LgSCAanfZoRSJfJN/wU1+jwvemyYjm5vY08lj6cTq3wR+KGGqCe4vuvD SWoudUxxIlOklfmjOR2O3f7BtH/zd5zZnSyMQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=agLVfQE69su+y9BMwvzHTj9FB8vhvdPbXxR0qyAL0w8=; b=DLQd+BQySmpvZ+ev7HXXe06uL04WJewl8nRsrP/PewM7otU2pdtBQCssYFhYsVrcyI ZJRMyGba/mIv87LwUt4dxVYHg2NY7LWteozXv/tvsx0uN9MyIe49ItJGwLSEHhlvM5eh Hd69H43eKUFqrOhExzCWXwLRFNi4PYp0d/M6lQmRuw5aNxak2oyXIFjXV5oh3NY4+8nO kUEegjrxuigf0Y2zbk+oVc+icDsBoBqBSgBxuVths/E9IlCfT+gz0rHd7T2RLb2gQlb3 peF475IljVXP8fNxVOJuySy4KztmhKtYUT/S3l39vCZJ5in25Hg7PQxTlTG97PQIJIm4 cJ5g==
X-Gm-Message-State: ALoCoQn5tf8oS6sNPYz3NFUpu8zqHZ0XrtGpQygwzIJ2R29i0MS8riC6m65CICDsk6mISyrTzIyn
MIME-Version: 1.0
X-Received: by 10.58.97.138 with SMTP id ea10mr124047veb.38.1377796633818; Thu, 29 Aug 2013 10:17:13 -0700 (PDT)
Received: by 10.58.168.180 with HTTP; Thu, 29 Aug 2013 10:17:13 -0700 (PDT)
Date: Thu, 29 Aug 2013 12:17:13 -0500
Message-ID: <CAOHm=4vAjb_CyaGm-4FrW8_7dSNtSk7YD0uUhWu7iQ31-HPkOg@mail.gmail.com>
Subject: External link to article on trends in anti-surveillance design
From: Dean Willis <dean.willis@softarmor.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e013a2860ee84da04e5194615
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 17:17:19 -0000

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

Some of you may recall me ranting several years ago about the importance of
including anti-surveillance features as mandatory aspects of our protocols.
I seem to recall getting (mostly) politely laughed at ...

Anyhow, there's an article on the topic in Wired right now that hints at
the commercial reasons why service companies MUST build anti-surveillance
into their products in order to maintain market viability -- because their
competitors are going to do it and draw away the users. The same can apply
to our protocol designs.

http://www.wired.com/opinion/2013/08/stop-clumping-tech-companies-in-with-government-in-the-surveillance-scandals-they-may-be-at-war/


he point I'd like to make is that not only should our protocols be designed
so as to reduce their surveilability, they should also be design to help
other protocols do the same. Encryption, random ports, random packet sizes,
random interpacket timings, multipath, and peer-to-peer with relay support.
Think about it.

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

<div dir=3D"ltr"><br><div>Some of you may recall me ranting several years a=
go about the importance of including anti-surveillance features as mandator=
y aspects of our protocols. I seem to recall getting (mostly) politely laug=
hed at ...</div>
<div><br></div><div>Anyhow, there&#39;s an article on the topic in Wired ri=
ght now that hints at the commercial reasons why service companies MUST bui=
ld anti-surveillance into their products in order to maintain market viabil=
ity -- because their competitors are going to do it and draw away the users=
. The same can apply to our protocol designs.</div>
<div><br></div><div><a href=3D"http://www.wired.com/opinion/2013/08/stop-cl=
umping-tech-companies-in-with-government-in-the-surveillance-scandals-they-=
may-be-at-war/">http://www.wired.com/opinion/2013/08/stop-clumping-tech-com=
panies-in-with-government-in-the-surveillance-scandals-they-may-be-at-war/<=
/a><br>
</div><div><br></div><div><br></div><div>he point I&#39;d like to make is t=
hat not only should our protocols be designed so as to reduce their surveil=
ability, they should also be design to help other protocols do the same. En=
cryption, random ports, random packet sizes, random interpacket timings, mu=
ltipath, and peer-to-peer with relay support. Think about it.</div>
</div>

--089e013a2860ee84da04e5194615--

From stpeter@stpeter.im  Thu Aug 29 10:22:40 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB4821E8088 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:22:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.388
X-Spam-Level: 
X-Spam-Status: No, score=-102.388 tagged_above=-999 required=5 tests=[AWL=0.211, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sEc+M8Qt6jMa for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:22:36 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9D7CF21E804E for <ietf@ietf.org>; Thu, 29 Aug 2013 10:22:31 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4066F41587; Thu, 29 Aug 2013 11:26:18 -0600 (MDT)
Message-ID: <521F8354.3030807@stpeter.im>
Date: Thu, 29 Aug 2013 11:22:28 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: External link to article on trends in anti-surveillance design
References: <CAOHm=4vAjb_CyaGm-4FrW8_7dSNtSk7YD0uUhWu7iQ31-HPkOg@mail.gmail.com>
In-Reply-To: <CAOHm=4vAjb_CyaGm-4FrW8_7dSNtSk7YD0uUhWu7iQ31-HPkOg@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 17:22:41 -0000

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

On 8/29/13 11:17 AM, Dean Willis wrote:
> 
> importance of including anti-surveillance features as mandatory 
> aspects of our protocols.

Interesting stuff, but more on-topic for the perpass list:

https://www.ietf.org/mailman/listinfo/perpass

Peter

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

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

iQIcBAEBAgAGBQJSH4NUAAoJEOoGpJErxa2pNxAP/0fNnkYKwbY7f8kF/3/oHijP
+XFYQa0/mKU0acPagW+sDod6+feqke/rtWs/dljBQ12ONIwfiZUVthUT6HoU8U2r
RwFbJoaHbDe5NxkqcqVx3bJMCWYvlso3hRZEeQOQzewf6U9mjxErHVpl/KZTp0Hf
/iuROfXX0EVr6LdCaktkTbpTf1Hwdm2E8okziCOwJ3VGPTwWIlfcsAnYu3ZVDZOk
Gy6Tr27ePmFI1zDcrjsmT5XVfL2VMre4xlLSyn2ODz8l+rk1demfzEJ++kN/N9dn
NacQCKHQYU2LuNXHcOm4GEBRJ06tvPN54sQ5H7iMZGt7BICY3BhciUKu1tNIBDne
xalUaKwYznfEa7QugZ9dzFPv1tel9yztICaxE2SyqCc2MUjzpj853hWEwvZBraV7
QfpJUQD04pw9mLLkfd2q6KWBUuG8a66ZMLSMCGZaQqnWoJsya9rqHbakm9d/MVsr
jTpUTW/qv4XEOk9ykgeD5afzZfRyqpo+3m5ByqH8rZt+I0RPn0o4ZY7mna4Tctp+
MhaTy2VBwCW80ICywqfliUXnQUro5hIKXacuWpVKCM0XLcYAOZInASH6P995k/ux
nvVK+Z02yBf/wTJChyP9rn9FXto1lXrHR4F0Ntnr7QrE0ygRocZ0viWool2rf7vR
f2WaIcKyqh40yx2SwsVu
=30q+
-----END PGP SIGNATURE-----

From john-ietf@jck.com  Thu Aug 29 10:48:19 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1C611E813A for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:48:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.471
X-Spam-Level: 
X-Spam-Status: No, score=-102.471 tagged_above=-999 required=5 tests=[AWL=-0.028, 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 J8BWiU-FW7SM for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:48:13 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E48CA11E8138 for <ietf@ietf.org>; Thu, 29 Aug 2013 10:48:12 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VF6KF-000I2e-Bb; Thu, 29 Aug 2013 13:48:07 -0400
Date: Thu, 29 Aug 2013 13:48:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, SM <sm@resistor.net>
Subject: Re: Last Call: <draft-cotton-rfc4020bis-01.txt> (Early IANA	Allocation of Standards Track Code Points) to Best Current Practice
Message-ID: <507358904A204EC71F2C5C3D@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVCFyiJbYZFYqz2cYcm3o=Ms0QRXLVTfXRSXt-rKQhWw2Q@mail.gmail.com>
References: <20130827215216.30701.52572.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130829083719.0cf0d4b0@resistor.net> <CAC4RtVCFyiJbYZFYqz2cYcm3o=Ms0QRXLVTfXRSXt-rKQhWw2Q@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 17:48:19 -0000

--On Thursday, August 29, 2013 12:43 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

>> In Section 2:
>> 
>>   'a.  The code points must be from a space designated as
>>   "Specification Required" (where an RFC will be used as the
>>        stable reference), "RFC Required", "IETF Review", or
>>        "Standards Action".'
>> 
>> I suggest not having the comment (where) and leaving it to
>> RFC 5226 to define "Specification Required".
> 
> Yes, except that's not what this means.
> 
> I tripped over the same text, and I suggest rephrasing it this
> way:
> 
> NEW
>    The code points must be from a space designated as
> "Specification    Required" (in cases where an RFC will be
> used as the stable reference),    "RFC Required", "IETF
> Review", or "Standards Action".

Barry, that leaves me even more confused because it seems to
essentially promote "Specification Required" into "RFC Required"
by allowing only those specifications published as RFCs.  

Perhaps, given that this is about Standards Track code points,
that is just what is wanted.  If so the intent would be a lot
more clear if the text went a step further and said:

NEWER:

	The code points must normally be from a space designated
	as "RFC Required", "IETF Review", or "Standards Action".
	In addition, code points from the "Specification
	Required" are allowed if the specification will be
	published as an RFC.

There is still a small procedural problem here, which is that
IANA is asking that someone guarantee RFC publication of a
document (or its successor) that may not be complete.  There is
no way to make that guarantee.  In particular, the guarantee of
Section 2 (c) without constraining the actions that IETF LC can
reasonably consider.  As I have argued earlier today in another
context, language that suggests really strong justification for
the tradeoff may be acceptable, but a guarantee to IANA by the
WG Chairs and relevant ADs, or even the full IESG, that
constrains a Last Call is not.   Section 3.2 begins to examine
that issue, but probably doesn't go quite far enough, especially
in the light of the "four conditions" of Section 2.

It would probably be appropriate to identify those conditions as
part of good-faith beliefs.

It might even be reasonable to require at least part of tee
"what if things change" analysis that Section 3.2 calls for
after the decision is made to be included in the request for
early allocation.  Requiring that analysis would also provide a
small additional safeguard against the scenarios discussed in
the Security Considerations section.

Incidentally, while I'm nit-picking about wording, the last
sentence of Section 3.3 has an unfortunate dependency on a form
of the verb "to expire".  Language more similar to that used for
RFCs might be more appropriate, e.g., that the beginning of IESG
Review (or issuance of an IETF Last Call) suspends the
expiration date until either an RFC is published or the IESG or
authors withdraws the document. 

   best,
   john


From Ted.Lemon@nominum.com  Thu Aug 29 10:51:04 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31E721F9BB6 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iqD9iEFef30q for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 10:50:57 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3380521F9B25 for <ietf@ietf.org>; Thu, 29 Aug 2013 10:50:57 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUh+KAEmVwnaHd5O9ypkJqfXC8Zk5+G+U@postini.com; Thu, 29 Aug 2013 10:50:57 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9CF7D1B8032 for <ietf@ietf.org>; Thu, 29 Aug 2013 10:50:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 809DC190070; Thu, 29 Aug 2013 10:50:56 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 29 Aug 2013 10:50:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: External link to article on trends in anti-surveillance design
Thread-Topic: External link to article on trends in anti-surveillance design
Thread-Index: AQHOpNupDaJAjC4Z60iYrVFJQkNUUpms5E0AgAAH8IA=
Date: Thu, 29 Aug 2013 17:50:55 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077526C50A@mbx-01.win.nominum.com>
References: <CAOHm=4vAjb_CyaGm-4FrW8_7dSNtSk7YD0uUhWu7iQ31-HPkOg@mail.gmail.com> <521F8354.3030807@stpeter.im>
In-Reply-To: <521F8354.3030807@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <637DE8C894D1104EB3998D2C47B58B29@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, Dean Willis <dean.willis@softarmor.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, 29 Aug 2013 17:51:04 -0000

On Aug 29, 2013, at 1:22 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> Interesting stuff, but more on-topic for the perpass list:

I think Deans point is precisely that it is _not_ a topic that can be restr=
icted to the perpass list.


From ron.even.tlv@gmail.com  Thu Aug 29 11:17:40 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E025611E814B; Thu, 29 Aug 2013 11:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  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 s1ZlOJdRAmVF; Thu, 29 Aug 2013 11:17:38 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3C81911E813D; Thu, 29 Aug 2013 11:17:38 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hi5so614652wib.3 for <multiple recipients>; Thu, 29 Aug 2013 11:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=oUzB1BwQ0IXz07y6AdqXVRFfDfFY0zqRjajLcV08vuU=; b=SAMF7pusISQp0aT8MB24QQTGvyxmo0lVHiWeYD6qAHi9loj/t5zRr/QETCPP3cfj99 NWwGBSsjYXBQDGwzE2M/sFEUw8ghf+CLlGEIGpS9YW2Bvfx1tFigWGwnqNpeJ1F/U92O ZujsuY0YjhiFfC79s/RlflHETHn5OndBHAT55Hg928Rbw5F6cPKzuNHaRphIWgcaP7B2 E5MbJznUnhVJOhdrXPFl8qWrTMLmI/RaScwYhEsDpHXLb+ZcCdseq2253C/rK0YuwNaf SeBkDocgN6b1q2I7NY9ejO9zVjFb1XsZcTeWvlyiP0jcNOGLc3xKOHMFOnRnhmBwqS6d a3Dg==
X-Received: by 10.180.184.107 with SMTP id et11mr16086773wic.60.1377800257198;  Thu, 29 Aug 2013 11:17:37 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id b13sm2571282wic.9.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 29 Aug 2013 11:17:36 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'t.p.'" <daedulus@btconnect.com>, <draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org>
References: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C28238@szxeml558-mbs.china.huawei.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C284D5@szxeml558-mbs.china.huawei.com><04cf01cea499$22eb4a80$68c1df80$@gmail.com><F73A3CB31E8BE34FA1BBE3C8F0CB2AE255C285CA@szxeml558-mbs.china.huawei.com> <04d701cea4a1$f8fdde00$eaf99a00$@gmail.com> <012001cea4cd$1845c680$4001a8c0@gateway.2wire.net>
In-Reply-To: <012001cea4cd$1845c680$4001a8c0@gateway.2wire.net>
Subject: RE: Gen-ART LC review ofdraft-ietf-mpls-return-path-specified-lsp-ping-12
Date: Thu, 29 Aug 2013 21:15:06 +0300
Message-ID: <054c01cea4e3$b207cc30$16176490$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFOtCz/kupT/msuDkJxBc8cYmi4kAJrrZpSAxjw2zQBgMlGEQLYu/AFA01uBKSaQv41wA==
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, 29 Aug 2013 18:17:40 -0000

HI,
I do not follow all the MPLS work, this Gen-ART review is done during the
IETF LC.  
I would think that your point should have been discussed in the WG before
sending the return path ping to publication.
BTW: I took a quick look at draft-andersson-mpls-lsp-ping-upd-00 third
paragraph of section 2 and I am not sure that the return path ping is
influenced since it does not use all the sub-tlv from tlv type 1 so it
should be a separate registry
Roni

> -----Original Message-----
> From: t.p. [mailto:daedulus@btconnect.com]
> Sent: 29 August, 2013 6:33 PM
> To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> ping.all@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART LC review
ofdraft-ietf-mpls-return-path-specified-lsp-
> ping-12
> 
> Roni
> 
> I find it difficult to know whether to agree with you or not since there
is
> another "gorilla" operating in this namespace, namely
> draft-andersson-mpls-lsp-ping-upd-00
> which sort of gives the option of taking out the sub-TLV types of a TLV
Type
> into a separate registry which can then be referenced by the
specifications of
> several TLV Types.  This I-D formally calls for no action by IANA, except
that it
> implies a reorganisation of the registries which IANA might well already
have
> executed - certainly, the registries no longer look the same as they did a
few
> months ago although that might also be a coincidence.
> 
> You make reference to the registry set up by RFC6426 but you should be
> aware that what is now in the IANA registries is not what was there when
> that RFC was approved; rather, it has changed as alluded to above..
> 
> If
> draft-andersson-mpls-lsp-ping-upd-00
> is approved, and my perception is that IANA assumes it has been, then
this,
> return-path I-D would appear to be barking up the wrong tree and needs
> revising to reflect the new IANA structure, namely that it needs to update
> the title which already exists Sub-TLVs for TLV Types 1 and 16 to become
Sub-
> TLVs for TLV Types 1 and 16 and 21 whereupon things start to fall into
place
> 
> draft-andersson-mpls-lsp-ping-upd-00
> also updates RFC4379 which, if accepted, means, I think, that this I-D
need
> not.
> 
> All very technically sound but we seem to have our processes upside down.
> 
> There is of course a lengthy history to this that is not material to the
current
> discussion.
> 
> Tom Petch
> 
> ----- Original Message -----
> From: "Roni Even" <ron.even.tlv@gmail.com>
> To: "'Mach Chen'" <mach.chen@huawei.com>; <draft-ietf-mpls-return-path-
> specified-lsp-ping.all@tools.ietf.org>
> Cc: <gen-art@ietf.org>; <ietf@ietf.org>
> Sent: Thursday, August 29, 2013 11:24 AM
> Subject: RE: Gen-ART LC review
> ofdraft-ietf-mpls-return-path-specified-lsp-ping-12
> 
> 
> > Hi,
> > This text is OK if one wants to implement this draft.
> > My concern was about the consistency of the IANA registration so that
> if
> > someone defines a new TLV type 1 based on RFC4379, IANA will know that
> it
> > must update also the registry for TLV type 21. If you see no such
> problem, I
> > have no concerns
> > Roni
> >
> > > -----Original Message-----
> > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > Sent: 29 August, 2013 1:05 PM
> > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > ping.all@tools.ietf.org
> > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > Subject: RE: Gen-ART LC review of
> > draft-ietf-mpls-return-path-specified-lsp-
> > > ping-12
> > >
> > > Hi Roni,
> > >
> > > How about this:
> > >
> > > " No assignments of sub-TLVs in the range of 0-16383 and 32768-49161
> > >     are made directly for TLV Type 21, sub-TLVs in these ranges are
> > >     copied from the assignments made for TLV Type 1 and kept the
> same
> > >     as that for TLV Type 1. All sub-TLVs in these ranges (include
> existing
> > >     and future defined) defined for TLV Type 1 apply to TLV Type 21.
> > >     Assignments of sub-..."
> > >
> > > Best regards,
> > > Mach
> > >
> > > > -----Original Message-----
> > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > Sent: Thursday, August 29, 2013 5:21 PM
> > > > To: Mach Chen;
> > > > draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > Subject: RE: Gen-ART LC review of
> > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > >
> > > > Hi,
> > > > I am not sure you responded to my latest email.
> > > >
> > > > Having the policy for TLV type 1 here is not enough in my view
> since I
> > > > only look at RFC4379 and create a new TLV type I will not know
> that I
> > > > have to register it also for the type 21 if it will not be
> mentioned
> > > >
> > > > As for the vendor specific see my other email Roni
> > > >
> > > > > -----Original Message-----
> > > > > From: Mach Chen [mailto:mach.chen@huawei.com]
> > > > > Sent: 29 August, 2013 11:33 AM
> > > > > To: Roni Even; draft-ietf-mpls-return-path-specified-lsp-
> > > > > ping.all@tools.ietf.org
> > > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > > Subject: RE: Gen-ART LC review of
> > > > draft-ietf-mpls-return-path-specified-lsp-
> > > > > ping-12
> > > > >
> > > > > Hi Roni,
> > > > >
> > > > > Thanks for your detailed review and comments!
> > > > >
> > > > > Please see my reply inline...
> > > > >
> > > > > > From: Roni Even [mailto:ron.even.tlv@gmail.com]
> > > > > > Sent: Wednesday, August 28, 2013 9:06 PM
> > > > > > To:
> > > > > >
> draft-ietf-mpls-return-path-specified-lsp-ping.all@tools.ietf.org
> > > > > > Cc: ietf@ietf.org; gen-art@ietf.org
> > > > > > Subject: Gen-ART LC review of
> > > > > > draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > > >
> > > > > > I am the assigned Gen-ART reviewer for this draft. For
> background
> > > > > > on Gen-ART, please see the FAQ at
> > > > > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > > > > > Please resolve these comments along with any other Last Call
> > > > > > comments you may receive.
> > > > > > Document: draft-ietf-mpls-return-path-specified-lsp-ping-12
> > > > > > Reviewer: Roni Even
> > > > > > Review Date:2013-8-28
> > > > > > IETF LC End Date: 2013-9-4
> > > > > > IESG Telechat date:
> > > > > >
> > > > > > Summary: This draft is almost ready for publication as a
> standard
> > > > > > track
> > > > RFC.
> > > > > >
> > > > > >
> > > > > > Major issues:
> > > > > > Minor issues:
> > > > > > I am not clear on the sub-TLV in section 6.2 1. If a new
> sub-TLV
> > > > > > is defined for TLV type 1 do they need also to be added to TLV
> type
> > 21.
> > > > > > This should be clear, and if there is some relation I think it
> > > > > > should be reflected in the IANA registry for TLV type 1
> > > > >
> > > > > Yes, type 21 TLV intends to reuse existing and future defined
> > > > > sub-TLVs for type TLV 1. And in Section 3.3, it has already
> stated
> > this, it
> > > says:
> > > > >
> > > > > "The Target FEC sub-TLVs defined in [RFC4379] provide a good way
> to
> > > > >    identify a specific return path.  The Reply Path TLV can
> carry any
> > > > >    sub-TLV defined for use in the Target FEC Stack TLV that can
> be
> > > > >    registered."
> > > > >
> > > > > So, for Section 6.2, to make it cleaner and more explicit, how
> about
> > > > > this
> > > > > change:
> > > > >
> > > > > Old:
> > > > >
> > > > > " No assignments of sub-TLVs in the range of 0-16383 and
> 32768-49161
> > > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
> are
> > > > >    copied from the assignments made for TLV Type 1. Assignments
> of
> > > > sub-..."
> > > > >
> > > > > New:
> > > > >
> > > > > " No assignments of sub-TLVs in the range of 0-16383 and
> 32768-49161
> > > > >    are made directly for TLV Type 21, sub-TLVs in these ranges
> are
> > > > >    copied from the assignments (including existing and future
> > allocations)
> > > > >    made for TLV Type 1. Assignments of sub-..."
> > > > >
> > > > >
> > > > > > 2. For the vendor or private use why a difference policy than
> the
> > > > > > rest of the sub-TLV registry
> > > > >
> > > > > This document does not make any changes to the "Vendor and
> Private
> > > use"
> > > > > definition, range and policy as defined in RFC4379. In RFC4379,
> it's
> > > > policy is
> > > > > defined different from other ranges.
> > > > >
> > > > > >
> > > > > > Nits/editorial comments:
> > > > > > 1. In section 3.4 I assume that "TC" is traffic class. It will
> be
> > > > > > good to expand and have reference.
> > > > >
> > > > > OK, will fix it when all last call comments received.
> > > > >
> > > > > Best regards,
> > > > > Mach
> >
> >



From superuser@gmail.com  Thu Aug 29 11:37:07 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65EC321E80B6 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 11:37:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[AWL=0.149,  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 Fa7kb-BxbPew for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 11:37:06 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id EC7B121E80AA for <ietf@ietf.org>; Thu, 29 Aug 2013 11:37:03 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id z11so771882wgg.10 for <ietf@ietf.org>; Thu, 29 Aug 2013 11:36:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Pfy2bVIyU1b/Hg/83r3/db3s9yALffzYp+evy6M1aJY=; b=WigMJMJ+7kLxyH+JhrOFW3Xmd/L9MwmwmV/bvITwyKFDy3EzaWnbLn8hQQHCbVpcCw jPro6pGw0Ez7yIuLOQVhYLi1x//Shyamji4VOqFeFtVFQVmx+F0gCqw33Z7ig20wz7U4 DyBMO7xkPSDC/QVPktRr0/d2YNPfrYRltjSn2bfe2fqhvHTKldyGMmP6PUdzwzCMm+2I /99fuTPis05UKjOnvO3ODTXtlEecKpPDG8Bw96VfFQJm0eNy0bb+tGS+cc74yEoZF1M0 OdenN4H2fwnwEViPhODX0gfiEP4j69PfeLI0p3gg4ZLeGqwkIq3IP42DsNIn57aZsvhw DQXA==
MIME-Version: 1.0
X-Received: by 10.194.75.165 with SMTP id d5mr7529445wjw.18.1377801419489; Thu, 29 Aug 2013 11:36:59 -0700 (PDT)
Received: by 10.180.75.144 with HTTP; Thu, 29 Aug 2013 11:36:59 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130829085018.0cef9ea0@resistor.net>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com> <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net> <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@mail.gmail.com> <6.2.5.6.2.20130829085018.0cef9ea0@resistor.net>
Date: Thu, 29 Aug 2013 11:36:59 -0700
Message-ID: <CAL0qLwahKAUg0Dvqp=JYAE8HNejutNYG1W=HHH4LoDG05H=aNQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=047d7bb04bc22e0c7604e51a644e
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, 29 Aug 2013 18:37:07 -0000

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

On Thu, Aug 29, 2013 at 8:57 AM, SM <sm@resistor.net> wrote:

> Hi Murray,
>
> At 01:14 21-08-2013, Murray S. Kucherawy wrote:
>
>> Ah.  I realize that CRLF is standard line termination for SMTP; is it
>> automatically the expected line termination for all line-oriented
>> protocols?  I don't know about others.
>>
>
> I would have to write a long answer to that question. :-)  I haven't had
> time to test what the draft specifies.  Thanks for addressing the comments.
>
>
>
We can go with CRLF, since it's been pointed out to me that most text-based
protocols have historically used that.  Who am I to change history?  :-)

-MSK

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

<div dir=3D"ltr">On Thu, Aug 29, 2013 at 8:57 AM, SM <span dir=3D"ltr">&lt;=
<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&gt=
;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
Hi Murray,<div class=3D"im"><br>
At 01:14 21-08-2013, Murray S. Kucherawy wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Ah. =A0I realize that CRLF is standard line termination for SMTP; is it aut=
omatically the expected line termination for all line-oriented protocols? =
=A0I don&#39;t know about others.<br>
</blockquote>
<br></div>
I would have to write a long answer to that question. :-) =A0I haven&#39;t =
had time to test what the draft specifies. =A0Thanks for addressing the com=
ments.<br>
<br><br></blockquote><div><br></div><div>We can go with CRLF, since it&#39;=
s been pointed out to me that most text-based protocols have historically u=
sed that.=A0 Who am I to change history?=A0 :-)<br><br>-MSK <br></div></div=
>
<br></div></div>

--047d7bb04bc22e0c7604e51a644e--

From scott.brim@gmail.com  Thu Aug 29 11:38:30 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414E721E80BB for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 11:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.148
X-Spam-Level: 
X-Spam-Status: No, score=-102.148 tagged_above=-999 required=5 tests=[AWL=0.451, 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 urttSg+LiWIS for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 11:38:29 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id A211E21E80BD for <ietf@ietf.org>; Thu, 29 Aug 2013 11:38:29 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id fb19so878109obc.38 for <ietf@ietf.org>; Thu, 29 Aug 2013 11:38:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=g8bT5O+mrsqNkzGPlS01RPCHSqnK6gWO0K+Pn2g4Glc=; b=VwvW3fEMXT2u/7F09+4Itot+4cgE5m16nuI095Mq4fXjHbPt89dkV6c7PWZjRiyS5o ZeWn4oSqjFMQtzuwTHA/N+7gXmFtAFSL01UvT5pOd3WHY7ZMVsYaErpMD2yk5WAO1MiD 6BPgpB3xBZepuZGBVTC3z09qH8RebpdO9JBmM+uLRmjPKRes/p1eOfqk4HiRR6o58OH2 5VY8uhNJcmVpWbDZf7l7qvnlhAGg1Gjffmv24AZedF4IJfyTwBAyGPlBeZ9Bs3ZlOL+z F3U5o9aD3yaeTnTzXn4y1CxPPC96xFiB2ELkFhp2t5p3pT7o8A53JG2L9tw0m4JsytQr vonA==
X-Received: by 10.182.230.163 with SMTP id sz3mr3461650obc.81.1377801508075; Thu, 29 Aug 2013 11:38:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Thu, 29 Aug 2013 11:38:08 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077526C50A@mbx-01.win.nominum.com>
References: <CAOHm=4vAjb_CyaGm-4FrW8_7dSNtSk7YD0uUhWu7iQ31-HPkOg@mail.gmail.com> <521F8354.3030807@stpeter.im> <8D23D4052ABE7A4490E77B1A012B63077526C50A@mbx-01.win.nominum.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 29 Aug 2013 14:38:08 -0400
Message-ID: <CAPv4CP99xqrhKFMfdKkw=31oqTgyADNUxy6_tANPaTLPWWTFfQ@mail.gmail.com>
Subject: Re: External link to article on trends in anti-surveillance design
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c2f63a75c1e404e51a697a
Cc: "<ietf@ietf.org>" <ietf@ietf.org>, Dean Willis <dean.willis@softarmor.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, 29 Aug 2013 18:38:30 -0000

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

On Thu, Aug 29, 2013 at 1:50 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Aug 29, 2013, at 1:22 PM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> > Interesting stuff, but more on-topic for the perpass list:
>
> I think Deans point is precisely that it is _not_ a topic that can be
> restricted to the perpass list.
>
>
Yes and yes.  Every protocol needs privacy considerations, and such
considerations SHOULD be discussed in every WG.  But we also need a place
where we can talk about them in general, and that's perpass.

One of the major points a WG should ensure is that a protocol does not
_limit_ the privacy possibilities in the environment it is part of.  That's
not easy, but see RFC 6973 for a start.

Scott

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

<div dir=3D"ltr">On Thu, Aug 29, 2013 at 1:50 PM, Ted Lemon <span dir=3D"lt=
r">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com" target=3D"_blank">Ted.Lemon=
@nominum.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Aug 29, 2013, at 1:22 P=
M, Peter Saint-Andre &lt;<a href=3D"mailto:stpeter@stpeter.im">stpeter@stpe=
ter.im</a>&gt; wrote:<br>


&gt; Interesting stuff, but more on-topic for the perpass list:<br>
<br>
</div>I think Deans point is precisely that it is _not_ a topic that can be=
 restricted to the perpass list.<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Yes and yes. =A0Eve=
ry protocol needs privacy considerations, and such considerations SHOULD be=
 discussed in every WG. =A0But we also need a place where we can talk about=
 them in general, and that&#39;s perpass. =A0</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">One of the =
major points a WG should ensure is that a protocol does not _limit_ the pri=
vacy possibilities in the environment it is part of. =A0That&#39;s not easy=
, but see RFC 6973 for a start.</div>

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Scott</div>=
</div>

--001a11c2f63a75c1e404e51a697a--

From erosen@cisco.com  Thu Aug 29 12:25:00 2013
Return-Path: <erosen@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 71E9911E8150 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 12:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.443
X-Spam-Level: 
X-Spam-Status: No, score=-10.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vou-DXNPzNtr for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 12:24:54 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 2D20A11E814C for <ietf@ietf.org>; Thu, 29 Aug 2013 12:24:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5557; q=dns/txt; s=iport; t=1377804294; x=1379013894; h=from:to:subject:reply-to:date:message-id; bh=ZPu+o7fmPOCEicec4HuF/TBq+42g39fVqt31ze6+ZDA=; b=agbSebOKKqUQf1UsyUmz+uXvWjnSdyqtwyqAT9USqbVKxQzN+rJ6HOCg LIscm6UBIO8t+c20YCN5T4UWeSDygkZHUOtX9ky+SxjmGVt/CDBc6g6Ll zO0yC6E2PcfXIXQOr7JroH2/7CrSuVip/82TDEdHE/kmysYjAu8He8Gwv g=;
X-IronPort-AV: E=Sophos;i="4.89,985,1367971200"; d="scan'208";a="253394269"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 29 Aug 2013 19:24:53 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r7TJOqCA025297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 29 Aug 2013 19:24:53 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id r7TJOq4c021728;  Thu, 29 Aug 2013 15:24:52 -0400
From: Eric Rosen <erosen@cisco.com>
To: ietf@ietf.org
Subject: LC comments on draft-cotton-rfc4020bis-01.txt
X-Mailer: MH-E 8.3.1; nmh 1.5; GNU Emacs 24.3.1
Date: Thu, 29 Aug 2013 15:24:52 -0400
Message-ID: <21727.1377804292@erosen-linux>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: erosen@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, 29 Aug 2013 19:25:00 -0000

I think the procedures proposed in this draft could be simplified a bit if
we'd just focus on the actual issue, viz., that the implementation and
deployment of a new specification is completely decoupled from the progress
of that specification through the standards process.  Once any significant
deployment has begun, the codepoints used by that deployment become de facto
unavailable for future use.  The only real issue is whether we want that
codepoint usage to be recorded in a public place, or whether we want to
pretend officially that the codepoints aren't used, and just let the
conflicts arise in the field.

>From this perspective, I think the following procedures are problematic:

- Section 2, point d:  early allocation is conditioned upon whether there is
  sufficient interest in early (pre-RFC) implementation and deployment in
  the community as judged by working group chairs or ADs.

  What the WG chairs and ADs really have to judge is whether failure to
  issue an early allocation is likely to result in de facto allocation of
  a codepoint, with consequent conflicts in the future.

  Of course, there have also been many cases where the codepoint is already
  in significant deployment before any "official" request for it has been
  made; WG chairs and ADs should take notice of this fact.

- Section 3.1, step 6: "IANA makes an allocation from the appropriate
  registry, marking it as 'Temporary', valid for a period of one year from
  the date of allocation.  The date of first allocation the date of expiry
  should also be recorded in the registry and made visible to the public."

  What is the point of marking it as "temporary"?  Once the codepoint is
  placed into use, it is not any more or less temporary than any other
  codepoint; the codepoint is unavailable for future reuse as long as the
  deployments.  Any codepoint that is no longer in use can of course be
  reused, even if its allocation is not marked "temporary".

  I do not understand the idea of making the allocation "expire" after just
  one year.  Are the deployments going to disappear after one year?  If not,
  then the codepoint allocation will not expire after one year.

- Section 3.3: "If early allocations expire before the document progresses
  to the point where IANA normally makes allocations, the authors and WG
  chairs may repeat the process in section 3.1 to request renewal of the
  code points.  At most, one renewal request may be made; thus, authors
  should choose carefully when the original request is to be made."

  First, it is not up to the authors to "choose carefully" when the original
  request is to be made.  At a certain point in the implementation process,
  the codepoint is needed.  Failure to get the codepoint soon enough will
  just cause the implementors to make up their own codepoint, which will
  invariably leak out into deployment.  

  Second, there is no reason whatsoever to put a two-year limit on the early
  allocation, unless one expects that the deployments using it will
  magically disappear after two years.

  I've seen a number of IETF standardization efforts lag six or seven years
  beyond the actual deployment of the standard.

  It might be worthwhile for the WG chairs to ask every few years whether
  the proposed use of a codepoint has been abandoned, but without some
  assurance that the codepoint will never be used as specified, there is no
  sense declaring it to be expired.

- Section 3.1: "Note that Internet-Drafts should not include a specific
  value of a code point until this value has been formally allocated by
  IANA."

  To me, this seems entirely counter-productive.  Failure to publicize the
  codepoint you're deploying doesn't solve or prevent any problems.  To the
  contrary, including the codepoint values you're using helps to find
  conflicts.

- Section 5: "There is a significant concern that the procedures in this
  document could be used as an end-run on the IETF process to achieve code
  point allocation when an RFC will not be published."

  This concern only makes sense when the codepoint is being requested by
  another SDO. If it's being requested by a vendor (or set of vendors),
  well, no vendor will tell it's customers "sorry, you can't have this
  feature because IETF hasn't allocated a codepoint".

  The real concern is the opposite -- folks will try to delay the allocation
  of a codepoint, in order to prevent their quicker competitors from gaining
  an advantage.  But this only leads to the use of codepoints that are not
  officially allocated.
  
My concrete suggestions for improving the draft would be:

- Emphasize that WG chairs and ADs should base their approval of a request
  on the likelihood that an unofficial codepoint will otherwise get
  allocated (or the fact that it is already in use).

- Eliminate the "temporary" and "automatic expiry" features, aldn eliminate
  the need to refresh a request after one year.

- Eliminate the requirement that an i-d not specify a codepoint value until
  IANA has allocated it

I also think it would be better if the draft stated explicitly that
deployment and standardization are completely decoupled, and that pre-RFC
deployments are a normal and common practice.

The ultimate solution to codepoint allocation problems is to require that
new protocols avoid the use of codepoint fields that contain 8 or fewer
bits.  But perhaps that's not within the scope of this draft.



From dhc@dcrocker.net  Thu Aug 29 12:29:11 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FAC11E8155 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 12:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GLNqn8lbksgH for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 12:29:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5B06311E814C for <ietf@ietf.org>; Thu, 29 Aug 2013 12:29:06 -0700 (PDT)
Received: from [172.29.109.57] (wsip-184-191-162-57.sd.sd.cox.net [184.191.162.57]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7TJT2dZ005550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 29 Aug 2013 12:29:06 -0700
Message-ID: <521FA0F9.6000107@dcrocker.net>
Date: Thu, 29 Aug 2013 12:28:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net> <521E0759.7090504@dcrocker.net> <33BAD063A63D81764705AC33@JcK-HP8200.jck.com>
In-Reply-To: <33BAD063A63D81764705AC33@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.66]); Thu, 29 Aug 2013 12:29:06 -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, 29 Aug 2013 19:29:11 -0000

On 8/29/2013 9:31 AM, John C Klensin wrote:
> I may be violating my promise to myself to stay out of
> SPF-specific issues,


Probably not, since your note has little to do with the realities of the 
SPFbis draft, which is a chartered working group product.  You might 
want to review its charter:

      http://datatracker.ietf.org/wg/spfbis/charter/

Note the specified goal of standards track and the /very/ severe 
constraints on work to be done.  Please remember that this is a charter 
that was approved by the IESG.  The working group produced was it was 
chartered to produce, for the purpose that was chartered.

More broadly, you (and others) might want to review that actual criteria 
the IETF has specified for Proposed in RFC2026.  Most of us like to cite 
all manner of personal criteria we consider important.  Though 
appealing, none of them is assigned formal status by the IETF, with 
respect to the Proposed Standards label; I believe in fact that there is 
nothing that we can point to, for such other criteria, represents IETF 
consensus for them.  The claim that we can't really document our 
criteria mostly means that we think it's ok to be subjective and 
whimsical.

Also for the broader topic, you also might want to reevaluate much of 
what your note does say, in light of the realities of Individual 
Submission (on the IETF track) which essentially never conforms to the 
criteria and concerns you seem to be asserting.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Thu Aug 29 13:11:59 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4917E21F8EB2 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 13:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bov-5ow2Pvl6 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 13:11:54 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6C18A11E8151 for <ietf@ietf.org>; Thu, 29 Aug 2013 13:11: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 1VF8ZN-000IDR-Uf; Thu, 29 Aug 2013 16:11:53 -0400
Date: Thu, 29 Aug 2013 16:11:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email,	Version 1) to Proposed Standard
Message-ID: <4F19B9606B70F70C255C0DDB@JcK-HP8200.jck.com>
In-Reply-To: <521FA0F9.6000107@dcrocker.net>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net> <521E0759.7090504@dcrocker.net> <33BAD063A63D81764705AC33@JcK-HP8200.jck.com> <521FA0F9.6000107@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 20:11:59 -0000

--On Thursday, August 29, 2013 12:28 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 8/29/2013 9:31 AM, John C Klensin wrote:
>> I may be violating my promise to myself to stay out of
>> SPF-specific issues,
> 
> 
> Probably not, since your note has little to do with the
> realities of the SPFbis draft, which is a chartered working
> group product.  You might want to review its charter:
> 
>       http://datatracker.ietf.org/wg/spfbis/charter/
 
> Note the specified goal of standards track and the /very/
> severe constraints on work to be done.  Please remember that
> this is a charter that was approved by the IESG.  The working
> group produced was it was chartered to produce, for the
> purpose that was chartered.

I have reviewed the charter, Dave.  THe reasons I've wanted to
stay out of this discussion made me afraid to make a posting
without doing so.   But the last I checked, WG charters are
approved by the IESG after reviewing whatever comments they
decide to solicit.  They are not IETF Consensus documents.  Even
if this one was, the WG co-chair and document shepherd have made
it quite clear that the WG carefully considered the design issue
and alternatives at hand.  I applaud that but, unless you are
going to argue that the charter somehow allows the WG to
consider some issues that cannot be reviewed on IETF Last Call,
either the design issue is legitimate or the WG violated its
charter.  I, at least, can't read the charter that way.

> More broadly, you (and others) might want to review that
> actual criteria the IETF has specified for Proposed in
> RFC2026.  Most of us like to cite all manner of personal
> criteria we consider important.  Though appealing, none of
> them is assigned formal status by the IETF, with respect to
> the Proposed Standards label; I believe in fact that there is
> nothing that we can point to, for such other criteria,
> represents IETF consensus for them.  The claim that we can't
> really document our criteria mostly means that we think it's
> ok to be subjective and whimsical.

The statement to which I objected was one in which you claimed
(at least as I understood it) that it was inappropriate to raise
a design consideration because the protocol was already widely
deployed.  Your paragraph above makes an entirely different
argument.  As I understand it, your argument above is that it
_never_ appropriate to object during IETF Last Call on the basis
of design considerations (whether it is desirable to evaluate
design considerations in a WG or not).  I believe that design
issues and architectural considerations can sometimes be
legitimate examples of "known technical defects".  If they were
not, then I don't know why the community is willing to spend
time on such documents (or even on having an IAB).

Again, it think it is perfectly reasonable to argue that a
particular design or architectural consideration should not be
applied to a particular specification.  My problem arises only
when it is claimed that such considerations or discussions are a
priori inappropriate.
 
> Also for the broader topic, you also might want to reevaluate
> much of what your note does say, in light of the realities of
> Individual Submission (on the IETF track) which essentially
> never conforms to the criteria and concerns you seem to be
> asserting.

If that were the case, either you are massively misunderstanding
what I am asserting or I don't see your point.   I believe that
my prior note, and this one, assert only one thing, which is
that it is inappropriate to bar any discussion --especially
architectural or design considerations-- from IETF Last Call
unless it addresses a principle that has already been
established for the particular protocol by IETF Consensus.  I
remain completely comfortable, modulo the various "rude
language" topics, with a discussion of why some architectural
principle is irrelevant to a particular specification or even
that trying to apply that principle would be stupid.  But a
discussion along those lines is still a discussion, not an
attempt to prevent a discussion.

And, yes, I believe that Individual Submissions should generally
be subject to a much higher degree of scrutiny on IETF Last Call
than WG documents.  I also believe that, if there appears to be
no community consensus one way or the other, that the IESG
should generally defer to the WG on WG documents but default to
non-approval of Individual Submissions.  But, unless I'm
completely misunderstanding the point you are trying to make, I
don't see what that has to do with this topic.

Dave, we had these sorts of discussions before.  If there are a
common patterns about them, they are that neither of us is
likely to convince the other and that both of us soon get to the
point of either muttering "he just doesn't get it" (or worse)
into our beards or getting really short-tempered.  I suggest
that we not subject the community to that.  By all means respond
to this note if you feel a need to do (I'm not trying to get the
last word and, if I have misunderstood you, I'd like to be
better informed), but then I suggest that we leave the
discussion to others if they believe it to be of value.

best,
    john






From sm@resistor.net  Thu Aug 29 15:55:20 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F6321F999B for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 15:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hla8-Xuyo6XS for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 15:55:19 -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 2B6DE21F9981 for <ietf@ietf.org>; Thu, 29 Aug 2013 15:55:19 -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 r7TMtEOC023236 for <ietf@ietf.org>; Thu, 29 Aug 2013 15:55:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377816918; bh=w05JLqnDcAxY9fI9NME3064bxk62X/NjO4CQmEYtDRE=; h=Date:To:From:Subject:In-Reply-To:References; b=PMxF1tamW9E4hzfVyZporSxQTYOk3lzpMCF95qTKB0xagNEa1ipWqpMthP0QT+udM I4Ou8/mFZT60BVI/dEFgkJSQ+dcy/OLmwpt2jNTxa31D+SfUlUc6r66WOsl4kdf0zu wSmPEWq3x2OX2bLKqS8HgHTZPJA+LpXRSpf0ShmE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377816918; i=@resistor.net; bh=w05JLqnDcAxY9fI9NME3064bxk62X/NjO4CQmEYtDRE=; h=Date:To:From:Subject:In-Reply-To:References; b=UT4u8/KfSWLAQZDJpis+4bwh8w1+MoIyP+Kd+Uo9k5BWWCbJe8HdWNw4SAWO2OBGg 720fC4Fse8PuaMtB3xCpfYdpRPMUa6CzWX3YfLzkFZfZGUrMCqIZYNkcP/jgdKIM7X o4tuVRtT0aK+lOasih1TNyQEnhQhkVJwbKO6y6pw=
Message-Id: <6.2.5.6.2.20130829152744.0cd688b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Aug 2013 15:50:29 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Mail lost yesterday
In-Reply-To: <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soto n.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk>
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: Thu, 29 Aug 2013 22:55:20 -0000

Hello,

Could whoever from the IETF "leadership" who is responsible for the 
matter please comment about the mail loss incident?

I previously commented about the visibility of IETF services.  That 
aspect of the IETF lacks transparency [1] and leaves it to the user 
to guess what is wrong at his/her end.

Regards,
-sm

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


From bob.hinden@gmail.com  Thu Aug 29 16:29:02 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3C611E817D for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 16:29: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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8t-S+mgigvl4 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 16:29:01 -0700 (PDT)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF9811E8192 for <ietf@ietf.org>; Thu, 29 Aug 2013 16:29:01 -0700 (PDT)
Received: by mail-wg0-f54.google.com with SMTP id e12so201015wgh.33 for <ietf@ietf.org>; Thu, 29 Aug 2013 16:29:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YHRjbJM18Pt+TXxwfu5hf5U4NeVONWbTr1mMT6i1hN8=; b=sW8aAfgZ31czP3Ub0ZMBjt5NCQ2sQ7n4fL3QRtq0bNLSCP5qXfDX2SlpfN++Wp5LxE 1GbSRpKDrPKQUsT7bjXZWpK3MJz2Qhkutet0UT54f1JiTK0+WAbBUwIeA47uV031BPPV xp9rOTsU6yJtY5ySESHjd1j55YFL5q1uKIyrEnMkD7zp3yx76kVpTyvE2byj+fm7Qz3u kyiLyxmRy3ky9SiUeyVh+PNGNsh2K4046rReiiRIBbALH9C5k08EmgfSGBQ96n1rh9wu V2OAyLRP3OEZTftZ2asmqn7Jk9JJ8QujH3dquG2atYVKjStmEOlzjFOMzSTIg+SZnVAf HSnw==
X-Received: by 10.180.205.236 with SMTP id lj12mr119086wic.22.1377818940743; Thu, 29 Aug 2013 16:29:00 -0700 (PDT)
Received: from [10.0.0.24] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPSA id i12sm237038wiw.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 Aug 2013 16:28:56 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Mail lost yesterday
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <6.2.5.6.2.20130829152744.0cd688b0@resistor.net>
Date: Thu, 29 Aug 2013 16:28:51 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <6.2.5.6.2.20130829152744.0cd688b0@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
Cc: 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, 29 Aug 2013 23:29:02 -0000

SM,

The place to report IETF operational problems is <ietf-action@ietf.org>. =
 I forwarded your email.

Bob

On Aug 29, 2013, at 3:50 PM, SM <sm@resistor.net> wrote:

> Hello,
>=20
> Could whoever from the IETF "leadership" who is responsible for the =
matter please comment about the mail loss incident?
>=20
> I previously commented about the visibility of IETF services.  That =
aspect of the IETF lacks transparency [1] and leaves it to the user to =
guess what is wrong at his/her end.
>=20
> Regards,
> -sm
>=20
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg68755.html
>=20


From hallam@gmail.com  Thu Aug 29 16:43:13 2013
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 A08FB11E818B for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 16:43:13 -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, 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 jtVItxMRlvgc for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 16:43:12 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 14F8E11E80D2 for <ietf@ietf.org>; Thu, 29 Aug 2013 16:43:11 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id c11so635641lbj.41 for <ietf@ietf.org>; Thu, 29 Aug 2013 16:43:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Oiw5y71cjBLxp/oVlmatgBEYQSuN6RMzuZPMFisTwyc=; b=Wf7FZ2oLk6GVf6aQl638y1pBCH1QwXbfj9DnNUn0qvOL2Id5WjJlJl6RnSkSS39ep6 6FIxrNq2Sj65Z4seKcXaxov+tee2KBkNOM2bwSx61QRd0IOJ0uCLgR6ymYfHMZgaH1h6 NlzuCnziFBjQVk13y+b9OgpNYTpb55EhE41qMejQ9ONSHfrR5vzmv3Cfx8dxyg3KjXKY 9CbpDX6C9gxJeoNapeoGjMnK+pJkkY1/7+XfThT9hOF12k0BMSYySPtj9M5Svj8UTRjq bnaHKfwQhbXMbUXQXi+3K1KJYKrkdcNXCcUG/f8GOV9k2iFR7mXmE8WxbA3OkzCh3nxn SyjA==
MIME-Version: 1.0
X-Received: by 10.112.51.166 with SMTP id l6mr5330913lbo.5.1377819790960; Thu, 29 Aug 2013 16:43:10 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Thu, 29 Aug 2013 16:43:10 -0700 (PDT)
In-Reply-To: <33BAD063A63D81764705AC33@JcK-HP8200.jck.com>
References: <9884B9CD-0ED3-4D89-A100-58D05EA4BC98@gmail.com> <6.2.5.6.2.20130823234808.0b7cfed0@elandnews.com> <C5D75C5C-D468-4104-A478-0A055F43AED9@gmail.com> <6.2.5.6.2.20130826182352.0cac3298@elandnews.com> <330A924C-17DA-4082-92AD-FDB6EF09192A@hopcount.ca> <6.2.5.6.2.20130827090837.0d7b3e18@elandnews.com> <6.2.5.6.2.20130828044224.06ee3980@resistor.net> <521E0759.7090504@dcrocker.net> <33BAD063A63D81764705AC33@JcK-HP8200.jck.com>
Date: Thu, 29 Aug 2013 19:43:10 -0400
Message-ID: <CAMm+LwhBv9gRVQai2ZndP4Ntypmk6icOB_8C9664C_3nSk4shg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a113366bc346d7f04e51eab56
Cc: Dave Crocker <dcrocker@bbiw.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: Thu, 29 Aug 2013 23:43:13 -0000

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

On Thu, Aug 29, 2013 at 12:31 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Wednesday, August 28, 2013 07:21 -0700 Dave Crocker
> <dhc@dcrocker.net> wrote:
>
> >> RFC 5507 primarily raises three concerns about TXT records:
> >
> > RFC 5507 is irrelevant to consideration of the SPFbis draft.
> >
> > Really.
> >
> > RFC 5507 concerns approaches to design.  However the SPFbis
> > draft is not designing a new capability.  It is documenting a
> > mechanism that has existed for quite a long time, is very
> > widely deployed, and has become an essential part of Internet
> > Mail's operational infrastructure that works to counter abuse.
> >...
>
> Dave.
>
> However, it seems to me that, for anything that is proposed to
> be a normal standards track document, the community necessarily
> ought to be able to take at least one whack at it on IETF LC.
>

+1



> That "one whack" principle suggests that one cannot say "this
> was developed and deployed elsewhere and is being published as
> Experimental" (which is what, IIR, was one thing that happened
> in the discussion of 4408) and then say "now the design quality
> of SPF is not a relevant consideration because it has been
> considered elsewhere and widely deployed".


That is something that seems to me to happen rather a lot. When I made
private comments on the CBOR draft I was told that the authors felt free to
ignore them because they were not engaged in an official IETF standards
action. Then when I complained about the Proposed Standard status I was
told that I was being rude for implying improper use of process.

My view is that if an AD is going to sponsor an individual submission as
standards track then this should be because the issue involved is of such
narrow interest that only the individual submitter and a few others are
interested in that type of proposal.


> If the IETF doesn't
> get a chance to evaluate design quality and even, if
> appropriate, to consider the tradeoffs between letting a
> possibly-odious specification be standardized and causing a fork
> between deployed-SPF and IETF-SPF, then the IETF's statements
> about what its standards mean become meaningless (at least in
> this particular type of case).
>

I think that is a fair point but I don't think it is a fair
characterization of the nature of the design objections being raised at the
time which were:

1) 'Policy is hard so we should't do it'
2) Receivers must not infringe the rights of email senders

I don't have a lot of tolerance for either objection. The first in
particular led me to tell several people that if they don't consider
themselves competent to solve a problem won't they kindly shut up and leave
it to the people who do.

But the outcome of the objections was that whether with justification or
not, it was decided that these are objections that would be fully answered
by running code. SPF was deployed and it works pretty much as the creators
expected. And one of the reasons it was a good idea to get SPF dispatched
quickly as Experimental was so that the rest of us could concentrate on
DKIM.


I think it is entirely reasonable to demand that when the IETF assists
parties trying to deploy a proposal by endorsing it as a Proposed Standard
then there should be an IETF consensus that the design is good. But that
isn't the case here. Meng and co achieved deployment of their scheme
without IETF endorsement.

So what the IETF is now being asked to do is to recognize the fact that if
you want to send email reliably on the Internet then you had better
configure your systems for SPF and/or DKIM.


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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Aug 29, 2013 at 12:31 PM, John C Klensin <span dir=3D"ltr">=
&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.co=
m</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
--On Wednesday, August 28, 2013 07:21 -0700 Dave Crocker<br>
<div class=3D"im">&lt;<a href=3D"mailto:dhc@dcrocker.net">dhc@dcrocker.net<=
/a>&gt; wrote:<br>
<br>
&gt;&gt; RFC 5507 primarily raises three concerns about TXT records:<br>
&gt;<br>
&gt; RFC 5507 is irrelevant to consideration of the SPFbis draft.<br>
&gt;<br>
&gt; Really.<br>
&gt;<br>
&gt; RFC 5507 concerns approaches to design. =A0However the SPFbis<br>
&gt; draft is not designing a new capability. =A0It is documenting a<br>
&gt; mechanism that has existed for quite a long time, is very<br>
&gt; widely deployed, and has become an essential part of Internet<br>
&gt; Mail&#39;s operational infrastructure that works to counter abuse.<br>
</div>&gt;...<br>
<br>
Dave.<br><br>
However, it seems to me that, for anything that is proposed to<br>
be a normal standards track document, the community necessarily<br>
ought to be able to take at least one whack at it on IETF LC.<br></blockquo=
te><div><br></div><div>+1</div><div><br></div><div>=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">

That &quot;one whack&quot; principle suggests that one cannot say &quot;thi=
s<br>
was developed and deployed elsewhere and is being published as<br>
Experimental&quot; (which is what, IIR, was one thing that happened<br>
in the discussion of 4408) and then say &quot;now the design quality<br>
of SPF is not a relevant consideration because it has been<br>
considered elsewhere and widely deployed&quot;. =A0</blockquote><div><br></=
div><div>That is something that seems to me to happen rather a lot. When I =
made private comments on the CBOR draft I was told that the authors felt fr=
ee to ignore them because they were not engaged in an official IETF standar=
ds action. Then when I complained about the Proposed Standard status I was =
told that I was being rude for implying improper use of process.</div>
<div><br></div><div>My view is that if an AD is going to sponsor an individ=
ual submission as standards track then this should be because the issue inv=
olved is of such narrow interest that only the individual submitter and a f=
ew others are interested in that type of proposal.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">If the IETF doesn&#39;t<br>
get a chance to evaluate design quality and even, if<br>
appropriate, to consider the tradeoffs between letting a<br>
possibly-odious specification be standardized and causing a fork<br>
between deployed-SPF and IETF-SPF, then the IETF&#39;s statements<br>
about what its standards mean become meaningless (at least in<br>
this particular type of case).<br></blockquote><div><br></div><div>I think =
that is a fair point but I don&#39;t think it is a fair characterization of=
 the nature of the design objections being raised at the time which were:</=
div>
<div><br></div><div>1) &#39;Policy is hard so we should&#39;t do it&#39;</d=
iv><div>2) Receivers must not infringe the rights of email senders</div><di=
v><br></div><div>I don&#39;t have a lot of tolerance for either objection. =
The first in particular led me to tell several people that if they don&#39;=
t consider themselves competent to solve a problem won&#39;t they kindly sh=
ut up and leave it to the people who do.</div>
<div><br></div><div>But the outcome of the objections was that whether with=
 justification or not, it was decided that these are objections that would =
be fully answered by running code. SPF was deployed and it works pretty muc=
h as the creators expected. And one of the reasons it was a good idea to ge=
t SPF dispatched quickly as Experimental was so that the rest of us could c=
oncentrate on DKIM.</div>
<div><br></div><div><br></div><div>I think it is entirely reasonable to dem=
and that when the IETF assists parties trying to deploy a proposal by endor=
sing it as a Proposed Standard then there should be an IETF consensus that =
the design is good. But that isn&#39;t the case here. Meng and co achieved =
deployment of their scheme without IETF endorsement.=A0</div>
<div><br></div><div>So what the IETF is now being asked to do is to recogni=
ze the fact that if you want to send email reliably on the Internet then yo=
u had better configure your systems for SPF and/or DKIM.</div><div><br>
</div></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.co=
m/">http://hallambaker.com/</a><br>
</div></div>

--001a113366bc346d7f04e51eab56--

From glenams@gmail.com  Thu Aug 29 18:16:45 2013
Return-Path: <glenams@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE17021E8051 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 18:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XThk0eikcsxw for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 18:16:45 -0700 (PDT)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 1569011E80D3 for <ietf@ietf.org>; Thu, 29 Aug 2013 18:16:45 -0700 (PDT)
Received: by mail-vc0-f174.google.com with SMTP id gd11so875086vcb.33 for <ietf@ietf.org>; Thu, 29 Aug 2013 18:16:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:message-id:subject:from:to :content-type; bh=RC/yV9pcP0MSXaQqk4eId/hF0UzRnKY5Ez5GoUv2N9Y=; b=X+e9io0di9GIa2JQCxhQYMWvoruD2c8Jpfj9sJ4sD+SgTYvi/AblU7986Pk1JPmI6c sbQA15xlnd4mIpHMr0LlrR3In57J4WKfx6a1SWiLr1LVM0n6hsGz9dW5MjsiZAlPJr5D yRClac3gCY8/HUCbWzoPZmyOeNZ9p67qKuTPXrSTG9fbTZhTfCwA9EFl34Tpy0okDffq uRZvx0qJZmYWEHrzX9xYy5/07VWyvlvWiIlLyD/gfHI9/vE+CiC0Cpoi3avZCTqlIHyH szDDBlE+lAzQeCGOukA7AnoROU+yrbLHB2gYDqf7rWOegFDuC5xXLvtFGT9tkxtQ/3go sn+w==
MIME-Version: 1.0
X-Received: by 10.58.155.68 with SMTP id vu4mr4477126veb.21.1377825404476; Thu, 29 Aug 2013 18:16:44 -0700 (PDT)
Sender: glenams@gmail.com
Received: by 10.59.1.132 with HTTP; Thu, 29 Aug 2013 18:16:44 -0700 (PDT)
Date: Thu, 29 Aug 2013 18:16:44 -0700
X-Google-Sender-Auth: N4aawe8vQ7BbEhQTbp2bwY_LYac
Message-ID: <CABL0ig7fSpoFTDq8yJ_L1Tk=feu9ewnOeC3kHFUDCXDYOM=CYQ@mail.gmail.com>
Subject: Mailman service interruption yesterday
From: Glen <glen@amsl.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
Reply-To: glen@amsl.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, 30 Aug 2013 01:16:45 -0000

Greetings:

This notification is being sent to the general community at the
request of the IAOC.

Yesterday the IETF experienced a 5.5-hour service outage on its
Mailman list processor, beginning at approximately 1530PDT yesterday.

In this failure, Mailman started dropping messages, rather than
bouncing them, as it should have done.  AMS received alerts from IETF
members that mail was not flowing correctly.  Following the initial
alert,  AMS staff logged in to the system, and were able to analyze
the problem and effect resolution.  Mailman service was restored and
verified.

Because of the nature of this outage, AMS was not, unfortunately, able
to recover the lost email messages themselves.  We searched the mail
logs, and sent notifications to all the senders that he was able to
locate in the log during the outage period, asking those individuals
to resend their email messages.

Service has been up and running continuously since 2100PDT yesterday,
and no further outages have been observed.  No other services were
impacted or interrupted during this time.

The point here is that if you sent email messages to IETF lists during
the outage period, they were not processed, and should be resent, to
ensure proper delivery.

I remind everyone that AMS - the IETF Secretariat - is always
reachable at "ietf-action@ietf.org", and I encourage everyone to
contact that address when there are problems.  Emails sent there are
tracked by the IETF's ticketing system, and reach the AMS IETF IT
Staff directly.  If mail itself is the issue, our out-of-band webform
at http://www.ietf.org/contact.html as a backup method of contact.
Note, however, that neither I nor members of my staff are generally on
*this* list, so emails sent to this, the general IETF discussion list,
will only reach us after many delays, if at all.  Please note and keep
a copy of the correct addresses to use to reach us, shown above, if
you need to.

Thank you for your patience during this outage.

Glen Barney
IT Director
AMS (IETF Secretariat)

From sm@resistor.net  Thu Aug 29 18:31:13 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414FB11E815B for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 18:31:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VbfLYFW3cYb6 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 18:31:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9057611E8107 for <ietf@ietf.org>; Thu, 29 Aug 2013 18:31:12 -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 r7U1UuAu002688; Thu, 29 Aug 2013 18:31:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377826261; bh=t/EEL86O99D5dlbQ74zOpFrehUIEJfLyHdCr0Ph7Rik=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZtH0krrFQorNYhJM5sFcnjh0V1qqYeXaTSUyMFEpT59rVdqzWpPD56ElFWGLjpUjT KIiwm+AKIVKl2HR/0wpGcLcS8DSLeOyQkacHDXLgJBXrkptJGMrE/37XenlfPvBd6U TKxDACnUnELaiWdBFcAAzPT1mNwPC7kCJKQyg7nM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377826261; i=@resistor.net; bh=t/EEL86O99D5dlbQ74zOpFrehUIEJfLyHdCr0Ph7Rik=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SdyG25i23/KEHh25PrF1KMTHrHvJ5U9mV6/EoOrWbVKRlRy4upNwcu323uzdoc/Gz 27ppPwtGNerQSdHvOe+MQTgM77TXz7Yo1ZpEGrsvF3zKjtjf1+/e3wIl/ycV9J3kN5 Nf5XtrJbBLXAQ1HKCDDiNrJsV73FykTWzHa35GPE=
Message-Id: <6.2.5.6.2.20130829173539.0cd44070@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 29 Aug 2013 18:29:33 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Mail lost yesterday
In-Reply-To: <7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <6.2.5.6.2.20130829152744.0cd688b0@resistor.net> <17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com> <6.2.5.6.2.20130829163103.0c665800@resistor.net> <7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 30 Aug 2013 01:31:13 -0000

Hello,

Thanks to Bob Hinden for the quick response.  What follows is a 
general comment.

My message was not a report about an operational problem.  It was 
about the lack of a timely notification, and maybe an explanation if 
anyone deems that appropriate, about these problems to the IETF community.

There is question of whether the services are being monitored.  There 
is also the question of the reliability of the services provided to 
the community.  Usage has likely increased since 2007.  I hope that 
the contract has been updated to take all of that into account.

Regards,
-sm


From narten@us.ibm.com  Thu Aug 29 21:53:16 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E093E21E804B for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.371
X-Spam-Level: 
X-Spam-Status: No, score=-109.371 tagged_above=-999 required=5 tests=[AWL=1.228, 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 2LpGXQoS+Ikr for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 21:53:10 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id E79B611E80DE for <ietf@ietf.org>; Thu, 29 Aug 2013 21:53:08 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 30 Aug 2013 00:53:07 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 30 Aug 2013 00:53:05 -0400
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 0EA7E6E8040 for <ietf@ietf.org>; Fri, 30 Aug 2013 00:53:05 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22035.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r7U4r49j18808850 for <ietf@ietf.org>; Fri, 30 Aug 2013 04:53:05 GMT
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 r7U4r4cW014285 for <ietf@ietf.org>; Fri, 30 Aug 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r7U4r489014267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 30 Aug 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r7U4r3s5003051 for <ietf@ietf.org>; Fri, 30 Aug 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r7U4r3fa002998 for ietf@ietf.org; Fri, 30 Aug 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201308300453.r7U4r3fa002998@rotala.raleigh.ibm.com>
Date: Fri, 30 Aug 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13083004-5806-0000-0000-00002295B407
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 04:53:17 -0000

Total of 140 messages in the last 7 days.
 
script run at: Fri Aug 30 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.43% |    9 |  6.04% |    76439 | sm+ietf@elandsys.com
  2.86% |    4 |  7.42% |    93857 | doug.mtview@gmail.com
  4.29% |    6 |  5.58% |    70653 | ron.even.tlv@gmail.com
  4.29% |    6 |  5.11% |    64709 | hallam@gmail.com
  3.57% |    5 |  4.80% |    60784 | abdussalambaryun@gmail.com
  4.29% |    6 |  3.98% |    50359 | hsantos@isdg.net
  4.29% |    6 |  3.42% |    43301 | scott@kitterman.com
  4.29% |    6 |  2.82% |    35654 | sm@resistor.net
  3.57% |    5 |  2.72% |    34437 | johnl@taugh.com
  2.86% |    4 |  3.23% |    40931 | daedulus@btconnect.com
  3.57% |    5 |  2.46% |    31093 | jelte.jansen@sidn.nl
  2.86% |    4 |  2.69% |    34006 | john-ietf@jck.com
  2.86% |    4 |  2.16% |    27383 | ted.lemon@nominum.com
  2.14% |    3 |  2.14% |    27092 | scott.brim@gmail.com
  2.14% |    3 |  2.02% |    25568 | jgunn6@csc.com
  2.14% |    3 |  1.71% |    21592 | bmanning@isi.edu
  2.14% |    3 |  1.62% |    20451 | dhc@dcrocker.net
  1.43% |    2 |  2.13% |    27011 | david.black@emc.com
  1.43% |    2 |  1.52% |    19222 | chris.dearlove@baesystems.com
  1.43% |    2 |  1.46% |    18515 | marka@isc.org
  1.43% |    2 |  1.45% |    18410 | loa@pi.nu
  1.43% |    2 |  1.45% |    18341 | mach.chen@huawei.com
  1.43% |    2 |  1.35% |    17077 | adrian@olddog.co.uk
  1.43% |    2 |  1.27% |    16094 | tjc@ecs.soton.ac.uk
  1.43% |    2 |  1.20% |    15192 | jordi.palet@consulintel.es
  1.43% |    2 |  1.18% |    14974 | presnick@qti.qualcomm.com
  1.43% |    2 |  1.13% |    14252 | bob.hinden@gmail.com
  0.71% |    1 |  1.37% |    17324 | jouni.nospam@gmail.com
  0.71% |    1 |  1.31% |    16603 | ben@nostrum.com
  0.71% |    1 |  1.26% |    15924 | michelle.cotton@icann.org
  0.71% |    1 |  1.08% |    13725 | spromano@unina.it
  0.71% |    1 |  0.91% |    11534 | mary.h.barnes@gmail.com
  0.71% |    1 |  0.90% |    11408 | emcmurry@computer.org
  0.71% |    1 |  0.90% |    11372 | bernard_aboba@hotmail.com
  0.71% |    1 |  0.89% |    11255 | narten@us.ibm.com
  0.71% |    1 |  0.85% |    10702 | paf@frobbit.se
  0.71% |    1 |  0.83% |    10452 | erosen@cisco.com
  0.71% |    1 |  0.70% |     8837 | sanjay.mishra@verizon.com
  0.71% |    1 |  0.69% |     8769 | hadriel.kaplan@oracle.com
  0.71% |    1 |  0.69% |     8741 | sgundave@cisco.com
  0.71% |    1 |  0.66% |     8347 | aallen@blackberry.com
  0.71% |    1 |  0.65% |     8235 | shem_waw@operamail.com
  0.71% |    1 |  0.64% |     8038 | dean.willis@softarmor.com
  0.71% |    1 |  0.62% |     7837 | ietf2dave@davearonson.com
  0.71% |    1 |  0.61% |     7772 | dave@cridland.net
  0.71% |    1 |  0.60% |     7554 | brian.e.carpenter@gmail.com
  0.71% |    1 |  0.60% |     7541 | superuser@gmail.com
  0.71% |    1 |  0.59% |     7523 | jari.arkko@piuha.net
  0.71% |    1 |  0.56% |     7027 | jabley@hopcount.ca
  0.71% |    1 |  0.55% |     7016 | cjbc@it.uc3m.es
  0.71% |    1 |  0.55% |     6988 | glen@amsl.com
  0.71% |    1 |  0.55% |     6959 | bmanning@vacation.karoshi.com
  0.71% |    1 |  0.53% |     6701 | cabo@tzi.org
  0.71% |    1 |  0.52% |     6598 | rpelletier@isoc.org
  0.71% |    1 |  0.52% |     6563 | l.wood@surrey.ac.uk
  0.71% |    1 |  0.51% |     6516 | arturo.servin@gmail.com
  0.71% |    1 |  0.51% |     6490 | damascene.joachimpillai@verizon.com
  0.71% |    1 |  0.51% |     6398 | mcr+ietf@sandelman.ca
  0.71% |    1 |  0.50% |     6389 | randy_presuhn@mindspring.com
  0.71% |    1 |  0.48% |     6099 | melinda.shore@gmail.com
  0.71% |    1 |  0.48% |     6070 | barryleiba@computer.org
  0.71% |    1 |  0.46% |     5880 | stpeter@stpeter.im
  0.71% |    1 |  0.46% |     5861 | swmike@swm.pp.se
  0.71% |    1 |  0.46% |     5798 | john@jlc.net
  0.71% |    1 |  0.41% |     5152 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |  140 |100.00% |  1265395 | Total


From peter@akayla.com  Thu Aug 29 23:20:58 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAD3F21F9E54; Thu, 29 Aug 2013 23:20:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5HoVmoz9f2j; Thu, 29 Aug 2013 23:20:54 -0700 (PDT)
Received: from p3plsmtpa07-09.prod.phx3.secureserver.net (p3plsmtpa07-09.prod.phx3.secureserver.net [173.201.192.238]) by ietfa.amsl.com (Postfix) with ESMTP id EE44121F9F13; Thu, 29 Aug 2013 23:20:53 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-09.prod.phx3.secureserver.net with  id JuLr1m00H1huGat01uLr4F; Thu, 29 Aug 2013 23:20:53 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-repute-media-type.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-repute-media-type-10
Date: Thu, 29 Aug 2013 23:21:12 -0700
Message-ID: <01f201cea549$20f84420$62e8cc60$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6lRc04j9eLeFbcRyehsozJ+8Ayhw==
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: Fri, 30 Aug 2013 06:20:58 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-repute-media-type-10
Reviewer: Peter Yee
Review Date: August-27-2013
IETF LC End Date: August-29-2013
IESG Telechat date: September-12-2013

Summary: This draft is on the right track but has open issues, described in
the review. [Ready with minor issues.]

This draft directs IANA to register an application/reputon+json media type.
It also defines a new IANA registry for reputation application-specific uses
of that media type.

Major issues:

Minor issues:

Authenticity and confidence ratings seem to be used interchangeably in the
document.  Authenticity is never defined, but it appears that it may
previously have been used in place of confidence.  The example spanning
pages 9 and 10 notes a confidence of 95% but uses that for the (undefined in
the document) authenticity value instead of the confidence value.  Either
define authenticity (which is absent in Section 3.1) or switch to
confidence.

Section 3.1, definition of rater: the wording of this definition could be
interpreted to mean either the party that is returning the rating
information in response to the query but which is not necessarily the party
creating the rating, or it could mean the party that created the rating.
This may go back to the muddled concept of authenticity (which seems to be
used to mean how much an unspecified "someone" believes that the rating
originated with the named rater) vs. confidence (how confident the rater is
in the rating).  This definition should be cleared up to remove the
ambiguity that floats throughout the document.

Nits:

Page 3, Section 3, 1st paragraph, 1st sentence: change "representaton" to
"representation".  Change "Javascript" to "JavaScript".

Page 3, Section 3, 1st paragraph, 3rd sentence: delete the 3rd occurrence of
"context".

Page 5, Section 4, 2nd paragraph, 2nd sentence: after "given" is there a
missing "application" or "query"?

Page 6, 1st paragraph, 1st sentence: change "specificaiton" to
"specification".

Page 7, definition of "auth-value": What is this??

Page 7, definition of ext-value, 1st comment: I think "specific syntax is
specified in specific  application" lacks specificity. ;-)

Page 8, Section 6.2, 1st sentence after 1st example: who is "we", Kemo Sabe?
This seems to imply a rater who is rating the rater.  There's also the
aforementioned issue of what authenticity means vs. confidence.

Page 9, 2nd paragraph after the example: change "an" to "a".

Page 9, 3rd paragraph after the example, 1st sentence: change " idenfities"
to "identifies".


		-Peter Yee




From jari.arkko@piuha.net  Fri Aug 30 01:05:11 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F0F221E80B0 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 01:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1m1WFr1f23b5 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 01:05:06 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4823121F9E00 for <ietf@ietf.org>; Fri, 30 Aug 2013 01:05:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3DC832CC48; Fri, 30 Aug 2013 11:05:03 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yq87CzuugF2u; Fri, 30 Aug 2013 11:05:02 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 934992CC46; Fri, 30 Aug 2013 11:05:02 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Mail lost yesterday
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20130829173539.0cd44070@resistor.net>
Date: Fri, 30 Aug 2013 11:05:03 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <6.2.5.6.2.20130829152744.0cd688b0@resistor.net> <17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com> <6.2.5.6.2.20130829163103.0c665800@resistor.net> <7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com> <6.2.5.6.2.20130829173539.0cd44070@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1508)
Cc: 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, 30 Aug 2013 08:05:11 -0000

SM:

I certainly agree that in incidents like this, a timely notification is =
in order. (Of course to the extent that the outage itself allows us to =
do that. Sometimes the outage or the queue that has built up during the =
outage delays sending a notification.)

And we normally do send notifications; in this case circumstances (such =
as people being out sick) conspired to delay sending the notification =
out. But it did eventually go out, and I'd like to thank Glen, Steve, =
and the team for dealing with the issue and restoring the service. Based =
on this experience, we should be able to make notifications faster on =
future incidents.

Also, I wanted to bring up a point about what to do if you see a =
problem. Glen already mentioned ietf-action@ietf.org. This is what you =
should normally use, if you see a problem. There has been a couple of =
incidents where this address would not have worked, such as when the =
entire connectivity to the IETF system is down. Obviously, the IAOC and =
AMS have worked hard to make sure this does not happen, and we are about =
to make another update soon that will significantly reduce the risk of =
site-wide problems. We think it would have prevented yesterday's =
problem, too. But should you find a situation where the IETF site is =
unreachable, IAOC and IESG members have a way to alert the staff. Please =
contact your nearest IESG/IAOC member to bring the issue to their =
attention. For instance, you can contact me at this e-mail address or =
jariarkko@jabber.org/jari.arkko@gmail.com with instant messaging. And =
since we are spread around the world, we often have noticed the problem =
already. In yesterday's incident, Pete Resnick noticed the problem and =
contacted AMS - thanks Pete!=20

Jari


From mary.h.barnes@gmail.com  Fri Aug 30 06:17:09 2013
Return-Path: <mary.h.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 35BF711E810C for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 06:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, 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 C-sQUGNpoo1c for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 06:17:08 -0700 (PDT)
Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [IPv6:2607:f8b0:400c:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2363621F9C4F for <ietf@ietf.org>; Fri, 30 Aug 2013 06:17:08 -0700 (PDT)
Received: by mail-vb0-f42.google.com with SMTP id e12so1270506vbg.15 for <ietf@ietf.org>; Fri, 30 Aug 2013 06:17: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=OMaL0T1RzNhFH2BnKJBPTirDwIsuFi0fFbI5EEv/j2g=; b=XmmxMGFzo983BNjYb1CxU8ikZO7vxV5b5dLJS2QqvRgfxNUT+WZJqDSw7LHMK4EK13 UZyjGgLXBhGfRvgm3gF+zncC7PlyWahoNRG9seaGev/STLauNkIHUF6c8aYhAQvUuOMl wEDoOhGJ7mpE/fz2AXvhFFpTCrBzYMUW8W1M3iBq+xyPPmbf7MSOCbQhdZhLMYQJ1J0f CVFGWWmgbYHOu6cyLY9XfSbm0xvu81ykL+N04n7DhQmCE9yU3jdn4chgGxS2J5t0XMnh DgOzrLGdRZMgL3xWHZq5Gvm/HERF/1aNIDSi6OqFKnqy9IlMmv5O44osEUg+JSK08etc 78UQ==
MIME-Version: 1.0
X-Received: by 10.58.119.233 with SMTP id kx9mr8266932veb.3.1377868626374; Fri, 30 Aug 2013 06:17:06 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Fri, 30 Aug 2013 06:17:06 -0700 (PDT)
In-Reply-To: <EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <6.2.5.6.2.20130829152744.0cd688b0@resistor.net> <17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com> <6.2.5.6.2.20130829163103.0c665800@resistor.net> <7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com> <6.2.5.6.2.20130829173539.0cd44070@resistor.net> <EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net>
Date: Fri, 30 Aug 2013 08:17:06 -0500
Message-ID: <CABmDk8ms5qVR+iV6gEN9Fck2Ez8+3hUoUtKp0deYnvSy9WboRw@mail.gmail.com>
Subject: Re: Mail lost yesterday
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11c391be05d64904e52a0a05
Cc: SM <sm@resistor.net>, Bob Hinden <bob.hinden@gmail.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 13:17:09 -0000

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

I will also add that when I requested it Steve sent me a list that
indicated who sent what messages to the mailing lists that I moderate. That
was really helpful as I could ping folks to resend and I was able to resend
those that I had sent myself, so it wasn't too onerous to recover given
that we also had the time window for the lost messages.

Regards,
Mary.


On Fri, Aug 30, 2013 at 3:05 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> SM:
>
> I certainly agree that in incidents like this, a timely notification is in
> order. (Of course to the extent that the outage itself allows us to do
> that. Sometimes the outage or the queue that has built up during the outage
> delays sending a notification.)
>
> And we normally do send notifications; in this case circumstances (such as
> people being out sick) conspired to delay sending the notification out. But
> it did eventually go out, and I'd like to thank Glen, Steve, and the team
> for dealing with the issue and restoring the service. Based on this
> experience, we should be able to make notifications faster on future
> incidents.
>
> Also, I wanted to bring up a point about what to do if you see a problem.
> Glen already mentioned ietf-action@ietf.org. This is what you should
> normally use, if you see a problem. There has been a couple of incidents
> where this address would not have worked, such as when the entire
> connectivity to the IETF system is down. Obviously, the IAOC and AMS have
> worked hard to make sure this does not happen, and we are about to make
> another update soon that will significantly reduce the risk of site-wide
> problems. We think it would have prevented yesterday's problem, too. But
> should you find a situation where the IETF site is unreachable, IAOC and
> IESG members have a way to alert the staff. Please contact your nearest
> IESG/IAOC member to bring the issue to their attention. For instance, you
> can contact me at this e-mail address or
> jariarkko@jabber.org/jari.arkko@gmail.com with instant messaging. And
> since we are spread around the world, we often have noticed the problem
> already. In yesterday's incident, Pete Resnick noticed the problem and
> contacted AMS - thanks Pete!
>
> Jari
>
>

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

<div dir=3D"ltr">I will also add that when I requested it Steve sent me a l=
ist that indicated who sent what messages to the mailing lists that I moder=
ate. That was really helpful as I could ping folks to resend and I was able=
 to resend those that I had sent myself, so it wasn&#39;t too onerous to re=
cover given that we also had the time window for the lost messages.<div>
<br></div><div>Regards,</div><div>Mary.=A0</div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Fri, Aug 30, 2013 at 3:05 AM, J=
ari Arkko <span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" tar=
get=3D"_blank">jari.arkko@piuha.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">SM:<br>
<br>
I certainly agree that in incidents like this, a timely notification is in =
order. (Of course to the extent that the outage itself allows us to do that=
. Sometimes the outage or the queue that has built up during the outage del=
ays sending a notification.)<br>

<br>
And we normally do send notifications; in this case circumstances (such as =
people being out sick) conspired to delay sending the notification out. But=
 it did eventually go out, and I&#39;d like to thank Glen, Steve, and the t=
eam for dealing with the issue and restoring the service. Based on this exp=
erience, we should be able to make notifications faster on future incidents=
.<br>

<br>
Also, I wanted to bring up a point about what to do if you see a problem. G=
len already mentioned <a href=3D"mailto:ietf-action@ietf.org">ietf-action@i=
etf.org</a>. This is what you should normally use, if you see a problem. Th=
ere has been a couple of incidents where this address would not have worked=
, such as when the entire connectivity to the IETF system is down. Obviousl=
y, the IAOC and AMS have worked hard to make sure this does not happen, and=
 we are about to make another update soon that will significantly reduce th=
e risk of site-wide problems. We think it would have prevented yesterday&#3=
9;s problem, too. But should you find a situation where the IETF site is un=
reachable, IAOC and IESG members have a way to alert the staff. Please cont=
act your nearest IESG/IAOC member to bring the issue to their attention. Fo=
r instance, you can contact me at this e-mail address or <a href=3D"http://=
jariarkko@jabber.org/jari.arkko@gmail.com" target=3D"_blank">jariarkko@jabb=
er.org/jari.arkko@gmail.com</a> with instant messaging. And since we are sp=
read around the world, we often have noticed the problem already. In yester=
day&#39;s incident, Pete Resnick noticed the problem and contacted AMS - th=
anks Pete!<br>

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

--001a11c391be05d64904e52a0a05--

From john-ietf@jck.com  Fri Aug 30 06:36:01 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF63911E8179 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 06:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W+NsT720f873 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 06:35:56 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3288821F830F for <ietf@ietf.org>; Fri, 30 Aug 2013 06:35:56 -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 1VFOrj-000JrA-RE for ietf@ietf.org; Fri, 30 Aug 2013 09:35:55 -0400
Date: Fri, 30 Aug 2013 09:35:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: An IANA Registry for DNS TXT RDATA  (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Message-ID: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 13:36:01 -0000

Hi.

Inspired by part of the SPF discussion but separate from it,
Patrik, Andrew, and I discovered a shortage of registries for
assorted DNS RDATA elements.  We have posted a draft to
establish one for TXT RDATA.  If this requires significant
discussion, we seek guidance from relevant ADs as to where they
would like that discussion to occur.

Three notes:

* As the draft indicates, while RFC 5507 and other documents
explain why subtypes are usually a bad idea, the registry
definition tries to be fairly neutral on the subject -- the idea
is to identify and register what is being done, not to pass
judgment. 

* While the use of special labels (in the language of 5507,
prefixes and suffixes) mitigates many of the issues with
specialized use of RDATA fields, they do not eliminate the
desirability of a registry (especially for debugging and
analysis purposes).

* While examining the DNS-related registries that exist today,
we discovered that some other registries seemed to be missing
and that the organization of the registries seemed to be
sub-optimal.  We considered attempting a "fix everything" I-D,
but concluded that the TXT RDATA registry was the most important
need and that it would be unwise to get its establishment bogged
down with other issue.  The I-D now contains a temporary
appendix that outlines the other issues we identified.  IMO,
thinking through the issues in that appendix, generating the
relevant I-D(s), and moving them through the system would be a
good exercise for someone who has little experience in the IETF
and who is interested in IANA registries and/or DNS details.  I
am unlikely to find time to do the work myself but would be
happy to work with a volunteer on pulling things together.

    best,
      john


---------- Forwarded Message ----------
Date: Friday, August 30, 2013 05:52 -0700
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-klensin-iana-txt-rr-registry-00.txt


A New Internet-Draft is available from the on-line
Internet-Drafts directories.


	Title           : An IANA Registry for Protocol Uses of Data
with the DNS TXT RRTYPE 	Author(s)       : John C Klensin
                          Andrew Sullivan
                          Patrik Faltstrom
	Filename        : draft-klensin-iana-txt-rr-registry-00.txt
	Pages           : 8
	Date            : 2013-08-30

Abstract:
   Some protocols use the RDATA field of the DNS TXT RRTYPE for
holding    data to be parsed, rather than for unstructured free
text.  This    document specifies the creation of an IANA
registry for protocol-    specific structured data to minimize
the risk of conflicting or    inconsistent uses of that RRTYPE
and data field.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-klensin-iana-txt-rr-registry

[...]

From hallam@gmail.com  Fri Aug 30 07:16:48 2013
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 9BFCD21E80D4 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 07:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.53
X-Spam-Level: 
X-Spam-Status: No, score=-2.53 tagged_above=-999 required=5 tests=[AWL=0.069,  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 7pO5iSWiQtKN for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 07:16:47 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 58A4C11E8128 for <ietf@ietf.org>; Fri, 30 Aug 2013 07:16:47 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id eo20so1555682lab.20 for <ietf@ietf.org>; Fri, 30 Aug 2013 07:16:46 -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=ZcAq2tsR32sZKaT9V2WK5ViRV51kuMqmDJ8Cu+RNngM=; b=FRYtjpiiTAt4rUM4tfe4aczOyBEjt1QDGaBtkDpMXoF2wdUyXwQW4lx2g8E6lEJMZJ VgJfD9vviyTXCVBvvU9zqjLpPAPxnQg4UuxHdjDh2SjhnRNaDGR4Z60rCn4HBOV4YkZn xIMPtrCJC2wUj97aIYNniw3YPCASwXbokO346spr0Jtn7acxejy56Bm2HKd8XW6CDZWc VaaAcy9JAYZebRHMLZlb5UddqLcY0EYZlKRA2C4jmuZXdq1oMvhqDAH/wDBhLhs/973m FRb68gj0qZhEOpO1ftVMzejSJZ7kpUF9Z+IzVsUomfNyAQvGv2oL0KcbppCJ+A7nmPSq QWqA==
MIME-Version: 1.0
X-Received: by 10.112.141.98 with SMTP id rn2mr856450lbb.49.1377872206185; Fri, 30 Aug 2013 07:16:46 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Fri, 30 Aug 2013 07:16:46 -0700 (PDT)
In-Reply-To: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com>
Date: Fri, 30 Aug 2013 10:16:46 -0400
Message-ID: <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com>
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c34460654cac04e52adfc6
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, 30 Aug 2013 14:16:48 -0000

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

On Fri, Aug 30, 2013 at 9:35 AM, John C Klensin <john-ietf@jck.com> wrote:

> Hi.
>
> Inspired by part of the SPF discussion but separate from it,
> Patrik, Andrew, and I discovered a shortage of registries for
> assorted DNS RDATA elements.  We have posted a draft to
> establish one for TXT RDATA.  If this requires significant
> discussion, we seek guidance from relevant ADs as to where they
> would like that discussion to occur.
>
> Three notes:
>
> * As the draft indicates, while RFC 5507 and other documents
> explain why subtypes are usually a bad idea, the registry
> definition tries to be fairly neutral on the subject -- the idea
> is to identify and register what is being done, not to pass
> judgment
>

RFC 5507 does indeed say that but it is an IAB document, not an IETF
consensus document and it is wrong.

The document was written by authors who wanted to promote the notion that
the DNS should accept deployment of new RR types and to do otherwise is a
standards violation. So it makes claims about some subtyping strategies
that are wildly inaccurate.

Prefixing works fine unless you need to use wildcards. What the draft does
not mention is that it is easy to fix the wildcarding problem. (see XPTR).


The consequence of this is that we still don't seem to have a registry for
DNS prefixes, or at least not in the place I expect it which is

Domain Name System (DNS) Parameters


Instead we have a bunch of registries that are protocol specific. Which
when the prefixes are from a common namespace is borked.

The IANA should be tracking SRV prefix allocations and DNSEXT seems to have
discussed numerous proposals. I have written some myself. But I can't find
evidence of one and we certainly have not updated SRV etc. to state that
the registry should be used.


Fixing TXT is optional, fixing the use of prefixes and having a proper
registry that is first come first served is essential. Right now we have
thousands of undocumented ad-hoc definitions.

This task has to be taken away from people who think cutting a new RR is
always the answer. It isn't. We are going to have hundreds of thousands of
Web Services and the DNS RR space is a 16 bit number.

Service discovery requires prefixes.

Here is a draft that works fine (except for the IETF review mistake). Just
put IETF last call on it:

http://tools.ietf.org/html/draft-gudmundsson-dns-srv-iana-registry-04



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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 30, 2013 at 9:35 AM, John C Klensin <span dir=3D"ltr">&=
lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi.<br>
<br>
Inspired by part of the SPF discussion but separate from it,<br>
Patrik, Andrew, and I discovered a shortage of registries for<br>
assorted DNS RDATA elements. =A0We have posted a draft to<br>
establish one for TXT RDATA. =A0If this requires significant<br>
discussion, we seek guidance from relevant ADs as to where they<br>
would like that discussion to occur.<br>
<br>
Three notes:<br>
<br>
* As the draft indicates, while RFC 5507 and other documents<br>
explain why subtypes are usually a bad idea, the registry<br>
definition tries to be fairly neutral on the subject -- the idea<br>
is to identify and register what is being done, not to pass<br>
judgment<br></blockquote><div><br></div><div>RFC 5507 does indeed say that =
but it is an IAB document, not an IETF consensus document and it is wrong.<=
/div><div><br></div><div>The document was written by authors who wanted to =
promote the notion that the DNS should accept deployment of new RR types an=
d to do otherwise is a standards violation. So it makes claims about some s=
ubtyping strategies that are wildly inaccurate.</div>
<div><br></div><div>Prefixing works fine unless you need to use wildcards. =
What the draft does not mention is that it is easy to fix the wildcarding p=
roblem. (see XPTR).</div><div><br></div><div><br></div><div>The consequence=
 of this is that we still don&#39;t seem to have a registry for DNS prefixe=
s, or at least not in the place I expect it which is</div>
<div><br></div><div><span style=3D"color:rgb(51,51,51);font-family:&#39;Ope=
n Sans&#39;,&#39;Helvetica Neue&#39;,Helvetica,Arial,sans-serif;font-size:1=
3px;font-weight:bold">Domain Name System (DNS) Parameters</span></div><div>
<br></div><div><br></div><div>Instead we have a bunch of registries that ar=
e protocol specific. Which when the prefixes are from a common namespace is=
 borked.=A0</div><div><br></div><div>The IANA should be tracking SRV prefix=
 allocations and DNSEXT seems to have discussed numerous proposals. I have =
written some myself. But I can&#39;t find evidence of one and we certainly =
have not updated SRV etc. to state that the registry should be used.</div>
<div><br></div><div><br></div><div>Fixing TXT is optional, fixing the use o=
f prefixes and having a proper registry that is first come first served is =
essential. Right now we have thousands of undocumented ad-hoc definitions.<=
/div>
<div><br></div><div>This task has to be taken away from people who think cu=
tting a new RR is always the answer. It isn&#39;t. We are going to have hun=
dreds of thousands of Web Services and the DNS RR space is a 16 bit number.=
</div>
<div><br></div><div>Service discovery requires prefixes.=A0</div><div><br><=
/div><div>Here is a draft that works fine (except for the IETF review mista=
ke). Just put IETF last call on it:</div><div><br></div><div><a href=3D"htt=
p://tools.ietf.org/html/draft-gudmundsson-dns-srv-iana-registry-04">http://=
tools.ietf.org/html/draft-gudmundsson-dns-srv-iana-registry-04</a><br>
</div><div><br></div><div><br></div><div><br></div></div>-- <br>Website: <a=
 href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c34460654cac04e52adfc6--

From sm@resistor.net  Fri Aug 30 07:28:38 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDF1511E81A7 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 07:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULInlALAvOAZ for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 07:28:38 -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 3453911E81A1 for <ietf@ietf.org>; Fri, 30 Aug 2013 07:28:37 -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 r7UESNis022453; Fri, 30 Aug 2013 07:28:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377872909; bh=3lZbQSXwF+7z161PhYprSXza8uvzEml7WFxMtnFtlnc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y78kaK8aBA5+cHOWp482rDNujTiBF8fnD6DGvvWlPKH5H85UPiQ1DWuFzIinOyb08 WLGDrM48d5uTHohL2Ke6MKE5CU7c26wRuuaCjW9ipVHk0hBPee5O2N9H1TVGhgnHyW X29e4XhXSmo6NBKEvKFNUGBhNuGBPIU5m9ZH1My4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1377872909; i=@resistor.net; bh=3lZbQSXwF+7z161PhYprSXza8uvzEml7WFxMtnFtlnc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uwB8Crrse3XzdI9w9qO5ryer1xOiVCt/fPu1IkWmQLVQFuno0y05ItR0GSw9QQh8o JoPXKs2CMLPrP1LJP/MVQU6lsC5OzYA+begcdLj5fX7uLiXQugSMKDU05g+QOln2WL 7NTfixHEtVCbR5emk4BUc8tnIKrSkIBLTKyvPmfQ=
Message-Id: <6.2.5.6.2.20130830053743.0c9031d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Aug 2013 07:26:50 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: SM <sm@resistor.net>
Subject: Re: Mail lost yesterday
In-Reply-To: <EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <6.2.5.6.2.20130829152744.0cd688b0@resistor.net> <17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com> <6.2.5.6.2.20130829163103.0c665800@resistor.net> <7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com> <6.2.5.6.2.20130829173539.0cd44070@resistor.net> <EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 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, 30 Aug 2013 14:28:39 -0000

Hi Jari,
At 01:05 30-08-2013, Jari Arkko wrote:
>I certainly agree that in incidents like this, a timely notification 
>is in order. (Of course to the extent that the outage itself allows 
>us to do that. Sometimes the outage or the queue that has built up 
>during the outage delays sending a notification.)

I'll refrain from commenting about the details of the last incident 
as there are extenuating circumstances.

My message was not about the contact address to report operational 
issues.  For what it is worth I did notice an issue with the mail 
archives but I didn't think that it was worth pursuing as my message 
was off-topic.  I read ietf-announce; there wasn't any notification 
there.  I assumed that there was either something wrong on my end or 
it could be some glitch which was not worth the bother.

IASA stated that:

  "The IASA defines the service requirements (statement of work, service
   level agreement)"

That information is not publicly available.

The message you wrote does not say anything about monitoring.  The 
practical question is whether IETF services are being 
monitored.  This is where the IETF "leadership" answers yes and I 
look unreasonable for asking more questions.  On a lighter note I 
have been watching too many IETF movies. :-)

The nit is why is the IETF still using PDT.

Regards,
-sm 


From cyrus@daboo.name  Fri Aug 30 07:38:42 2013
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA15811E8111 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 07:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEPh5N75S3sm for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 07:38:37 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0E13011E8103 for <ietf@ietf.org>; Fri, 30 Aug 2013 07:38:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 6537F4A4CAD6; Fri, 30 Aug 2013 10:38:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjyQhekBCUOl; Fri, 30 Aug 2013 10:38:33 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 866C94A4CACB; Fri, 30 Aug 2013 10:38:32 -0400 (EDT)
Date: Fri, 30 Aug 2013 10:38:31 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Phillip Hallam-Baker <hallam@gmail.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Message-ID: <3B833B3E8A7BD501E72E1C85@caldav.corp.apple.com>
In-Reply-To: <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=629
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, 30 Aug 2013 14:38:43 -0000

Hi Phillip,

--On August 30, 2013 at 10:16:46 AM -0400 Phillip Hallam-Baker 
<hallam@gmail.com> wrote:

> Service discovery requires prefixes.
>
> Here is a draft that works fine (except for the IETF review mistake). Just
> put IETF last call on it:
>
> http://tools.ietf.org/html/draft-gudmundsson-dns-srv-iana-registry-04

I believe that draft was superseded by RFC6335 and all service names (SRV 
prefix labels) are now recorded at 
<http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml> 
- indeed several of those come from RFCs I have written that add new SRV 
names.

-- 
Cyrus Daboo


From tony@att.com  Fri Aug 30 07:47:36 2013
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 1C78511E8179; Fri, 30 Aug 2013 07:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.34
X-Spam-Level: 
X-Spam-Status: No, score=-106.34 tagged_above=-999 required=5 tests=[AWL=0.258, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4H3jgeBRkF+Z; Fri, 30 Aug 2013 07:47:30 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id BA07E11E8111; Fri, 30 Aug 2013 07:47:21 -0700 (PDT)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 970b0225.0.3942764.00-368.10858105.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>);  Fri, 30 Aug 2013 14:47:23 +0000 (UTC)
X-MXL-Hash: 5220b07b0df8664b-98ef9d4eda90721d7ba5dc589117ddfb11a0ae0c
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UElKFn020732; Fri, 30 Aug 2013 10:47:21 -0400
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UEl8jA020513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Aug 2013 10:47:16 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi132.aldc.att.com (RSA Interceptor); Fri, 30 Aug 2013 14:46:55 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UEktvQ012523; Fri, 30 Aug 2013 10:46:55 -0400
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UEkmLl012277; Fri, 30 Aug 2013 10:46:48 -0400
Received: from [135.70.72.203] (vpn-135-70-72-203.vpn.swst.att.com[135.70.72.203]) by maillennium.att.com (mailgw1) with ESMTP id <20130830144646gw1004nhace> (Authid: tony); Fri, 30 Aug 2013 14:46:47 +0000
X-Originating-IP: [135.70.72.203]
Message-ID: <5220B055.2000704@att.com>
Date: Fri, 30 Aug 2013 10:46:45 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>, General discussion of application-layer protocols <apps-discuss@ietf.org>,  draft-ietf-repute-model.all@tools.ietf.org
Subject: AppsDir review of draft-ietf-repute-model-08
X-Enigmail-Version: 1.5.2
Content-Type: multipart/alternative; boundary="------------060402010505070101090409"
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.229.23]
X-AnalysisOut: [v=2.0 cv=EZl/toaC c=1 sm=0 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=x8D5cakk9fsA:10 a=sCfsyOEanakA:10 a=409FU5KnOX8A:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=1ndyL1IG]
X-AnalysisOut: [x4cA:10 a=48vgC7mUAAAA:8 a=uU-FClygtGCEoXK0zUUA:9 a=wPNLvf]
X-AnalysisOut: [GTeEIA:10 a=_W_S_7VecoQA:10 a=lGDGW7yqLC3wcVEe:21]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 14:47:36 -0000

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

I have been selected as the Applications Area Directorate reviewer for this draft (for background on appsdir, please see http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate).

Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft.



Document:  draft-ietf-repute-model-08
Title: A Model for Reputation Reporting

Reviewer: Tony Hansen
Review Date: 2013-08-29
IESG Telechat Date: 9/12
IETF Last Call Expires: LC for 07 expired on 2013-08-29, but 08 superseded that


Summary:
The document is ready for publication. Minor notes follow that can be fixed in AUTH48.

The document describes a model for reputation services, particularly those being produced by the Repute WG. It follows the recommendations of RFc4101 for describing a protocol model, which requires answers to 1) the problem the protocol is trying to achieve, 2) the meaning of messages transmitted, and 3) important unobvious features of the protocol. This document accomplishes its goals quite well.



==== ORGANIZATIONAL COMMENT ====

Section 3 "High-Level Architecture" starts with an extended example of where a reputation service would fit into an existing service. Finally, more than a page later, it starts describing the architecture that is supposed to be the topic of this section. I suggest that the section be split into two, with the beginning given the heading along the lines of "Example of a Reputation Service Being Used", and the "High-Level Architecture" heading moved right before the paragraph that starts "This document outlines". Alternatively, add subsection titles.


 
==== MINOR NITS ====

Changes below are marked with >>><<<.

==== Section 1, paragraph 5 starting with "A full trust"

I think this sentence would read better as follows, both for readability and to match the style of the surrounding sentences:

OLD: Some need only produce a basic rating, while others need to provide
OLD: underlying detail.

NEW: Some need >>to<< only produce a basic rating, while others need to provide
NEW: >>the<< underlying detail.

==== Section 2, paragraph 1 starting with "The basic premise"

I think this sentence would read better with the introduction some additional punctuation.

OLD: Typically client and service operators enter into
OLD: some kind of agreement during which some parameters are exchanged
OLD: such as the location at which the reputation service can be reached,
OLD: the nature of the reputation data being offered, possibly some client
OLD: authentication details, and the like.

NEW: Typically client and service operators enter into
NEW: some kind of agreement during which some parameters are exchanged>>>,<<<
NEW: such as>>>:<<< the location at which the reputation service can be reached,
NEW: the nature of the reputation data being offered, possibly some client
NEW: authentication details, and the like.

==== Section 3, paragraph 5 starting with "It provides"

I think there is a typo in this sentence and the word "one" should be "done".

OLD: (Although not typically thought of as a 'transport', the DNS
OLD: provides generic capabilities and can be thought of as a mechanism
OLD: for transporting queries and responses that have nothing to do with
OLD: Internet addresses, such as is one with a DNS BlockList [DNSBL <http://tools.ietf.org/html/draft-ietf-repute-model-08#ref-DNSBL>].)

NEW: (Although not typically thought of as a 'transport', the DNS
NEW: provides generic capabilities and can be thought of as a mechanism
NEW: for transporting queries and responses that have nothing to do with
NEW: Internet addresses, such as is >>>done<<< with a DNS BlockList [DNSBL <http://tools.ietf.org/html/draft-ietf-repute-model-08#ref-DNSBL>].)

==== Section 4.1, paragraph 2 starting with "Response Sets have"

I think this sentence should be parenthetical:

OLD: IANA registries are created in a separate document.

NEW: >>>(<<<IANA registries are created in a separate document.>>>)<<<


==== Section 9.3

I think this sentence reads better as follows:

OLD: Numerous other topics related to use and management of reputation
OLD: systems can be found in [I-D.REPUTE-CONSIDERATIONS].

NEW: Numerous other topics related to >>>the<<< use and management of reputation
NEW: systems can be found in [I-D.REPUTE-CONSIDERATIONS].


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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <pre wrap="">I have been selected as the Applications Area Directorate reviewer for this draft (for background on appsdir, please see <a class="moz-txt-link-freetext" href="http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate">http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate</a>).

Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft.



Document:  draft-ietf-repute-model-08
Title: A Model for Reputation Reporting

Reviewer: Tony Hansen
Review Date: 2013-08-29
IESG Telechat Date: 9/12
IETF Last Call Expires: LC for 07 expired on 2013-08-29, but 08 superseded that


Summary:
The document is ready for publication. Minor notes follow that can be fixed in AUTH48.

The document describes a model for reputation services, particularly those being produced by the Repute WG. It follows the recommendations of RFc4101 for describing a protocol model, which requires answers to 1) the problem the protocol is trying to achieve, 2) the meaning of messages transmitted, and 3) important unobvious features of the protocol. This document accomplishes its goals quite well.



==== ORGANIZATIONAL COMMENT ====

Section 3 "High-Level Architecture" starts with an extended example of where a reputation service would fit into an existing service. Finally, more than a page later, it starts describing the architecture that is supposed to be the topic of this section. I suggest that the section be split into two, with the beginning given the heading along the lines of "Example of a Reputation Service Being Used", and the "High-Level Architecture" heading moved right before the paragraph that starts "This document outlines". Alternatively, add subsection titles.


&nbsp;
==== MINOR NITS ====

Changes below are marked with &gt;&gt;&gt;&lt;&lt;&lt;.

==== Section 1, paragraph 5 starting with "A full trust"

I think this sentence would read better as follows, both for readability and to match the style of the surrounding sentences:

OLD: Some need only produce a basic rating, while others need to provide
OLD: underlying detail.

NEW: Some need &gt;&gt;to&lt;&lt; only produce a basic rating, while others need to provide
NEW: &gt;&gt;the&lt;&lt; underlying detail.

==== Section 2, paragraph 1 starting with "The basic premise"

I think this sentence would read better with the introduction some additional punctuation.

OLD: Typically client and service operators enter into
OLD: some kind of agreement during which some parameters are exchanged
OLD: such as the location at which the reputation service can be reached,
OLD: the nature of the reputation data being offered, possibly some client
OLD: authentication details, and the like.

NEW: Typically client and service operators enter into
NEW: some kind of agreement during which some parameters are exchanged&gt;&gt;&gt;,&lt;&lt;&lt;
NEW: such as&gt;&gt;&gt;:&lt;&lt;&lt; the location at which the reputation service can be reached,
NEW: the nature of the reputation data being offered, possibly some client
NEW: authentication details, and the like.

==== Section 3, paragraph 5 starting with "It provides"

I think there is a typo in this sentence and the word "one" should be "done".

OLD: (Although not typically thought of as a 'transport', the DNS
OLD: provides generic capabilities and can be thought of as a mechanism
OLD: for transporting queries and responses that have nothing to do with
OLD: Internet addresses, such as is one with a DNS BlockList [<a href="http://tools.ietf.org/html/draft-ietf-repute-model-08#ref-DNSBL" title="&quot;DNS Blacklists and Whitelists&quot;">DNSBL</a>].)

NEW: (Although not typically thought of as a 'transport', the DNS
NEW: provides generic capabilities and can be thought of as a mechanism
NEW: for transporting queries and responses that have nothing to do with
NEW: Internet addresses, such as is &gt;&gt;&gt;done&lt;&lt;&lt; with a DNS BlockList [<a href="http://tools.ietf.org/html/draft-ietf-repute-model-08#ref-DNSBL" title="&quot;DNS Blacklists and Whitelists&quot;">DNSBL</a>].)

==== Section 4.1, paragraph 2 starting with "Response Sets have"

I think this sentence should be parenthetical:

OLD: IANA registries are created in a separate document.

NEW: &gt;&gt;&gt;(&lt;&lt;&lt;IANA registries are created in a separate document.&gt;&gt;&gt;)&lt;&lt;&lt;


==== Section 9.3

I think this sentence reads better as follows:

OLD: Numerous other topics related to use and management of reputation
OLD: systems can be found in [I-D.REPUTE-CONSIDERATIONS].

NEW: Numerous other topics related to &gt;&gt;&gt;the&lt;&lt;&lt; use and management of reputation
NEW: systems can be found in [I-D.REPUTE-CONSIDERATIONS].
</pre>
    <div style="bottom: auto; left: 287px; right: auto; top: 122px;
      display: none;" class="translator-theme-default"
      id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

--------------060402010505070101090409--

From schlitt@theworld.com  Thu Aug 29 09:31:09 2013
Return-Path: <schlitt@theworld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 002DA11E8124 for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id holQyfI4T1Pz for <ietf@ietfa.amsl.com>; Thu, 29 Aug 2013 09:31:03 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id D8DA411E811B for <ietf@ietf.org>; Thu, 29 Aug 2013 09:30:54 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r7TGU9jC026224; Thu, 29 Aug 2013 12:30:12 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r7TGU8PX198372; Thu, 29 Aug 2013 12:30:08 -0400 (EDT)
Received: from localhost (schlitt@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) with ESMTP id r7TGU8pl198299; Thu, 29 Aug 2013 12:30:08 -0400 (EDT)
X-Authentication-Warning: shell01.TheWorld.com: schlitt owned process doing -bs
Date: Thu, 29 Aug 2013 12:30:07 -0400
From: Dan Schlitt <schlitt@theworld.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-spfbis-4408bis-19.txt> (Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1) to Proposed Standard
In-Reply-To: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>
Message-ID: <Pine.SGI.4.61.1308291142180.193807@shell01.TheWorld.com>
References: <20130819131916.22579.36328.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Fri, 30 Aug 2013 08:04:31 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 16:31:09 -0000

I did not participate in the original working group that developed SPF. 
However I had a number of long phone conversations with one of the folks 
who was active in the group. A good part of those conversations involved 
the use of the TXT record. I objected to overloading that RR. In 
response there was a bit of disparagement of namedroppers folks who 
joined in the discussions. In the end I was told that TXT worked and 
that was that.

I did join in the current working group and when the subject of the TXT 
and SPF records came up I commented that I believed it was inappropriate 
to overload the TXT record and that the SPF record was the correct way 
to go and a transition plan should be worked out. It became clear that 
there was a group that were determined to use the TXT record and get rid 
of the SPF record. So I didn't see much benefit in pushing my view in 
the WG.

As the manager of a modestly large network I found the TXT record as a 
useful tool in management of the network. Such a use was even suggested 
by other system managers. That was a time when the Internet was a 
friendlier place. Today I might do things differently and not make some 
of the TXT records visible on the public Internet. But they would still 
be useful for internal management.

The discussions in the working group made it clear that there were 
design problems with SPF. It would have benefited from a well focused 
problem statement and a related requirements statement. Most of the 
problems are internal to the framework.

It is a sender policy and there is no corresponding receiver policy 
framework. There were those who wished to add in things that essentially 
were a receiver policy.

The design feature that has a wider impact on the Internet is the use of 
the DNS. The working group was dominated by the internals of the 
framework and had little concern with broader questions. Internally the 
TXT record was their choice.

I believe that it is unwise to have a standards track protocol which 
overloads the TXT record. It is this last call which has a broader look 
at the proposed standard that is the place to make this judgment.

As far as the current use of the SPF RR is concerned I have the feeling 
that the members of the working group had a rather optimistic view of 
the actual use of the sender policy. It is not on the standards track. 
Having a standards track version should encourage more use of the 
framework. If the standard said use the SPF record that would increase 
its use. A transition plan which allowed the current installed base to 
continue on would allow a standard with out disruption.

It would be a shame to lose all the other work on the framework so, if 
the current version of the document can't for some reason be changed, it 
should be published as informational. It should be edited so that it 
describes the current use of the framework with suggestions for improved 
opperation.

I do think that the folks who were tasked with leading the working group 
should be given credit for the job that they did. It was not the easiest 
working group to deal with. There were time when I feared that it would 
drop into the disfunctional state as, for example usefor. They avoided 
that and got the work back on track.

/dan

-- 

Dan Schlitt
schlitt@Theworld.com



From hallam@gmail.com  Fri Aug 30 08:48:20 2013
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 D5F2D21F9DB4 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 08:48:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level: 
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, 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 ndQmcFVixF7p for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 08:48:08 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 858DA21F9FF9 for <ietf@ietf.org>; Fri, 30 Aug 2013 08:48:07 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id eo20so1680372lab.34 for <ietf@ietf.org>; Fri, 30 Aug 2013 08:48: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=5xv6dXwtlgQytKYmMuLAuPuG2UYnR7Kjg6tdOPMxdfU=; b=csZ9Q2OKujVlL3PL0eia875wVwPMC3k8d/rHgx9RgqVpgXIOeeffh3MU0yoD+leN0i 6/JmFQh2XE1QeoAKo5VpavzpuVfi2oqycX3TPa7RXl9OCbz6Y/5FVQa23BPPJHSo6XFA kIoVxLR4mXvTCrcQG5BJVMng5YPD+unFtMKST09U5dyG3YGWcWzCSlQIBOe15pVWvrb7 O6HuM4MTAXyTIKCSDDTw8Haj5mKJK/kOTkuDDkGAbMMFgqqsYDUlfxBzI+3NXrXaaI7M NCY11MA1T2IF012pARBmPUY9BY7LzaRS3OnMpI27mA8JwKgLw6KwFIcJhau08jOc4qUk 4RYg==
MIME-Version: 1.0
X-Received: by 10.112.158.225 with SMTP id wx1mr2344473lbb.37.1377877686399; Fri, 30 Aug 2013 08:48:06 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Fri, 30 Aug 2013 08:48:06 -0700 (PDT)
In-Reply-To: <3B833B3E8A7BD501E72E1C85@caldav.corp.apple.com>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com> <3B833B3E8A7BD501E72E1C85@caldav.corp.apple.com>
Date: Fri, 30 Aug 2013 11:48:06 -0400
Message-ID: <CAMm+Lwgg9e9ram3o7yk=XvF-zJhC4Ay_5gnveXo8M=41YM-6=g@mail.gmail.com>
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: multipart/alternative; boundary=001a11c349320ab68704e52c2624
Cc: John C Klensin <john-ietf@jck.com>, 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, 30 Aug 2013 15:48:21 -0000

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

On Fri, Aug 30, 2013 at 10:38 AM, Cyrus Daboo <cyrus@daboo.name> wrote:

> Hi Phillip,
>
>
> --On August 30, 2013 at 10:16:46 AM -0400 Phillip Hallam-Baker <
> hallam@gmail.com> wrote:
>
>  Service discovery requires prefixes.
>>
>> Here is a draft that works fine (except for the IETF review mistake). Just
>> put IETF last call on it:
>>
>> http://tools.ietf.org/html/**draft-gudmundsson-dns-srv-**iana-registry-04<http://tools.ietf.org/html/draft-gudmundsson-dns-srv-iana-registry-04>
>>
>
> I believe that draft was superseded by RFC6335 and all service names (SRV
> prefix labels) are now recorded at <http://www.iana.org/**
> assignments/service-names-**port-numbers/service-names-**
> port-numbers.xhtml<http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml>>
> - indeed several of those come from RFCs I have written that add new SRV
> names.


Ah, its there but not in the DNS area where I was looking.

Thanks.



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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Aug 30, 2013 at 10:38 AM, Cyrus Daboo <span dir=3D"ltr">&lt=
;<a href=3D"mailto:cyrus@daboo.name" target=3D"_blank">cyrus@daboo.name</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Phillip,<div class=3D"im"><br>
<br>
--On August 30, 2013 at 10:16:46 AM -0400 Phillip Hallam-Baker &lt;<a href=
=3D"mailto:hallam@gmail.com" target=3D"_blank">hallam@gmail.com</a>&gt; wro=
te:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Service discovery requires prefixes.<br>
<br>
Here is a draft that works fine (except for the IETF review mistake). Just<=
br>
put IETF last call on it:<br>
<br>
<a href=3D"http://tools.ietf.org/html/draft-gudmundsson-dns-srv-iana-regist=
ry-04" target=3D"_blank">http://tools.ietf.org/html/<u></u>draft-gudmundsso=
n-dns-srv-<u></u>iana-registry-04</a><br>
</blockquote>
<br></div>
I believe that draft was superseded by RFC6335 and all service names (SRV p=
refix labels) are now recorded at &lt;<a href=3D"http://www.iana.org/assign=
ments/service-names-port-numbers/service-names-port-numbers.xhtml" target=
=3D"_blank">http://www.iana.org/<u></u>assignments/service-names-<u></u>por=
t-numbers/service-names-<u></u>port-numbers.xhtml</a>&gt; - indeed several =
of those come from RFCs I have written that add new SRV names.</blockquote>
<div><br></div><div>Ah, its there but not in the DNS area where I was looki=
ng.</div><div><br></div><div>Thanks.=A0</div></div><br><br clear=3D"all"><d=
iv><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hal=
lambaker.com/</a><br>

</div></div>

--001a11c349320ab68704e52c2624--

From john-ietf@jck.com  Fri Aug 30 09:13:41 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E8711E8115 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 09:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wawp0a1BDyHm for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 09:13:36 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8496821F9FBA for <ietf@ietf.org>; Fri, 30 Aug 2013 09:13:36 -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 1VFRKI-000K1Z-3J; Fri, 30 Aug 2013 12:13:34 -0400
Date: Fri, 30 Aug 2013 12:13:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <hallam@gmail.com>, Cyrus Daboo <cyrus@daboo.name>
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Message-ID: <F1D91E1FF217CF7C63DFC337@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+Lwgg9e9ram3o7yk=XvF-zJhC4Ay_5gnveXo8M=41YM-6=g@mail.gmail.com>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com> <3B833B3E8A7BD501E72E1C85@caldav.corp.apple.com> <CAMm+Lwgg9e9ram3o7yk=XvF-zJhC4Ay_5gnveXo8M=41YM-6=g@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion 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, 30 Aug 2013 16:13:41 -0000

--On Friday, August 30, 2013 11:48 -0400 Phillip Hallam-Baker
<hallam@gmail.com> wrote:

>> I believe that draft was superseded by RFC6335 and all
>> service names (SRV prefix labels) are now recorded at
>> <http://www.iana.org/**
>> assignments/service-names-**port-numbers/service-names-**
>> port-numbers.xhtml<http://www.iana.org/assignments/service-na
>> mes-port-numbers/service-names-port-numbers.xhtml>> - indeed
>> several of those come from RFCs I have written that add new
>> SRV names.
> 
> 
> Ah, its there but not in the DNS area where I was looking.

And that is exactly the reason why that temporary appendix calls
for some rethinking and reorganization of how the registries are
organized so as to make that, and similar registries, easier to
find.  

While I continue to believe that doing the work would be a good
exercise for a relative newcomer, if one of you wants to go at
it, please do so with my blessings.

   john





From braden@isi.edu  Fri Aug 30 10:20:38 2013
Return-Path: <braden@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 6024421F9C56 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 10:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id stxN0is2VmaD for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 10:20:25 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 0843C21F8804 for <ietf@ietf.org>; Fri, 30 Aug 2013 10:20:24 -0700 (PDT)
Received: from [128.9.160.107] (cat.isi.edu [128.9.160.107]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r7UGuMH2028018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 30 Aug 2013 09:56:27 -0700 (PDT)
Message-ID: <5220CEB6.2020509@isi.edu>
Date: Fri, 30 Aug 2013 09:56:22 -0700
From: Bob Braden <braden@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com> <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net> <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@mail.gmail.com> <6.2.5.6.2.20130829085018.0cef9ea0@resistor.net> <CAL0qLwahKAUg0Dvqp=JYAE8HNejutNYG1W=HHH4LoDG05H=aNQ@mail.gmail.com>
In-Reply-To: <CAL0qLwahKAUg0Dvqp=JYAE8HNejutNYG1W=HHH4LoDG05H=aNQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: braden@isi.edu
Cc: SM <sm@resistor.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 17:20:38 -0000

CR LF was first adopted for the Telnet NVT (Network Virtual Terminal). I 
think it was Jon
Postel's choice, and no one disagreed. Then when FTP was defined, it 
seemed most economical
to use the same. In fact, doesn't the FTP spec explicitly say that the 
conventions on the control
connection should be those of Telnet? Later, when Jon defined SMTP, I am 
sure that
Jon would not have dreamed of using different end-of-line conventions in 
different protocols.

I would hope that you would not dream of it, either.

Bob Braden

>
> We can go with CRLF, since it's been pointed out to me that most 
> text-based protocols have historically used that.  Who am I to change 
> history?  :-)
>
> -MSK
>


From michelle.cotton@icann.org  Fri Aug 30 10:21:37 2013
Return-Path: <michelle.cotton@icann.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D3C21E805F for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 10:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 56Mbl-4dfUiW for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 10:21:31 -0700 (PDT)
Received: from EXPFE100-1.exc.icann.org (expfe100-1.exc.icann.org [64.78.22.236]) by ietfa.amsl.com (Postfix) with ESMTP id 51A8421E8082 for <ietf@ietf.org>; Fri, 30 Aug 2013 10:21:31 -0700 (PDT)
Received: from EXVPMBX100-1.exc.icann.org ([64.78.22.232]) by EXPFE100-1.exc.icann.org ([64.78.22.236]) with mapi; Fri, 30 Aug 2013 10:21:30 -0700
From: Michelle Cotton <michelle.cotton@icann.org>
To: John C Klensin <john-ietf@jck.com>, Phillip Hallam-Baker <hallam@gmail.com>, Cyrus Daboo <cyrus@daboo.name>
Date: Fri, 30 Aug 2013 10:21:23 -0700
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Thread-Topic: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Thread-Index: Ac6lpV2ka33q84qIToCq8BDzf/uVOQ==
Message-ID: <CE462076.E6EEC%michelle.cotton@icann.org>
In-Reply-To: <F1D91E1FF217CF7C63DFC337@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.6.130613
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3460702883_6800157"
MIME-Version: 1.0
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, 30 Aug 2013 17:21:37 -0000

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

This is helpful feedback.
We are looking at how the listing of the registries is used by the
community.  
There have been suggestions of adding keywords to help when people search
for registries.
As the list of registries grows, we want to make sure it is useful and
that registries can easily be found.
We may be requesting community feedback in the near future about how the
listing of registries could change.

Thank you,

--Michelle


Michelle Cotton
Manager, IANA Services
ICANN

On 8/30/13 9:13 AM, "John C Klensin" <john-ietf@jck.com> wrote:

>
>
>--On Friday, August 30, 2013 11:48 -0400 Phillip Hallam-Baker
><hallam@gmail.com> wrote:
>
>>> I believe that draft was superseded by RFC6335 and all
>>> service names (SRV prefix labels) are now recorded at
>>> <http://www.iana.org/**
>>> assignments/service-names-**port-numbers/service-names-**
>>> port-numbers.xhtml<http://www.iana.org/assignments/service-na
>>> mes-port-numbers/service-names-port-numbers.xhtml>> - indeed
>>> several of those come from RFCs I have written that add new
>>> SRV names.
>> 
>> 
>> Ah, its there but not in the DNS area where I was looking.
>
>And that is exactly the reason why that temporary appendix calls
>for some rethinking and reorganization of how the registries are
>organized so as to make that, and similar registries, easier to
>find.  
>
>While I continue to believe that doing the work would be a good
>exercise for a relative newcomer, if one of you wants to go at
>it, please do so with my blessings.
>
>   john
>
>
>
>

--B_3460702883_6800157
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIITugYJKoZIhvcNAQcCoIITqzCCE6cCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EYYwggb2MIIF3qADAgECAhAFLoNW3qD4JhFZyohPBtNqMA0GCSqGSIb3DQEBBQUAMGIxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xITAfBgNVBAMTGERpZ2lDZXJ0IEFzc3VyZWQgSUQgQ0EtMTAeFw0xMzAzMjAwMDAw
MDBaFw0xNjAzMjAxMjAwMDBaMIGfMQswCQYDVQQGEwJVUzETMBEGA1UECBMKQ2FsaWZvcm5p
YTEUMBIGA1UEBxMLTG9zIEFuZ2VsZXMxPDA6BgNVBAoTM0ludGVybmV0IENvcnBvcmF0aW9u
IGZvciBBc3NpZ25lZCBOYW1lcyBhbmQgTnVtYmVyczENMAsGA1UECxMESUFOQTEYMBYGA1UE
AxMPTWljaGVsbGUgQ290dG9uMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxWwq
bCL/Xkl+g9mKzyjxA8YKyTJgMKkfuNPm2Pi5iWmUGpAHkSCUX/YKf1rninFM8JkzffVgInmx
juZQRW7lP2796RU0UAUdEsbfDcE5l4dj8h7omA2HkiwvKgxBwegr8VHjzUxOzSetAio5Y2qA
Fs7EY97BX6aulzP+tyKi5+7GSBRq+SguiLYETk4FZo8nmyK8E0210+ozwlUQ0VSfkpWluyc/
wQtRo/vQYoM0DPgVaxkE9r20ReyqaE+mxN2pqKl8qoiNMUAnbJIVUSfZhIxS4yoVKNLsOJzo
CYSrD6JgNOmzbEOfrTMWMAhh1RCqp5bcaZ4Zlq2lbrIGHzPgSwIDAQABo4IDaDCCA2QwHwYD
VR0jBBgwFoAUFQASKxOYspkH7R7for5XDStnAs0wHQYDVR0OBBYEFFcRyKFrxJAiHzozbxx0
fzjeiYmeMCQGA1UdEQQdMBuBGW1pY2hlbGxlLmNvdHRvbkBpY2Fubi5vcmcwDgYDVR0PAQH/
BAQDAgWgMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggrBgEFBQcDAjB9BgNVHR8EdjB0MDigNqA0
hjJodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNybDA4
oDagNIYyaHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEQ0EtMS5j
cmwwggHFBgNVHSAEggG8MIIBuDCCAbQGCmCGSAGG/WwEAQIwggGkMDoGCCsGAQUFBwIBFi5o
dHRwOi8vd3d3LmRpZ2ljZXJ0LmNvbS9zc2wtY3BzLXJlcG9zaXRvcnkuaHRtMIIBZAYIKwYB
BQUHAgIwggFWHoIBUgBBAG4AeQAgAHUAcwBlACAAbwBmACAAdABoAGkAcwAgAEMAZQByAHQA
aQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMAdABpAHQAdQB0AGUAcwAgAGEAYwBjAGUAcAB0AGEA
bgBjAGUAIABvAGYAIAB0AGgAZQAgAEQAaQBnAGkAQwBlAHIAdAAgAEMAUAAvAEMAUABTACAA
YQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkAaQBuAGcAIABQAGEAcgB0AHkAIABBAGcAcgBlAGUA
bQBlAG4AdAAgAHcAaABpAGMAaAAgAGwAaQBtAGkAdAAgAGwAaQBhAGIAaQBsAGkAdAB5ACAA
YQBuAGQAIABhAHIAZQAgAGkAbgBjAG8AcgBwAG8AcgBhAHQAZQBkACAAaABlAHIAZQBpAG4A
IABiAHkAIAByAGUAZgBlAHIAZQBuAGMAZQAuMHcGCCsGAQUFBwEBBGswaTAkBggrBgEFBQcw
AYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEEGCCsGAQUFBzAChjVodHRwOi8vY2FjZXJ0
cy5kaWdpY2VydC5jb20vRGlnaUNlcnRBc3N1cmVkSURDQS0xLmNydDAMBgNVHRMBAf8EAjAA
MA0GCSqGSIb3DQEBBQUAA4IBAQAzABp5GDSqoV3ty0YLFXRO8ZlHtgsLOP+5AmAS9P0mDEny
uO6xbrWK/Oi+9/UfcnYKYUGkFvukHBFLowWakQngPhHLjEhNl2QYC4dbQWLd9z4gZWBWYVzs
EreLwUSbRbE3G1r/lkUK3EYO5xAAWtFcv0I4Ixd3//0zxg0ohWW7fm22ypXr8HIBffpptim+
6oO6X55ME5789phHZZDQt6haEHyMnAQNW2SL6e8cgSL30lPcpStRCXriyXBdoSI+oW83+9u3
SvhjG9WXw8sso9oWMBWo8BhSTERNzLYbxQMazYHW5L/BUBUICTR6l3W96+rjpPZDZVpd9wgR
AG54dZ+mMIIGzTCCBbWgAwIBAgIQBv35A5YDreoACus/J7u6GzANBgkqhkiG9w0BAQUFADBl
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln
aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwHhcNMDYx
MTEwMDAwMDAwWhcNMjExMTEwMDAwMDAwWjBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGln
aUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2Vy
dCBBc3N1cmVkIElEIENBLTEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDogi2Z
+crCQpWlgHNAcNKeVlRcqcTSQQaPyTP8TUWRXIGf7Syc+BZZ3561JBXCmLm0d0ncicQK2q/L
XmvtrbBxMevPOkAMRk2T7It6NggDqww0/hhJgv7HxzFIgHweog+SDlDJxofrNj/YMMP/pvf7
os1vcyP+rFYFkPAyIRaJxnCI+QWXfaPHQ90C6Ds97bFBo+0/vtuVSMTuHrPyvAwrmdDGXRJC
geGDboJzPyZLFJCuWWYKxI2+0s4Grq2Eb0iEm09AufFM8q+Y+/bOQF1c9qjxL6/siSLyaxhl
scFzrdfx2M8eCnRcQrhofrfVdwonVnwPYqQ/MhRglf0HBKIJAgMBAAGjggN6MIIDdjAOBgNV
HQ8BAf8EBAMCAYYwOwYDVR0lBDQwMgYIKwYBBQUHAwEGCCsGAQUFBwMCBggrBgEFBQcDAwYI
KwYBBQUHAwQGCCsGAQUFBwMIMIIB0gYDVR0gBIIByTCCAcUwggG0BgpghkgBhv1sAAEEMIIB
pDA6BggrBgEFBQcCARYuaHR0cDovL3d3dy5kaWdpY2VydC5jb20vc3NsLWNwcy1yZXBvc2l0
b3J5Lmh0bTCCAWQGCCsGAQUFBwICMIIBVh6CAVIAQQBuAHkAIAB1AHMAZQAgAG8AZgAgAHQA
aABpAHMAIABDAGUAcgB0AGkAZgBpAGMAYQB0AGUAIABjAG8AbgBzAHQAaQB0AHUAdABlAHMA
IABhAGMAYwBlAHAAdABhAG4AYwBlACAAbwBmACAAdABoAGUAIABEAGkAZwBpAEMAZQByAHQA
IABDAFAALwBDAFAAUwAgAGEAbgBkACAAdABoAGUAIABSAGUAbAB5AGkAbgBnACAAUABhAHIA
dAB5ACAAQQBnAHIAZQBlAG0AZQBuAHQAIAB3AGgAaQBjAGgAIABsAGkAbQBpAHQAIABsAGkA
YQBiAGkAbABpAHQAeQAgAGEAbgBkACAAYQByAGUAIABpAG4AYwBvAHIAcABvAHIAYQB0AGUA
ZAAgAGgAZQByAGUAaQBuACAAYgB5ACAAcgBlAGYAZQByAGUAbgBjAGUALjALBglghkgBhv1s
AxUwEgYDVR0TAQH/BAgwBgEB/wIBADB5BggrBgEFBQcBAQRtMGswJAYIKwYBBQUHMAGGGGh0
dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTBDBggrBgEFBQcwAoY3aHR0cDovL2NhY2VydHMuZGln
aWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNydDCBgQYDVR0fBHoweDA6oDig
NoY0aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNy
bDA6oDigNoY0aHR0cDovL2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9v
dENBLmNybDAdBgNVHQ4EFgQUFQASKxOYspkH7R7for5XDStnAs0wHwYDVR0jBBgwFoAUReui
r/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQEFBQADggEBAEZQPsm3KCSnOB22WymvUs9S
6TFHq1Zce9UNC0Gz7+x1H3Q48rJcYaKclcNQ5IK5I9G6OoZyrTh4rHVdFxc0ckeFlFbR67s2
hHfMJKXzBBlVqefj56tizfuLLZDCwNK1lL1eT7EF0g49GqkUW6aGMWKoqDPkmzmnxPXOHXh2
lCVz5Cqrz5x2S+1fwksW5EtwTACJHvzFebxMElf+X+EevAJdqP77BzhPDcZdkbkPZ0XN1oPt
55INjbFpjE/7WeAjD9KqrgB87pxCDs+R1ye3Fu4Pw718CqDuLAhVhSK46xgaTfwqIa1JMYNH
lXdx3LEbS0scEJx3FMGdTy9alQgpECYwggO3MIICn6ADAgECAhAM5+DlF9hG/o/lYPwb8DA5
MA0GCSqGSIb3DQEBBQUAMGUxCzAJBgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMx
GTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQg
SUQgUm9vdCBDQTAeFw0wNjExMTAwMDAwMDBaFw0zMTExMTAwMDAwMDBaMGUxCzAJBgNVBAYT
AlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2VydC5jb20x
JDAiBgNVBAMTG0RpZ2lDZXJ0IEFzc3VyZWQgSUQgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAK0OFc7kQ4BcsYfzt2D5cRKlrtwmlIiq9M71IDkoWGAM+IDaqRWV
MmE8tbEohIqK3J8KDIMXeo+QrIrneVNcMYQq9g+YMjZ2zN7dPKii72r7IfJSYd+fINcf4rHZ
/hhk0hJbX/lYGDW8R82hNvlrf9SwOD7BG8OMM9nYLxj+KA+zp4PWw25EwGE1lhb+WZyLdm3X
8aJLDSv/C3LanmDQjpA1xnhVhyChz+VtCshJfDGYM2wi6YfQMlqiuhOCEe05F52ZOnKh5vqk
2dUXMXWuhX0irj8BRob2KHnIsdrkVxfEfhwOsLSSplazvbKX7aqn8LfFqD+VFtD/oZbrCF8Y
d08CAwEAAaNjMGEwDgYDVR0PAQH/BAQDAgGGMA8GA1UdEwEB/wQFMAMBAf8wHQYDVR0OBBYE
FEXroq/0ksuCMS1Ri6enIZ3zbcgPMB8GA1UdIwQYMBaAFEXroq/0ksuCMS1Ri6enIZ3zbcgP
MA0GCSqGSIb3DQEBBQUAA4IBAQCiDrzf4u3w43JzemSUv/dyZtgy5EJ1Yq6H6/LV2d5Ws5/M
zhQouQ2XYFwSTFjk0z2DSUVYlzVpGqhH6lbGeasS2GeBhN9/CTyU5rgmLCC9PbMoifdf/yLi
l4Qf6WXvh+DfwWdJs13rsgkq6ybteL59PyvztyY1bV+JAbZJW58BBZurPSXBzLZ/wvFvhsb6
ZGjrgS2U60K3+owe3WLxvlBnt2y98/Efaww2BxZ/N3ypW2168RJGYIPXJwS+S86XvsNnKmgR
34DnDDNmvxMNFG7zfx9jEB76jRslbWyPpbdhAbHSoyahEHGdreLD+cOZUbcrBwjOLuZQsqf6
CkUvovDyMYIB/DCCAfgCAQEwdjBiMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQg
SW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSEwHwYDVQQDExhEaWdpQ2VydCBBc3N1
cmVkIElEIENBLTECEAUug1beoPgmEVnKiE8G02owCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJ
BDEWBBQSW1itPu62JYG82A4Wt6R1IsPbIjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xMzA4MzAxNzIxMjNaMA0GCSqGSIb3DQEBAQUABIIBACNLbyoyv4vS
K9wP+xFbapn7vNCmSHlHa+W7nXq1bls8HirEvpcqT5XCu7+jFCGGLsGPvIhUnzefSrgP810n
R8LoKHwjRi5NOe6lwqHm4K4uew9t7QAK3rMefAjIVGlhI3V1jcPXOhTIsF7y34LJAeKIbuoW
iMTxeB2P/P/Z1Ab2KwbT9ADWtJpH8HjUw3oZEjA/Qzg4NINsy+F1WLWcStp6MCTC7AoRfzEY
ilu4Dnc1tghpjb9sXgDbeoTC3eP1V6m3dl2osxEjtcsLDg3KDmbCfFIs27aqUm7Qo1neDVMI
eZM8sugOu/zXg3V23Ls8WUrrz+eHv9/+T00zrr+nEyY=

--B_3460702883_6800157--

From hsantos@isdg.net  Fri Aug 30 11:37:39 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F7C21F9FF2 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 11:37:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.443
X-Spam-Level: 
X-Spam-Status: No, score=-102.443 tagged_above=-999 required=5 tests=[AWL=0.156, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71awv0YvIXbG for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 11:37:34 -0700 (PDT)
Received: from secure.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC6C21F9F23 for <ietf@ietf.org>; Fri, 30 Aug 2013 11:37:23 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1993; t=1377887840; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=hjiLyK+ZTqlVEY++eB9T8nQDJqI=; b=OOc5QkK9z/7ujegHE4S9 74nA14/fCOpybfkWpChjueiTa61fwwVelk2wX98tDhAeVJY8GiN0yZOJmdKdq/SJ S0+5q6bORcntOUdKVETCdYPxdBO8RiRzuLGsag04wWjj8i/Rxnme49Pzo7t0DEPR AJDKBiEUinapnglExQl1fxs=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 14:37: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 opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 55379858.13298.3844; Fri, 30 Aug 2013 14:37:19 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1993; t=1377887515; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=e4Nir9L /yvzPaob3KVbwmpPpeaEodx5+9w8c16hF4bM=; b=SYRlo9A8sozzbj7eg8qWAHZ uqWsspQyuBtqqCUInl+zo4Exm7XE4ut8uH1Nxqb4qdC1dVM50X/iK0CxXvTOZwGP VzNKBr6wk3ry90dOnIMwTrG2lOGcQ55upGm8hLikNZQoEHxMOohxTkr7ZntirxTn wxUpeQhLagtLHYFmx9LY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 14:31:55 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3796762596.9.2896; Fri, 30 Aug 2013 14:31:53 -0400
Message-ID: <5220E659.1070906@isdg.net>
Date: Fri, 30 Aug 2013 14:37:13 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: AppsDir review of draft-ietf-repute-model-08
References: <5220B055.2000704@att.com>
In-Reply-To: <5220B055.2000704@att.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-repute-model.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>, General discussion of application-layer protocols <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 18:37:40 -0000

On 8/30/2013 10:46 AM, Tony Hansen wrote:
>
> The document describes a model for reputation services, particularly those being produced by the Repute WG. It follows the recommendations of RFc4101 for describing a protocol model, which requires answers to 1) the problem the protocol is trying to achieve, 2) the meaning of messages transmitted, and 3) important unobvious features of the protocol. This document accomplishes its goals quite well.

Hi Tony,

As a high potential implementator of this DKIM-REPUTE framework and 
user of any future REPUTE products based on this DKIM-REPUTE 
framework, I am somewhat disappointed to find not a single integration 
consideration for the highly adopted SPF technology.  Not a single 
mentioning of the word or the integrated use of this highly adopted 
mail transport augmented technology.

Any adopter of this framework or its products who are also SPF 
implementors would need to know at the very least how current 
protocols are affected and also can affect DKIM-REPUTE product 
designers.

For example, DKIM-REPUTE product designers would need to consider SPF 
reputons product models.  Simple text as follows can resolve the 
integration consideration with little SPF fanfare the draft obviously 
tried to avoid:

    REPUTE protocols based on this framework need to consider reputons
    based on SMTP level filtering protocols such SPF [RFC4408],
    IP based filtering [DNSRBL] or others.

    The design consideration for operations may necessitate disabling
    or relaxing SMTP level filters in order to enable filtering based
    on this DKIM-REPUTE model.

I am seeing all this as an integrator of all mentioned mail 
technologies; SPF, SENDERID/SUBMITTER, DKIM, ADSP, VBR.  I welcome 
this REPUTE framework. It should consider the existence of other 
protocols and integrators need some design tips. Besides, for any 
provider of a REPUTE service, they will benefit by these integrated 
considerations as well.

Thanks

-- 
HLS



From john-ietf@jck.com  Fri Aug 30 11:53:29 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D71911E810E for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 11:53:29 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8LS0hujA8uuk for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 11:53:23 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 36A8D21F9E00 for <ietf@ietf.org>; Fri, 30 Aug 2013 11:53:21 -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 1VFToh-000KBq-GA; Fri, 30 Aug 2013 14:53:07 -0400
Date: Fri, 30 Aug 2013 14:53:02 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Braden <braden@isi.edu>, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation	Query Protocol) to Proposed Standard
Message-ID: <8EC9C92C6AADD2832A92D9B1@JcK-HP8200.jck.com>
In-Reply-To: <5220CEB6.2020509@isi.edu>
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com> <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net> <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@mail.gmail.com> <6.2.5.6.2.20130829085018.0cef9ea0@resistor.net> <CAL0qLwahKAUg0Dvqp=JYAE8HNejutNYG1W=HHH4LoDG05H=aNQ@mail.gmail.com> <5220CEB6.2020509@isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: SM <sm@resistor.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 18:53:30 -0000

--On Friday, August 30, 2013 09:56 -0700 Bob Braden
<braden@isi.edu> wrote:

> CR LF was first adopted for the Telnet NVT (Network Virtual
> Terminal). I think it was Jon
> Postel's choice, and no one disagreed.

A tad more complicated, IIR.  It turns out that, with some
systems interpreting LF as "same position next line" and some as
"first position, next line", some interpreting CR as "same
position, this line" and some as "first position next line", CR
LF was the only safe universal choice.  At least one of those
four interpretations was a clear violation of the early versions
of the ASCII standard but the relevant vendor didn't care or was
too ignorant to notice.  That particular bit of analysis was
known pre-ARPANET' I wouldn't be surprised to find it on some
earlier Teletype documentation.  

I have no idea who make the decision for Telnet and friends, but
I wouldn't be at all surprised if it were Jon.  The decision
was, however, pretty constrained.

Similarly, it was an important design constraint for FTP and
later for SMTP, WHIS, FINGer, and a bunch of other things that
they (the control connection for the form) be able to run over
Telnet connections (on a different port).  I don't know whether
that was cause or effect wrt  the CRLF choices for those
protocols, but it probably figured in.  I've suspected whether
that was part of what drove the port mode in preference to some
fancy service-selection handshaking at the beginning of the
connection but I have no idea how that set of decisions were
made. 

> Then when FTP was
> defined, it seemed most economical
> to use the same. In fact, doesn't the FTP spec explicitly say
> that the conventions on the control
> connection should be those of Telnet? 

Yep.  RFC 959, Page 34 (snicker) and RFC 1123 Section 4.1.2.10.
There were even some discussions about the interactions between
Telnet option negotiation and FTP (Section 4.1.2.12 of RFC 1123
was, I think, intended to definitively settle those).

> Later, when Jon defined
> SMTP, I am sure that
> Jon would not have dreamed of using different end-of-line
> conventions in different protocols.
> 
> I would hope that you would not dream of it, either.

Indeed.

   john


From ajs@anvilwalrusden.com  Fri Aug 30 12:20:47 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2E521F9967; Fri, 30 Aug 2013 12:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.833
X-Spam-Level: 
X-Spam-Status: No, score=-0.833 tagged_above=-999 required=5 tests=[AWL=0.007,  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 ETJo32aaQ8YN; Fri, 30 Aug 2013 12:20:38 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 44A2A21F9B03; Fri, 30 Aug 2013 12:20:38 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 62DD18A031; Fri, 30 Aug 2013 19:20:36 +0000 (UTC)
Date: Fri, 30 Aug 2013 15:20:34 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, apps-discuss@ietf.org
Subject: Re: AppsDir review of draft-ietf-repute-model-08
Message-ID: <20130830192034.GP56500@mx1.yitter.info>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5220E659.1070906@isdg.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: Fri, 30 Aug 2013 19:20:47 -0000

On Fri, Aug 30, 2013 at 02:37:13PM -0400, Hector Santos wrote:
> 
> For example, DKIM-REPUTE product designers would need to consider
> SPF reputons product models.  Simple text as follows can resolve the
> integration consideration with little SPF fanfare the draft
> obviously tried to avoid:

Why should the framework document contain details of how various
particular reputation services interact?  If you want a discussion of
reputation-service-interaction mechanisms in the draft, that's one
thing.  If you want to talk about how SPF and DKIM interact, then I
think this is probably the wrong draft.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From hsantos@isdg.net  Fri Aug 30 12:22:29 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF93611E80FA for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.453
X-Spam-Level: 
X-Spam-Status: No, score=-102.453 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tT7MW-s-DUxm for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:22:24 -0700 (PDT)
Received: from secure.winserver.com (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 51DFA21F9A4C for <ietf@ietf.org>; Fri, 30 Aug 2013 12:22:24 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2959; t=1377890541; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=di0kyVlLWC3X5e5ANxUyfTJ8SC8=; b=fMAN2PgVk1kDMw3jZJ+V ktS5UyzWbwTe2wyfFXHOECa9r/0WH26SlvpcIuPPstp/Rw1U25iYdol3k3stKNwz TwlQaNPcfWoDPFRaieOwecwgFKPKCirLtazBOaZolJDDrLJSf11+LHM6rWAXXa2n Hd2a0lb35hkBTTeeWtONoe0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 15:22:21 -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 58080626.13298.4420; Fri, 30 Aug 2013 15:22:20 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2959; t=1377890211; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=I4B5F0O 8zoMzxxz60BJnd4M3+NaLiJ6KgkfuOtSHNFM=; b=gttU8+DYAKTdqsXxfUdwEZT LXwMPgjHche2iWjOiGOno2SLwtLZLOWVFxjGdLJp71QC3SBoIvs/zwGVJ7MngIdk /EhftsnwEt1cLs8UYNB82x1q6Mhzat/IZNSn9hMYaiaSHftXLNMMBR9wjIot4i3N mWmOxAOAnmyKNYA2QY9U=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 15:16:51 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3799459487.9.1056; Fri, 30 Aug 2013 15:16:50 -0400
Message-ID: <5220F0E2.2040309@isdg.net>
Date: Fri, 30 Aug 2013 15:22:10 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-ietf-repute-query-http-09.txt> (A Reputation Query Protocol) to Proposed Standard
References: <20130815144121.15477.78141.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130815092301.0b86a398@resistor.net> <CAL0qLwZvaH-hb5eydR4HdfXcE6GPooJ57ZPfOxK3OFn1d6wqrQ@mail.gmail.com> <6.2.5.6.2.20130821002423.0ba0ed20@resistor.net> <CAL0qLwYnY6YS2W2wuK_BxQ_Fva2hSNAZ9DaNSkeFGcOXtPjvCw@mail.gmail.com> <6.2.5.6.2.20130829085018.0cef9ea0@resistor.net> <CAL0qLwahKAUg0Dvqp=JYAE8HNejutNYG1W=HHH4LoDG05H=aNQ@mail.gmail.com> <5220CEB6.2020509@isi.edu> <8EC9C92C6AADD2832A92D9B1@JcK-HP8200.jck.com>
In-Reply-To: <8EC9C92C6AADD2832A92D9B1@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, Bob Braden <braden@isi.edu>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 19:22:29 -0000

John,

I don't think it would of been fun designing and testing a text-based 
hosting protocol manually with your terminal/telecommunication/telnet 
client "New Line Mode" (add LF to CR) option disabled or server text 
responses only issue CR or LF.

It would of been very hard or confusing to do this stuff visually. :)

Most, if not all of our text based protocols borrow the same 
ASCII/ANSI/VT100/TELNET framework and there are even considerations 
for different terminators in the area of timeouts and also learning 
via the initial handshakes.

--
HLS

On 8/30/2013 2:53 PM, John C Klensin wrote:
>
>
> --On Friday, August 30, 2013 09:56 -0700 Bob Braden
> <braden@isi.edu> wrote:
>
>> CR LF was first adopted for the Telnet NVT (Network Virtual
>> Terminal). I think it was Jon
>> Postel's choice, and no one disagreed.
>
> A tad more complicated, IIR.  It turns out that, with some
> systems interpreting LF as "same position next line" and some as
> "first position, next line", some interpreting CR as "same
> position, this line" and some as "first position next line", CR
> LF was the only safe universal choice.  At least one of those
> four interpretations was a clear violation of the early versions
> of the ASCII standard but the relevant vendor didn't care or was
> too ignorant to notice.  That particular bit of analysis was
> known pre-ARPANET' I wouldn't be surprised to find it on some
> earlier Teletype documentation.
>
> I have no idea who make the decision for Telnet and friends, but
> I wouldn't be at all surprised if it were Jon.  The decision
> was, however, pretty constrained.
>
> Similarly, it was an important design constraint for FTP and
> later for SMTP, WHIS, FINGer, and a bunch of other things that
> they (the control connection for the form) be able to run over
> Telnet connections (on a different port).  I don't know whether
> that was cause or effect wrt  the CRLF choices for those
> protocols, but it probably figured in.  I've suspected whether
> that was part of what drove the port mode in preference to some
> fancy service-selection handshaking at the beginning of the
> connection but I have no idea how that set of decisions were
> made.
>
>> Then when FTP was
>> defined, it seemed most economical
>> to use the same. In fact, doesn't the FTP spec explicitly say
>> that the conventions on the control
>> connection should be those of Telnet?
>
> Yep.  RFC 959, Page 34 (snicker) and RFC 1123 Section 4.1.2.10.
> There were even some discussions about the interactions between
> Telnet option negotiation and FTP (Section 4.1.2.12 of RFC 1123
> was, I think, intended to definitively settle those).
>
>> Later, when Jon defined
>> SMTP, I am sure that
>> Jon would not have dreamed of using different end-of-line
>> conventions in different protocols.
>>
>> I would hope that you would not dream of it, either.
>
> Indeed.
>
>     john
>
>
>



From john-ietf@jck.com  Fri Aug 30 12:36:07 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1438521F9EB8 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:36:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Or4v-U+y+aEn for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:35:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 95E9021F9344 for <ietf@ietf.org>; Fri, 30 Aug 2013 12:35: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 1VFUU8-000KFC-V3; Fri, 30 Aug 2013 15:35:56 -0400
Date: Fri, 30 Aug 2013 15:35:51 -0400
From: John C Klensin <john-ietf@jck.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Message-ID: <580EB1DB59FBEF1041667C2C@JcK-HP8200.jck.com>
In-Reply-To: <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion 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, 30 Aug 2013 19:36:07 -0000

Hi.  I'm going to comment very sparsely on responses to this
draft, especially those that slide off into issues that seem
basically irrelevant to the registry and the motivation for its
creation.   My primary reason is that I don't want to burden the
IETF list with a back-and-forth exchange, particularly about
religious matters.  The comments below are as much to clarify
that plan as they are to response to the particular comments in
Phillip's note.

--On Friday, August 30, 2013 10:16 -0400 Phillip Hallam-Baker
<hallam@gmail.com> wrote:

> RFC 5507 does indeed say that but it is an IAB document, not
> an IETF consensus document and it is wrong.

Yes. it is an IAB document.  And, yes, one of the coauthors of
this draft is a coauthor of 5507 and presumably doesn't share
your opinion of its wrongness.

But that is irrelevant to this particular document.  5507 is
used to set context for discussing the need for the registry and
to establish some terminology.  If the Hallam-Baker Theory of
DNS Extensions had been published in the RFC Series, we might
have drawn on it for context and terminology instead.  Or not,
but we didn't have the choice.   Your description of the motives
of the authors of 5507 is an even better example.  Perhaps you
are correct.  Perhaps you aren't.  But whether you are correct
or not makes absolutely no difference to the actionable content
of this draft.  

The "more prefixes" versus "more RRTYPES" versus subtypes versus
pushing some of these ideas into a different CLASS versus
whatever else one can think of are also very interesting... and
have nothing to do with whether this registry should be created
or what belongs in it.

Since you obviously don't like 5507, I would suggest that you
either prepare a constructive critique and see if you can get it
published or, even better, prepare an alternate description of
how things should be handled and see if you can get consensus
for it.   This document is not a useful place to attack it
because its main conclusions just don't make any difference to
it.  If you have contextual or introductory text that you prefer
wrt justifying or setting up the registry, by all means post it
to the list.  If people prefer it to the 5507 text, there is no
reason why it shouldn't go into a future version of the draft.


> The consequence of this is that we still don't seem to have a
> registry for DNS prefixes, or at least not in the place I
> expect it which is
> 
> Domain Name System (DNS) Parameters
>...

Yes.  It it too hard to find.  That also has nothing to do with
this particular registry.  It is connected to why the I-D
contains a temporary and informative appendix about DNS-related
registries and where one might expect to find them.  Our hope is
that the appendix will motivate others (or IANA) to do some work
to organize things differently or otherwise make them easier to
find.  But whether action is taken on the appendix or not has
nothing to do with whether this registry is created.

> The IANA should be tracking SRV prefix allocations and DNSEXT
> seems to have discussed numerous proposals. I have written
> some myself. But I can't find evidence of one and we certainly
> have not updated SRV etc. to state that the registry should be
> used.

The IANA is extremely constrained about what it can do without
some direction from the IETF.  The appendix is there to provide
a preliminary pointer to some areas that might need work (at
least as much or more by the IETF as by IANA).  If you have
specific things that belong on the list (the working version of
what will become -01 already is corrected to point to the SRV
registry), I'd be happy to add them, with one condition: if we
end up in a discussion of the details of the appendix rather
than the particular proposed registry, the appendix will
disappear.  It is a forward pointer to work that probably should
be done, not the work itself.

> Fixing TXT is optional, fixing the use of prefixes and having
> a proper registry that is first come first served is
> essential. Right now we have thousands of undocumented ad-hoc
> definitions.

Let me restate that.  Some of us believe that it is time to "fix
TXT" or, more specifically, to create a registry that can
accommodate identification of what is being done, whether one
approves of it or not.  If other things need fixing too --and I
agree that at least some of them do-- please go to it.  If the
appendix is useful in that regard, great.  If not, I'm not
particularly attached to it.
 
Neither the structure and organization of IANA registries
generally nor the future of service discovery have anything to
do with this draft.  If you want to discuss them, please start
another thread.

  thanks,
    john



From hsantos@isdg.net  Fri Aug 30 12:39:33 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70B2811E8113 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.461
X-Spam-Level: 
X-Spam-Status: No, score=-102.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpt3yXW3vI+A for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:39:28 -0700 (PDT)
Received: from winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 97AFA21F9FF9 for <ietf@ietf.org>; Fri, 30 Aug 2013 12:39:24 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1667; t=1377891561; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Z5KjKQPKxIVKf/dSqK7Kt4YwDsc=; b=drg7G+Kb1zULEt9Qt5SU GUXAZqWS40tBOAbjZUulYHjtiiWxDpWiT+A/SjzWW13RcMKvZNTpOLd3YrU/id1B iJCZZaKp5Zvn8HJExlIpUsU3VsulomQw/ApUIBqzRTDIIlgN4lQ+1KayACCNwAtt Qij5+GkFZkuRN+0CRmn6sX0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 15:39:21 -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 59100779.13298.3572; Fri, 30 Aug 2013 15:39:20 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1667; t=1377891236; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=QL8FPtP 6qZqoSBxQEE57by/Hspo0rYFzyQYD1aGjOvk=; b=rKY67d2hiErbAEK37xueCEP 2JtqfMdNFTu9NmDTJddiuj+suG4IZgKlxnMF3b96fA1zqQyDE6FGly1Lg31BVMq3 k9vSrFCYmHg84XxGJWeurLLr0L8JszOkBplpW6Q29LFA/gFf5CYWfV5kICIHZzzT rFMGRV7Tb/O0geLMd5ZM=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 15:33:56 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3800483987.9.4308; Fri, 30 Aug 2013 15:33:55 -0400
Message-ID: <5220F4E2.7030005@isdg.net>
Date: Fri, 30 Aug 2013 15:39:14 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: AppsDir review of draft-ietf-repute-model-08
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <20130830192034.GP56500@mx1.yitter.info>
In-Reply-To: <20130830192034.GP56500@mx1.yitter.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 19:39:33 -0000

Hi Andrew,

I think it can be generalized functional description without 
specifics. Designs based on REPUTE and its users of such products, 
will need some information. That may come (hopefully) from the REPUTE 
product designer. I am suggesting to remind such future REPUTE product 
designers of such considerations.   I think it will help the technical 
marketing of REPUTE products and REPUTE service providers.  If a 
choice has to be made between an SMTP layer filtering protocols and 
some new REPUTE payload filter, then what choices are those to be 
considered.

Keep in mind I would be a classic target audience new reader and user 
of this document. I did not participate in the WG. We should not 
expect the audience of the document to be required to visit archives 
of the Repute WG to find or extract these very real and practical 
integration considerations.  The document should have these general 
considerations summarized.

Thanks

On 8/30/2013 3:20 PM, Andrew Sullivan wrote:
> On Fri, Aug 30, 2013 at 02:37:13PM -0400, Hector Santos wrote:
>>
>> For example, DKIM-REPUTE product designers would need to consider
>> SPF reputons product models.  Simple text as follows can resolve the
>> integration consideration with little SPF fanfare the draft
>> obviously tried to avoid:
>
> Why should the framework document contain details of how various
> particular reputation services interact?  If you want a discussion of
> reputation-service-interaction mechanisms in the draft, that's one
> thing.  If you want to talk about how SPF and DKIM interact, then I
> think this is probably the wrong draft.
>
> Best,
>
> A
>

-- 
HLS



From brian.e.carpenter@gmail.com  Fri Aug 30 12:43:54 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 326B411E812A for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NukJb3qf-fi3 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:43:53 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id CD09F11E8125 for <ietf@ietf.org>; Fri, 30 Aug 2013 12:43:53 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id xb4so2244661pbc.8 for <ietf@ietf.org>; Fri, 30 Aug 2013 12:43:53 -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=onH59tqriFyXVNywVaoFmDG3Ffd5mXgFfr4Ny9Mnaak=; b=f3F604kTmj62KqmnWWD/zAGvMHniItCcmEUA8+HFOzu5hnRLm/pl+iPWQlN8P1foJ+ UaupStyeY3DBP8jJjr3PYfE0P2RJLJNg2uY5196O4mewC51JU2H4+jaawurPcmcF63I5 tmpRL0o/R7zTlGzir91a8gNHpsHv/yBfWgIYhD27dUT+JFh4dL5S4eUZDw10dPx5efih gvDDwyo3fFj4MKc6UJmKPmyLvEs6+TZ8IKPa+zl11Z+Z+XYZUhc0+CYu2skfKy/MI5Bh jEK/O39xQHQKaPhTtpYUB/9jgKkJyFife5A5vTy2TeH4b3Cy62AtcPvklxq9W6sa5AkL dm8A==
X-Received: by 10.66.145.166 with SMTP id sv6mr12456853pab.31.1377891833579; Fri, 30 Aug 2013 12:43:53 -0700 (PDT)
Received: from [192.168.178.20] (159.198.69.111.dynamic.snap.net.nz. [111.69.198.159]) by mx.google.com with ESMTPSA id dg3sm46158025pbc.24.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 12:43:52 -0700 (PDT)
Message-ID: <5220F5FD.2020803@gmail.com>
Date: Sat, 31 Aug 2013 07:43:57 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Mail lost yesterday
References: <521F8A93.2090309@venaas.com>	<9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk>	<EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk>	<6.2.5.6.2.20130829152744.0cd688b0@resistor.net>	<17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com>	<6.2.5.6.2.20130829163103.0c665800@resistor.net>	<7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com>	<6.2.5.6.2.20130829173539.0cd44070@resistor.net>	<EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net> <6.2.5.6.2.20130830053743.0c9031d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130830053743.0c9031d0@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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, 30 Aug 2013 19:43:54 -0000

On 31/08/2013 02:26, SM wrote:
...
> 
> The nit is why is the IETF still using PDT.

I assure you that things were operationally much worse when the
Secretariat was using EDT.

Really - the service level has improved continuously over the last
eight years. Of course things can always be better, and we learn
collectively from every incident, but compared to various corporate
and campus services I have used, IETF participants have nothing
to complain about.

    Brian

From paf@frobbit.se  Fri Aug 30 12:47:19 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C6A21E808F for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:47:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MzptlmGHiu4y for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 12:47:18 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 27A2121E8082 for <ietf@ietf.org>; Fri, 30 Aug 2013 12:47:17 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::257d:5471:eef1:af91] (unknown [IPv6:2a02:80:3ffc:0:257d:5471:eef1:af91]) by mail.frobbit.se (Postfix) with ESMTPSA id 217E82200A; Fri, 30 Aug 2013 21:47:16 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <580EB1DB59FBEF1041667C2C@JcK-HP8200.jck.com>
Date: Fri, 30 Aug 2013 21:47:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <121C23AF-C6BE-4099-A635-21CE59C5F477@frobbit.se>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <CAMm+LwhwrNuYfAKri+hK328ULOZwv+sh=rUXm4pAYziMRBW78w@mail.gmail.com> <580EB1DB59FBEF1041667C2C@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1508)
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, 30 Aug 2013 19:47:19 -0000

On 30 aug 2013, at 21:35, John C Klensin <john-ietf@jck.com> wrote:

> The "more prefixes" versus "more RRTYPES" versus subtypes versus
> pushing some of these ideas into a different CLASS versus
> whatever else one can think of are also very interesting... and
> have nothing to do with whether this registry should be created
> or what belongs in it.

One of the key messages in RFC 5507 is that one should have a selector =
of what RR you want in the triple {owner, type, class} and not as part =
of the RDATA.

This document is about creating a registry for the selectors that =
obviously are needed *IF* one have structured data in the RDATA part of =
the TXT resource record type.

Two very different things indeed.

   Patrik


From ajs@anvilwalrusden.com  Fri Aug 30 13:09:30 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2B621F9FBA; Fri, 30 Aug 2013 13:09:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level: 
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[AWL=0.006,  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 3IQtKC7t5SNL; Fri, 30 Aug 2013 13:09:23 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 8C35621F9FF2; Fri, 30 Aug 2013 13:09:23 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id EEF988A031; Fri, 30 Aug 2013 20:09:21 +0000 (UTC)
Date: Fri, 30 Aug 2013 16:09:20 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: AppsDir review of draft-ietf-repute-model-08
Message-ID: <20130830200920.GS56500@mx1.yitter.info>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <20130830192034.GP56500@mx1.yitter.info> <5220F4E2.7030005@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5220F4E2.7030005@isdg.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ietf@ietf.org, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 20:09:31 -0000

On Fri, Aug 30, 2013 at 03:39:14PM -0400, Hector Santos wrote:

> archives of the Repute WG to find or extract these very real and
> practical integration considerations.  The document should have
> these general considerations summarized.

But your suggestion was for protocol-specific advice.  I don't know
how to write that in a generic way.  If you have specific text you
want, I can evaluate.  Your suggestion here, however, is one for which
I don't know the response.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From superuser@gmail.com  Fri Aug 30 13:18:14 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8EF111E80FA; Fri, 30 Aug 2013 13:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.48
X-Spam-Level: 
X-Spam-Status: No, score=-2.48 tagged_above=-999 required=5 tests=[AWL=0.119,  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 LklqU-Q9jUj4; Fri, 30 Aug 2013 13:18:14 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by ietfa.amsl.com (Postfix) with ESMTP id 03DED21F9E91; Fri, 30 Aug 2013 13:18:13 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id hi5so2279867wib.16 for <multiple recipients>; Fri, 30 Aug 2013 13:18: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=cL2j6x/kydBfMQn/+bTAowui5gMcF6vID4o5oSIxNjk=; b=M8lXpPZWRaPzSu8iJmAnU0fQtObt9jCvk+N3JIHWClvCLOC38M9NTihgjKOwz3m16N 4zXTY1IPX8rf1kRF6CmIiLNM2aAV5DEB6ok+iUh8WWcT11OZhZg96Z+a41Fd4bMU+V7p iZgFEi8YzzIrbVUh44qpCvDmkgD6wGYV1FpA72L48wmLtpUFJraylA2yNmdyGx9SH0BA ekhsHXr2zsKZmKtJSGwowMnM6KTt9+zR34VZJYcuD3fbV55iwTnakm6N5G26T77UYdXq xbx4V6Z7LWRXOI3O3XBCctpb0zqeQHz7HrQk758R0rSyCWPMBegp6KgP1RpgM2XOvCK/ 1Kcg==
MIME-Version: 1.0
X-Received: by 10.180.189.9 with SMTP id ge9mr3832624wic.52.1377893893133; Fri, 30 Aug 2013 13:18:13 -0700 (PDT)
Received: by 10.180.75.144 with HTTP; Fri, 30 Aug 2013 13:18:12 -0700 (PDT)
In-Reply-To: <20130830192034.GP56500@mx1.yitter.info>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <20130830192034.GP56500@mx1.yitter.info>
Date: Fri, 30 Aug 2013 13:18:12 -0700
Message-ID: <CAL0qLwb+F2yAN=+fz7h0bKFgxDfGcK_=Nskw2Ek_H9BgEcVc9A@mail.gmail.com>
Subject: Re: AppsDir review of draft-ietf-repute-model-08
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a11c3430209de9404e52fec22
Cc: ietf <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 20:18:15 -0000

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

On Fri, Aug 30, 2013 at 12:20 PM, Andrew Sullivan <ajs@anvilwalrusden.com>wrote:

> On Fri, Aug 30, 2013 at 02:37:13PM -0400, Hector Santos wrote:
> > For example, DKIM-REPUTE product designers would need to consider
> > SPF reputons product models.  Simple text as follows can resolve the
> > integration consideration with little SPF fanfare the draft
> > obviously tried to avoid:
>
> Why should the framework document contain details of how various
> particular reputation services interact?  If you want a discussion of
> reputation-service-interaction mechanisms in the draft, that's one
> thing.  If you want to talk about how SPF and DKIM interact, then I
> think this is probably the wrong draft.
>
>
The document we're talking about here only describes a general
architecture.  DKIM is present in the document for illustration purposes
only; it doesn't limit REPUTE to being used by DKIM.  The more
protocol-specific stuff, which already does include SPF support, is in
draft-ietf-repute-email-identifiers.

-MSK

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

<div dir=3D"ltr">On Fri, Aug 30, 2013 at 12:20 PM, Andrew Sullivan <span di=
r=3D"ltr">&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">a=
js@anvilwalrusden.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><=
div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Fri, Aug 30, 2013 at 02=
:37:13PM -0400, Hector Santos wrote:<br>
&gt; For example, DKIM-REPUTE product designers would need to consider<br>
&gt; SPF reputons product models. =A0Simple text as follows can resolve the=
<br>
&gt; integration consideration with little SPF fanfare the draft<br>
&gt; obviously tried to avoid:<br>
<br>
</div>Why should the framework document contain details of how various<br>
particular reputation services interact? =A0If you want a discussion of<br>
reputation-service-interaction mechanisms in the draft, that&#39;s one<br>
thing. =A0If you want to talk about how SPF and DKIM interact, then I<br>
think this is probably the wrong draft.<br>
<br></blockquote><div><br></div><div>The document we&#39;re talking about h=
ere only describes a general architecture.=A0 DKIM is present in the docume=
nt for illustration purposes only; it doesn&#39;t limit REPUTE to being use=
d by DKIM.=A0 The more protocol-specific stuff, which already does include =
SPF support, is in draft-ietf-repute-email-identifiers.<br>
<br>-MSK<br></div></div></div></div>

--001a11c3430209de9404e52fec22--

From ynir@checkpoint.com  Fri Aug 30 13:39:00 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8C811E8128 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 13:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.64
X-Spam-Level: 
X-Spam-Status: No, score=-10.64 tagged_above=-999 required=5 tests=[AWL=-0.041, 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 dxVCAQ0a5q0P for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 13:38:54 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3ED11E8125 for <ietf@ietf.org>; Fri, 30 Aug 2013 13:38:53 -0700 (PDT)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r7UKcZ05031187; Fri, 30 Aug 2013 23:38:35 +0300
X-CheckPoint: {522102CB-1C-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.173]) by IL-EX10.ad.checkpoint.com ([169.254.2.246]) with mapi id 14.02.0347.000; Fri, 30 Aug 2013 23:38:35 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Subject: Re: Mail lost yesterday
Thread-Topic: Mail lost yesterday
Thread-Index: AQHOpSBh8IdrNaBvMUmFFpPX/ureUpmtMreAgABqqwCAAGfegA==
Date: Fri, 30 Aug 2013 20:38:34 +0000
Message-ID: <1E900DFE-7FC9-4F81-B999-26E0907A6216@checkpoint.com>
References: <521F8A93.2090309@venaas.com> <9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <EMEW3|025851ca777aedbd6e4d3205eef397c0p7SN4A03tjc|ecs.soton.ac.uk|9A7DF530-2363-4CCB-A1DC-69DCBB4BF89C@ecs.soton.ac.uk> <6.2.5.6.2.20130829152744.0cd688b0@resistor.net> <17D27131-B1B7-479C-9BCF-FBD7D259A992@gmail.com> <6.2.5.6.2.20130829163103.0c665800@resistor.net> <7E2F95D4-C5C2-449D-AF32-5DB513ABBCB2@gmail.com> <6.2.5.6.2.20130829173539.0cd44070@resistor.net> <EA3F6C2F-B353-4E2F-8C2D-805E2FC9ED46@piuha.net> <6.2.5.6.2.20130830053743.0c9031d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130830053743.0c9031d0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.30]
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ED86D1F9372385438628A090A66F645F@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 20:39:00 -0000

On Aug 30, 2013, at 5:26 PM, SM <sm@resistor.net> wrote:
>=20
> The nit is why is the IETF still using PDT.

Because we don't want to get into a religious war of GMT vs UTC.

From hsantos@isdg.net  Fri Aug 30 13:45:50 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 633A221F9FB6 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 13:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.004
X-Spam-Level: 
X-Spam-Status: No, score=-102.004 tagged_above=-999 required=5 tests=[AWL=-0.327, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lLG-23tdDnQL for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 13:45:45 -0700 (PDT)
Received: from ftp.catinthebox.net (groups.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 02D0521F9E99 for <ietf@ietf.org>; Fri, 30 Aug 2013 13:45:44 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1084; t=1377895541; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=S+ZE0gfW06CgeXN27JlTze1AXaI=; b=Uu5XCu9U2vLy3fT2txvj kkO0lV0+rH/Yny/gYWFebTkOFIU8nIouD567roP4kLLlD1Sl42oU26WBc+1RPx8m kBRCdyT1EpsQ0eUvQUpQBv9ITJNbrzRWk+oIhdaUKa4xr1iOSVqgjSSohPUEpVy5 14VrhLrs5pnyXUD5fS0mFtE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 16:45:41 -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 63081300.13298.2728; Fri, 30 Aug 2013 16:45:41 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1084; t=1377895217; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=4wxD8WU NFVM5Qitx2NFTABp7Tt57ZDl8AxzQ0UcP+IU=; b=MXrJpHCLp9cAM3GhyBiKVw5 nnqn3c6VNMPJGeHgc0nNvD3UpjyP1Xmhv5RNbSj5YVcr1o+bvAyDv7X8+nnWNl+o oHtlSyWXNLUSy7MXLDTPvG/gFNM5ZXV+tvv9F5PS7p5ENgPJu6SCOtzsVW2fkNvZ hxeWDl3yMTPLIYAOKeug=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 30 Aug 2013 16:40:17 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3804465533.9.2216; Fri, 30 Aug 2013 16:40:16 -0400
Message-ID: <52210470.1080905@isdg.net>
Date: Fri, 30 Aug 2013 16:45:36 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: AppsDir review of draft-ietf-repute-model-08
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <20130830192034.GP56500@mx1.yitter.info> <5220F4E2.7030005@isdg.net> <20130830200920.GS56500@mx1.yitter.info>
In-Reply-To: <20130830200920.GS56500@mx1.yitter.info>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 20:45:51 -0000

On 8/30/2013 4:09 PM, Andrew Sullivan wrote:
> On Fri, Aug 30, 2013 at 03:39:14PM -0400, Hector Santos wrote:
>
>> archives of the Repute WG to find or extract these very real and
>> practical integration considerations.  The document should have
>> these general considerations summarized.
>
> But your suggestion was for protocol-specific advice.  I don't know
> how to write that in a generic way.  If you have specific text you
> want, I can evaluate.

I had the start of one in my original post:

    REPUTE protocols based on this framework need to consider reputons
    based on SMTP level filtering protocols such SPF [RFC4408],
    IP based filtering [DNSRBL] or others.

If too specific (but explain why DKIM is mentioned?), then

    REPUTE protocols based on this framework should consider any
    reputons based on SMTP level filtering protocols in their designs.

with and/or:

    The design consideration for operations may necessitate disabling
    or relaxing SMTP level filters in order to enable filtering based
    on this DKIM-REPUTE model.

Thanks

-- 
HLS



From tony@att.com  Fri Aug 30 15:26:52 2013
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 4162E21F9EC4; Fri, 30 Aug 2013 15:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.738
X-Spam-Level: 
X-Spam-Status: No, score=-105.738 tagged_above=-999 required=5 tests=[AWL=-0.431, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z8E8HxO9N8LA; Fri, 30 Aug 2013 15:26:45 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 1756E21F9EBE; Fri, 30 Aug 2013 15:26:45 -0700 (PDT)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 22c11225.0.4226721.00-228.11656772.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>);  Fri, 30 Aug 2013 22:26:45 +0000 (UTC)
X-MXL-Hash: 52211c250229014d-a4f7a0e8c0cdd78a7ace08e3e3b044596b8bb2d6
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UMQfbf025343; Fri, 30 Aug 2013 18:26:42 -0400
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UMQPIc025217 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Aug 2013 18:26:34 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi131.aldc.att.com (RSA Interceptor); Fri, 30 Aug 2013 22:26:16 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UMQFqi003498; Fri, 30 Aug 2013 18:26:15 -0400
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id r7UMQ7e7003296; Fri, 30 Aug 2013 18:26:10 -0400
Received: from [135.70.221.184] (vpn-135-70-221-184.vpn.east.att.com[135.70.221.184]) by maillennium.att.com (mailgw1) with ESMTP id <20130830222601gw1004nhaee> (Authid: tony); Fri, 30 Aug 2013 22:26:06 +0000
X-Originating-IP: [135.70.221.184]
Message-ID: <52211BF8.80907@att.com>
Date: Fri, 30 Aug 2013 18:26:00 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
Subject: Re: AppsDir review of draft-ietf-repute-model-08
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net>
In-Reply-To: <5220E659.1070906@isdg.net>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=UTF-8
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.229.23]
X-AnalysisOut: [v=2.0 cv=EZl/toaC c=1 sm=0 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=GibGvsWJ3EMA:10 a=sCfsyOEanakA:10 a=SRphlgSVIREA:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=IkcTkHD0fZMA:10 a=zQP7CpK]
X-AnalysisOut: [OAAAA:8 a=D1GT84r3OkIA:10 a=RoLo4V4g0zLiQJr0MqQA:9 a=QEXdD]
X-AnalysisOut: [O2ut3YA:10]
Cc: draft-ietf-repute-model.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>, General discussion of application-layer protocols <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 22:26:52 -0000

On 8/30/2013 2:37 PM, Hector Santos wrote:
> On 8/30/2013 10:46 AM, Tony Hansen wrote:
>>
>> The document describes a model for reputation services, particularly
>> those being produced by the Repute WG. It follows the recommendations
>> of RFc4101 for describing a protocol model, which requires answers to
>> 1) the problem the protocol is trying to achieve, 2) the meaning of
>> messages transmitted, and 3) important unobvious features of the
>> protocol. This document accomplishes its goals quite well.
>
> As a high potential implementator of this DKIM-REPUTE framework and
> user of any future REPUTE products based on this DKIM-REPUTE
> framework, I am somewhat disappointed to find not a single integration
> consideration for the highly adopted SPF technology.  Not a single
> mentioning of the word or the integrated use of this highly adopted
> mail transport augmented technology.  ...

Hector, what you're suggesting would be fine for a document that
specifically was written about reputation servers for email services.
But draft-ietf-repute-model is not the place for it.

While draft-ietf-repute-model does contain an example of how a
reputation service could be used to help assess a DKIM identifier, that
is not the thrust of this document.

RFC 4101 (Writing Protocol Models) contains this advice:

    3.2 Abstraction is good
    ... try to abstract away pieces ...
    3.3 A few well-chosen details sometimes help
    ... it's often a good approach to talk about the material in the
abstract and
    then provide a concrete description of one specific piece to bring
it into focus. ...

The DKIM example is just that, an example of one way the model could be
used. It is strictly illustrative and not exclusionary in any way.

    Tony Hansen

From doug.mtview@gmail.com  Fri Aug 30 16:24:22 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763CD21E808F; Fri, 30 Aug 2013 16:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[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 p9YMcmrxwIow; Fri, 30 Aug 2013 16:24:22 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0107C21E8082; Fri, 30 Aug 2013 16:24:21 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so2447379pdj.29 for <multiple recipients>; Fri, 30 Aug 2013 16:24:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=tXTYvHVqzvg35hizl4RCZ07gMCmiPV19J+oa6MuMOKM=; b=lkavhXKf+oSS87DF8y0oTB3mY4uSOCU/7yDJLdTLmMNHbB5hERoybgK34CUp8HSAKb aZYm8QEPR8X+HQBCfsIKHVVa/RoMN8ztfQ07AeAFsOiVZ+o1dRpHa4cV9PjleVrVDLeD sXtrBXaHmiKiuWIMr/bCLiuGSu6lBMbGU+l8ZJUPXmsmh8SpCOXicL7lu+8KpYe37WmK ztd/A+SYMe4zf1+4I0qkCtXeSK4xexsYh9koAWzwk1WERBCyh3r06sPpp43zhPZPlLLF givhD1AdqOFQnRZPizm8H5MLk+DT5x5fXoWYM9Fy9H2B40Hf0Z7cWft6PxZyGhu/QU56 nVvg==
X-Received: by 10.68.228.230 with SMTP id sl6mr12485359pbc.98.1377905061766; Fri, 30 Aug 2013 16:24:21 -0700 (PDT)
Received: from [192.168.2.201] (c-24-6-103-174.hsd1.ca.comcast.net. [24.6.103.174]) by mx.google.com with ESMTPSA id tr10sm332391pbc.22.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 30 Aug 2013 16:24:20 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A1B8A873-E72A-4726-95DC-CB77011E11A6"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: AppsDir review of draft-ietf-repute-model-08
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <52211BF8.80907@att.com>
Date: Fri, 30 Aug 2013 16:24:17 -0700
Message-Id: <F9E6B2DA-0FD7-497E-BDF9-24AD5B5E32AA@gmail.com>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <52211BF8.80907@att.com>
To: Tony Hansen <tony@att.com>
X-Mailer: Apple Mail (2.1508)
Cc: draft-ietf-repute-model.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>, General discussion of application-layer protocols <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2013 23:24:22 -0000

--Apple-Mail=_A1B8A873-E72A-4726-95DC-CB77011E11A6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear Tony,

Use of DKIM offers a very poor authentication example, since this draft =
makes the same errors made in RFC5863.  It is wrong to suggest the DKIM =
protocol permits associating a validated identifier to a message as =
stated in the Introduction.  This is the same erroneous conflation of a =
message fragment with that of a message.  In most cases, DKIM does not =
adequately protect message integrity as explained in =
http://tools.ietf.org/html/draft-otis-dkim-harmful-03.  In addition, =
DKIM can not authenticate who is accountable for having sent the message =
which makes it impossible to safely assign reputation.  As such, DKIM =
should never be referred to as a message authentication protocol.  =
StartTLS would represent a much better example.=20

Regards,
Douglas Otis=

--Apple-Mail=_A1B8A873-E72A-4726-95DC-CB77011E11A6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Dear =
Tony,</div><div><br></div>Use of DKIM offers a very poor authentication =
example, since this draft makes the same errors made in RFC5863. =
&nbsp;It is wrong to suggest the DKIM&nbsp;protocol&nbsp;permits =
associating a validated identifier to a message as stated in the =
Introduction. &nbsp;This is the same erroneous conflation of a message =
fragment with that of a message. &nbsp;In most cases, DKIM does not =
adequately protect message integrity as explained in <a =
href=3D"http://tools.ietf.org/html/draft-otis-dkim-harmful-03">http://tool=
s.ietf.org/html/draft-otis-dkim-harmful-03</a>. &nbsp;In addition, DKIM =
can not authenticate who is accountable for having sent the message =
which makes it impossible to safely assign reputation. &nbsp;As such, =
DKIM should never be referred to as a message authentication protocol. =
&nbsp;StartTLS would represent a much better =
example.&nbsp;<div><br></div><div>Regards,</div><div>Douglas =
Otis</div></body></html>=

--Apple-Mail=_A1B8A873-E72A-4726-95DC-CB77011E11A6--

From ajs@anvilwalrusden.com  Fri Aug 30 16:39:32 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3E921E8091; Fri, 30 Aug 2013 16:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level: 
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[AWL=0.006,  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 9FV09qDXPfGo; Fri, 30 Aug 2013 16:39:27 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id F10B921E8082; Fri, 30 Aug 2013 16:39:26 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id D24F18A031; Fri, 30 Aug 2013 23:39:25 +0000 (UTC)
Date: Fri, 30 Aug 2013 19:39:24 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, apps-discuss@ietf.org
Subject: Re: AppsDir review of draft-ietf-repute-model-08
Message-ID: <20130830233923.GY56500@mx1.yitter.info>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <52211BF8.80907@att.com> <F9E6B2DA-0FD7-497E-BDF9-24AD5B5E32AA@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <F9E6B2DA-0FD7-497E-BDF9-24AD5B5E32AA@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: Fri, 30 Aug 2013 23:39:32 -0000

Hi Doug!

On Fri, Aug 30, 2013 at 04:24:17PM -0700, Douglas Otis wrote:

> Use of DKIM offers a very poor authentication example

Thanks for the feedback.  I don't recall you having made this point on
the repute mailing list.  Did you, & I missed it?

Do you have a better example, specifically excluding â€¦

> StartTLS would represent a much better example.

â€¦this, which strikes me as suffering from a different but related set
of issues along the lines you're complaining about?

Alternatively, if we recast the description of DKIM to call it
something else, but still used it as an example of what REPUTE is
trying to do, would that solve your objection?

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@elandsys.com  Fri Aug 30 17:53:29 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41D411E80A2; Fri, 30 Aug 2013 17:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qgKFub29KgCa; Fri, 30 Aug 2013 17:53:27 -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 AE03321F9DD5; Fri, 30 Aug 2013 17:53:26 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.70]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7V0pUuK001627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Aug 2013 17:51:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377910304; bh=omB6O6MlRFZaimTEi9YY0KUB3cD91Nimvnx460GkCIY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Pzk2ZRoCH3qL8RDRWw5hhFoN8xvgwbflKOhkuLY5/bqQES1ry7jI3ODidEzETRciv 9tF8a58zQP7YUv0X22J7Ozo+bgH8N+qJwEeHHJkJ89PsI8KxMCYMZTpgryZNA8clRe uhiiyo8Rrm5CPywMb9EA0XGIgP6DqJdECrMRfWRM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377910304; i=@elandsys.com; bh=omB6O6MlRFZaimTEi9YY0KUB3cD91Nimvnx460GkCIY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=j6e9mIZWkIX90QjU4OxJWfry6ZaxVXBS7o+850T7/9EE0RDjcpktD3qAKYxTKq+S3 yz4mpT+nctuBO+z7MzfkKxDiQkt3ORUWbEywbq6Asi9jPq6XB7cIu3BDz8oaoF0DcO ZCO7L7i0O/DXB7ktA3zBKkeP/kh5+8uexGlUlj54=
Message-Id: <6.2.5.6.2.20130830172652.06409ab8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Aug 2013 17:46:51 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: AppsDir review of draft-ietf-repute-model-08
In-Reply-To: <52211BF8.80907@att.com>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <52211BF8.80907@att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Claudio Allocchio <Claudio.Allocchio@garr.it>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 00:53:29 -0000

Hello,

After reading the reviews of the Application Area Directorate review 
it seems to me that there is some misunderstanding of what an 
Application Area Directorate review is about.  The review is to give 
the Applications Area Directors a sense of how important it is that 
they pay attention to a draft.

If there is a problem with a working group draft that problem should 
be taken up with the working group instead of the Applications Area 
Directorate reviewer.  If there is a problem with the Applications 
Area Directorate review it is okay in my opinion to discuss about 
that with the reviewer.

Regards,
S. Moonesamy


From sm@elandsys.com  Fri Aug 30 18:18:41 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E078E21E80A1 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 18:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id auByBYCVJjUd for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 18:18: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 02F7721E8082 for <ietf@ietf.org>; Fri, 30 Aug 2013 18:18:40 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.70]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7V1IQJa020263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 30 Aug 2013 18:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377911918; bh=OKUfiZPlR/NnqoeMDRJ4haTLLJdJaaiiQhAoIHMzCzQ=; h=Date:To:From:Subject:In-Reply-To:References; b=Ni/LkQ/x+Qdh1xRhwdLxxEhornuYTKGTLT5gsF9DoZFMP/o7GXUJRx4YLOlwKyGz+ D8eim9H1bzm6b1IdOhRN2pnxAJFZwyMWUay9x9tnJC5aSceIIzk5CB95RNfM8Nw1n+ 3mtseHlZ0P43zY4zRQdwfdQxwh6yvK2Qx09Ev2QM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377911918; i=@elandsys.com; bh=OKUfiZPlR/NnqoeMDRJ4haTLLJdJaaiiQhAoIHMzCzQ=; h=Date:To:From:Subject:In-Reply-To:References; b=hAdQRoZkbIy0h77jQZV5eGrFkmZ5apoT6C3zWZ2cvMnFOPigOZEi82AtL4hPPq1mi pDPAUjDINHd55P3/3+uEzpVO9TQJdO6hJe1u5mfoNwFbJ+x3mhfw1+msPzZSlzaMrS wmUsJ5Oq4lD1MddWmh9FL6E02arEpgdPFHZXI4hM=
Message-Id: <6.2.5.6.2.20130830175621.0c9472d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Aug 2013 18:17:02 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: WG Review: Dynamic Host Configuration (dhc)
In-Reply-To: <20130830165300.16729.46895.idtracker@ietfa.amsl.com>
References: <20130830165300.16729.46895.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 01:18:42 -0000

Hello,
At 09:53 30-08-2013, The IESG wrote:
>The Dynamic Host Configuration (dhc) working group in the Internet Area
>of the IETF is undergoing rechartering. The IESG has not made any

[snip]

>Milestones:
>   Done     - WG Last Call on DHCP Options for Internet Storage Name
>Service (draft-ietf-dhc-isnsoption-03.txt)
>   Done     - WG Last Call on Load Balancing for DHCPv6
>(draft-ietf-dhc-dhcpv6-loadb-02.txt)
>   Done     - WG Last Call on Time Configuration Options for DHCPv6
>(draft-ietf-dhc-dhcpv6-opt-timeconfig-01.txt)
>   Done     - WG Last Call on IPv6 Prefix Options for DHCPv6
>(draft-troan-dhcpv6-opt-prefix-delegation-02.txt)
>   Done     - WG Last Call on DNS Configuration options for DHCPv6
>(draft-ietf-dhc-dhcpv6-opt-dnsconfig-01.txt)
>   Done     - WG Last Call on NIS Configuration Options for DHCPv6
>(draft-ietf-dhc-dhcpv6-opt-nisconfig-01.txt)
>   Done     - Resubmit draft-ietf-dhc-dhcpv6-28.txt to IESG
>   Done     - Identify DHCPv4 authentication design team
>   Done     - Identify DHCPv4 specification review design team
>   Done     - Identify DHCPv4 relay agent message authentication design
>team
>   Done     - Submit DHCP Options for Internet Storage Name Service to
>IESG (draft-ietf-dhc-isnsoption)
>   Done     - Submit DNS Configuration options for DHCPv6 to IESG
>(draft-ietf-dhc-dhcpv6-opt-dnsconfig)
>   Done     - Submit NIS Configuratio Options for DHCPv6 to IESG
>(draft-ietf-dhc-dhcpv6-opt-nisconfig)
>   Done     - Submit IPv6 Prefix Options for DHCPv6 to IESG
>(draft-troan-dhcpv6-opt-prefix-delegation)
>   Done     - Submit 'Detection of Network Attachment (DNA) in IPv4' to
>IESG (draft-ietf-dhc-dna-ipv4)
>   Done     - Resolve IPR issues around 'Rapid Commit Option for DHCPv4'
>   Done     - Publish report on dual-stack issues in DHCP
>(draft-ietf-dhc-dual-stack)
>   Done     - Publish report on requirements for renumbering using
>stateless  DHCPv6 (draft-ietf-dhc-stateless-dhcpv6-renumbering)
>   Done     - Submit 'Lifetime Option for DHCPv6' to IESG
>(draft-ietf-dhc-lifetime)
>   Done     - Submit 'Rapid Commit Option for DHCPv4' to IESG
>(draft-ietf-dhc-rapid-commit-opt)
>   Done     - Submit DDNS/DHCP documents to IESG
>   Done     - Submit 'Node-Specific Client Identifiers for DHCPv4' to IESG
>(draft-ietf-dhc-3315id-for-v4)
>   Done     - WG last call for 'Subnet Allocation Option'
><draft-ietf-dhc-subnet-alloc-04>
>   Done     - WG last call on 'Virtual Subnet Selection Option'
><draft-ietf-dhc-vpn-option>
>   Oct 2007 - Submit 'Subnet Allocation Option'
>(draft-ietf-dhc-subnet-alloc-04) to IESG for Proposed Standard
>   Nov 2007 - WG last call on 'Guidelines for Creating New DHCP Options'
>(draft-ietf-dhc-option-guidelines)
>   Nov 2007 - Submit 'Virtual Subnet Selection Option',
>(draft-ietf-dhc-vpn-option) and (draft-ietf-dhc-agent-vpn-id) to IESG for
>Proposed Standard
>   Dec 2007 - WG last call for 'Domain Suffix Option for DHCPv6'
>(draft-ietf-dhc-dhcpv6-opt-dnsdomain)
>   Jan 2008 - Submit 'Domain Suffix Option for DHCPv6'
>(draft-ietf-dhc-dhcpv6-opt-dnsdomain) to IESG for Proposed Standard
>   Jan 2008 - Submit 'Guidelines for Creating New DHCP Options'
>(draft-ietf-dhc-option-guidelines) to IESG for Best Current Practice
>   Jan 2008 - Develop plan for advancing DHCPv4 and DHCPv6 plan to include
>completion of DHCPv4 specification review report, 'Implementation Issues
>with RFC 2131' (draft-ietf-dhc-implementation) for Informational
>   Feb 2008 - WG last call for 'Status of Reclassifying DHCPv4 Options'
>(draft-ietf-dhc-status-3942)
>   Feb 2008 - WG last call for 'Dual-stack clients and merging of data
>from DHCPv4 and DHCPv6' (draft-ietf-dhc-dual-stack-merge); waiting for
>more experience with IPv6 deployment
>   Feb 2008 - WG last call for 'Rebind Capability in DHCPv6 Reconfigure
>Messages'  (draft-ietf-dhc-dhcpv6-reconfigure-rebind)
>   Mar 2008 - Submit 'Status of Reclassifying DHCPv4 Options'
>(draft-ietf-dhc-status-3942) to IESG for Informational
>   Apr 2008 - 2nd WG last call for 'DHCP Relay Agent Assignment
>Notification Option (draft-ietf-dhc-dhcpv6-agentopt-delegate) and 'DHCPv6
>Server Reply Sequence Number Option'  (draft-ietf-dhc-dhcpv6-srsn-option)
>   May 2008 - Submit 'Rebind Capability in DHCPv6 Reconfigure Messages'
>(draft-ietf-dhc-dhcpv6-reconfigure-rebind) to IESG for Proposed Standard
>   Jun 2008 - WG last call on 'Layer 2 Relay Agent Behaviour'
>(draft-ietf-dhc-layer2-relay-agent)
>   Jul 2008 - Submit 'Layer 2 Relay Agent Behaviour' to IESG
>(draft-ietf-dhc-layer2-relay-agent) for Informational
>   Jul 2008 - Submit 'DHCP Relay Agent Assignment Notification Option'
>(draft-ietf-dhc-dhcpv6-agentopt-delegate) and 'DHCPv6 Server Reply
>Sequence Number Option' (draft-ietf-dhc-dhcpv6-srsn-option) to IESG for
>Proposed Standard
>   Jul 2008 - Recharter, if needed

Did the DHC working group read the milestones?  I ask because it's 
been a few years since the year 2008 ended.

I looked at the last draft mentioned above.  The last revision is 
dated February 2009.  The DHC working group was supposed to deliver 
that draft to the IESG in July 2008.

I looked up draft-ietf-dhc-container-opt-07.  The state as at April 
2013 mentions "WG Document Revised I-D Needed - Issue raised by 
WGLC".  There is a note which says: "This document did NOT pass WGLC 
as there was no support for it and Ralph indicated that there were 
several IESG Discusses from several years ago (2009) that did not get 
addressed".

Regards,
S. Moonesamy  


From ajs@anvilwalrusden.com  Fri Aug 30 19:51:04 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0AF121F9ADD; Fri, 30 Aug 2013 19:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.834
X-Spam-Level: 
X-Spam-Status: No, score=-0.834 tagged_above=-999 required=5 tests=[AWL=0.006,  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 g99UGEnrsRpb; Fri, 30 Aug 2013 19:50:58 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id D172D21F9AA7; Fri, 30 Aug 2013 19:50:58 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 379158A031; Sat, 31 Aug 2013 02:50:56 +0000 (UTC)
Date: Fri, 30 Aug 2013 22:50:54 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org, apps-discuss@ietf.org
Subject: Re: [apps-discuss] AppsDir review of draft-ietf-repute-model-08
Message-ID: <20130831025054.GC58179@mx1.yitter.info>
References: <5220B055.2000704@att.com> <5220E659.1070906@isdg.net> <52211BF8.80907@att.com> <F9E6B2DA-0FD7-497E-BDF9-24AD5B5E32AA@gmail.com> <20130830233923.GY56500@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20130830233923.GY56500@mx1.yitter.info>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 02:51:04 -0000

Colleagues, and Doug especially,

The message I sent (below) wasn't intended as a "shut up and go away"
message, but a genuine query.  I have grave doubts that TLS is the
right example (to begin with, I think fitting it into the REPUTE
approach, given the existing CA structure, would also be
controversial); but I'm genuinely trying to understand how to make the
document better, & not trying to tell anyone to go away.

Best,

A

On Fri, Aug 30, 2013 at 07:39:24PM -0400, Andrew Sullivan wrote:
> Hi Doug!
> 
> On Fri, Aug 30, 2013 at 04:24:17PM -0700, Douglas Otis wrote:
> 
> > Use of DKIM offers a very poor authentication example
> 
> Thanks for the feedback.  I don't recall you having made this point on
> the repute mailing list.  Did you, & I missed it?
> 
> Do you have a better example, specifically excluding â€¦
> 
> > StartTLS would represent a much better example.
> 
> â€¦this, which strikes me as suffering from a different but related set
> of issues along the lines you're complaining about?
> 
> Alternatively, if we recast the description of DKIM to call it
> something else, but still used it as an example of what REPUTE is
> trying to do, would that solve your objection?
> 
> Best,
> 
> A
> 

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Ted.Lemon@nominum.com  Fri Aug 30 20:00:03 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF8621F9BEB for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 20:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AudzEQQxpg2e for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 19:59:58 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id DE54A21F9CD9 for <ietf@ietf.org>; Fri, 30 Aug 2013 19:59:57 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUiFcLL/JxxRmazOMN5xxktG2SlB74Fu+@postini.com; Fri, 30 Aug 2013 19:59:57 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6110A1B8149 for <ietf@ietf.org>; Fri, 30 Aug 2013 19:59:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CAEA4190078; Fri, 30 Aug 2013 19:59:53 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 30 Aug 2013 19:59:46 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: WG Review: Dynamic Host Configuration (dhc)
Thread-Topic: WG Review: Dynamic Host Configuration (dhc)
Thread-Index: AQHOpegR6SC/1YgJIUS2S4zKzP/NYZmvFdWA
Date: Sat, 31 Aug 2013 02:59:46 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077526EBD8@mbx-01.win.nominum.com>
References: <20130830165300.16729.46895.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130830175621.0c9472d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130830175621.0c9472d0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <2BA8E83B85525A4CA0967A843868A1C6@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 03:00:03 -0000

On Aug 30, 2013, at 9:17 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Did the DHC working group read the milestones?  I ask because it's been a=
 few years since the year 2008 ended.

Yes.   The minutes have been updated in the datatracker: https://datatracke=
r.ietf.org/wg/dhc/charter/

I don't know why this didn't show up in the announcement message.   Actuall=
y, the announcement really ought to just point to the datatracker, since wh=
at's there is normative.

The container option draft is not considered particularly pressing at the m=
oment=97there was some renewed interest in it a couple of IETFs ago, but I =
don't think it's gone anywhere.


From sm@elandsys.com  Fri Aug 30 21:11:32 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678CE21F9C42 for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 21:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6m-LbYKmYF+m for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 21:11:28 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63F2421F93E4 for <ietf@ietf.org>; Fri, 30 Aug 2013 21:11:26 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.70]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7V4B2q5015264 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Aug 2013 21:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377922276; bh=9HDNCz5WeT03TmUCsO6dNKgq/abbeU/9PVBv7JZZhiA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4JXKDEZFslkT+pi+UyTthNRpHwc55HtgJOAYVeff8cRuqnnffFUHBC0oO+k/R+80z JthRRRJRsJD/h1jSjzTIVyX6QVHcCaC0E5bEjD0sv9mCV1HB/bQiTz+ZTSz4oFqaZt x5lUa/uPJhm5qbiby6wT9JF9wKqYuM/ykk+B8R88=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377922276; i=@elandsys.com; bh=9HDNCz5WeT03TmUCsO6dNKgq/abbeU/9PVBv7JZZhiA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AP6yO7auLzX3/6MwBKK9g2/ajFGgJB/2iibvzL5UXsLmsCEQGidQZRy+aqVIZmQqR oiUp50uaXoNnQQ+FUhFiTX79GLIVGZLNQHlECGLJ/9zyEkGO/ceK7yIIXgcBBSDebI zCX/I/EFDOPztJ4czDIrHQj83jh5Ks25FfNq3HUE=
Message-Id: <6.2.5.6.2.20130830204418.0c34faf8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 30 Aug 2013 21:10:25 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Is the datatracker authoritative (was: WG Review: Dynamic Host Configuration (dhc))
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077526EBD8@mbx-01.win.nominu m.com>
References: <20130830165300.16729.46895.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130830175621.0c9472d0@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077526EBD8@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 04:11:32 -0000

Hi Ted,
At 19:59 30-08-2013, Ted Lemon wrote:
>Yes.   The minutes have been updated in the datatracker: 
>https://datatracker.ietf.org/wg/dhc/charter/

Thanks.

>I don't know why this didn't show up in the announcement 
>message.   Actually, the

I assumed that the message was generated by the datatracker.

>  announcement really ought to just point to the datatracker, since 
> what's there is normative.

This is an individual opinion.  Please assume that the entire IETF 
disagrees with it.  The datatracker is not the authoritative version 
of a charter.  It is the message archived in the relevant mailing 
list which is considered as authoritative.  The rationale is related 
to note of record.

Regards,
S. Moonesamy 


From ajs@anvilwalrusden.com  Fri Aug 30 22:36:10 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6051C21F9D2B for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 22:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.835
X-Spam-Level: 
X-Spam-Status: No, score=-0.835 tagged_above=-999 required=5 tests=[AWL=0.005,  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 3YJxK0kRDQmC for <ietf@ietfa.amsl.com>; Fri, 30 Aug 2013 22:35:57 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8C721F9CE3 for <ietf@ietf.org>; Fri, 30 Aug 2013 22:35:56 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 292B78A031 for <ietf@ietf.org>; Sat, 31 Aug 2013 05:35:56 +0000 (UTC)
Date: Sat, 31 Aug 2013 01:35:51 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Is the datatracker authoritative (was: WG Review: Dynamic Host Configuration (dhc))
Message-ID: <20130831053551.GA20837@mx1.yitter.info>
References: <20130830165300.16729.46895.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130830175621.0c9472d0@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077526EBD8@mbx-01.win.nominum.com> <6.2.5.6.2.20130830204418.0c34faf8@elandnews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20130830204418.0c34faf8@elandnews.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: Sat, 31 Aug 2013 05:36:10 -0000

On Fri, Aug 30, 2013 at 09:10:25PM -0700, S Moonesamy wrote:
> At 19:59 30-08-2013, Ted Lemon wrote:

> > announcement really ought to just point to the datatracker, since
> >what's there is normative.
> 
> This is an individual opinion.  Please assume that the entire IETF
> disagrees with it.  The datatracker is not the authoritative version
> of a charter. 

Oh, my heaven, I hope this is false.  What you are proposing is that
an actually useful versioned repository from which we we pull all our
data is less "official", FSVO, than something else.  If that's true,
then the IETF has in fact siezed up in bureaucratic tape -- red or
otherwise.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jari.arkko@piuha.net  Sat Aug 31 01:59:50 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC81321E80B4 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 01:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jc1vCu2r-tqi for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 01:59:45 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4191E21E80A7 for <ietf@ietf.org>; Sat, 31 Aug 2013 01:59:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 394302CC50; Sat, 31 Aug 2013 11:59:43 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VIg1wpwmNP2u; Sat, 31 Aug 2013 11:59:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 53FED2CC46; Sat, 31 Aug 2013 11:59:42 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Is the datatracker authoritative (was: WG Review: Dynamic Host Configuration (dhc))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20130830204418.0c34faf8@elandnews.com>
Date: Sat, 31 Aug 2013 11:59:42 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E024019-4C74-4DE5-8DC9-A2E008A1BB96@piuha.net>
References: <20130830165300.16729.46895.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130830175621.0c9472d0@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077526EBD8@mbx-01.win.nominum.com> <6.2.5.6.2.20130830204418.0c34faf8@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1508)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Aug 2013 08:59:50 -0000

SM,

> I assumed that the message was generated by the data tracker.

The secretariat sends out last call and WG review messages, but the data =
comes from the tracker. For WGs, this is actually a relatively recent =
addition. A while ago the proposed charters were not tracked in the =
database. In any case, I'm not sure what happened - maybe an oversight =
in the still manual part of the process to send out the mail or maybe =
the milestone update (that was done just a few days ago) did not get =
there in time. I'm glad you noticed the issue, however! Thanks!

>> announcement really ought to just point to the datatracker, since =
what's there is normative.
>=20
> This is an individual opinion.  Please assume that the entire IETF =
disagrees with it.  The datatracker is not the authoritative version of =
a charter.  It is the message archived in the relevant mailing list =
which is considered as authoritative.  The rationale is related to note =
of record.

We try really hard to make sure various sources agree. In general, the =
amount of automation has been increasing, and we run almost everything =
just off the data tracker, so I'm hopeful that we're mostly OK. With =
some exceptions, such as this incident.

But as a practical point, I have to tell you that at least this AD can =
not remember much about documents and working groups without going =
through a database. We rely a lot on the datatracker, and the data =
tracker is also the source of the data that you see on the web site. We =
often go through e-mail on a topic as well (such as when deciding =
whether to recommend the approval of a document), but for things like =
charters the tracker really is in practice what we look at - normative =
or not.

Jari


From bmanning@isi.edu  Sat Aug 31 02:53:11 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 199A411E8136 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 02:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fy6YUQXBLEFo for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 02:53:06 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB1411E8132 for <ietf@ietf.org>; Sat, 31 Aug 2013 02:53:06 -0700 (PDT)
Received: from [192.168.1.4] (h27.129.49.24.static.bajabb.com [24.49.129.27] (may be forged)) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r7V9qKns007276 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 31 Aug 2013 02:52:31 -0700 (PDT)
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: manning bill <bmanning@isi.edu>
In-Reply-To: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com>
Date: Sat, 31 Aug 2013 02:52:20 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <35373CD9-8583-4283-952B-9ABD2141E74B@isi.edu>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@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: Sat, 31 Aug 2013 09:53:11 -0000

given the nature of the TXT RR, in particular the RDATA field,
I presume it is the path of prudence to set the barrier to registration
in this new IANA registry to be -VERY- low.

Or is the intent to create a "two" class system, registered and =
unregistered types?

/bill


On 30August2013Friday, at 6:35, John C Klensin wrote:

> Hi.
>=20
> Inspired by part of the SPF discussion but separate from it,
> Patrik, Andrew, and I discovered a shortage of registries for
> assorted DNS RDATA elements.  We have posted a draft to
> establish one for TXT RDATA.  If this requires significant
> discussion, we seek guidance from relevant ADs as to where they
> would like that discussion to occur.
>=20
> Three notes:
>=20
> * As the draft indicates, while RFC 5507 and other documents
> explain why subtypes are usually a bad idea, the registry
> definition tries to be fairly neutral on the subject -- the idea
> is to identify and register what is being done, not to pass
> judgment.=20
>=20
> * While the use of special labels (in the language of 5507,
> prefixes and suffixes) mitigates many of the issues with
> specialized use of RDATA fields, they do not eliminate the
> desirability of a registry (especially for debugging and
> analysis purposes).
>=20
> * While examining the DNS-related registries that exist today,
> we discovered that some other registries seemed to be missing
> and that the organization of the registries seemed to be
> sub-optimal.  We considered attempting a "fix everything" I-D,
> but concluded that the TXT RDATA registry was the most important
> need and that it would be unwise to get its establishment bogged
> down with other issue.  The I-D now contains a temporary
> appendix that outlines the other issues we identified.  IMO,
> thinking through the issues in that appendix, generating the
> relevant I-D(s), and moving them through the system would be a
> good exercise for someone who has little experience in the IETF
> and who is interested in IANA registries and/or DNS details.  I
> am unlikely to find time to do the work myself but would be
> happy to work with a volunteer on pulling things together.
>=20
>    best,
>      john
>=20
>=20
> ---------- Forwarded Message ----------
> Date: Friday, August 30, 2013 05:52 -0700
> From: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-klensin-iana-txt-rr-registry-00.txt
>=20
>=20
> A New Internet-Draft is available from the on-line
> Internet-Drafts directories.
>=20
>=20
> 	Title           : An IANA Registry for Protocol Uses of Data
> with the DNS TXT RRTYPE 	Author(s)       : John C Klensin
>                          Andrew Sullivan
>                          Patrik Faltstrom
> 	Filename        : draft-klensin-iana-txt-rr-registry-00.txt
> 	Pages           : 8
> 	Date            : 2013-08-30
>=20
> Abstract:
>   Some protocols use the RDATA field of the DNS TXT RRTYPE for
> holding    data to be parsed, rather than for unstructured free
> text.  This    document specifies the creation of an IANA
> registry for protocol-    specific structured data to minimize
> the risk of conflicting or    inconsistent uses of that RRTYPE
> and data field.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-klensin-iana-txt-rr-registry
>=20
> [...]


From ron.even.tlv@gmail.com  Sat Aug 31 04:30:07 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A98BF11E8141; Sat, 31 Aug 2013 04:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.015,  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 hKGuVdPg-+Ae; Sat, 31 Aug 2013 04:30:06 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E510411E8140; Sat, 31 Aug 2013 04:30:05 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id c11so389898wgh.5 for <multiple recipients>; Sat, 31 Aug 2013 04:30:05 -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 :thread-index:content-language; bh=E/xERvTptF4plyVZLXWy0wbK/w5jq5nWAfcOoGoBFO4=; b=VlFHP7tWjNBB+Jzqu7fvTMi8idPsrzQfuo7gcvQRCHGXAyXA75cIs2i2o9jWP3mfHx /UlU8oKeiHJeApv3Xi7K6k6+f+uiwGvY7AN7cHy6xDpxe06+Jowyzt0gWHkE9oKEMIWp 5vDlXTxoz1g4VoLq/5maOrYmSwRsUZZyKbLAr4lWQ1Ii8IE2rKTxNNpc2QU9WrXN3STV hfpeLPars12xRbJJRfjkLtuexYq9OXGUgVXwmNYnFdiEetSTCrZYjNnFY2qH7CROZLU7 RSSbjI38wttoJG2UHfGhmgXgh89iymoStlo6s/4aPwq3uaWictW1AmmiJyBuuAEPjTH/ 2z7g==
X-Received: by 10.180.9.69 with SMTP id x5mr6048842wia.41.1377948605046; Sat, 31 Aug 2013 04:30:05 -0700 (PDT)
Received: from RoniE ([109.67.221.133]) by mx.google.com with ESMTPSA id r6sm3346401wiw.0.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 31 Aug 2013 04:30:04 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-repute-model.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-repute-model-08
Date: Sat, 31 Aug 2013 14:27:34 +0300
Message-ID: <00bc01cea63d$186aee80$4940cb80$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BD_01CEA656.3DB8C2C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac6mPJbMGY3dBgwARLqHKWvc/8h3RA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 11:30:07 -0000

This is a multipart message in MIME format.

------=_NextPart_000_00BD_01CEA656.3DB8C2C0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I was asked to review the 08 version but my comments from 07 were not
addressed and I did not see any response. So I am resending my previous
review

As for making it a standard track document, I am not sure since it looks to
me as an overview and not standard. And there is no normative language in
the document.

Roni Even

 

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-repute-model-07

Reviewer: Roni Even

Review Date:2013-8-20

IETF LC End Date: 2013-8-29

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

Minor issues:

I was wondering why the "Further Discussion" section 9.3 is part of the
security section. I think it should be a separate section.

Nits/editorial comments:

Section 3 the end of 2nd paragraph "mechansisms" to "mechanisms"

 

 


------=_NextPart_000_00BD_01CEA656.3DB8C2C0
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.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I was asked to review =
the 08 version but my comments from 07 were not addressed and I did not =
see any response. So I am resending my previous review<o:p></o:p></p><p =
class=3DMsoNormal>As for making it a standard track document, I am not =
sure since it looks to me as an overview and not standard. And there is =
no normative language in the document.<o:p></o:p></p><p =
class=3DMsoNormal>Roni Even<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I am the =
assigned Gen-ART reviewer for this draft. For background on Gen-ART, =
please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-ietf-repute-model-07</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;8&#8211;20<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-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 an Informational =
RFC.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Major issues:<o:p></o:p></p><p =
class=3DMsoNormal>Minor issues:<o:p></o:p></p><p class=3DMsoNormal>I was =
wondering why the &#8220;Further Discussion&#8221; section 9.3 is part =
of the security section. I think it should be a separate =
section.<o:p></o:p></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal>Section 3 the end of =
2<sup>nd</sup> paragraph &#8220;mechansisms&#8221; to =
&#8220;mechanisms&#8221;<span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3Dpolicy.abstract></a><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00BD_01CEA656.3DB8C2C0--


From Ted.Lemon@nominum.com  Sat Aug 31 06:06:08 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6460321F9D23 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 06:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aW8SfEtaT18y for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 06:06:01 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 79C3121F9C60 for <ietf@ietf.org>; Sat, 31 Aug 2013 06:06:00 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUiHqN9soJgDy2OZGr4t8S/TP+CNm+Z8h@postini.com; Sat, 31 Aug 2013 06:06:00 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 23B121B814E for <ietf@ietf.org>; Sat, 31 Aug 2013 06:05:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7B993190078; Sat, 31 Aug 2013 06:05:58 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sat, 31 Aug 2013 06:05:58 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Is the datatracker authoritative (was: WG Review: Dynamic Host Configuration (dhc))
Thread-Topic: Is the datatracker authoritative (was: WG Review: Dynamic Host Configuration (dhc))
Thread-Index: AQHOpgArxPOI2lFjB0KBkkA8JvAM65mvvwMA
Date: Sat, 31 Aug 2013 13:05:57 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077526F1D9@mbx-01.win.nominum.com>
References: <20130830165300.16729.46895.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130830175621.0c9472d0@resistor.net> <8D23D4052ABE7A4490E77B1A012B63077526EBD8@mbx-01.win.nominum.com> <6.2.5.6.2.20130830204418.0c34faf8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130830204418.0c34faf8@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F4D497311EDB6B4CA199A468452792C8@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 13:06:08 -0000

On Aug 31, 2013, at 12:10 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>> announcement really ought to just point to the datatracker, since what's=
 there is normative.
>=20
> This is an individual opinion.  Please assume that the entire IETF disagr=
ees with it.  The datatracker is not the authoritative version of a charter=
.  It is the message archived in the relevant mailing list which is conside=
red as authoritative.  The rationale is related to note of record.

I have to admit that I did not expect my assertion here to be controversial=
.   The assertion is certainly true about drafts, which we do not mail to m=
ailing lists.   The charter that was mailed to the IETF mailing list is in =
fact the version that's in the datatracker, so you could argue that it's fi=
ne for the mailing list version to be normative.

However, you mentioned that there's no way to track versions of the charter=
 in the datatracker, and this is actually not true=97you can indeed track v=
ersions in the datatracker.   This is particularly useful since during the =
review process, changes are made.   So you have a version that goes out on =
the wg mailing list.   And then ultimately that gets reviewed by the IESG, =
and very typically the IESG wants changes.

In the DHC charter, there were three changes made during the IESG review pr=
ocess=97two work items were separated out as their own bullet items that ha=
d been included in larger bullet items, and two bullet items were reordered=
 and reworded to change the emphasis and restrict the scope of one of them.=
   Two of these changes were made to satisfy requests by IESG members.   Th=
e third change was made because one of the working group chairs noticed tha=
t one of the first two changes actually unintentionally excluded some work =
the chair anticipated that the working group should do.

You can actually see all of these changes by looking in the datatracker, bu=
t you would have to review the IESG mailing list and the dhc-chairs mailing=
 list to find out about them otherwise.

It's worth pointing out that the datatracker is a _lot_ more capable than i=
t used to be.   When I first started using it, I pretty much never used it,=
 because it was almost always easier to get what I needed on the tools site=
.   I still find the tools site's UI easier to work with, but the datatrack=
er has a lot of very useful functionality for tracking work as it moves thr=
ough the IETF process.   I feel very lucky that the datatracker update happ=
ened just before I became an AD, because I don't know how I would have done=
 my job without the new functionality.

So my statement was one of practicality, not one of process.   On a practic=
al level, it's easiest to have one place to go to look for things, and not =
have to look all over the place to get a sense of what has gone on.   That'=
s the datatracker.   If the IETF in fact feels that it should not be normat=
ive, I guess that's okay, but I think it's a lot more work for everyone.


From john-ietf@jck.com  Sat Aug 31 06:28:26 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34E3021F9EEE for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 06:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpUp4WmWepNn for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 06:28:20 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1D06521F9E7C for <ietf@ietf.org>; Sat, 31 Aug 2013 06:28:20 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VFlDv-000LWw-6b; Sat, 31 Aug 2013 09:28:19 -0400
Date: Sat, 31 Aug 2013 09:28:14 -0400
From: John C Klensin <john-ietf@jck.com>
To: manning bill <bmanning@isi.edu>
Subject: Re: An IANA Registry for DNS TXT RDATA  (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
Message-ID: <B6453291BFB6FFDD3C65119A@JcK-HP8200.jck.com>
In-Reply-To: <35373CD9-8583-4283-952B-9ABD2141E74B@isi.edu>
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <35373CD9-8583-4283-952B-9ABD2141E74B@isi.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: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 31 Aug 2013 13:28:26 -0000

--On Saturday, August 31, 2013 02:52 -0700 manning bill
<bmanning@isi.edu> wrote:

> given the nature of the TXT RR, in particular the RDATA field,
> I presume it is the path of prudence to set the barrier to
> registration in this new IANA registry to be -VERY- low.

That is indeed the intent.  If the document isn't clear enough
about that, text would be welcome.  I'm still searching for the
right words (and hoping that the discussion will interact in
both directions with the 5226bis effort
(draft-leiba-cotton-iana-5226bis), but our thought is that the
"expert reviewer" will provide advice and education about the
desirability of good quality registrations back up by good
quality and stable documents.  But, if the best we can get is
registrant contact info, name of a protocol, and a clue about
distinguishing information, then that is the best we can get.

> Or is the intent to create a "two" class system, registered
> and unregistered types?

In one sense, that result is inevitable because some of the
locally-developed and used stuff that lives in TXT records will
probably not be registered no matter what we do.  That is still
better than the current situation of a one-class system in which
nothing is registered.  But the intent is to get as much
registered as possible.

Again, if the I-D isn't clear, text would be welcome.

   john


From superuser@gmail.com  Sat Aug 31 07:40:02 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED29411E8119; Sat, 31 Aug 2013 07:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, 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 iHvkUbd1bcv6; Sat, 31 Aug 2013 07:40:01 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C8FCA11E810C; Sat, 31 Aug 2013 07:40:00 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id c11so483434wgh.1 for <multiple recipients>; Sat, 31 Aug 2013 07:40: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=MXUQ6fxwfafnmtrQjqj0q9IMbXC2RxoGbIzCkO8gqRY=; b=Ug7KQp212HiXxqpiDPtGzFK1YDiMTIeIYCnC6kcLyOfhWLB1U95eaE4DGlWVGi8pan 80QdaTjl2pOrbn/Pysd9vdvo/lg5KfF+g7fxoJ30PKmruynFvk5bctKAJmt2HVgUyMts qS4Ipc+hFmJT60pMNZaPu9gNAdjTZbLqOhYZ01eqscA1lBwB2ieWc6UeikvSRxFqn7+Y u4wakYrLphbB3J+57b8Hub/NV7iLDoDrLnxL43ISXvEMOcvK3117hUmkjPOn5jWAXsOr YeYEeOY97AXKtOZYjD2ZzSYYqX71Vd/qAPIHlQhzNtpGDhAk9bmrnQoSEeB0KVBvHUNs P/+Q==
MIME-Version: 1.0
X-Received: by 10.194.8.9 with SMTP id n9mr15608649wja.11.1377959999949; Sat, 31 Aug 2013 07:39:59 -0700 (PDT)
Received: by 10.180.75.144 with HTTP; Sat, 31 Aug 2013 07:39:59 -0700 (PDT)
In-Reply-To: <00bc01cea63d$186aee80$4940cb80$@gmail.com>
References: <00bc01cea63d$186aee80$4940cb80$@gmail.com>
Date: Sat, 31 Aug 2013 07:39:59 -0700
Message-ID: <CAL0qLwYWYMbZgtR0rAuqb9sdNY7ttXhePbCdSrq5vrfvsNaHzw@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-ietf-repute-model-08
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b41c54c4fd73204e53f5001
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-repute-model.all@tools.ietf.org, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 14:40:02 -0000

--047d7b41c54c4fd73204e53f5001
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Roni,

I didn't see your previous review for some reason.  I can't respond in full
now as I'm about to travel, but I will over the long weekend (unless Andrew
gets to it first).

Thanks,

-MSK



On Sat, Aug 31, 2013 at 4:27 AM, Roni Even <ron.even.tlv@gmail.com> wrote:

> I was asked to review the 08 version but my comments from 07 were not
> addressed and I did not see any response. So I am resending my previous
> review****
>
> As for making it a standard track document, I am not sure since it looks
> to me as an overview and not standard. And there is no normative language
> in the document.****
>
> Roni Even****
>
> ** **
>
> 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-repute-model-07****
>
> Reviewer: Roni Even****
>
> Review Date:2013=968=9620****
>
> IETF LC End Date: 2013-8=9629****
>
> IESG Telechat date: ****
>
> ** **
>
> Summary: This draft is ready for publication as an Informational RFC.****
>
> ** **
>
> ** **
>
> Major issues:****
>
> Minor issues:****
>
> I was wondering why the =93Further Discussion=94 section 9.3 is part of t=
he
> security section. I think it should be a separate section.****
>
> Nits/editorial comments:****
>
> Section 3 the end of 2nd paragraph =93mechansisms=94 to =93mechanisms=94*=
***
>
> ** **
>
> ** **
>

--047d7b41c54c4fd73204e53f5001
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi Roni,<br><br>I didn&#39;t see your previous r=
eview for some reason.=A0 I can&#39;t respond in full now as I&#39;m about =
to travel, but I will over the long weekend (unless Andrew gets to it first=
).<br>
<br></div>Thanks,<br><br></div>-MSK<br><br></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Sat, Aug 31, 2013 at 4:27 AM, Roni E=
ven <span dir=3D"ltr">&lt;<a href=3D"mailto:ron.even.tlv@gmail.com" target=
=3D"_blank">ron.even.tlv@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"=
EN-US"><div><p class=3D"MsoNormal"><a name=3D"140d4236f5d32334_OLE_LINK2"><=
/a><a name=3D"140d4236f5d32334_OLE_LINK1"></a>I was asked to review the 08 =
version but my comments from 07 were not addressed and I did not see any re=
sponse. So I am resending my previous review<u></u><u></u></p>
<p class=3D"MsoNormal">As for making it a standard track document, I am not=
 sure since it looks to me as an overview and not standard. And there is no=
 normative language in the document.<u></u><u></u></p><p class=3D"MsoNormal=
">
Roni Even<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=A0<u></u></p><p c=
lass=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. For b=
ackground on Gen-ART, please see the FAQ at &lt;<a href=3D"http://wiki.tool=
s.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tool=
s.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<u></u><u></u></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<u></u><u></u></p><p><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Documen=
t: </span><span style=3D"font-family:&quot;Courier New&quot;">draft-ietf-re=
pute-model-07</span><u></u><u></u></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">Reviewer: Roni Even<u></u><u></u></span></p><p><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
">Review Date:2013=968=9620<u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;">IETF LC End Date: 2013-8=9629<u></u><u></u></span></p><p><s=
pan style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;">IESG Telechat date: <u></u><u></u></span></p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><u></u>=A0<u></u></span></p><p><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary: This d=
raft is ready for publication as an Informational RFC.<u></u><u></u></span>=
</p>
<p><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;"><u></u>=A0<u></u></span></p><p><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u>=A0<u></=
u></span></p>
<p class=3D"MsoNormal">Major issues:<u></u><u></u></p><p class=3D"MsoNormal=
">Minor issues:<u></u><u></u></p><p class=3D"MsoNormal">I was wondering why=
 the =93Further Discussion=94 section 9.3 is part of the security section. =
I think it should be a separate section.<u></u><u></u></p>
<p class=3D"MsoNormal">Nits/editorial comments:<u></u><u></u></p><p class=
=3D"MsoNormal">Section 3 the end of 2<sup>nd</sup> paragraph =93mechansisms=
=94 to =93mechanisms=94<span style><u></u><u></u></span></p><p class=3D"Mso=
Normal"><a name=3D"140d4236f5d32334_policy.abstract"></a><u></u>=A0<u></u><=
/p>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p></div></div></blockquote></div>=
<br></div>

--047d7b41c54c4fd73204e53f5001--

From iab-chair@iab.org  Sat Aug 31 09:33:59 2013
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A86D21F9E44; Sat, 31 Aug 2013 09:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.149
X-Spam-Level: 
X-Spam-Status: No, score=-102.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmUk+qAnPzFw; Sat, 31 Aug 2013 09:33:58 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id B1D9911E8158; Sat, 31 Aug 2013 09:33:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 00098A6092; Sat, 31 Aug 2013 09:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYhTelvcLaUN; Sat, 31 Aug 2013 09:33:04 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-154-95.washdc.fios.verizon.net [96.241.154.95]) by c9a.amsl.com (Postfix) with ESMTPSA id 6D81A9FBA2; Sat, 31 Aug 2013 09:33:04 -0700 (PDT)
Subject: Re: Call for Volunteers to Serve on the ICANN Nominating Committee
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IAB Chair <iab-chair@iab.org>
In-Reply-To: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org>
Date: Sat, 31 Aug 2013 12:33:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4513AB2-E02A-47E8-B0B2-72DF45B1D92A@iab.org>
References: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Sat, 31 Aug 2013 16:33:59 -0000

The IAB has selected Russ Mundy to serve on the 2014 ICANN NOMCOM.  An =
active member in the IETF and ICANN communities, Russ serves as a =
vice-chair of the Security & Stability Advisory Committee of ICANN and =
has been an active participant in the IETF for many years, having =
implemented DNSSEC.  We wish Russ every success in this important role, =
and we encourage community members to share their views with Russ about =
the various leadership positions that he will have a part in selecting.

We thank everyone who put their name forward as a candidate for this =
position, as well as Ole Jacobsen for his years of service in this role.

On behalf of the IAB,
  Russ Housley
  IAB Chair


On Jun 27, 2013, at 10:36 PM, IAB Chair wrote:

> Please forward to all interested parties.
>=20
> Dear Colleagues,
>=20
> The IAB (on behalf of the IETF) has been asked to supply a member to =
the 2014 ICANN Nominating Committee (NomCom) by 15 August 2013. We would =
therefore like to ask the community for volunteers to serve on the ICANN =
NomCom. If you are interested, please send a short e-mail to iab-chair =
at iab.org with a copy to execd at iab.org with your motivation and =
information concerning your familiarity with the IETF and ICANN.  The =
deadline for volunteering is 19 July 2013.
>=20
> The IAB will select from the available candidates, taking into account =
the familiarity with ICANN and the IETF, their roles, and their =
processes. The selected candidate will serve on the ICANN NomCom on =
personal title; however, we will be looking for a candidate who has an =
understanding of the interests of the technical community.
>=20
> The ICANN NomCom process itself is governed by the ICANN bylaws; an =
abstract of the relevant articles can be found at =
http://nomcom.icann.org/bylaws.htm.  In addition, each NomCom determines =
a number of its own operational procedures, including the role of the =
NomCom in recruiting and selecting candidates.
>=20
> The ICANN Nominating Committee typically meets in person at or around =
three consecutive ICANN meetings. The first of these meetings, when the=20=

> committee is formally established, will be held  22-23 November 2013 =
following the Buenos Aires ICANN meeting on 17-21 November. The =
committee will next attend the "Spring" ICANN meeting, which in 2014 =
will be in Singapore on 23-27 March 2014. Finally, the committee will =
meet during and after the "Summer" ICANN meeting in London on 22-26 June =
2014 where the final slate of candidates for the ICANN Board, the GNSO, =
ccNSO,and ALAC will be agreed upon.
>=20
> Candidates should be able to join monthly teleconferences (typically =
at UTC 14:00), with the expectation that these teleconferences will held =
weekly during the candidate assessment process in May-June.
>=20
> NOTE: ICANN does cover travel and hotel costs for a pre-determined =
number of days at each of the 3 consecutive ICANN meetings.
>=20
> For more information about the ICANN NomCom see: =
http://nomcom.icann.org/.  If you are willing to be considered or would =
like to nominate someone for the position, please send an email to =
iab-chair at iab.org and execd at iab.org.
>=20
> On behalf of the IAB,
>  Russ Housley
>  IAB Chair


From paf@frobbit.se  Sat Aug 31 09:51:03 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE9921F8FCE; Sat, 31 Aug 2013 09:51:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6WJSihebgU3; Sat, 31 Aug 2013 09:51:03 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id E70AA21F8F97; Sat, 31 Aug 2013 09:51:02 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::257d:5471:eef1:af91] (unknown [IPv6:2a02:80:3ffc:0:257d:5471:eef1:af91]) by mail.frobbit.se (Postfix) with ESMTPSA id 5512723F2E; Sat, 31 Aug 2013 18:51:01 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Call for Volunteers to Serve on the ICANN Nominating Committee
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <A4513AB2-E02A-47E8-B0B2-72DF45B1D92A@iab.org>
Date: Sat, 31 Aug 2013 18:51:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BB98B7D-79E6-46F5-A772-55E9E738E4B0@frobbit.se>
References: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org> <A4513AB2-E02A-47E8-B0B2-72DF45B1D92A@iab.org>
To: ietf@ietf.org, IAB <iab@iab.org>
X-Mailer: Apple Mail (2.1508)
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: Sat, 31 Aug 2013 16:51:03 -0000

On 31 aug 2013, at 18:33, IAB Chair <iab-chair@iab.org> wrote:

> An active member in the IETF and ICANN communities, Russ serves as a =
vice-chair of the Security & Stability Advisory Committee of ICANN and =
has been an active participant in the IETF for many years, having =
implemented DNSSEC.

There is a mistake here. Let me correct it.

Russ is the liaison from the Security and Stability Advisory Committee =
(SSAC) to DNS Root Server System Advisory Committee (RSSAC), both =
advisory committees of ICANN.

Jim Galvin is the vice chair of SSAC.

That said, congratulations to IAB for a good choice of liaison!

   Patrik F=E4ltstr=F6m
   Chair, SSAC


From housley@vigilsec.com  Sat Aug 31 09:53:31 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 073CE21F8FF5; Sat, 31 Aug 2013 09:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JK-Lf5v-f8pB; Sat, 31 Aug 2013 09:53:24 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id BD47A21F942D; Sat, 31 Aug 2013 09:53:24 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 2AC7EF24120; Sat, 31 Aug 2013 12:53:46 -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 ezr76gOG1wIs; Sat, 31 Aug 2013 12:53:22 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-154-95.washdc.fios.verizon.net [96.241.154.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id CA225F240B8; Sat, 31 Aug 2013 12:53:44 -0400 (EDT)
Subject: Re: [IAB] Call for Volunteers to Serve on the ICANN Nominating Committee
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=iso-8859-1
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <2BB98B7D-79E6-46F5-A772-55E9E738E4B0@frobbit.se>
Date: Sat, 31 Aug 2013 12:53:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <09D269A5-046D-4812-AF7F-21CA70539EA2@vigilsec.com>
References: <5607FF5A-75CB-4A4B-9B3C-2798D6DF9BFB@iab.org> <A4513AB2-E02A-47E8-B0B2-72DF45B1D92A@iab.org> <2BB98B7D-79E6-46F5-A772-55E9E738E4B0@frobbit.se>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 16:53:31 -0000

Patrik:

Thanks for the correction.  The error is mine.

Russ


On Aug 31, 2013, at 12:51 PM, Patrik F=E4ltstr=F6m wrote:

> On 31 aug 2013, at 18:33, IAB Chair <iab-chair@iab.org> wrote:
>=20
>> An active member in the IETF and ICANN communities, Russ serves as a =
vice-chair of the Security & Stability Advisory Committee of ICANN and =
has been an active participant in the IETF for many years, having =
implemented DNSSEC.
>=20
> There is a mistake here. Let me correct it.
>=20
> Russ is the liaison from the Security and Stability Advisory Committee =
(SSAC) to DNS Root Server System Advisory Committee (RSSAC), both =
advisory committees of ICANN.
>=20
> Jim Galvin is the vice chair of SSAC.
>=20
> That said, congratulations to IAB for a good choice of liaison!
>=20
>   Patrik F=E4ltstr=F6m
>   Chair, SSAC
>=20


From melinda.shore@gmail.com  Sat Aug 31 11:03:01 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B2121E80CB for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.46
X-Spam-Level: 
X-Spam-Status: No, score=-2.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 Y5BiQwwHHO8P for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:03:00 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 779C121E80CA for <ietf@ietf.org>; Sat, 31 Aug 2013 11:03:00 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id bj1so3590869pad.0 for <ietf@ietf.org>; Sat, 31 Aug 2013 11:03:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=R18RMQYKROYCe8XKNFyGDjdGp1MwvmNN59CgIkH3bAs=; b=mi+ge+I/HyoP2E4nTC58vd5XmZPtvzSLD4DPgK0mIkVktEqToGJxjMHtfyHsV1Cbi6 2J+0/tIPs+REHwgdAW1aOLimOG+J/sdGWFBNGbC3KCtAbLbdvbJDl/5v666bz0JxEjNP WgoMoNBE1vlFVFa+vcD/d34rjbh1tITGQAAJN35h6VOMeR1PJzd6ui5rRMzMyhV7UiWE GBUUykm5PmYvIhHC+oBEZhEJqSVl8Tj9Ao9tdFcTO0Lls3oSiFXOSOEjUNdN4WZITd7O 9Dfepen+L/z+5cI8wxWTQzAHBGbZI3GWKOcEStCdHtTH1MDQ2g4w0tAp5ykTFDZ4uGPh sOqw==
X-Received: by 10.68.211.2 with SMTP id my2mr16773714pbc.15.1377972180228; Sat, 31 Aug 2013 11:03:00 -0700 (PDT)
Received: from spandex.local (209-193-56-207-rb1.fai.dsl.dynamic.acsalaska.net. [209.193.56.207]) by mx.google.com with ESMTPSA id ia5sm5345896pbc.42.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 Aug 2013 11:02:59 -0700 (PDT)
Message-ID: <52222FD1.9000805@gmail.com>
Date: Sat, 31 Aug 2013 10:02:57 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: sm+ietf@elandsys.com, IETF Discussion <ietf@ietf.org>
Subject: draft-moonesamy-ietf-conduct-3184bis
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 18:03:01 -0000

It seems like this would be a good time for an update.  A few
comments:

. I think there are a few things that we've been taking for
  granted that everybody knows, because they did, but that
  may not longer be the case and consequently they should be
  made explicit.  One that really popped out at me while
  reading this is that we may need to be clearer that people
  are participating in the IETF as individuals and
  contributions are evaluated in that light

. I'd like to see some mention of consensus-seeking behavior;
  that is to say, we make decisions on the basis of rough
  consensus and so the goal of discussion should be to build
  consensus rather than to "win."

. I'm not 100% comfortable with the concept of "violating
  guidelines

. I think it was a good idea to remove text that could be
  discouraging to new participants.

Melinda

From hallam@gmail.com  Sat Aug 31 11:15:54 2013
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 EF29421F91C9 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  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 JLgUUPPYpLLw for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:15:50 -0700 (PDT)
Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 16B3F11E812D for <ietf@ietf.org>; Sat, 31 Aug 2013 11:15:49 -0700 (PDT)
Received: by mail-qa0-f46.google.com with SMTP id i13so314035qae.5 for <ietf@ietf.org>; Sat, 31 Aug 2013 11:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/l/k9myRcfjjSB8u6nN2YRwhcZOPHBVuTY2AAtL0g1g=; b=liHAnPph9WAO+ifuxPVnRQQrgsg0D9p2mMJlBJ2m/RJ8LJ6yilaZdXx6VEUqBmpsjd gatVwiK0zVa/KpslWVVKAgM+sG8g2wcOwzwH3VV1ICGiK5UJhDOwTDYDAgcb5rUkz6om 8jWcj7pzribHZrkds7NHl7nZEWyYTvcFPmx4owY4w946Ujg61TpGAKppQ7kLELRvqFyo oAMH479VoFE6CcltjAj24zGGae8N2N7CJKrhLvfM7wOmrTgbIGerk9+MzFLwPvdpRp6U nesjWDKQbA+B3Jg5ctqCjrfJ33vp8NHlULWO8bMP8qbwD5D9DAlA48+ALln2AMro/jrm IFWA==
X-Received: by 10.224.127.8 with SMTP id e8mr2907791qas.60.1377972947567; Sat, 31 Aug 2013 11:15:47 -0700 (PDT)
Received: from new-host-4.home (pool-108-7-229-221.bstnma.fios.verizon.net. [108.7.229.221]) by mx.google.com with ESMTPSA id q18sm6636899qad.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 Aug 2013 11:15:45 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
From: Phill <hallam@gmail.com>
In-Reply-To: <52222FD1.9000805@gmail.com>
Date: Sat, 31 Aug 2013 14:15:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <86C71367-ABC2-4FE7-B7A0-12C59C26CA31@gmail.com>
References: <52222FD1.9000805@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1508)
Cc: sm+ietf@elandsys.com, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 18:15:55 -0000

On Aug 31, 2013, at 2:02 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> It seems like this would be a good time for an update.  A few
> comments:
>=20
> . I think there are a few things that we've been taking for
>  granted that everybody knows, because they did, but that
>  may not longer be the case and consequently they should be
>  made explicit.  One that really popped out at me while
>  reading this is that we may need to be clearer that people
>  are participating in the IETF as individuals and
>  contributions are evaluated in that light
>=20
> . I'd like to see some mention of consensus-seeking behavior;
>  that is to say, we make decisions on the basis of rough
>  consensus and so the goal of discussion should be to build
>  consensus rather than to "win."
>=20
> . I'm not 100% comfortable with the concept of "violating
>  guidelines
>=20
> . I think it was a good idea to remove text that could be
>  discouraging to new participants.


I think it would be useful to point out that there is a big difference =
between getting a draft published as an RFC and getting the proposal =
deployed.

The point of the IETF process is that it provides an opportunity to =
build the consensus necessary to deploy the proposal. The consensus is =
the real product, the documents are secondary.

Which is why I find the folk who work as consultants claiming to 'grease =
the skids' of IETF process and get documents through are doing their =
clients and the community a disservice. Yes, it is possible to get a =
document published through the backdoor. But doing business that way =
misses the opportunity to build consensus.


It is also the case that some consensus matters more than others. A =
proposal cannot be deployed without the support of people who write code =
and operate infrastructure that must be changed. So people who work to =
effect a back room carve up that cuts those people out of the process =
are wasting everyone's time=

From dhc@dcrocker.net  Sat Aug 31 11:16:14 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD77321F9F31 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:16: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 v6PI4i0EzhT5 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:16:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC99821F9E0D for <ietf@ietf.org>; Sat, 31 Aug 2013 11:16:07 -0700 (PDT)
Received: from [172.29.102.244] (wsip-184-191-162-57.sd.sd.cox.net [184.191.162.57]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7VIFpki016303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 31 Aug 2013 11:15:55 -0700
Message-ID: <522232D0.60107@dcrocker.net>
Date: Sat, 31 Aug 2013 11:15:44 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
References: <52222FD1.9000805@gmail.com>
In-Reply-To: <52222FD1.9000805@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 31 Aug 2013 11:15:55 -0700 (PDT)
Cc: sm+ietf@elandsys.com, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 18:16:15 -0000

On 8/31/2013 11:02 AM, Melinda Shore wrote:
> . I'd like to see some mention of consensus-seeking behavior;
>    that is to say, we make decisions on the basis of rough
>    consensus and so the goal of discussion should be to build
>    consensus rather than to "win."

+10.

Might be worth referencing Pete Resnick's draft; at this point, casting 
it as one person's 'exploration' of the concept might avoid taking it as 
official, while still treating it as useful.

By way of operationalizing the idea of discussing-to-build-consensus 
might be emphasizing both explanation -- to help people understand a 
view -- and modification -- to adjust the view based on feedback.

A characteristic of talking to win, rather than explore, is having a 
very rigid manner of making comments, essentially only re-stating a 
point.  By contrast, real discussion incorporates comments being made, 
rather than merely seeking to refute them.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Sat Aug 31 11:58:17 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB1521F9FED for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.213
X-Spam-Level: 
X-Spam-Status: No, score=-102.213 tagged_above=-999 required=5 tests=[AWL=0.387, 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 9QhZTT5tHdtl for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 11:58:17 -0700 (PDT)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB6421F90CF for <ietf@ietf.org>; Sat, 31 Aug 2013 11:58:17 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id m1so2858167oag.4 for <ietf@ietf.org>; Sat, 31 Aug 2013 11:58:15 -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=Zotd4eT+lrgN1zoX62WNgF9tY69th7sNu0cbtTJWiGQ=; b=Ev4iHysd3HiO72P4ng5LYoM2+LyMQNFKHtd6cIpe3UxFKojZuanaWNwdryY5En/IOY KKT0fejGmpTFkHz5ROI72SF9qT5RaGIyf2tegqqLT3dJfsMtq4o1fQBEWnJr9CuZe/pX u5oEnX9DXbP4J0dK4bMgYPEKME2zZ5esO1xymMWJhe5OlXBnptfjxDl+7jRBmI7zsUEO MEI+WFJmUzPKZoZC/L/8km9+Z0k2OI4ynURUcz0Sm4yTobstol6Ivvzraa2TQmAAHmv+ kYzyeDIpEgidMVzRF6GcLlkobK8KdeK4UOelvVu9USVjYJ0AIHz6IuPEfZGLR/sfHQFh xCZA==
X-Received: by 10.182.225.162 with SMTP id rl2mr11341344obc.72.1377975495116;  Sat, 31 Aug 2013 11:58:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.44.105 with HTTP; Sat, 31 Aug 2013 11:57:55 -0700 (PDT)
In-Reply-To: <522232D0.60107@dcrocker.net>
References: <52222FD1.9000805@gmail.com> <522232D0.60107@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 31 Aug 2013 14:57:55 -0400
Message-ID: <CAPv4CP8w4ra_=wVpXGnjhaFMGuffgNbzA1CBE0Y7zJtYxRqbtg@mail.gmail.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
To: Crocker Dave <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: S Moonesamy <sm+ietf@elandsys.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 18:58:17 -0000

Pete, what is that draft waiting on before becoming an Informational RFC?

From sm@elandsys.com  Sat Aug 31 13:29:51 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840DC11E8187 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 13:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xu+S6ivA5O1v for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 13:29: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 F207111E8184 for <ietf@ietf.org>; Sat, 31 Aug 2013 13:29:44 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.159.51]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r7VKTLEs006415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Aug 2013 13:29:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1377980974; bh=QlXQe2dkgerlMzpLD1/uwki64c0kOoIt6t/i705+LzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nMWiR2Jip6PTfqoEYgJ+qhKLqe73qOKuG5txUVq6E4lf+p4MIw5UWyzTdwiOn44nz WVWy1OKBE0IOF5YuFVTyNrRxvBzGiapxcKo/4JIS5LXySu2Xd/cN4ulBQyiNDIiBa6 Wg3DCJi9tO6MtE4ePu2wwkglfRIIM9+mmFwmDCx8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1377980974; i=@elandsys.com; bh=QlXQe2dkgerlMzpLD1/uwki64c0kOoIt6t/i705+LzM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MTaL3yJerZQMaLmIzT6jZARx1BQqE2s8BP4GpRYrPXos5P9t2muLvt+j/yMbWZPXh YlP3xVWs/xw5AjSZWUIRafqqdsKsq0zXuGwPkys+P4IjdozhJe2rRxgnPZatp1m7cN aOERVxkk0CQtnwj3L+V3N3VubIO/4D2qfX4xZVTQ=
Message-Id: <6.2.5.6.2.20130831115700.0ae3c008@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 31 Aug 2013 12:58:52 -0700
To: Melinda Shore <melinda.shore@gmail.com>, Phill <hallam@gmail.com>, dcrocker@bbiw.net
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
In-Reply-To: <52222FD1.9000805@gmail.com>
References: <52222FD1.9000805@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: Sat, 31 Aug 2013 20:29:51 -0000

At 11:02 31-08-2013, Melinda Shore wrote:
>It seems like this would be a good time for an update.  A few
>comments:
>
>. I think there are a few things that we've been taking for
>   granted that everybody knows, because they did, but that
>   may not longer be the case and consequently they should be
>   made explicit.  One that really popped out at me while
>   reading this is that we may need to be clearer that people
>   are participating in the IETF as individuals and
>   contributions are evaluated in that light

Yes.

>. I'd like to see some mention of consensus-seeking behavior;
>   that is to say, we make decisions on the basis of rough
>   consensus and so the goal of discussion should be to build
>   consensus rather than to "win."

As a quick reply, it may be possible to put that under Item 2 in 
Section 2.  My preference would be to pick a comment from Ted Lemon {1]:

   "Not trying to figure out if what they said meaningfully contradicts your
    own position, and not making a sincere effort to determine if they might be
    correct in contradicting your position."

and use the above to mention "sincere effort".

>. I'm not 100% comfortable with the concept of "violating
>   guidelines

I added that based on a comment from Lars Eggert [2].  The word 
"breach" may be more appropriate.  I should have used the word 
"consequences" for Appendix B.

>. I think it was a good idea to remove text that could be
>   discouraging to new participants.

There was a comment from Lars Eggert [3]:

   '"when you begin to participate in a WG, maybe approach the chairs or
    longer-term participants in order get a view on whether the issues
    you wish to discuss fit the current work of the group."
    Rationale: I HAVE seen newcomers raise issues that were either outside
    the scope, or raise them in ways that got them a bad reception, and a
    little caution about how to get the best result is IMO good.'

My preference is for that to be part of the Newcomers tutorial and/or 
the Tao instead of a guideline for conduct.

At 11:15 31-08-2013, Phill wrote:
>I think it would be useful to point out that there is a big 
>difference between getting a draft published as an RFC and getting 
>the proposal deployed.
>
>The point of the IETF process is that it provides an opportunity to 
>build the consensus necessary to deploy the proposal. The consensus 
>is the real product, the documents are secondary.

It would be better to discuss the above as part of the tutorial material.

>It is also the case that some consensus matters more than others. A 
>proposal cannot be deployed without the support of people who write 
>code and operate infrastructure that must be changed. So people who 
>work to effect a back room carve up that cuts those people out of 
>the process are wasting everyone's time

Proposals which do not have the support of the people who write the 
code tend to be ignored by the people who write the code.

At 11:15 31-08-2013, Dave Crocker wrote:
>Might be worth referencing Pete Resnick's draft; at this point, 
>casting it as one person's 'exploration' of the concept might avoid 
>taking it as official, while still treating it as useful.

My preference is to use "sincere effort".  I'll wait for Pete Resnick 
to argue why his draft should be referenced. :-)

>By way of operationalizing the idea of discussing-to-build-consensus 
>might be emphasizing both explanation -- to help people understand a 
>view -- and modification -- to adjust the view based on feedback.

I think that it would be good to have a discussion of that draft when 
Pete Resnick says that it is ready for discussion.

>A characteristic of talking to win, rather than explore, is having a 
>very rigid manner of making comments, essentially only re-stating a 
>point.  By contrast, real discussion incorporates comments being 
>made, rather than merely seeking to refute them.

The problem may be that it is not clear whether the point will be 
considered as valid.  There may be a view that restating a point is 
useful or else the point will be noticed.  In a long thread some 
points do get missed.  I'll mention an interesting comment:

  "I almost always get at least some private responses, and they inflict
   discomfort often enough for me to not enjoy this communication mode"

It is not possible to have a real discussion if people do not feel 
comfortable to discuss.

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/ietf/current/msg81864.html
2. http://www.ietf.org/mail-archive/web/diversity/current/msg00222.html
3. http://www.ietf.org/mail-archive/web/diversity/current/msg00209.html
4. http://www.ietf.org/mail-archive/web/diversity/current/msg00243.html 


From mohta@necom830.hpcl.titech.ac.jp  Sat Aug 31 14:15:32 2013
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0A5811E818A for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 14:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nId+OdZG3TTt for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 14:15:27 -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 3EC0011E818F for <ietf@ietf.org>; Sat, 31 Aug 2013 14:15:25 -0700 (PDT)
Received: (qmail 22980 invoked from network); 31 Aug 2013 21:10: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; 31 Aug 2013 21:10:28 -0000
Message-ID: <52225C88.8090107@necom830.hpcl.titech.ac.jp>
Date: Sun, 01 Sep 2013 06:13:44 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: An IANA Registry for DNS TXT RDATA (I-D Action: draft-klensin-iana-txt-rr-registry-00.txt)
References: <314C280ADBC42CC60123EF3D@JcK-HP8200.jck.com> <35373CD9-8583-4283-952B-9ABD2141E74B@isi.edu> <B6453291BFB6FFDD3C65119A@JcK-HP8200.jck.com>
In-Reply-To: <B6453291BFB6FFDD3C65119A@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 21:15:32 -0000

The draft does not assure that existing usages are compatible
with each other.

Still, the draft may assure new usages compatible with each other.

However, people who want to have new (sub)types for the new usages
should better simply request new RRTYPEs.

If we need subtypes because 16bit RRTYPE space is not enough
(I don't think so), the issue should be addressed by itself
by introducing a new RRTYPE (some considerations on subtype
dependent caching may be helpful), not TXT, which can assure
compatibilities between subtypes.

For the existing usages, some informational RFC, describing
compatibilities (or lack of them) between the existing usages,
might help.

						Masataka Ohta

From hsantos@isdg.net  Sat Aug 31 14:51:03 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E57C21E8089 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 14:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.447
X-Spam-Level: 
X-Spam-Status: No, score=-102.447 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 G+IKd5oSmy7U for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 14:50:52 -0700 (PDT)
Received: from news.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5FEC321F9CA8 for <ietf@ietf.org>; Sat, 31 Aug 2013 14:50:51 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6386; t=1377985849; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=6WhMyNGLC1Ee+wuoT6WsR17NQ8g=; b=L/ldb4Lutt92kVBiJ5Yd Cn74mbm7HJ3siZbh3MY3MtpGWVY+EfQnCppKQJJKdc3Ne7Gh3kfETA6T8GNfNnO1 FLTAppGyyMAWeaov8JSm59AUGP1bsSN1SiTqohKHNlM/Eg9/b16lYZXdMvsZ09zK whhyRm27YNCXwlsBk1EbWp8=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 31 Aug 2013 17:50:49 -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 153387518.14371.3184; Sat, 31 Aug 2013 17:50:48 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=6386; t=1377985519; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=P9++WIY jHHBCNJOGxvkUv+2QHYBy1lpW8lGg7QB6WNA=; b=GRpGwc05uF/Wfqe8PfoaL1I RcoM8w1bmX8Gy213sNGgdojEPISkGVG/zX+QZlvzRAQoH++caGhqrsnDnl6wf45N e1iK/DbJcgTuT6xIqaTw1zLFl/v1tdEf7uyVj/rHn5leowNtHuzdCsAQ6VvzKu+e OPqIiGkSqeR/tveFQJJ8=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 31 Aug 2013 17:45:19 -0400
Received: from [192.168.1.74] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3894767596.9.4076; Sat, 31 Aug 2013 17:45:18 -0400
Message-ID: <52226531.5010801@isdg.net>
Date: Sat, 31 Aug 2013 17:50:41 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
References: <52222FD1.9000805@gmail.com> <6.2.5.6.2.20130831115700.0ae3c008@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130831115700.0ae3c008@elandnews.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2013 21:51:03 -0000

Along with the other recent drafts for streamlining the RFC process, I 
get the feeling even this new drafting on conduct is simply going to 
be a new rubber stamping tool to shut down the process of due diligent 
engineering discussions, required cross areas reviews, including 
increasing conflict of interest concerns.

There is a lost of engineering diversity when there is a lack or lost 
of industry representation. Folks who shy away, turned off or 
excommunicated based on leveraging conduct policies, we get a behavior 
I call "Consensus by Osmosis" -- rough consensus, higher potential for 
appeals and huge LC debates.

Too much rough consensus conclusions left to the WGLC and IETF LC that 
should and can be worked out before hand.

Ideally, I would like to see new external "APPEAL-LIKE" paths 
("Instant Replay Timeouts viewed by people in the booths") to help, 
settle, minimize serious issues in a WG before WGLC and IETF LC begins.

Perhaps this draft should has some statements about what is expected 
of the project leaders in the area of processing participant inputs. 
I think the draft should also define or describe:

    - Participants
    - Individuals
    - Project Leaders  (AD, CHAIRS, EDITORS?)

Ideally, proper professional conduct should include an expectation the 
leaders will be not be ignoring participants, individuals, industry 
peers and vice versa, of course.

-- 
HLS

On 8/31/2013 3:58 PM, S Moonesamy wrote:
> At 11:02 31-08-2013, Melinda Shore wrote:
>> It seems like this would be a good time for an update.  A few
>> comments:
>>
>> . I think there are a few things that we've been taking for
>>   granted that everybody knows, because they did, but that
>>   may not longer be the case and consequently they should be
>>   made explicit.  One that really popped out at me while
>>   reading this is that we may need to be clearer that people
>>   are participating in the IETF as individuals and
>>   contributions are evaluated in that light
>
> Yes.
>
>> . I'd like to see some mention of consensus-seeking behavior;
>>   that is to say, we make decisions on the basis of rough
>>   consensus and so the goal of discussion should be to build
>>   consensus rather than to "win."
>
> As a quick reply, it may be possible to put that under Item 2 in
> Section 2.  My preference would be to pick a comment from Ted Lemon {1]:
>
>    "Not trying to figure out if what they said meaningfully
> contradicts your
>     own position, and not making a sincere effort to determine if they
> might be
>     correct in contradicting your position."
>
> and use the above to mention "sincere effort".
>
>> . I'm not 100% comfortable with the concept of "violating
>>   guidelines
>
> I added that based on a comment from Lars Eggert [2].  The word
> "breach" may be more appropriate.  I should have used the word
> "consequences" for Appendix B.
>
>> . I think it was a good idea to remove text that could be
>>   discouraging to new participants.
>
> There was a comment from Lars Eggert [3]:
>
>    '"when you begin to participate in a WG, maybe approach the chairs or
>     longer-term participants in order get a view on whether the issues
>     you wish to discuss fit the current work of the group."
>     Rationale: I HAVE seen newcomers raise issues that were either
> outside
>     the scope, or raise them in ways that got them a bad reception, and a
>     little caution about how to get the best result is IMO good.'
>
> My preference is for that to be part of the Newcomers tutorial and/or
> the Tao instead of a guideline for conduct.
>
> At 11:15 31-08-2013, Phill wrote:
>> I think it would be useful to point out that there is a big
>> difference between getting a draft published as an RFC and getting
>> the proposal deployed.
>>
>> The point of the IETF process is that it provides an opportunity to
>> build the consensus necessary to deploy the proposal. The consensus
>> is the real product, the documents are secondary.
>
> It would be better to discuss the above as part of the tutorial material.
>
>> It is also the case that some consensus matters more than others. A
>> proposal cannot be deployed without the support of people who write
>> code and operate infrastructure that must be changed. So people who
>> work to effect a back room carve up that cuts those people out of
>> the process are wasting everyone's time
>
> Proposals which do not have the support of the people who write the
> code tend to be ignored by the people who write the code.
>
> At 11:15 31-08-2013, Dave Crocker wrote:
>> Might be worth referencing Pete Resnick's draft; at this point,
>> casting it as one person's 'exploration' of the concept might avoid
>> taking it as official, while still treating it as useful.
>
> My preference is to use "sincere effort".  I'll wait for Pete Resnick
> to argue why his draft should be referenced. :-)
>
>> By way of operationalizing the idea of discussing-to-build-consensus
>> might be emphasizing both explanation -- to help people understand a
>> view -- and modification -- to adjust the view based on feedback.
>
> I think that it would be good to have a discussion of that draft when
> Pete Resnick says that it is ready for discussion.
>
>> A characteristic of talking to win, rather than explore, is having a
>> very rigid manner of making comments, essentially only re-stating a
>> point.  By contrast, real discussion incorporates comments being
>> made, rather than merely seeking to refute them.
>
> The problem may be that it is not clear whether the point will be
> considered as valid.  There may be a view that restating a point is
> useful or else the point will be noticed.  In a long thread some
> points do get missed.  I'll mention an interesting comment:
>
>   "I almost always get at least some private responses, and they inflict
>    discomfort often enough for me to not enjoy this communication mode"
>
> It is not possible to have a real discussion if people do not feel
> comfortable to discuss.
>
> Regards,
> S. Moonesamy
>
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg81864.html
> 2. http://www.ietf.org/mail-archive/web/diversity/current/msg00222.html
> 3. http://www.ietf.org/mail-archive/web/diversity/current/msg00209.html
> 4. http://www.ietf.org/mail-archive/web/diversity/current/msg00243.html
>
>



From sm@elandsys.com  Sat Aug 31 20:32:33 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFBC821E8051 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 20:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmZFLZ5P02P5 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 20:32:33 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1469911E80D3 for <ietf@ietf.org>; Sat, 31 Aug 2013 20:32:32 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.159.51]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r813WGAt003429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Aug 2013 20:32:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1378006350; bh=gltF16yPKL4glk5MFx3BucF/NXFGEieUZ8G71jf7fCc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1qMjQU/NyNi41l79BT1ScKXjvYHn5IqDujwSfS8QromHYMvmgmh2JMn8G+a9eeGai ETJSfQrc8UDe8ZzX0MX2b36ycI0xwC/IVwNWrKxAxmxPVy/e3dvtyFG7/sQWjlxLfK o9Z5JcLaUgN0zjGZf5/DaPJtXssF0HfohI4j8GmA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1378006350; i=@elandsys.com; bh=gltF16yPKL4glk5MFx3BucF/NXFGEieUZ8G71jf7fCc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jXrmrOeDElUSo5ealLhH5TN458C3hW/+Xn+/vvkc6iCKD2d6JHlKxQYyE/FAZl3Ej NV7pHsqpNS9NMfj/wiJ//jtXsY4uf9KzwDEAu72M18t5ZdzSD/3pLFr25UnCkpPl1b 9eW+OAGtX70Iu9UPH+XFQmqpyACx7NkGiiq/oYKc=
Message-Id: <6.2.5.6.2.20130831191134.0ae023f8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 31 Aug 2013 19:52:44 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
In-Reply-To: <52226531.5010801@isdg.net>
References: <52222FD1.9000805@gmail.com> <6.2.5.6.2.20130831115700.0ae3c008@elandnews.com> <52226531.5010801@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 03:32:33 -0000

Hi Hector,
At 14:50 31-08-2013, Hector Santos wrote:
>Along with the other recent drafts for streamlining the RFC process, 
>I get the feeling even this new drafting on conduct is simply going 
>to be a new rubber stamping tool to shut down the process of due 
>diligent engineering discussions, required cross areas reviews, 
>including increasing conflict of interest concerns.
>
>There is a lost of engineering diversity when there is a lack or 
>lost of industry representation. Folks who shy away, turned off or 
>excommunicated based on leveraging conduct policies, we get a 
>behavior I call "Consensus by Osmosis" -- rough consensus, higher 
>potential for appeals and huge LC debates.

I don't find appeals to be a problem.  I don't find huge Last Call 
debates to be a problem.  Unpleasant behavior is a problem as it 
creates an unworkable climate.  I don't think that it is possible to 
build consensus in such circumstances.

Lars Eggert made the following comment:

   "I actually WANT this draft to talk about the CONSEQUENCES (posting rights
    getting taken away, personal attendance made impossible, etc.) of not
    following the code of conduct! I think that would be by FAR the most
    impactful addition we could make."

Some of the above is already possible (see Appendix B).

Anyone having concerns about conflict of interest can raise the 
concerns.  This draft does not prevent that from happening.  This 
draft is not about cross-area reviews.

>Perhaps this draft should has some statements about what is expected 
>of the project leaders in the area of processing participant inputs. 
>I think the draft should also define or describe:
>
>    - Participants
>    - Individuals
>    - Project Leaders  (AD, CHAIRS, EDITORS?)

The roles are discussed in RFC 2418.

Regards,
S. Moonesamy   


From william.mccall@gmail.com  Sat Aug 31 21:41:40 2013
Return-Path: <william.mccall@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A1811E81BB for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 21:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sdDZSBAXrxuC for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 21:41:39 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4A311E8118 for <ietf@ietf.org>; Sat, 31 Aug 2013 21:41:39 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id dn14so3317675obc.40 for <ietf@ietf.org>; Sat, 31 Aug 2013 21:41:38 -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=F1Wy90CbOA/r+fbuSVZ86uKKEduNUKFq1lEPHnYuaL8=; b=WkrruBHKOgZFGJETJ8Bi4VCCgquQ+TRbks8gTtlB/dirhAihT+dijTnK26fTecgUI+ VjG+wD373Rdyr8trS78wDIXibmDBS2OnHLtiEtWUyxXJT0I7C4kTQ025UVAmM5SPasg1 /sTuT9/Dj/08K2OwJa2j2iL2jcp2Tahuj1JX2q7BM9bkoyzBZLaSb71vjKUqQjyHL5/H c5YAIReDV1MimK2DYokC0u3PeYfRcTBl2JmU1Qo6/raZAg99aFxpMsmndvGF9ksKCo45 P8mIb2O5gSYZqvXfDQfmNzbH5jYoKXWXseDfCUJBg58Lzx/bPDkWnIcAACcOUC9Fnmga /4EQ==
X-Received: by 10.182.247.68 with SMTP id yc4mr12440471obc.67.1378010498613; Sat, 31 Aug 2013 21:41:38 -0700 (PDT)
Received: from [10.10.0.56] (cpe-66-25-3-111.tx.res.rr.com. [66.25.3.111]) by mx.google.com with ESMTPSA id r3sm7062988oep.2.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 Aug 2013 21:41:38 -0700 (PDT)
Message-ID: <5222C585.3010106@gmail.com>
Date: Sat, 31 Aug 2013 23:41:41 -0500
From: William McCall <william.mccall@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
References: <52222FD1.9000805@gmail.com> <6.2.5.6.2.20130831115700.0ae3c008@elandnews.com> <52226531.5010801@isdg.net> <6.2.5.6.2.20130831191134.0ae023f8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130831191134.0ae023f8@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 04:41:40 -0000

On 08/31/2013 09:52 PM, S Moonesamy wrote:
>
> Lars Eggert made the following comment:
>
>   "I actually WANT this draft to talk about the CONSEQUENCES (posting 
> rights
>    getting taken away, personal attendance made impossible, etc.) of not
>    following the code of conduct! I think that would be by FAR the most
>    impactful addition we could make."
>
> Some of the above is already possible (see Appendix B).
>
Just one point that irks me a bit about this draft... this draft would 
imply the violation of the code upon those who do (however 
inadvertently) are 1) Native English speakers and 2) use slang of some 
nature (which is quite arbitrary). I'd ask for the original phrasing to 
be more or less preserved (I see a few wording changes worthwhile) to 
avoid the implied absurdity.

The application of Lars' comment would potentially provide for penalty 
here, so I think it is worthwhile to fight this point now.

I promise I'll try not to use my generally unintelligible speech.

--WM

From sm@elandsys.com  Sat Aug 31 22:53:16 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E135F11E8127 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 22:53:16 -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.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWQbLeKL42bS for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 22:53:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B0A11E80DC for <ietf@ietf.org>; Sat, 31 Aug 2013 22:53:15 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.159.51]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r815qt7p014213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Aug 2013 22:53:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1378014788; bh=bncgCREOV9GrEkWgPbJpiUWM84K3q5634suW0QEKTyE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=j+tJnvUiBDnU6wlLlJXKne2QhLfi0sJDbh56jYW4wQzcHoyisX/PTOPSb11XC8r1o eTqJWp9Br76FiV5bZTwy3BDKh45LXTlIEIKoJYmtznSv9SqIqsY7vqDB9jSPGSiUVi XbBrKHZd37TYetdXLQlbRMIONnVa0CLG6VW/3vCM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1378014788; i=@elandsys.com; bh=bncgCREOV9GrEkWgPbJpiUWM84K3q5634suW0QEKTyE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LwYxa/Zn7g3NOzeBoHUcLc0kxYJ0LIH9Kj3mWgqAhHzTFUgnbkEWE1ZTABYNf9V8Y KnlnUbxInW8L9APJ7N9QVHd38DOXxlhAQjvkVl+E7YCX2Itwv7IEsa9NqTiaBuKoHU PxM9ABeTMirXhcuC7crWulgwSothSctDxbnErzYE=
Message-Id: <6.2.5.6.2.20130831222258.0b590b60@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 31 Aug 2013 22:51:48 -0700
To: William McCall <william.mccall@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
In-Reply-To: <5222C585.3010106@gmail.com>
References: <52222FD1.9000805@gmail.com> <6.2.5.6.2.20130831115700.0ae3c008@elandnews.com> <52226531.5010801@isdg.net> <6.2.5.6.2.20130831191134.0ae023f8@elandnews.com> <5222C585.3010106@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 05:53:17 -0000

Hi William,
At 21:41 31-08-2013, William McCall wrote:
>Just one point that irks me a bit about this draft... this draft 
>would imply the violation of the code upon those who do (however 
>inadvertently) are 1) Native English speakers and 2) use slang of 
>some nature (which is quite arbitrary). I'd ask for the original 
>phrasing to be more or less preserved (I see a few wording changes 
>worthwhile) to avoid the implied absurdity.
>
>The application of Lars' comment would potentially provide for 
>penalty here, so I think it is worthwhile to fight this point now.

The original phrasing is as follows:

   "English is the de facto language of the IETF, but it is not the
    native language of many IETF participants.  Native English
    speakers attempt to speak clearly and a bit slowly and to limit
    the use of slang in order to accommodate the needs of all
    listeners."

The draft reuses the text.  That text could be rewritten as:

    English is the de facto language of the IETF, but it is not the
    native language of many IETF participants.  Native English
    participants attempt to accommodate the needs of other
    participants by communicating clearly.

Regards,
S. Moonesamy 


From scott@kitterman.com  Sat Aug 31 23:15:34 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 325DB11E81C5 for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 23:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRumoN98N7Bt for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 23:15:27 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id ECEA111E81C3 for <ietf@ietf.org>; Sat, 31 Aug 2013 23:15:26 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 0297A20E40FD; Sun,  1 Sep 2013 02:15:25 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1378016125; bh=mBYWfsOg04E77jO1vOo8SHBXhTUB34UARNCRa0HOdcI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Q64i7yP84cFyjmL7Xu+qW4WO+Du64cPbay0k1QMX5Wezm//0VHo7u38LMz1JPaq3M QqG2ilhtrGU8Bu78RFOFsHMPirQ4Nny7hLvNk0klxAGcv48QOahFDJaHsLNGOFB2yr fEp8xSPgE4kEul6SO2HPLsMMfIaqPA0iH3Jp034g=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id DF4F020E40C8;  Sun,  1 Sep 2013 02:15:24 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
Date: Sun, 01 Sep 2013 02:15:24 -0400
Message-ID: <1787410.DcsOcSFY3Y@scott-latitude-e6320>
User-Agent: KMail/4.10.5 (Linux/3.8.0-29-generic; KDE/4.10.5; i686; ; )
In-Reply-To: <6.2.5.6.2.20130831222258.0b590b60@elandnews.com>
References: <52222FD1.9000805@gmail.com> <5222C585.3010106@gmail.com> <6.2.5.6.2.20130831222258.0b590b60@elandnews.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 06:15:34 -0000

On Saturday, August 31, 2013 22:51:48 S Moonesamy wrote:
> Hi William,
> 
> At 21:41 31-08-2013, William McCall wrote:
> >Just one point that irks me a bit about this draft... this draft
> >would imply the violation of the code upon those who do (however
> >inadvertently) are 1) Native English speakers and 2) use slang of
> >some nature (which is quite arbitrary). I'd ask for the original
> >phrasing to be more or less preserved (I see a few wording changes
> >worthwhile) to avoid the implied absurdity.
> >
> >The application of Lars' comment would potentially provide for
> >penalty here, so I think it is worthwhile to fight this point now.
> 
> The original phrasing is as follows:
> 
>    "English is the de facto language of the IETF, but it is not the
>     native language of many IETF participants.  Native English
>     speakers attempt to speak clearly and a bit slowly and to limit
>     the use of slang in order to accommodate the needs of all
>     listeners."
> 
> The draft reuses the text.  That text could be rewritten as:
> 
>     English is the de facto language of the IETF, but it is not the
>     native language of many IETF participants.  Native English
>     participants attempt to accommodate the needs of other
>     participants by communicating clearly.

That does seem better, but don't all parties have an obligation to attempt to 
communicate clearly?

Scott K

From melinda.shore@gmail.com  Sat Aug 31 23:40:44 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE2411E81CD for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 23:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYi-u93scplj for <ietf@ietfa.amsl.com>; Sat, 31 Aug 2013 23:40:43 -0700 (PDT)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id A67EE11E81CC for <ietf@ietf.org>; Sat, 31 Aug 2013 23:40:43 -0700 (PDT)
Received: by mail-pa0-f49.google.com with SMTP id ld10so3910260pab.8 for <ietf@ietf.org>; Sat, 31 Aug 2013 23:40:41 -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=QRBNifSE5wRRwnQteibkiiKwKFIPQ0vo+I/yVy4Qe+Y=; b=jN1hbOdYcjfC7akFOeyVG9TAnj44DtmcKZZolVEcGcZMvBNJrJKNrhk2lrO7p7aeVv ZraD0+HSsfIOSrM8QO+mz/xOLUQzbjo81Lq7gzrv0qPW9FoTfOeBvzPW19SnxtaQ26Hn a/5j8IB0QYLrk+OioX32ujzbHrdLwpvOeazvuVhKTPAexCw49RS5dj9jmhTffab89dYv CPdl0i5rW6g7CJAoj4lBw5vEHQN8fc3356kro3kQ/z723/tdxDLgMv0hLjv8AV/FGP6K ATOxlXg491im5M3bLzYNHTWSAbG6H8byviVHpZEDDYuM4FxS8qIe7Fu9nsOtchwNllyc sLoQ==
X-Received: by 10.68.202.169 with SMTP id kj9mr731275pbc.140.1378017641255; Sat, 31 Aug 2013 23:40:41 -0700 (PDT)
Received: from spandex.local (66-230-85-10-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.10]) by mx.google.com with ESMTPSA id py4sm8087077pbc.14.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 31 Aug 2013 23:40:40 -0700 (PDT)
Message-ID: <5222E166.7040902@gmail.com>
Date: Sat, 31 Aug 2013 22:40:38 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-moonesamy-ietf-conduct-3184bis
References: <52222FD1.9000805@gmail.com> <5222C585.3010106@gmail.com> <6.2.5.6.2.20130831222258.0b590b60@elandnews.com> <1787410.DcsOcSFY3Y@scott-latitude-e6320>
In-Reply-To: <1787410.DcsOcSFY3Y@scott-latitude-e6320>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Sep 2013 06:40:44 -0000

On 8/31/13 10:15 PM, Scott Kitterman wrote:
> That does seem better, but don't all parties have an obligation to attempt to 
> communicate clearly?

Yes, but ...

I think it's particularly incumbent on native English speakers to
avoid highly idiomatic or stylized language - English that is not
taught to non-native speakers.  It may be better to say something
along those lines, although I don't think you can go too wrong
in remind people to communicate clearly.  (This is not entirely
unrelated to the seeking consensus issue)

Melinda

