Re: [salud] Review of draft-ietf-salud-alert-info-urns-09 (Dale R. Worley) Wed, 13 November 2013 21:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 03A7121E8136 for <>; Wed, 13 Nov 2013 13:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.157
X-Spam-Status: No, score=-3.157 tagged_above=-999 required=5 tests=[AWL=0.442, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id NQMC5e-H56wJ for <>; Wed, 13 Nov 2013 13:25:33 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id BEFAF21E811A for <>; Wed, 13 Nov 2013 13:25:32 -0800 (PST)
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id rADLPEC6018752 for <>; Wed, 13 Nov 2013 16:25:16 -0500
Received: from ( []) by (8.13.6/8.12.8) with ESMTP id rADLMesH4896516 for <>; Wed, 13 Nov 2013 16:22:41 -0500 (EST)
Received: (from worley@localhost) by (8.13.6/8.13.6/Submit) id rADLMedI4896972; Wed, 13 Nov 2013 16:22:40 -0500 (EST)
Date: Wed, 13 Nov 2013 16:22:40 -0500 (EST)
Message-Id: <>
From: (Dale R. Worley)
Sender: (Dale R. Worley)
In-reply-to: <> (
References: <>
Subject: Re: [salud] Review of draft-ietf-salud-alert-info-urns-09
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Sip ALerting for User Devices working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 13 Nov 2013 21:25:39 -0000

(as an individual)

To make sure people don't overlook it, I want to extract from my LC
comments that there are a couple of places in the URN namespace
registration where I think it would be better to use "MUST" rather
than "must", because we want to make sure that implementers meet those

    - 4.  URN Specification for the "alert"  namespace identifier

       Process for identifier resolution:  The process of identifier
	  resolution is the process by which a rendering device chooses a
	  rendering to represent a sequence of "alert" URNs.  The device is
	  allowed great leeway in making this choice, but the process must
	  obey the rules of Section 8.1.  The device is expected to

    I think this requirement is sufficiently important we should impress
    implementors that it is a requirement.

	  Future standardization may allow <alert-label>s
	  that are A-labels, and so interpreters of "alert" URNs must
	  operate correctly when given such URNs as input.

    Similarly, I think we want to use "MUST" here.