Re: [DNSOP] CLIENT-SUBNET bis appetite?

Warren Kumari <warren@kumari.net> Thu, 14 December 2017 18:10 UTC

Return-Path: <warren@kumari.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0002E129413 for <dnsop@ietfa.amsl.com>; Thu, 14 Dec 2017 10:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 5hoSrngYYl_f for <dnsop@ietfa.amsl.com>; Thu, 14 Dec 2017 10:10:12 -0800 (PST)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 6003012704A for <dnsop@ietf.org>; Thu, 14 Dec 2017 10:10:12 -0800 (PST)
Received: by mail-wr0-x233.google.com with SMTP id g53so5933702wra.2 for <dnsop@ietf.org>; Thu, 14 Dec 2017 10:10:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RuscjWVGd67xS0MAh10N67skU6Am/n1hYeQLXn5WqZo=; b=WDPZLF5BFi5lyHxWFXiF7X4pD9zXTMIoQoV1jgXKzhFJbQbyQaI3C/EzUnK6kzbOHE UYH5qbng+PixmlQxw4X3rkIUXowB/fG47SkSqObkxzAZ0uwwP+qQqOxDznRJQ1kXMnGd IYoY00rq5fdxenRwriXuWkwEQ63lFP3ts/xht4TH5BjjKeSQyQiE4aCF6qQfl0HBoOnq qZQY2gJ738/DnzJarhtL3bTus21IMHgaoux4Tl6wembtnlC6N8w++Kq4SLvweV2iUY8Y teTk2ALVg6hk0tAXhS7vjNZdd1RKxwo3U055M4VzhBEBOckI8vmWbaYl1tws3BmvIppq 21Pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RuscjWVGd67xS0MAh10N67skU6Am/n1hYeQLXn5WqZo=; b=IifErP3lfx5Myp4FdDCoRLDPZuoLpI5QhXg+cvaXi2lcuEzKpHuCXK5gXFznJFelLK rhEGzHCwdTWeO5r5JRhNwOUqb6t2vaJSW/mCUl3wAHbdFtNSDSyfvR2KOHyT9NHUw+UH 8IFiQZ8EqMHJH2SlYUQCPkNhEFldf6Eyk1Vx2qspbhprSpzR9Wy2tJ44DW9OTbQzwb2S GNFPB9TEFdHxpukbec1jRMHJ+27quJ7FZ0DsrgUjmR8wyvipu+R8/TCNS8TawmXyx05l ohL7GP7j/lXVZN7dU8f+6n2zu91qKToZttBXLVPTeTvunpSDdUKcVotY2mZiPZrCrheH IMjA==
X-Gm-Message-State: AKGB3mLp4u0hTIRGAGUZlDlC83wHsEp5PO/whwUA6qB9GETfBN+AuFlr JxpV6k6XwTd+LndAB+ozxqtBatkY0Vgr/0HL0nlWOgZW
X-Google-Smtp-Source: ACJfBovSi+R4n+zwB+nigmD02Fr2lrsf3rc3QcRV1EYrDSx38st8LtuzM50+ulHZ1LgW7/hehx5m1M5Kd2lY42g76n4=
X-Received: by 10.223.135.243 with SMTP id c48mr6398351wrc.140.1513275010672; Thu, 14 Dec 2017 10:10:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.160.149 with HTTP; Thu, 14 Dec 2017 10:09:30 -0800 (PST)
In-Reply-To: <20171214173913.GA18100@jurassic.lan.banu.com>
References: <20171214173913.GA18100@jurassic.lan.banu.com>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 14 Dec 2017 13:09:30 -0500
Message-ID: <CAHw9_iJ-JiAbK+jdDB7vGKAO7rWvymU7fUAKNerWn-k5X5pQbQ@mail.gmail.com>
To: Mukund Sivaraman <muks@isc.org>
Cc: dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hc8nSOmtbGJT0HUzyO7v874EboE>
Subject: Re: [DNSOP] CLIENT-SUBNET bis appetite?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 14 Dec 2017 18:10:15 -0000

On Thu, Dec 14, 2017 at 12:39 PM, Mukund Sivaraman <muks@isc.org> wrote:
> Any appetite for it? Don't throw things at me.. I ask because the
> current thing is slowly getting more widely deployed and there are
> design issues that can do with a ECS2 that breaks from ECS1 protocol. I
> ask because I'm once again having to deal with myriad implementation
> cases and dislike it.
>

<no hats, other than author on the original doc.>
As I'm sure you know / remember, getting the first version though was
quite a slog. I suspect that, seeing as there seems to be good support
for the initial version, getting a new one done will be much simpler,
but the obvious question is:
How would ECS2 differ, and how would it interact with ECS1 / backward
compatibility?

W

</no hats>
>                 Mukund
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf