
From gonzalo.camarillo@ericsson.com  Tue Aug  9 03:00:23 2011
Return-Path: <gonzalo.camarillo@ericsson.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 5BAF721F898E for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 03:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HK8PiXn8uaHr for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 03:00:22 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by ietfa.amsl.com (Postfix) with ESMTP id 95F4E21F888A for <salud@ietf.org>; Tue,  9 Aug 2011 03:00:22 -0700 (PDT)
X-AuditID: c1b4fb3d-b7c17ae00000262e-af-4e410552e798
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 7B.12.09774.255014E4; Tue,  9 Aug 2011 12:00:50 +0200 (CEST)
Received: from [131.160.36.41] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.137.0; Tue, 9 Aug 2011 12:00:46 +0200
Message-ID: <4E41054E.6020608@ericsson.com>
Date: Tue, 9 Aug 2011 13:00:46 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: salud@ietf.org
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAA==
Subject: [salud] Shall we close the SALUD WG?
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: Tue, 09 Aug 2011 10:00:23 -0000

Folks,

during the last months, I have sent several low-energy warnings to this
list. Despite those warnings, I do not see any activity in this group.
My question to you is, why shouldn't we close this WG?

Thanks,

Gonzalo


From laura.liess.dt@googlemail.com  Tue Aug  9 04:18: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 C648A21F8B5D for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 04:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.117
X-Spam-Level: 
X-Spam-Status: No, score=-3.117 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWTGFjoDjvJQ for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 04:18:04 -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 0F7AF21F8B39 for <salud@ietf.org>; Tue,  9 Aug 2011 04:18:03 -0700 (PDT)
Received: by vxi29 with SMTP id 29so2408757vxi.31 for <salud@ietf.org>; Tue, 09 Aug 2011 04:18:31 -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; bh=UQh+MZcDwoPXZiXh3RlSl/fiInjhrutk0okrh3RziUs=; b=jG21kvp9aNjycZwnhTYT4dEph7KsEq+ajq+LO0WC8FUHCo+2F3ZYVyNWnozSbuV+Lx /sd1INEDw9HeGDs5g8u3hzsyURXgt+2IaUvRsiy/09q7RbYgfCtyHkdjhOemp/8segRX 665gMpLVtABqtVvmyHAy2tZvxUbmf/0G/IC9k=
MIME-Version: 1.0
Received: by 10.52.69.147 with SMTP id e19mr7154192vdu.399.1312888710941; Tue, 09 Aug 2011 04:18:30 -0700 (PDT)
Received: by 10.52.107.74 with HTTP; Tue, 9 Aug 2011 04:18:29 -0700 (PDT)
In-Reply-To: <4E41054E.6020608@ericsson.com>
References: <4E41054E.6020608@ericsson.com>
Date: Tue, 9 Aug 2011 13:18:29 +0200
Message-ID: <CACWXZj28Dz-Rza_Sz5n+rjsMeUp1mmKyTxKJtRP-Ked4iMpZDw@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Dale Worley <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: salud@ietf.org
Subject: Re: [salud] Shall we close the SALUD WG?
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: Tue, 09 Aug 2011 11:18:04 -0000

Gonzalo,

We had the last discussion between the 1-st and 20-th of July. We are
in principle done with the requirements and use cases.  We also have
in the current draft a mechanism proposal which is sufficient to cover
the use cases we know of.

Dale would like to have the mechanism to be more general and in his
last mail he promissed to come up with a proposal. I supposed people
were busy with the IETF-meeting. But you are right, it's time to
restart the discussion.

(I think little activity is often a problem for the mini-WGs.  This
does not necessarily mean that people are not interested in the issue.
)

Kind regards,
Laura


2011/8/9 Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>:
> Folks,
>
> during the last months, I have sent several low-energy warnings to this
> list. Despite those warnings, I do not see any activity in this group.
> My question to you is, why shouldn't we close this WG?
>
> Thanks,
>
> Gonzalo
>
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>

From aallen@rim.com  Tue Aug  9 08:09:25 2011
Return-Path: <aallen@rim.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 B193521F8BEC for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 08:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.169
X-Spam-Level: 
X-Spam-Status: No, score=-5.169 tagged_above=-999 required=5 tests=[AWL=0.034,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H1M2QlPTg3gE for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 08:09:25 -0700 (PDT)
Received: from mhs060cnc.rim.net (mhs060cnc.rim.net [208.65.73.34]) by ietfa.amsl.com (Postfix) with ESMTP id C2B8B21F8BB1 for <salud@ietf.org>; Tue,  9 Aug 2011 08:09:24 -0700 (PDT)
X-AuditID: 0a41282f-b7c9bae0000046eb-52-4e414db2fce5
Received: from XHT109CNC.rim.net (xht109cnc.rim.net [10.65.12.218]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by mhs060cnc.rim.net (SBG) with SMTP id 12.A1.18155.2BD414E4; Tue,  9 Aug 2011 15:09:38 +0000 (GMT)
Received: from XCT104ADS.rim.net (10.67.111.45) by XHT109CNC.rim.net (10.65.12.218) with Microsoft SMTP Server (TLS) id 8.3.159.2; Tue, 9 Aug 2011 11:09:53 -0400
Received: from XMB105ADS.rim.net ([fe80::c47b:e609:558:1b44]) by XCT104ADS.rim.net ([fe80::90f9:3b89:1d94:aa9b%22]) with mapi id 14.01.0289.001; Tue, 9 Aug 2011 10:09:51 -0500
From: Andrew Allen <aallen@rim.com>
To: Laura Liess <laura.liess.dt@googlemail.com>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Dale Worley <dworley@avaya.com>
Thread-Topic: [salud] Shall we close the SALUD WG?
Thread-Index: AQHMVns7gaX0PfkzaEKI7Nz1giYBUpUUsvyA///jpnA=
Date: Tue, 9 Aug 2011 15:09:51 +0000
Message-ID: <BBF5DDFE515C3946BC18D733B20DAD23020AF1@XMB105ADS.rim.net>
References: <4E41054E.6020608@ericsson.com> <CACWXZj28Dz-Rza_Sz5n+rjsMeUp1mmKyTxKJtRP-Ked4iMpZDw@mail.gmail.com>
In-Reply-To: <CACWXZj28Dz-Rza_Sz5n+rjsMeUp1mmKyTxKJtRP-Ked4iMpZDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.70.110.251]
Content-Type: text/plain; charset="us-ascii"
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKKsWRmVeSWpSXmKPExsXC5chzS3eTr6OfwarnRhZtu+YwW2xavpLJ Ys4VQ4u7HQcYHVg8Dq6cw+7x6+tVNo+nEyazeyxZ8pMpgCWqgdEmMS8vvySxJFUhJbU42VbJ JzU9MUchoCizLDG5UsElszg5JzEzN7VISSEzxVbJREmhICcxOTU3Na/EVimxoCA1L0XJjksB A9gAlWXmKaTmJeenZOal2yp5BvvrWliYWuoaKtnpIoGEf9wZfZNuMxZ0Slac6ljA2sDYJNLF yMkhIWAi8XbPQhYIW0ziwr31bF2MXBxCAr1MEo93T2WBcJYySky+fxHK2cwosXruNVaQFjYB ZYnlv2cwgtgiAm2MElOfMYHYzAKqEntvLwGyOTiEBQwlli+1hCgxkvh46jsrhG0l0TGpB2wz i4CKRP/0o2CtvAJuEicm/mIGsYUEiiTam6+CxTkFAiUWv/jNDmIzAl36/dQaqFXiEreezGeC +EBAYsme88wQtqjEy8f/WCFsRYknjZtZIOp1JBbs/sQGYWtLLFv4mhlir6DEyZlPWCD2Skvs OLmGcQKjxCwkK2YhaZ+FpH0WkvYFjCyrGAVzM4oNzAyS85L1ijJz9fJSSzYxgtOPhv4Oxr69 WocYBTgYlXh4Ba0c/YRYE8uKK3MPMUpwMCuJ8Ab6AIV4UxIrq1KL8uOLSnNSiw8xWgBDaCKz FHdyPjA15pXEGxsYoHCUxHmDpQ38hATSgSksOzW1ILUIppWJg1OqgTEpkevFkiPiSccl+/I2 Lt4dMM9bqSAo5EX7osCMLLYDb09NWP9RUEZlefK9lJvNmUdda/1nVx9+/eSTqNIa492fxFmf 3f+/lW8Cx/UTOUJ3M3SFg5WDbes7HGaLbn60aN3rovyI15v287C5Sc0s3Lhozbr9K3uz7654 KsbUVPFGO+lI6tMVWYeVWIozEg21mIuKEwFx4qWzWAMAAA==
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] Shall we close the SALUD WG?
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: Tue, 09 Aug 2011 15:09:25 -0000

3GPP have a release 8 dependency on draft-ietf-salud-alert-info-urns so we n=
eed a home for this work to continue. The 3GPP community is still interested=
 in this work and I believe the 3GPP community will contribute to this work=
 in order to complete it. I am willing to review the revised draft.

I think the best thing is to let the work continue in Salud.

As Laura indicates a WG with only one or two drafts is likely to have a low=
 level of activity. This was an issue I wanted to raise in the RAI area meet=
ing but due to the ECRIT emergency callback identifier offline discussion I=
 was unable to attend the RAI area meeting until just before it finished.

I think in dispatch in future we should try to ensure that WGs have a critic=
al mass (not just one or two drafts and not just a handful of people), howev=
er we need to still be able to work on drafts that are of interest to a limi=
ted number of stakeholders. Maybe some small tasks could be in future combin=
ed in a single WG rather than split between mini WGs. For instance maybe the=
 salud work and the cuss work could have been combined in a single WG. The p=
articipation in both of these has significant overlap. I know this may mean=
 re-chartering groups and potentially having a scope of somewhat unrelated w=
ork but I think we can be too purist with the principle of dividing the work=
 up narrowly. I think a balanced approach is needed where the level of parti=
cipation and amount of work is also considered as well as the relationship o=
f the scope of the work. 

Andrew

> -----Original Message-----
> From: salud-bounces@ietf.org [mailto:salud-bounces@ietf.org] On Behalf Of
> Laura Liess
> Sent: Tuesday, August 09, 2011 6:18 AM
> To: Gonzalo Camarillo; Dale Worley
> Cc: salud@ietf.org
> Subject: Re: [salud] Shall we close the SALUD WG?
> 
> Gonzalo,
> 
> We had the last discussion between the 1-st and 20-th of July. We are
> in principle done with the requirements and use cases.  We also have
> in the current draft a mechanism proposal which is sufficient to cover
> the use cases we know of.
> 
> Dale would like to have the mechanism to be more general and in his
> last mail he promissed to come up with a proposal. I supposed people
> were busy with the IETF-meeting. But you are right, it's time to
> restart the discussion.
> 
> (I think little activity is often a problem for the mini-WGs.  This
> does not necessarily mean that people are not interested in the issue.
> )
> 
> Kind regards,
> Laura
> 
> 
> 2011/8/9 Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>:
> > Folks,
> >
> > during the last months, I have sent several low-energy warnings to this
> > list. Despite those warnings, I do not see any activity in this group.
> > My question to you is, why shouldn't we close this WG?
> >
> > Thanks,
> >
> > Gonzalo
> >
> > _______________________________________________
> > 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

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

From dworley@avaya.com  Tue Aug  9 12:34:35 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 D6F4C11E80FF for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 12:34:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.462
X-Spam-Level: 
X-Spam-Status: No, score=-103.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXYN0sk19SZz for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 12:34:34 -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 953E011E80DD for <salud@ietf.org>; Tue,  9 Aug 2011 12:34:34 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlAIALCKQU6HCzI1/2dsb2JhbABCpz5wB4FHEihRARUpQicEGxqlLIN+ApwHhWdfBJgsi2A
X-IronPort-AV: E=Sophos;i="4.67,345,1309752000"; d="scan'208";a="261559447"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Aug 2011 15:34:58 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 Aug 2011 15:27:00 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Tue, 9 Aug 2011 15:34:57 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "salud@ietf.org" <salud@ietf.org>
Date: Tue, 9 Aug 2011 15:32:32 -0400
Thread-Topic: Interpreting a series of URNs
Thread-Index: AQHMVssemcDCcjYvsUmgvyVI+FVtJg==
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@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] Interpreting a series of URNs
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: Tue, 09 Aug 2011 19:34:35 -0000

[as individual]

Here is a draft of a description of how to interpret a series of URNs, even=
 if
the series has multiple URNs for a single alert-category or contradicstory
URNs.

--------------------

The general idea of the following rules is that each alert-info URN is
obeyed as much as it can be, given the limitations given by the
previous alert-info URNs in the sequence.  So in a series of URNs,
they are in strict priority order:  the first one has absolute
control, and the last one is obeyed only to the degree that it is
compatible with all the preceding URNs.

If a process adds a URN to the beginning of a series of URNs, then
that URN will be obeyed, and the remaining URNs can only modify its
effect.  If a process adds a URN to the end of a series of URNs, then
that URN can only modify the effect of the preceding URNs.



A series of URNs in the namespace 'alert' is interpreted by a device
in the following way:

The device that interprets the series of URNs knows the set of
alerting signals that it can generate and which alert URNs each signal
is compatible with.

The device interprets each URN in order, starting with the first.

As the device progresses through the series of URNs, it maintains
(implicitly or explicitly) the subset of its alerting signals that are
compatible with the URNs as they have been interpreted so far.
Initially, this set is the entire set of alerting signals that the
device can generate.

To interpret an additional URN, the device examines the URN to
determine if it recognizes the alert-category and the
alert-indication.  If the device does not recognize the
alert-category, it skips the URN and continues with the next URN,
without changing the current set of alerting signals.  If the device
does not recognize the entire alert-indication, it successively
removes the final 'name' until it does recognize what remains of the
alert-indication, and then continues with interpreting the shorter
URN.  If the device does not recognize even the first 'name' of the
alert-indication, it skips the URN and continues with the next URN (as
what remains of the URN provides no information at all about the
alterting signal).

The device then eliminates from the current set of alerting signals
all signals which are not compatible with the (possibly shortened) URN
that is being interpreted.  If one or more signals remain in the set,
the device continues with the next URN, using the reduced set of
signals.

If no signals in the current set are compatible with the URN, the
device shortens the URN by removing the final 'name' from its
alert-indication.  The device then returns to restricting the previous
current set based on compatibility with the shorter URN.  If one or
more signals then remain in the set, the device continues with the
next URN.

If again no signals remain in the set, the device shortens the URN
again by removing another 'name' from the alert-indication, and
attempts the restriction of the set again.  This process continues
until either one or more signals remain after the restriction, or the
first alert-indication of the URN is removed, at which point this URN
has been reduced to having no meaning (and thus excludes no alerting
signals), and the device continues on to interpret the next URN.

At the end of interpreting the sequence, the current set will
necessarily contain one or more alerting signals.  The device choses
one signal from among these signals in any way it likes.

Dale

From dworley@avaya.com  Tue Aug  9 12:44:21 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 122BD21F8B6C for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 12:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.464
X-Spam-Level: 
X-Spam-Status: No, score=-103.464 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBOzNYKmD48M for <salud@ietfa.amsl.com>; Tue,  9 Aug 2011 12:44:20 -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 91FE221F8B6A for <salud@ietf.org>; Tue,  9 Aug 2011 12:44:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAO+MQU7GmAcF/2dsb2JhbABCpz53gUABAQEBAgESKEQLAgEIDQghEDIlAQEEARIIGodLoWkCnAeFZ18EmCyLYA
X-IronPort-AV: E=Sophos;i="4.67,345,1309752000"; d="scan'208";a="296672693"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 09 Aug 2011 15:44:49 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 09 Aug 2011 15:41:40 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Tue, 9 Aug 2011 15:44:48 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "salud@ietf.org" <salud@ietf.org>
Date: Tue, 9 Aug 2011 15:41:56 -0400
Thread-Topic: [salud] Shall we close the SALUD WG?
Thread-Index: AcxWeztBaWLeK94ESTirMmRLDPXmhQAUSrvA
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F5804@DC-US1MBEX4.global.avaya.com>
References: <4E41054E.6020608@ericsson.com>
In-Reply-To: <4E41054E.6020608@ericsson.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] Shall we close the SALUD WG?
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: Tue, 09 Aug 2011 19:44:21 -0000

> From: Gonzalo Camarillo [Gonzalo.Camarillo@ericsson.com]
>=20
> during the last months, I have sent several low-energy warnings to this
> list. Despite those warnings, I do not see any activity in this group.
> My question to you is, why shouldn't we close this WG?

Since July 1, we have been moving the dicsussion along, in that we've
identified the 4 points that need to be resolved.

I admit that I've not done anything in the last two weeks, but I was
at the IETF for one week, and I was on vacation for the other week.  I
expect to be able to do more work over the next month.

Dale

From laura.liess.dt@googlemail.com  Thu Aug 11 07:57:32 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 F154121F86C7 for <salud@ietfa.amsl.com>; Thu, 11 Aug 2011 07:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.094
X-Spam-Level: 
X-Spam-Status: No, score=-3.094 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VofOUZZc3-YF for <salud@ietfa.amsl.com>; Thu, 11 Aug 2011 07:57:32 -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 C086D21F8571 for <salud@ietf.org>; Thu, 11 Aug 2011 07:57:31 -0700 (PDT)
Received: by vxi29 with SMTP id 29so2122029vxi.31 for <salud@ietf.org>; Thu, 11 Aug 2011 07:58:06 -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=Ft/jYQiNk1XsEyqHBtOlUQY8MG3S7PqHiNhf2wyGGW0=; b=thMVTrZwDCpaQoLtrrFZVnR6yVdMt2Okr7gY6k84Ud4VkJcul6VyCSUmw+KP11j4+Y XoxDZUE2n3umX1PFwZApHLinjh2wDiCDVbwLR4U+aFpzFSkn8Gt/egmmDZgO1aQ9tTRT FDRCZHwei+tkwHg917i3BIlRD9TNI8lJCbZhM=
MIME-Version: 1.0
Received: by 10.52.106.137 with SMTP id gu9mr8981287vdb.382.1313074685985; Thu, 11 Aug 2011 07:58:05 -0700 (PDT)
Received: by 10.52.110.198 with HTTP; Thu, 11 Aug 2011 07:58:05 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@DC-US1MBEX4.global.avaya.com>
References: <AQHMVssemcDCcjYvsUmgvyVI+FVtJg==> <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@DC-US1MBEX4.global.avaya.com>
Date: Thu, 11 Aug 2011 16:58:05 +0200
Message-ID: <CACWXZj0tOKs2podfQMgR+EbtO9kCAeqLeo-PkooBGuh0HsjOBg@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] Interpreting a series of URNs
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, 11 Aug 2011 14:57:33 -0000

Dale,

Thank you very much for the elaborate description. I have one question
on the algorithm.

 Take the following example:
The device has a set of alerting signals consisting which are for
<urn:alert:source:external>, <urn:alert:source:internal>,
<urn:alert:priority:low>, <urn:alert:priority:high>. It receives
<urn:alert:source:external>.  The device eliminates
<urn:alert:source:internal> and keeps  <urn:alert:source:external>,
<urn:alert:priority:low>, <urn:alert:priority:high>.  Could it happen
that it chooses to render <urn:alert:priority:high> or did I miss
something in the algorithm description?

Thanks a lot
Laura





2011/8/9 Worle R (Dale) <dworley@avaya.com>:
> [as individual]
>
> Here is a draft of a description of how to interpret a series of URNs, ev=
en if
> the series has multiple URNs for a single alert-category or contradicstor=
y
> URNs.
>
> --------------------
>
> The general idea of the following rules is that each alert-info URN is
> obeyed as much as it can be, given the limitations given by the
> previous alert-info URNs in the sequence. =A0So in a series of URNs,
> they are in strict priority order: =A0the first one has absolute
> control, and the last one is obeyed only to the degree that it is
> compatible with all the preceding URNs.
>
> If a process adds a URN to the beginning of a series of URNs, then
> that URN will be obeyed, and the remaining URNs can only modify its
> effect. =A0If a process adds a URN to the end of a series of URNs, then
> that URN can only modify the effect of the preceding URNs.
>
>
>
> A series of URNs in the namespace 'alert' is interpreted by a device
> in the following way:
>
> The device that interprets the series of URNs knows the set of
> alerting signals that it can generate and which alert URNs each signal
> is compatible with.
>
> The device interprets each URN in order, starting with the first.
>
> As the device progresses through the series of URNs, it maintains
> (implicitly or explicitly) the subset of its alerting signals that are
> compatible with the URNs as they have been interpreted so far.
> Initially, this set is the entire set of alerting signals that the
> device can generate.
>
> To interpret an additional URN, the device examines the URN to
> determine if it recognizes the alert-category and the
> alert-indication. =A0If the device does not recognize the
> alert-category, it skips the URN and continues with the next URN,
> without changing the current set of alerting signals. =A0If the device
> does not recognize the entire alert-indication, it successively
> removes the final 'name' until it does recognize what remains of the
> alert-indication, and then continues with interpreting the shorter
> URN. =A0If the device does not recognize even the first 'name' of the
> alert-indication, it skips the URN and continues with the next URN (as
> what remains of the URN provides no information at all about the
> alterting signal).
>
> The device then eliminates from the current set of alerting signals
> all signals which are not compatible with the (possibly shortened) URN
> that is being interpreted. =A0If one or more signals remain in the set,
> the device continues with the next URN, using the reduced set of
> signals.
>
> If no signals in the current set are compatible with the URN, the
> device shortens the URN by removing the final 'name' from its
> alert-indication. =A0The device then returns to restricting the previous
> current set based on compatibility with the shorter URN. =A0If one or
> more signals then remain in the set, the device continues with the
> next URN.
>
> If again no signals remain in the set, the device shortens the URN
> again by removing another 'name' from the alert-indication, and
> attempts the restriction of the set again. =A0This process continues
> until either one or more signals remain after the restriction, or the
> first alert-indication of the URN is removed, at which point this URN
> has been reduced to having no meaning (and thus excludes no alerting
> signals), and the device continues on to interpret the next URN.
>
> At the end of interpreting the sequence, the current set will
> necessarily contain one or more alerting signals. =A0The device choses
> one signal from among these signals in any way it likes.
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>

From dworley@avaya.com  Thu Aug 11 12:08:04 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 67CE721F8C29 for <salud@ietfa.amsl.com>; Thu, 11 Aug 2011 12:08:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.461
X-Spam-Level: 
X-Spam-Status: No, score=-103.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QiyFFv11xnou for <salud@ietfa.amsl.com>; Thu, 11 Aug 2011 12:08:03 -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 871B621F8C28 for <salud@ietf.org>; Thu, 11 Aug 2011 12:08:03 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAPknRE7GmAcF/2dsb2JhbABBp1l3gUABAQEBAgESKD8FCwIBCA0IIRAyJQEBBA4FCBEJh02hHAKcGIVoXwSYN4ti
X-IronPort-AV: E=Sophos;i="4.67,357,1309752000"; d="scan'208";a="261924680"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 11 Aug 2011 15:08:37 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 11 Aug 2011 15:05:21 -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, 11 Aug 2011 15:08:36 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Laura Liess <laura.liess.dt@googlemail.com>
Date: Thu, 11 Aug 2011 15:08:36 -0400
Thread-Topic: [salud] Interpreting a series of URNs
Thread-Index: AcxYNxtUXlfnb4QOS6GydPxN4ZXDbQAH4okl
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F580B@DC-US1MBEX4.global.avaya.com>
References: <AQHMVssemcDCcjYvsUmgvyVI+FVtJg==> <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@DC-US1MBEX4.global.avaya.com>, <CACWXZj0tOKs2podfQMgR+EbtO9kCAeqLeo-PkooBGuh0HsjOBg@mail.gmail.com>
In-Reply-To: <CACWXZj0tOKs2podfQMgR+EbtO9kCAeqLeo-PkooBGuh0HsjOBg@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] Interpreting a series of URNs
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, 11 Aug 2011 19:08:04 -0000

[as individual]

> From: Laura Liess [laura.liess.dt@googlemail.com]
>=20
> Thank you very much for the elaborate description.

BTW, I am interested in any advice on how to make the description
clearer, or about anything that is unclear.  If we can't make this
clear enough to be widely understood, we'll have to give it up and do
something simpler.

> I have one question on the algorithm.
>=20
> Take the following example:
>=20
> The device has a set of alerting signals consisting which are for
> <urn:alert:source:external>, <urn:alert:source:internal>,
> <urn:alert:priority:low>, <urn:alert:priority:high>. It receives
> <urn:alert:source:external>.  The device eliminates
> <urn:alert:source:internal> and keeps  <urn:alert:source:external>,
> <urn:alert:priority:low>, <urn:alert:priority:high>.  Could it happen
> that it chooses to render <urn:alert:priority:high> or did I miss
> something in the algorithm description?

I think it could.

Let me go through your example in more detail to make sure I
understand it.  I am going to call the signals "signal-external",
etc. to avoid confusing the signals with the URNs.  So there are 4
signals, each of which is compatible with the following URNs:

signal-external is compatible with:
    <urn:alert:source:external>
    <urn:alert:priority:low>
    <urn:alert:priority:high>

signal-internal is compatible with:
    <urn:alert:source:internal>
    <urn:alert:priority:low>
    <urn:alert:priority:high>

signal-low is compatible with:
    <urn:alert:source:external>
    <urn:alert:source:internal>
    <urn:alert:priority:low>

signal-high is compatible with:
    <urn:alert:source:external>
    <urn:alert:source:internal>
    <urn:alert:priority:high>

The device receives <urn:alert:source:external>, which eliminates one
signal, but leaves no criterion to choose from among the three
remaining signals.  The algorithm assumes that the device chooses one
of the remaining signals based on some unstated criterion.

I guess this example has this odd feature because the algorithm is
oriented toward ruling out signals that are incompatible with URNs,
rather than ranking which signals are most compatible with the URNs.

A similar example would be to have 3 signals, "signal-normal" used in
normal situations (internal, low priority), "signal-external" used for
external calls, and "signal-high" for his priority calls:

signal-normal is compatible with:
    <urn:alert:source:external>
    <urn:alert:source:internal>
    <urn:alert:priority:low>
    <urn:alert:priority:high>

signal-external is compatible with:
    <urn:alert:source:external>
    <urn:alert:priority:low>
    <urn:alert:priority:high>

signal-high is compatible with:
    <urn:alert:source:external>
    <urn:alert:source:internal>
    <urn:alert:priority:high>

Then if <urn:alert:source:internal> is received, signal-normal and
signal-high are both compatible.  So it seems that the device would
have to know to to choose signal-normal over signal-high.

What would make life easier in this situation is if we had 4 signals,
one for each combination of source and priority.

The benefit of the algorithm is that it knows when to remove the final
"name" from a URN, which is when the URN is compatible with none of
the remaining signals.  That allows people to extend URNs into even
more specialized URNs without causing devices to malfunction --
devices that do not understand the extension "name" will remove it.

But it seems that in a lot of common cases, we want to say that some
URNs are "more compatible" with certain signals than other signals.
I'll have to think about the ramifications of that...

Dale

From laura.liess.dt@googlemail.com  Fri Aug 12 07:16:58 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 8197F21F84BF for <salud@ietfa.amsl.com>; Fri, 12 Aug 2011 07:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.077
X-Spam-Level: 
X-Spam-Status: No, score=-3.077 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HDmLpaWEsRC for <salud@ietfa.amsl.com>; Fri, 12 Aug 2011 07:16:57 -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 4DF7021F842D for <salud@ietf.org>; Fri, 12 Aug 2011 07:16:57 -0700 (PDT)
Received: by vxi29 with SMTP id 29so3036657vxi.31 for <salud@ietf.org>; Fri, 12 Aug 2011 07:17:29 -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=i4iAnYMMgyOqtBCZgzHmTAdGsqhaPqo7HkS16PxXI3M=; b=Q1duVAFRNzohEKzYmLFdSJNMU8FzED1CVP6UabP6LwFPtrVrOV4hscAlXSO4jOO6Zb xx2+Za+2C6YE6njnbTrHGjR18f1srPp6F1JCmwj62/5YTzh5fsPEDHgP+y34aVpBo3yr Q3QeJFGyLfMIiAEwnwYXDqkWE6ez9kBZXMJyc=
MIME-Version: 1.0
Received: by 10.52.68.3 with SMTP id r3mr878954vdt.248.1313158649204; Fri, 12 Aug 2011 07:17:29 -0700 (PDT)
Received: by 10.52.110.198 with HTTP; Fri, 12 Aug 2011 07:17:28 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F580B@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@DC-US1MBEX4.global.avaya.com> <CACWXZj0tOKs2podfQMgR+EbtO9kCAeqLeo-PkooBGuh0HsjOBg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F580B@DC-US1MBEX4.global.avaya.com>
Date: Fri, 12 Aug 2011 16:17:28 +0200
Message-ID: <CACWXZj19At9p=mWEKGH-sf16UGm3Kd--4acocq9JghPn+MT=2A@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] Interpreting a series of URNs
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, 12 Aug 2011 14:16:58 -0000

Dale,

Please see inline.

2011/8/11 Worley, Dale R (Dale) <dworley@avaya.com>:
> [as individual]
>
>> From: Laura Liess [laura.liess.dt@googlemail.com]
>>
>> Thank you very much for the elaborate description.
>
> BTW, I am interested in any advice on how to make the description
> clearer, or about anything that is unclear. =A0If we can't make this
> clear enough to be widely understood, we'll have to give it up and do
> something simpler.

[LL] I like your idea and I am not sure at all it is easy to find
something simpler.

>
>> I have one question on the algorithm.
>>
>> Take the following example:
>>
>> The device has a set of alerting signals consisting which are for
>> <urn:alert:source:external>, <urn:alert:source:internal>,
>> <urn:alert:priority:low>, <urn:alert:priority:high>. It receives
>> <urn:alert:source:external>. =A0The device eliminates
>> <urn:alert:source:internal> and keeps =A0<urn:alert:source:external>,
>> <urn:alert:priority:low>, <urn:alert:priority:high>. =A0Could it happen
>> that it chooses to render <urn:alert:priority:high> or did I miss
>> something in the algorithm description?
>
> I think it could.
>
> Let me go through your example in more detail to make sure I
> understand it. =A0I am going to call the signals "signal-external",
> etc. to avoid confusing the signals with the URNs. =A0So there are 4
> signals, each of which is compatible with the following URNs:
>
> signal-external is compatible with:
> =A0 =A0<urn:alert:source:external>
> =A0 =A0<urn:alert:priority:low>
> =A0 =A0<urn:alert:priority:high>
>
> signal-internal is compatible with:
> =A0 =A0<urn:alert:source:internal>
> =A0 =A0<urn:alert:priority:low>
> =A0 =A0<urn:alert:priority:high>
>
> signal-low is compatible with:
> =A0 =A0<urn:alert:source:external>
> =A0 =A0<urn:alert:source:internal>
> =A0 =A0<urn:alert:priority:low>
>
> signal-high is compatible with:
> =A0 =A0<urn:alert:source:external>
> =A0 =A0<urn:alert:source:internal>
> =A0 =A0<urn:alert:priority:high>
>
> The device receives <urn:alert:source:external>, which eliminates one
> signal, but leaves no criterion to choose from among the three
> remaining signals. =A0The algorithm assumes that the device chooses one
> of the remaining signals based on some unstated criterion.
>
> I guess this example has this odd feature because the algorithm is
> oriented toward ruling out signals that are incompatible with URNs,
> rather than ranking which signals are most compatible with the URNs.

Exactly. This is the reason why I choosed this example.
>
> A similar example would be to have 3 signals, "signal-normal" used in
> normal situations (internal, low priority), "signal-external" used for
> external calls, and "signal-high" for his priority calls:
>
> signal-normal is compatible with:
> =A0 =A0<urn:alert:source:external>
> =A0 =A0<urn:alert:source:internal>
> =A0 =A0<urn:alert:priority:low>
> =A0 =A0<urn:alert:priority:high>
>
> signal-external is compatible with:
> =A0 =A0<urn:alert:source:external>
> =A0 =A0<urn:alert:priority:low>
> =A0 =A0<urn:alert:priority:high>
>
> signal-high is compatible with:
> =A0 =A0<urn:alert:source:external>
> =A0 =A0<urn:alert:source:internal>
> =A0 =A0<urn:alert:priority:high>
>
> Then if <urn:alert:source:internal> is received, signal-normal and
> signal-high are both compatible. =A0So it seems that the device would
> have to know to to choose signal-normal over signal-high.
>
> What would make life easier in this situation is if we had 4 signals,
> one for each combination of source and priority.
>
> The benefit of the algorithm is that it knows when to remove the final
> "name" from a URN, which is when the URN is compatible with none of
> the remaining signals. =A0That allows people to extend URNs into even
> more specialized URNs without causing devices to malfunction --
> devices that do not understand the extension "name" will remove it.

[LL] I see another advantage, from the point of view of the network:
Proxies will want to overwrite Alert-Info URNs in certain situations.
E.g. carriers don't want
their customers to be bothered by SPIT INVITEs with <urn:alert:priority:hig=
h>,
so they need a mean to tell the end device not to play the signal. If
only one urn per category is allowed, the only thing the proxy can do
is to find out if <urn:alert:priority:high> or a child of it is
present and delete or overwrite it.
However, if the call is a call between two units of the same
enterprise with the VoIP traffic traversing the carrier network, the
caller and the callee may not want  <urn:alert:priority:high> to be
overwritten by the carrier. This is not possible with the rules
described above without a lot of provisioning at the carrier, which is
probably not posible at all in practice.
With your algorithm principle, the carrier only needs to add
<urn:alert:priority:normal > at the beginning of the urn-chain. The
end device will have both URNs,  <urn:alert:priority:normal > and
<urn:alert:priority:high >, in that order. Most end devices would
eliminate devices
<urn:alert:priority:high >. Enterprise devices, which will recognise
the sender as beeing from the own enterprise, could keep and render
it. The algoritm is great and gives us a lot of flexibility.

It's just that we probably need to make some small modifications for
the algorithm to work in all cases. I think this is possible if we add
some non-critical restrictions and some actions.

1) We require the sets of the Alert-Info URNs to consist of a number
of disjunct trees. The roots of the trees are the alert-categories.
"private" branches can be added everywhere in a tree. There are no
"private" trees.

2) Every URN received by the end device is then on some branch of one
of the trees. Let's select these tree branches.

3) Every device has a basic set of supported signals,  which
correspond to Alert-Info URNs. (Additionaly it may have a set of
additional supported signals which are combinations of two or more
basic signals from different trees.) Let's select the tree branches
which contain at least one signal from the basic signal set.

4) Put the tree branches selected at 2) and the tree branches selected
at 3) on top of each other.

5) Eliminate all  received URNs which are not equal to a suppoted
signal or do not have at least a supported signal as a parent.
(Eliminate all received URNs for which we don't have a rendering.)

6) Eliminate all suported signals that are not equal to a received URN
or do not have at least a a received URN as a child, but keep at least
the default signal for each category. ( Eliminate all signals for
which I didn't received any indication to render them.)or take Take
the I didn't received any indication to render this signal, so I take
the default. )

7) We have now trees with one or more branches left. The leafs are
allways a received URN, "oldest" node is allways a basic signal which
the device can render.

8) At this point the device has a set of received URNs which have all
al least one parent which is a signal (this means we know how to
render it). If there is only one received URN left in a category, then
the device keeps its youngest signal parent.

9) If we have more than one received URN left in a tree we need
priority rules. The URN order in the Alert-Info-header is used if the
device has no other rules. In this case the device keeps the youngest
signal parent of the first URN in this category from the
Alert-Info-header.

10) The device can have special rules. Back again to the "priority"
example, the enterprise device which knows that the message is from
within the enterprise via a carrier which inserts the URNs at the
beginning of the Alert-Info-header, could have a rule saying that not
the first, but the last URN has to be be rendered.

My intention was that the algorithm is in principle the same with what
you proposed, just that it eliminates the signals for which no
indication was received.  I am not sure if it works.

Thanks a lot
Laura








>
> But it seems that in a lot of common cases, we want to say that some
> URNs are "more compatible" with certain signals than other signals.
> I'll have to think about the ramifications of that...
>
> Dale
>

From dworley@avaya.com  Fri Aug 19 13:17:31 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 2392021F8B6E for <salud@ietfa.amsl.com>; Fri, 19 Aug 2011 13:17:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.951
X-Spam-Level: 
X-Spam-Status: No, score=-102.951 tagged_above=-999 required=5 tests=[AWL=-0.352, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sWzW63iVS9Li for <salud@ietfa.amsl.com>; Fri, 19 Aug 2011 13:17:30 -0700 (PDT)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 51AFC21F8B6D for <salud@ietf.org>; Fri, 19 Aug 2011 13:17:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAOTETk7GmAcF/2dsb2JhbABBqA13gUABAQEBAxIoPxACAQgNKRAyJQEBBA4NGqRAApwOhWlfBJg9i2c
X-IronPort-AV: E=Sophos;i="4.68,252,1312171200"; d="scan'208";a="202775863"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 19 Aug 2011 16:18:03 -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; 19 Aug 2011 16:14:20 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.172]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 19 Aug 2011 16:18:03 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Laura Liess <laura.liess.dt@googlemail.com>
Date: Fri, 19 Aug 2011 16:18:01 -0400
Thread-Topic: [salud] Interpreting a series of URNs
Thread-Index: AcxY+prNdfU7ArSVS9OJE9cQaVJORwFsEdi8
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B222B1F583D@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@DC-US1MBEX4.global.avaya.com> <CACWXZj0tOKs2podfQMgR+EbtO9kCAeqLeo-PkooBGuh0HsjOBg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F580B@DC-US1MBEX4.global.avaya.com>, <CACWXZj19At9p=mWEKGH-sf16UGm3Kd--4acocq9JghPn+MT=2A@mail.gmail.com>
In-Reply-To: <CACWXZj19At9p=mWEKGH-sf16UGm3Kd--4acocq9JghPn+MT=2A@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] Interpreting a series of URNs
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, 19 Aug 2011 20:17:31 -0000

[as individual]

I am just now getting back to this work, and I haven't had time to fully
digest your response.

However, as an addendum to my previous message, the following may be
a useful approach:

- Normatively, state a few requirements that the process of interpreting UR=
Ns
  must follow.  I believe that we can keep these principles to a small numb=
er,
  probably five or fewer.

- Non-normatively, provide an algorithm whose results satisfy the requireme=
nts.
  This algorithm would be similar to the one I stated previously, with addi=
tions
  to handle situations like the one you proposed.  An example algorithm (1)=
 proves
  that the normative requirements can be met, and (2) provides an initial i=
mplementation
  for manufacturers.

What could these requirements be?  I think we want to have the following tw=
o
requirements, but there may be more.

- Each alert-info URN has precedence over all URNs that follow it, and
  its interpretation is subordinate to all URNs that precede it.

- If the UA cannot implement the effect of a URN (because it does not
  recognize the URN or the URN's effect is precluded by
  higher-precedence, preceding URNs), the UA must remove the final
  "name" of the URN repeatedly until either (1) the resulting URN is
  recognized and can be given effect, or (2) the resulting URN is
  reduced to having no "names".  In case (2), the entire URN cannot be
  given effect, so it is ignored.

Dale


From laura.liess.dt@googlemail.com  Mon Aug 22 20:35:47 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 05B1D21F85AE for <salud@ietfa.amsl.com>; Mon, 22 Aug 2011 20:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.065
X-Spam-Level: 
X-Spam-Status: No, score=-3.065 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPtRyDlsgZVd for <salud@ietfa.amsl.com>; Mon, 22 Aug 2011 20:35:46 -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 406EF21F85AB for <salud@ietf.org>; Mon, 22 Aug 2011 20:35:43 -0700 (PDT)
Received: by vws12 with SMTP id 12so5761268vws.31 for <salud@ietf.org>; Mon, 22 Aug 2011 20:36:49 -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=5doalzZJeH5RNuclw17z6rJWBPY4bYAA+DdkaS82wNQ=; b=qJ10SUh39QaDV2+sbR0lvGNGUUZSiuAO3Pi8k8wrRy356t3ZTm8UcUv6VJafNfoEq4 LOmfWvI9NGKRr3TaAlTci/3SWC6g+RyhmICU3jaL0vbbPpX687SpJDS21HVOy2DVj39a dsH/TCVWHoSeA8434OPaWsXsjIW6jamQcJ/sk=
MIME-Version: 1.0
Received: by 10.52.33.112 with SMTP id q16mr2909470vdi.114.1314070609283; Mon, 22 Aug 2011 20:36:49 -0700 (PDT)
Received: by 10.52.110.101 with HTTP; Mon, 22 Aug 2011 20:36:49 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222B1F583D@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B222B1F5803@DC-US1MBEX4.global.avaya.com> <CACWXZj0tOKs2podfQMgR+EbtO9kCAeqLeo-PkooBGuh0HsjOBg@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F580B@DC-US1MBEX4.global.avaya.com> <CACWXZj19At9p=mWEKGH-sf16UGm3Kd--4acocq9JghPn+MT=2A@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B222B1F583D@DC-US1MBEX4.global.avaya.com>
Date: Tue, 23 Aug 2011 05:36:49 +0200
Message-ID: <CACWXZj2vGjQriU6_Zpq01==oRY7EV-Y08oT_T8sDGaW2BTVBRA@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] Interpreting a series of URNs
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: Tue, 23 Aug 2011 03:35:47 -0000

Dale,

We  we have to specify the algorithm anyway. I think we can derive the
normative rules from it.

(I will be away on vacation during the next 3 weeks. I don't know if I
will have internet access.)

Thanks
Laura



2011/8/19 Worley, Dale R (Dale) <dworley@avaya.com>:
> [as individual]
>
> I am just now getting back to this work, and I haven't had time to fully
> digest your response.
>
> However, as an addendum to my previous message, the following may be
> a useful approach:
>
> - Normatively, state a few requirements that the process of interpreting =
URNs
> =A0must follow. =A0I believe that we can keep these principles to a small=
 number,
> =A0probably five or fewer.
>
> - Non-normatively, provide an algorithm whose results satisfy the require=
ments.
> =A0This algorithm would be similar to the one I stated previously, with a=
dditions
> =A0to handle situations like the one you proposed. =A0An example algorith=
m (1) proves
> =A0that the normative requirements can be met, and (2) provides an initia=
l implementation
> =A0for manufacturers.
>
> What could these requirements be? =A0I think we want to have the followin=
g two
> requirements, but there may be more.
>
> - Each alert-info URN has precedence over all URNs that follow it, and
> =A0its interpretation is subordinate to all URNs that precede it.
>
> - If the UA cannot implement the effect of a URN (because it does not
> =A0recognize the URN or the URN's effect is precluded by
> =A0higher-precedence, preceding URNs), the UA must remove the final
> =A0"name" of the URN repeatedly until either (1) the resulting URN is
> =A0recognized and can be given effect, or (2) the resulting URN is
> =A0reduced to having no "names". =A0In case (2), the entire URN cannot be
> =A0given effect, so it is ignored.
>
> Dale
>
>
