[weirds] [Technical Errata Reported] RFC7483 (4503)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 14 October 2015 14:58 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id AAB7A1A00B4
for <weirds@ietfa.amsl.com>; Wed, 14 Oct 2015 07:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001,
SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100]
autolearn=ham
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 76brnE991s9I for <weirds@ietfa.amsl.com>;
Wed, 14 Oct 2015 07:58:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49])
by ietfa.amsl.com (Postfix) with ESMTP id EEFA31A911F
for <weirds@ietf.org>; Wed, 14 Oct 2015 07:58:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30)
id EB9F218046A; Wed, 14 Oct 2015 07:58:26 -0700 (PDT)
To: andy@arin.net, shollenbeck@verisign.com, barryleiba@computer.org,
olaf@nlnetlabs.nl, superuser@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20151014145826.EB9F218046A@rfc-editor.org>
Date: Wed, 14 Oct 2015 07:58:26 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/4zXLqlWjckB_ll4M-QOokHxwxXo>
Cc: weirds@ietf.org, rfc-editor@rfc-editor.org
Subject: [weirds] [Technical Errata Reported] RFC7483 (4503)
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service
\(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>,
<mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>,
<mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 14:58:41 -0000
The following errata report has been submitted for RFC7483, "JSON Responses for the Registration Data Access Protocol (RDAP)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7483&eid=4503 -------------------------------------- Type: Technical Reported by: Scott Hollenbeck <shollenbeck@verisign.com> Section: 5.2 and 5.3 Original Text ------------- In Section 5.2: \\"ldhName\\" : \\"ns1.xn--fo-5ja.example\\", \\"unicodeName\\" : \\"ns1.foo.example\\", In Section 5.3: \\"ldhName\\" : \\"xn--fo-5ja.example\\", \\"unicodeName\\" : \\"foo.example\\", \\"ldhName\\" : \\"xn--fo-cka.example\\", \\"unicodeName\\" : \\"foo.example\\" \\"ldhName\\" : \\"xn--fo-fka.example\\", \\"unicodeName\\" : \\"foo.example\\" \\"ldhName\\": \\"xn--fo-8ja.example\\", \\"unicodeName\\" : \\"foo.example\\" Corrected Text -------------- In Section 5.2: \\"ldhName\\" : \\"ns1.xn--fo-5ja.example\\", \\"unicodeName\\" : \\"ns1.fóo.example\\", In Section 5.3: \\"ldhName\\" : \\"xn--fo-5ja.example\\", \\"unicodeName\\" : \\"fóo.example\\", \\"ldhName\\" : \\"xn--fo-cka.example\\", \\"unicodeName\\" : \\"fõo.example\\" \\"ldhName\\" : \\"xn--fo-fka.example\\", \\"unicodeName\\" : \\"föo.example\\" \\"ldhName\\" : \\"xn--fo-8ja.example\\", \\"unicodeName\\" : \\"fôo.example\\" Notes ----- The unicodeName examples in RFC 7483 are invalid per RFC 5890. Here\\'s an example from Section 5.2 on page 23: \\"unicodeName\\" : \\"ns1.foo.example\\", Section 3 of 7483 says this about Unicode names: \\"Unicode names: Textual representations of DNS names where one or more of the labels are U-labels as described by [RFC5890].\\" 5890 says: \\"A \\"U-label\\" is an IDNA-valid string of Unicode characters, in Normalization Form C (NFC) and including at least one non-ASCII character, expressed in a standard Unicode Encoding Form (such as UTF-8).\\" The examples in 7483 contain all ASCII characters. Syntactically valid examples are shown in the corrected text. Ignore the backslash characters. They were inserted by the errata submission tool. 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. -------------------------------------- RFC7483 (draft-ietf-weirds-json-response-14) -------------------------------------- Title : JSON Responses for the Registration Data Access Protocol (RDAP) Publication Date : March 2015 Author(s) : A. Newton, S. Hollenbeck Category : PROPOSED STANDARD Source : Web Extensible Internet Registration Data Service Area : Applications Stream : IETF Verifying Party : IESG
- [weirds] [Technical Errata Reported] RFC7483 (450… RFC Errata System
- Re: [weirds] [Technical Errata Reported] RFC7483 … Barry Leiba
- [weirds] [Errata Verified] RFC7483 (4503) RFC Errata System