From laura.liess.dt@googlemail.com Fri Feb 8 06:16:44 2013 Return-Path: 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 7E1A921F8814 for ; Fri, 8 Feb 2013 06:16:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ac7u2B4qnGqf for ; Fri, 8 Feb 2013 06:16:43 -0800 (PST) Received: from mail-lb0-f179.google.com (mail-lb0-f179.google.com [209.85.217.179]) by ietfa.amsl.com (Postfix) with ESMTP id 5097D21F87F6 for ; Fri, 8 Feb 2013 06:16:43 -0800 (PST) Received: by mail-lb0-f179.google.com with SMTP id j14so3031111lbo.10 for ; Fri, 08 Feb 2013 06:16:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=O4/WSBaucGCYsdvbDcWXXXKatpFfRXogZL4+pfvesDc=; b=USoO36TURSAVv7BBS6noeAMWFlr9ZwPuCCHLT8M+TH2ANQ7ESqwmOVcUtOOy51LWIt hT8ABgsUwCn4n0ayNXkZIulXTp6GP3NuqTdblz3cKTTtPKqZy5DaGyrc8ehyDGfpcGFf H3AVd8a/IjwTfQ8ZNb3Np1jXalMLd0b3yyDHb7pl05VuNibUDtwb8y3IvkHvKCqXE3/U 5VscIH41sNCOJ2QGo/ux/OUqEoSGSRjlIyeP1kcvaDVPmINztxnusU60QWJKBR+wfjQv bzGYAapxow4ORB0Ve4NvD879BmrIJG1iHYkiQte4o2ul50vYD+r78EXPiiqyz70I5qgo IRHw== MIME-Version: 1.0 X-Received: by 10.112.84.228 with SMTP id c4mr2291656lbz.113.1360333002069; Fri, 08 Feb 2013 06:16:42 -0800 (PST) Received: by 10.114.95.99 with HTTP; Fri, 8 Feb 2013 06:16:41 -0800 (PST) In-Reply-To: <057.7a5f62e2602eb6d273497968d68ec4cc@trac.tools.ietf.org> References: <057.7a5f62e2602eb6d273497968d68ec4cc@trac.tools.ietf.org> Date: Fri, 8 Feb 2013 15:16:41 +0100 Message-ID: From: Laura Liess To: salud issue tracker Content-Type: text/plain; charset=ISO-8859-1 Cc: draft-ietf-salud-alert-info-urns@tools.ietf.org, dworley@avaya.com, salud@ietf.org Subject: Re: [salud] #4: Using s as X-BeenThere: salud@ietf.org 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: Fri, 08 Feb 2013 14:16:44 -0000 I think this is a good idea. I think it is no problem to change the ABNF-syntax accordingly. By the way, it seems to me that your mail didn't go to the salud ML, also salud@ietf.org was in your CC. Thank you Laura 2013/1/28 salud issue tracker : > #4: Using s as > > Should private-names be usable as alert-categories as well as components > alert-indications (alternatives with an alert-category)? > > Allowing this would allow private definitions of entire alert-categories. > Disallowing this would constrain private definitions to be further > refinement of standard categories. > > -- > -------------------------+------------------------------------------------- > Reporter: | Owner: draft-ietf-salud-alert-info- > dworley@avaya.com | urns@tools.ietf.org > Type: defect | Status: new > Priority: major | Milestone: > Component: alert-info- | Version: > urns | Keywords: > Severity: - | > -------------------------+------------------------------------------------- > > Ticket URL: > salud > From laura.liess.dt@googlemail.com Mon Feb 11 06:35:21 2013 Return-Path: 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 33C4F21F87D2 for ; Mon, 11 Feb 2013 06:35:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.978 X-Spam-Level: X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czFrQycygeaD for ; Mon, 11 Feb 2013 06:35:20 -0800 (PST) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCD121F87C3 for ; Mon, 11 Feb 2013 06:35:20 -0800 (PST) Received: by mail-la0-f48.google.com with SMTP id fq13so5882283lab.35 for ; Mon, 11 Feb 2013 06:35:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=SPTjdR4G1LGpuX+TKhd8Gbk81ut9h67KxV/m3s84ExA=; b=WeyWc8t5qo+xMYaoUxa8GGprI/nNgu2p96FSceXxPkQH3XrhXm9Fo5EcdocUwdwGky BvrRcibSbFTkjCt/z1RnEDX61IvChyKUh48IQkdBnQzP+fi/Ea+bPnvgm2UxgtMvLHfK TdbA1fXbBPWQ+KOYlTqYqO46tc6tTMoUcS+p1R0drRBRKfvfEBFzBeF+G5AW/pzHLco0 zql5evdKouYOBI9ALIYNN5mytYD5kJPhnOAzJAvCnGXw9aJ+tUBxUd5RvHzQ5rWNVms8 MAABdGbD85B8FDqtqPPIRhNcLnzUWzdC9yO4z9xYlsXuMINT2znPFv3ux4HVTEB98bF6 OaWA== MIME-Version: 1.0 X-Received: by 10.112.40.129 with SMTP id x1mr5855305lbk.95.1360593319213; Mon, 11 Feb 2013 06:35:19 -0800 (PST) Received: by 10.114.95.99 with HTTP; Mon, 11 Feb 2013 06:35:19 -0800 (PST) Date: Mon, 11 Feb 2013 15:35:19 +0100 Message-ID: From: Laura Liess To: salud@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [salud] Do we need the FQDN to be followed by at least one label? X-BeenThere: salud@ietf.org 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: Mon, 11 Feb 2013 14:35:21 -0000 Hi, We agreed that the FQDN must be followed by at least one label, because the FQDN alone does not specify anything in particular (it was my own proposal at some time.) See 5) in Dale's message http://www.ietf.org/mail-archive/web/salud/current/msg00290.html However, it seems to me that this is no longer true. We changed the syntax for some times since then. E.g. or make sense. Note: Paul already agreed to this statement. Thanks a lot Laura From worley@shell01.TheWorld.com Mon Feb 11 09:26:23 2013 Return-Path: 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 52F5C21F87D4 for ; Mon, 11 Feb 2013 09:26:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.705 X-Spam-Level: X-Spam-Status: No, score=-2.705 tagged_above=-999 required=5 tests=[AWL=0.275, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxy89a7-UKkZ for ; Mon, 11 Feb 2013 09:26:22 -0800 (PST) Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id B6DE421F86F5 for ; Mon, 11 Feb 2013 09:26:22 -0800 (PST) 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 r1BHQDLJ027340; Mon, 11 Feb 2013 12:26:15 -0500 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 r1BHQDV11661797; Mon, 11 Feb 2013 12:26:13 -0500 (EST) Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1BHQC3N1651824; Mon, 11 Feb 2013 12:26:12 -0500 (EST) Date: Mon, 11 Feb 2013 12:26:12 -0500 (EST) Message-Id: <201302111726.r1BHQC3N1651824@shell01.TheWorld.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: Laura Liess In-reply-to: (laura.liess.dt@googlemail.com) References: Cc: salud@ietf.org Subject: Re: [salud] Do we need the FQDN to be followed by at least one label? X-BeenThere: salud@ietf.org 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: Mon, 11 Feb 2013 17:26:23 -0000 > From: Laura Liess > > We agreed that the FQDN must be followed by at least > one label, because the FQDN alone does not > specify anything in particular (it was my own proposal at some time.) > See 5) in Dale's message > http://www.ietf.org/mail-archive/web/salud/current/msg00290.html > > However, it seems to me that this is no longer true. We changed the > syntax for some times since then. E.g. > or > make sense. > > Note: Paul already agreed to this statement. Yes, I agree. The real condition is that if there is an FQDN, there must be at least one label that logically follows it. But of course, in the syntax "...:foo@example.com:...", the label "foo" does *logically* follow the FQDN (although it is *written* first). (I have some memory that I said something incorrect about this in the past.) Dale From laura.liess.dt@googlemail.com Tue Feb 12 07:25:58 2013 Return-Path: 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 C539B21F8EFC for ; Tue, 12 Feb 2013 07:25:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.678 X-Spam-Level: X-Spam-Status: No, score=-1.678 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_52=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAHzjgSjnRQy for ; Tue, 12 Feb 2013 07:25:58 -0800 (PST) Received: from mail-la0-x234.google.com (la-in-x0234.1e100.net [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id E404C21F8EF0 for ; Tue, 12 Feb 2013 07:25:57 -0800 (PST) Received: by mail-la0-f52.google.com with SMTP id fs12so190514lab.25 for ; Tue, 12 Feb 2013 07:25:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=zSH27J9IHmnehkBN3eZwTEccbsptH2RI6pf0q/0MyIo=; b=neQgT437C/v2sUpELIxcgO4XF03Ufj0xtpSAunhP5yaq+JDR1XBaIGjXendVdJSb/J 3US07BMji1mlCaw3/quYkCvft2EmyiSJCx320VVJFXPCfRA1NUWCuKgVHToyUXLYD1EU raameRFzc6Yjmq7wPtBKzZbtGqa7ac/+rx8txPRBn7Eq7xlSpWCGw2oPPhoTMf8V6XMN PhUN5a+00hPZPXfuiJl0i8rLL1bc336m05oNneI4rznZgCcDzpeikbthX3wZdbU0nLik dw0fJDDPLzM/Wne4TAzWcvYkz0dVxhSIXp6xO2auMn5v+j97Y2y4XVHzg9SXsX8S0/T+ 1OjA== MIME-Version: 1.0 X-Received: by 10.152.104.36 with SMTP id gb4mr17088455lab.13.1360682756699; Tue, 12 Feb 2013 07:25:56 -0800 (PST) Received: by 10.114.95.99 with HTTP; Tue, 12 Feb 2013 07:25:56 -0800 (PST) Date: Tue, 12 Feb 2013 16:25:56 +0100 Message-ID: From: Laura Liess To: salud@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [salud] Opinion concerning ticket #1 issues X-BeenThere: salud@ietf.org 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: Tue, 12 Feb 2013 15:25:58 -0000 Hi, Here are my personal view/opinions on the issues in ticket #1: (1)We already agreed on (1b), didnt'we? (2) It seems that we couldn't get an agreement on using "~", Paul doesn't like it. I am OK with Paul's proposal to use "(...)" e.g., "telephone.com(2013)". Other opinions? (3) I think we should try with (3a1). At least a domain owner who owned the domain at the default date should be allowed to omit the date. (4) Let's try with (4c). (5) (5b) because of (4c). The syntax would be DATE = [CC] YY ["-" MM ["-" DD] ]. (6) Maximizing the number of current users who can use the default date is a good argument in favor of (6b), so I would say let's take (6b). (7) I would propose to add Paul's proposal from http://www.ietf.org/mail-archive/web/salud/current/msg00295.html to the draft text and then discuss it with Alfred Hoenes. Maybe he knows how reliable domaintools.com is. Thank you Laura From pkyzivat@alum.mit.edu Tue Feb 12 07:39:00 2013 Return-Path: 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 71F0121F8EDB for ; Tue, 12 Feb 2013 07:39:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.062 X-Spam-Level: X-Spam-Status: No, score=-0.062 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, J_CHICKENPOX_52=0.6, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jiSKzGouwfE5 for ; Tue, 12 Feb 2013 07:38:56 -0800 (PST) Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id D0C1021F8ED8 for ; Tue, 12 Feb 2013 07:38:55 -0800 (PST) Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta03.westchester.pa.mail.comcast.net with comcast id zPeJ1k0031YDfWL53Tevx3; Tue, 12 Feb 2013 15:38:55 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta20.westchester.pa.mail.comcast.net with comcast id zTeu1k01D3ZTu2S3gTevRo; Tue, 12 Feb 2013 15:38:55 +0000 Message-ID: <511A620E.50407@alum.mit.edu> Date: Tue, 12 Feb 2013 10:38:54 -0500 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: salud@ietf.org References: In-Reply-To: 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=1360683535; bh=41GMqf3v/UKzHcWNAg5vgSHhx/SafEICQV7P3rt6vQQ=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=UyidXIsTNVZjsh4b5ubsZODverut/x5haKxmttLbMgOXYU1idSTnCswGXB01n6O07 11j0oWLnsCZbwNhViQl3+9zFyRspq0km5JzDP1imaJkia3lCMkuGbaayCgyQuyKKKc HPqqx+ig4rXWb2V58Ps3P5KcNGonUcxVlVm6MdUgqXyJYCih8ItgweKLKgSmZWnfe/ 9GBgHV+TUBnamxdhz75NST0rDBN6JWpsbBY1QpeXqr0MYheVPU8E8nSnVwZ2alhEzz OSya62+1EEQcbcyfgedYz6GDhj4FvqEWNaa3R0luVE80t5MLgxSU0PLGOw82Wz1TIR shgezPPQnmtqA== Subject: Re: [salud] Opinion concerning ticket #1 issues X-BeenThere: salud@ietf.org 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: Tue, 12 Feb 2013 15:39:00 -0000 I'm fine with everything here. Thanks, Paul On 2/12/13 10:25 AM, Laura Liess wrote: > Hi, > > Here are my personal view/opinions on the issues in ticket #1: > > (1)We already agreed on (1b), didnt'we? > > (2) It seems that we couldn't get an agreement on using "~", Paul > doesn't like it. I am OK with Paul's proposal to use "(...)" e.g., > "telephone.com(2013)". Other opinions? > > (3) I think we should try with (3a1). At least a domain owner who > owned the domain at the default date should be allowed to omit the > date. > > (4) Let's try with (4c). > > (5) (5b) because of (4c). The syntax would be DATE = [CC] YY ["-" MM > ["-" DD] ]. > > (6) Maximizing the number of current users who can use the default > date is a good argument in favor of (6b), so I would say let's take > (6b). > > (7) I would propose to add Paul's proposal from > http://www.ietf.org/mail-archive/web/salud/current/msg00295.html to > the draft text and then discuss it with Alfred Hoenes. Maybe he knows > how reliable domaintools.com is. > > Thank you > Laura > _______________________________________________ > salud mailing list > salud@ietf.org > https://www.ietf.org/mailman/listinfo/salud > From laura.liess.dt@googlemail.com Wed Feb 13 00:15:16 2013 Return-Path: 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 BF4E121F8A6F for ; Wed, 13 Feb 2013 00:15:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.977 X-Spam-Level: X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-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 2pAcc0L18lnk for ; Wed, 13 Feb 2013 00:15:16 -0800 (PST) Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) by ietfa.amsl.com (Postfix) with ESMTP id EF17321F89D5 for ; Wed, 13 Feb 2013 00:15:12 -0800 (PST) Received: by mail-lb0-f169.google.com with SMTP id m4so761526lbo.0 for ; Wed, 13 Feb 2013 00:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ADpgbL7p4mXFlHCxHBpvH1lkhHvci8OudOztt7NPnfQ=; b=Z338t02Bn4zHJLDJ2dBCEM6o+4NYuuu8vynvvR/WuM7YSgkD94B+HhIHnrIhH8NrtU Cf3+HRMGglPOv1NK6cOpEVL10dlZV5IYA8Pt7fYLAK+Fh5TwTQJvfJ9zUM2eky9GLJS5 LXRFwyZOHmLa5A9198J9GbkkUZqakEaNQK3yeFfr4DA+Ero3xgfSKTyPtJO7vkCMCrjK liXS+GBruRCmbZ6WBOJCTABv7HhWqqTA/aHsUkTPoZB7TCGkOcgxk+ykvfJxvkHxdm2r CwT8Srrpaw6muokVeVXII+nMqPTtD4HeFxSa9FjRMJEddQg9qh76Rex7eHPaEoKWsMkp y3AQ== MIME-Version: 1.0 X-Received: by 10.152.104.36 with SMTP id gb4mr19404258lab.13.1360743311845; Wed, 13 Feb 2013 00:15:11 -0800 (PST) Received: by 10.114.95.99 with HTTP; Wed, 13 Feb 2013 00:15:11 -0800 (PST) Date: Wed, 13 Feb 2013 09:15:11 +0100 Message-ID: From: Laura Liess To: salud@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [salud] Ticket #2 X-BeenThere: salud@ietf.org 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 Feb 2013 08:15:16 -0000 Hi, It seem to me that we already have a general agreement that the lables should be in the ordinary order. Any other opinions? Thank you laura From laura.liess.dt@googlemail.com Wed Feb 13 06:46:44 2013 Return-Path: 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 C4BC821F871D for ; Wed, 13 Feb 2013 06:46:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.827 X-Spam-Level: X-Spam-Status: No, score=-1.827 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_LOW=-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 OkoUk81Eshj6 for ; Wed, 13 Feb 2013 06:46:44 -0800 (PST) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by ietfa.amsl.com (Postfix) with ESMTP id CFD3021F86FC for ; Wed, 13 Feb 2013 06:46:43 -0800 (PST) Received: by mail-lb0-f177.google.com with SMTP id go11so1002561lbb.36 for ; Wed, 13 Feb 2013 06:46:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=fR35KN+UtrcujZOZ3m0UUlvo+Q3Nyt41bpNCOGWGTIE=; b=JJbpY9rpf0YsdbDFguKsmnDP7NKxc0ZWHk7YEIZStFM6tnTR8w5xNsjXCcaP5Ytqb9 o/AV8XaTI4lN0b8bGJvy1nFG3TRQeLE74eoX+n7unHv2j7szmqU+RhDgMaanvSSdaUHo c3RiS4RyKh9EALwoj3dD6dfBUmF0L0wiIAsp8D3YdXD+q1D2wQn2iDXScc3P22Z1GgQ4 jjKH6sCS2KdWAefyJ5dr3h7a1U03oQqyEeX8B6MPgR97LA1sAUfuo/OIvsxRmGzOJ5z8 6H47VpnQ+BwmUOjnwJNUq7Sxu5br4BVCrtt/rqQGB7QTCBPsVJmcuVcqHxhcTQlKL01y RaXg== MIME-Version: 1.0 X-Received: by 10.152.125.239 with SMTP id mt15mr20423388lab.26.1360766802841; Wed, 13 Feb 2013 06:46:42 -0800 (PST) Received: by 10.114.95.99 with HTTP; Wed, 13 Feb 2013 06:46:42 -0800 (PST) Date: Wed, 13 Feb 2013 15:46:42 +0100 Message-ID: From: Laura Liess To: salud@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 14:46:44 -0000 Hi, Because we had several changes and discussions which affect the syntax, I send a new version to the list, including the rules for . I used the , and
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 usage: a) A provider is permitted to use any within its domain name ownership time period. b) If the is absent, it defaults to 2013-01-01. c) If
or are absent each defaults to 01. d) If is absent it defaults to 20. e) Comparison is based on the full 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 From keith.drage@alcatel-lucent.com Wed Feb 13 07:13:48 2013 Return-Path: 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 10A9E21F8753 for ; Wed, 13 Feb 2013 07:13:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -108.628 X-Spam-Level: X-Spam-Status: No, score=-108.628 tagged_above=-999 required=5 tests=[AWL=1.321, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_FR=0.35, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] 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 1bP1Xw+F4LNd for ; Wed, 13 Feb 2013 07:13:47 -0800 (PST) Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by ietfa.amsl.com (Postfix) with ESMTP id EDB4F21F86C5 for ; Wed, 13 Feb 2013 07:13:46 -0800 (PST) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail5.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id r1DFDeIW022242 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Feb 2013 16:13:45 +0100 Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.46]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Wed, 13 Feb 2013 16:13:42 +0100 From: "DRAGE, Keith (Keith)" To: Laura Liess , "salud@ietf.org" Date: Wed, 13 Feb 2013 16:13:40 +0100 Thread-Topic: [salud] New version of the ABNF-syntax Thread-Index: Ac4J+PmS2xiFvaTHRYus67Spab2ziAAA1Y1w Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.13 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 15:13:48 -0000 Not clear from this extract what associated normative references you have.= =20 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 J= anuary "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 >=20 > Hi, >=20 > Because we had several changes and discussions which affect the > syntax, I send a new version to the list, including the rules for > . I used the , and
definitions from the > RFC 4198. > Please let me know what you think of it. >=20 > alert-URN =3D "urn:alert:" alert-identifier > alert-identifier =3D alert-category ":" alert-indication > alert-category =3D name/private-name > alert-indication =3D alert-name *(":" alert-name) > alert-name =3D name/private-name > name =3D label > private-name =3D label"@"provider-id["(" date ")"] > provider-id =3D 1*(label ".") toplabel > date =3D [CC] YY ["-" MM ["-" DD] ] > label =3D let-dig [ *let-dig-hyp let-dig ] > let-dig-hyp =3D let-dig / "-" > let-dig =3D ALPHA / DIGIT > YY =3D CC > CC =3D DIGIT DIGIT > MM =3D ("0" %x31-39) / ("1" %x30-32) > DD =3D ("0" %x31-39) / (%x31-32 DIGIT) / "30" / > "31" > ALPHA =3D %x41-5A / %x61-7A ; A-Z / a-z > DIGIT =3D %x30-39 ; 0-9 > DIGIT-1-9 =3D %x31-39 ; 1-9 > DIGIT-2-9 =3D %x32-39 ; 2-9 >=20 > Following rules apply to the usage: > a) A provider is permitted to use any within its domain > name ownership time period. > b) If the is absent, it defaults to 2013-01-01. > c) If
or are absent each defaults to 01. > d) If is absent it defaults to 20. > e) Comparison is based on the full 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. >=20 >=20 > Thank you > Laura > _______________________________________________ > salud mailing list > salud@ietf.org > https://www.ietf.org/mailman/listinfo/salud From pkyzivat@alum.mit.edu Wed Feb 13 10:03:42 2013 Return-Path: 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 3825C21F8589 for ; Wed, 13 Feb 2013 10:03:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.796 X-Spam-Level: X-Spam-Status: No, score=0.796 tagged_above=-999 required=5 tests=[AWL=-1.067, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, MANGLED_TOOL=2.3, RDNS_NONE=0.1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I0Zma3rdvk34 for ; Wed, 13 Feb 2013 10:03:41 -0800 (PST) Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 244D021F8501 for ; Wed, 13 Feb 2013 10:03:37 -0800 (PST) Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta13.westchester.pa.mail.comcast.net with comcast id zo5P1k0011swQuc5Du3diX; Wed, 13 Feb 2013 18:03:37 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta15.westchester.pa.mail.comcast.net with comcast id zu3d1k00S3ZTu2S3bu3doB; Wed, 13 Feb 2013 18:03:37 +0000 Message-ID: <511BD578.5090001@alum.mit.edu> Date: Wed, 13 Feb 2013 13:03:36 -0500 From: Paul Kyzivat User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: salud@ietf.org References: In-Reply-To: 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=1360778617; bh=ontV9kPqwOwR0qzKX70ckcelGWwAa47kpye0k3vxm04=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=fhh8FM1xRHuPx0BlHwb3yqAyZffcRPSNnRweO9BXNr4ueiu5+ZtC20trs7kvYVtK5 zvK6borK59Gqux3smpEtDUVVV4mjqYK+l21zmiqNsdSR7q1WrLfVCNZ4c6hKf1Gd2E EGNCrKuRt8hwqwQDgH2OwQTBejuDxvRxAujWNSh32qPVfwxwXsuJju3ECDeW5O8pHC +GLaVhEtEKwgUKJYdmgBDSmYjalnC3d/gnIhu3ePlKeGaCN2AAEQna23VuzXnboObc fRR6gBTuFdvc39N2e6aQqyG5AyQ1/NxwkkiyAcj2Mhbw8AnnbpzRTURgwH3+EBDr/p BQIn9EoTSYF3Q== 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 18:03:42 -0000 On 2/13/13 9:46 AM, Laura Liess wrote: > Hi, > > Because we had several changes and discussions which affect the > syntax, I send a new version to the list, including the rules for > . I used the , and
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 Since private-name is now allowed as a category as well as an alert-name, the above can be simplified further: alert-URN = "urn:alert:" alert-identifier alert-identifier = alert-category ":" alert-indication alert-category = alert-name alert-indication = alert-name *(":" alert-name) alert-name = label/private-name > private-name = label"@"provider-id["(" date ")"] > provider-id = 1*(label ".") toplabel Definition of toplabel is missing. > 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 usage: > a) A provider is permitted to use any within its domain > name ownership time period. > b) If the is absent, it defaults to 2013-01-01. > c) If
or are absent each defaults to 01. > d) If is absent it defaults to 20. > e) Comparison is based on the full 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. I'd like to propose a major change to (f): "The meaning of a private-name with a particular domain name and date is specified by the owner of the domain at that date. The first owner of a domain may specify the meaning of private-names with dates prior to first ownership. As a consequence, the first owner of a domain may specify the meaning of a private-name that contains no date." (My point is that anybody can *use* a private name with any date they want. The only issue is what (if anything) it *means*. Since there is no registration for private-names, we can just talk about it in a general way.) I'm not entirely satisfied with the above. A private-name out of context doesn't really have a meaning. It is the whole alert-identifier that has a meaning. But I don't know how to say this in a comprehensible way. Thanks, Paul From worley@shell01.TheWorld.com Wed Feb 13 11:57:13 2013 Return-Path: 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 D974921E8051 for ; Wed, 13 Feb 2013 11:57:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.727 X-Spam-Level: X-Spam-Status: No, score=-2.727 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grpm8lJ0CSFY for ; Wed, 13 Feb 2013 11:57:13 -0800 (PST) Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id 4B22021E8037 for ; Wed, 13 Feb 2013 11:57:07 -0800 (PST) Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1DJuvL4004994; Wed, 13 Feb 2013 14:56:59 -0500 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 r1DJuuEB1794289; Wed, 13 Feb 2013 14:56:56 -0500 (EST) Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1DJusJI1795782; Wed, 13 Feb 2013 14:56:54 -0500 (EST) Date: Wed, 13 Feb 2013 14:56:54 -0500 (EST) Message-Id: <201302131956.r1DJusJI1795782@shell01.TheWorld.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: "DRAGE, Keith (Keith)" In-reply-to: (keith.drage@alcatel-lucent.com) References: Cc: salud@ietf.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 19:57:14 -0000 > From: "DRAGE, Keith (Keith)" > > Not clear from this extract what associated normative references you have. Yeah, we need to put in a reference to RFC 3339 in somewhere. But for discussion purposes, you can safely assume that's what we mean. Dale From worley@shell01.TheWorld.com Wed Feb 13 13:06:08 2013 Return-Path: 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 8F36E21F8777 for ; Wed, 13 Feb 2013 13:06:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.587 X-Spam-Level: X-Spam-Status: No, score=-1.587 tagged_above=-999 required=5 tests=[AWL=-0.907, BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s1QF3PFoOxIT for ; Wed, 13 Feb 2013 13:06:06 -0800 (PST) Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id CE03121F8770 for ; Wed, 13 Feb 2013 13:06:05 -0800 (PST) Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1DL5Ena019573 for ; Wed, 13 Feb 2013 16:05:16 -0500 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 r1DL5Ept1790455 for ; Wed, 13 Feb 2013 16:05:14 -0500 (EST) Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1DL5BM01801234; Wed, 13 Feb 2013 16:05:11 -0500 (EST) Date: Wed, 13 Feb 2013 16:05:11 -0500 (EST) Message-Id: <201302132105.r1DL5BM01801234@shell01.TheWorld.com> From: worley@ariadne.com (Dale R. Worley) Sender: worley@ariadne.com (Dale R. Worley) To: salud@ietf.org In-reply-to: (laura.liess.dt@googlemail.com) References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 21:06:08 -0000 (as an individual) OK, we can see that this is going well because the ABNF is quite simple and clear. I've made the following adjustments in the version below: - aligned the columns and normalized the spacing between elements - put blank lines to break the rules in to sections, and reordered the rules - applied Paul's simplification - changed the rule "YY=CC" to "YY=DIGIT DIGIT", because YY is semantically different from CC - removed DIGIT-1-9 and DIGIT-2-9, because they are not used - added a rule for "toplabel" - broken private-name into two parts, because one of the rules needs to refer to the provider-id-and-date part alert-URN = "urn:alert:" alert-identifier alert-identifier = alert-category ":" alert-indication alert-category = alert-name alert-indication = alert-name *(":" alert-name) alert-name = label / private-name name = label private-name = label "@" provider provider = provider-id ["(" date ")"] provider-id = 1*(label ".") toplabel [I'm not sure I like the names of the two preceding rules.] toplabel = ALPHA [ *let-dig-hyp let-dig ] label = let-dig [ *let-dig-hyp let-dig ] let-dig-hyp = let-dig / "-" let-dig = ALPHA / DIGIT date = [CC] YY [ "-" MM ["-" DD] ] CC = DIGIT DIGIT YY = 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 I want to make two modifications so that the ABNF symbols can be used to describe the semantics more easily: 1. I want to have a symbol that refers to the component of the URN that can be removed during the resolution algorithm. Currently, alert-name is used for both alert-category and as a component of alert-indication. 2. I want to have a syntactic distinction between alert-names which have standard meanings and alert-names which are privately defined. However, both of these changes are messy and unclear when written in ABNF. So I will see if I can use semantic specifications to achieve the same result. The semantic rules are: 1) provider-id: This is intended to match the allowed ABNF for domain names. (What is the correct normative reference? With internationalization, is our syntax still correct?) 2) date: syntax is a subset of ??? in RFC 3339. 2a) If is absent from , it defaults to 2013-01-01. 2b) If
or are absent, each defaults to 01. 2c) If is absent, it defaults to 20. In all situations, including comparison of URNs and determining which entity defines the meanings of s, s are interpreted as if they contain values with a full "CCYY-MM-DD" value, which is determined according to the above rules. 3) Comparison of URNs: Comparison is case-insensitive, considering the URNs as character strings (but with respect to rule (2)). 4) Removing components when interpreting URNs: (section 8.1 step (b)) The s of the URN are removed sequentially from back to front, until the first in the is removed, at which point the URN is discarded from consideration. 5) Definition of meaning of
or are absent, each defaults to 01. > 2c) If is absent, it defaults to 20. > > In all situations, including comparison of URNs and determining which > entity defines the meanings of s, s are > interpreted as if they contain values with a full "CCYY-MM-DD" > value, which is determined according to the above rules. > > 3) Comparison of URNs: > > Comparison is case-insensitive, considering the URNs as character > strings (but with respect to rule (2)). > > 4) Removing components when interpreting URNs: > (section 8.1 step (b)) > > The s of the URN are removed sequentially from back to > front, until the first in the is > removed, at which point the URN is discarded from consideration. > > 5) Definition of meaning of
or are absent, each defaults to 01. > 2c) If is absent, it defaults to 20. > > In all situations, including comparison of URNs and determining which > entity defines the meanings of s, s are > interpreted as if they contain values with a full "CCYY-MM-DD" > value, which is determined according to the above rules. > > 3) Comparison of URNs: > > Comparison is case-insensitive, considering the URNs as character > strings (but with respect to rule (2)). > > 4) Removing components when interpreting URNs: > (section 8.1 step (b)) > > The s of the URN are removed sequentially from back to > front, until the first in the is > removed, at which point the URN is discarded from consideration. > > 5) Definition of meaning of