Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-rfc2317bis
神明達哉 <jinmei@wide.ad.jp> Wed, 13 January 2016 17:23 UTC
Return-Path: <jinmei.tatuya@gmail.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 13FFA1B2F87 for <dnsop@ietfa.amsl.com>; Wed, 13 Jan 2016 09:23:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, 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 s8wF9pzCBNZL for <dnsop@ietfa.amsl.com>; Wed, 13 Jan 2016 09:23:17 -0800 (PST)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (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 90CDA1B2F88 for <dnsop@ietf.org>; Wed, 13 Jan 2016 09:23:15 -0800 (PST)
Received: by mail-ig0-x22f.google.com with SMTP id z14so156118775igp.1 for <dnsop@ietf.org>; Wed, 13 Jan 2016 09:23:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Cid+HBqkxVhCK/fIOnHuXew4XQ3T/L/B+fF2VyRxjgc=; b=ZoSGqF5IIY2oWvAWDahLep2TRKf1SG/JCUKjzpXPWHzxyXgEQ+TvOKwPmBtqWI0f8h ia87kbrfvyFjbd+dhS4Yr/qiFPu7AQ2QFWtot8YpRS+Ea6NTf/YnYHTAuqhk/IissDNL rJkAhsmvjFrs03HYWcF061kLMLqCm9FuhyNl3JPB94xFmkwYlPA1Ya/hgUgVpb34s02e jdu3KSfddRqbE+r6b0RZQwAwzmROtM/1I79rG6LuQNRJV9w39vEutzqNijF37CSKmRkd 28/DiQydRtBPW/1K6ZNQBmh9n2JSExIcEaUn/Q0GgnZ5pqOftupsgdg7JCeC1BQYt38a nhqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Cid+HBqkxVhCK/fIOnHuXew4XQ3T/L/B+fF2VyRxjgc=; b=fGUQ+7n14hEAtZAKFsUfj9z8tckPo9OvGBHx1l47I0BEoRM/OVVtfeRZnsrRZhee5/ WrJT35kvwTPDtNGGJATEQULk2eqUuqNSe+NJO0Ti+4Dm2NO271JDkepIi2ptGgnhRhlz vP4i4o581s9E+NOQqy3B8FYmdPraSlRsl4ogCVItV8HQx/Eyoq9rwUFClyEGuDz9VuY/ x8uES5t0A11wM5f+nLoM8B7VNJ2jO78aAbDbxz2Ir9/MxiV6D8lgG4Cll+3ssu7gMMnN hPzqrAoUVfw/eQNXJ1HnBoKHFb4g03rG7E7J3fnY4pxm+K/jEsoxET8oOK3paBsNVoOP xA0A==
X-Gm-Message-State: ALoCoQngpvit8J1b2HqNoXRKe5DxmedF+nZOByooBTXxbE54hWrXDFhNOx7x79YNU+q0/ASmhLu73dcEUj66guxi0KVdQMXIUQ==
MIME-Version: 1.0
X-Received: by 10.50.13.100 with SMTP id g4mr23056938igc.64.1452705795051; Wed, 13 Jan 2016 09:23:15 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.129.80 with HTTP; Wed, 13 Jan 2016 09:23:14 -0800 (PST)
In-Reply-To: <alpine.LSU.2.00.1601131007410.8365@hermes-2.csi.cam.ac.uk>
References: <566E329D.7010007@gmail.com> <CAJE_bqeR5nVGOnLWQ3CzWKR86===VoXWNsqyas3yJEG5zX2n=Q@mail.gmail.com> <alpine.LSU.2.00.1601131007410.8365@hermes-2.csi.cam.ac.uk>
Date: Wed, 13 Jan 2016 09:23:14 -0800
X-Google-Sender-Auth: flhCud-ykYCUPBfT9n6qRvaZ2GM
Message-ID: <CAJE_bqc53vizG54TS9yRCfP62EdnzyP=5piDRVKixAWB+_C+kw@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: Tony Finch <dot@dotat.at>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/KE_OHZDG_-Vinf-XiEtnnjy3Hds>
Cc: Tim Wicinski <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>
Subject: Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-rfc2317bis
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: <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: Wed, 13 Jan 2016 17:23:18 -0000
At Wed, 13 Jan 2016 10:13:42 +0000, Tony Finch <dot@dotat.at> wrote: > > - I wonder why its intended status is standards track. It generally > > just talks about operational techniques rather than describe some > > new protocol, so a BCP seems to be more appropriate (in fact RFC2317 > > is a BCP). Perhaps it's because this document will "update" RFC2136? > > I'm not necessarily opposed to it, but just curious. > > Yes, it's because of the changes to UPDATE. (See the questions for > reviewers in the appendices) Ah, okay, I overlooked the appendix. RFC 2317 is BCP 20. Should this document be moved to the standards track, since it updates RFC 2136? Or should the UPDATE amendment be a separate document? With this understanding I have two followup questions: - If a document is marked as "Updates <Standards Track RFC>", does it automatically mean its status should be Standards Track, too? - Does rfc2317bis really "update" RFC2136 in the first place? It certainly provides some additional client behavior that uses RFC2136, but it doesn't seem to require any change to RFC2136 itself (am I overlooking something?). > > - Section 8 > > > > Similarly, for its IPv6 network 2001:db8:A::/48, organization A again > > asks for a DNAME record, like this: > > > > I'm not sure why 'a' in '2001:db8:A::' is upper-cased, but if > > there's not a strong reason for it I'd consider lower-casing it, > > applying the recommendation of RFC5952 (whose primary target is not > > literature like I-Ds or RFCs, but I think it's generally better to > > have consistent view in various textual representations of IPv6 > > addresses). > > I have used "2001:db8:A::" for the same reason I used "A.example". Is it > too cute? I don't see the reason you used "A.example" either...but in any case this is a minor point that is probably just a matter of taste, so if you have a strong preference of this particular style I wouldn't object. -- JINMEI, Tatuya
- [DNSOP] Call for Adoption: draft-fanf-dnsop-rfc23… Tim Wicinski
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Bob Harold
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… 神明達哉
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… 神明達哉
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Tim Wicinski
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Andreas Gustafsson
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Andreas Gustafsson
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Tony Finch
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… Andreas Gustafsson
- Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-r… 神明達哉