Re: [Dots] WGLC on draft-ietf-dots-architecture-08

"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Mon, 03 December 2018 11:18 UTC

Return-Path: <TirumaleswarReddy_Konda@mcafee.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 D7736130E19 for <dots@ietfa.amsl.com>; Mon, 3 Dec 2018 03:18:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.761
X-Spam-Level:
X-Spam-Status: No, score=-5.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mcafee.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 fSxXv3Txa-UZ for <dots@ietfa.amsl.com>; Mon, 3 Dec 2018 03:18:06 -0800 (PST)
Received: from DNVWSMAILOUT1.mcafee.com (dnvwsmailout1.mcafee.com [161.69.31.173]) (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 64220130E4B for <dots@ietf.org>; Mon, 3 Dec 2018 03:18:05 -0800 (PST)
X-NAI-Header: Modified by McAfee Email Gateway (5500)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mcafee.com; s=s_mcafee; t=1543835903; h=From: To:Subject:Thread-Topic:Thread-Index:Date: Message-ID:References:In-Reply-To:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: dlp-product:dlp-version:dlp-reaction:authentication-results: x-originating-ip:x-ms-publictraffictype:x-microsoft-exchange-diagnostics: x-ms-exchange-antispam-srfa-diagnostics:x-ms-office365-filtering-correlation-id: x-microsoft-antispam:x-ms-traffictypediagnostic: x-microsoft-antispam-prvs:x-ms-exchange-senderadcheck: x-exchange-antispam-report-cfa-test:x-forefront-prvs: x-forefront-antispam-report:received-spf:x-microsoft-antispam-message-info: spamdiagnosticoutput:spamdiagnosticmetadata: Content-Type:Content-Transfer-Encoding:MIME-Version: X-MS-Exchange-CrossTenant-Network-Message-Id: X-MS-Exchange-CrossTenant-originalarrivaltime: X-MS-Exchange-CrossTenant-fromentityheader: X-MS-Exchange-CrossTenant-id:X-MS-Exchange-Transport-CrossTenantHeadersStamped: X-OriginatorOrg:X-NAI-Spam-Flag:X-NAI-Spam-Level: X-NAI-Spam-Threshold:X-NAI-Spam-Score:X-NAI-Spam-Version; bh=DT043OTYK1fN2K5cqFp0Hw4eC0T78vSi0XPhaB y5+Fc=; b=K8H3i01uw83OKUT6aR4YEj634XGMKzQL7ho8TYk8 GgQqsJzbYksKol4s0xGdoZAcRdBE115iUrl6ka4Q4+95s1eyDL ZFikoul50DLSt8Sg2/4TwaldN2MokpaIGYLjHWdDOATv+v/jeY SWOM8jih26Uw5t8CmTCwl1NlXz6J/vI=
Received: from DNVEXAPP1N04.corpzone.internalzone.com (unknown [10.44.48.88]) by DNVWSMAILOUT1.mcafee.com with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-SHA384) id 344d_85cc_ea336c02_ccd4_417d_8c5d_b037e44d4e35; Mon, 03 Dec 2018 05:18:22 -0600
Received: from DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 3 Dec 2018 04:17:54 -0700
Received: from DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) by DNVEXUSR1N08.corpzone.internalzone.com (10.44.48.81) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 3 Dec 2018 04:17:52 -0700
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEXAPP1N06.corpzone.internalzone.com (10.44.48.90) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Mon, 3 Dec 2018 04:17:52 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (10.44.176.242) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Mon, 3 Dec 2018 04:17:51 -0700
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB1860.namprd16.prod.outlook.com (10.172.29.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1382.18; Mon, 3 Dec 2018 11:17:51 +0000
Received: from BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::b8de:7bb:cfa3:22ee]) by BN6PR16MB1425.namprd16.prod.outlook.com ([fe80::b8de:7bb:cfa3:22ee%8]) with mapi id 15.20.1382.020; Mon, 3 Dec 2018 11:17:50 +0000
From: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Roman Danyliw <rdd@cert.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: WGLC on draft-ietf-dots-architecture-08
Thread-Index: AdSGnlgla3cLRB5MRLWQWFaJSQftBABEEW3wAAZceYAAB9nNYAAEkILwAB+EMpAACKXk4AACgplwAAhHgoAAg12NMAAJg9xQ
Date: Mon, 03 Dec 2018 11:17:50 +0000
Message-ID: <BN6PR16MB1425A44F8819DA7516AD0AB6EAAE0@BN6PR16MB1425.namprd16.prod.outlook.com>
References: <359EC4B99E040048A7131E0F4E113AFC0184C49169@marathon> <787AE7BB302AE849A7480A190F8B93302E04F649@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <BN6PR16MB1425AD85A67FFE5A0EA5A769EAD20@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E04F981@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <BN6PR16MB1425D2A6BED037A18098CF54EAD20@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E04FF7F@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <BN6PR16MB1425379772574B34E678406DEAD30@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E050207@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <DM5PR16MB1436848B4B3EC35B6EF67D9BEAD30@DM5PR16MB1436.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E050B73@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302E050B73@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
dlp-product: dlpe-windows
dlp-version: 11.1.0.61
dlp-reaction: no-action
authentication-results: spf=none (sender IP is ) smtp.mailfrom=TirumaleswarReddy_Konda@McAfee.com;
x-originating-ip: [103.245.47.20]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB1860; 6:H5KjNymiYLZiLgkl1jeLm7h6gL/WNvVmcopFbgyJAmQLdO62QPEMpfWHjVEfkhqvKGmgev0mHs2rkcdGpd+397xrUf8RYz3FW1QZHbLv5F5RzcMwhJc/2tsCRN3sBis3TE1vTLipa5O3yiCC2NQMz34Un1l6s6yCEufbxBMIZnWbQ7TrAnlArSIwcip/rh1QcPMj1AdiOQO4FngGwxOwHgI5ZzUhrcWcUKrNkdIXQE7o9tS6b6Paq7ldlESXZqA9UPDNU/1EfpAUCp6BhQObyvuyHauc3MaeHQ8ArlEIqNaVIX4bvTohUWc3EFNBMdLsioQaT0KO5WwRO7xB55kbSjRfppK8Cibae9Ur0/K9S/w3DD/MVuW7+S0f0cHY4ht/ktgL/W7lHEg/b8uyHnhurCwOW8qDVvhleDBNsicljWL8jV77Lu3qVXFkMFOLF+xA/fM8r/ZfMDbHo/wKR2HnIQ==; 5:Jfm7YMICCPJZLahs+DQiwx/qbT5ABbiR1ledL/6bczszS9CGgX55oKJujFIHb9loigXk8+u4XrYGAe4DuMGssEYRRLKTu+5/+Io8cgSqP1TsVe1W4HiK2DQxuw59xLokYgSMvuJad5EEhqD7ZMnfUi+PVHM2DX+M2HGTMrHzgPc=; 7:i2VE81XmXV1XtxRQEE30qWwPrJvwbJF50OcyDdG0ZeFr4PP4u47CXFn8eYan8JFyXbOyEQ2QlDUe6wIklR7dhLgboy4fSZ8MytkcvSho0NKvXjxWv9XnAeZqN2BKdcrseBnps87AZFUEUIUKjVLgKQ==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 8c2931a4-3616-494c-b6e6-08d65910f686
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB1860;
x-ms-traffictypediagnostic: BN6PR16MB1860:
x-microsoft-antispam-prvs: <BN6PR16MB186069BDB384D679D3EC31F7EAAE0@BN6PR16MB1860.namprd16.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231455)(999002)(944501493)(52105112)(10201501046)(3002001)(148016)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123560045)(20161123564045)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:BN6PR16MB1860; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB1860;
x-forefront-prvs: 08756AC3C8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(396003)(366004)(136003)(39860400002)(32952001)(189003)(199004)(55784004)(13464003)(53936002)(81166006)(81156014)(66066001)(316002)(53546011)(6506007)(229853002)(68736007)(11346002)(8936002)(478600001)(14454004)(5024004)(486006)(25786009)(14444005)(97736004)(966005)(80792005)(6306002)(110136005)(93886005)(446003)(2501003)(6246003)(9686003)(6116002)(71200400001)(105586002)(305945005)(74316002)(3846002)(102836004)(256004)(476003)(106356001)(71190400001)(7736002)(99286004)(7696005)(6436002)(186003)(76176011)(26005)(8676002)(55016002)(5660300001)(33656002)(72206003)(2906002)(86362001)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB1860; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: gEI3rM/37Xb0PieI9cAGBnof7g+ZbNZlcodPskDwOI0reCp7Zs6gpwNyMlL+EkbZ/eSRCKcoMyv4CJMnmV9C6rpRaFAcjKRC/qhVewrk8pUD6yZZA+sZo3nRbpzwye61NnvTLlQPTPp1EQOgMkIJaBjWhW0KZ5szyDnP+apMiedAaTAe4785W36bgnlDlaM5z/pYcD8yWMrMXi74Y+S9Pi4QNDBcXpd7TYnE/t15aCIM68pe1lJCwhGAIq24SPdjFbpBo5f8+7zyC4OdCMV3lphv8IbnlawfKm8dkf78+WLYgqnlC2TtukIzrFELiE3hDqpo1SonAIUgdERXbmCcRojRfyGbY/p89S2f/GmFPA0=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8c2931a4-3616-494c-b6e6-08d65910f686
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Dec 2018 11:17:50.8104 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB1860
X-OriginatorOrg: mcafee.com
X-NAI-Spam-Flag: NO
X-NAI-Spam-Level:
X-NAI-Spam-Threshold: 15
X-NAI-Spam-Score: 0.5
X-NAI-Spam-Version: 2.3.0.9418 : core <6430> : inlines <6975> : streams <1806047> : uri <2759444>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9zZCKV-_xLNHip4dr54SY59D0DQ>
Subject: Re: [Dots] WGLC on draft-ietf-dots-architecture-08
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: Mon, 03 Dec 2018 11:18:10 -0000

Thanks Med, update looks good; just one Nit
Redirected signaling is also applicable to DOTS data channel (replace "DOTS signal channel session" with "DOTS session").

-Tiru

> -----Original Message-----
> From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com>
> Sent: Monday, December 3, 2018 12:17 PM
> To: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com>;
> Roman Danyliw <rdd@cert.org>; dots@ietf.org
> Subject: RE: WGLC on draft-ietf-dots-architecture-08
> 
> 
> 
> Hi Tiru,
> 
> I updated the file to take into account your feedback:
> 
> Xml: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-
> dots-architecture-09.xml
> Diff: https://github.com/boucadair/IETF-Drafts-
> Reviews/blob/master/wdiff%20draft-ietf-dots-architecture-09.txt%20draft-ietf-
> dots-architecture-09.pdf
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Dots [mailto:dots-bounces@ietf.org] De la part de Konda,
> > Tirumaleswar Reddy Envoyé : vendredi 30 novembre 2018 17:14 À :
> > BOUCADAIR Mohamed TGI/OLN; Roman Danyliw; dots@ietf.org Objet : Re:
> > [Dots] WGLC on draft-ietf-dots-architecture-08
> >
> > Hi Med,
> >
> > I don't fully agree with some of the updates.  I propose the following
> > changes:
> >
> > [1] Replace " A DOTS session can be a DOTS data channel session or a
> > DOTS signal channel session" with "A DOTS session can be a DOTS data
> > channel session or a DOTS signal channel session or both."
> > [2] I thought we agreed to say the following:
> > A DOTS signal channel session is associated with a single transport
> > connection (TCP or UDP session) and an ephemeral security association
> > (e.g. a TLS or DTLS session). Similarly,  a DOTS data channel session
> > is associated with a single TCP connection and an ephemeral TLS security
> association.
> > [3] Direct and recursive signaling is applicable to both DOTS signal
> > and data channel sessions, replace "DOTS signal channel session" with "DOTS
> session".
> > [4] In Section 3.1.2, replace "session" with "DOTS session"
> > [5] Remove the following line:
> > "These sessions may belong to the same or distinct DOTS channels
> > (signal or data).
> >
> > Cheers,
> > -Tiru
> >
> > > -----Original Message-----
> > > From: mohamed.boucadair@orange.com
> <mohamed.boucadair@orange.com>
> > > Sent: Friday, November 30, 2018 5:40 PM
> > > To: Konda, Tirumaleswar Reddy
> <TirumaleswarReddy_Konda@McAfee.com>;
> > > Roman Danyliw <rdd@cert.org>; dots@ietf.org
> > > Subject: RE: WGLC on draft-ietf-dots-architecture-08
> > >
> > > 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.
> > >
> > > Re-,
> > >
> > > OK. Thanks.
> > >
> > > FWIW, I also made on my side some changes that I'd like to see made
> > > to fix
> > the
> > > issues we discussed so far:
> > >
> > > Xml:
> > > https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-
> > ietf-
> > > dots-architecture-09.xml
> > > Diff: https://github.com/boucadair/IETF-Drafts-
> > > Reviews/blob/master/wdiff%20draft-ietf-dots-architecture-09.txt%20dr
> > > aft-
> > ietf-
> > > dots-architecture-09.pdf
> > >
> > > Feel free to reuse the modified version.
> > >
> > > (Removing parts that were agreed and focusing on the last pending
> > > one)
> > >
> > > > > > >
> > > > > > > > DOTS data channel draft is not using the term "DOTS data
> > > > > > > > channel session", we can fix the signal channel draft to
> > > > > > > > use "DOTS data channel" instead of "DOTS data channel session".
> > > > > > > >
> > > > > > >
> > > > > > > [Med] May be. BTW, this part of the text:
> > > > > > >
> > > > > > > " Conversely, a
> > > > > > >    DOTS session cannot exist without an established signal
> > > > > > > channel
> > "
> > > > > > >
> > > > > > > is conflicting with this one:
> > > > > > >
> > > > > > > "
> > > > > > > To allow for DOTS
> > > > > > >    service flexibility, neither the order of contact nor the time
> > > > > > >    interval between channel creations is specified.  A DOTS
> > > > > > > client
> > MAY
> > > > > > >    establish signal channel first, and then data channel, or
> > > > > > > vice
> > > > versa."
> > > > >
> > > > > [Med] This one is still pending.
> > > >
> > > > The above line looks clear to me, what is the confusion ?
> > > >
> > >
> > > [Med] The problem is not with the last line with this one:
> > >
> > > "DOTS session cannot exist without an established signal channel"
> > >
> > > Which means that dots signal channel session is a pre-requisite for
> > > DOTS
> > data
> > > channel. This is conflict with the other excerpt I cited.
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots