Re: [Iptel] [Editorial Errata Reported] RFC3966 (4376)
OKUMURA Shinji <ietf.shinji@gmail.com> Mon, 08 June 2015 10: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 4085A1A891E for <iptel@ietfa.amsl.com>; Mon, 8 Jun 2015 03:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.599
X-Spam-Level: ****
X-Spam-Status: No, score=4.599 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 v2pzwVgddB8v for <iptel@ietfa.amsl.com>; Mon, 8 Jun 2015 03:11:56 -0700 (PDT)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (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 F36F71A891C for <iptel@ietf.org>; Mon, 8 Jun 2015 03:11:55 -0700 (PDT)
Received: by pdbnf5 with SMTP id nf5so101401798pdb.2 for <iptel@ietf.org>; Mon, 08 Jun 2015 03:11:55 -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=+fzSqvjxf8pxBvoJGkVi23Fk06/bMGa8XNt2PLa1gxk=; b=EOiL8WIy/SM+SPvj6HdY8k+/Bwn3tFs6WLBL547DRD0YNV3cEuwY4MmjAGqXXDPxj4 9qYnat6XCkirZSvvOjcFQ5nWEvFqG6iiLyRdXKtYdoz7aqYJyXRgy8qTD5gKcg96XxrY UYaNFc4WLarg8VbEq+05G4FTg0/Yc12VlAIW3LYRjTgpJlDNbq2mRKa4agTFgF3pQ78S r2TLSJNQiSKbeXVDHD4q88we81LKBkeHnTkFp0gC9uYrrU3zqkKWDnMLUBRKWdTDzeS8 M3GvcAyvBQiYvLeQ7xxb+u/DCpqOcbChRGKMtvIRn9ZFIW6N6aAyqeJsgE/fwifAFp5T S3Hw==
X-Received: by 10.66.160.71 with SMTP id xi7mr27954629pab.19.1433758315658; Mon, 08 Jun 2015 03:11:55 -0700 (PDT)
Received: from gmail.com (x156176.ppp.asahi-net.or.jp. [122.249.156.176]) by mx.google.com with ESMTPSA id to6sm2089171pbc.19.2015.06.08.03.11.52 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 08 Jun 2015 03:11:53 -0700 (PDT)
From: OKUMURA Shinji <ietf.shinji@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Date: Mon, 08 Jun 2015 19:11:46 +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: <5571BB75.5040008@alum.mit.edu>
References: <20150526154737.6666D180207@rfc-editor.org> <D18A12D9.1033C2%jason_livingood@cable.comcast.com> <CD098708DF903D876E8D0@gmail.com> <5571BB75.5040008@alum.mit.edu>
Message-Id: <A1D0A1D3870259ietf.shinji@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/iptel/Mf90LyolBrZuPqwCMSBqV96kVPs>
Cc: iptel@ietf.org
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: Mon, 08 Jun 2015 10:11:57 -0000
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). 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