[DNSOP] terminology: glue

Casey Deccio <casey@deccio.net> Mon, 04 May 2015 14:32 UTC

Return-Path: <casey@deccio.net>
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 11A831A1A76 for <dnsop@ietfa.amsl.com>; Mon, 4 May 2015 07:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.022
X-Spam-Level:
X-Spam-Status: No, score=0.022 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 6T26dUn0jVjX for <dnsop@ietfa.amsl.com>; Mon, 4 May 2015 07:32:40 -0700 (PDT)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (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 854591A1A7B for <dnsop@ietf.org>; Mon, 4 May 2015 07:32:37 -0700 (PDT)
Received: by igblo3 with SMTP id lo3so83130608igb.0 for <dnsop@ietf.org>; Mon, 04 May 2015 07:32:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=deccio.net; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=+nL51JZIXqJmnmA3rL5EiNU69bOSPwvqEw1SluWsvew=; b=K64s4buaZXnjmcdtcTrjxuBhuGV3kdadGfyKEoFlidtbUJ1Og2gkPVj/TFF4OIksH5 8iTomhZTHIUAQDWTstatTCe2dDO8wgGmBKlGRbFyCwiBsTPNopJEdYrDE1WD/DgXL+wb 4yK+cNIkTt6bBtgUFm0ELAWrWJvZUGgcRdjGQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=+nL51JZIXqJmnmA3rL5EiNU69bOSPwvqEw1SluWsvew=; b=V4GSwf0CeMAN+dWEhYokV7EGW+vMhUFTHVJ1S2gdG9VLyIr02YtRO5RvEs1EBTFG9j ziKtSFN4bT11hsqG4Ob6h1yZMf+08XoCsdyIXowPUn9wM9z2gCQGvdwx1Hd3O028T0lH 9q5PhRfwK6ct0bAX/VvMHuaYMeY2RWZ3Gr5fai/h74Q7dYR4+CmXbS2s89MJvdj9tvXQ o08jZ5Sn/riqUkvhDqr0PlQEu4VgDO55OUjNTFvIHnOq/yfrN7TEk3yO+Frcf0j04XFT NdBRN/59cpgJVA+mo6m/dZeiZOh4E7tFmUN/occlcyNCMYfp7EEhGdbWkg57iZ0+3chU BwQA==
X-Gm-Message-State: ALoCoQncwT5WeRQ8YkMwsNYd1QCwUNE10MeSPVEop9QsSktZYGC/69rKM9R+NSM+U/n4ZIZQOdhU
MIME-Version: 1.0
X-Received: by 10.43.167.137 with SMTP id ne9mr27788377icc.7.1430749956884; Mon, 04 May 2015 07:32:36 -0700 (PDT)
Received: by 10.50.23.78 with HTTP; Mon, 4 May 2015 07:32:36 -0700 (PDT)
Date: Mon, 04 May 2015 10:32:36 -0400
Message-ID: <CAEKtLiTq_OLY_aPqdntwHCQV0m64T=1wuDNRbtnLGi01bb90qw@mail.gmail.com>
From: Casey Deccio <casey@deccio.net>
To: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c2fa1af15e100515426e92"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/OnE9Ox_UiCliowZY_83MhncgKd0>
Subject: [DNSOP] terminology: glue
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: Mon, 04 May 2015 14:32:41 -0000

I am still a bit uncomfortable with the -01 definition of glue,
specifically the reference to RFC 2181.  I think the reference to RFC 2181
is useful and necessary, but I hesitate to think that RFC 2181's use of
glue is a redefinition that is intended to apply outside of the RFC
itself.  That is, I believe the term was overloaded (similar to the
apparent overloading of "label" discussed in another recent dnsop thread).

Here is some proposed re-wording (modified from a previous proposal), which
both adds more context (quoted from earlier RFC 1034 text) for the use of
glue to the first paragraph and gives less weight to the RFC 2181 reference
in the second.

Glue records -- "[Records] which are not part of the
   authoritative data [for a zone], and are address resource records for
   the servers [in a subzone].  These RRs are only necessary if the name
   server's name is 'below' the cut, and are only used as part of a
   referral response."  Without glue "we could be faced with the situation
   where the NS RRs tell us that in order to learn a name server's
   address, we should contact the server using the address we wish to
   learn." (Definition from RFC 1034, section 4.2.1)

   A later definition is that glue "includes any record in a zone file
   that is not properly part of that zone, including nameserver records
   of delegated sub-zones (NS records), address records that accompany
   those NS records (A, AAAA, etc), and any other stray data that might
   appear" ([RFC2181], section 5.4.1).  Although glue is sometimes used
   today with this wider definition in mind, the context surrounding the
   RFC 2181 definition suggests it is intended to apply to the use of glue
   within document itself and not necessarily beyond.