Re: [DNSOP] On some terminology in draft-ietf-dnsop-respsize (truncation)

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 03 March 2014 18:52 UTC

Return-Path: <ajs@anvilwalrusden.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 0C5FB1A0343 for <dnsop@ietfa.amsl.com>; Mon, 3 Mar 2014 10:52:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 qpmzM0OTMZAd for <dnsop@ietfa.amsl.com>; Mon, 3 Mar 2014 10:52:28 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C13161A032A for <dnsop@ietf.org>; Mon, 3 Mar 2014 10:52:28 -0800 (PST)
Received: from mx1.yitter.info (dhcp-bbc4.meeting.ietf.org [31.133.187.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 512F28A031 for <dnsop@ietf.org>; Mon, 3 Mar 2014 18:52:25 +0000 (UTC)
Date: Mon, 3 Mar 2014 13:52:23 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140303185223.GE5406@mx1.yitter.info>
References: <20140303105138.GA3875@laperouse.bortzmeyer.org> <53149C57.1040105@redbarn.org> <C9C88C7D-E43E-4687-961F-980A4839F561@virtualized.org> <5314CE01.3030806@redbarn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5314CE01.3030806@redbarn.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/pQKe88oJSe6pSyZptg8VpnlU2IU
Subject: Re: [DNSOP] On some terminology in draft-ietf-dnsop-respsize (truncation)
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, 03 Mar 2014 18:52:30 -0000

On Mon, Mar 03, 2014 at 10:46:25AM -0800, Paul Vixie wrote:
> a protocol clarification (not a change, which dnsop can't by charter
> make) 

I really don't think our biggest problem is making the RFC publication
mechanisms move.  If we determine this is a "change" in some sense
because it's clarifying the meaning of the protocol, we can send it up
via AD sponsorship or run it through the INT area WG or whatever.  I
think it's very valuable to get some clear idea of what we think
first, though.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com