IETF Logo Mail Archive

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

Dean Willis <dean.willis@softarmor.com> Wed, 28 October 2009 16:36 UTC

Return-Path: <dean.willis@softarmor.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 19F7A28C222 for <dispatch@core3.amsl.com>; Wed, 28 Oct 2009 09:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level:
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GeV7Ve0yJOgt for <dispatch@core3.amsl.com>; Wed, 28 Oct 2009 09:35:59 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 55A8228C206 for <dispatch@ietf.org>; Wed, 28 Oct 2009 09:35:59 -0700 (PDT)
Received: from [192.168.2.102] (cpe-76-182-198-42.tx.res.rr.com [76.182.198.42]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id n9SGa7uZ028172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 28 Oct 2009 11:36:09 -0500
Message-ID: <4AE872F1.90108@softarmor.com>
Date: Wed, 28 Oct 2009 11:36:01 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@cisco.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>
In-Reply-To: <4AE850B9.80607@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 16:36:00 -0000

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?

--
dean

v2.23.0 | Report a Bug | By Email