Re: [DNSOP] Brief addition to terminology-bis draft

"StJohns, Michael" <msj@nthpermutation.com> Tue, 04 September 2018 04:29 UTC

Return-Path: <msj@nthpermutation.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 EE612130E4C for <dnsop@ietfa.amsl.com>; Mon, 3 Sep 2018 21:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20150623.gappssmtp.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 lQzXiMGI91YS for <dnsop@ietfa.amsl.com>; Mon, 3 Sep 2018 21:29:43 -0700 (PDT)
Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) (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 215E7130DF1 for <dnsop@ietf.org>; Mon, 3 Sep 2018 21:29:43 -0700 (PDT)
Received: by mail-wr1-x444.google.com with SMTP id v17-v6so2379137wrr.9 for <dnsop@ietf.org>; Mon, 03 Sep 2018 21:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SvnfFjjLPGusurplJA/0FS+ZT7LZSNth83euhzZrrOM=; b=q00k9WpOdMqDO/OL6IoPncQ49CaQLQk9rzy0pNkzF8EDavXZbHRRW9ZD15N71OszNL dwnhvGw7Qilo7eu3MybtGdE/GEnedgpufG4QyJ11zyzkXjmt1UfKLdloZ8kAX+2VanYG K/ginag0uUWWbpw0JgtP14loptKxr6VyoAp3ajDlMfhtBlbu14ZBiTlgaVStFPfLPniU l9zl1ykkjbcz0+7aAQKDx/vMkE6+mVtEdbdcgQdiLWSChXCbJSqWO4Nv/4qwk6JPOXzO n0bJv1nwB65dC4+VVvjO+02zO7IsMOYGiXMo/QFsaG3e1vSWTTjzVhf2ysMkvApSpK8q wK+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SvnfFjjLPGusurplJA/0FS+ZT7LZSNth83euhzZrrOM=; b=WHmIVdstleq/YWH591DehL85/GzkkoFjmJ3eNlu9orNr26GEzBF122Es6FGzOtzvsS VHKtFrTwkIO41HCPH9SqzXBzcoUobUilFPNDnByw0S+QqAmoT5xTJxzvqmaDYTuabvUM 7ZmFPn8L/6VvvWx0/RfbTorZMQUBKCJd6uH5Qc2JJaQvZXJZL5RYJuFULVTmKrRzN4pk I9PeNKdXoMaJNlbkpkhrHYYU5AUPJCFvEVznBin/f2hfd1iNRmBCWwwnLa5sp0L7fC68 XPhLIR9A3Dsbnl2Ln/NirQySNjPc34DAEaSq0FbCeC2iq7sPjB4WwQRCazrwdzUlQ47m s70w==
X-Gm-Message-State: APzg51B480MH7gU43jRg02dnvImv6Eb5K9ZJaerV+2oFKmtEwpRTAYTM MhCY7c2lfZ2Kxz/L5MFYwrgMyPJO+KLPlvpjjIWfHQ==
X-Google-Smtp-Source: ANB0VdaCHKJV6DNRwzHoQCgEiIDHDIBsxr0/Yb6IIUuzpJElmIlnbCmt0F1z3Mi7HV1IZiP8n8dxmr/Ma9qrpdHIucU=
X-Received: by 2002:adf:afd3:: with SMTP id y19-v6mr21162057wrd.176.1536035381571; Mon, 03 Sep 2018 21:29:41 -0700 (PDT)
MIME-Version: 1.0
References: <4AA8656A-7D2F-4584-B84D-47E97483CCC2@gmail.com> <5B8D548E.5080205@redbarn.org> <30BF3D0E-1EE9-4310-ACCB-413E019B6D93@isc.org>
In-Reply-To: <30BF3D0E-1EE9-4310-ACCB-413E019B6D93@isc.org>
From: "StJohns, Michael" <msj@nthpermutation.com>
Date: Tue, 4 Sep 2018 00:29:30 -0400
Message-ID: <CANeU+ZDMLxpS1VLCunM6DRmkLqtt521Q+QSHwdhvMZ-+eGqSMA@mail.gmail.com>
To: Mark Andrews <marka@isc.org>
Cc: Paul Vixie <paul@redbarn.org>, Suzanne Woolf <suzworldwide@gmail.com>, dnsop@ietf.org, draft-ietf-dnsop-terminology-bis.all@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004804450575041bba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/qLtA4456VTGREAM700qRiHMvfMQ>
Subject: Re: [DNSOP] Brief addition to terminology-bis draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
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, 04 Sep 2018 04:29:46 -0000

Actually, 5.2 suggests that a master  file (not zone) should contain a
single class and single SOA record.  That’s not the same thing as limiting
a zone to a single class AFAICT.

Mike


On Mon, Sep 3, 2018 at 18:49 Mark Andrews <marka@isc.org>; wrote:

> RFC 1035 Section 5.2 limits a zone to be single class.
>
> > On 4 Sep 2018, at 1:34 am, Paul Vixie <paul@redbarn.org>; wrote:
> >
> >
> >
> > Suzanne Woolf wrote:
> >> Hi all,
> >>
> >> During the IESG review, Adam Roach noticed that
> >> draft-ietf-dnsop-terminology-bis talked about “class" but never defined
> >> it. This seemed to the authors and chairs like a reasonable thing to
> >> fix. It’s also important enough that we want WG review, but not
> >> extensive enough to require a new LC.
> >>
> >> Here's the definition that the authors would like to add to the
> document:
> >>
> >>
> >>    Class:
> >>    A class "identifies a protocol family or instance of a protocol"
> >>    (Quoted from [RFC1034], Section 3.6). "The DNS tags all data with a
> >>    class as well as the type, so that we can allow parallel use of
> >>    different formats for data of type address." (Quoted from [RFC1034],
> >>    Section 2.2). In practice, the class for nearly every query is "IN".
> >>    There are some queries for "CH", but they are usually for the
> >>    purposes of information about the server itself rather than for a
> >>    different type of address.
> >>
> >> Please let us know your opinions yea or nay by Monday, Sept. 10,
> >> midnight UTC.
> >
> > i don't think this def'n serves the need. we need to speak more truth:
> >
> > "The Class tag was weakly defined, such that either a zone can have data
> in multiple classes, or each class can have its own zone cut hierarchy, and
> so neither interpretation can be relied upon by DNS protocol implementers."
> >
> > then go on to "in practice..."
> >
> > --
> > P Vixie
> >
> > _______________________________________________
> > DNSOP mailing list
> > DNSOP@ietf.org
> > https://www.ietf.org/mailman/listinfo/dnsop
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742              INTERNET: marka@isc.org
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>