[salud] Further adjustment to namespace registration template
worley@ariadne.com (Dale R. Worley) Tue, 26 March 2013 20:29 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 DCC6521F8D1F for <salud@ietfa.amsl.com>; Tue, 26 Mar 2013 13:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[AWL=-0.898, BAYES_50=0.001, 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 9Ma4CiMF61Yr for <salud@ietfa.amsl.com>; Tue, 26 Mar 2013 13:29:12 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 4F37F21F8D1E for <salud@ietf.org>; Tue, 26 Mar 2013 13:29:12 -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 r2QKSrV5013342 for <salud@ietf.org>; Tue, 26 Mar 2013 16:28:56 -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 r2QKSru31223261 for <salud@ietf.org>; Tue, 26 Mar 2013 15:28:53 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r2QKSr4X1224519; Tue, 26 Mar 2013 16:28:53 -0400 (EDT)
Date: Tue, 26 Mar 2013 16:28:53 -0400
Message-Id: <201303262028.r2QKSr4X1224519@shell01.TheWorld.com>
From: worley@ariadne.com
Sender: worley@ariadne.com
To: salud@ietf.org
Subject: [salud] Further adjustment to namespace registration template
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: Tue, 26 Mar 2013 20:29:13 -0000
This is an update to the part of the "Declaration of syntactic structure" that describes that comparison is to be case-insensitive but URNs must be transmitted as registered. It extends this rule to restrict private defintions to have a definite case as well, and copies the rule that an entity should use a single <provider> value for all their definitions. I don't think this will be controversial, but previously we hadn't specified that private definitions must have fixed cases. Dale @@ -132,10 +48,22 @@ syntax for Non Reserved LDH-labels [RFC5890]. <domain-label>s MUST comply with the syntax for Non Reserved LDH- labels or for A-labels [RFC5890]. Comparisons MUST follow the - comparison rules for the corresponding type of label. Registered - URNs MUST be transmitted as registered. A new name MUST NOT be - registered if it is equal by the comparison rules above to an - already registered name. + comparison rules for the corresponding type of label (which is + case-insensitive). + + Registered <alert-category>s and <alert-ind-parts>s MUST be + transmitted using the case as registered. <private-name>s and + privately-defined <alert-ind-part>s MUST be transmitted using + the case as defined by the owning entity. A new use of an + <alert-label> must not be registered if it would result in an + <alert-URN> that is equal by the comparison rules above to an + already registered <alert-URN>. A new use of an <alert-label> + must not be privately defined if it would result in an + <alert-URN> that is equal by the comparison rules above to an + existing privately-define <alert-URN> (in which case, the + existing <alert-URN> is necessarily defined by the same entity). + An entity SHOULD use only one <provider> value (including taking + case into account) for all <private-name>s that it defines. The ABNF [RFC5234] for the Alert -Info URNs is shown below: @@ -144,7 +72,7 @@ alert-identifier = alert-category ":" alert-indication alert-category = alert-name alert-indication = alert-ind-part *(":" alert-ind-part) - alert-ind-part = alert-name + alert-ind-part = alert-name alert-name = alert-label / private-name private-name = alert-label "@" provider provider = provider-id ["(" date ")"]
- [salud] Further adjustment to namespace registrat… Dale R. Worley