
From laura.liess.dt@googlemail.com  Wed Jun  1 06:57:12 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 2439BE081F for <salud@ietfa.amsl.com>; Wed,  1 Jun 2011 06:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.954
X-Spam-Level: 
X-Spam-Status: No, score=-2.954 tagged_above=-999 required=5 tests=[AWL=0.023,  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 zFrre2MXONO9 for <salud@ietfa.amsl.com>; Wed,  1 Jun 2011 06:57:11 -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 81615E07FD for <salud@ietf.org>; Wed,  1 Jun 2011 06:57:11 -0700 (PDT)
Received: by vxg33 with SMTP id 33so5693389vxg.31 for <salud@ietf.org>; Wed, 01 Jun 2011 06:57:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=PUVr3Ypa1SPDOdPslMoTdHkAHXKJV/UkYTkm4lGBHEo=; b=CffcPC1oxo6Ur93xeB8PNpMtpZfxctLUQm15bNUVqv4s+a0ELjMcCjfz2c/5EBamJ0 h0dtly/URZ5h8EdHkl2ST45GA9OAEP9nTJL2ZiHRGC6CrXm8K+Uv7T6n00ORvAQy9JXh IeqU6MTJihMdNmTj/D63btmoMwxp4+SnZPOTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=iDYY/lQPMpy8i58WTqac1zjysqN6Y14HLB5yxWrT4OHdIbQA3N1B1arIbl3gQMjiYF MuVeHmFoqzNrWuEwFGabHcNGIg7qVgC4DNSFT8o3mAPn+t0QojLSeJKD7F/i3VUKRQux rEpMa4fHfJb4dFF3Ib79pAGkE+ZoNSKwM3wHc=
MIME-Version: 1.0
Received: by 10.52.97.33 with SMTP id dx1mr2907623vdb.34.1306936630896; Wed, 01 Jun 2011 06:57:10 -0700 (PDT)
Received: by 10.52.111.35 with HTTP; Wed, 1 Jun 2011 06:57:10 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B222907E980@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>
Date: Wed, 1 Jun 2011 15:57:10 +0200
Message-ID: <BANLkTi=iMCxzo-8NX3MEWxkVJdumC_DBag@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: Wed, 01 Jun 2011 13:57:12 -0000

Dale,

Please see inline.

>
> First, let us try to list all the open technical issues on the mailing li=
st.
[LL] You are right.

=A0The issues that I know of are:
>
> - 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)?

[LL]  I will try to recapitulate the history of this subject and the
issues which were raised for both alternatives:
- In the initial draft in bliss we had some kind of single URN.
- Adam objected we have to register a very high number of URN with
IANA to cover all possible combinations.
- Additional issues with single URN: Intermediaries may want to insert
or  delete elements of the URN or add an URN. We need rules for this
(e.g. a proxy want to discard priority:high).
-  Paul came up with the multiple URN proposal and the values
definitions as currently described in Section 5.

Would we have advantages if  switching back to single URN? Even for
single URNs, we need combination/removal rules or rules for
inserting/removing parts of URNs in case intermediaries whant to
change the rendering at the receiving UA. And what do we handle the
number of IANA registrations?

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

[LL] I think they are. E.g.  we already defined
urn:alert:source:family. If there is a need to be more specific, we
can subdivide this into urn:alert:source:family.normal (or default, or
whatever) and urn:alert:source:family.children. Or maybe I did not
understand you correctly?

>
> - 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?)

[LL] We currently have private.<private-name> for every
alert-category.Maybe this is not enough?
>
> - How does the "legacy" URN <urn:alert:service:normal> fit into the new s=
ystem?

[LL] I am not sure I understand what you mean with this. Change the
name "normal" by , e.g. "default"? Or is it  something else ?

[LL] These are also the issues I know about.
>
> Dale
>

From dworley@avaya.com  Mon Jun  6 11:59:25 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 2812111E81C2 for <salud@ietfa.amsl.com>; Mon,  6 Jun 2011 11:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[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 1HhQzKNH06Bt for <salud@ietfa.amsl.com>; Mon,  6 Jun 2011 11:59:24 -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 68B2711E816B for <salud@ietf.org>; Mon,  6 Jun 2011 11:59:24 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACgj7U3GmAcF/2dsb2JhbABTpiZ3rhgCmzyGIQSVXopx
X-IronPort-AV: E=Sophos;i="4.65,327,1304308800"; d="scan'208";a="250020671"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 06 Jun 2011 14:59:22 -0400
X-IronPort-AV: E=Sophos;i="4.65,327,1304308800"; d="scan'208";a="629932765"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 06 Jun 2011 14:59:22 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.192]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Mon, 6 Jun 2011 14:59:21 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Laura Liess <laura.liess.dt@googlemail.com>
Date: Mon, 6 Jun 2011 14:55:07 -0400
Thread-Topic: Next steps for Alert-Info URN draft
Thread-Index: AcwgY87AOGyYVVXVSjOXOsWvDfw9qwEF3HRD
Message-ID: <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>
In-Reply-To: <BANLkTi=iMCxzo-8NX3MEWxkVJdumC_DBag@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: Mon, 06 Jun 2011 18:59:25 -0000

[as chair]

Hey, everybody!!!

So far, we have only 5 open technical issues listed.  Do they really cover =
everything
that is left to be done?

We don't need solution proposals right now, just to make sure we see the wh=
ole
landscape of problems.

Currently known problems:

- Shall we combine all the characteristics into one URN (leading to a very =
large set of possible URNs), or specify each characteristic in a separate U=
RN (and have the UA combine them)?

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

- 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?)

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

Dale
