
From dworley@avaya.com  Thu Jul  7 12:03:11 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA291F0CCC for <salud@ietfa.amsl.com>; Thu,  7 Jul 2011 12:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.306
X-Spam-Level: 
X-Spam-Status: No, score=-96.306 tagged_above=-999 required=5 tests=[AWL=-7.107, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, J_CHICKENPOX_26=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_33=0.6, J_CHICKENPOX_35=0.6, J_CHICKENPOX_39=0.6, J_CHICKENPOX_43=0.6, J_CHICKENPOX_44=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_46=0.6, J_CHICKENPOX_47=0.6, J_CHICKENPOX_48=0.6, J_CHICKENPOX_54=0.6, J_CHICKENPOX_55=0.6, J_CHICKENPOX_56=0.6, J_CHICKENPOX_57=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_63=0.6, J_CHICKENPOX_64=0.6, J_CHICKENPOX_65=0.6, J_CHICKENPOX_66=0.6, J_CHICKENPOX_75=0.6, J_CHICKENPOX_82=0.6, J_CHICKENPOX_83=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlaTYfIVb6hP for <salud@ietfa.amsl.com>; Thu,  7 Jul 2011 12:03:10 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id C633721F8539 for <salud@ietf.org>; Thu,  7 Jul 2011 12:02:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlYBAJYBFk6HCzI1/2dsb2JhbAA2HYRCkz6OSG5wB7ArAopGgVeBdoRYiDOBK4QAgQ0El2GLQg
X-IronPort-AV: E=Sophos;i="4.65,494,1304308800"; d="scan'208";a="289393919"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 07 Jul 2011 15:02:34 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 07 Jul 2011 14:55:36 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Thu, 7 Jul 2011 15:02:26 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "salud@ietf.org" <salud@ietf.org>
Date: Thu, 7 Jul 2011 14:58:52 -0400
Thread-Topic: Nomcom 2011-2012: Third Call for Volunteers 
Thread-Index: Acw7KK/8e4QX3aO6ROyd3yEToSFJoABrzkWH
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F574D@DC-US1MBEX4.global.avaya.com>
References: <20110704154717.2490021F8677@ietfa.amsl.com>
In-Reply-To: <20110704154717.2490021F8677@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: [salud] FW: Nomcom 2011-2012: Third Call for Volunteers
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jul 2011 19:03:11 -0000

SWYgeW91IGhhdmUgYXR0ZW5kZWQgMyBvZiB0aGUgbGFzdCA1IElFVEYgbWVldGluZ3MsIHlvdSBh
cmUgcXVhbGlmaWVkIHRvDQp2b2x1bnRlZXIgZm9yIHRoZSBJRVRGIE5vbWluYXRpbmcgQ29tbWl0
dGVlLiAgTW9yZSB2b2x1bnRlZXJzIGFyZSBuZWVkZWQNCmZvciB0aGUgTm9taW5hdGluZyBDb21t
aXR0ZWUgdG8gZW5zdXJlIGEgZmFpciBjcm9zcy1zZWN0aW9uIG9mIHRoZSBJRVRGDQpjb21tdW5p
dHkuDQoNCkRhbGUNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
RnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFtpZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJl
aGFsZiBPZiBOb21Db20gQ2hhaXIgW25vbWNvbS1jaGFpckBpZXRmLm9yZ10NClNlbnQ6IE1vbmRh
eSwgSnVseSAwNCwgMjAxMSAxMTo0NyBBTQ0KVG86IElFVEYgQW5ub3VuY2VtZW50IGxpc3QNCkNj
OiBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBOb21jb20gMjAxMS0yMDEyOiBUaGlyZCBDYWxsIGZv
ciBWb2x1bnRlZXJzDQoNClRoaXMgaXMgdGhlIFRoaXJkIGNhbGwgZm9yIFZvbHVudGVlcnMgZm9y
IHRoZSAyMDExLTEyIE5vbWNvbS4gIFdlIGFyZQ0KYWxtb3N0IHRocm91Z2ggdGhlIHZvbHVudGVl
ciBwZXJpb2Qgc28gaWYgeW91IGFyZSBjb25zaWRlcmluZw0Kdm9sdW50ZWVyaW5nLCBwbGVhc2Ug
ZG8gc28gdmVyeSBzb29uLg0KDQpXZSBoYXZlIGhhZCBhIHZlcnkgZ29vZCByZXNwb25zZSB0byB0
aGUgaW5pdGlhbCBjYWxsIGZvciB2b2x1bnRlZXJzIGFuZA0KSSBhbSBwbGVhc2VkIHRvIHJlcG9y
dCB0aGF0IHdlIGhhdmUgODQgdm9sdW50ZWVycyB0aHVzIGZhciB3aG9zZQ0KcXVhbGlmaWNhdGlv
bnMgaGF2ZSBiZWVuIGNvbmZpcm1lZCBieSB0aGUgc2VjcmV0YXJpYXQuIEkgaGF2ZSBub3RpZmll
ZA0KZWFjaCBvZiB0aGVzZSB2b2x1bnRlZXJzIGJ5IGVtYWlsLg0KDQpIb3dldmVyLCB3ZSB3b3Vs
ZCBsaWtlIHRvIGhhdmUgbWFueSBtb3JlIHZvbHVudGVlcnMuIFRoZSBtb3JlIHZvbHVudGVlcnMs
DQp0aGUgYmV0dGVyIGNoYW5jZSB3ZSBoYXZlIG9mIGNob29zaW5nIGEgcmFuZG9tIHlldCByZXBy
ZXNlbnRhdGl2ZSBjcm9zcw0Kc2VjdGlvbiBvZiB0aGUgSUVURiBwb3B1bGF0aW9uLiBZb3UgaGF2
ZSB1bnRpbCAxMTo1OSBwbSBFRFQgSnVseSAxMCwgMjAxMQ0KdG8gdm9sdW50ZWVyIGZvciBOb21j
b20gYnV0IGl0IHdvdWxkIGJlIG11Y2ggYmV0dGVyIGlmIHlvdSBjYW4gdm9sdW50ZWVyDQphcyBl
YXJseSBhcyBwb3NzaWJsZS4NCg0KSWYgeW91IHZvbHVudGVlcmVkIGJlZm9yZSAwOTowMCBFRFQg
b24gSnVuZSAyOSB0byBzZXJ2ZSBhcyBhIHZvdGluZyBtZW1iZXINCmFuZCBoYXZlIG5vdCByZWNl
aXZlZCBhIGNvbmZpcm1hdGlvbiBlbWFpbCBmcm9tIG1lLCBwbGVhc2UgcmUtc3VibWl0IGFuZA0K
YnJpbmcgdG8gbXkgYXR0ZW50aW9uIHJpZ2h0IGF3YXkhDQoNCkRldGFpbHMgYWJvdXQgdGhlIHBy
b2Nlc3MgZm9yIHZvbHVudGVlcmluZyBmb3IgdGhlIE5vbWNvbSBhbmQgdGhlIGxpc3QNCm9mIG9w
ZW4gcG9zaXRpb25zIGZvciB3aGljaCB0aGUgbm9taW5hdGluZyBjb21taXR0ZWUgaXMgcmVzcG9u
c2libGUgYXJlDQpzdW1tYXJpemVkIGluIHRoZSBpbml0aWFsIGFubm91bmNlbWVudDoNCg0KaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9hbm4vbm9tY29tLzI5MzgvDQoNClRoZSA4NCB2b2x1
bnRlZXJzIHdobyBoYXZlIHRodXMgZmFyIGJlZW4gcXVhbGlmaWVkIGJ5IHRoZSBzZWNyZXRhcmlh
dA0KYXJlOg0KDQpBbGlhIEF0bGFzLEp1bmlwZXIgTmV0d29ya3MNCkxpeGlhIFpoYW5nLFVDTEEN
Cldhc3NpbSBIYWRkYWQgLEVyaWNzc29uDQpHbGVuIFpvcm4sTmV0d29yayBaZW4NClJpY2hhcmQg
QmFybmVzLEJCTiBUZWNobm9sb2dpZXMNClN0ZXBoZW4gS2VudCxCQk4gVGVjaG5vbG9naWVzDQpT
Y290dCBNYW5zZmllbGQsRXJpY3Nzb24NClRpbmEgVFNPVSAoVGluZyBaT1UpLEZ1dHVyZVdlaSBU
ZWNobm9sb2dpZXMNCkZlcm5hbmRvIEdvbnQsVVROL0ZSSA0KS2FyZW4gU2VvLEJCTiBUZWNobm9s
b2dpZXMNCkppZSBEb25nLEh1YXdlaSBUZWNobm9sb2dpZXMNCk1hY2ggQ2hlbixIdWF3ZWkgVGVj
aG5vbG9naWVzIENvLiBMdGQuDQpTaGVuZyBKaWFuZyxIdWF3ZWkgVGVjaG5vbG9naWVzIENvLiBM
dGQuDQpEaW1pdHJpIFBhcGFkaW1pdHJpb3UsQWxjYXRlbC1MdWNlbnQNClRob21hcyBELiBOYWRl
YXUsQ0EgVGVjaG5vbG9naWVzDQpEYXZpZCBNZXllcixDaXNjbyBTeXN0ZW1zL1VuaXZlcnNpdHkg
b2YgT3JlZ29uDQpXZXNsZXkgR2VvcmdlLFRpbWUgV2FybmVyIENhYmxlDQpDdWxsZW4gSmVubmlu
Z3MsQ2lzY28NClN0ZXBoZW4gSGFubmEsSnVuaXBlciBOZXR3b3Jrcw0KU3RlcGhhbiBXZW5nZXIs
QmlkeW8gSW5jLg0KS2V5dXIgUGF0ZWwsQ2lzY28gU3lzdGVtcw0KTWljaGFlbCAoTWlrZSkgSGFt
aWx0b24sQnJlYWtpbmdQb2ludCBTeXN0ZW1zDQpCZWhjZXQgU2FyaWtheWEsSHVhd2VpIFVTQQ0K
TWFyayBUb3duc2xleSxDaXNjbyBTeXN0ZW1zDQpGcmVkIEJha2VyLENpc2NvIFN5c3RlbXMNCkJy
aWFuIFRyYW1tZWxsLEVUSCBa77+9cmljaA0KU2FtIEhhcnRtYW4sUGFpbmxlc3MgU2VjdXJpdHkN
CkNocmlzIEdyaWZmaXRocyxDb21jYXN0DQpHZW9yZ2UgTWljaGFlbHNvbixBUE5JQw0KSmlhbmth
bmcgWWFvLENOTklDDQpTb2hlbCBLaGFuLENvbWNhc3QNCkRhY2hlbmcgWmhhbmcsSHVhd2VpDQpM
aWFuc2h1IFpoZW5nLEh1YXdlaSBUZWNobm9sb2dpZXMNCkh1aSBEZW5nLENoaW5hIE1vYmlsZQ0K
R2FuZyBDaGVuLENoaW5hIE1vYmlsZQ0KTWlyamEgS++/vWhsZXdpbmQsVW5pdmVyc2l0eSBvZiBT
dHV0dGdhcnQgSUtSDQpKb2huIEUgRHJha2UsSnVuaXBlciBOZXR3b3Jrcw0KTWF0dCBMZXBpbnNr
aSxCQk4gVGVjaG5vbG9naWVzDQpTdWJpciBEYXMsVGVsY29yZGlhIFRlY2hub2xvZ2llcyBJbmMN
CllpIFpoYW8sSHVhd2VpDQpKb2huIFNjdWRkZXIsSnVuaXBlciBOZXR3b3Jrcw0KQ2hyaXN0ZXIg
SG9sbWJlcmcsTE0gRXJpY3Nzb24NClRlZW11IFNhdm9sYWluZW4sTm9raWENClNhbWl0YSBDaGFr
cmFiYXJ0aSxFcmljc3Nvbg0KSmFhcCBBa2tlcmh1aXMsTkxuZXQgbGFicw0KSmFzb24gV2VpbCxU
aW1lIFdhcm5lciBDYWJsZQ0KUmFuZHkgQnVzaCxJbnRlcm5ldCBJbml0aWF0aXZlIEphcGFuDQpD
aHJpc3RpYW4gU2NobWlkdCxOb2tpYSBTaWVtZW5zIE5ldHdvcmtzDQpTZWFuIFNoZW4sQ05OSUMN
CkxvdSBCZXJnZXIsTGFiTiBDb25zdWx0aW5nIEwuTC5DLg0KRG9uYWxkIEVhc3RsYWtlLEh1YXdl
aQ0KWGlhb2h1IFh1LEh1YXdlaSBUZWNobm9sb2dpZXMgY28uIEx0ZC4NCkLvv71yamUgT2hsbWFu
LEVyaWNzc29uDQpEZWJvcmFoIEJydW5nYXJkLEFUJlQNCk1hZ251cyBXZXN0ZXJsdW5kLEVyaWNz
c29uDQpaaGVuIENhbyxDaGluYSBNb2JpbGUNCkhhZHJpZWwgS2FwbGFuLEFjbWUgUGFja2V0DQpM
aWxsYSBEb3ZuZXIsRXJpY3Nzb24NCkpvaG4gSmFzb24gQnJ6b3pvd3NraSxDb21jYXN0DQpKb25u
ZSBTb2luaW5lbixSZW5lc2FzIE1vYmlsZQ0KSmF2aWVyIFViaWxsb3MsU3dlZGlzaCBJbnN0aXR1
dGUgb2YgQ29tcHV0ZXIgU2NpZW5jZQ0KRXJpYyBHcmF5LEVyaWNzc29uDQpUaG9tYXMgSGVyYnN0
LFNpbHZlciBTcHJpbmcgTmV0d29ya3MNCk5pbmcgWm9uZyxIdWF3ZWkgVGVjaG5vbG9naWVzDQpI
YWliaW4gU29uZyxIdWF3ZWkgVGVjaG5vbG9naWVzDQpZaW5namllIEd1LEh1YXdlaSBUZWNobm9s
b2dpZXMNCkhvbmd5dSBMaSxIdWF3ZWkgVGVjaG5vbG9naWVzDQpUZXJyeSBNYW5kZXJzb24sSUNB
Tk4NCkFyaSBLZXJhbmVuLEVyaWNzc29uDQpKb3VuaSBLb3Job25lbixOb2tpYSBTaWVtZW5zIE5l
dHdvcmtzDQpCaHVtaXAgS2hhc25hYmlzaCxaVEUgVVNBIEluYy4NCkRhcGVuZyBMaXUsQ2hpbmEg
TW9iaWxlDQpGYW5nd2VpIEh1LFpURSBDb3Jwb3JhdGlvbg0KT2xlIFRyb2FuLENpc2NvDQpQYXNj
YWwgVGh1YmVydCxDaXNjbw0KV29qY2llY2ggRGVjLENpc2NvDQpHdW50ZXIgVmFuIGRlIFZlbGRl
LENpc2NvDQpOaW5nIFNvLFZlcml6b24gSW5jLi9Vbml2ZXJzaXR5IG9mIFRleGFzIGF0IERhbGxh
cw0KR3VvbWFuIGxpdSxaVEUNClNpbW9uIFBpZXRybyBSb21hbm8sTWVldGVjaG8vVW5pdmVyc2l0
eSBvZiBOYXBvbGkNCkx1Y2EgTWFydGluaSxDaXNjbw0KQmlsbCBWZXJTdGVlZyxDaXNjbw0KVG9l
cmxlc3MgRWNrZXJ0LENpc2NvIFN5c3RlbXMNCkpvc2VwaCBTYWxvd2V5LENpc2NvIFN5c3RlbXMN
Cg0KVGhlIHByaW1hcnkgYWN0aXZpdHkgZm9yIHRoaXMgbm9tY29tIHdpbGwgYmVnaW4gZHVyaW5n
IElFVEYtODEgaW4NClF1ZWJlYyBDaXR5IGFuZCBzaG91bGQgYmUgY29tcGxldGVkIGJ5IEphbnVh
cnkgMjAxMi4gVGhlIG5vbWNvbSB3aWxsDQpiZSBjb2xsZWN0aW5nIHJlcXVpcmVtZW50cyBmcm9t
IHRoZSBjb21tdW5pdHksIGFzIHdlbGwgYXMgdGFsa2luZyB0bw0KY2FuZGlkYXRlcyBhbmQgdG8g
Y29tbXVuaXR5IG1lbWJlcnMgYWJvdXQgY2FuZGlkYXRlcy4gVGhlcmUgd2lsbCBiZQ0KcmVndWxh
cmx5IHNjaGVkdWxlZCBjb25mZXJlbmNlIGNhbGxzIHRvIGVuc3VyZSBwcm9ncmVzcy4gVGh1cywg
YmVpbmcgYQ0Kbm9tY29tIG1lbWJlciBkb2VzIHJlcXVpcmUgc29tZSB0aW1lIGNvbW1pdG1lbnQu
DQoNClBsZWFzZSB2b2x1bnRlZXIgYnkgc2VuZGluZyBhbiBlbWFpbCB0byBtZSBiZWZvcmUNCjEx
OjU5IHBtIEVEVCBKdWx5IDEwLCAyMDExIGFzIGZvbGxvd3M6DQoNClRvOiBzdXJlc2gua3Jpc2hu
YW5AZXJpY3Nzb24uY29tDQpTdWJqZWN0OiBOb21jb20gMjAxMS0xMiBWb2x1bnRlZXINCg0KUGxl
YXNlIGluY2x1ZGUgdGhlIGZvbGxvd2luZyBpbmZvcm1hdGlvbiBpbiB0aGUgYm9keSBvZiB0aGUg
bWFpbDoNCg0KRnVsbCBOYW1lOiAgLy8gQXMgeW91IGVudGVyIGluIHRoZSBJRVRGIFJlZ2lzdHJh
dGlvbiBGb3JtLA0KICAgICAgICAgICAgLy8gRmlyc3QvR2l2ZW4gbmFtZSBmb2xsb3dlZCBieSBM
YXN0L0ZhbWlseSBOYW1lDQoNCkN1cnJlbnQgUHJpbWFyeSBBZmZpbGlhdGlvbjogLy8gdHlwaWNh
bGx5IHdoYXQgZ29lcyBpbiB0aGUgQ29tcGFueQ0KICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAvLyBmaWVsZCBpbiB0aGUgSUVURiBSZWdpc3RyYXRpb24gRm9ybQ0KDQpFbWFpbCBBZGRyZXNz
KGVzKTogLy8gYWxsIGVtYWlsIGFkZHJlc3NlcyB1c2VkIHRvIFJlZ2lzdGVyIGZvciB0aGUNCiAg
ICAgICAgICAgICAgICAgICAvLyBwYXN0IDUgSUVURiBtZWV0aW5ncw0KICAgICAgICAgICAgICAg
ICAgIC8vIFBsZWFzZSBkZXNpZ25hdGUgYSBQcmVmZXJyZWQgZW1haWwgYWRkcmVzcyBmb3INCiAg
ICAgICAgICAgICAgICAgICAvLyBjb250YWN0IGlmIHRoZXJlIGlzIG1vcmUgdGhhbiBvbmUgZW1h
aWwgYWRkcmVzcw0KDQpUZWxlcGhvbmUgbnVtYmVyOiAgLy8gV2l0aCBjb3VudHJ5IGNvZGUgKGZv
ciBjb25maXJtYXRpb24gaWYgc2VsZWN0ZWQpDQoNClBsZWFzZSBleHBlY3QgYW4gZW1haWwgcmVz
cG9uc2UgZnJvbSBtZSB3aXRoaW4gMyBidXNpbmVzcyBkYXlzIHN0YXRpbmcNCndoZXRoZXIgb3Ig
bm90IHlvdSBhcmUgcXVhbGlmaWVkLiAgSWYgeW91IGRvIG5vdCByZWNlaXZlIGEgcmVzcG9uc2Ug
aW4NCnRoaXMgdGltZWZyYW1lLCBwbGVhc2UgcmUtc2VuZCB5b3VyIGVtYWlsIHdpdGggdGhlIHRh
ZyAiUkVTRU5EOiIgYWRkZWQNCnRvIHRoZSBzdWJqZWN0IGxpbmUuDQoNCklmIHlvdSBhcmUgbm90
IHlldCBzdXJlIHlvdSB3b3VsZCBsaWtlIHRvIHZvbHVudGVlciwgcGxlYXNlIGNvbnNpZGVyDQp0
aGF0IE5vbWNvbSBtZW1iZXJzIHBsYXkgYSB2ZXJ5IGltcG9ydGFudCByb2xlIGluIHNoYXBpbmcg
dGhlDQpsZWFkZXJzaGlwIG9mIHRoZSBJRVRGLiAgRW5zdXJpbmcgdGhlIGxlYWRlcnNoaXAgb2Yg
dGhlIElFVEYgaXMgZmFpcg0KYW5kIGJhbGFuY2VkIGFuZCBjb21wcmlzZWQgb2YgdGhvc2Ugd2hv
IGNhbiBsZWFkIHRoZSBJRVRGIGluIHRoZSByaWdodA0KZGlyZWN0aW9uIGlzIGFuIGltcG9ydGFu
dCByZXNwb25zaWJpbGl0eSB0aGF0IHJlc3RzIG9uIHRoZSBJRVRGDQpwYXJ0aWNpcGFudHMgYXQg
bGFyZ2UuIFZvbHVudGVlcmluZyBmb3IgdGhlIE5vbWNvbSBpcyBhIGdvb2Qgd2F5IG9mDQpjb250
cmlidXRpbmcgaW4gdGhhdCBkaXJlY3Rpb24uDQoNCkkgd2lsbCBiZSBwdWJsaXNoaW5nIGEgbW9y
ZSBkZXRhaWxlZCB0YXJnZXQgdGltZXRhYmxlLCBhcyB3ZWxsIGFzDQpkZXRhaWxzIG9mIHRoZSBy
YW5kb21uZXNzIHNlZWRzIHRvIGJlIHVzZWQgZm9yIHRoZSBSRkMgMzc5NyBzZWxlY3Rpb24NCnBy
b2Nlc3MgdmVyeSBzb29uLg0KDQpUaGFuayB5b3UgaW4gYWR2YW5jZSBmb3IgeW91ciBwYXJ0aWNp
cGF0aW9uLg0KDQpTdXJlc2ggS3Jpc2huYW4NCk5vbWNvbSBDaGFpciAyMDExLTIwMTINCkVtYWls
OiBub21jb20tY2hhaXJAaWV0Zi5vcmcsIHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20NCg==

From laura.liess.dt@googlemail.com  Fri Jul  8 07:11:38 2011
Return-Path: <laura.liess.dt@googlemail.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0645621F8A8D for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 07:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.827
X-Spam-Level: 
X-Spam-Status: No, score=-2.827 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t+6bIGTMIyuq for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 07:11:37 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1F39721F8A39 for <salud@ietf.org>; Fri,  8 Jul 2011 07:11:34 -0700 (PDT)
Received: by vxi40 with SMTP id 40so1849256vxi.31 for <salud@ietf.org>; Fri, 08 Jul 2011 07:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=zhYoZA9MeFrd16UsQv1RxlSvWY6ZDIN8ivv61cdDW2M=; b=vMGHBT6XOQ8F3K0NVJyTWVv1crDpyw2iRTbrw4BveLcq/HZWsZeuKKI9ixJUNfHTKm 667k9DhCFunKaU9v9NWb9+AQKrA8gi+/Wk+iWuw73rmmX21gIwGhAzpLRleEklkDCpnp mTx/o2NIitMtFDSwzXBBTEMGC21iFx1bKZ/ec=
MIME-Version: 1.0
Received: by 10.52.65.242 with SMTP id a18mr2414218vdt.25.1310134288032; Fri, 08 Jul 2011 07:11:28 -0700 (PDT)
Received: by 10.52.111.73 with HTTP; Fri, 8 Jul 2011 07:11:27 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907E99F@DC-US1MBEX4.global.avaya.com>
References: <BANLkTi=NAmTiG6=pcQj0JUGBL=S-NUw6zw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E94D@DC-US1MBEX4.global.avaya.com> <BANLkTi=4Fr3zJit_nz5PnJJP69E99xeWbQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E94E@DC-US1MBEX4.global.avaya.com> <BANLkTi=qphB8XezK3GKoFufgBFNoPmbUHQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E980@DC-US1MBEX4.global.avaya.com> <BANLkTi=iMCxzo-8NX3MEWxkVJdumC_DBag@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E99F@DC-US1MBEX4.global.avaya.com>
Date: Fri, 8 Jul 2011 16:11:27 +0200
Message-ID: <CACWXZj3Yx2sG2tMYvP-N0vUp-=o1wrouMDgiihrTihU7A6T=PQ@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] Next steps for Alert-Info URN draft
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 14:11:38 -0000

Dale,

There was no answer from the mailing list so I think people are not
aware of additional technical issues at this time. Maybe new issues
will come up later. I think we should go on and try to agree on a
solution. Maybe this is not the right time because  people are quite
busy now preparing the upcoming IETF meeting. However, after the
meeting, we should try to make some real progress with the issues.

Thank you
Laura



2011/6/6 Worley, Dale R (Dale) <dworley@avaya.com>:
> [as chair]
>
> Hey, everybody!!!
>
> So far, we have only 5 open technical issues listed. =A0Do they really co=
ver everything
> that is left to be done?
>
> We don't need solution proposals right now, just to make sure we see the =
whole
> landscape of problems.
>
> Currently known problems:
>
> - Shall we combine all the characteristics into one URN (leading to a ver=
y large set of possible URNs), or specify each characteristic in a separate=
 URN (and have the UA combine them)?
>
> - In regard to extensibility, shall we arrange for each characteristic va=
lue to be subdividable into more narrowly-defined values, which are themsel=
ves subdividable, etc.?
>
> - In regard to extensibility, what proprietary or non-standard extensions=
 will be possible?
>
> - How will non-standard extensions be designated? =A0(Will they be consis=
tently marked by a particular prefix? =A0Will they be constructed from doma=
in names?)
>
> - How does the "legacy" URN <urn:alert:service:normal> fit into the new s=
ystem?
>
> Dale
>

From dworley@avaya.com  Fri Jul  8 11:38:44 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F089921F8B98 for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 11:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.205
X-Spam-Level: 
X-Spam-Status: No, score=-103.205 tagged_above=-999 required=5 tests=[AWL=0.394, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKCyeuTqSJpF for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 11:38:43 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id BCF1121F8B8F for <salud@ietf.org>; Fri,  8 Jul 2011 11:38:38 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHdOF07GmAcF/2dsb2JhbABUp1F3rwgCmwaGOASXZotG
X-IronPort-AV: E=Sophos;i="4.65,500,1304308800"; d="scan'208";a="289625591"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 08 Jul 2011 14:38:24 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 Jul 2011 14:37:03 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Fri, 8 Jul 2011 14:38:23 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Laura Liess <laura.liess.dt@googlemail.com>
Date: Fri, 8 Jul 2011 14:36:50 -0400
Thread-Topic: Next steps for Alert-Info URN draft
Thread-Index: Acw9ePUh/w6LxvReR7uiTp8jIozhwQAJQsBT
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5757@DC-US1MBEX4.global.avaya.com>
References: <BANLkTi=NAmTiG6=pcQj0JUGBL=S-NUw6zw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E94D@DC-US1MBEX4.global.avaya.com> <BANLkTi=4Fr3zJit_nz5PnJJP69E99xeWbQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E94E@DC-US1MBEX4.global.avaya.com> <BANLkTi=qphB8XezK3GKoFufgBFNoPmbUHQ@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E980@DC-US1MBEX4.global.avaya.com> <BANLkTi=iMCxzo-8NX3MEWxkVJdumC_DBag@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222907E99F@DC-US1MBEX4.global.avaya.com>, <CACWXZj3Yx2sG2tMYvP-N0vUp-=o1wrouMDgiihrTihU7A6T=PQ@mail.gmail.com>
In-Reply-To: <CACWXZj3Yx2sG2tMYvP-N0vUp-=o1wrouMDgiihrTihU7A6T=PQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] Next steps for Alert-Info URN draft
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 18:38:44 -0000

________________________________________
From: Laura Liess [laura.liess.dt@googlemail.com]

There was no answer from the mailing list so I think people are not
aware of additional technical issues at this time. Maybe new issues
will come up later. I think we should go on and try to agree on a
solution. Maybe this is not the right time because  people are quite
busy now preparing the upcoming IETF meeting. However, after the
meeting, we should try to make some real progress with the issues.
_______________________________________

Certainly you're right that there hasn't been any response.  Yes, let's
try to get some discussion of the issues going.

Dale

From dworley@avaya.com  Fri Jul  8 11:55:45 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC7221F8A04 for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 11:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.221
X-Spam-Level: 
X-Spam-Status: No, score=-103.221 tagged_above=-999 required=5 tests=[AWL=0.378, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOB2UyhgYS-Y for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 11:55:45 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id AC31921F8A5B for <salud@ietf.org>; Fri,  8 Jul 2011 11:55:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAIAJZRF07GmAcF/2dsb2JhbABUp1FwB6pzg3UCmwmGOASXZotG
X-IronPort-AV: E=Sophos;i="4.65,500,1304308800"; d="scan'208";a="255631414"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 Jul 2011 14:55:42 -0400
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 08 Jul 2011 14:54:22 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 8 Jul 2011 14:55:41 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "salud@ietf.org" <salud@ietf.org>
Date: Fri, 8 Jul 2011 14:54:03 -0400
Thread-Topic: Currently known technical issues
Thread-Index: AQHMPaChQSDo0aNbP0iH5AS+ESC22A==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 18:55:45 -0000

[as chair]

Given that nobody has suggested any further technical issues, I am repeatin=
g the list, but giving a short description of the benefits of the various a=
lternative choices.  Please weigh in!

- Shall we combine all the characteristics into one URN, or specify each ch=
aracteristic in a separate URN?

The first alternative leads to a very large set of possible URNs, but leave=
s each URN interpretable in isolation.  The second alternative uses a small=
 set of URNs (possibly finite), but requires that they be used in groups fo=
r complex renderings.  The ultimate logic for combining the specified facet=
s of the rendering is exactly the same, but the way the complexity is expre=
ssed differs.

- In regard to extensibility, shall we arrange for each characteristic valu=
e to be subdividable into more narrowly-defined values, which are themselve=
s subdividable, etc.?

Allowing for infinite subdividability is good in abstract, but makes the sy=
stem more complex.  Are there practical requirements to be met?

- In regard to extensibility, what proprietary or non-standard extensions w=
ill be possible?

- How will non-standard extensions be designated?  (Will they be consistent=
ly marked by a particular prefix?  Will they be constructed from domain nam=
es?)

There may be practical requirements as well -- How common will private exte=
nsions be?  Do we need to worry about explicit "namespaces" for extensions?

- How does the "legacy" URN <urn:alert:service:normal> fit into the new sys=
tem?

This is sort of an after-thought, in that once we decide on the above quest=
ions, the detailed syntax will be devised to make the legacy URN valid.

Dale

From pkyzivat@alum.mit.edu  Fri Jul  8 12:23:04 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5EF21F8C1C for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 12:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level: 
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iaJP2BDcKjJJ for <salud@ietfa.amsl.com>; Fri,  8 Jul 2011 12:23:03 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id A1E3321F8C09 for <salud@ietf.org>; Fri,  8 Jul 2011 12:22:57 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by QMTA11.westchester.pa.mail.comcast.net with comcast id 5X2h1h0040vyq2s5BXNyJP; Fri, 08 Jul 2011 19:22:58 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta05.westchester.pa.mail.comcast.net with comcast id 5XNx1h0060tdiYw3RXNxhb; Fri, 08 Jul 2011 19:22:58 +0000
Message-ID: <4E17590F.2010907@alum.mit.edu>
Date: Fri, 08 Jul 2011 15:22:55 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: salud@ietf.org
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 19:23:04 -0000

While its interesting to dice the issues this way, from a practical 
perspective I have trouble answering them independently. Ultimately it 
is an engineering problem to come up with a solution that balances the 
tradeoffs between these things into usable mechanism.

For instance, in principle it would be good to have hierarchical URNs 
that are extensible privately and publicly at every level. But something 
less than that is probably ok, and may be preferable if its easier to 
use and understand.

IMO what we need are complete mechanism proposals. The items you list 
below can be evaluated as attributes of the candidate mechanisms and 
used to contrast one with another. They can also be used to suggest 
avenues for improvement for a particular mechanism.

At the moment we have the mechanism proposed in 
draft-ietf-salud-alert-info-urns, and an alternative proposed by Dale. I 
have't seen any evidence that anybody is interested in proposing another 
distinct approach.

	Thanks,
	Paul

On 7/8/11 2:54 PM, Worley, Dale R (Dale) wrote:
> [as chair]
>
> Given that nobody has suggested any further technical issues, I am repeating the list, but giving a short description of the benefits of the various alternative choices.  Please weigh in!
>
> - Shall we combine all the characteristics into one URN, or specify each characteristic in a separate URN?
>
> The first alternative leads to a very large set of possible URNs, but leaves each URN interpretable in isolation.  The second alternative uses a small set of URNs (possibly finite), but requires that they be used in groups for complex renderings.  The ultimate logic for combining the specified facets of the rendering is exactly the same, but the way the complexity is expressed differs.
>
> - In regard to extensibility, shall we arrange for each characteristic value to be subdividable into more narrowly-defined values, which are themselves subdividable, etc.?
>
> Allowing for infinite subdividability is good in abstract, but makes the system more complex.  Are there practical requirements to be met?
>
> - In regard to extensibility, what proprietary or non-standard extensions will be possible?
>
> - How will non-standard extensions be designated?  (Will they be consistently marked by a particular prefix?  Will they be constructed from domain names?)
>
> There may be practical requirements as well -- How common will private extensions be?  Do we need to worry about explicit "namespaces" for extensions?
>
> - How does the "legacy" URN<urn:alert:service:normal>  fit into the new system?
>
> This is sort of an after-thought, in that once we decide on the above questions, the detailed syntax will be devised to make the legacy URN valid.
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>


From laura.liess.dt@googlemail.com  Mon Jul 11 06:13:02 2011
Return-Path: <laura.liess.dt@googlemail.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE3C321F84D8 for <salud@ietfa.amsl.com>; Mon, 11 Jul 2011 06:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.877
X-Spam-Level: 
X-Spam-Status: No, score=-2.877 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7sUkCYrw0TG for <salud@ietfa.amsl.com>; Mon, 11 Jul 2011 06:12:56 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9C321F86A0 for <salud@ietf.org>; Mon, 11 Jul 2011 06:12:56 -0700 (PDT)
Received: by vws12 with SMTP id 12so4013504vws.31 for <salud@ietf.org>; Mon, 11 Jul 2011 06:12:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=a04iIpy0O1JzHRo47zvR6nqBqbRwviXQ7CeA0fhEeqY=; b=SNZg6QV5T+bXsCX5uJmqJYASTrHyQgl8y/IkMO7R0zM1C+gd7DXEMu26F82NKs2+lB pbxoawtQFHOUiCP9CPF9t6BqbxSDedhZCDqHGHhLg9u98b25FI1GDAKprqOv3cGQFlRY 6VUkZ512h+u75W1J4TFFxEvzImpb+Nv7g6k/k=
MIME-Version: 1.0
Received: by 10.52.179.4 with SMTP id dc4mr5284843vdc.97.1310389975247; Mon, 11 Jul 2011 06:12:55 -0700 (PDT)
Received: by 10.52.182.234 with HTTP; Mon, 11 Jul 2011 06:12:54 -0700 (PDT)
In-Reply-To: <4E17590F.2010907@alum.mit.edu>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <4E17590F.2010907@alum.mit.edu>
Date: Mon, 11 Jul 2011 15:12:54 +0200
Message-ID: <CACWXZj16MGJxwfSpE4a15ougPYEjpmJNFc4PS-Tma8yh0G=Mtg@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: salud@ietf.org
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2011 13:13:02 -0000

Paul,
My understanding is that you propose to go,  for both approaches,
through Dale's issues list and try to answer the issues.
Is this correct?

Laura





2011/7/8 Paul Kyzivat <pkyzivat@alum.mit.edu>:
> While its interesting to dice the issues this way, from a practical
> perspective I have trouble answering them independently. Ultimately it is=
 an
> engineering problem to come up with a solution that balances the tradeoff=
s
> between these things into usable mechanism.
>
> For instance, in principle it would be good to have hierarchical URNs tha=
t
> are extensible privately and publicly at every level. But something less
> than that is probably ok, and may be preferable if its easier to use and
> understand.
>
> IMO what we need are complete mechanism proposals. The items you list bel=
ow
> can be evaluated as attributes of the candidate mechanisms and used to
> contrast one with another. They can also be used to suggest avenues for
> improvement for a particular mechanism.
>
> At the moment we have the mechanism proposed in
> draft-ietf-salud-alert-info-urns, and an alternative proposed by Dale. I
> have't seen any evidence that anybody is interested in proposing another
> distinct approach.
>
> =A0 =A0 =A0 =A0Thanks,
> =A0 =A0 =A0 =A0Paul
>
> On 7/8/11 2:54 PM, Worley, Dale R (Dale) wrote:
>>
>> [as chair]
>>
>> Given that nobody has suggested any further technical issues, I am
>> repeating the list, but giving a short description of the benefits of th=
e
>> various alternative choices. =A0Please weigh in!
>>
>> - Shall we combine all the characteristics into one URN, or specify each
>> characteristic in a separate URN?
>>
>> The first alternative leads to a very large set of possible URNs, but
>> leaves each URN interpretable in isolation. =A0The second alternative us=
es a
>> small set of URNs (possibly finite), but requires that they be used in
>> groups for complex renderings. =A0The ultimate logic for combining the
>> specified facets of the rendering is exactly the same, but the way the
>> complexity is expressed differs.
>>
>> - In regard to extensibility, shall we arrange for each characteristic
>> value to be subdividable into more narrowly-defined values, which are
>> themselves subdividable, etc.?
>>
>> Allowing for infinite subdividability is good in abstract, but makes the
>> system more complex. =A0Are there practical requirements to be met?
>>
>> - In regard to extensibility, what proprietary or non-standard extension=
s
>> will be possible?
>>
>> - How will non-standard extensions be designated? =A0(Will they be
>> consistently marked by a particular prefix? =A0Will they be constructed =
from
>> domain names?)
>>
>> There may be practical requirements as well -- How common will private
>> extensions be? =A0Do we need to worry about explicit "namespaces" for
>> extensions?
>>
>> - How does the "legacy" URN<urn:alert:service:normal> =A0fit into the ne=
w
>> system?
>>
>> This is sort of an after-thought, in that once we decide on the above
>> questions, the detailed syntax will be devised to make the legacy URN va=
lid.
>>
>> Dale
>> _______________________________________________
>> salud mailing list
>> salud@ietf.org
>> https://www.ietf.org/mailman/listinfo/salud
>>
>
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>

From pkyzivat@alum.mit.edu  Mon Jul 11 10:26:56 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A699A21F8D3F for <salud@ietfa.amsl.com>; Mon, 11 Jul 2011 10:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.465
X-Spam-Level: 
X-Spam-Status: No, score=-2.465 tagged_above=-999 required=5 tests=[AWL=0.134,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEbbgbXxApEV for <salud@ietfa.amsl.com>; Mon, 11 Jul 2011 10:26:56 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by ietfa.amsl.com (Postfix) with ESMTP id E97D721F8B9D for <salud@ietf.org>; Mon, 11 Jul 2011 10:26:48 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta13.westchester.pa.mail.comcast.net with comcast id 6gzp1h00227AodY5DhSp7Q; Mon, 11 Jul 2011 17:26:49 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta19.westchester.pa.mail.comcast.net with comcast id 6hSo1h00X0tdiYw3fhSoxc; Mon, 11 Jul 2011 17:26:49 +0000
Message-ID: <4E1B3256.8040200@alum.mit.edu>
Date: Mon, 11 Jul 2011 13:26:46 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Laura Liess <laura.liess.dt@googlemail.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <4E17590F.2010907@alum.mit.edu> <CACWXZj16MGJxwfSpE4a15ougPYEjpmJNFc4PS-Tma8yh0G=Mtg@mail.gmail.com>
In-Reply-To: <CACWXZj16MGJxwfSpE4a15ougPYEjpmJNFc4PS-Tma8yh0G=Mtg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: salud@ietf.org
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jul 2011 17:26:56 -0000

On 7/11/11 9:12 AM, Laura Liess wrote:
> Paul,
> My understanding is that you propose to go,  for both approaches,
> through Dale's issues list and try to answer the issues.
> Is this correct?

yeah, I think that is a way to acknowledge the issues and use them in a 
productive way.

Basically we then end up with a table of two columns (one for each 
approach) and a bunch of rows (one for each of Dale's issues).
Then we can score them against one another.

	Thanks,
	Paul

> 2011/7/8 Paul Kyzivat<pkyzivat@alum.mit.edu>:
>> While its interesting to dice the issues this way, from a practical
>> perspective I have trouble answering them independently. Ultimately it is an
>> engineering problem to come up with a solution that balances the tradeoffs
>> between these things into usable mechanism.
>>
>> For instance, in principle it would be good to have hierarchical URNs that
>> are extensible privately and publicly at every level. But something less
>> than that is probably ok, and may be preferable if its easier to use and
>> understand.
>>
>> IMO what we need are complete mechanism proposals. The items you list below
>> can be evaluated as attributes of the candidate mechanisms and used to
>> contrast one with another. They can also be used to suggest avenues for
>> improvement for a particular mechanism.
>>
>> At the moment we have the mechanism proposed in
>> draft-ietf-salud-alert-info-urns, and an alternative proposed by Dale. I
>> have't seen any evidence that anybody is interested in proposing another
>> distinct approach.
>>
>>         Thanks,
>>         Paul
>>
>> On 7/8/11 2:54 PM, Worley, Dale R (Dale) wrote:
>>>
>>> [as chair]
>>>
>>> Given that nobody has suggested any further technical issues, I am
>>> repeating the list, but giving a short description of the benefits of the
>>> various alternative choices.  Please weigh in!
>>>
>>> - Shall we combine all the characteristics into one URN, or specify each
>>> characteristic in a separate URN?
>>>
>>> The first alternative leads to a very large set of possible URNs, but
>>> leaves each URN interpretable in isolation.  The second alternative uses a
>>> small set of URNs (possibly finite), but requires that they be used in
>>> groups for complex renderings.  The ultimate logic for combining the
>>> specified facets of the rendering is exactly the same, but the way the
>>> complexity is expressed differs.
>>>
>>> - In regard to extensibility, shall we arrange for each characteristic
>>> value to be subdividable into more narrowly-defined values, which are
>>> themselves subdividable, etc.?
>>>
>>> Allowing for infinite subdividability is good in abstract, but makes the
>>> system more complex.  Are there practical requirements to be met?
>>>
>>> - In regard to extensibility, what proprietary or non-standard extensions
>>> will be possible?
>>>
>>> - How will non-standard extensions be designated?  (Will they be
>>> consistently marked by a particular prefix?  Will they be constructed from
>>> domain names?)
>>>
>>> There may be practical requirements as well -- How common will private
>>> extensions be?  Do we need to worry about explicit "namespaces" for
>>> extensions?
>>>
>>> - How does the "legacy" URN<urn:alert:service:normal>    fit into the new
>>> system?
>>>
>>> This is sort of an after-thought, in that once we decide on the above
>>> questions, the detailed syntax will be devised to make the legacy URN valid.
>>>
>>> Dale
>>> _______________________________________________
>>> salud mailing list
>>> salud@ietf.org
>>> https://www.ietf.org/mailman/listinfo/salud
>>>
>>
>> _______________________________________________
>> salud mailing list
>> salud@ietf.org
>> https://www.ietf.org/mailman/listinfo/salud
>>
>


From dworley@avaya.com  Fri Jul 15 13:51:05 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3113121F8B51 for <salud@ietfa.amsl.com>; Fri, 15 Jul 2011 13:51:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.303
X-Spam-Level: 
X-Spam-Status: No, score=-104.303 tagged_above=-999 required=5 tests=[AWL=1.296, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZpMwktwFsGK for <salud@ietfa.amsl.com>; Fri, 15 Jul 2011 13:51:04 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB5121F8B48 for <salud@ietf.org>; Fri, 15 Jul 2011 13:51:00 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEFAI+nIE7GmAcF/2dsb2JhbABUp29wB7AIAptNhVtfBJgEi1E
X-IronPort-AV: E=Sophos;i="4.67,210,1309752000"; d="scan'208";a="291023120"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 15 Jul 2011 16:51:00 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 15 Jul 2011 16:49:13 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 15 Jul 2011 16:50:56 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "salud@ietf.org" <salud@ietf.org>
Date: Fri, 15 Jul 2011 16:50:55 -0400
Thread-Topic: Currently known technical issues
Thread-Index: AQHMPaChQSDo0aNbP0iH5AS+ESC22JTt2see
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 20:51:05 -0000

[as individual]

There are (IMHO) only 4 significant design points right now, in the
vague state that crosses between requirements and design.  I think at
this time we can decide on the more requirement-like aspects of the
problem. -- Such as, will there be many or a few extension URNs
defined?

First, going through the points and looking at the advantages of
alternatives.  There are interactions between the points, which
suggest some choices which I will discuss at the end of this message.

> - Shall we combine all the characteristics into one URN, or specify
>   each characteristic in a separate URN?
>=20
> The first alternative leads to a very large set of possible URNs, but
> leaves each URN interpretable in isolation.  The second alternative
> uses a small set of URNs (possibly finite), but requires that they be
> used in groups for complex renderings.  The ultimate logic for
> combining the specified facets of the rendering is exactly the same,
> but the way the complexity is expressed differs.

Advantages of the single-URN approach:  Each URN can be interpreted
alone, and code that considers Alert-Info as a simple list of URNs
works by examining the URNs until it finds one that it can
understand.  The ordering of the list only expresses the sequence in
which the UA should check the URNs in order to find one it
understands, and we do not have to suffer the conceptual problem that
the interpretation of a list of URNs depends on their order.

Advantages of the multiple-URN approach:  Each URN is simpler to
understand.  In effect, we press the COMMA of the Alert-Info list into
service as the major-level divider of the Alert-Info information.  In
strict logic, this makes little difference, but it may be a significant
human-factors difference.  As a result, the syntax of URNs is simpler,
and in many practical situations, may be reduced to a fixed, finite
list.

> - In regard to extensibility, shall we arrange for each characteristic
>   value to be subdividable into more narrowly-defined values, which
>   are themselves subdividable, etc.?
>=20
> Allowing for infinite subdividability is good in abstract, but makes
> the system more complex.  Are there practical requirements to be met?

Advantages of multiple-level extensibility:  Reduced risk that vendors
will decide they need to extend Alert-Info but can't do so within our
framework, and so add some ugly hack.

Advantages of simple extensibility:  The syntax of the URNs is simpler
-- this is particularly so in the single-URN approach; in the
multiple-URN approach, the simplification is fairly small.

> - In regard to extensibility, what proprietary or non-standard
>   extensions will be possible?

If we have multiple-level extensibility, this question is answered
automatically:  Any characteristic value can be subdivided by any
vendor in any way.

If extensibility is limited, then we have to plan where extensibility
is admissible.

> - How will non-standard extensions be designated?  (Will they be
>   consistently marked by a particular prefix?  Will they be
>   constructed from domain names?)
>=20
> There may be practical requirements as well -- How common will private
> extensions be?  Do we need to worry about explicit "namespaces" for
> extensions?

There seem to be three approaches for building extension names:
reversed domain names (a la Java packages), a prefix like "v-" or
"[vendor name]-", or free-for-all.

Advantages of reversed domain names:  Name organization is clearly
delineated.

Advantages of simple prefixes:  Names are shorter, but collision
should still be rare.

Advantages of free-for-all:  Easy transition of a vendor extension
into standard usage.

----------

There is particular complexity introduced when combining the
single-URN approach and extensibility that allows a characteristic to
be specified by a variable number of words.  I think that there will
be more need for extensibility than we see right now, as vendors have
a lot of legacy features to bring in.  So let me propose as a debating
point:

- multiple-URN
- multiple-level extensibility

To ease extensibility:

- every defined URN can be extended by subdividing it

I am undecided on what syntax is best for extension names.

----------

Relative to draft-ietf-salud-alert-info-urns-02, this leads to changes
like this:

   service                        RFC XXXX  Alert-category for "service"
                                            alert-identifiers.
   service:normal                 RFC XXXX  Normal ring /rinback
                                            rendering (default value).
   service:call-waiting           RFC XXXX  Call waiting was
                                            initiated at the other side
                                            of the call.
   service:forward                RFC XXXX  Call has been forwarded.
   service:recall.calback         RFC XXXX  Recall due to callback.
   service:recall.hold            RFC XXXX  Recall due to call hold.
   service:recall.transfer        RFC XXXX  Recall due to callback.
   service:private.<private-name> RFC XXXX  Reserved for private
                                            extensions.

Remember that "service:normal" in this table means a URN
<urn:alert:service:normal>.

The "service:recall.xxx" group is turned into an additional level of
qualification:  service:recall.callback becomes
service:recall:callback, etc.  The reason for changing "." into ":"
here is that I'm converting to a simpler syntax that is allowed by
using the multiple-URN approach.

service:private.<name> remains as is, assuming that "private." is the
prefix for all private names.  (See the 4th major issue.)  Although it
seems to me to be excessively long.  Note that "." functions as a
letter here, that the various "private.a", "private.b", etc. are not
child nodes of the node service:private, they are siblings of
service:forward, etc.

But in addition, we would allow "private.<name>" children of all the
standard URNs, e.g., service:forward:private.<name> is a private
variant of service:forward in the same way that service:private.<name>
is an entirely private service-type designation.

Dale

From pkyzivat@alum.mit.edu  Sat Jul 16 08:36:38 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D558321F8663 for <salud@ietfa.amsl.com>; Sat, 16 Jul 2011 08:36:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.547
X-Spam-Level: 
X-Spam-Status: No, score=-3.547 tagged_above=-999 required=5 tests=[AWL=1.052,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9FMKmagRzMMH for <salud@ietfa.amsl.com>; Sat, 16 Jul 2011 08:36:38 -0700 (PDT)
Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by ietfa.amsl.com (Postfix) with ESMTP id 1841A21F863A for <salud@ietf.org>; Sat, 16 Jul 2011 08:36:38 -0700 (PDT)
Received: from omta13.emeryville.ca.mail.comcast.net ([76.96.30.52]) by qmta15.emeryville.ca.mail.comcast.net with comcast id 8faA1h00117UAYkAFfcbUc; Sat, 16 Jul 2011 15:36:35 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta13.emeryville.ca.mail.comcast.net with comcast id 8fca1h00l0tdiYw8ZfcbkD; Sat, 16 Jul 2011 15:36:36 +0000
Message-ID: <4E21B000.1010003@alum.mit.edu>
Date: Sat, 16 Jul 2011 11:36:32 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: salud@ietf.org
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Jul 2011 15:36:38 -0000

I'm still inclined toward the multiple urn approach, which Dale now 
seems to be favoring as well.

I'm pretty much neutral about the changes to that approach Dale is 
suggesting.

I think we need to talk about how easy we want private extensions to be. 
The use of these leads to dialects that present some barriers to 
interop. However this is minimized as long as the private extensions are 
always subdivisions of some existing URN, since those that don't 
understand the extension can just ignore it and used the unsubdivided 
version.

Its worse with new top-level URNs. Maybe we shouldn't allow private ones 
at the top level.

	Thanks,
	Paul

On 7/15/11 4:50 PM, Worley, Dale R (Dale) wrote:
> [as individual]
>
> There are (IMHO) only 4 significant design points right now, in the
> vague state that crosses between requirements and design.  I think at
> this time we can decide on the more requirement-like aspects of the
> problem. -- Such as, will there be many or a few extension URNs
> defined?
>
> First, going through the points and looking at the advantages of
> alternatives.  There are interactions between the points, which
> suggest some choices which I will discuss at the end of this message.
>
>> - Shall we combine all the characteristics into one URN, or specify
>>    each characteristic in a separate URN?
>>
>> The first alternative leads to a very large set of possible URNs, but
>> leaves each URN interpretable in isolation.  The second alternative
>> uses a small set of URNs (possibly finite), but requires that they be
>> used in groups for complex renderings.  The ultimate logic for
>> combining the specified facets of the rendering is exactly the same,
>> but the way the complexity is expressed differs.
>
> Advantages of the single-URN approach:  Each URN can be interpreted
> alone, and code that considers Alert-Info as a simple list of URNs
> works by examining the URNs until it finds one that it can
> understand.  The ordering of the list only expresses the sequence in
> which the UA should check the URNs in order to find one it
> understands, and we do not have to suffer the conceptual problem that
> the interpretation of a list of URNs depends on their order.
>
> Advantages of the multiple-URN approach:  Each URN is simpler to
> understand.  In effect, we press the COMMA of the Alert-Info list into
> service as the major-level divider of the Alert-Info information.  In
> strict logic, this makes little difference, but it may be a significant
> human-factors difference.  As a result, the syntax of URNs is simpler,
> and in many practical situations, may be reduced to a fixed, finite
> list.
>
>> - In regard to extensibility, shall we arrange for each characteristic
>>    value to be subdividable into more narrowly-defined values, which
>>    are themselves subdividable, etc.?
>>
>> Allowing for infinite subdividability is good in abstract, but makes
>> the system more complex.  Are there practical requirements to be met?
>
> Advantages of multiple-level extensibility:  Reduced risk that vendors
> will decide they need to extend Alert-Info but can't do so within our
> framework, and so add some ugly hack.
>
> Advantages of simple extensibility:  The syntax of the URNs is simpler
> -- this is particularly so in the single-URN approach; in the
> multiple-URN approach, the simplification is fairly small.
>
>> - In regard to extensibility, what proprietary or non-standard
>>    extensions will be possible?
>
> If we have multiple-level extensibility, this question is answered
> automatically:  Any characteristic value can be subdivided by any
> vendor in any way.
>
> If extensibility is limited, then we have to plan where extensibility
> is admissible.
>
>> - How will non-standard extensions be designated?  (Will they be
>>    consistently marked by a particular prefix?  Will they be
>>    constructed from domain names?)
>>
>> There may be practical requirements as well -- How common will private
>> extensions be?  Do we need to worry about explicit "namespaces" for
>> extensions?
>
> There seem to be three approaches for building extension names:
> reversed domain names (a la Java packages), a prefix like "v-" or
> "[vendor name]-", or free-for-all.
>
> Advantages of reversed domain names:  Name organization is clearly
> delineated.
>
> Advantages of simple prefixes:  Names are shorter, but collision
> should still be rare.
>
> Advantages of free-for-all:  Easy transition of a vendor extension
> into standard usage.
>
> ----------
>
> There is particular complexity introduced when combining the
> single-URN approach and extensibility that allows a characteristic to
> be specified by a variable number of words.  I think that there will
> be more need for extensibility than we see right now, as vendors have
> a lot of legacy features to bring in.  So let me propose as a debating
> point:
>
> - multiple-URN
> - multiple-level extensibility
>
> To ease extensibility:
>
> - every defined URN can be extended by subdividing it
>
> I am undecided on what syntax is best for extension names.
>
> ----------
>
> Relative to draft-ietf-salud-alert-info-urns-02, this leads to changes
> like this:
>
>     service                        RFC XXXX  Alert-category for "service"
>                                              alert-identifiers.
>     service:normal                 RFC XXXX  Normal ring /rinback
>                                              rendering (default value).
>     service:call-waiting           RFC XXXX  Call waiting was
>                                              initiated at the other side
>                                              of the call.
>     service:forward                RFC XXXX  Call has been forwarded.
>     service:recall.calback         RFC XXXX  Recall due to callback.
>     service:recall.hold            RFC XXXX  Recall due to call hold.
>     service:recall.transfer        RFC XXXX  Recall due to callback.
>     service:private.<private-name>  RFC XXXX  Reserved for private
>                                              extensions.
>
> Remember that "service:normal" in this table means a URN
> <urn:alert:service:normal>.
>
> The "service:recall.xxx" group is turned into an additional level of
> qualification:  service:recall.callback becomes
> service:recall:callback, etc.  The reason for changing "." into ":"
> here is that I'm converting to a simpler syntax that is allowed by
> using the multiple-URN approach.
>
> service:private.<name>  remains as is, assuming that "private." is the
> prefix for all private names.  (See the 4th major issue.)  Although it
> seems to me to be excessively long.  Note that "." functions as a
> letter here, that the various "private.a", "private.b", etc. are not
> child nodes of the node service:private, they are siblings of
> service:forward, etc.
>
> But in addition, we would allow "private.<name>" children of all the
> standard URNs, e.g., service:forward:private.<name>  is a private
> variant of service:forward in the same way that service:private.<name>
> is an entirely private service-type designation.
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>


From john.elwell@siemens-enterprise.com  Mon Jul 18 02:12:24 2011
Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C9321F8B8C for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 02:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.485
X-Spam-Level: 
X-Spam-Status: No, score=-107.485 tagged_above=-999 required=5 tests=[AWL=1.114, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wo15rdFYPPZ3 for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 02:12:23 -0700 (PDT)
Received: from mail182.messagelabs.com (mail182.messagelabs.com [85.158.139.83]) by ietfa.amsl.com (Postfix) with SMTP id 5602821F851A for <salud@ietf.org>; Mon, 18 Jul 2011 02:12:22 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-2.tower-182.messagelabs.com!1310980339!10607855!1
X-StarScan-Version: 6.2.17; banners=-,-,-
X-Originating-IP: [62.134.46.10]
Received: (qmail 4575 invoked from network); 18 Jul 2011 09:12:19 -0000
Received: from unknown (HELO senmx12-mx) (62.134.46.10) by server-2.tower-182.messagelabs.com with SMTP; 18 Jul 2011 09:12:19 -0000
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id BF73723F03EC; Mon, 18 Jul 2011 11:12:18 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.57]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 18 Jul 2011 11:12:15 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "salud@ietf.org" <salud@ietf.org>
Date: Mon, 18 Jul 2011 11:12:12 +0200
Thread-Topic: [salud] Currently known technical issues
Thread-Index: AcxDzikfoYuKgm/cRyGrfYqr+yuCkABW9plQ
Message-ID: <A444A0F8084434499206E78C106220CA08F1C115ED@MCHP058A.global-ad.net>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com> <4E21B000.1010003@alum.mit.edu>
In-Reply-To: <4E21B000.1010003@alum.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
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 09:12:25 -0000

=20

> -----Original Message-----
> From: salud-bounces@ietf.org [mailto:salud-bounces@ietf.org]=20
> On Behalf Of Paul Kyzivat
> Sent: 16 July 2011 16:37
> To: salud@ietf.org
> Subject: Re: [salud] Currently known technical issues
>=20
> I'm still inclined toward the multiple urn approach, which Dale now=20
> seems to be favoring as well.
[JRE] That's my inclination too.

>=20
> I'm pretty much neutral about the changes to that approach Dale is=20
> suggesting.
>=20
> I think we need to talk about how easy we want private=20
> extensions to be.=20
> The use of these leads to dialects that present some barriers to=20
> interop. However this is minimized as long as the private=20
> extensions are=20
> always subdivisions of some existing URN, since those that don't=20
> understand the extension can just ignore it and used the unsubdivided=20
> version.
>=20
> Its worse with new top-level URNs. Maybe we shouldn't allow=20
> private ones=20
> at the top level.
[JRE] This is a good point. If a top level extension is not recognised, wha=
t would you fall back too? Of course, you might not recognise a top level v=
alue that has been introduced by subsequent standards action, so that is a =
problem in any case. I guess you just have to disregard a URN whose top lev=
el value you don't recognise. Even so, it might be good to remove "private"=
 from this top level, to discourage non-standardized top levels.

John

>=20
> 	Thanks,
> 	Paul
>=20
> On 7/15/11 4:50 PM, Worley, Dale R (Dale) wrote:
> > [as individual]
> >
> > There are (IMHO) only 4 significant design points right now, in the
> > vague state that crosses between requirements and design. =20
> I think at
> > this time we can decide on the more requirement-like aspects of the
> > problem. -- Such as, will there be many or a few extension URNs
> > defined?
> >
> > First, going through the points and looking at the advantages of
> > alternatives.  There are interactions between the points, which
> > suggest some choices which I will discuss at the end of=20
> this message.
> >
> >> - Shall we combine all the characteristics into one URN, or specify
> >>    each characteristic in a separate URN?
> >>
> >> The first alternative leads to a very large set of=20
> possible URNs, but
> >> leaves each URN interpretable in isolation.  The second alternative
> >> uses a small set of URNs (possibly finite), but requires=20
> that they be
> >> used in groups for complex renderings.  The ultimate logic for
> >> combining the specified facets of the rendering is exactly=20
> the same,
> >> but the way the complexity is expressed differs.
> >
> > Advantages of the single-URN approach:  Each URN can be interpreted
> > alone, and code that considers Alert-Info as a simple list of URNs
> > works by examining the URNs until it finds one that it can
> > understand.  The ordering of the list only expresses the sequence in
> > which the UA should check the URNs in order to find one it
> > understands, and we do not have to suffer the conceptual=20
> problem that
> > the interpretation of a list of URNs depends on their order.
> >
> > Advantages of the multiple-URN approach:  Each URN is simpler to
> > understand.  In effect, we press the COMMA of the=20
> Alert-Info list into
> > service as the major-level divider of the Alert-Info=20
> information.  In
> > strict logic, this makes little difference, but it may be a=20
> significant
> > human-factors difference.  As a result, the syntax of URNs=20
> is simpler,
> > and in many practical situations, may be reduced to a fixed, finite
> > list.
> >
> >> - In regard to extensibility, shall we arrange for each=20
> characteristic
> >>    value to be subdividable into more narrowly-defined=20
> values, which
> >>    are themselves subdividable, etc.?
> >>
> >> Allowing for infinite subdividability is good in abstract,=20
> but makes
> >> the system more complex.  Are there practical requirements=20
> to be met?
> >
> > Advantages of multiple-level extensibility:  Reduced risk=20
> that vendors
> > will decide they need to extend Alert-Info but can't do so=20
> within our
> > framework, and so add some ugly hack.
> >
> > Advantages of simple extensibility:  The syntax of the URNs=20
> is simpler
> > -- this is particularly so in the single-URN approach; in the
> > multiple-URN approach, the simplification is fairly small.
> >
> >> - In regard to extensibility, what proprietary or non-standard
> >>    extensions will be possible?
> >
> > If we have multiple-level extensibility, this question is answered
> > automatically:  Any characteristic value can be subdivided by any
> > vendor in any way.
> >
> > If extensibility is limited, then we have to plan where=20
> extensibility
> > is admissible.
> >
> >> - How will non-standard extensions be designated?  (Will they be
> >>    consistently marked by a particular prefix?  Will they be
> >>    constructed from domain names?)
> >>
> >> There may be practical requirements as well -- How common=20
> will private
> >> extensions be?  Do we need to worry about explicit "namespaces" for
> >> extensions?
> >
> > There seem to be three approaches for building extension names:
> > reversed domain names (a la Java packages), a prefix like "v-" or
> > "[vendor name]-", or free-for-all.
> >
> > Advantages of reversed domain names:  Name organization is clearly
> > delineated.
> >
> > Advantages of simple prefixes:  Names are shorter, but collision
> > should still be rare.
> >
> > Advantages of free-for-all:  Easy transition of a vendor extension
> > into standard usage.
> >
> > ----------
> >
> > There is particular complexity introduced when combining the
> > single-URN approach and extensibility that allows a=20
> characteristic to
> > be specified by a variable number of words.  I think that there will
> > be more need for extensibility than we see right now, as=20
> vendors have
> > a lot of legacy features to bring in.  So let me propose as=20
> a debating
> > point:
> >
> > - multiple-URN
> > - multiple-level extensibility
> >
> > To ease extensibility:
> >
> > - every defined URN can be extended by subdividing it
> >
> > I am undecided on what syntax is best for extension names.
> >
> > ----------
> >
> > Relative to draft-ietf-salud-alert-info-urns-02, this leads=20
> to changes
> > like this:
> >
> >     service                        RFC XXXX  Alert-category=20
> for "service"
> >                                              alert-identifiers.
> >     service:normal                 RFC XXXX  Normal ring /rinback
> >                                              rendering=20
> (default value).
> >     service:call-waiting           RFC XXXX  Call waiting was
> >                                              initiated at=20
> the other side
> >                                              of the call.
> >     service:forward                RFC XXXX  Call has been=20
> forwarded.
> >     service:recall.calback         RFC XXXX  Recall due to callback.
> >     service:recall.hold            RFC XXXX  Recall due to=20
> call hold.
> >     service:recall.transfer        RFC XXXX  Recall due to callback.
> >     service:private.<private-name>  RFC XXXX  Reserved for private
> >                                              extensions.
> >
> > Remember that "service:normal" in this table means a URN
> > <urn:alert:service:normal>.
> >
> > The "service:recall.xxx" group is turned into an additional level of
> > qualification:  service:recall.callback becomes
> > service:recall:callback, etc.  The reason for changing "." into ":"
> > here is that I'm converting to a simpler syntax that is allowed by
> > using the multiple-URN approach.
> >
> > service:private.<name>  remains as is, assuming that=20
> "private." is the
> > prefix for all private names.  (See the 4th major issue.) =20
> Although it
> > seems to me to be excessively long.  Note that "." functions as a
> > letter here, that the various "private.a", "private.b", etc. are not
> > child nodes of the node service:private, they are siblings of
> > service:forward, etc.
> >
> > But in addition, we would allow "private.<name>" children of all the
> > standard URNs, e.g., service:forward:private.<name>  is a private
> > variant of service:forward in the same way that=20
> service:private.<name>
> > is an entirely private service-type designation.
> >
> > Dale
> > _______________________________________________
> > salud mailing list
> > salud@ietf.org
> > https://www.ietf.org/mailman/listinfo/salud
> >
>=20
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
> =

From laura.liess.dt@googlemail.com  Mon Jul 18 08:11:04 2011
Return-Path: <laura.liess.dt@googlemail.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D06B621F8B82 for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 08:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.902
X-Spam-Level: 
X-Spam-Status: No, score=-3.902 tagged_above=-999 required=5 tests=[AWL=1.075,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66aPlKfQBT9H for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 08:11:00 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0627421F8B12 for <salud@ietf.org>; Mon, 18 Jul 2011 08:10:59 -0700 (PDT)
Received: by vws12 with SMTP id 12so3089026vws.31 for <salud@ietf.org>; Mon, 18 Jul 2011 08:10:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=E1UPZuO0jDBL68nif8jIYuGNdrFp0+JfeV+io8qIzoA=; b=tBA8o4wbcGVLYBcZMM6H4VxaiR0AwhUqUhkMVHah2P9G/cIUQ/G0FzHYLUDRVZ1Sdi 3e+nHbZ5TFJevaF8bdklDE3r7sMtoOH5DBkrd1Nmi4wOoTRxODqfK4YzxPGvB9SScdha 8lQtGcH9CZhp83qNUsnGiV7GCHu0WHoxikWoc=
MIME-Version: 1.0
Received: by 10.52.28.79 with SMTP id z15mr6370801vdg.365.1311001859503; Mon, 18 Jul 2011 08:10:59 -0700 (PDT)
Received: by 10.52.182.234 with HTTP; Mon, 18 Jul 2011 08:10:59 -0700 (PDT)
In-Reply-To: <A444A0F8084434499206E78C106220CA08F1C115ED@MCHP058A.global-ad.net>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com> <4E21B000.1010003@alum.mit.edu> <A444A0F8084434499206E78C106220CA08F1C115ED@MCHP058A.global-ad.net>
Date: Mon, 18 Jul 2011 17:10:59 +0200
Message-ID: <CACWXZj18OWu0-N4Fyz2kRsxTy+Xqnd=vUYJnkH2Ku1zYMAhesg@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 15:11:04 -0000

Hi,
Thank you for the elaborate and constructive input.
I also favor the multiple-URN with multiple-level extensibility. For
the multiple-URN approach we have orthogonal categories. Only one urn
of each category is allowed in a SIP-message. With this approach, we
can see the URNs of a category as nodes of a tree. With the
multiple-level extensibility, each tree can allways be extended by
adding new leaves (standardized or private). We have in principle a
separate tree for each category. We have to register each tree level
and each node with IANA. This is acceptable.

For the single-URN approach we don't have such a simple structure. We
have a very large set of of combinations, many of them do not make
sense. Maybe there are ways to restrict this large set of
combinations, but it seems to me that this approch is more problematic
than the multiple-URNs approach.

Also I am fine with using ":" instead of "." as separator and
restricting the usage of private extensions to the lower levels.

Thanks
Laura



2011/7/18 Elwell, John <john.elwell@siemens-enterprise.com>:
>
>
>> -----Original Message-----
>> From: salud-bounces@ietf.org [mailto:salud-bounces@ietf.org]
>> On Behalf Of Paul Kyzivat
>> Sent: 16 July 2011 16:37
>> To: salud@ietf.org
>> Subject: Re: [salud] Currently known technical issues
>>
>> I'm still inclined toward the multiple urn approach, which Dale now
>> seems to be favoring as well.
> [JRE] That's my inclination too.
>
>>
>> I'm pretty much neutral about the changes to that approach Dale is
>> suggesting.
>>
>> I think we need to talk about how easy we want private
>> extensions to be.
>> The use of these leads to dialects that present some barriers to
>> interop. However this is minimized as long as the private
>> extensions are
>> always subdivisions of some existing URN, since those that don't
>> understand the extension can just ignore it and used the unsubdivided
>> version.
>>
>> Its worse with new top-level URNs. Maybe we shouldn't allow
>> private ones
>> at the top level.
> [JRE] This is a good point. If a top level extension is not recognised, w=
hat would you fall back too? Of course, you might not recognise a top level=
 value that has been introduced by subsequent standards action, so that is =
a problem in any case. I guess you just have to disregard a URN whose top l=
evel value you don't recognise. Even so, it might be good to remove "privat=
e" from this top level, to discourage non-standardized top levels.
>
> John
>
>>
>> =A0 =A0 =A0 Thanks,
>> =A0 =A0 =A0 Paul
>>
>> On 7/15/11 4:50 PM, Worley, Dale R (Dale) wrote:
>> > [as individual]
>> >
>> > There are (IMHO) only 4 significant design points right now, in the
>> > vague state that crosses between requirements and design.
>> I think at
>> > this time we can decide on the more requirement-like aspects of the
>> > problem. -- Such as, will there be many or a few extension URNs
>> > defined?
>> >
>> > First, going through the points and looking at the advantages of
>> > alternatives. =A0There are interactions between the points, which
>> > suggest some choices which I will discuss at the end of
>> this message.
>> >
>> >> - Shall we combine all the characteristics into one URN, or specify
>> >> =A0 =A0each characteristic in a separate URN?
>> >>
>> >> The first alternative leads to a very large set of
>> possible URNs, but
>> >> leaves each URN interpretable in isolation. =A0The second alternative
>> >> uses a small set of URNs (possibly finite), but requires
>> that they be
>> >> used in groups for complex renderings. =A0The ultimate logic for
>> >> combining the specified facets of the rendering is exactly
>> the same,
>> >> but the way the complexity is expressed differs.
>> >
>> > Advantages of the single-URN approach: =A0Each URN can be interpreted
>> > alone, and code that considers Alert-Info as a simple list of URNs
>> > works by examining the URNs until it finds one that it can
>> > understand. =A0The ordering of the list only expresses the sequence in
>> > which the UA should check the URNs in order to find one it
>> > understands, and we do not have to suffer the conceptual
>> problem that
>> > the interpretation of a list of URNs depends on their order.
>> >
>> > Advantages of the multiple-URN approach: =A0Each URN is simpler to
>> > understand. =A0In effect, we press the COMMA of the
>> Alert-Info list into
>> > service as the major-level divider of the Alert-Info
>> information. =A0In
>> > strict logic, this makes little difference, but it may be a
>> significant
>> > human-factors difference. =A0As a result, the syntax of URNs
>> is simpler,
>> > and in many practical situations, may be reduced to a fixed, finite
>> > list.
>> >
>> >> - In regard to extensibility, shall we arrange for each
>> characteristic
>> >> =A0 =A0value to be subdividable into more narrowly-defined
>> values, which
>> >> =A0 =A0are themselves subdividable, etc.?
>> >>
>> >> Allowing for infinite subdividability is good in abstract,
>> but makes
>> >> the system more complex. =A0Are there practical requirements
>> to be met?
>> >
>> > Advantages of multiple-level extensibility: =A0Reduced risk
>> that vendors
>> > will decide they need to extend Alert-Info but can't do so
>> within our
>> > framework, and so add some ugly hack.
>> >
>> > Advantages of simple extensibility: =A0The syntax of the URNs
>> is simpler
>> > -- this is particularly so in the single-URN approach; in the
>> > multiple-URN approach, the simplification is fairly small.
>> >
>> >> - In regard to extensibility, what proprietary or non-standard
>> >> =A0 =A0extensions will be possible?
>> >
>> > If we have multiple-level extensibility, this question is answered
>> > automatically: =A0Any characteristic value can be subdivided by any
>> > vendor in any way.
>> >
>> > If extensibility is limited, then we have to plan where
>> extensibility
>> > is admissible.
>> >
>> >> - How will non-standard extensions be designated? =A0(Will they be
>> >> =A0 =A0consistently marked by a particular prefix? =A0Will they be
>> >> =A0 =A0constructed from domain names?)
>> >>
>> >> There may be practical requirements as well -- How common
>> will private
>> >> extensions be? =A0Do we need to worry about explicit "namespaces" for
>> >> extensions?
>> >
>> > There seem to be three approaches for building extension names:
>> > reversed domain names (a la Java packages), a prefix like "v-" or
>> > "[vendor name]-", or free-for-all.
>> >
>> > Advantages of reversed domain names: =A0Name organization is clearly
>> > delineated.
>> >
>> > Advantages of simple prefixes: =A0Names are shorter, but collision
>> > should still be rare.
>> >
>> > Advantages of free-for-all: =A0Easy transition of a vendor extension
>> > into standard usage.
>> >
>> > ----------
>> >
>> > There is particular complexity introduced when combining the
>> > single-URN approach and extensibility that allows a
>> characteristic to
>> > be specified by a variable number of words. =A0I think that there will
>> > be more need for extensibility than we see right now, as
>> vendors have
>> > a lot of legacy features to bring in. =A0So let me propose as
>> a debating
>> > point:
>> >
>> > - multiple-URN
>> > - multiple-level extensibility
>> >
>> > To ease extensibility:
>> >
>> > - every defined URN can be extended by subdividing it
>> >
>> > I am undecided on what syntax is best for extension names.
>> >
>> > ----------
>> >
>> > Relative to draft-ietf-salud-alert-info-urns-02, this leads
>> to changes
>> > like this:
>> >
>> > =A0 =A0 service =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0RFC XXX=
X =A0Alert-category
>> for "service"
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0alert-identifiers.
>> > =A0 =A0 service:normal =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 RFC XXXX =A0Nor=
mal ring /rinback
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0rendering
>> (default value).
>> > =A0 =A0 service:call-waiting =A0 =A0 =A0 =A0 =A0 RFC XXXX =A0Call wait=
ing was
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0initiated at
>> the other side
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0of the call.
>> > =A0 =A0 service:forward =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0RFC XXXX =A0Cal=
l has been
>> forwarded.
>> > =A0 =A0 service:recall.calback =A0 =A0 =A0 =A0 RFC XXXX =A0Recall due =
to callback.
>> > =A0 =A0 service:recall.hold =A0 =A0 =A0 =A0 =A0 =A0RFC XXXX =A0Recall =
due to
>> call hold.
>> > =A0 =A0 service:recall.transfer =A0 =A0 =A0 =A0RFC XXXX =A0Recall due =
to callback.
>> > =A0 =A0 service:private.<private-name> =A0RFC XXXX =A0Reserved for pri=
vate
>> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0extensions.
>> >
>> > Remember that "service:normal" in this table means a URN
>> > <urn:alert:service:normal>.
>> >
>> > The "service:recall.xxx" group is turned into an additional level of
>> > qualification: =A0service:recall.callback becomes
>> > service:recall:callback, etc. =A0The reason for changing "." into ":"
>> > here is that I'm converting to a simpler syntax that is allowed by
>> > using the multiple-URN approach.
>> >
>> > service:private.<name> =A0remains as is, assuming that
>> "private." is the
>> > prefix for all private names. =A0(See the 4th major issue.)
>> Although it
>> > seems to me to be excessively long. =A0Note that "." functions as a
>> > letter here, that the various "private.a", "private.b", etc. are not
>> > child nodes of the node service:private, they are siblings of
>> > service:forward, etc.
>> >
>> > But in addition, we would allow "private.<name>" children of all the
>> > standard URNs, e.g., service:forward:private.<name> =A0is a private
>> > variant of service:forward in the same way that
>> service:private.<name>
>> > is an entirely private service-type designation.
>> >
>> > Dale
>> > _______________________________________________
>> > salud mailing list
>> > salud@ietf.org
>> > https://www.ietf.org/mailman/listinfo/salud
>> >
>>
>> _______________________________________________
>> salud mailing list
>> salud@ietf.org
>> https://www.ietf.org/mailman/listinfo/salud
>>
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>

From dworley@avaya.com  Mon Jul 18 12:32:23 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28E75228011 for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 12:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.357
X-Spam-Level: 
X-Spam-Status: No, score=-103.357 tagged_above=-999 required=5 tests=[AWL=0.242, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uVO+kUm+e-lr for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 12:32:21 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 9E55C21F874A for <salud@ietf.org>; Mon, 18 Jul 2011 12:32:21 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHKJJE6HCzI1/2dsb2JhbABTEKdqd4h8p2UCm1WFXV8EmASLAFM
X-IronPort-AV: E=Sophos;i="4.67,223,1309752000"; d="scan'208";a="291424593"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by co300216-co-outbound.net.avaya.com with ESMTP; 18 Jul 2011 15:32:20 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 18 Jul 2011 15:25:07 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Mon, 18 Jul 2011 15:32:20 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "salud@ietf.org" <salud@ietf.org>
Date: Mon, 18 Jul 2011 15:32:20 -0400
Thread-Topic: [salud] Currently known technical issues
Thread-Index: AcxDzisMywDfMmaDQV2qpxf0fWJ6NgBsfIp5
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F578C@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com>, <4E21B000.1010003@alum.mit.edu>
In-Reply-To: <4E21B000.1010003@alum.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
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 19:32:23 -0000

> From: Paul Kyzivat [pkyzivat@alum.mit.edu]
>=20
> I'm still inclined toward the multiple urn approach, which Dale now
> seems to be favoring as well.

I favor the single-URN approach *in principle*.  But the multiple-URN
approach makes things easier on humans in several ways.  In
particular, it makes the syntax problems much simpler.  And while the
specifications are executed by computers (which won't be affected
much), the software is designed (and debugged) by humans.

In particular, it becomes so much easier to arrange for:

	urn:alert:service:recall:hold:level4:level5:avaya:foo

without it being confusing to someone trying to debug a system.

> I think we need to talk about how easy we want private extensions to be.
> The use of these leads to dialects that present some barriers to
> interop. However this is minimized as long as the private extensions are
> always subdivisions of some existing URN, since those that don't
> understand the extension can just ignore it and used the unsubdivided
> version.
>=20
> Its worse with new top-level URNs. Maybe we shouldn't allow private ones
> at the top level.

Yes, I think that is key:  "this is minimized as long as the private
extensions are always subdivisions of some existing URN"

I suspect there will be points where private top-level categories
would make sense -- but that will not be common.  The problem is that
vendors will frequently *think* they need a private top-level
category.

Can we enforce some sort of "expert review" requirement on vendor
extensions?

Dale

From dworley@avaya.com  Mon Jul 18 12:55:53 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 576D621F8456 for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 12:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.364
X-Spam-Level: 
X-Spam-Status: No, score=-103.364 tagged_above=-999 required=5 tests=[AWL=0.235, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ceNxNyx9Dn5Q for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 12:55:52 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF2D21F8422 for <salud@ietf.org>; Mon, 18 Jul 2011 12:51:51 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EANKNJE7GmAcF/2dsb2JhbABTp3p3iHynZAKbWIVdXwSYBItT
X-IronPort-AV: E=Sophos;i="4.67,223,1309752000"; d="scan'208";a="257238747"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 18 Jul 2011 15:51:50 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by co300216-co-erhwest-out.avaya.com with ESMTP; 18 Jul 2011 15:49:55 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Mon, 18 Jul 2011 15:51:49 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Laura Liess <laura.liess.dt@googlemail.com>, "Elwell, John" <john.elwell@siemens-enterprise.com>
Date: Mon, 18 Jul 2011 15:51:49 -0400
Thread-Topic: [salud] Currently known technical issues
Thread-Index: AcxFXOwo02AkExT7R5GhXplyh/D2TAAJJwJt
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F578D@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com> <4E21B000.1010003@alum.mit.edu> <A444A0F8084434499206E78C106220CA08F1C115ED@MCHP058A.global-ad.net>, <CACWXZj18OWu0-N4Fyz2kRsxTy+Xqnd=vUYJnkH2Ku1zYMAhesg@mail.gmail.com>
In-Reply-To: <CACWXZj18OWu0-N4Fyz2kRsxTy+Xqnd=vUYJnkH2Ku1zYMAhesg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 19:55:53 -0000

[as individual]

[BTW -- If I forget to mark a message, it means I am posting as an individu=
al.]

> From: Laura Liess [laura.liess.dt@googlemail.com]
>=20
> I also favor the multiple-URN with multiple-level extensibility. For
> the multiple-URN approach we have orthogonal categories. Only one urn
> of each category is allowed in a SIP-message.

I think we do not want to limit a set of URNs to have only one of each
category.  Instead, I think we want a rule that the earlier URNs are
to be given higher priority when two URNs conflict, but an arbitrary
sequence is allowed.  This allows implementing a number of actions
very simply:

- If you put a URN at the beginning of a sequence, its effect will be
  carried out if at all possible, regardless of the following URNs.
  E.g., if you put "urn:alert:service:recall" at the beginning of the
  string, the UA will indicate "recall" if it possibly can, and then
  beyond that, it will indicate whatever of the original URNs it can.

- If you put a URN at the end of a sequence, its effect will be added
  to the indication, as long as it is compatible with what was
  specified earlier.

- If you put two URNs in a sequence, and one is an extension of the
  other, they both have full effect (which is the same as the effect
  of the longest one).  So you can write this sequence without an
  error:

  urn:alert:service:recall,
      urn:priority:high,
          urn:alert:service:recall:private:avaya:X

  and get the effect "urn:alert:service:recall:private:avaya:X"

And in general, resolving these sorts of contradictory specifications
will be necessary because UAs won't have renderings for all
combinations of the values that they support.  E.g., a UA may have
renderings for:

#1   urn:alert:A:1, urn:alert:B:1
#2   urn:alert:A:1, urn:alert:B:2
#3   urn:alert:A:2, urn:alert:B:2

but no rendering for

     urn:alert:A:2, urn:alert:B:1

So if I send it "urn:alert:A:2, urn:alert:B:1", there is a
contradiction -- but the sender couldn't have predicted the
contradiction, because it isn't obvious from the syntax.

The concept is that

    Alert-Info: urn:alert:A:2, urn:alert:B:1

gives priority to the "A:2" part, and so the UA would choose rendering
#3 above.  But

    Alert-Info: urn:alert:B:1, urn:alert:A:2

gives priority to the "B:1" part, and so it would choose rendering #1
above.

Once you can handle this sort of contradiction, it's easy to handle
contradictory specifications of the same characteristic -- use the
first of them.

Dale

From pkyzivat@alum.mit.edu  Mon Jul 18 13:41:21 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5242C21F8504 for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 13:41:21 -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.020,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28XN7gnXym3x for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 13:41:20 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by ietfa.amsl.com (Postfix) with ESMTP id B420021F84FD for <salud@ietf.org>; Mon, 18 Jul 2011 13:41:20 -0700 (PDT)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta01.westchester.pa.mail.comcast.net with comcast id 9YXF1h0041ZXKqc51YhMru; Mon, 18 Jul 2011 20:41:21 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta21.westchester.pa.mail.comcast.net with comcast id 9YhG1h0040tdiYw3hYhHvx; Mon, 18 Jul 2011 20:41:18 +0000
Message-ID: <4E249A6A.1030202@alum.mit.edu>
Date: Mon, 18 Jul 2011 16:41:14 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com>, <4E21B000.1010003@alum.mit.edu> <CD5674C3CD99574EBA7432465FC13C1B222B1F578C@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F578C@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 20:41:21 -0000

On 7/18/11 3:32 PM, Worley, Dale R (Dale) wrote:
>> From: Paul Kyzivat [pkyzivat@alum.mit.edu]
>>
>> I'm still inclined toward the multiple urn approach, which Dale now
>> seems to be favoring as well.
>
> I favor the single-URN approach *in principle*.  But the multiple-URN
> approach makes things easier on humans in several ways.  In
> particular, it makes the syntax problems much simpler.  And while the
> specifications are executed by computers (which won't be affected
> much), the software is designed (and debugged) by humans.
>
> In particular, it becomes so much easier to arrange for:
>
> 	urn:alert:service:recall:hold:level4:level5:avaya:foo
>
> without it being confusing to someone trying to debug a system.
>
>> I think we need to talk about how easy we want private extensions to be.
>> The use of these leads to dialects that present some barriers to
>> interop. However this is minimized as long as the private extensions are
>> always subdivisions of some existing URN, since those that don't
>> understand the extension can just ignore it and used the unsubdivided
>> version.
>>
>> Its worse with new top-level URNs. Maybe we shouldn't allow private ones
>> at the top level.
>
> Yes, I think that is key:  "this is minimized as long as the private
> extensions are always subdivisions of some existing URN"
>
> I suspect there will be points where private top-level categories
> would make sense -- but that will not be common.  The problem is that
> vendors will frequently *think* they need a private top-level
> category.
>
> Can we enforce some sort of "expert review" requirement on vendor
> extensions?

We can specify any of the standard mechanisms that we want, including 
expert review.

	Thanks,
	Paul

From pkyzivat@alum.mit.edu  Mon Jul 18 13:43:54 2011
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400EA21F86C3 for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 13:43:54 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ul1e3loaHsyA for <salud@ietfa.amsl.com>; Mon, 18 Jul 2011 13:43:53 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [76.96.59.211]) by ietfa.amsl.com (Postfix) with ESMTP id 7615221F84FB for <salud@ietf.org>; Mon, 18 Jul 2011 13:43:53 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by QMTA11.westchester.pa.mail.comcast.net with comcast id 9YcR1h0061ei1Bg5BYjtw3; Mon, 18 Jul 2011 20:43:53 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([24.62.109.41]) by omta24.westchester.pa.mail.comcast.net with comcast id 9Yjr1h00l0tdiYw3kYjswF; Mon, 18 Jul 2011 20:43:52 +0000
Message-ID: <4E249B06.1090502@alum.mit.edu>
Date: Mon, 18 Jul 2011 16:43:50 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: salud@ietf.org
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com> <4E21B000.1010003@alum.mit.edu> <A444A0F8084434499206E78C106220CA08F1C115ED@MCHP058A.global-ad.net>, <CACWXZj18OWu0-N4Fyz2kRsxTy+Xqnd=vUYJnkH2Ku1zYMAhesg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F578D@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F578D@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2011 20:43:54 -0000

Dale,

I agree with the approach you are suggesting below.
But I think it requires some fairly careful specification of how these 
are to be interpreted if we are to get consistent implementation.
You already wrote some words about something similar in your earlier 
post on the single url approach, which could probably be adapted to fit 
here.

	Thanks,
	Paul

On 7/18/11 3:51 PM, Worley, Dale R (Dale) wrote:
> [as individual]
>
> [BTW -- If I forget to mark a message, it means I am posting as an individual.]
>
>> From: Laura Liess [laura.liess.dt@googlemail.com]
>>
>> I also favor the multiple-URN with multiple-level extensibility. For
>> the multiple-URN approach we have orthogonal categories. Only one urn
>> of each category is allowed in a SIP-message.
>
> I think we do not want to limit a set of URNs to have only one of each
> category.  Instead, I think we want a rule that the earlier URNs are
> to be given higher priority when two URNs conflict, but an arbitrary
> sequence is allowed.  This allows implementing a number of actions
> very simply:
>
> - If you put a URN at the beginning of a sequence, its effect will be
>    carried out if at all possible, regardless of the following URNs.
>    E.g., if you put "urn:alert:service:recall" at the beginning of the
>    string, the UA will indicate "recall" if it possibly can, and then
>    beyond that, it will indicate whatever of the original URNs it can.
>
> - If you put a URN at the end of a sequence, its effect will be added
>    to the indication, as long as it is compatible with what was
>    specified earlier.
>
> - If you put two URNs in a sequence, and one is an extension of the
>    other, they both have full effect (which is the same as the effect
>    of the longest one).  So you can write this sequence without an
>    error:
>
>    urn:alert:service:recall,
>        urn:priority:high,
>            urn:alert:service:recall:private:avaya:X
>
>    and get the effect "urn:alert:service:recall:private:avaya:X"
>
> And in general, resolving these sorts of contradictory specifications
> will be necessary because UAs won't have renderings for all
> combinations of the values that they support.  E.g., a UA may have
> renderings for:
>
> #1   urn:alert:A:1, urn:alert:B:1
> #2   urn:alert:A:1, urn:alert:B:2
> #3   urn:alert:A:2, urn:alert:B:2
>
> but no rendering for
>
>       urn:alert:A:2, urn:alert:B:1
>
> So if I send it "urn:alert:A:2, urn:alert:B:1", there is a
> contradiction -- but the sender couldn't have predicted the
> contradiction, because it isn't obvious from the syntax.
>
> The concept is that
>
>      Alert-Info: urn:alert:A:2, urn:alert:B:1
>
> gives priority to the "A:2" part, and so the UA would choose rendering
> #3 above.  But
>
>      Alert-Info: urn:alert:B:1, urn:alert:A:2
>
> gives priority to the "B:1" part, and so it would choose rendering #1
> above.
>
> Once you can handle this sort of contradiction, it's easy to handle
> contradictory specifications of the same characteristic -- use the
> first of them.
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>


From dworley@avaya.com  Wed Jul 20 12:16:37 2011
Return-Path: <dworley@avaya.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B12DA21F8748 for <salud@ietfa.amsl.com>; Wed, 20 Jul 2011 12:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.409
X-Spam-Level: 
X-Spam-Status: No, score=-103.409 tagged_above=-999 required=5 tests=[AWL=0.190, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gfvtO-U0VS+Q for <salud@ietfa.amsl.com>; Wed, 20 Jul 2011 12:16:37 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 27A2021F86D9 for <salud@ietf.org>; Wed, 20 Jul 2011 12:16:37 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAJsoJ07GmAcF/2dsb2JhbABTEKdXd4h8o1gCm1CFXl8EmBOLAVM
X-IronPort-AV: E=Sophos;i="4.67,237,1309752000"; d="scan'208";a="291918607"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 20 Jul 2011 15:16:36 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 20 Jul 2011 15:14:30 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 20 Jul 2011 15:16:30 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "salud@ietf.org" <salud@ietf.org>
Date: Wed, 20 Jul 2011 15:14:03 -0400
Thread-Topic: [salud] Currently known technical issues
Thread-Index: AcxFi2v3wmYHSfV+QfWK9WxJ4tFZWQBhcM72
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F57A3@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5759@DC-US1MBEX4.global.avaya.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F5781@DC-US1MBEX4.global.avaya.com> <4E21B000.1010003@alum.mit.edu> <A444A0F8084434499206E78C106220CA08F1C115ED@MCHP058A.global-ad.net>, <CACWXZj18OWu0-N4Fyz2kRsxTy+Xqnd=vUYJnkH2Ku1zYMAhesg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F578D@DC-US1MBEX4.global.avaya.com>, <4E249B06.1090502@alum.mit.edu>
In-Reply-To: <4E249B06.1090502@alum.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
Subject: Re: [salud] Currently known technical issues
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <salud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/salud>, <mailto:salud-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/salud>
List-Post: <mailto:salud@ietf.org>
List-Help: <mailto:salud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/salud>, <mailto:salud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2011 19:16:37 -0000

[as individual]

> From: Paul Kyzivat
>=20
> > I think we do not want to limit a set of URNs to have only one of each
> > category.  Instead, I think we want a rule that the earlier URNs are
> > to be given higher priority when two URNs conflict, but an arbitrary
> > sequence is allowed.
>=20
> But I think it requires some fairly careful specification of how these
> are to be interpreted if we are to get consistent implementation.
> You already wrote some words about something similar in your earlier
> post on the single url approach, which could probably be adapted to fit
> here.

Let me write another version of the algorithm I described some months
ago.  I'm sure that I can make it much clearer what the processing is
doing.  Then people can discuss whether that is a workable approach.

Dale
