IETF Logo Mail Archive

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

"Jon Shallow" <supjps-ietf@jpshallow.com> Wed, 05 December 2018 09:41 UTC

Return-Path: <supjps-ietf@jpshallow.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 E6D701276D0 for <dots@ietfa.amsl.com>; Wed, 5 Dec 2018 01:41:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 XCuQ9Hs2Gipr for <dots@ietfa.amsl.com>; Wed, 5 Dec 2018 01:41:07 -0800 (PST)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B6C11286E7 for <dots@ietf.org>; Wed, 5 Dec 2018 01:41:07 -0800 (PST)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.91) (envelope-from <jon.shallow@jpshallow.com>) id 1gUTg0-0000U7-0p; Wed, 05 Dec 2018 09:41:04 +0000
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: mohamed.boucadair@orange.com, 'Roman Danyliw' <rdd@cert.org>, dots@ietf.org
References: <359EC4B99E040048A7131E0F4E113AFC0184C52FEF@marathon> <787AE7BB302AE849A7480A190F8B93302E050BC5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302E050BC5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Date: Wed, 05 Dec 2018 09:41:03 -0000
Message-ID: <05f601d48c7e$a50fa1a0$ef2ee4e0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDebrujFrO9EYLWb4+fu0sqHcDfLQIy4aK+p0gqvvA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/3FX7t7npjUwKL-swdVh4Tkn3P3Y>
Subject: Re: [Dots] Call for adoption on draft-boucadair-dots-multihoming
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: Wed, 05 Dec 2018 09:41:09 -0000

Hi Med

To help the reader with the first reference to PI/PA

s/Provider-Independent (PI) vs. Provider-Aggregatable (PA)/
Provider-Independent (PI) vs. Provider-Aggregatable (PA) IP addresses/

A typo

s/getaway/gateway/

Not clear

s/ DOTS clients, these later MUST contact all DOTS gateways/DOTS clients,
these MUST contact all DOTS gateways/

Otherwise, it makes sense to me.

Regards

Jon

-----Original Message-----
From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of
mohamed.boucadair@orange.com
Sent: 03 December 2018 06:53
To: Roman Danyliw; dots@ietf.org
Cc: draft-boucadair-dots-multihoming@ietf.org
Subject: Re: [Dots] Call for adoption on draft-boucadair-dots-multihoming

Re-,

I support this draft.

FWIW, I don't have any IPR related to this I-D.

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Roman Danyliw
> Envoyé : vendredi 30 novembre 2018 23:31
> À : dots@ietf.org
> Objet : [Dots] Call for adoption on draft-boucadair-dots-multihoming
> 
> Hello!
> 
> This is the start of a two week call for input on the WG adoption of the
> document:
> 
> draft-boucadair-dots-multihoming
> https://tools.ietf.org/html/draft-boucadair-dots-multihoming-04
> 
> The document has been presented and discussed at IETF 103, IETF 100 and
IETF
> 99;  and revisions have been made based on WG feedback.  This document was
> created and deferred in the interest of simplifying the requirements and
> architecture drafts now getting ready for publication.
> 
> 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

_______________________________________________
Dots mailing list
Dots@ietf.org
https://www.ietf.org/mailman/listinfo/dots

v2.23.0 | Report a Bug | By Email