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

Dean Willis <dean.willis@softarmor.com> Thu, 29 October 2009 00:55 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 CAFFA3A690F for <dispatch@core3.amsl.com>; Wed, 28 Oct 2009 17:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level:
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 vvk+VUUwiFEY for <dispatch@core3.amsl.com>; Wed, 28 Oct 2009 17:55:35 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 09D7B3A686A for <dispatch@ietf.org>; Wed, 28 Oct 2009 17:55:34 -0700 (PDT)
Received: from [192.168.2.105] (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 n9T0sHjO031292 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 28 Oct 2009 19:54:18 -0500
Message-Id: <FE639E83-0D65-462D-9394-02632199470E@softarmor.com>
From: Dean Willis <dean.willis@softarmor.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
In-Reply-To: <4AE880A4.3060702@cisco.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 28 Oct 2009 19:54:11 -0500
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> <4AE880A4.3060702@cisco.com>
X-Mailer: Apple Mail (2.936)
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: Thu, 29 Oct 2009 00:55:35 -0000

On Oct 28, 2009, at 12:34 PM, Paul Kyzivat wrote:

>
>
> 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.

Not if the intermediaries are B2BUAs.  I'm wondering about alert-info  
and authentication. Perhaps anything that can change the alerting  
model really OUGHT to be a B2BUA and capable of re-authenticating the  
request.

--
Dean