Re: [Dots] WGLC on draft-ietf-dots-architecture-08
"Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com> Tue, 04 December 2018 13:47 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 DEA71130DD5 for <dots@ietfa.amsl.com>; Tue, 4 Dec 2018 05:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.76
X-Spam-Level:
X-Spam-Status: No, score=-5.76 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, URIBL_BLOCKED=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 0w3IPpF6kPK6 for <dots@ietfa.amsl.com>; Tue, 4 Dec 2018 05:47:26 -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 00F2E126DBF for <dots@ietf.org>; Tue, 4 Dec 2018 05:47:25 -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=1543931263; 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=wO+TM35MKKOAHhSfUaZBmHa4sxHBbi/sgjHsjI irsag=; b=BHKcwAtGk8pC2ggun9CT0JizQDXq/xNK7SvE612g S4sGMH+zAmXS1tKcdf6tXzFm4TsPV+Td653fqRmSRkOhKQ6Vda tvb+OzVE0z6R8xCmc1BktXfviR8/UWodujDU5xRcYwfBELs6Zk eLk3w9wRScTzbMCY7YGFlEAFpLpGvrc=
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 7900_e009_f77adc65_731a_4672_ad1d_ecffdde604b2; Tue, 04 Dec 2018 07:47:43 -0600
Received: from DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 4 Dec 2018 06:47:03 -0700
Received: from DNVEX10N01.corpzone.internalzone.com (10.44.82.192) by DNVEXAPP1N04.corpzone.internalzone.com (10.44.48.88) with Microsoft SMTP Server (TLS) id 15.0.1347.2 via Frontend Transport; Tue, 4 Dec 2018 06:47:03 -0700
Received: from DNVO365EDGE2.corpzone.internalzone.com (10.44.176.74) by DNVEX10N01.corpzone.internalzone.com (10.44.82.192) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 4 Dec 2018 06:47:03 -0700
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (10.44.176.241) by edge.mcafee.com (10.44.176.74) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 4 Dec 2018 06:47:01 -0700
Received: from BN6PR16MB1425.namprd16.prod.outlook.com (10.172.207.19) by BN6PR16MB0100.namprd16.prod.outlook.com (10.172.112.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1382.21; Tue, 4 Dec 2018 13:46:59 +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.023; Tue, 4 Dec 2018 13:46:59 +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+EMpAACKXk4AACgplwAAhHgoAAg12NMAAJg9xQAAG5H4AABQ7dgAAtle+QAAM21uA=
Date: Tue, 04 Dec 2018 13:46:59 +0000
Message-ID: <BN6PR16MB1425B397EE3D957CAB366193EAAF0@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> <BN6PR16MB1425A44F8819DA7516AD0AB6EAAE0@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E050F35@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <BN6PR16MB14251466063C92F20ADF9D96EAAE0@BN6PR16MB1425.namprd16.prod.outlook.com> <787AE7BB302AE849A7480A190F8B93302E051A1F@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302E051A1F@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: [122.167.172.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR16MB0100; 6:9UwTVc/MSmi+jQkImKBSU1KhbRWPs8xkgwV66GXzNDrpXhFOPZnICQcnBTN7Ng+0UT9g8LpJ8N0f0QXT+W8jevxd+JoDp2Yd3jYiSe58T2pNEYloIiK6Qa2vtsAEFjXPHZGvh0X3p7o7qSNgc7U5qtFZkleWAI1wbJgbH8et1dRZTUUH8u1NBu4/C/ZXq/Mp0koNcGV2u/jlUToR76ZL9OdH3GXrs0oBYiN44AOhKZo6H+3WmBnzWcA+T8XPpUunT3OkNKWn5AnkBJOMoNTRrP6Dziykk1LVclh3Ec3M6s0PQRjop5scnq7vqs3Bng2bCE2J2coX2n+wdlcrQTfCMD75HT7vyc8RlpiiHt0se1uL2xqsKMrLzudB3ptO27y7hTcC1GJ020ogq67F7eUExZlFyv6lK625TnRodk2a04vHv9Qo7DLqIiHAcs7IbWduZoC6kTp6j2i/H1+BQZK9uw==; 5:3diFUyJeu4IpWGVnY67vE5nwmkJoe6O9rrs7ovmhx7iiuTJEsdIw9jX2s/lsQVOUeb7wQUWxPQVIvd8hJuTdDNnHbbtaYfZ+NsmR73xCyh6Tmc23Cuwy6nePhWgE6sz4OFdkjZX6JjpwG6FOt/cpPda1lcWhs2Wyw6WEypdlOWI=; 7:4wpmPR469CT0NQ8yiyGae3pd/vQosPFo0itoT/P4+LKW6CBYAUSYDCwRbPgVYE5lNjhq9yzOMYFiKWJ1gSpsKiqdEh2pJm+O1iSncDlLtzyV5eMy7QU2bNs1Qhzma9/b+tJ5KageKe/hNp31xlmu/A==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 1d0f1a0c-15fb-4a3b-f2fd-08d659eef680
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:BN6PR16MB0100;
x-ms-traffictypediagnostic: BN6PR16MB0100:
x-microsoft-antispam-prvs: <BN6PR16MB0100C68134DC6B709163282DEAAF0@BN6PR16MB0100.namprd16.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(3231455)(999002)(944501493)(52105112)(93006095)(93001095)(148016)(149066)(150057)(6041310)(20161123558120)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(201708071742011)(7699051)(76991095); SRVR:BN6PR16MB0100; BCL:0; PCL:0; RULEID:; SRVR:BN6PR16MB0100;
x-forefront-prvs: 0876988AF0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(366004)(136003)(396003)(39850400004)(199004)(189003)(32952001)(55784004)(13464003)(53936002)(106356001)(110136005)(3846002)(6116002)(186003)(6306002)(9686003)(105586002)(2906002)(6436002)(256004)(229853002)(14444005)(5024004)(33656002)(316002)(66066001)(26005)(93886005)(11346002)(14454004)(74316002)(8676002)(66574009)(72206003)(478600001)(99286004)(71200400001)(446003)(102836004)(8936002)(25786009)(78486014)(71190400001)(476003)(6246003)(81156014)(305945005)(486006)(5660300001)(7736002)(80792005)(97736004)(86362001)(7696005)(53546011)(55016002)(2501003)(68736007)(6506007)(966005)(76176011)(81166006)(85282002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR16MB0100; H:BN6PR16MB1425.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: McAfee.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: eYX87GpwbM0PSJfCjZpqk8xbe82qcOoQjF9AP7+UMKs/ZqgxBuCbJGezFrH3rottfZlqwp4IYTJqMPWk2sNHejO5Nhbn1Tr1L0G+r5/AB2lrM39dqsN1IaWtkgjvhPYtr3vSOtboEWC/fgx12KFLkAhQzLnv320h4byni9VMh747DWvo/X0T5WO3fDjYaQS1Mu+dSksZrEPHNjf4fu5zwbnENWfgUUX7EWeJLiKKVkCpx13kj4+3VwmtBG7uc4oaLdP9tTxBDnvlmT6R7H+KNz2CRG4pt/VoI71hthqD8KI6QwDIx9KAnBgHway/j6+p2BQEBpfzHKox+0hLaBzvekBYxdvQLSpafNsTHS/cfL8=
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: 1d0f1a0c-15fb-4a3b-f2fd-08d659eef680
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2018 13:46:59.1677 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4943e38c-6dd4-428c-886d-24932bc2d5de
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR16MB0100
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 <6432> : inlines <6975> : streams <1806153> : uri <2759991>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/h55JeNTir7ycoh0wt4zm1LUz2Sc>
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: Tue, 04 Dec 2018 13:47:29 -0000
> -----Original Message----- > From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com> > Sent: Tuesday, December 4, 2018 5:46 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. > > Tiru, > > We don't have the same constraints for the data channel compared to those of > the signal channel. As such, when a problem is encountered to contact a DOTS > server, another server may be used following some local logic (e.g., sequential > through a list). > > I suggest we keep the architecture aligned with the requirements agreed so far > by the WG: that is, redirect signaling is only a requirements for the signal > channel. I don't see a strong reason to disagree. -Tiru > > Thank you. > > Cheers, > Med > > > -----Message d'origine----- > > De : Dots [mailto:dots-bounces@ietf.org] De la part de Konda, > > Tirumaleswar Reddy Envoyé : lundi 3 décembre 2018 15:39 À : BOUCADAIR > > Mohamed TGI/OLN; Roman Danyliw; dots@ietf.org Objet : Re: [Dots] WGLC > > on draft-ietf-dots-architecture-08 > > > > > -----Original Message----- > > > From: mohamed.boucadair@orange.com > <mohamed.boucadair@orange.com> > > > Sent: Monday, December 3, 2018 5:50 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. > > > > > > As per redirected signaling, the WG has only this requirement for > > > the > > signal > > > channel (SIG-005). > > > > SIG-005 is explicitly discussing redirected signaling because of the > > attack condition. > > I don't see a reason why redirect signaling is not applicable to DOTS > > data channel to increase the DOTS server operational flexibility and > > scalability. > > > > -Tiru > > > > > > > > Cheers, > > > Med > > > > > > > -----Message d'origine----- > > > > De : Dots [mailto:dots-bounces@ietf.org] De la part de Konda, > > > > Tirumaleswar Reddy Envoyé : lundi 3 décembre 2018 12:18 À : > > > > BOUCADAIR Mohamed TGI/OLN; Roman Danyliw; dots@ietf.org Objet : > > > > Re: [Dots] WGLC on draft-ietf-dots-architecture-08 > > > > > > > > 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/dra > > > > > ft- > > > > 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 > > > > > > > > > > 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 > > > > > > > /dra > > > > > > > ft- > > > > > > 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 > > > > _______________________________________________ > > > > 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
- [Dots] WGLC on draft-ietf-dots-architecture-08 Roman Danyliw
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Panwei (William)
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- [Dots] 答复: WGLC on draft-ietf-dots-architecture-08 Xialiang (Frank, Network Integration Technology Research Dept)
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 mohamed.boucadair
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Konda, Tirumaleswar Reddy
- Re: [Dots] WGLC on draft-ietf-dots-architecture-08 Roman Danyliw