IETF Logo Mail Archive

Re: [Teep] IETF 101 agenda requests

"faibish, sorin" <Faibish.Sorin@dell.com> Mon, 26 March 2018 23:12 UTC

Return-Path: <Faibish.Sorin@dell.com>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ABDB1277BB; Mon, 26 Mar 2018 16:12:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=pSLQcFEs; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=NQQCdouj
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 84HDipzv2Z19; Mon, 26 Mar 2018 16:12:50 -0700 (PDT)
Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (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 B9A11126C25; Mon, 26 Mar 2018 16:12:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1522105399; x=1553641399; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=obxj3eWG3oT9+MnzYWG7O6rBDLkMjfP25G7qrwJsYlo=; b=pSLQcFEss05ViYIf8gFqGyfQRng8ka4rTXCQx00v+eUTDpl5T4yPrRVk 1eWRSzgcQU7bxPNFeyLYJm2KgEnzd9csjQna14UqnKVzn2jUs0nGwbv0t vUyzFJpt12SB+wOn8lh4oMU1azj/CJdpDDXRPuo9/cVBf30N6Yx7S/NEG M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2GUAABVfblah8mZ6ERdDgwBAQEBAQIBAQEBCAEBAQGCbyMEfg5wKAqYZIF0dRyUGj0LHg6EWQKDfSE4FAECAQEBAQEBAgECEAEBAQoLCQgoIwyCOCQBDkshCDIBAQEBAQEBAQEBAQEBAQEBAQEXAj0BEgIYAQEBBDoGOQELBAIBCBEEAQEBChQJBzIUCQgBAQQOBQgThHMBDq5ygneFTIIPAwWFPoEUDHqBVECBDIJTNIFBgVICA4Fdgy+CJJdCCAKFUIoPhjKEV4kThjwCBAIEBQIUgSUzgWAMCHCDEoIvgQUBCIJChROFBDpvjmOBFwEB
X-IPAS-Result: A2GUAABVfblah8mZ6ERdDgwBAQEBAQIBAQEBCAEBAQGCbyMEfg5wKAqYZIF0dRyUGj0LHg6EWQKDfSE4FAECAQEBAQEBAgECEAEBAQoLCQgoIwyCOCQBDkshCDIBAQEBAQEBAQEBAQEBAQEBAQEXAj0BEgIYAQEBBDoGOQELBAIBCBEEAQEBChQJBzIUCQgBAQQOBQgThHMBDq5ygneFTIIPAwWFPoEUDHqBVECBDIJTNIFBgVICA4Fdgy+CJJdCCAKFUIoPhjKEV4kThjwCBAIEBQIUgSUzgWAMCHCDEoIvgQUBCIJChROFBDpvjmOBFwEB
Received: from esa1.dell-outbound2.iphmx.com ([68.232.153.201]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Mar 2018 18:03:18 -0500
From: "faibish, sorin" <Faibish.Sorin@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa1.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Mar 2018 05:03:15 +0600
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd53.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id w2QNCjoM018876 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Mar 2018 19:12:48 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com w2QNCjoM018876
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1522105968; bh=93HR0XVgMc9W7QTH2FywOVQVRaM=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=NQQCdoujqOmJ7CL8QuXpTjkwJmZk5NqQsqn++ih5fEIZrMv79oXtzdDYWw6Ea/Eqe Xp6NOrwoZzxD4sWJa7Gkiy6hO2CxPZGtsXMjfX1j6VyLzJxrlrTprE+y47vgg5jwSj hvgTQEZMB8Wydo7GUNqQz1qbOdGHr7E/Hn/IxRvg=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd53.lss.emc.com w2QNCjoM018876
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd55.lss.emc.com (RSA Interceptor); Mon, 26 Mar 2018 19:12:37 -0400
Received: from MXHUB320.corp.emc.com (MXHUB320.corp.emc.com [10.146.3.98]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id w2QNCZ9B000357 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Mon, 26 Mar 2018 19:12:38 -0400
Received: from MX304CL01.corp.emc.com ([fe80::2d21:ebf8:dc15:2b07]) by MXHUB320.corp.emc.com ([10.146.3.98]) with mapi id 14.03.0382.000; Mon, 26 Mar 2018 19:12:37 -0400
To: Benjamin Kaduk <kaduk@mit.edu>
CC: Dave Thaler <dthaler@microsoft.com>, teep <teep@ietf.org>, "teep-chairs@ietf.org" <teep-chairs@ietf.org>
Thread-Topic: [Teep] IETF 101 agenda requests
Thread-Index: AdO9Xdcov18dMzNFTtSIcGlRK17eigEYdluQAEF0EYAApIpjUA==
Date: Mon, 26 Mar 2018 23:12:37 +0000
Message-ID: <2313358402DBCC4DB2F2DC03CB08BBFE0100C5FE@MX304CL01.corp.emc.com>
References: <MWHPR21MB078111616FCDCF87134B0FC0A3D70@MWHPR21MB0781.namprd21.prod.outlook.com> <2313358402DBCC4DB2F2DC03CB08BBFEFF050A@MX304CL01.corp.emc.com> <20180323123925.GD25919@kduck.kaduk.org>
In-Reply-To: <20180323123925.GD25919@kduck.kaduk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.252.59.25]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/_ywLW9JBLWd6v8__ROY3AxYtQbA>
Subject: Re: [Teep] IETF 101 agenda requests
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 23:12:53 -0000

We discussed the DDoS in Singapore and we had a presentation on the DDoS:
https://datatracker.ietf.org/meeting/100/materials/slides-100-saag-inter-domain-ddos-mitigations-potentials-challenges-and-solutions-min-suk-kang/

So, I would like to include this usecase as a target for the WG. I will write a draft related to this usecase. Thanks

./Sorin 

-----Original Message-----
From: Benjamin Kaduk [mailto:kaduk@mit.edu] 
Sent: Friday, March 23, 2018 8:39 AM
To: faibish, sorin <faibish_sorin@emc.com>
Cc: Dave Thaler <dthaler@microsoft.com>; teep <teep@ietf.org>; teep-chairs@ietf.org
Subject: Re: [Teep] IETF 101 agenda requests

Hi Sorin,

On Thu, Mar 22, 2018 at 09:26:22AM +0000, faibish, sorin wrote:
> New proposed usecase for TEEP WG.
> 
> Most recently the frequency and intensity of DDoS attacks from IoT devices increased with attacks almost every day. The reason of the proliferation of DDoS attacks from IoT devices is a result of the lower and maybe inexistent security protection of cheap IoT devices that have no security features implemented as this would increase the cost of such devices using any security HW. In the current charter of TEEP there sre 3 usecases and I would like to add the protectioin against DDoS of IoT as a new usecase:

On a quick read of the charter, I don't see how this topic would be in scope -- am I missing something that would allow it?

Thanks,

Ben

v2.23.0 | Report a Bug | By Email