Re: [Dots] Call for adoption on draft-boucadair-dots-server-discovery

Dan Wing <danwing@gmail.com> Thu, 13 December 2018 03:22 UTC

Return-Path: <danwing@gmail.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8276A128CF2 for <dots@ietfa.amsl.com>; Wed, 12 Dec 2018 19:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dG5bhjdfx2hY for <dots@ietfa.amsl.com>; Wed, 12 Dec 2018 19:22:48 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 9A76C124D68 for <dots@ietf.org>; Wed, 12 Dec 2018 19:22:48 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id i12so350390pfo.7 for <dots@ietf.org>; Wed, 12 Dec 2018 19:22:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rfBa6S2NBf8EvteYOklFAMtj1XWZ8pZgHrttiyTxRls=; b=okzyu2XmYy0tV9Eeyvy6JHRjUdHK4oQMFW+9YB8LbOLcCEBb8eNlPUO1cHlQUVBEop TEuBnldpCYCTjWdDO+0LpZ0uEIz4sBUwz3shVa1PIGchuXe8yNUtfSUjqupEMPd0oIyh WezOfoyb6/tFOTKfnPjij9RN4ZwHPawAoRKbE1qttbzvo4r4/9ca+F1J9Pb3UdCTsspC oCbkiosgGdHwiTiqwDqujGoGif3CD1jgmWTDP/G28bGGXR2QFngN4SY86kBBtZEWscnW gN3Q3XGieKYPWvcnlhiBM3mCHmByPO7aYsJwLxvwKBH32qkIwHrpbfXa6FSdYEcE542L l9Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=rfBa6S2NBf8EvteYOklFAMtj1XWZ8pZgHrttiyTxRls=; b=m3VEHn04bEnIGgEMraANyJ4sjw5FG5QrmzUWj6nNdCdpS+keNegIA4r4QtAnW2hDuP 3PXsPW+A1rwI6/QE7VT1uzKKAtIoV2C8XGKFDBo643jswjNLCjUhpCHLS2+2rPrUQylw /GjJFacP7nmS/yOeXk5YSPxHJOhNjGpYsLPZihFtnioul/gEhaWTU73NlpttKZ3Itb+V bTAQrsWe1uKWc88UbpcITalLbm9ST4C72rVPPoWRSzTO4qtl95c8e+oDu0U8idq7qeo+ 5DnLsyJKbDtveCxTnLmkVlOU68caianzkyiuZEwYZFxK7h8trhcifh6oX3xPHJAXnHjx po/w==
X-Gm-Message-State: AA+aEWZP8692bI3kbE3STpTmZD6y+uJUcs42boL4Hz8+j2o3swfDAyqO LyGGdxBdulPAeNbuEDs5cTow8Lh4
X-Google-Smtp-Source: AFSGD/UjdDQ9wPx8L73wwwFbB4CyyvLAxm4wZl5hJ3CRqqbaEpfeEu9g2i3X9PFDx4qT37sFx7+trQ==
X-Received: by 2002:a62:3888:: with SMTP id f130mr22102934pfa.132.1544671367992; Wed, 12 Dec 2018 19:22:47 -0800 (PST)
Received: from [192.168.86.180] ([75.111.77.103]) by smtp.gmail.com with ESMTPSA id d202sm597464pfd.58.2018.12.12.19.22.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Dec 2018 19:22:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Dan Wing <danwing@gmail.com>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC0184C52F1B@marathon>
Date: Wed, 12 Dec 2018 19:22:46 -0800
Cc: "dots@ietf.org" <dots@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C0138CB-2B3C-4A9D-A013-2232879A72AD@gmail.com>
References: <359EC4B99E040048A7131E0F4E113AFC0184C52F1B@marathon>
To: Roman Danyliw <rdd@cert.org>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/KcZwwNO2af7dItqtaqvhocx7ppg>
Subject: Re: [Dots] Call for adoption on draft-boucadair-dots-server-discovery
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2018 03:22:51 -0000

I support adoption of this draft.  

However, I would really encourage the working group to analyze if all 4 discovery methods are really necessary.  4 mechanisms causes a bifurcation of products.  It complicates the features of a DOTS gateway, and raises questions such as "is quality implementation of a DOTS gateway expected to interoperate amongst the 4 DOTS discovery mechanisms."  Such interoperation becomes necessary when, say, some devices won't support DHCPv6 (Android) but an ISP only supports DHCPv4 & DHCPv6 DOTS discovery, for example.  There are other examples of incompatible discovery and how a vendor or an open-source DOTS gateway might try to overcome such issues with a Discovery Interoperability Feature ...

-d


> On Nov 30, 2018, at 2:21 PM, Roman Danyliw <rdd@cert.org> wrote:
> 
> Hello!
> 
> This is the start of a two week call for input on the WG adoption of the document:
> 
> draft-boucadair-dots-server-discovery
> https://tools.ietf.org/html/draft-boucadair-dots-server-discovery-05
> 
> The document has been presented and discussed at IETF 103, IETF 100 and IETF 99;  and revisions have been made based on WG feedback.  Discussion of adoption of this draft was previously deferred pending submission of the signal draft for publication (which occurred in September 2018).
> 
> At the IETF 103 meeting, there were not many participants who had read the draft.
> 
> Please provide feedback to the list/chairs if you believe that this document should be adopted as a WG document.  The adoption call will end on December 14 2018.
> 
> Regards,
> Roman and Frank
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots