
From nobody Wed Jun  4 12:31:41 2014
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.)
----------------------------------------------------------------------


From nobody Thu Jun  5 06:32:31 2014
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 3C3421A012D for <salud@ietfa.amsl.com>; Thu,  5 Jun 2014 06:32:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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 ws71ACBf31XH for <salud@ietfa.amsl.com>; Thu,  5 Jun 2014 06:32:28 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ED031A007C for <salud@ietf.org>; Thu,  5 Jun 2014 06:32:27 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id b13so888822wgh.17 for <salud@ietf.org>; Thu, 05 Jun 2014 06:32:20 -0700 (PDT)
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=kxH+5nh+t4xerD014i9wcTJW73x56TJ2eArxW1KEZws=; b=vwW0wwU7jxUKtLK3p8TUJY5yeF5vuu4Y1FQ2Oz/GfGxAa4NZEyNsOnXTWNSikgy2kg 98Gi4bfZvlX5Syo5NI0GB4Rm0KYq6prNDQyinUNwo7zOEywxVfnYy0IUGcga30pdFuto E+decPLtBYcaPowDxFhUobqYyMsHwGaVZy2k9jjp2vKloP26i4+dNf8volSCijCVv0LV /oXGxilmWRi5LniAwGVnu/vlqtVSFgZ+/BWnljP82dYSMeahBqqxgPreTuo6ubm+wnsc IjQXXuz3/tWKKxehsmQO1WGKnCX6jXjkOTVhdJwujp+LdlMY0T3zkbwlh+lX13NccM5T ZbWg==
MIME-Version: 1.0
X-Received: by 10.180.81.102 with SMTP id z6mr15806937wix.54.1401975139942; Thu, 05 Jun 2014 06:32:19 -0700 (PDT)
Received: by 10.180.228.106 with HTTP; Thu, 5 Jun 2014 06:32:19 -0700 (PDT)
In-Reply-To: <201406041931.s54JVUfD014598@hobgoblin.ariadne.com>
References: <201406041931.s54JVUfD014598@hobgoblin.ariadne.com>
Date: Thu, 5 Jun 2014 15:32:19 +0200
Message-ID: <CACWXZj22FDrBW6sGH1gn1iVCCZFpDvXrtsLVP-q1EV2gtEBCvA@mail.gmail.com>
From: Laura Liess <laura.liess.dt@googlemail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=f46d04428fb4334a8904fb16c668
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/W1lwe3XrK03iPxuXS2Zh92ZLzTM
Cc: salud@ietf.org
Subject: Re: [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: Thu, 05 Jun 2014 13:32:30 -0000

--f46d04428fb4334a8904fb16c668
Content-Type: text/plain; charset=ISO-8859-1

2014-06-04 21:31 GMT+02:00 Dale R. Worley <worley@ariadne.com>:

> [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:
>


I think if we don't want extenssions which do not comply to these
princilpes we should use MUST.  Or do we want to allow exceptions?

If we use SHOULD, what happens if someone wants an extenssion which does
not comply. Is the designated expert allowed to reject the extenssion
because it does not comply? Or is a source for never ending discussions?

Thank you
Laura



>
> [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.)
> ----------------------------------------------------------------------
>
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>

--f46d04428fb4334a8904fb16c668
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">2014-06-04 21:31 GMT+02:00 Dale R. Worley <span dir=3D"ltr">&lt;<a =
href=3D"mailto:worley@ariadne.com" target=3D"_blank">worley@ariadne.com</a>=
&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">[as an author]<br>
<br>
This is a second draft of the changes needed to change the policy for<br>
alert-info URNs from &quot;Standards Action&quot; to &quot;Specification Re=
quired&quot;.<br>
I think I&#39;ve found all places in the text that would need to be<br>
modified. =A0I&#39;ve incorporated the changes suggested by Paul and<br>
clarified the language in a few places.<br>
<br>
(Reading the description of &quot;Specification Required&quot; in RFC 5226,=
 it<br>
seems that usually the specification will be an RFC. =A0But the RFC<br>
could be AD-sponsored, or I suppose, independent, which saves quite a<br>
bit of overhead compared to &quot;Standards Action&quot;.)<br>
<br>
An important question is whether I&#39;ve captured all of the guidelines<br=
>
that will be needed by the expert, which are listed in section 10.1.<br>
<br>
There is also a question about the use of MUST vs. SHOULD in several<br>
places.<br></blockquote><br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">
<br>
What do people think?<br>
<br>
Dale<br>
<br>
----------------------------------------------------------------------<br>
=A0 =A09.1. =A0Registry<br>
<br>
=A0 =A0...<br>
=A0 =A0The policy for adding a new standard &lt;alert-category&gt; is &#39;=
Standards<br>
=A0 =A0Action&#39;. =A0The policy for adding &lt;alert-identifiers&gt;s or =
patterns of<br>
=A0 =A0&lt;alert-identifiers&gt;s within a particular &lt;alert-category&gt=
; may differ<br>
=A0 =A0for each &lt;alert-category&gt;and MUST be defined by the document d=
efining<br>
=A0 =A0the corresponding &lt;alert-category&gt;.<br>
<br>
Replace this with:<br>
<br>
The policy for adding a new standard &lt;alert-category&gt;, or, within a<b=
r>
particular &lt;alert-category&gt;, a new standard &lt;alert-identifier&gt; =
or<br>
pattern of &lt;alert-identifier&gt;s is &#39;Specification Required&#39; ac=
cording<br>
to the guidelines in section 10.1.<br>
<br>
=A0 =A09.2. =A0Initial IANA Registration<br>
<br>
=A0 =A0This document defines the &lt;alert-category&gt;s &#39;service&#39;,=
 &#39;source&#39;,<br>
=A0 =A0&#39;priority&#39;, &#39;duration&#39;, &#39;delay&#39; and &#39;loc=
ale&#39;. =A0The policy for adding<br>
=A0 =A0an &lt;alert-identifier&gt; for any of these &lt;alert-category&gt;s=
 is Standards<br>
=A0 =A0Action.<br>
<br>
Delete the last sentence.<br>
<br>
=A0 =A0...<br>
=A0 =A010. =A0Extension Rules<br>
<br>
=A0 =A010.1. =A0General Extension Rules<br>
<br>
=A0 =A0The set of &quot;alert&quot; URNs is extensible. =A0An extension &qu=
ot;at the top<br>
=A0 =A0level&quot; creates an new &lt;alert-category&gt; (which represents =
a new<br>
=A0 =A0alerting characteristic), an extension &quot;at the second level&quo=
t; creates<br>
=A0 =A0a new &lt;alert-indication&gt; value for an existing &lt;alert-categ=
ory&gt; , an<br>
=A0 =A0extension &quot;at the third level&quot; creates a subdivision of an=
 existing<br>
=A0 =A0&lt;alert-indication&gt; (that has one &lt;alert-ind-part&gt; ), etc=
. =A0URNs allow<br>
=A0 =A0(in principle) indefinite subdivision of existing &lt;alert-indicati=
on&gt;<br>
=A0 =A0values, although most of the standard &quot;alert&quot; URNs have on=
ly one<br>
=A0 =A0level of subdivision and a few have two levels of subdivision.<br>
<br>
=A0 =A0Designers of extensions should take care to derive the new URN from<=
br>
=A0 =A0the most specific base URN which has the correct meaning; a new URN<=
br>
=A0 =A0should have no semantic overlap with any sibling URN, i.e., there ca=
n<br>
=A0 =A0be no calls to which both URNs could apply.<br>
<br>
Replace the preceding paragraph with:<br>
<br>
Extensions, either standard or private, MUST (SHOULD?) conform to<br>
the following principles:<br></blockquote><div><br><div><br></div><div>I th=
ink if we don&#39;t want extenssions which do not comply to these princilpe=
s we should use MUST.=A0 Or do we want to allow exceptions?<br><br></div>
If
 we use SHOULD, what happens if someone wants an extenssion which does=20
not comply. Is the designated expert allowed to reject the extenssion=20
because it does not comply? Or is a source for never ending discussions?<br=
>=A0<br></div><div>Thank you<br></div><div>Laura<br></div><div><br>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">

<br>
[The following sentences use &quot;is&quot; and &quot;are&quot; rather than=
 &quot;must&quot;,<br>
&quot;should&quot;, &quot;can&quot;, etc. =A0That allows the strength of th=
ese statements to<br>
be determined only by the RFC 2119 word in the preceding sentence, and<br>
prevents these statements from setting their own strength.]<br>
<br>
A new &lt;alert-category&gt; is independent of all previously-existing<br>
&lt;alert-category&gt;s; there are potentially calls to which all<br>
combinations of &lt;alert-identifier&gt;s in the new &lt;alert-category&gt;=
 with<br>
all &lt;alert-identifier&gt;s in all previously-existing &lt;alert-category=
&gt;s<br>
can be meaningfully applied.<br>
<br>
A new &lt;alert-identifier&gt; that has more than one &lt;alert-ind-part&gt=
; is a<br>
semantic refinement of a parent &lt;alert-identifier&gt;, the parent being<=
br>
obtained by deleting the final &lt;alert-ind-part&gt;. =A0The new<br>
&lt;alert-identifier&gt; has as parent the most specific previously-existin=
g<br>
&lt;alert-identifier&gt; whose meaning includes all potential calls to whic=
h<br>
the new &lt;alert-identifier&gt; could be applied.<br>
<br>
A new &lt;alert-identifier&gt; has no semantic overlap with any sibling<br>
&lt;alert-identifier&gt; (&lt;alert-identifier&gt;s that differ only in the=
 final<br>
&lt;alert-ind-part&gt;). =A0I.e., there could be no call to which both<br>
&lt;alert-identifier&gt;s could meaningfully apply.<br>
<br>
=A0 =A0The process for defining new standard &quot;alert&quot; URNs is desc=
ribed in<br>
=A0 =A0Section 9.1. =A0Currently, all such definitions require Standards<br=
>
=A0 =A0Action. =A0The process for defining new &quot;alert&quot; URNs via t=
he private<br>
=A0 =A0extension mechanism is described in Section 10.2.<br>
<br>
The second sentence becomes: =A0All such definitions require Expert<br>
Review.<br>
<br>
=A0 =A010.2. =A0Private Extension Rules<br>
<br>
=A0 =A0...<br>
=A0 =A0Creating private extension &quot;alert&quot; URNs is not a Standards=
 Action and<br>
=A0 =A0they are not registered with IANA.<br>
<br>
=A0 =A0Once an organization obtains the right to use a particular &lt;provi=
der&gt;<br>
=A0 =A0for constructing &lt;private-name&gt;s, it will retain that right fo=
rever,<br>
=A0 =A0unless it transfers that right to another organization. =A0The<br>
=A0 =A0organization defining a private extension is responsible for ensurin=
g<br>
=A0 =A0persistence of the meaning of the private extension, and for ensurin=
g<br>
=A0 =A0that the private extension does not duplicate any standard URN or an=
y<br>
=A0 =A0private extension that the organization is aware of. =A0(In either<b=
r>
=A0 =A0case, the organization SHOULD use the existing URN for its purposes.=
)<br>
<br>
Replace the preceding paragraph with:<br>
<br>
The organization defining a private extension is responsible for<br>
ensuring persistence of the meaning of the private extension.<br>
<br>
Private extensions MUST (SHOULD?) conform to the principles of<br>
section 10.1, both in regard to previously-existing standard<br>
&lt;alert-URN&gt;s and in regard to any previously-existing private<br>
extensions using the same &lt;provider&gt; value, and any other private<br>
extensions that the organization is aware of. =A0In particular, a<br>
private extension MUST (SHOULD?) not duplicate any standard URN or any<br>
private extension that the organization is aware of. =A0(In either case,<br=
>
the organization MUST (SHOULD?) use the existing URN for its purposes.)<br>
----------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
salud mailing list<br>
<a href=3D"mailto:salud@ietf.org">salud@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/salud" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/salud</a><br>
</blockquote></div><br></div></div>

--f46d04428fb4334a8904fb16c668--


From nobody Thu Jun  5 08:22:46 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 8AEB41A025C for <salud@ietfa.amsl.com>; Thu,  5 Jun 2014 08:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 Nevv_D2D07lJ for <salud@ietfa.amsl.com>; Thu,  5 Jun 2014 08:22:44 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 46BC11A02DE for <salud@ietf.org>; Thu,  5 Jun 2014 08:20:16 -0700 (PDT)
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44]) by qmta01.westchester.pa.mail.comcast.net with comcast id AdXY1o0050xGWP851fLAY5; Thu, 05 Jun 2014 15:20:10 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta12.westchester.pa.mail.comcast.net with comcast id AfL91o00V3ZTu2S3YfL9DV; Thu, 05 Jun 2014 15:20:10 +0000
Message-ID: <53908AA9.1020502@alum.mit.edu>
Date: Thu, 05 Jun 2014 11:20:09 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: salud@ietf.org
References: <201406041931.s54JVUfD014598@hobgoblin.ariadne.com>
In-Reply-To: <201406041931.s54JVUfD014598@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1401981610; bh=42QzRr5BQ5DBFdY2f+DuC5gVxLC8SxBOhYcTBQCGG7k=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=L9j4lAMrn9K1hHnn/tHYfbx/OBuOGIq92KRbgQK1QPfBjb0LOXhdtC/QEx+In6nsG rA8Ean6OAzXz+uNGioX5VtVppsIpUR10oEnuX1s2PoFEyYzpvO+nysr7H9cPrEGz1N ge+vvna5PoZHQ92Nnmjw57On5NB/FxNRABWlE3ooozfGo3kk8hc9soH9WjIXiM+vb7 jiIiLd0B38956FimtR9z9VUp1EpVCfW9Xj5ToTALU3pb4gte4mExGeolg/NdGCn5f8 FwN3/xM7zyaAIe16diq/ttTUe/RRHhtbH0fiMppCw1/VcIAwLqkQ8GEOdPGCkFm+Bs jkFIoWC0gPGTw==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/9GhDMSM_LIjblxXfB25-Uh8rZZo
Subject: Re: [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: Thu, 05 Jun 2014 15:22:45 -0000

On 6/4/14 3:31 PM, Dale R. Worley wrote:
> [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:

MUST!

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

I think I am losing the big picture here of how the standard and private 
definitions relate. I think I need to look at this all together in a new 
version of the draft. Is this new second sentence intended to apply only 
to standard extensions? Why is this paragraph not in a section titled 
"Standard Extension Rules"?

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

Am I right that this is not (yet) dealing with a change to registering 
<provider>s?

	Thanks,
	Paul


From nobody Thu Jun  5 11:19:59 2014
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 167BC1A02B5 for <salud@ietfa.amsl.com>; Thu,  5 Jun 2014 11:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 xG-F4KI4nWxu for <salud@ietfa.amsl.com>; Thu,  5 Jun 2014 11:19:47 -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 7CCFF1A02DC for <salud@ietf.org>; Thu,  5 Jun 2014 11:19:45 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta15.westchester.pa.mail.comcast.net with comcast id AcWE1o0041vXlb85FiKew5; Thu, 05 Jun 2014 18:19:38 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta17.westchester.pa.mail.comcast.net with comcast id AiKe1o00S1KKtkw3diKe9V; Thu, 05 Jun 2014 18:19:38 +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 s55IJbBw019197; Thu, 5 Jun 2014 14:19:37 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s55IJbTN019196; Thu, 5 Jun 2014 14:19:37 -0400
Date: Thu, 5 Jun 2014 14:19:37 -0400
Message-Id: <201406051819.s55IJbTN019196@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: salud@ietf.org
In-reply-to: <CACWXZj22FDrBW6sGH1gn1iVCCZFpDvXrtsLVP-q1EV2gtEBCvA@mail.gmail.com> (laura.liess.dt@googlemail.com)
References: <201406041931.s54JVUfD014598@hobgoblin.ariadne.com> <CACWXZj22FDrBW6sGH1gn1iVCCZFpDvXrtsLVP-q1EV2gtEBCvA@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1401992378; bh=ZIDd39Dhhe1dTmbUppbpPbr1PkSiL18Z0meUyQLRr1M=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=huCbUtHdX6XnrXxW1M6UWXCV8FUA7fRVD6ziGPBZWPYii5L9I3Hc+FE5yeP7/sRl2 TcrBvZhD+bdzD052e/pmOqWOYM45Pl4vXV/t1J4M9SJCsdNswDQoVnBk2pybKP8CFb 8DG39gIN2AvoG70ff37m9QHUVyPvWx9scZbzebNn0ZwIIOhIZYaJ00KEP905Rtn31Y sE/h3CtFFEPk+c4Zc7Dm9I1cypl1KNrgrUG6JRRINHmgtB2QbZaJRmde0dMa5dt2BH Z/TFSh5RJ2q2mAWKQFVC4ilz3WRJqFoxql/UP+h0Xpd0aYD7kd3xJuaeZQhvSIqz2X a6LUcsFRlEXew==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/-jPrwuj-VdoHIC_wQgYbmkoPpgQ
Subject: Re: [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: Thu, 05 Jun 2014 18:19:56 -0000

> From: Laura Liess <laura.liess.dt@googlemail.com>
>
> > Extensions, either standard or private, MUST (SHOULD?) conform to
> > the following principles:
> 
> I think if we don't want extenssions which do not comply to these
> princilpes we should use MUST.  Or do we want to allow exceptions?
> 
> If we use SHOULD, what happens if someone wants an extenssion which does
> not comply. Is the designated expert allowed to reject the extenssion
> because it does not comply? Or is a source for never ending discussions?

> From: Paul Kyzivat <pkyzivat@alum.mit.edu>

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

Based on both your comments, I agree that we want MUST.  Otherwise,
people will try to get approval for poorly-designed extensions.

> From: Paul Kyzivat <pkyzivat@alum.mit.edu>
>
> >     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.
> 
> I think I am losing the big picture here of how the standard and private 
> definitions relate. I think I need to look at this all together in a new 
> version of the draft. Is this new second sentence intended to apply only 
> to standard extensions? Why is this paragraph not in a section titled 
> "Standard Extension Rules"?

Yes, the wording is unclear.

The -12 version has:

    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.

       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.

I'm proposing that we make the rules more explicit, to provide
guidance to the Designated Expert.  That changes section 10.1 to:

     10.  Extension Rules

     10.1.  General Extension Rules

The first paragraph is unchanged, or mostly unchanged.  Its goal is to
give the reader the overall concept of the extension mechanism.

     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.

What was the second paragraph of 10.1 becomes the following 4
paragraphs.  (I've improved the second of these paragraphs since my
previous message.  I think it is now clear enough.)

     Extensions, either standard or private, MUST conform to the
     following principles:

     A new <alert-category> is independent of all previously-existing
     <alert-category>s:  For any combination of one <alert-identifier>
     in the new <alert-category> with one <alert-identifier> in any of
     the previously-existing <alert-category>s, there are potential
     calls to which the combination 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 old third paragraph becomes as follows.  (I've connected the first
and second sentences with a semicolon.  I believe that makes it
clearer that the things that require Expert Review are new standard
URNs.)

     The process for defining new standard "alert" URNs is described
     in Section 9.1; all such definitions require Expert Review.  The
     process for defining new "alert" URNs via the private extension
     mechanism is described in Section 10.2.

Perhaps "process" should be changed to "procedure".

The previous paragraph gives pointers to the sections that describe
the procedures for establishing a new URNs.  Section 9.1 describes the
registry for alert URNs.  Section 10.2 gives "Private Extension
Rules".

> > 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.)
> > ----------------------------------------------------------------------
> 
> Am I right that this is not (yet) dealing with a change to registering 
> <provider>s?

That is correct in principle.  But I do not believe that changing the
definition of <provider> will change any of the text we are
discussing; we can discuss the two topics independently.

Dale


From nobody Thu Jun 12 15:23:05 2014
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 B53FB1A02A2 for <salud@ietfa.amsl.com>; Thu, 12 Jun 2014 15:23:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ESfEtWedy600 for <salud@ietfa.amsl.com>; Thu, 12 Jun 2014 15:23:01 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id DC8281A0271 for <salud@ietf.org>; Thu, 12 Jun 2014 15:23:00 -0700 (PDT)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta04.westchester.pa.mail.comcast.net with comcast id Da2i1o0021ap0As54aP03i; Thu, 12 Jun 2014 22:23:00 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta22.westchester.pa.mail.comcast.net with comcast id DaNz1o00v1KKtkw3iaP0l4; Thu, 12 Jun 2014 22:23:00 +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 s5CMMx30020000; Thu, 12 Jun 2014 18:22:59 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s5CMMx9k019999; Thu, 12 Jun 2014 18:22:59 -0400
Date: Thu, 12 Jun 2014 18:22:59 -0400
Message-Id: <201406122222.s5CMMx9k019999@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: 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=1402611780; bh=zwznsf5eHobZOTkO919QTwlCIKMvmJlkVo4RPxl3hy4=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=b8NK23NNWU5ZTqWISfwI7FLlCktfmHb54+2gv60nlU+eAbzAPb4tZOs64tliguzkJ VunfIjvpnOVNDT3wZAflSY/7VLCWAyRM3Pgn7XSIE6a7rR2fJbwifn5rFwbGSj5E7+ X6paItkBjcrR0bmtnKIco0jXqr3AAf+KYEDzLqFQpLhud3Wgad5/YWQvFqQC/dxO85 Jo8cZvGjykXWBiooS3ua2ngL+CZVFx9hftn2EsCRTtt9reiprc10N453L8sIAmZyDu Oj0UVeEU6VtGAX3Ao+hRMLtPGF229YgkmBtVyNtqNwt+bUMw23K9Xu7SwANPJLaR4/ LCheOTiF5kKcg==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/eNzZnsKZ7bGXURVnvzrjlx5G-KQ
Subject: [salud] Changing the syntax of private extensions
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, 12 Jun 2014 22:23:02 -0000

[as an author]

draft-ietf-salud-alert-info-urns-12 constructs private extensions
using domain names.  For instance, in

      urn:alert:distinctive@a.example.com:long-long

"distinctive@a.example.com" is a <private-name> that is defined by the
owner of "a.example.com".  The full syntax of <private-name>s can
include a date:

    classification@army.mil(2013-03)

The IESG has criticized this scheme as being too complicated and as
involving the IETF in defining in detail the management of the right
to use particular domain name/date combinations in <private-name>s.
The IESG has proposed replacing this scheme with simple names that
would be registered by users in a first-come, first-served registry
managed by IANA.

The primary authors of the draft have been discussing this change.
Our current consensus on changing the draft is:

- Use a registry with a "First Come First Served" policy for
  <provider> values.  Per RFC 5226:

      First Come First Served - Assignments are made to anyone on a
            first come, first served basis.  There is no substantive
            review of the request, other than to ensure that it is
            well-formed and doesn't duplicate an existing assignment.
            However, requests must include a minimal amount of clerical
            information, such as a point of contact (including an email
            address) and a brief description of how the value will be
            used.  Additional information specific to the type of value
            requested may also need to be provided, as defined by the
            namespace.  For numbers, the exact value is generally
            assigned by IANA; with names, specific text strings can
            usually be requested.

            Examples: SASL mechanism names [RFC4422], LDAP Protocol
            Mechanisms, and LDAP Syntax [RFC4520].

- Use the syntax "provider = alert-label".  In particular, <provider>
  does not contain dots and thus can't be a complete domain name.
  This prevents registrants from choosing <provider>s that match
  domain names, disentangling <provider> from domain names.  The
  syntax becomes (with the changes marked):

         private-name      = alert-label "@" provider
    >>>  provider          = alert-label
         alert-label       = let-dig [ *let-dig-hyp let-dig ]
    >>>  [ Production <domain-label> is deleted. ]
         let-dig-hyp       = let-dig / "-"
         let-dig           = ALPHA / DIGIT

      [...]

      <alert-label>s MUST comply with the syntax for Non Reserved LDH-
      labels [RFC5890].  [deletion]
      Registered URNs and components thereof MUST be transmitted as
      registered (including case).

  That is, <providers> have the syntax of ordinary ASCII DNS labels.
  We expect that in practice organizations will select <provider>
  values that resemble the first component of their domain names.

- The right to define <private-name>s using a particular registered
  <provider> remains an intellectual property right, but because it is
  similar to many other such rights defined in RFCs, we do not need to
  document that.

- Trademark infringement questions can be left to the same legal
  mechanisms organizations now use to resolve trademark infringement
  questions regarding domain names and other identifiers, so we do not
  need to document that either.

Before we go to the work of writing the detailed textual changes, we
want to present this proposal to the working group to solicit your
comments.

Dale


From nobody Wed Jun 25 18:08:45 2014
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 018A81B2E9B for <salud@ietfa.amsl.com>; Wed, 25 Jun 2014 18:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 H7AxI2wbnOIz for <salud@ietfa.amsl.com>; Wed, 25 Jun 2014 18:07:41 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 50BC41B2E97 for <salud@ietf.org>; Wed, 25 Jun 2014 18:07:36 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by QMTA11.westchester.pa.mail.comcast.net with comcast id Jokj1o0021uE5Es5Bp7bFN; Thu, 26 Jun 2014 01:07:35 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta16.westchester.pa.mail.comcast.net with comcast id Jp7b1o00G1KKtkw3cp7bF5; Thu, 26 Jun 2014 01:07:35 +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 s5Q17Yw6028883; Wed, 25 Jun 2014 21:07:34 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s5Q17YB0028882; Wed, 25 Jun 2014 21:07:34 -0400
Date: Wed, 25 Jun 2014 21:07:34 -0400
Message-Id: <201406260107.s5Q17YB0028882@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: 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=1403744855; bh=G3hheN75vuX697UUmY0GAk4fCba7PIkNZAvtBlhKP20=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=UPirMZ/NUllS1uYcH4KQIa9Zkn0ld/orJVXgISHuoWNAGefUa/nuNIL02cUayQJh9 vPTUvhPvXhujuLbARYxSVUi694jl7BHX7dr2+K4m4P8JjFWKy/RJV0jFaI70quZ4F6 YelK4XSIg4j0Y7E7AGZ7+Fytb/NEPULAS2X8ehWHvAkfyXAsd9/LE4zNkMmZwGLE5J vY7dZxtLc1sHIeHYqTTtaQDBYXccI3XGGalawosRyAbD5cmsI/rOOq0Fs+qUu/8sMX 0Rfw1BGHXNQ7NA7pNyzLnJJuGuy7l4z0Cdhuxapluj3WYHxG16fGw0BM9Bg+1Qo7dk ixCSLCejQ7zKw==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/-8DrdAzXCLYpoU77s7RTWH8l2IE
Subject: [salud] Draft revision 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: Thu, 26 Jun 2014 01:07:57 -0000
X-List-Received-Date: Thu, 26 Jun 2014 01:07:57 -0000

[as an author]

I've assembled an XML2RFC draft incorporating the changes for
"specification required".  The substantive changes are the same as in
'Third draft of changes for "specification required"', but I've also
revised the description of the registration table, now that we've
fixed the information that needs to be recorded:

   There is one table, whose rows are used to register
   alert-categories, alert-identifiers, and patterns of alert
   identifiers.  The table does not include policy values, as the
   policy is uniformly "specification required".

I've added a proper reference to RFC 2434, which defines the
"specification required" policy.

The XML and text versions can be obtained from

https://svn.resiprocate.org/rep/ietf-drafts/worley/draft-worley-salud-alert-info-urns-12-update3.txt

https://svn.resiprocate.org/rep/ietf-drafts/worley/draft-worley-salud-alert-info-urns-12-update3.xml

You can see the diffs between revision 12 and this draft with

https://www.ietf.org/rfcdiff?url1=draft-ietf-salud-alert-info-urns-12&difftype=--html&submit=Go!&url2=http%3A%2F%2Fsvn.resiprocate.org%2Frep%2Fietf-drafts%2Fworley%2Fdraft-worley-salud-alert-info-urns-12-update3.txt

Dale


From nobody Wed Jun 25 18:24:24 2014
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 9CA441B2EB2 for <salud@ietfa.amsl.com>; Wed, 25 Jun 2014 18:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 r-Hzi1oZX5tj for <salud@ietfa.amsl.com>; Wed, 25 Jun 2014 18:24:21 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 48A061B2EAE for <salud@ietf.org>; Wed, 25 Jun 2014 18:24:21 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta05.westchester.pa.mail.comcast.net with comcast id Jokj1o0021uE5Es55pQLHT; Thu, 26 Jun 2014 01:24:20 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta16.westchester.pa.mail.comcast.net with comcast id JpQL1o00M1KKtkw3cpQL5c; Thu, 26 Jun 2014 01:24:20 +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 s5Q1OKsV030713; Wed, 25 Jun 2014 21:24:20 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s5Q1OKVZ030712; Wed, 25 Jun 2014 21:24:20 -0400
Date: Wed, 25 Jun 2014 21:24:20 -0400
Message-Id: <201406260124.s5Q1OKVZ030712@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: 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=1403745860; bh=wNpyuEbKXOxIvRbDFyhGk3j9MP8rEocf1qGh9qMv1SU=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=XZOPEi8udkx1JoEa+5IqjqSfy855t6dBGhFFvjSul4yTeTPrylvyAraosB0s12jAH qGPV1hm21KD0uM9ryfnzM+MuYD/nAw7Lft5xNKTZa7npn8Ci1vD3CjespzaPm+U1eB Tc5ZlRhoUqbYx74auJewMJHMsHprvP5J85c3Gm2OFsx4EBm5rfk5zX+kyXGMymGvl+ 5EMQTvKOjWhgYM+dZuW+DUkNtxjr4oilu44ME8cKlIglVO2L3ZPu7au8G0kW+XhTRW 2adammnrzPagDW93LuRHQo1DD3uABgKGog9PMULcLKF7w7s6I3bKsmrEJNKdCj2S24 mKplvzpw3ohZQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/salud/OtEQrnMJs-3YqAhYT7zvHxSGS2g
Subject: [salud] Combined draft revision
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, 26 Jun 2014 01:24:22 -0000

[as an author]

I've assembled an XML2RFC draft that incorporates both the "general
revisions" (update1) and the changes for "specification required"
update3, along with one or two editorial changes.

The XML and text versions can be obtained from

https://svn.resiprocate.org/rep/ietf-drafts/worley/draft-worley-salud-alert-info-urns-12-update1and3.txt

https://svn.resiprocate.org/rep/ietf-drafts/worley/draft-worley-salud-alert-info-urns-12-update1and3.xml

You can see the diffs between revision 12 and this draft with

https://www.ietf.org/rfcdiff?url1=draft-ietf-salud-alert-info-urns-12&difftype=--html&submit=Go!&url2=http%3A%2F%2Fsvn.resiprocate.org%2Frep%2Fietf-drafts%2Fworley%2Fdraft-worley-salud-alert-info-urns-12-update1and3.txt

(This does not include any changes to <provider> values.)

Dale

