Re: [DNSOP] Call for Adoption: draft-fanf-dnsop-rfc2317bis
神明達哉 <jinmei@wide.ad.jp> Mon, 18 January 2016 18:01 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 C6AC61B3B2F for <dnsop@ietfa.amsl.com>; Mon, 18 Jan 2016 10:01:54 -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 cu-vToiVBjrS for <dnsop@ietfa.amsl.com>; Mon, 18 Jan 2016 10:01:53 -0800 (PST)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 A07671B3B31 for <dnsop@ietf.org>; Mon, 18 Jan 2016 10:01:53 -0800 (PST)
Received: by mail-ig0-x235.google.com with SMTP id mw1so52863150igb.1 for <dnsop@ietf.org>; Mon, 18 Jan 2016 10:01:53 -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=IkcN5JgVoQjD8J0l5ja7qdlWMiNQbllKEnkeUblbZKc=; b=FCK8NQRnNiTJ6o0YmRuwglVtHAGc9YEr1/VIbvlE5qYQRc2TaKKCf5FXOwS1VY+ddl jUEFdjojRmV3iQDKSyMlZOvr1F0O8nxhblPLhbaWOmIW3g2pQCKy4n/g0jZETKb1+jBY jW/mJePuvA8mOPdOYXr29wg6VfIJvzF2RpDifC3hMHgbWfuwY+rEU4OFGrzMLBjcNo2D gCSlM6FgN1m3kqb9qQtQ9LAvDOpQqh5b0vjvsc+vjEMaaS6XzrnQpvP3PEQ7WGsEpQXL AvyIS/3ZjCWu7w4PLyL7EMb2dJFV7BjnRaXLLB7KhUVEQW/NQXiQ5YRZGhL9NaRZVBBI XK9g==
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=IkcN5JgVoQjD8J0l5ja7qdlWMiNQbllKEnkeUblbZKc=; b=bxYh4cTeAACJmiyw2RTuRPnPq+ADZ1eO5LLAd92bOMYOIklBeM6JJh/DRoirzJi19U Mq+IBB6rRAwcWRqsJpcwqcwtXmDzRcANvoMCscZgRvwNSSnA2V8tJVbuQ2a4ud1M/LZT 0vVU6TMiUuyoIbU5tqp+/Cn4hDJYSZnCvWm5wpbyTOr7g1kqhE24DGEPXfZIb3Nq6ItO 8Msn3c7Dlj/7l5VD46+5xeJisvXL8Dx0dpbb3HcpxAvZ6IRxyUwECmiDLYLhs00Y4rMM MIDqkQ+ssJTEwh6n89Akb+Qi048u7YfQdRq+PNHqxhR1SOXu2bcMoEqAQNpVcS0X4G3S We9g==
X-Gm-Message-State: AG10YOQA+EcUHwOtL0HUyfhBQi/0KXUOgZ9o4IOKemJx7DutNwpt6CnQk50sBIuPYvl3iL57HadPFrCVgZELSA==
MIME-Version: 1.0
X-Received: by 10.50.111.111 with SMTP id ih15mr12254547igb.78.1453140112895; Mon, 18 Jan 2016 10:01:52 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.129.80 with HTTP; Mon, 18 Jan 2016 10:01:52 -0800 (PST)
In-Reply-To: <22173.2856.460371.326297@guava.gson.org>
References: <566E329D.7010007@gmail.com> <CAJE_bqeR5nVGOnLWQ3CzWKR86===VoXWNsqyas3yJEG5zX2n=Q@mail.gmail.com> <alpine.LSU.2.00.1601131007410.8365@hermes-2.csi.cam.ac.uk> <CAJE_bqc53vizG54TS9yRCfP62EdnzyP=5piDRVKixAWB+_C+kw@mail.gmail.com> <alpine.LSU.2.00.1601141306000.8365@hermes-2.csi.cam.ac.uk> <22171.35498.720284.788325@guava.gson.org> <alpine.LSU.2.00.1601180947500.21715@hermes-2.csi.cam.ac.uk> <22172.52821.887433.918681@guava.gson.org> <alpine.LSU.2.00.1601181154080.21715@hermes-2.csi.cam.ac.uk> <22173.2856.460371.326297@guava.gson.org>
Date: Mon, 18 Jan 2016 10:01:52 -0800
X-Google-Sender-Auth: VTZOHlR1RCk-4_qMtOEg8R5Hjyc
Message-ID: <CAJE_bqd2xzSO2u9r0X49u8FO_UvoVkEuBU-OYpVuCjyO9-UqWA@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: Andreas Gustafsson <gson@araneus.fi>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/Yy55SoHpwCDldxRVaODXJi7zBDo>
Cc: Tony Finch <dot@dotat.at>, 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: Mon, 18 Jan 2016 18:01:54 -0000
At Mon, 18 Jan 2016 17:56:24 +0200, Andreas Gustafsson <gson@araneus.fi> wrote: > > Can you point to specific wording that needs changing? > > Mainly, the "Updates: 2136", and each instance of "UPDATE client". > For example, in the Introduction, you could change > > While these methods interoperate well with DNS resolvers, they > require some care from dynamic DNS UPDATE clients that are trying to > change IN-ADDR.ARPA mappings. The client needs to follow the CNAME > and/or DNAME redirections so that its UPDATE request changes the > canonical PTR record without disrupting the redirections. > > to something like > > While these methods interoperate well with DNS resolvers, they > require some care from entities that update IN-ADDR.ARPA mappings, > such as DHCP servers and IP management systems. These need to > follow the CNAME and/or DNAME redirections so that the update > changes the canonical PTR record without disrupting the redirections. FWIW, this makes much more sense to me than "Updates: 2136". I also agree with this rationale: At Mon, 18 Jan 2016 13:36:53 +0200, Andreas Gustafsson <gson@araneus.fi> wrote: > The requirements in Section 9 should apply to entities like DHCP > servers and IP management systems, whose functionality includes the > management of reverse mappings, and that may contain, call upon, or > (if we must use that term) "be" an UPDATE client to perform the > changes. But an entity that only serves as an UPDATE client, like > the "nsupdate" program in the BIND distribution, should not be subject > to the requirements because it does not deal specifically with reverse > mappings, but with arbitrary DNS names and records. Calling them > "requirements on UPDATE clients" when they only apply to entities > that are more than just UPDATE clients seems wrong to me. -- 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… 神明達哉