Re: [salud] New version of the ABNF-syntax

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 08 March 2013 17:23 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 6A1B521F8628 for <salud@ietfa.amsl.com>; Fri, 8 Mar 2013 09:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.27
X-Spam-Level:
X-Spam-Status: No, score=-0.27 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 BmDM+9mt9wKp for <salud@ietfa.amsl.com>; Fri, 8 Mar 2013 09:23:08 -0800 (PST)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id ED11E21F8615 for <salud@ietf.org>; Fri, 8 Mar 2013 09:23:07 -0800 (PST)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta02.westchester.pa.mail.comcast.net with comcast id 8zf71l0050mv7h0515P75Y; Fri, 08 Mar 2013 17:23:07 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta11.westchester.pa.mail.comcast.net with comcast id 95P61l00z3ZTu2S3X5P7UM; Fri, 08 Mar 2013 17:23:07 +0000
Message-ID: <513A1E7A.3000600@alum.mit.edu>
Date: Sat, 09 Mar 2013 01:23:06 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: salud@ietf.org
References: <CACWXZj2WhAsmQ3Ku7bVpiNhbFxX7-vx9d9wWzzKgiVLSeKk__g@mail.gmail.com> <201302132105.r1DL5BM01801234@shell01.TheWorld.com> <CACWXZj0Qq=Q=7necdgCPLeFAMbr3gg-WmBb-8UzegseEd_b_Qw@mail.gmail.com> <201302181854.r1IIsNFG2067515@shell01.TheWorld.com> <CACWXZj2P58HXJUAYQyB_mp9z_-qCCVwKD1jHhcJg6kGxJ5xVng@mail.gmail.com> <201302212027.r1LKRU4D2297154@shell01.TheWorld.com> <CACWXZj1txwpeCFqAJrJQpL845BNswyvm651WABGULr0DuEwF3A@mail.gmail.com> <201302221824.r1MIOpqh2386335@shell01.TheWorld.com> <CACWXZj0nsvE0ey2H=a0azN+eWSPq2oJnbC6VxyRKA0bEhkPQjg@mail.gmail.com> <51390F9F.2070708@alum.mit.edu> <201303081630.r28GUSKl028790@shell01.TheWorld.com> <CACWXZj2cadevRdh8uFXraqhrNtMguiid+RZVRNt0T30yeyzykg@mail.gmail.com>
In-Reply-To: <CACWXZj2cadevRdh8uFXraqhrNtMguiid+RZVRNt0T30yeyzykg@mail.gmail.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=q20121106; t=1362763387; bh=1DOKDzifgiF5GRAsrMwVCF3oL6GvDvgnMXBfS45AO6I=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Dqaf/lO9ZHqvfoZ2ByJuLENX3adKhoyxksltkZjnBrOE+6NF7RIq4h1ea499/bbM6 ScnAkmoAPYVhpsgV7xAcplqxx70xiVoP6g2YAbuHaC/VBuchslNsRp/66ghXkKdGCx COZZ1YUgXEDzU0Y5Av+qPLsg5s02TTd6zec6zymuwDRQglnJRn2qtVG9cwnTnS9rCo vP4fn6Hvi5GnY+REgdhbPiFa9QWJSA57F0K6YUrq61yoInWTVKLsybgKIu0tvG/liA Zss3Pn3srdTtuHxRoMRXHSQqm7YuT2tfRaxSY1IdkVF6YcFG+gCG+MsFzkms86D2CB pUrUzgpVFdzqA==
Subject: Re: [salud] New version of the ABNF-syntax
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: Fri, 08 Mar 2013 17:23:09 -0000

I'm ok with leaving as-is.

	Paul

On 3/9/13 12:57 AM, Laura Liess wrote:
> Dale,
>
>
> 2013/3/8 Dale R. Worley <worley@ariadne.com <mailto:worley@ariadne.com>>
>
>      > >        alert-URN         = "urn:alert:" alert-identifier
>      > >        alert-identifier  = alert-category ":" alert-indication
>      > >        alert-category    = alert-name
>      > >        alert-indication  = alert-name *(":" alert-name)
>      > >        alert-name        = alert-label / private-name
>      > >        private-name      = alert-label "@" provider
>      > >        provider          = provider-id ["(" date ")"]
>      > >        provider-id       = 1*(domain-label ".") domain-label
>      > >        alert-label       = let-dig [ *let-dig-hyp let-dig ]
>      > >        domain-label      = let-dig [ *let-dig-hyp let-dig ]
>
>      > Date: Fri, 08 Mar 2013 06:07:27 +0800
>      > From: Paul Kyzivat <pkyzivat@alum.mit.edu
>     <mailto:pkyzivat@alum.mit.edu>>
>      >
>      > This looks good. For reasons of non-redundancy, I would be
>     inclined to
>      > make one tweak:
>      >
>      >     alert-label = domain-label
>
>     We might consider:
>
>              alert-label       = label
>              domain-label      = label
>              label             = let-dig [ *let-dig-hyp let-dig ]
>
>     But the savings are small.
>
>
> I would leave them as they are, for the reasons I gave in my previous
> mail to Paul.
>
> Additionally,  I found out that we use the word "label"  in the section
> 6.1 in a way which would not be consistent with the syntax above.
>
>    "Alert URN identifiers are identified by <label>s managed by IANA,
>     according to the processes outlined in [RFC5226] in a new registry
>     called "Alert URN Labels".  Thus, creating a new Alert-Info URN
>     identifier requires IANA action.  The policy for adding a new alert
>     category is 'Standards Action'.  (This document defines the alert
>     categories 'service', 'source', 'priority', 'duration', 'delay' and
>     'locale'. ) The policy for assigning <label>s to <alert-indication>s
>     and the rules to combine them may differ for each <alert-category>
>     and MUST be defined by the document describing the corresponding
>     alert category. "
>
>
> Thank you
> Laura
>
>
>
>
>
>
>
>
>     Dale
>     _______________________________________________
>     salud mailing list
>     salud@ietf.org <mailto:salud@ietf.org>
>     https://www.ietf.org/mailman/listinfo/salud
>
>
>
>
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud
>