Re: [salud] WGLC of draft-ietf-salud-alert-info-urns-09

Laura Liess <laura.liess.dt@googlemail.com> Thu, 16 January 2014 14:59 UTC

Return-Path: <laura.liess.dt@googlemail.com>
X-Original-To: salud@ietfa.amsl.com
Delivered-To: salud@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24E851AE259 for <salud@ietfa.amsl.com>; Thu, 16 Jan 2014 06:59:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.122
X-Spam-Level: *
X-Spam-Status: No, score=1.122 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_84=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sk8ABKFLi_Ut for <salud@ietfa.amsl.com>; Thu, 16 Jan 2014 06:59:04 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5EAC51AE0D7 for <salud@ietf.org>; Thu, 16 Jan 2014 06:59:04 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id w7so1523874lbi.27 for <salud@ietf.org>; Thu, 16 Jan 2014 06:58:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LezWqYLExdfwonmP7vyOrFU50ddaLUJP5GamM1yPwpc=; b=FYVsE4tx6gGkU4Dk3y2kLjeJzO2DMZ6e7chZ7B2OT0ZbpuE6gXA3mNXEdyIcVQV5aF 7BRBO+vRreYp7kebzDB/M3WICYBF5CnN0H/DuSqR2ap2CiYPUA66zLNefdwpA/7w6VL/ tgpj9LU1gYDllu5+0MxCa4u7G3YpET+OmZLCWNNxn8ZML0nZM16/ZfVKdpclKRMxdTc4 VNPlM0ufXXteMIkQdM8wyrkEDI5NBUFb6S7BGbwc5aoD2rQb992IkyedKTbC3KYe3R23 AbPsA8SvqjpE0hJWfDplktIe/FNoS2MLkfj6dOyA3nVhIe1Qpkavwdd8GQihsP6a7sQa 2xpg==
MIME-Version: 1.0
X-Received: by 10.152.28.230 with SMTP id e6mr5365177lah.3.1389884330568; Thu, 16 Jan 2014 06:58:50 -0800 (PST)
Received: by 10.114.169.129 with HTTP; Thu, 16 Jan 2014 06:58:50 -0800 (PST)
In-Reply-To: <201401072032.s07KWYwn2340453@shell01.TheWorld.com>
References: <201311201944.rAKJiS7d5355422@shell01.TheWorld.com> <528D41F2.8090200@alum.mit.edu> <201401072032.s07KWYwn2340453@shell01.TheWorld.com>
Date: Thu, 16 Jan 2014 15:58:50 +0100
Message-ID: <CACWXZj2=9oEPFwKYt=gRC+SbncMTBBBA_9E=fcK9e1o2Ver68w@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=089e0160b79acd70ba04f017a943
Cc: "salud@ietf.org" <salud@ietf.org>
Subject: Re: [salud] WGLC of draft-ietf-salud-alert-info-urns-09
X-BeenThere: salud@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Jan 2014 14:59:07 -0000

Dale,

I changed the draft as you propose.

Thank you
Laura

2014/1/7 Dale R. Worley <worley@ariadne.com>

> Here is my revision of section 9.2 (the examples) based on Paul's
> suggestions.  It can be compared directly with the text in -09.
>
>
> 9.2.  Examples of how the algorithm works
>
>    The following examples show how the algorithm described in the
>    previous section works:
>
> 9.2.1.  Example 1
>
>    The device has a set of four alerting signals.  We list their primary
>    meanings, and the locations that they are placed in the feature
>    trees:
>
>    Signal 1
>
>       Meaning: external
>       Locations:
>       - source:external
>       - priority (that is, the root node of the priority tree)
>
>    Signal 2
>
>       Meaning: internal
>       Locations:
>       - source:internal
>       - priority
>
>    Signal 3
>
>       Meaning: low
>       Locations:
>       - source
>       - priority:low
>
>    Signal 4
>
>       Meaning: high
>       Locations:
>       - source
>       - priority:high
>
>    To which we add:
>
>    Signal 5
>
>       Meaning: default
>       Locations:
>       - source
>       - priority
>
>    If the device receives <urn:alert:source:internal>, then the sort is:
>
>    Signals at source:internal: (this is, first place)
>
>       Signal 2:  internal
>
>    Signals at source: (tied for second place)
>
>       Signal 3:  low
>       Signal 4:  high
>       Signal 5:  default
>
>    And these signals are excluded from the set:
>
>       Signal 1:  external
>
>    So in this example, the sorting algorithm properly gives first place
>    to Signal 2 "internal".
>
> 9.2.2.  Example 2
>
>    Let us add to the set of signals in Example 1 ones that express
>    combinations like "internal, high priority", but let us specifically
>    exclude the combination "internal, low priority" so as to set up some
>    tricky examples.  This enlarges our set of signals:
>
>    Signal 1
>
>       Meaning: default
>       Locations:
>       - source
>       - priority
>
>    Signal 2
>
>       Meaning: external
>       Locations:
>       - source:external
>       - priority
>
>    Signal 3
>
>       Meaning: internal
>       Locations:
>       - source:internal
>       - priority
>
>    Signal 4
>
>       Meaning: low
>       Locations:
>       - source
>       - priority:low
>
>    Signal 5
>
>       Meaning: high
>       Locations:
>       - source
>       - priority:high
>
>    Signal 6
>
>       Meaning: external high
>       Locations:
>
>       - source:external
>       - priority:high
>
>    Signal 7
>
>       Meaning: external low
>       Locations:
>       - source:external
>       - priority:low
>
>    Signal 8
>
>       Meaning: internal high
>       Locations:
>       - source:internal
>       - priority:high
>
>    If the device receives <urn:alert:source:internal>, then the sort is:
>
>    Signals at source:internal: (that is, tied for first place)
>
>       Signal 3:  internal
>       Signal 8:  internal high
>
>    Signals at source: (tied for second place)
>
>       Signal 4:  low
>       Signal 5:  high
>       Signal 1:  default
>
>    Signals excluded from the set:
>
>       Signal 2:  external
>       Signal 7:  external low
>       Signal 6:  external high
>
>    Two signals are tied for the first place, but the final sort orders
>    them:
>
>       Signal 3:  internal
>       Signal 8:  internal high
>
>    because it puts the least-specific signal first.  So Signal 3
>    "internal" is chosen.
>
> 9.2.3.  Example 3
>
>    The same device receives <urn:alert:source:external>,
>    <urn:alert:priority:low>.  The first sort (due to
>    <urn:alert:source:external>) is:
>
>    Signals at source:external:
>
>       Signal 2:  external
>       Signal 7:  external low
>       Signal 6:  external high
>
>    Signals at source:
>
>       Signal 4:  low
>       Signal 5:  high
>       Signal 1:  default
>
>    Signals excluded:
>
>       Signal 3:  internal
>       Signal 8:  internal high
>
>    The second sort (due to <urn:alert:priority:low>) puts signals at
>    priority:low before signals at priority, and excludes signal at
>    priority:high:
>
>       Signal 7:  external low
>       Signal 2:  external
>       Signal 4:  low
>       Signal 1:  default
>
>    Excluded:
>
>       Signal 6:  external high
>       Signal 5:  high
>       Signal 3:  internal
>       Signal 8:  internal high
>
>    So, Signal 7 "external low" is chosen.
>
> 9.2.4.  Example 4
>
>    Suppose the same device receives <urn:alert:source:internal>,
>    <urn:alert:priority:low>.  Note that there is no signal that
>    corresponds to this combination.
>
>    The first sort is based on source:internal, and results in this
>    order:
>
>       Signal 3:  internal
>       Signal 8:  internal high
>       Signal 4:  low
>       Signal 5:  high
>       Signal 1:  default
>
>    Excluded:
>
>       Signal 2:  external
>       Signal 7:  external low
>       Signal 6:  external high
>
>    The second sort is based on priority:low, and results in this order:
>
>       Signal 3:  internal
>       Signal 4:  low
>       Signal 1:  default
>
>    Excluded:
>
>       Signal 8:  internal high
>       Signal 5:  high
>       Signal 7:  external low
>       Signal 2:  external
>       Signal 6:  external high
>
>    So Signal 3 "internal" is chosen.
>
> 9.2.5.  Example 5
>
>    Let us set up a simple set of signals, with three signals giving
>    priority:
>
>    Signal 1
>
>       Meaning: default
>       Locations:
>       - priority
>
>    Signal 2
>
>       Meaning: low
>       Locations:
>       - priority:low
>
>    Signal 3
>
>       Meaning: high
>       Locations:
>       - priority:high
>
>    Notice that we've used the "default" signal to cover "normal
>    priority".  That is so the signal will cover situations where no
>    priority URN is present, as well as the ones with
>    <urn:alert:priority:normal>.  So we're deliberately failing to
>    distinguish "priority:normal" from the default priority.
>
>    If the device receives <urn:alert:priority:low>, the sort is:
>
>       Signal 2:  low
>       Signal 1:  default
>
>    Excluded:
>
>       Signal 3:  high
>
>    and Signal 2 "low" is chosen.
>
>    Similarly, if the device receives <urn:alert:priority:high>, Signal 3
>    "high" is chosen.
>
>    If the device receives <urn:alert:priority:normal>, the sort is:
>
>       Signal 1:  default
>
>    Excluded:
>
>       Signal 2:  low
>       Signal 3:  high
>
>    and Signal 1 "default" is chosen.
>
>    If no "priority" URN is received, Signal 1 "default" will be put
>    before Signal 2 "low" and Signal 3 "high" by the final sort, and so
>    it will be chosen.
>
>
> Dale
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>