Re: [Iptel] [Editorial Errata Reported] RFC3966 (4376)
OKUMURA Shinji <ietf.shinji@gmail.com> Tue, 09 June 2015 07:11 UTC
Return-Path: <ietf.shinji@gmail.com>
X-Original-To: iptel@ietfa.amsl.com
Delivered-To: iptel@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2412D1B29BF for <iptel@ietfa.amsl.com>; Tue, 9 Jun 2015 00:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.899
X-Spam-Level: *
X-Spam-Status: No, score=1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FSL_HELO_FAKE=3.899, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mCTQNcIK7nZ4 for <iptel@ietfa.amsl.com>; Tue, 9 Jun 2015 00:11:47 -0700 (PDT)
Received: from mail-pa0-x241.google.com (mail-pa0-x241.google.com [IPv6:2607:f8b0:400e:c03::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81D671B29C6 for <iptel@ietf.org>; Tue, 9 Jun 2015 00:11:47 -0700 (PDT)
Received: by pabli10 with SMTP id li10so2621438pab.1 for <iptel@ietf.org>; Tue, 09 Jun 2015 00:11:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:mime-version:content-type :content-transfer-encoding:in-reply-to:references:message-id; bh=Gx2gqHUaDfdbdubUu6c3enRUmZtHkxuBIR8ObTq4B04=; b=jyoQVu9zSCZYo2QkeUKx9gkLim8y5RkgqwJtP73OZRpGN4jNDh1TGOlANhnqXNsoLE vvQi3zr+/X3rSXCPirSKggXyx8Bdk0FI/OPCPO8s3TP3pV6XXPL73AyZkzQn8Q392J2k RvVNY/gxS2MRUW9QVkYVos6gQLTG781NKaS0IJaXgHYBk11QBUwzkVyMT3//TKvYVCjh g2wWj80u1aUim2DeUaVOXTzsdMjPQ8K+RoZVYDeTyUhVwak5RUDoPlY6bATvYJW8kTAt sWAulqpEvMlH5+tnM5ZkLI7Wp4TDij7PYewdV7qjunT6BTyTYCAY3Koi0gjrfoO7ngpR gXLw==
X-Received: by 10.70.91.136 with SMTP id ce8mr30737416pdb.29.1433833907150; Tue, 09 Jun 2015 00:11:47 -0700 (PDT)
Received: from gmail.com (x156176.ppp.asahi-net.or.jp. [122.249.156.176]) by mx.google.com with ESMTPSA id tr3sm1590795pbc.75.2015.06.09.00.11.43 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 09 Jun 2015 00:11:46 -0700 (PDT)
From: OKUMURA Shinji <ietf.shinji@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Date: Tue, 09 Jun 2015 16:11:39 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: HidemaruMail 6.43 (WinNT,603)
In-Reply-To: <5575A53B.80205@alum.mit.edu>
References: <CD098708DF903D876E8D0@gmail.com> <5571BB75.5040008@alum.mit.edu> <A1D0A1D3870259ietf.shinji@gmail.com> <5575A53B.80205@alum.mit.edu>
Message-Id: <C8D0A28387A268ietf.shinji@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/iptel/-BjP9kNqlFE4pG99t676V4mHHWw>
Cc: ben@nostrum.com, jdrosen@cisco.com, iptel@ietf.org, alissa@cooperw.in, RFC Errata System <rfc-editor@rfc-editor.org>, hgs@cs.columbia.edu
Subject: Re: [Iptel] [Editorial Errata Reported] RFC3966 (4376)
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IP Telephony <iptel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iptel/>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2015 07:11:49 -0000
Paul Kyzivat wrote: >On 6/8/15 6:11 AM, OKUMURA Shinji wrote: >> Hi Paul, >> >>> On 5/27/15 7:30 AM, OKUMURA Shinji wrote: >>>> Hi, >>>> >>>> phonedigit is used in an extension rule. >>>> >>>> extension = ";ext=" 1*phonedigit >>>> >>>> if the original definition is correct, I think a following >>>> description is valid. >>>> >>>> tel:1234;ext=;phone-context=example.com >>>> >>>> May an extension number be an empty string? >>> >>> That would be bad. >>> >>> But your errata fix isn't sufficient for extension because it would >>> allow an extension including only visual-separators. ISTM that to >>> complete the fix the rule for extension also needs to be changed to: >>> >>> extension = ";ext=" *phonedigit DIGIT *phonedigit >> >> I see, and IIUC this is reducible as below. >> >> extension = ";ext=" *visual-separator DIGIT *phonedigit >> >> The two are equivalent, but from a parser implementor's perspective >> the latter is better (I think). > >I agree the two are equivalent. I think one can argue about which is >easier to understand. I would like to add one more thing. According to the former, it is hard to determine whether a first DIGIT is phonedigit or DIGIT. >But for clarity I do think the same construction >ought to be used in both the definition of extension and >global-number-digits. For an errata I think it is preferable to minimize >the changes to the text, so I think I favor using the form currently >used in global-number-digits. I agree with you. >(If there was to be another bis, then that would be a good time to >change it. And then, I think I would define a new rule for this >construction, that would then be used in both global-number-digits and >extension.) I quite agree. Regards, Shinji >>>> At the very start what is the reason why visual-separator became an >>>> optional rule? >>> >>> I don't know. It certainly seems to have been a mistake. >>> >>>> according to the document history, >>>> >>>> RFC2806 >>>> phonedigit = DIGIT / visual-separator >>>> >>>> draft-ietf-iptel-rfc2806bis-01 >>>> phonedigit = DIGIT [ visual-separator ] >>>> phonedigit-hex = HEXDIG [ visual-separator ] >>>> >>>> draft-ietf-iptel-rfc2806bis-02 >>>> phonedigit = DIGIT / [ visual-separator ] >>>> phonedigit-hex = HEXDIG / "*" / "#" / [ visual-separator ] >>> >>> Thanks, >>> Paul >>> >>>> Anydody know the intent of this fix? >>>> >>>> Regards, >>>> Shinji >>>> >>>>> This errata should be rejected. >>>>> >>>>> - Jason >>>>> >>>>> >>>>> >>>>> On 5/26/15, 11:47 AM, "RFC Errata System" <rfc-editor@rfc-editor.org> >>>>> wrote: >>>>> >>>>>> The following errata report has been submitted for RFC3966, >>>>>> "The tel URI for Telephone Numbers". >>>>>> >>>>>> -------------------------------------- >>>>>> You may review the report below and at: >>>>>> http://www.rfc-editor.org/errata_search.php?rfc=3966&eid=4376 >>>>>> >>>>>> -------------------------------------- >>>>>> Type: Editorial >>>>>> Reported by: OKUMURA Shinji <ietf.shinji@gmail.com> >>>>>> >>>>>> Section: 3 >>>>>> >>>>>> Original Text >>>>>> ------------- >>>>>> phonedigit = DIGIT / [ visual-separator ] >>>>>> phonedigit-hex = HEXDIG / "*" / "#" / [ visual-separator ] >>>>>> >>>>>> >>>>>> Corrected Text >>>>>> -------------- >>>>>> phonedigit = DIGIT / visual-separator; >>>>>> phonedigit-hex = HEXDIG / "*" / "#" / visual-separator; >>>>>> >>>>>> >>>>>> Notes >>>>>> ----- >>>>>> An optional and alternative rule is typically meaningless. >>>>>> >>>>>> Instructions: >>>>>> ------------- >>>>>> This erratum is currently posted as "Reported". If necessary, please >>>>>> use "Reply All" to discuss whether it should be verified or >>>>>> rejected. When a decision is reached, the verifying party (IESG) >>>>>> can log in to change the status and edit the report, if necessary. >>>>>> >>>>>> -------------------------------------- >>>>>> RFC3966 (draft-ietf-iptel-rfc2806bis-09) >>>>>> -------------------------------------- >>>>>> Title : The tel URI for Telephone Numbers >>>>>> Publication Date : December 2004 >>>>>> Author(s) : H. Schulzrinne >>>>>> Category : PROPOSED STANDARD >>>>>> Source : IP Telephony >>>>>> Area : Real-time Applications and Infrastructure >>>>>> Stream : IETF >>>>>> Verifying Party : IESG >>
- [Iptel] [Editorial Errata Reported] RFC3966 (4376) RFC Errata System
- Re: [Iptel] [Editorial Errata Reported] RFC3966 (… Livingood, Jason
- Re: [Iptel] [Editorial Errata Reported] RFC3966 (… OKUMURA Shinji
- Re: [Iptel] [Editorial Errata Reported] RFC3966 (… Paul Kyzivat
- Re: [Iptel] [Editorial Errata Reported] RFC3966 (… OKUMURA Shinji
- Re: [Iptel] [Editorial Errata Reported] RFC3966 (… Paul Kyzivat
- Re: [Iptel] [Editorial Errata Reported] RFC3966 (… OKUMURA Shinji
- [Iptel] [Errata Held for Document Update] RFC3966… RFC Errata System