Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis
Dick Franks <rwfranks@acm.org> Tue, 03 July 2018 00:45 UTC
Return-Path: <rwfranks@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E30B130E74 for <dnsop@ietfa.amsl.com>; Mon, 2 Jul 2018 17:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sbkxY75pbPoR for <dnsop@ietfa.amsl.com>; Mon, 2 Jul 2018 17:45:46 -0700 (PDT)
Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 D7F5D130EAA for <dnsop@ietf.org>; Mon, 2 Jul 2018 17:45:45 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id j33-v6so173290wrj.5 for <dnsop@ietf.org>; Mon, 02 Jul 2018 17:45:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nz92dGn9PK0t0cIJUdb8Mdwz2sdVf89eDXAPlJTlDkA=; b=d+Dq/+4O6sP94d8LQ8lqctj9LU7JZeps/ylg63GgHMNVSBSdR1XyC0OD8+OagsWqFw esoMbC9oFQWul2gCvZLwMTkJU1v5mMsePoA/rTGGLfC56RSq0P3b9SbloeANlMll5PyL TT7OI/QLJYEI8RaH8h4ilrb4Y1zDlqLK9idTmET6FTavl8Zl5OU5at6MU5virFLI2LGN sQGsy1f8sMirHQDS2iNL1evafAXST+973VhmlR6goezn7PKQrlezBrk8ScEYb6UA7yUA KZyCr5Ea4PUJUOilESftSOPn/huWZ0qbzfycGS3Asd09kDa3n1XUpLTWdli6iYdwrPlt /uPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nz92dGn9PK0t0cIJUdb8Mdwz2sdVf89eDXAPlJTlDkA=; b=sGrD4bQzDLz9LoADe26AUNq7LxpocFGFn/8izQyULAEcjmLj02ZfMLBxj92CU8wW/C M9lyMBo3xXuVJw0lOoSMnCnKcOkW9QqzcirdWSv7EoB3DPSqyVN3a8evj75iVS10GOOz +wy18/W9ESPmbLzsZloaCs/8j8WRky0aHEAw0ZjDcZDaYScMrNAcPt9krQsg2yWUCeZh Vi6xUIZhJntrANDlJYE8x4MZsPmmUfFFH358NGymZQCFHbxQiO3RaV0cO0jLV7jna1iI 3Qdde1OI93OptSSaV+qYLqjVp0l00PMUfiE0fH6qFgeETTKdI/UIpAiM8iO9gMGLRCx1 XlIQ==
X-Gm-Message-State: APt69E1ghu+is7QtcVC+XsEEHU6F5qsOfGE7UjbKocY7pLOTSO8L/wR6 gcnIFA+rXWaK8G+MkMZ/p6R+yKDSzqR1Xo7AQck=
X-Google-Smtp-Source: AAOMgpe0ibAfnV3hQ+FT+zT/jhlqp4UHwYvU+/giI54119GRQiiAw3/oew0YU1uTSCH3kmJy+UQdMWr+6kTJY6ArmDI=
X-Received: by 2002:adf:a20a:: with SMTP id p10-v6mr21222447wra.196.1530578744314; Mon, 02 Jul 2018 17:45:44 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 2002:adf:c7c4:0:0:0:0:0 with HTTP; Mon, 2 Jul 2018 17:45:03 -0700 (PDT)
In-Reply-To: <3AA1BCE3-42CE-4D35-AD25-B06712FE705E@vpnc.org>
References: <17A1E6A9-E43F-41AB-B24D-4B29F17FCC07@gmail.com> <CAKW6Ri7y4K6Aj570GKOJB3p-kiWrWMSx++YrAHf5gq1DQgeSKQ@mail.gmail.com> <3AA1BCE3-42CE-4D35-AD25-B06712FE705E@vpnc.org>
From: Dick Franks <rwfranks@acm.org>
Date: Tue, 03 Jul 2018 01:45:03 +0100
X-Google-Sender-Auth: p9acc3TMmpwJ8FhjD7m07jhygp0
Message-ID: <CAKW6Ri5AGsxEWZsFk=SO5KRMiMb8r+jGhmAFr0GXdBeQoSrngw@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005b10a705700da252"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DpxwbSlyrsjKi_FckwYZAn4UQsY>
Subject: Re: [DNSOP] Working Group Last Call on draft-ietf-dnsop-terminology-bis
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jul 2018 00:45:48 -0000
On 2 July 2018 at 00:03, Paul Hoffman <paul.hoffman@vpnc.org> wrote >8 > Well, RFC 1035 *does* say that it is in ASCII, whether we like that or not. Perhaps we need to remind ourselves what RFC1035 actually *does* say. ASCII is mentioned in three places only: 2.3.3 para 1, initially about case-insensitive character string comparisons, but then wanders off-topic: However, future additions beyond current usage may need to use the full binary octet capabilities in names, so attempts to store domain names in 7-bit ASCII or use of special bytes to terminate labels, etc., should be avoided. 3.1 para 3, supposedly dealing with preferred name syntax, also has another crack at case-insensitive comparisons: Name servers and resolvers must compare labels in a case-insensitive manner (i.e., A=a), assuming ASCII with zero parity. Non-alphabetic codes must match exactly. 6.1.2 para 3, in a section dealing with nameserver internal data structures, yet again gets fixated on character case issues: One way to solve the case problem is to store the labels for each node in two pieces: a standardized-case representation of the label where all ASCII characters are in a single case, together with a bit mask that denotes which characters are actually of a different case. 3.1 para 1, dealing with domain names in DNS messages, which being an external interface, one might expect character encoding to be specified, does not mention ASCII at all. Furthermore, in the whole of section 5, which specifies the format of master files, there is no mention of the character encoding of the files themselves. There is only one other occurrence of "encoding" remotely relevant to the present discussion. 5.1 last para, dealing with special characters and escape sequences: Because these files are text files several special encodings are necessary to allow arbitrary data to be loaded. There is nothing in the subsequent \DDD description to indicate that the decimal number represents an ASCII code point, which it clearly must if labels are ASCII encoded. The other occurrences of "encoding" are in section 8, and deal with mailbox addresses and related matters of no interest here. The proposition that RFC1035 mandates ASCII "presentation format" is demonstrably false. >8 > ... An application could choose to encode the presentation format using a > different encoding, but that's outside the scope of the protocol. Application programs do not "choose the encoding"; that "choice" is inflicted upon them by the I/O system provided by the platform on which they run. If the platform uses EBCDIC, then "presentation format" is EBCDIC encoded, constrained (in this instance) to use the same printable character repertoire as on an ASCII platform. --Dick
- Re: [DNSOP] Working Group Last Call on draft-ietf… Suzanne Woolf
- Re: [DNSOP] Working Group Last Call on draft-ietf… Vladimír Čunát
- [DNSOP] Working Group Last Call on draft-ietf-dns… Suzanne Woolf
- Re: [DNSOP] Working Group Last Call on draft-ietf… Dick Franks
- Re: [DNSOP] Working Group Last Call on draft-ietf… Paul Hoffman
- Re: [DNSOP] Working Group Last Call on draft-ietf… Paul Hoffman
- Re: [DNSOP] Working Group Last Call on draft-ietf… Vladimír Čunát
- Re: [DNSOP] Working Group Last Call on draft-ietf… Dick Franks
- Re: [DNSOP] Working Group Last Call on draft-ietf… Sara Dickinson
- Re: [DNSOP] Working Group Last Call on draft-ietf… Matthew Pounsett
- Re: [DNSOP] Working Group Last Call on draft-ietf… Joe Abley
- Re: [DNSOP] Working Group Last Call on draft-ietf… Kal Feher
- Re: [DNSOP] Working Group Last Call on draft-ietf… Dick Franks
- Re: [DNSOP] Working Group Last Call on draft-ietf… George Michaelson
- [DNSOP] Fwd: Working Group Last Call on draft-iet… william manning
- Re: [DNSOP] Working Group Last Call on draft-ietf… Joe Abley
- Re: [DNSOP] Working Group Last Call on draft-ietf… fujiwara
- Re: [DNSOP] Working Group Last Call on draft-ietf… Paul Hoffman