[salud] A better example -- comments sought

worley@ariadne.com (Dale R. Worley) Wed, 19 June 2013 17:44 UTC

Return-Path: <worley@shell01.TheWorld.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 CBE1421F9D82 for <salud@ietfa.amsl.com>; Wed, 19 Jun 2013 10:44:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level:
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
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 pMSpX-fXGhv5 for <salud@ietfa.amsl.com>; Wed, 19 Jun 2013 10:44:14 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 204E721F9D5D for <salud@ietf.org>; Wed, 19 Jun 2013 10:44:02 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r5JHgVMu015353 for <salud@ietf.org>; Wed, 19 Jun 2013 13:42:33 -0400
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r5JHgVFx6956527 for <salud@ietf.org>; Wed, 19 Jun 2013 13:42:31 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r5JHgVIW6937700; Wed, 19 Jun 2013 13:42:31 -0400 (EDT)
Date: Wed, 19 Jun 2013 13:42:31 -0400
Message-Id: <201306191742.r5JHgVIW6937700@shell01.TheWorld.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: salud@ietf.org
Subject: [salud] A better example -- comments sought
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, 19 Jun 2013 17:44:20 -0000

The authors are discussing adding a section showing examples of use of
the extension features.  In that section is an example "Subsetting a
private extension URN".  That example is not very realistic (I can say
that because I wrote it myself), so I propose this replacement example:

    The company designated by "alfa.example.com(2013)" wants to define a
    set of URNs that specify the different ring patterns used by a
    "distinctive ring" service to alert for incoming calls that are
    directed to different directory numbers.  These ring patterns are
    composed of groups of ring sounds that have particular patterns of
    lengths.

    The company can create a private <alert-category>,
    "distinctive@alfa.example.com", and within it assign three 'alert'
    URNs that indicate the three different ring patterns used by the
    company's service:

	urn:alert:distinctive@alfa.example.com:long-long
	urn:alert:distinctive@alfa.example.com:short-long-short
	urn:alert:distinctive@alfa.example.com:short-short-long

    Later, the company designated by "bravo.example.com(2013)" wants to
    define an additional 'alert' URN for the ring pattern "short short",
    which it uses to support a fourth directory number for a phone
    instrument.  The company can create a <private-name> to be used with
    the "distinctive@alfa.example.com" <alert-category>:

	urn:alert:distinctive@alfa.example.com:short-short@bravo.example.com

Comments?

Dale