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

Not clear from this extract what associated normative references you have. 

They need to at least cover which calendar is in use, and how sequences of digits or letter digits are converted into days or months (for example is January "01" or "10" and indeed is January the 1st month.

Keith

> -----Original Message-----
> From: salud-bounces@ietf.org [mailto:salud-bounces@ietf.org] On Behalf Of
> Laura Liess
> Sent: 13 February 2013 14:47
> To: salud@ietf.org
> Subject: [salud] New version of the ABNF-syntax
> 
> Hi,
> 
> Because we had several changes and discussions which affect the
> syntax,  I send a new version to the list, including the rules for
> <date>.  I used the <provider-id>,  <MM> and <DD> definitions from the
> RFC 4198.
> Please let me know what you think of it.
> 
>        alert-URN         = "urn:alert:" alert-identifier
>        alert-identifier    = alert-category ":" alert-indication
>        alert-category    = name/private-name
>        alert-indication   = alert-name *(":" alert-name)
>        alert-name         = name/private-name
>        name                = label
>        private-name      = label"@"provider-id["(" date ")"]
>        provider-id          = 1*(label ".") toplabel
>        date                  = [CC] YY ["-" MM ["-" DD] ]
>        label                  = let-dig [ *let-dig-hyp let-dig ]
>        let-dig-hyp          = let-dig / "-"
>        let-dig                = ALPHA / DIGIT
>        YY                    = CC
>        CC                    = DIGIT DIGIT
>       MM                    = ("0" %x31-39) / ("1" %x30-32)
>       DD                     = ("0" %x31-39) / (%x31-32 DIGIT) / "30" /
> "31"
>       ALPHA               = %x41-5A / %x61-7A   ; A-Z / a-z
>       DIGIT                  = %x30-39 ; 0-9
>       DIGIT-1-9             = %x31-39 ; 1-9
>       DIGIT-2-9             = %x32-39 ; 2-9
> 
>     Following rules apply to the <date> usage:
>        a) A provider is permitted to use any <date> within its domain
> name ownership time period.
>        b) If the <date> is absent, it defaults to 2013-01-01.
>        c) If <DD> or <MM> are absent each defaults to 01.
>        d)  If <CC> is absent it defaults to 20.
>        e)  Comparison is based on the full <CCYY-MM-DD> after defaults
> have been filled in.
>        f)   A provider is allowed to use a domain name without a date
> if he owns the domain at the default year 2013 or if he is able to
> verify that he is the first owner of the domain, e.g. by checking
> reliable domain history tools.   Note: We assume that the domain
> ownership does not change during the same year.
> 
> 
> Thank you
> Laura
> _______________________________________________
> salud mailing list
> salud@ietf.org
> https://www.ietf.org/mailman/listinfo/salud