Re: To "lose the argument in the WG"

"Pete Resnick" <presnick@qti.qualcomm.com> Tue, 14 February 2017 23:12 UTC

Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA79129407 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level:
X-Spam-Status: No, score=-7.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.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 mGxgJBYvNY5H for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:12:36 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5410129454 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:12:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1487113956; x=1518649956; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=3NwP9wS1HIX2igbYRlDnQeyc+qRkUT3QxQRgBauXLRs=; b=CH24hJnKPscLvsQF6fJyQiQr9VvBeyagAEiQMsU4TXkMQIwkoxdX666P +kdpQy/gvpQARkv3SHQ/7BJY6FkTZSE8ddNWTbIENtE1qk9jVGKrFboeO KZ8cL7Bsa7o/MeYlRvI6XnXy/++j3BGHXau+lcWJNlEEY18h0ZimNYr/R I=;
X-IronPort-AV: E=Sophos;i="5.35,163,1484035200"; d="scan'208,217";a="358262169"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 14 Feb 2017 15:12:36 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8439"; a="1313690670"
Received: from unknown (HELO [10.64.121.67]) ([10.64.121.67]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Feb 2017 15:12:36 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 15:12:04 -0800
Message-ID: <2E079756-5944-4EF5-A82C-E983B9E8F237@qti.qualcomm.com>
In-Reply-To: <20170214060156.73B32639AEDF@rock.dv.isc.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_A009120F-ADFE-49CB-9EC9-C58EAFC1E7A2_="
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Qa4kjGLb17YzOc_7g7OjukqsAs>
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:12:38 -0000

On 13 Feb 2017, at 22:01, Mark Andrews wrote:

> I gave up trying to convince behave that the DNS64 DNSSEC processing
> was insane.  [...]
>
> I also gave up trying to get 5.9. "Always Set the CD Bit on Queries"
> removed from the draft for RFC 6840.  [...]
>
> Should I have raise these again at IETF last call?

I would hope that you would have appealed to the chair at the time of 
the chair declaring the document ready for Last Call, and if that failed 
appealed to the AD. And it should have gone to Last Call with a note in 
the shepherd writeup indicating that a participant identified what he 
thought were two essential objections, and the reasoning for why the WG 
still felt that the outcome was reasonable. If that all happened, then 
no, you shouldn't bring it up at Last Call, except perhaps to identify 
the issue to others with expertise in the area who weren't part of the 
discussion and who might be able to better explain why these were 
"WG-running-off-the-cliff" issues and not 
"reasonable-engineering-tradeoffs". But you had better say *that*, not 
simply rehash the issue. Last Call should be about "something went wrong 
in the judgement of consensus", not "I prefer a different outcome".

Now, if Last Call was the first time that you noticed the issue, that 
would suck, but then it is reasonable to bring it up.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478