[salud] Second draft of changes for "specification required"

worley@ariadne.com (Dale R. Worley) Wed, 04 June 2014 19:31 UTC

Return-Path: <worley@ariadne.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 1631E1A0359 for <salud@ietfa.amsl.com>; Wed, 4 Jun 2014 12:31:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 bKoHXb-aTmGG for <salud@ietfa.amsl.com>; Wed, 4 Jun 2014 12:31:38 -0700 (PDT)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id D64F81A033B for <salud@ietf.org>; Wed, 4 Jun 2014 12:31:37 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta15.westchester.pa.mail.comcast.net with comcast id AAQm1o00527AodY5FKXXt3; Wed, 04 Jun 2014 19:31:31 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta19.westchester.pa.mail.comcast.net with comcast id AKXX1o00B1KKtkw3fKXX71; Wed, 04 Jun 2014 19:31:31 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s54JVURp014599 for <salud@ietf.org>; Wed, 4 Jun 2014 15:31:30 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s54JVUfD014598; Wed, 4 Jun 2014 15:31:30 -0400
Date: Wed, 4 Jun 2014 15:31:30 -0400
Message-Id: <201406041931.s54JVUfD014598@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
To: salud@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1401910291; bh=s/wf7bMo4k46Jdx5j0mDlqsH9sQepLg4VX1dp8Kuzm8=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=c/boawMt08d2NtP2E2258GOKPorx6UR2InbedoVfog+wHMDBzIP6/Oss1JVxZproZ X1buegqBbvn+9GJ6tndOBFPGA5rHr8sJo59pjeIoyc0m2DHUTELDe5Z8tU6LTDFAlb hFw1+YZFdgMeUa+2Q2iopaQS/IzDZ861uvJPnGVuQSBe4w4FIRutRg1h9Zx8nV45he kA+t9mWgcWQV3fj4RzyD0lcpw7BLIzgnyLKgKS3dpLZ9zBqIVDiSTsTkhnNEgi76a9 P5I9u/qv2VbA1lPZNlznCoM6pdXftF+AdulM/kn869JfVZleH3C5YGRl4cIXjAXyuZ EnxNdGld0BlXQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/TZ-LvBb7ouMnhdwZdDfY19l8rAo
Subject: [salud] Second draft of changes for "specification required"
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: Wed, 04 Jun 2014 19:31:40 -0000

[as an author]

This is a second draft of the changes needed to change the policy for
alert-info URNs from "Standards Action" to "Specification Required".
I think I've found all places in the text that would need to be
modified.  I've incorporated the changes suggested by Paul and
clarified the language in a few places.

(Reading the description of "Specification Required" in RFC 5226, it
seems that usually the specification will be an RFC.  But the RFC
could be AD-sponsored, or I suppose, independent, which saves quite a
bit of overhead compared to "Standards Action".)

An important question is whether I've captured all of the guidelines
that will be needed by the expert, which are listed in section 10.1.

There is also a question about the use of MUST vs. SHOULD in several
places.

What do people think?

Dale

----------------------------------------------------------------------
   9.1.  Registry

   ...
   The policy for adding a new standard <alert-category> is 'Standards
   Action'.  The policy for adding <alert-identifiers>s or patterns of
   <alert-identifiers>s within a particular <alert-category> may differ
   for each <alert-category>and MUST be defined by the document defining
   the corresponding <alert-category>.

Replace this with:

The policy for adding a new standard <alert-category>, or, within a
particular <alert-category>, a new standard <alert-identifier> or
pattern of <alert-identifier>s is 'Specification Required' according
to the guidelines in section 10.1.

   9.2.  Initial IANA Registration

   This document defines the <alert-category>s 'service', 'source',
   'priority', 'duration', 'delay' and 'locale'.  The policy for adding
   an <alert-identifier> for any of these <alert-category>s is Standards
   Action.

Delete the last sentence.

   ...
   10.  Extension Rules

   10.1.  General Extension Rules

   The set of "alert" URNs is extensible.  An extension "at the top
   level" creates an new <alert-category> (which represents a new
   alerting characteristic), an extension "at the second level" creates
   a new <alert-indication> value for an existing <alert-category> , an
   extension "at the third level" creates a subdivision of an existing
   <alert-indication> (that has one <alert-ind-part> ), etc.  URNs allow
   (in principle) indefinite subdivision of existing <alert-indication>
   values, although most of the standard "alert" URNs have only one
   level of subdivision and a few have two levels of subdivision.

   Designers of extensions should take care to derive the new URN from
   the most specific base URN which has the correct meaning; a new URN
   should have no semantic overlap with any sibling URN, i.e., there can
   be no calls to which both URNs could apply.

Replace the preceding paragraph with:

Extensions, either standard or private, MUST (SHOULD?) conform to
the following principles:

[The following sentences use "is" and "are" rather than "must",
"should", "can", etc.  That allows the strength of these statements to
be determined only by the RFC 2119 word in the preceding sentence, and
prevents these statements from setting their own strength.]

A new <alert-category> is independent of all previously-existing
<alert-category>s; there are potentially calls to which all
combinations of <alert-identifier>s in the new <alert-category> with
all <alert-identifier>s in all previously-existing <alert-category>s
can be meaningfully applied.

A new <alert-identifier> that has more than one <alert-ind-part> is a
semantic refinement of a parent <alert-identifier>, the parent being
obtained by deleting the final <alert-ind-part>.  The new
<alert-identifier> has as parent the most specific previously-existing
<alert-identifier> whose meaning includes all potential calls to which
the new <alert-identifier> could be applied.

A new <alert-identifier> has no semantic overlap with any sibling
<alert-identifier> (<alert-identifier>s that differ only in the final
<alert-ind-part>).  I.e., there could be no call to which both
<alert-identifier>s could meaningfully apply.

   The process for defining new standard "alert" URNs is described in
   Section 9.1.  Currently, all such definitions require Standards
   Action.  The process for defining new "alert" URNs via the private
   extension mechanism is described in Section 10.2.

The second sentence becomes:  All such definitions require Expert
Review.

   10.2.  Private Extension Rules

   ...
   Creating private extension "alert" URNs is not a Standards Action and
   they are not registered with IANA.

   Once an organization obtains the right to use a particular <provider>
   for constructing <private-name>s, it will retain that right forever,
   unless it transfers that right to another organization.  The
   organization defining a private extension is responsible for ensuring
   persistence of the meaning of the private extension, and for ensuring
   that the private extension does not duplicate any standard URN or any
   private extension that the organization is aware of.  (In either
   case, the organization SHOULD use the existing URN for its purposes.)

Replace the preceding paragraph with:

The organization defining a private extension is responsible for
ensuring persistence of the meaning of the private extension.

Private extensions MUST (SHOULD?) conform to the principles of
section 10.1, both in regard to previously-existing standard
<alert-URN>s and in regard to any previously-existing private
extensions using the same <provider> value, and any other private
extensions that the organization is aware of.  In particular, a
private extension MUST (SHOULD?) not duplicate any standard URN or any
private extension that the organization is aware of.  (In either case,
the organization MUST (SHOULD?) use the existing URN for its purposes.)
----------------------------------------------------------------------