Re: [DNSOP] draft-ietf-dnsop-dns-terminology needs to define "label"?

manning <bmanning@karoshi.com> Sun, 03 May 2015 00:31 UTC

Return-Path: <bmanning@karoshi.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 512B11A92E5 for <dnsop@ietfa.amsl.com>; Sat, 2 May 2015 17:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 nnnE5wnffMem for <dnsop@ietfa.amsl.com>; Sat, 2 May 2015 17:31:27 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDB341A92E4 for <dnsop@ietf.org>; Sat, 2 May 2015 17:31:26 -0700 (PDT)
Received: from [10.5.5.107] ([118.194.192.64]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id t430UPRi023745 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 2 May 2015 17:31:02 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="us-ascii"
From: manning <bmanning@karoshi.com>
In-Reply-To: <C6EF6F9F-9518-4AC1-9B40-203602FBB3E5@interisle.net>
Date: Sat, 02 May 2015 17:29:28 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABACD294-BF30-465C-8793-6AAC6F8DBE48@karoshi.com>
References: <F62C728A-2B84-4863-B4F4-474B8F49CA6F@gmail.com> <CADA1DAC-5EFC-491C-92DB-AAFF0E0A5F26@vpnc.org> <C6EF6F9F-9518-4AC1-9B40-203602FBB3E5@interisle.net>
To: Chapin Lyman <lyman@interisle.net>
X-Mailer: Apple Mail (2.1878.6)
X-MailScanner-ID: t430UPRi023745
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: bmanning@karoshi.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/UgkCzeiJmaCsbcpx8XIisOZ-1GY>
Cc: DNSOP WG <dnsop@ietf.org>, Suzanne Woolf <suzworldwide@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [DNSOP] draft-ietf-dnsop-dns-terminology needs to define "label"?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 03 May 2015 00:31:29 -0000

this is what I think of when I look at the DNS protocol.   Well done Lyman!

manning

bmanning@karoshi.com
PO Box 12317
Marina del Rey, CA 90295
310.322.8102



On 30April2015Thursday, at 8:14, Lyman Chapin <lyman@interisle.net> wrote:

> 
> On Apr 29, 2015, at 6:39 PM, Paul Hoffman wrote:
> 
>> On Apr 29, 2015, at 2:44 PM, Suzanne Woolf <suzworldwide@gmail.com> wrote:
>>> I'm suggesting a new definition in Sec. 2, as follows: 
>>> 
>>> "Label -- The portion of a domain name at each node in the tree making up a fully-qualified domain name" 
>> 
>> Works for me. What do others think?
> 
> I'm uncomfortable with both "portion" and "making up." Labels are the "atoms" from which FQDN compounds are constructed, and "portion" isn't precise enough to capture that; and I don't think that "making up" will translate well beyond English. How about:
> 
> "Label - The identifier of an individual node in the sequence of nodes that comprise a fully-qualified domain name."
> 
> - Lyman
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop