Re: [Dots] FW: [core] 🔔 WG adoption of draft-boucadair-core-hop-limit

"Jon Shallow" <supjps-ietf@jpshallow.com> Tue, 11 September 2018 11:02 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 625AB130E6E; Tue, 11 Sep 2018 04:02:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 ry8gZz5XZ2vr; Tue, 11 Sep 2018 04:02:34 -0700 (PDT)
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 736FE130DFE; Tue, 11 Sep 2018 04:02:34 -0700 (PDT)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.90_1) (envelope-from <jon.shallow@jpshallow.com>) id 1fzgRE-0006TF-B2; Tue, 11 Sep 2018 12:02:32 +0100
From: "Jon Shallow" <supjps-ietf@jpshallow.com>
To: <core@ietf.org>, "'Konda, Tirumaleswar Reddy'" <TirumaleswarReddy_Konda@mcafee.com>, <dots@ietf.org>
References: <E0995B43-F895-4EB3-B26D-12F85EB2FF39@tzi.org> <BN6PR16MB142514B1FAEC3B7709E55819EA040@BN6PR16MB1425.namprd16.prod.outlook.com>
In-Reply-To: <BN6PR16MB142514B1FAEC3B7709E55819EA040@BN6PR16MB1425.namprd16.prod.outlook.com>
Date: Tue, 11 Sep 2018 12:02:33 +0100
Message-ID: <039901d449be$f0b9cf70$d22d6e50$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQK1Oh2mxC0bxkfFsbamK+CvdY52jwHrXoHYoxmtKxA=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/T3RbNPcayXoDw9VBdq84o1w6VSg>
Subject: Re: [Dots] =?utf-8?b?Rlc6IFtjb3JlXSDwn5SUIFdHIGFkb3B0aW9uIG9mIGRy?= =?utf-8?q?aft-boucadair-core-hop-limit?=
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: Tue, 11 Sep 2018 11:02:36 -0000

Hi CoRE WG,

I have read the draft and support it.
I do not see any issues with it being a WG document.

Regards

Jon

-----Original Message-----
From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of Konda, Tirumaleswar Reddy
Sent: 11 September 2018 06:57
To: dots@ietf.org
Subject: [Dots] FW: [core] 🔔 WG adoption of draft-boucadair-core-hop-limit

Hi all,

Please review https://tools.ietf.org/html/draft-boucadair-core-hop-limit-00 and respond to the WG adoption call in CoRE WG. 
DOTS signal channel is using the Hop-Limit Option defined in this draft.

Cheers,
-Tiru

-----Original Message-----
From: core <core-bounces@ietf.org> On Behalf Of Carsten Bormann
Sent: Tuesday, September 11, 2018 1:25 AM
To: Core <core@ietf.org>
Subject: [core] 🔔 WG adoption of draft-boucadair-core-hop-limit

This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

It seems we have converged at draft-boucadair-core-hop-limit as the draft providing the hop limit function needed by DOTS, but we haven’t done the formal WG adoption yet.

This is a formal call for adoption of this draft as a WG document of the CoRE WG.
If you have read the draft and support adopting it, please say so.
If you see a problem with adopting it as a WG document, please tell us.
For both, remember that WG adoption does not mean that we already have consensus on all the details, just that this is the right working document to address the issue (and that we should address the issue in the first place).
Please do mention any issues that you already know; these also can be brought up in Wednesday’s virtual interim Webex call.

This formal WG adoption call runs until the end of September 17th.
(Given the state of the discussion, we might then have a Working Group last call of an updated document right next.)

Grüße, Carsten

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