IETF Logo Mail Archive

Re: [DNSOP] Seeking discussion of draft-ietf-dnsop-cookies-01

神明達哉 <jinmei@wide.ad.jp> Wed, 06 May 2015 18:19 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 69EA91A88F1 for <dnsop@ietfa.amsl.com>; Wed, 6 May 2015 11:19:09 -0700 (PDT)
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 vW3LpPjXW48W for <dnsop@ietfa.amsl.com>; Wed, 6 May 2015 11:19:08 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (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 1A5F81A8863 for <dnsop@ietf.org>; Wed, 6 May 2015 11:19:08 -0700 (PDT)
Received: by igbyr2 with SMTP id yr2so138709175igb.0 for <dnsop@ietf.org>; Wed, 06 May 2015 11:19:07 -0700 (PDT)
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=/iTf7R1nIZLHdLvMcGjTIkY9dN95tKm4X0Io7MZljD4=; b=CEJ73o/R5LM9PqL1G2HqVOPrKwbwbA2LZG+quK8cVzbT/OLNf21/buRXLH+3JQ0W/z vWpSvJeHsU+Pu0wVwP940MOSOTkua6DoMJYFghQHePJoEyoyrA23AmFCrOBwWhguVcV5 kLMYBCaIMxwogwblgdYlGepP7AidRniD+xBUlU7ZXaDEtjUznguYp1rlnfZD0/4Gvqy/ pfGZdB13y7uk4j0plZVOA/ytoqWqh2GBz5N81wuHk77A1K98L/+eL4ZddSE5RglUxaPG spfGr6f9albuVwY5op1WQpBiQ+cE78Jt8sRpzRZHJVTzRG6zJNvSOGmlO4mohgFZ/rkg WlHA==
MIME-Version: 1.0
X-Received: by 10.43.68.133 with SMTP id xy5mr3830865icb.72.1430936347639; Wed, 06 May 2015 11:19:07 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.50.80 with HTTP; Wed, 6 May 2015 11:19:07 -0700 (PDT)
In-Reply-To: <20150501232130.GA13049@isc.org>
References: <20150501232130.GA13049@isc.org>
Date: Wed, 06 May 2015 11:19:07 -0700
X-Google-Sender-Auth: KTNpHN2oapROulfWnVPLPT-EzzI
Message-ID: <CAJE_bqe2FhYgCrOzh4ZRZYOO=YoJC3_QOoMwq1KLPbc30Y==mw@mail.gmail.com>
From: 神明達哉 <jinmei@wide.ad.jp>
To: Evan Hunt <each@isc.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/W8Sm1i72X9M8Rr2ox2_clXZ0aFI>
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] Seeking discussion of draft-ietf-dnsop-cookies-01
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: Wed, 06 May 2015 18:19:09 -0000

At Fri, 1 May 2015 23:21:30 +0000,
Evan Hunt <each@isc.org> wrote:

> The chief difference between the two is the presence of an error code field
> in Eastlake cookies; Andrews found it redundant/unnecessary (as discussed
> in https://www.ietf.org/mail-archive/web/dnsop/current/msg13984.html).
> The hope was that including both mechanisms in the draft would lead to
> a working group discussion about whether the error code is, in fact,
> necessary or desirable; unfortunately, not much discussion has happened
> yet.

Can someone explain why we'd need the separate error codes based on
the position of supporting them (i.e, not to persuade others on
dropping them)?  msg13984.html was basically written to argue against
them, so it could potentially and unintentionally be biased.  I'll try
to find any such explanation myself, but if someone already knows it
better can do that, it would also help.

--
JINMEI, Tatuya

v2.23.0 | Report a Bug | By Email