Re: [dispatch] New version for the Alert-Info URNs draft: draft-liess-dispatch-alert-info-urns-00.txt

Paul Kyzivat <pkyzivat@cisco.com> Wed, 28 October 2009 17:34 UTC

Return-Path: <pkyzivat@cisco.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D67663A6A45 for <dispatch@core3.amsl.com>; Wed, 28 Oct 2009 10:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level:
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SY8F5pMCBBAy for <dispatch@core3.amsl.com>; Wed, 28 Oct 2009 10:34:38 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 686893A69A7 for <dispatch@ietf.org>; Wed, 28 Oct 2009 10:34:19 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEACsd6EpAZnwN/2dsb2JhbADCQ5gxhD8E
X-IronPort-AV: E=Sophos;i="4.44,641,1249257600"; d="scan'208";a="65374996"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 28 Oct 2009 17:34:31 +0000
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n9SHYUx1023191; Wed, 28 Oct 2009 17:34:31 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Oct 2009 13:34:29 -0400
Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Oct 2009 13:34:29 -0400
Message-ID: <4AE880A4.3060702@cisco.com>
Date: Wed, 28 Oct 2009 13:34:28 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
References: <40FB0FFB97588246A1BEFB05759DC8A0038854EC@S4DE9JSAANI.ost.t-com.de> <4ADCCF93.2070208@cisco.com> <40FB0FFB97588246A1BEFB05759DC8A003885F8F@S4DE9JSAANI.ost.t-com.de> <4ADFB028.3010604@cisco.com> <40FB0FFB97588246A1BEFB05759DC8A0038FD976@S4DE9JSAANI.ost.t-com.de> <4AE850B9.80607@cisco.com> <4AE872F1.90108@softarmor.com>
In-Reply-To: <4AE872F1.90108@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Oct 2009 17:34:29.0777 (UTC) FILETIME=[E74E1010:01CA57F4]
Cc: anwars@avaya.com, dispatch@ietf.org, L.Liess@telekom.de
Subject: Re: [dispatch] New version for the Alert-Info URNs draft: draft-liess-dispatch-alert-info-urns-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 17:34:38 -0000

Dean Willis wrote:
> Paul Kyzivat wrote:
> 
>> But that works more easily if the Alert-Info URNs are mutually
>> exclusive, so the recipient just chooses one it understands and renders
>> that.
>>
>> But I guess it can still work in the multi-dimensional approach. Each
>> URN that is understood must imply the values of one or more of those
>> dimensions.
> 
> this is starting to sound like multipart/related and multipart/alternative.
> 
> Perhaps we are barking up the wrong tree, and alerts should be body
> parts selected by a new content-disposition?

Did you imply a smiley on this message?

On the off chance that you did not, its important that it be possible 
for intermediaries to add the Alert-Info, which pretty much excludes 
using body parts.

	Thanks,
	Paul